Valiran Posted February 11 Share Posted February 11 Hello! On an i7-1260p, is that normal that Plex uses /dev/dri/card0 for hw transcode? Shouldn't use renderD128 instead? Quote Link to comment
bigrizz Posted February 19 Share Posted February 19 @lotetreemedia just another vote of thanks for your guide. I wish all guides were this helpful. I quickly managed to get hw transcoding going on my new server after pulling my hair out following other information in my searches. Quote Link to comment
craigr Posted February 19 Share Posted February 19 This has now gotten a lot easier. Guide below works for Intel, AMD, and Nvidia: Quote Link to comment
francispb Posted February 19 Share Posted February 19 On 11/8/2022 at 10:59 AM, Unpack5920 said: Hi, the blacklist is not a good idea. If i915 is in use, you should ensure that Plex is stopped before you make the changes. Try these lines in the console: rmmod i915 echo "options i915 enable_fbc=1 enable_guc=3" > /etc/modprobe.d/i915.conf modprobe i915 cat /etc/modprobe.d/i915.conf should show you the new settings for the driver which will be loaded with "mod probe i915" Looks like HW-Acceleration works fine for you. The settings in the "go" files should ensure, that the setting will be automatically done after reboot. Which kind of error-message do you get? Thank you very much, I was trying to make the plex transcoding work for days and I couldn't, now it worked. Quote Link to comment
sage2050 Posted February 23 Share Posted February 23 thanks for the guide, worked without issue Quote Link to comment
yamraid Posted February 27 Share Posted February 27 (edited) I stumbled upon this thread as I'm having issues using HW transcoding when HDR tonemapping is enabled in Plex (using the hotio container). I have an Intel i3-10100 CPU with quicksync, and am running Unraid v6.11.5. HW transcoding works flawlessly in all other circumstances. Are there any recurring issues with HW transcoding for HDR tonemapping that might cause this? Or is it more likely to be my config? I have /dev/dri/ mapped as a device in the container itself, then: modprobe i915 chmod -R 777 /dev/dri ..added to /boot/config/go Quick edit to mention that I removed the above lines from my /boot/config/go file as I understand these are no longer needed. Hasn't fixed my issue though unfortunately. Edited February 27 by yamraid Quote Link to comment
decibelio99 Posted March 4 Share Posted March 4 (edited) Thanks a lot. Could I use this trick with Tvheadend? Edited March 5 by decibelio99 a question Quote Link to comment
KoPVM Posted April 13 Share Posted April 13 Hi, Thanks to this guide i have managed to get GPU transcoding working on my intel iGPU while also having an Nvidia 2070 installed using the HardwareDevicePath="/dev/dri/renderD129" in the preferences file. The problem I am having is after rebooting unraid it seems like the number of the graphics cards sometimes switches. ie the iGPU is now renderD128 instead of renderD129. Is there anything I can do to stop this happening? Thanks Quote Link to comment
KoPVM Posted April 19 Share Posted April 19 The only solution I have found to the above problem is to bind the 2070 to vfio at boot. I have then created a small ubuntu vm which can be enabled to put the graphics card into low power states when it isn't being used on my windows vm. Might not be the most elegant solution but it appears to be working. Quote Link to comment
skrumzy Posted May 30 Share Posted May 30 I will literally paypal anyone 20 to get hw transcoding on my N5105 Jasper Lake box using the LinuxServer container to work. I've lost count of how many times I've tried between running docker on bare metal, my asustor through ADM, and now my asustor running unRAID. Short details: /dev/dri is being passed and shows in the container wide open /dev/dri permissions seem correct querying user abc and validating group membership against /dev/dri Log files show attempts to use hw but no device is available Running the latest unRAID What the hell else is there..... However, I can spin up a VM, pass the gpu through, and have hw transcoding done in less then 5. I am trying sooooooo hard to abandon this route as its not efficient at all on my current resources. If anyone has the time to do screen sharing, could be a quick easy 20 bucks and saving me from compulsively buying 1300 in equipment, setting my asustor on my porch, and punting it as far as I can. Then going inside to grab a bat to finish it off in grand 'Office Space' style while gangsters paradise plays on the portable speaker in the background..... Sanity has left me... BTW, brand new user, currently in trial mode to see if I really want to convert over. Hi. 1 Quote Link to comment
skrumzy Posted Tuesday at 12:17 PM Share Posted Tuesday at 12:17 PM (edited) 11 hours ago, skrumzy said: I will literally paypal anyone 20 to get hw transcoding on my N5105 Jasper Lake box using the LinuxServer container to work. I've lost count of how many times I've tried between running docker on bare metal, my asustor through ADM, and now my asustor running unRAID. Short details: /dev/dri is being passed and shows in the container wide open /dev/dri permissions seem correct querying user abc and validating group membership against /dev/dri Log files show attempts to use hw but no device is available Running the latest unRAID What the hell else is there..... However, I can spin up a VM, pass the gpu through, and have hw transcoding done in less then 5. I am trying sooooooo hard to abandon this route as its not efficient at all on my current resources. If anyone has the time to do screen sharing, could be a quick easy 20 bucks and saving me from compulsively buying 1300 in equipment, setting my asustor on my porch, and punting it as far as I can. Then going inside to grab a bat to finish it off in grand 'Office Space' style while gangsters paradise plays on the portable speaker in the background..... Sanity has left me... BTW, brand new user, currently in trial mode to see if I really want to convert over. Hi. #Asustor #N5105 #Jasper Fixed it.........finally. For anyone else struggling, my cure, was to update the i915.conf file on the unRAID stick by removing the force_probe=4c8a option and replacing it with enable_guc=2. I searched a little bit(not much) on what force_probe=4c8a does and couldn't find anything. Updating the conf and executing modprobe in the OS did not reload the module and work for me. I had to update the i915.conf on the USB to have the settings on boot otherwise unRAID just overwrites the file. YMMV but use the graphic to determine which GuC and HuC level you need... Edited Tuesday at 12:18 PM by skrumzy 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.