2024-07-04, 04:40 AM
As always, you are correct. I missed that.
2024-07-04, 04:40 AM
As always, you are correct. I missed that.
2024-07-04, 01:57 PM
(This post was last modified: 2024-07-04, 02:06 PM by container_ship. Edited 1 time in total.)
2024-07-04, 05:59 PM
Mimic my settings and see if that changes your transcode performance.
2024-07-04, 06:06 PM
(This post was last modified: 2024-07-04, 06:07 PM by container_ship.)
Well a new issue came up and I don't know if this is the right place to ask.
Please tell me and I will create a new post. After running the Jellyfin Docker for a while, it crashed (no idea why) and wouldn't start again. The logs for the restart said that /dev/dri/renderD128 is missing. Well checking that and somehow the ARC GPU is now unclaimed in lshw -C display with no usable driver. This is the second time this happened. First I thought adding dg2_huc_gsc.bin was the problem but I guess not. A rollback to a snapshot before installing docker and jellyfin restores the gpu and it's drivers. (2024-07-04, 05:59 PM)TheDreadPirate Wrote: Mimic my settings and see if that changes your transcode performance. I did and it improved to about 70fps-80fps but then the other issue came up.
2024-07-04, 06:43 PM
My main Jellyfin is directly installed on bare metal Ubuntu. But my test instances are running on docker and I've never experienced what you described. Are you passing in renderD128 explicitly or are you just passing in /dev/dri entirely? It SHOULDN'T matter but sometimes makes a difference for some users.
2024-07-04, 06:50 PM
(This post was last modified: 2024-07-04, 06:51 PM by container_ship.)
I'm passing in renderD128 explicitly.
This is my compose file: Code: version: '3'
2024-07-04, 07:27 PM
Try just passing in /dev/dri entirely. The Intel driver will automatically select the first available Intel device if you have more than one, but you only have one.
2024-07-05, 04:09 PM
|
|
|