igpu - wits end!

[zapp8rannigan]

Hi all,

 

I don't think this is actually an unraid problem but i'm not sure where else to turn. I'm trying to get my igpu to be recognised.

 

I think i have my bios setup correctly (screenshot). but when i type cd dev/dri nothing is coming up.

 

Any ideas?

 

Specs are i5-11600 with an Asus Prime Z590-A

[SimonF]

4 hours ago, zapp8rannigan said:

Hi all,

 

I don't think this is actually an unraid problem but i'm not sure where else to turn. I'm trying to get my igpu to be recognised.

 

I think i have my bios setup correctly (screenshot). but when i type cd dev/dri nothing is coming up.

 

Any ideas?

 

Specs are i5-11600 with an Asus Prime Z590-A

Have you followed requirements to enable the i915 driver, if you are on 6.10rc2 + it is enabled by default.

 

but before this release you have to do and this from 6.9.0 onwards. 

 

GPU Driver Integration
Unraid OS now includes selected in-tree GPU drivers: ast (Aspeed), i915 (Intel), amdgpu and radeon (AMD).  For backward compatibility, these drivers are blacklisted by default via corresponding conf files in /etc/modprobe.d:

/etc/modprobe.d/ast.conf
/etc/modprobe.d/i915.conf
/etc/modprobe.d/amdgpu.conf
/etc/modprobe.d/radeon.conf
Each of these files has a single line that blacklists the driver, preventing it from being loaded by the Linux kernel.

It is possible to override the settings in these files by creating a custom conf file in the config/modprobe.d directory on your USB flash boot device.  For example, to un-blacklist the amdgpu driver create an empty file by typing this command in a Terminal session:

touch /boot/config/modprobe.d/amdgpu.conf
This only needs to be done once, it does not need to be added to your go script.


In 6.9.1, if your go script contains a modprobe command for your GPU and/or a command to fix the permissions on /dev/dri, you should remove them:

modprobe amdgpu
chmod -R 777 /dev/dri
In 6.9.0, if the docker you are using is unable to access the GPU, add/keep this line to your go script:

chmod -R 777 /dev/dri
but remove this one:

modprobe amdgpu

 

[zapp8rannigan]

5 hours ago, SimonF said:

... but before this release you have to do and this from 6.9.0 onwards. 

 

GPU Driver Integration
Unraid OS now includes selected in-tree GPU drivers: ast (Aspeed), i915 (Intel), amdgpu and radeon (AMD).  For backward compatibility, these drivers are blacklisted by default via corresponding conf files in /etc/modprobe.d:

/etc/modprobe.d/ast.conf
/etc/modprobe.d/i915.conf
/etc/modprobe.d/amdgpu.conf
/etc/modprobe.d/radeon.conf
Each of these files has a single line that blacklists the driver, preventing it from being loaded by the Linux kernel.

It is possible to override the settings in these files by creating a custom conf file in the config/modprobe.d directory on your USB flash boot device.  For example, to un-blacklist the amdgpu driver create an empty file by typing this command in a Terminal session:

touch /boot/config/modprobe.d/amdgpu.conf
This only needs to be done once, it does not need to be added to your go script.


In 6.9.1, if your go script contains a modprobe command for your GPU and/or a command to fix the permissions on /dev/dri, you should remove them:

modprobe amdgpu
chmod -R 777 /dev/dri
In 6.9.0, if the docker you are using is unable to access the GPU, add/keep this line to your go script:

chmod -R 777 /dev/dri
but remove this one:

modprobe amdgpu

 

 

Thanks for replying. I'm on 6.10rc2, do I need to do the above as well? Or is that also pre rc2?

[SimonF]

10 minutes ago, zapp8rannigan said:

 

Thanks for replying. I'm on 6.10rc2, do I need to do the above as well? Or is that also pre rc2?

From RC2

 

In-tree GPU drivers are now loaded by default if corresponding hardware is detected:

amdgpu

ast

i915

radeon

 

These drivers are required mostly for motherboard on-board graphics used in GUI boot mode.  Loading of a driver can be prohibited by creating the appropriate file named after the driver:

echo "blacklist i915" > /boot/config/modprobe.d/i915.conf

Alternately, the device can be isolated from Linux entirely via the System Devices page.  Note that in Unraid OS 6.9 releases the in-tree GPU drivers are blacklisted by default and to enabling loading a driver you need to create an empty "conf" file.  After upgrading to Unraid OS 6.10 you may delete those files, or leave them as-is.  This change was made to greatly improve the Desktop GUI experience for new users.

 

Do you see i915 loaded for the igpu if you hover on the system devices page?

 

 

 

[zapp8rannigan]

39 minutes ago, SimonF said:

Do you see i915 loaded for the igpu if you hover on the system devices page?

 

 

 

 

Yep its listed there.
I've just had a look in the modprobe.d folder under config and its empty...could that be my issue?

When i load into gui mode i just get a black screen and a flashing text line at the top

[SimonF]

48 minutes ago, zapp8rannigan said:

 

Yep its listed there.
I've just had a look in the modprobe.d folder under config and its empty...could that be my issue?

When i load into gui mode i just get a black screen and a flashing text line at the top

Sorry error on my part the driver is not loaded, Should look like this.

My i915 is blacklisted. You could try touch /boot/config/modprobe.d/i915.conf to see if that resolves the issue but should be loading by default.

 

Do you see anything in the logs? I have an alderlake so need to add an option.

 

root@computenode:/var/log# cat /var/log/syslog  | grep i915
Apr  9 11:55:45 computenode kernel: i915 0000:00:02.0: Your graphics device 4680 is not properly supported by the driver in this
Apr  9 11:55:45 computenode kernel: kernel version. To force driver probe anyway, use i915.force_probe=4680
Apr  9 13:15:42 computenode kernel: i915: unknown parameter 'option.force_probe' ignored
Apr  9 13:15:42 computenode kernel: i915 0000:00:02.0: Your graphics device 4680 is not properly supported by the driver in this
Apr  9 13:15:42 computenode kernel: kernel version. To force driver probe anyway, use i915.force_probe=4680
Apr  9 13:16:04 computenode kernel: i915: unknown parameter 'i915.force_probe' ignored
Apr  9 13:16:04 computenode kernel: i915 0000:00:02.0: Your graphics device 4680 is not properly supported by the driver in this
Apr  9 13:16:04 computenode kernel: kernel version. To force driver probe anyway, use i915.force_probe=4680
Apr  9 13:23:27 computenode kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access
Apr  9 13:23:27 computenode kernel: fb0: switching to i915 from EFI VGA
Apr  9 13:23:27 computenode kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Apr  9 13:23:27 computenode kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Apr  9 13:23:27 computenode kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adls_dmc_ver2_01.bin (v2.1)
Apr  9 13:23:27 computenode kernel: i915 0000:00:02.0: [drm] GuC firmware i915/tgl_guc_62.0.0.bin version 62.0 submission:disabled
Apr  9 13:23:27 computenode kernel: i915 0000:00:02.0: [drm] GuC SLPC: disabled
Apr  9 13:23:27 computenode kernel: i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 authenticated:yes
Apr  9 13:23:27 computenode kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
Apr  9 13:23:27 computenode kernel: fbcon: i915drmfb (fb0) is primary device
Apr  9 13:23:28 computenode kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device

 

 

[zapp8rannigan]

44 minutes ago, SimonF said:

Sorry error on my part the driver is not loaded, Should look like this.

 Sorry i don't understrand, whats the difference? other than mine lists the UHD750?

As for the logs which ones am i looking for, i've trying the system logs under tools but theres nothing there that mentions i915

Would my diagnostics help?

 

I've just tried to reboot with the conf file in modprobe but no difference. Starting to think its this motherboard, I've had issues with ASUS boards in the past, I'm on the current firmware but still no joy

babs-diagnostics-20220409-1413.zip

Edited April 9, 2022 by zapp8rannigan

[SimonF]

1 hour ago, zapp8rannigan said:

I've just tried to reboot with the conf file in modprobe but no difference. Starting to think its this motherboard, I've had issues with ASUS boards in the past, I'm on the current firmware but still no joy

Ok your CPU needs a force probe also. Have a look at this tread, but I am not sure which one will be for yours.

 

Format will be similar to this. If you run modprobe i915 you should see correct version in the syslog.

[zapp8rannigan]

Okay,

 

Been trying a few different things, nothing working so far.
Tried the force probe as shown in your notepad screenshot. no joy
tried the same again with "options i915 enable_guc=2" also added, and also tried deleting them and adding i915.force_probe=4c8a to the syslinux config

Nothing working.

 

Just got to your post asking the guy to run:

root@computenode:~# modprobe -c | grep force_probe

root@computenode:~# dmesg | grep i915 lsmod | grep i915

 

I've just done that but can't see any errors?

 

root@Babs:~# dmesg  | grep i915
lsmod  | grep i915
[   26.369731] i915 0000:00:02.0: [drm] VT-d active for gfx access
[   26.373454] i915 0000:00:02.0: vgaarb: deactivate vga console
[   26.375489] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   26.379702] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/rkl_dmc_ver2_02.bin (v2.2)
[   26.495381] i915 0000:00:02.0: [drm] GuC firmware i915/tgl_guc_49.0.1.bin version 49.0 submission:disabled
[   26.495385] i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc_7.5.0.bin version 7.5 authenticated:yes
[   26.508315] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
[   26.544716] fbcon: i915 (fb0) is primary device
[   26.612950] i915 0000:00:02.0: [drm] fb0: i915 frame buffer device
i915                 2396160  1
iosf_mbi               16384  1 i915
ttm                    69632  1 i915
drm_kms_helper        245760  1 i915
drm                   487424  4 drm_kms_helper,i915,ttm
intel_gtt              24576  1 i915
i2c_algo_bit           16384  2 igb,i915
i2c_core               86016  7 drm_kms_helper,i2c_algo_bit,igb,i2c_smbus,i2c_i801,i915,drm
video                  49152  1 i915
backlight              20480  3 video,i915,drm
root@Babs:~#

 

 

root@Babs:~# lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04)
root@Babs:~#

 

root@Babs:~# ls -la /dev/dri
total 0
drwxrwxrwx  3 root root       100 Apr 10 00:06 ./
drwxr-xr-x 16 root root      4000 Apr 10 00:08 ../
drwxrwxrwx  2 root root        80 Apr 10 00:06 by-path/
crwxrwxrwx  1 root video 226,   0 Apr 10 00:06 card0
crwxrwxrwx  1 root video 226, 128 Apr 10 00:06 renderD128

 

 

Hmm feel like it might actually be working now....just had a mess about on plex and it appears to be transcoding with the igpu. Just going to try booting into gui mode now.

Edited April 9, 2022 by zapp8rannigan