Emby won't detect my Intel Arc310

[JonBo 1]

Hi Everyone,

I've been using Jellyfin and have encountered some frustrations so I thought I'd try Emby Premier as a comparison.  Thing is....I can't seem to get it to detect my Intel Arc310.

I see the card and renderer in my /dev/dri folder but the hardware detection is only showing me information on my Intel CPU GPU and not the arc310.  In jellyfin I just told it to use the D129 renderer instead of the D128 but I don't see that option anywhere.

Attaching my hardware detection as well.

hardware_detection-63873488857.txt

[JonBo 1]

Of note, I can see all the scripts in /app/emby/bin all try to access emby from /opt/emby-server which doesn't exist.  I've symlinked that in and the scripts seem to run manually and they also list my arc310.

 

I'll try and restart emby and get a fresh detection.

[JonBo 1]

That change didn't make any difference at all.  Attaching my server logs here.

embyserver.txt

[StuartKicks 0]

Did you get any further with this?

[yocker 1247]

On 1/26/2025 at 9:05 PM, JonBo said:

Hi Everyone,

I've been using Jellyfin and have encountered some frustrations so I thought I'd try Emby Premier as a comparison.  Thing is....I can't seem to get it to detect my Intel Arc310.

I see the card and renderer in my /dev/dri folder but the hardware detection is only showing me information on my Intel CPU GPU and not the arc310.  In jellyfin I just told it to use the D129 renderer instead of the D128 but I don't see that option anywhere.

Attaching my hardware detection as well.

hardware_detection-63873488857.txt 174.19 kB · 3 downloads

How are Emby's permissions on your computer? Might be a permission problem.

[Luke 42077]

@JonBo?

[JonBo 1]

Hi!

I've made no progress so far.  Nothing I've tried as worked, but to be fair, I've been on vacation as well so I'm just getting back to this.

I run in Docker using docker-compose and I've run it in privileged mode currently which I expect would remove any permission issues.

So, no progress but I'll experiment around with it shortly again. Thanks for asking!

[JonBo 1]

Okay, progress is being made.  I realized I was using some third-party packaging of Emby so I've switched to the official Emby image (duh!).

Now neither card is being detected but at least it is telling me that!  I think @yockeris onto something with the permission issue.  The image is running privileged so I don't see why there would be a problem.  But I'll keep digging.  

Any input would be appreciated.  Attaching my hardware detection log in case anyone is keen to help

 

 

hardware_detection-63875036673.txt

embyserver.txt

Edited February 13, 2025 by JonBo

[JonBo 1]

Okay, I think I've solved it.  The problem seems to come from having multiple Renderers and failure when detecting the CUDA settings for NVidia.

Whenever I have both my integrated and discrete graphics cards ( renderD128 and renderD129) in the /dev/dri the hardware detection starts looking at renderD128 but then stops detection after it gets an error trying to check NVidia settings!

So, I changed my docker compose to only mount a single renderD129 like this:

devices:
      - /dev/dri/renderD129:/dev/dri/renderD129
      - /dev/dri/card2:/dev/dri/card2
 

And, when running in non-priveleged mode, Emby only gets to see this single card and detects it correctly!  But, of note, it still exits with a failure when it is trying to scan for NVidia functions!!!!!!

 

So, workaround in place, but I'd say there is a bug at play here.  Unless there is a way to configure hardwrae detection to SKIP NVidia detection and limit it to QuickSync/VAAPI?