Jump to content

Recommended Posts

Posted
On 6/6/2026 at 7:17 AM, brushie said:

Not sure if I should make this it's own thread but I'll just start here.

I updated TrueNAS Scale from Electric Eel (24.10) to Fangtooth (25.04) and currently Emby cannot detect my A770 for hardware acceleration. On Electric Eel, it was working just fine. Checking the hardware detection logs, I get an error for “Failed to open the drm device (null)”. I'm pointing my finger more at TrueNAS being the culprit, but checking if anyone here might have a workaround or solution. There's currently a workaround using shell commands for nvidia cards but doesn't really help much for Intel cards. 

hardware_detection-63916292682.txt 31.2 kB · 0 downloads

HI, are you still having an issue with this?

  • 1 month later...
audiom3
Posted

Hi @Lukeis there any update on pushing a newer update through Scale?  We're still on 4.9.5.0.  I have had a fairly serious issue now twice where ffmpeg fails to terminate and runs all night while I sleep.  The common factors are: DV P7.6, PGS subtitles and a 3rd Gen FireTV Cube.  I have too many rips to convert all subs to subrips. 

I have woken twice to the nice surprise of seeing some of my Intel 13th Gen Cores cooking at near 90C and CPU at 65%.  I have added a Cron job to kill ffmpeg if it's running for 2+ hours but it would sure be nice to have this issue patched.  Thanks for all of your hard work!

BrettDioson
Posted (edited)
10 hours ago, audiom3 said:

Hi @Lukeis there any update on pushing a newer update through Scale?  We're still on 4.9.5.0.  I have had a fairly serious issue now twice where ffmpeg fails to terminate and runs all night while I sleep.  The common factors are: DV P7.6, PGS subtitles and a 3rd Gen FireTV Cube.  I have too many rips to convert all subs to subrips. 

I have woken twice to the nice surprise of seeing some of my Intel 13th Gen Cores cooking at near 90C and CPU at 65%.  I have added a Cron job to kill ffmpeg if it's running for 2+ hours but it would sure be nice to have this issue patched.  Thanks for all of your hard work!

@Lukedoesn't control the TrueNAS package repository for Emby.  That's Stavros-K in the TrueNAS community IIRC.

I did however notice the latest Emby released version doesn’t have the same numbering scheme as the previous releases that ended in .0.  This “latest” is 4.10.0.40.

what was the outcome on versioning for the truenas package team to know a stable version?  Was the “stable” tag ever implemented?

 

Edited by BrettDioson
Posted
5 hours ago, BrettDioson said:

@Lukedoesn't control the TrueNAS package repository for Emby.  That's Stavros-K in the TrueNAS community IIRC.

I did however notice the latest Emby released version doesn’t have the same numbering scheme as the previous releases that ended in .0.  This “latest” is 4.10.0.40.

what was the outcome on versioning for the truenas package team to know a stable version?  Was the “stable” tag ever implemented?

 

Right it's supposed to end in .0. I think that means you may have to wait until a 4.10.1.0 update is out.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...