![]() it's not the proper dri files)?Įdit: Uploaded Diagnostics diagnostics-20230621-1250. ![]() NEW: (Web) Updated to 4.108. Everything worked w/ the 12100 so what gives now? Is it possible the card0/renderD128 is from the 12100 and not the 13500 (i.e. is now available to Plex Pass users in the Beta update channel. If I go to the site and look at the latest version for. and checking for updates says Im running the latest (I had the LATEST tag set in the template). It’s a relatively light update, including a single change and a few fixes but we’d recommend installing the latest release of PMS, as well as any other NAS package, to ensure you’re running with as few security vulnerabilities as possible. The version listed in Plex settings is 1. Its also happening with the Plex webapp in a browser. tried transcoding w/ Jellyfin, which shows GPU activity in the unraid web GUI (unlike Plex), but also stresses my CPU to 60%+ so I don't think that's fully working either. This is happening on a 2019 Shield Pro, an Apple TV 4K and a Firestick 4K. verified card0 and renderD128 exist in /dev/dri tried adding HardwareDevicePath="/dev/dri/renderD128" to Plex settings added/removed the unraid 6.12 i915 blacklist settings (re)installed and verified the iGPU plugin and the /dev/dri extra parameter switching containers (Hotio -> LSIO -> Official) ![]() Previously I had a 12100 and Plex transcoding was working great, but I recently upgraded to a 13500 and unraid 6.12.1 (not sure if the 13500 iGPU was working before the unraid update) and I cannot get the iGPU to work. ![]() I cannot seem to get my iGPU to work w/ Plex. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |