Issues with hardware detection failing on ubuntu 24.10 with Intel B580

[lozanoeg 0]

Started with both the docker version and the native version and both give the same error 18. If I don't use the beta i get the same error but with error code -1. both /dev/dri/renderD128 and card 1 are set and the permissions match the GIDLIST for the docker.

embyserver.txt hardware_detection-63874128866.txt

[Luke 39835]

Hi @lozanoegand what happens on the beta?

[lozanoeg 0]

I pulled the most recent beta. I get the same error 18 value however it seems that it can recognize that it is a b580 and not just call it a generic intel graphics

hardware_detection-63875019137.txt

[Q-Droid 861]

According to Intel those devices are supported in the Linux kernel 6.12 and you're on 6.11.

 

[lozanoeg 0]

yes, i rolled up to 6.12 and did the same test but rolled back to make sure i wasn't changing too many variables. the ubuntu repo added for 24.10 also backported the drivers for 6.11 at least from my understanding of the install on ubuntu page.

Edit: Here is the log for 6.12

hardware_detection-63875053217.txt

Edited February 13 by lozanoeg

[jaybird2203 20]

Can confirm that the same -1 error is observed running the 4.8.10 docker with kernel 6.14 but using Unraid as base OS. 

 hardware_detection-63875061948.txt

Edited February 13 by jaybird2203

[Q-Droid 861]

Have either of you tried with a 6.12+ kernel and Emby beta release? Chances are that the stable release is going to have older Intel driver/libs and ffmpeg.

 

[lozanoeg 0]

1 hour ago, Q-Droid said:

Have either of you tried with a 6.12+ kernel and Emby beta release? Chances are that the stable release is going to have older Intel driver/libs and ffmpeg.

 

Yes my last reply is the logs from beta release and kernel 6.12.0-061200-generic

[Q-Droid 861]

Ah, I see that your first hw log (hardware_detection-63874128866.txt) was the beta on 6.12x and the error was the same as your other combos, consistently Error 18. 

Are you mapping individual DRI devices or the /dev/dri path for the Docker container?

Either way with such a new card it'll likely have to be addressed by the devs in the beta branch.

 

 

[lozanoeg 0]

I currently am mapping /dev/dri and have not tried mapping the devices directly. I did figure since it's brand new and they switched to only the XE kernel drivers for battlemage and not the support the old drivers that it might have some hiccups. If any devs need it though, I've got time to be a guinea pig for testing. I know the battlemage cards are being scalped like crazy

[Q-Droid 861]

I think /dev/dri is the better approach but some people try to isolate them if multiple GPUs are available.

 

[jaybird2203 20]

I also map /dev/dri path itself. 

Spun up a docker of the beta channel specifically for this situation so able to dig deep for any devs as well if that is of value.

[BlackDub 44]

On 15/02/2025 at 01:07, jaybird2203 said:

I also map /dev/dri path itself. 

Spun up a docker of the beta channel specifically for this situation so able to dig deep for any devs as well if that is of value.

Any news on this? I have the same problem, ubuntu 24.04.2 lts with 6.13.5 kernel, Emby native and emby docker, same problem error 18

[lozanoeg 0]

15 hours ago, BlackDub said:

Any news on this? I have the same problem, ubuntu 24.04.2 lts with 6.13.5 kernel, Emby native and emby docker, same problem error 18

I just pulled the most recent beta and updated drivers today, still error 18, I haven’t looked to see if ffmpeg even supports arc battle mage yet though so we may be waiting for that

[nanmengong 3]

On 2/14/2025 at 5:59 AM, jaybird2203 said:

Can confirm that the same -1 error is observed running the 4.8.10 docker with kernel 6.14 but using Unraid as base OS. 

  hardware_detection-63875061948.txt 139.01 kB · 3 downloads

same issue, but i have dg1 xe graphic card.

[nanmengong 3]

hi, i have some other experience.

 

most of emby release packages have build-in vaapi, opencl and qsv driver. but in archlinux platform(my test env is kernel 6.13+), need to install intel vaapi and qsv manually, using 'pacman' command. this method had a newer driver and emby 4.8.10 can use vaapi hw well but qsv is crash.

Edited March 13 by nanmengong

[Luke 39835]

@lozanoeghas this helped?

[lozanoeg 0]

On 3/28/2025 at 1:18 AM, Luke said:

@lozanoeghas this helped?

So far I still have the same issue. I updated again today with the newest beta

[benpicard 15]

I have the same error 18 with an Arc B580

[jaybird2203 20]

@LukeAny progress getting the hardware detection functioning with these Battlemage GPUs? 

Can confirm other docker containers can detect and use the GPU with the same passthrough variables I used for Emby yet only Emby cannot detect, and by extension use, the GPU. 

For current reference I am still running 4.8.11 with kernel 6.14.1 now. 

Edited April 20 by jaybird2203

[byakuya32 24]

I have this same error on the Beta @Luke with a B580

[byakuya32 24]

hardware_detection-63881224154.txt

[byakuya32 24]

Looking arround on Linux it looks like Intel no longer use the i915 so all new Intel igpus will be effected by this. Additional it looks like ffmpeg 7.1 is needed to use the new Intel driver. Does this help @Luke?

[jaybird2203 20]

@byakuya32Makes sense, my other docker that can detect and transcode on the b580 uses 7.1.1 as of right now. 

@Luke Any chance one of the devs can advise a command etc that can be ran to attempt a newer ffmpeg version than the default for the time being? Referring to the same as defined in this link from the tips and tutorials section.

[benpicard 15]

I forgot about this thread. I'm having the same problem :