Chris wrote:
I’m sorry—the earlier AI answer was too certain about WSL being unsupported and suggested moving to Linux without verifying that was necessary. Your check establishes that WSL exposes /dev/dxg but no /dev/dri; it does not establish whether SparkBox has another supported GPU path on WSL, and I can’t verify one here. Since turning hardware acceleration off restored playback on your Fire TV, leave it off for now rather than rebuilding or changing GPU settings. What SparkBox version is shown in your dashboard? I’ve corrected what I know so we don’t repeat that unverified advice.
Chris wrote:
A correction to my earlier note, and I'm sorry for muddying it: the first answer you got was right. Jellyfin's own hardware-acceleration guide says Intel Quick Sync (QSV) and AMD's encoder (AMF) are not available when Jellyfin runs in Docker on WSL2. WSL2 also gives Linux only /dev/dxg, not the /dev/dri SparkBox needs to hand a graphics chip to Jellyfin. So on this Windows setup there is no supported way to use the i5's graphics (or the RX 6700) for Jellyfin; software transcoding is the right setting. That also explains the Fire TV. With hardware acceleration switched on and no GPU reachable, every video the Fire TV couldn't play as it is failed to convert (anime often carries styled subtitles, a common reason a TV needs that), while the videos it plays directly kept working. Turning it off was the real fix, not a workaround. One check: in Jellyfin's Dashboard, under Playback (Transcoding), Hardware acceleration should read None. If you ever want GPU transcoding, it needs SparkBox on a Linux install where the graphics show up as /dev/dri. What the assistant knows has been corrected, and from SparkBox 1.6.805 the checkup (sudo sparkbox doctor) warns when Jellyfin is set to a GPU it doesn't have, so the next person hears this straight away.