March 28, 20251 yr dg1 gpu can be seen in system devices, config has been set as below, but can't still be used.
March 28, 20251 yr Community Expert 9 hours ago, allenchou1994 said: dg1 gpu can be seen in system devices, config has been set as below, but can't still be used. Post diagnostics
March 31, 20251 yr Author On 3/28/2025 at 9:23 PM, SimonF said: Post diagnostics here is my diagnostics tower-diagnostics-20250331-1845.zip
April 1, 20251 yr Community Expert 10 hours ago, allenchou1994 said: here is my diagnostics tower-diagnostics-20250331-1845.zip 210.82 kB · 0 downloads You need to have the following. Mar 31 18:38:00 Tower kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device Mar 31 18:38:00 Tower kernel: i915 0000:04:00.0: Your graphics device 4908 is not properly supported by i915 in this Mar 31 18:38:00 Tower kernel: kernel version. To force driver probe anyway, use i915.force_probe=4908 Mar 31 18:38:00 Tower kernel: module parameter or CONFIG_DRM_I915_FORCE_PROBE=4908 configuration option, Mar 31 18:38:00 Tower kernel: or (recommended) check for kernel updates. Mar 31 18:38:00 Tower kernel: xe 0000:04:00.0: Your graphics device 4908 is not officially supported Mar 31 18:38:00 Tower kernel: by xe driver in this kernel version. To force Xe probe, Mar 31 18:38:00 Tower kernel: use xe.force_probe='4908' and i915.force_probe='!4908' Mar 31 18:38:00 Tower kernel: module parameters or CONFIG_DRM_XE_FORCE_PROBE='4908' and Mar 31 18:38:00 Tower kernel: CONFIG_DRM_I915_FORCE_PROBE='!4908' configuration options. Examples in system drivers
April 1, 20251 yr Author 11 hours ago, SimonF said: You need to have the following. Mar 31 18:38:00 Tower kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device Mar 31 18:38:00 Tower kernel: i915 0000:04:00.0: Your graphics device 4908 is not properly supported by i915 in this Mar 31 18:38:00 Tower kernel: kernel version. To force driver probe anyway, use i915.force_probe=4908 Mar 31 18:38:00 Tower kernel: module parameter or CONFIG_DRM_I915_FORCE_PROBE=4908 configuration option, Mar 31 18:38:00 Tower kernel: or (recommended) check for kernel updates. Mar 31 18:38:00 Tower kernel: xe 0000:04:00.0: Your graphics device 4908 is not officially supported Mar 31 18:38:00 Tower kernel: by xe driver in this kernel version. To force Xe probe, Mar 31 18:38:00 Tower kernel: use xe.force_probe='4908' and i915.force_probe='!4908' Mar 31 18:38:00 Tower kernel: module parameters or CONFIG_DRM_XE_FORCE_PROBE='4908' and Mar 31 18:38:00 Tower kernel: CONFIG_DRM_I915_FORCE_PROBE='!4908' configuration options. Examples in system drivers my dg1 gpu id is 4098 system drivers has been modified like
April 2, 20251 yr Community Expert 7 hours ago, allenchou1994 said: my dg1 gpu id is 4098 system drivers has been modified like Did you reboot after adding entries to system drivers?
April 7, 20251 yr Author On 4/2/2025 at 2:34 PM, SimonF said: Did you reboot after adding entries to system drivers? sure i did， just don't work
April 9, 20251 yr Author On 4/8/2025 at 3:05 AM, SimonF said: Can you provide current diagnostics tower-diagnostics-20250409-1151.zip
April 9, 20251 yr Community Expert Solution 3 hours ago, allenchou1994 said: tower-diagnostics-20250409-1151.zip 529.17 kB · 0 downloads Looks like the modprobe are not in place. Apr 7 14:54:32 Tower kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device Apr 7 14:54:32 Tower kernel: i915 0000:04:00.0: Your graphics device 4908 is not properly supported by i915 in this Apr 7 14:54:32 Tower kernel: kernel version. To force driver probe anyway, use i915.force_probe=4908 Apr 7 14:54:32 Tower kernel: module parameter or CONFIG_DRM_I915_FORCE_PROBE=4908 configuration option, Apr 7 14:54:32 Tower kernel: or (recommended) check for kernel updates. Apr 7 14:54:32 Tower kernel: xe 0000:04:00.0: Your graphics device 4908 is not officially supported Apr 7 14:54:32 Tower kernel: by xe driver in this kernel version. To force Xe probe, Apr 7 14:54:32 Tower kernel: use xe.force_probe='4908' and i915.force_probe='!4908' Apr 7 14:54:32 Tower kernel: module parameters or CONFIG_DRM_XE_FORCE_PROBE='4908' and Apr 7 14:54:32 Tower kernel: CONFIG_DRM_I915_FORCE_PROBE='!4908' configuration options. You modprobe files on the boot should look like this. root@computenode:~# cat /boot/config/modprobe.d/i915.conf options i915 force_probe=!4908 root@computenode:~# cat /boot/config/modprobe.d/xe.conf options xe force_probe=4908 root@computenode:~# Something is spamming the logs. Maybe a plugin doing fan control? Apr 7 15:03:36 Tower kernel: pgrep[43970]: segfault at 14 ip 000015333483c74e sp 00007ffcd20cdd20 error 6 in libprocps.so.8.0.2[974e,153334837000+a000] likely on CPU 5 (core 5, socket 0) Apr 7 15:03:36 Tower kernel: Code: 75 0a 48 83 c4 50 5d 41 5c 41 5d c3 e8 cb af ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 54 55 48 89 f5 53 48 89 fb <c7> 47 14 00 00 00 00 48 85 f6 0f 84 52 01 00 00 48 8b 86 d0 01 00 Apr 7 15:04:01 Tower root: pwm-hdd-fan: set fan to value 143
April 13, 20251 yr Author On 4/9/2025 at 3:14 PM, SimonF said: Looks like the modprobe are not in place. Apr 7 14:54:32 Tower kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device Apr 7 14:54:32 Tower kernel: i915 0000:04:00.0: Your graphics device 4908 is not properly supported by i915 in this Apr 7 14:54:32 Tower kernel: kernel version. To force driver probe anyway, use i915.force_probe=4908 Apr 7 14:54:32 Tower kernel: module parameter or CONFIG_DRM_I915_FORCE_PROBE=4908 configuration option, Apr 7 14:54:32 Tower kernel: or (recommended) check for kernel updates. Apr 7 14:54:32 Tower kernel: xe 0000:04:00.0: Your graphics device 4908 is not officially supported Apr 7 14:54:32 Tower kernel: by xe driver in this kernel version. To force Xe probe, Apr 7 14:54:32 Tower kernel: use xe.force_probe='4908' and i915.force_probe='!4908' Apr 7 14:54:32 Tower kernel: module parameters or CONFIG_DRM_XE_FORCE_PROBE='4908' and Apr 7 14:54:32 Tower kernel: CONFIG_DRM_I915_FORCE_PROBE='!4908' configuration options. You modprobe files on the boot should look like this. root@computenode:~# cat /boot/config/modprobe.d/i915.conf options i915 force_probe=!4908 root@computenode:~# cat /boot/config/modprobe.d/xe.conf options xe force_probe=4908 root@computenode:~# Something is spamming the logs. Maybe a plugin doing fan control? Apr 7 15:03:36 Tower kernel: pgrep[43970]: segfault at 14 ip 000015333483c74e sp 00007ffcd20cdd20 error 6 in libprocps.so.8.0.2[974e,153334837000+a000] likely on CPU 5 (core 5, socket 0) Apr 7 15:03:36 Tower kernel: Code: 75 0a 48 83 c4 50 5d 41 5c 41 5d c3 e8 cb af ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 41 54 55 48 89 f5 53 48 89 fb <c7> 47 14 00 00 00 00 48 85 f6 0f 84 52 01 00 00 48 8b 86 d0 01 00 Apr 7 15:04:01 Tower root: pwm-hdd-fan: set fan to value 143 thank you! xe driver could be used now, but there is still some problem gpu statistics seems don't work with dg1, information about dg1 can rarely be shown. i changed bios setting for dg1 to be in pcie 3.0 *4, but seems it only worked in pcie 1.0*1
September 7, 2025Sep 7 The pcie bug is only a display one and well known for Intel Arc. lspci shows since years only pcie gen1 x1 but the cards are still functioning normally with their full bus.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.