Server Version#: Version 1.24.2.4973
Player Version#: Version 1.33.0.2444-a220eae4
I’m having a problem with Plex Media Server running on my Small Green Computer (SGC) SonicTransporter i9-9900 3.3Ghz which is running a proprietary version of Fedora (5.6.13-100.sgc.fc30.x86_64) 30 (screenshot attached).
This is similar to the problem identified in this post:
No evidence of HW Transcoding and numerous buffering issues at the players.
Despite numerous help desk requests to SGC, they don’t seem to understand why Quick Sync isn’t working on their server. I suspect it a software issue with their OS.
Yes, PMS is an app that is available when purchasing the SonicTransporter. It’s primary market is as a ROON Server - an excellent one at that. PLEX (PMS) is an app that is available within the OS.
This is a customized version of Fedora 30 on a closed implementation solution.
There is no customer access to the OS from what I’m able to read so far.
All I can give you is a screenshot of the SonicOrbiter OS (SGC’s custom Fedora OS) which shows
the 3 apps that I have installed, amongst the Available Apps that SGC authorizes to work with their streaming appliance.
Plex Media Server is updated automatically on a regular basis.
Given the closed nature of the implementation, I am going to be of very little, possibly no assistance without additional information from their product team.
Please stand by Chuck as @agillis1970 from SGC needs to participate. This appliance should have the ability to run multiple Plex sessions with HW Transcoding.
That’s why I purchased this system as it could act as my music and movie server. Files reside on a NAS.
Quick Sync is evidently not enabled as it’s impossible for me to show HW Transcoding on any Plex Player.
I’ve checked and re-checked my Plex Settings. Tried toggling several settings off/on to see if I can get this to work but nothing does.
I’m left with the conclusion that something in the OS is preventing QSV from working. I have even tried an HDMI Dummy Plug – which didn’t do anything – just to eliminate the obvious.
I apologize for my naive questions but couldn’t they add this directory to my unit? Not sure if I understand the significance of this missing directory, Chuck.
The node entry is something the Linux kernel creates as it starts.
Linux kernel init probes the hardware.
In a QuickSync-capable Intel CPU (-2xxx or higher, where -7xxx series or higher will give you HDR/UHD capability), the kernel sees the Intel i915 chip in the CPU and then, if the drivers are present in the kernel, looks for the i965 interface chip.
if it has the appropriate i915 and i965 drivers (Fedora 26 and higher do by default), a file node (filesystem entry) is created so it can be accessed as a device. That’s why it’s placed in /dev.
Subdirectory dri is used for direct rendering.
The name assigned matches where the QSV chip sits on the hardware bus.
You end up with /dev/dri/renderD128 ( rendering device 128)
This is what Plex looks for when it wants to do hardware transcoding.
Without it, it has to do everything in software – which can be painfully slow.
To “fix” this requires them to provide all the kernel drivers needed (not much).
The question, IMHO, is whether they want to be an audio & video streamer or just the audiophile streamer ?
Linux kernel init probes the hardware. (yes that happens)
In a QuickSync-capable Intel CPU (-2xxx or higher, where -7xxx series or higher will give you HDR/UHD capability), the kernel sees the Intel i915 chip in the CPU and then, if the drivers are present in the kernel, looks for the i965 interface chip. (yes we have an intel i9-9900)
if it has the appropriate i915 and i965 drivers (Fedora 26 and higher do by default), a file node (filesystem entry) is created so it can be accessed as a device. That’s why it’s placed in /dev.
Yes, The driver does seem to be available in Fedora 30
Subdirectory dri is used for direct rendering . This does not happen. the dri directory does no get created
If the full default kernel is supplied, the node will be created provided QSV is not disabled in the BIOS / hardware (which is possible on certain motherboards)