Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Intel Arc support

Featured Replies

2 hours ago, Beaniiman said:

 

OK, now trying jellyfin for the first time and can not seem to get transcoding to work at all.  I just get an error during playback.  Anyone used jellyfin with an ARC GPU that could help out a newbie.

 

Please share the ffmpeg transcode log file.

  • Replies 402
  • Views 145.1k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Kernel 6.0.1 is stable since today, chances are high that the next Unraid release includes it.

  • DeadDevil6210
    DeadDevil6210

    Oke so this weekend i had some free time to spend and checked out support on unraid 6.12 rc2. I started of fresh by reinstalling my flash drive and putting back a copy of the config folder on to it. 

  • What are your vm settings for the guys getting passthrough working? Any special steps taken? I keep getting code 43 after installing the latest beta drivers. 

Posted Images

Where do I find that, I can try and transcode something and get the log if you can tell me where the log is.

Is this what you need?  See Attached.

Log[1]

1 hour ago, Beaniiman said:

Is this what you need?  See Attached.

Log[1] 5.91 kB · 2 downloads

You didn't set the correct permissions to allow Jellyfin to access /dev/dri/renderD128.

We have detailed instructions on setting up hardware acceleration.

 

On host:

sudo usermod -aG render jellyfin

sudo usermod -aG video jellyfin

 

Docker:

https://jellyfin.org/docs/general/administration/hardware-acceleration/intel/#configure-with-linux-virtualization

 

Also, use QSV instead of VA-API.

Edited by nyanmisaka

Do you need a Linux 6.2 custom kernel for this to work? I tried running Docker Jellyfin with just unRaid 6.12 RC2 and it is detecting the video card after I did the probe stuff. I'm just getting these errors. It works fine if I use my IGPU Intel 13500.

 

[h264_qsv @ 0x56080e203e80] Error during QSV decoding.: device failed (-17) Error while decoding stream #0:0: Input/output error [h264_qsv @ 0x56080e203e80] Err or during QSV decoding.: device failed (-17) Error while decoding stream #0:0: Input/output error

Log_QSV_ARC.txt

30 minutes ago, goodolwheatie said:

Do you need a Linux 6.2 custom kernel for this to work? I tried running Docker Jellyfin with just unRaid 6.12 RC2 and it is detecting the video card after I did the probe stuff. I'm just getting these errors. It works fine if I use my IGPU Intel 13500.

 

[h264_qsv @ 0x56080e203e80] Error during QSV decoding.: device failed (-17) Error while decoding stream #0:0: Input/output error [h264_qsv @ 0x56080e203e80] Err or during QSV decoding.: device failed (-17) Error while decoding stream #0:0: Input/output error

Log_QSV_ARC.txt 704.17 kB · 0 downloads

 

Correct. Linux 6.2 is the first version that has full ARC support at kernel level.

-17 device failed error means your current kernel driver doesn't support QSV yet. You have to wait Unraid to update its kernel.

 

Quote

Jellyfin server 10.8.9+ and the latest jellyfin-ffmpeg5 support Intel ARC discrete GPU on both Windows and Linux 6.2+.

 

Can confirm @DeadDevil6210 method works for me as well with the ASRock A380 on 6.12 RC2 for emby.

 

Still struggling to get handbrake going. For emby Arc Cards aren't supported just yet except in the :beta branch. Once I did that the GPU popped up along side my nvidia gpu.

 

Anyone got it working in handbrake yet?

1 hour ago, nyanmisaka said:

 

Correct. Linux 6.2 is the first version that has full ARC support at kernel level.

-17 device failed error means your current kernel driver doesn't support QSV yet. You have to wait Unraid to update its kernel.

 

 

Makes sense! 😸Thanks for the response cat!

5 hours ago, nyanmisaka said:

You didn't set the correct permissions to allow Jellyfin to access /dev/dri/renderD128.

We have detailed instructions on setting up hardware acceleration.

 

On host:

sudo usermod -aG render jellyfin

sudo usermod -aG video jellyfin

 

Docker:

https://jellyfin.org/docs/general/administration/hardware-acceleration/intel/#configure-with-linux-virtualization

 

Also, use QSV instead of VA-API.

OK I tried that as well as "input" and got 2 different error messages. I never saw anything about creating a user anywhere, what do I do now?  Thanks for the help btw, learning slowly.

# sudo usermod -aG render jellyfin
sudo usermod -aG video jellyfin
sudo usermod -aG input jellyfin
usermod: group 'render' does not exist
usermod: user 'jellyfin' does not exist
usermod: user 'jellyfin' does not exist

 

 

8 hours ago, Beaniiman said:

OK I tried that as well as "input" and got 2 different error messages. I never saw anything about creating a user anywhere, what do I do now?  Thanks for the help btw, learning slowly.

# sudo usermod -aG render jellyfin
sudo usermod -aG video jellyfin
sudo usermod -aG input jellyfin
usermod: group 'render' does not exist
usermod: user 'jellyfin' does not exist
usermod: user 'jellyfin' does not exist

 

 

You didn't use the deb installation package, right? jellyfin user comes with the jellyfin-server*.deb package. If you use portable jellyfin build, you need to add the current user to the render group.

 

usermod -aG render $USER
usermod -aG video $USER

 

Edited by nyanmisaka

hmm, I did that and it appears the same issue is still there.  Looking at the logs its the same problem.

 

I used the jellyfin/jellyfin docker from the store, the official one.  Are there more things I need to change in that config?

10 hours ago, Beaniiman said:

hmm, I did that and it appears the same issue is still there.  Looking at the logs its the same problem.

 

I used the jellyfin/jellyfin docker from the store, the official one.  Are there more things I need to change in that config?

 

https://jellyfin.org/docs/general/administration/hardware-acceleration/intel/#official-docker

 

Read the step 1 and 2. Set the correct "group-add" value.

On 3/25/2023 at 7:17 AM, nyanmisaka said:

 

I think I have the same problem with the groups as Beanliman has! I don't understand what to do with this groups. Is that the standard way to make QSV work or it so hard because Intel arc is still not fully supported?

Anyway it seems that my A380 is recognized and the driver is loaded but for some reason I can't get Tdarr and Jellyfin use it.

I spent the last night troubleshooting but maybe it better to wait for the official support!

FFmpeg.Transcode-2023-03-26_18-01-18_13932a79fd3043d9690bc4e830695695_df787dc8.log

On 3/26/2023 at 10:14 AM, Anadoliev said:

I think I have the same problem with the groups as Beanliman has! I don't understand what to do with this groups. Is that the standard way to make QSV work or it so hard because Intel arc is still not fully supported?

Anyway it seems that my A380 is recognized and the driver is loaded but for some reason I can't get Tdarr and Jellyfin use it.

I spent the last night troubleshooting but maybe it better to wait for the official support!

FFmpeg.Transcode-2023-03-26_18-01-18_13932a79fd3043d9690bc4e830695695_df787dc8.log 13.84 kB · 3 downloads

Yeah, I gave up.  I sure its something silly but I am too new to this level of customization I think.

  • Author

Is 6.12 to include the latest Linux kernel with full support? After six months of talking about it I’m kinda wondering why updating the kernel is so difficult for unraid to do. Is there a lot to be done on the OS side?

  • Community Expert
7 minutes ago, FlyingTexan said:

After six months of talking about it I’m kinda wondering why updating the kernel is so difficult for unraid to do.

Current open-zfs does not support kernel 6.2, only up to 6.1, since Unraid now uses zfs it must wait for a compatible release before updating.

  • 3 weeks later...

I have a 16gb A770. If I upgrade to the RC, will it work out of the box? It is currently sitting in my unraid on the latest stable build but it isn't picking it up. I'd upgrade to the rc if it will make it work though.

  • Community Expert
1 hour ago, IllMethods said:

I have a 16gb A770. If I upgrade to the RC, will it work out of the box? It is currently sitting in my unraid on the latest stable build but it isn't picking it up. I'd upgrade to the rc if it will make it work though.

You may have to do the modprobe switch to enable pre 6.12, I cannot remember if it was seen in 6.11 series. Does it show in lspci?

 

03:00.0 VGA compatible controller: Intel Corporation DG2 [Arc A770] (rev 08)
04:00.0 Audio device: Intel Corporation DG2 Audio Controller

 

root@computenode:~# cat /boot/config/modprobe.d/i915.conf 
options i915 force_probe=56a0

 

I have a 770 in my test server which is currently on 6.12

 

the value should show in 

 

root@computenode:~# dmesg | grep i915

2 hours ago, SimonF said:

You may have to do the modprobe switch to enable pre 6.12, I cannot remember if it was seen in 6.11 series. Does it show in lspci?

 

03:00.0 VGA compatible controller: Intel Corporation DG2 [Arc A770] (rev 08)
04:00.0 Audio device: Intel Corporation DG2 Audio Controller

 

root@computenode:~# cat /boot/config/modprobe.d/i915.conf 
options i915 force_probe=56a0

 

I have a 770 in my test server which is currently on 6.12

 

the value should show in 

 

root@computenode:~# dmesg | grep i915

 

I upgraded to 6.12.0-rc3 2023-04-14

 

It now shows under system devices

 

[8086:56a0]03:00.0 VGA compatible controller: Intel Corporation DG2 [Arc A770] (rev 08)

[8086:4f90]04:00.0 Audio device: Intel Corporation DG2 Audio Controller

 

I still can not see it using intel_gpu_top though. It also doesn't show if I type cd /dev/dri in the terminal. I can only see my igpu. I do have the drivers (I think), just not quite sure where I need to put them.

 

dmesg | grep i915
[   30.877393] i915 0000:00:02.0: vgaarb: deactivate vga console
[   30.877433] i915 0000:00:02.0: [drm] Using Transparent Hugepages
[   30.877996] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[   30.878366] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
[   30.880444] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adls_dmc_ver2_01.bin (v2.1)
[   30.897672] i915 0000:00:02.0: [drm] GuC firmware i915/tgl_guc_70.bin version 70.5.1
[   30.897676] i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc.bin version 7.9.3
[   30.910846] i915 0000:00:02.0: [drm] HuC authenticated
[   30.910855] i915 0000:00:02.0: [drm] GuC submission disabled
[   30.910861] i915 0000:00:02.0: [drm] GuC SLPC disabled
[   30.911678] mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
[   30.911766] i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized
[   30.935475] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
[   30.938966] i915 0000:03:00.0: Your graphics device 56a0 is not properly supported by the driver in this
               kernel version. To force driver probe anyway, use i915.force_probe=56a0
[   31.617122] fbcon: i915drmfb (fb0) is primary device
[   31.652671] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device

Edited by IllMethods

  • Community Expert
13 minutes ago, IllMethods said:

 

I upgraded to 6.12.0-rc3 2023-04-14

 

It now shows under system devices

 

[8086:56a0]03:00.0 VGA compatible controller: Intel Corporation DG2 [Arc A770] (rev 08)

[8086:4f90]04:00.0 Audio device: Intel Corporation DG2 Audio Controller

 

I still can not see it using intel_gpu_top though. It also doesn't show if I type cd /dev/dri in the terminal. I can only see my igpu. I do have the drivers (I think), just not quite sure where I need to put them.

 

dmesg | grep i915
[   30.877393] i915 0000:00:02.0: vgaarb: deactivate vga console
[   30.877433] i915 0000:00:02.0: [drm] Using Transparent Hugepages
[   30.877996] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[   30.878366] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
[   30.880444] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adls_dmc_ver2_01.bin (v2.1)
[   30.897672] i915 0000:00:02.0: [drm] GuC firmware i915/tgl_guc_70.bin version 70.5.1
[   30.897676] i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc.bin version 7.9.3
[   30.910846] i915 0000:00:02.0: [drm] HuC authenticated
[   30.910855] i915 0000:00:02.0: [drm] GuC submission disabled
[   30.910861] i915 0000:00:02.0: [drm] GuC SLPC disabled
[   30.911678] mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
[   30.911766] i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized
[   30.935475] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
[   30.938966] i915 0000:03:00.0: Your graphics device 56a0 is not properly supported by the driver in this
               kernel version. To force driver probe anyway, use i915.force_probe=56a0
[   31.617122] fbcon: i915drmfb (fb0) is primary device
[   31.652671] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device

You need to create this file and reboot.

 

root@computenode:~# cat /boot/config/modprobe.d/i915.conf 
options i915 force_probe=56a0

 

as you can see here the driver is not loaded for the ARC.

 

[   30.938966] i915 0000:03:00.0: Your graphics device 56a0 is not properly supported by the driver in this
               kernel version. To force driver probe anyway, use i915.force_probe=56a0

 

This will show the loaded modules. I suspect currently you will not see anything for modules.

root@computenode:~# lspci -ks 03:00.0
03:00.0 VGA compatible controller: Intel Corporation DG2 [Arc A770] (rev 08)
        Subsystem: Intel Corporation Device 1020
        Kernel driver in use: vfio-pci
        Kernel modules: i915

 

intel_gpu_top -L will show devices if you have multiple you may need to specify the card.

 

My arc is in a VM at present.

 

root@computenode:~# intel_gpu_top  -d pci:slot=0000:03:00.0
Requested device pci:slot=0000:03:00.0 not found!

root@computenode:~# 

I will create the file and reboot

 

lspci -ks 03:00.0
03:00.0 VGA compatible controller: Intel Corporation DG2 [Arc A770] (rev 08)
        Subsystem: Intel Corporation Device 1020
        Kernel modules: i915

 

This is what I'm getting before doing so

16 minutes ago, SimonF said:

root@computenode:~# cat /boot/config/modprobe.d/i915.conf 
options i915 force_probe=56a0

 

dmesg | grep i915
[   32.955884] i915 0000:00:02.0: vgaarb: deactivate vga console
[   32.955915] i915 0000:00:02.0: [drm] Using Transparent Hugepages
[   32.956484] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[   32.956854] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
[   32.958660] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adls_dmc_ver2_01.bin (v2.1)
[   32.975842] i915 0000:00:02.0: [drm] GuC firmware i915/tgl_guc_70.bin version 70.5.1
[   32.975846] i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc.bin version 7.9.3
[   32.989623] i915 0000:00:02.0: [drm] HuC authenticated
[   32.989633] i915 0000:00:02.0: [drm] GuC submission disabled
[   32.989639] i915 0000:00:02.0: [drm] GuC SLPC disabled
[   32.990448] mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
[   32.990540] i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized
[   33.012630] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
[   33.015885] i915 0000:03:00.0: enabling device (0000 -> 0002)
[   33.015925] i915 0000:03:00.0: [drm] Incompatible option enable_guc=3 - HuC is not supported!
[   33.616625] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   33.616690] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   33.693781] fbcon: i915drmfb (fb0) is primary device
[   33.727223] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
[   34.217386] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   34.217434] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   34.818104] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   34.818148] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   35.418812] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   35.418854] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   36.019520] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   36.019568] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   36.019663] i915 0000:03:00.0: [drm] mslice mask all zero!
[   36.620249] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   36.620291] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   37.220955] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   37.220996] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   37.821683] [drm:fw_domain_wait_ack_set [i915]] *ERROR* render: timed out waiting for forcewake ack request.
[   37.822130] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   38.423202] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   38.423652] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   39.024722] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   39.025165] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   39.626248] [drm:fw_domain_wait_ack_set [i915]] *ERROR* render: timed out waiting for forcewake ack request.
[   39.626690] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   40.227770] [drm:fw_domain_wait_ack_set [i915]] *ERROR* render: timed out waiting for forcewake ack request.
[   40.228218] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   40.829305] [drm:fw_domain_wait_ack_set [i915]] *ERROR* render: timed out waiting for forcewake ack request.
[   40.829752] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   41.430835] [drm:fw_domain_wait_ack_set [i915]] *ERROR* render: timed out waiting for forcewake ack request.
[   41.431916] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   42.033674] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   42.034084] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   42.635110] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   42.635520] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   43.236562] [drm:fw_domain_wait_ack_set [i915]] *ERROR* render: timed out waiting for forcewake ack request.
[   43.236976] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   43.838003] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   43.838351] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   43.839440] i915 0000:03:00.0: [drm] *ERROR* rcs'0 reset request timed out: {request: 00000001, RESET_CTL: 00000000}
[   43.840460] i915 0000:03:00.0: [drm] *ERROR* rcs'0 reset request timed out: {request: 00000001, RESET_CTL: 00000000}
[   43.841473] i915 0000:03:00.0: [drm] *ERROR* bcs'0 reset request timed out: {request: 00000001, RESET_CTL: 00000000}
[   44.442481] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   44.442840] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   45.043820] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   45.044168] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   45.645130] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   45.645472] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   46.246433] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   46.246775] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   46.847739] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   46.848086] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   47.449051] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   47.449399] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   48.050359] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   48.050707] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   48.651679] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   48.652037] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   49.253045] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   49.253573] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   49.854754] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   49.855318] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   50.456532] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   50.456921] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   50.457357] i915 0000:03:00.0: [drm] *ERROR* CCS_BASE_ADDR register did not have expected value
[   50.457683] i915 0000:03:00.0: BAR 0: releasing [mem 0x41000000-0x41ffffff 64bit]
[   50.457997] i915 0000:03:00.0: BAR 2: releasing [mem 0x6000000000-0x63ffffffff 64bit pref]
[   50.458391] i915 0000:03:00.0: [drm] Failed to resize BAR2 to 1M (-EINVAL)
[   50.458838] i915 0000:03:00.0: BAR 2: assigned [mem 0x6000000000-0x63ffffffff 64bit pref]
[   50.459530] i915 0000:03:00.0: BAR 0: assigned [mem 0x41000000-0x41ffffff 64bit]
[   50.460041] i915 0000:03:00.0: [drm] *ERROR* Failed to setup region(-5) type=1
[   50.494242] i915 0000:03:00.0: Device initialization failed (-5)
[   50.494585] i915: probe of 0000:03:00.0 failed with error -5

  • Community Expert
5 minutes ago, IllMethods said:

 

dmesg | grep i915
[   32.955884] i915 0000:00:02.0: vgaarb: deactivate vga console
[   32.955915] i915 0000:00:02.0: [drm] Using Transparent Hugepages
[   32.956484] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[   32.956854] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
[   32.958660] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adls_dmc_ver2_01.bin (v2.1)
[   32.975842] i915 0000:00:02.0: [drm] GuC firmware i915/tgl_guc_70.bin version 70.5.1
[   32.975846] i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc.bin version 7.9.3
[   32.989623] i915 0000:00:02.0: [drm] HuC authenticated
[   32.989633] i915 0000:00:02.0: [drm] GuC submission disabled
[   32.989639] i915 0000:00:02.0: [drm] GuC SLPC disabled
[   32.990448] mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
[   32.990540] i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized
[   33.012630] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
[   33.015885] i915 0000:03:00.0: enabling device (0000 -> 0002)
[   33.015925] i915 0000:03:00.0: [drm] Incompatible option enable_guc=3 - HuC is not supported!
[   33.616625] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   33.616690] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   33.693781] fbcon: i915drmfb (fb0) is primary device
[   33.727223] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
[   34.217386] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   34.217434] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   34.818104] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   34.818148] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   35.418812] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   35.418854] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   36.019520] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   36.019568] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   36.019663] i915 0000:03:00.0: [drm] mslice mask all zero!
[   36.620249] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   36.620291] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   37.220955] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   37.220996] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   37.821683] [drm:fw_domain_wait_ack_set [i915]] *ERROR* render: timed out waiting for forcewake ack request.
[   37.822130] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   38.423202] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   38.423652] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   39.024722] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   39.025165] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   39.626248] [drm:fw_domain_wait_ack_set [i915]] *ERROR* render: timed out waiting for forcewake ack request.
[   39.626690] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   40.227770] [drm:fw_domain_wait_ack_set [i915]] *ERROR* render: timed out waiting for forcewake ack request.
[   40.228218] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   40.829305] [drm:fw_domain_wait_ack_set [i915]] *ERROR* render: timed out waiting for forcewake ack request.
[   40.829752] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   41.430835] [drm:fw_domain_wait_ack_set [i915]] *ERROR* render: timed out waiting for forcewake ack request.
[   41.431916] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   42.033674] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   42.034084] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   42.635110] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   42.635520] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   43.236562] [drm:fw_domain_wait_ack_set [i915]] *ERROR* render: timed out waiting for forcewake ack request.
[   43.236976] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   43.838003] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   43.838351] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   43.839440] i915 0000:03:00.0: [drm] *ERROR* rcs'0 reset request timed out: {request: 00000001, RESET_CTL: 00000000}
[   43.840460] i915 0000:03:00.0: [drm] *ERROR* rcs'0 reset request timed out: {request: 00000001, RESET_CTL: 00000000}
[   43.841473] i915 0000:03:00.0: [drm] *ERROR* bcs'0 reset request timed out: {request: 00000001, RESET_CTL: 00000000}
[   44.442481] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   44.442840] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   45.043820] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   45.044168] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   45.645130] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   45.645472] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   46.246433] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   46.246775] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   46.847739] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   46.848086] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   47.449051] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   47.449399] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   48.050359] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   48.050707] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   48.651679] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   48.652037] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   49.253045] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   49.253573] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   49.854754] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   49.855318] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   50.456532] [drm:fw_domain_wait_ack_set [i915]] *ERROR* gt: timed out waiting for forcewake ack request.
[   50.456921] i915 0000:03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0xd7/0xec [i915]
[   50.457357] i915 0000:03:00.0: [drm] *ERROR* CCS_BASE_ADDR register did not have expected value
[   50.457683] i915 0000:03:00.0: BAR 0: releasing [mem 0x41000000-0x41ffffff 64bit]
[   50.457997] i915 0000:03:00.0: BAR 2: releasing [mem 0x6000000000-0x63ffffffff 64bit pref]
[   50.458391] i915 0000:03:00.0: [drm] Failed to resize BAR2 to 1M (-EINVAL)
[   50.458838] i915 0000:03:00.0: BAR 2: assigned [mem 0x6000000000-0x63ffffffff 64bit pref]
[   50.459530] i915 0000:03:00.0: BAR 0: assigned [mem 0x41000000-0x41ffffff 64bit]
[   50.460041] i915 0000:03:00.0: [drm] *ERROR* Failed to setup region(-5) type=1
[   50.494242] i915 0000:03:00.0: Device initialization failed (-5)
[   50.494585] i915: probe of 0000:03:00.0 failed with error -5

Do you have resizable Bar and above 4G nemory enabled in the bios?

Yes they're both enabled

I had a 3060 installed but I swapped it out for this card

 

I just double checked to be sure

20230424_022839.jpg

Edited by IllMethods

Strange, it works now. It took a couple reboots though. So now in my apps, do I need to map to /dev/dri/card0 now instead of /dev/dri/?

 

Changing to /dev/dri/renderD128 seems to work for the iGPU, /renderD129 doesn't seem to do anything to get the a770 to work.

 

I guess there is still a bit more waiting to do.

Edited by IllMethods

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.