Everything has been updated. The OS can see the graphics card and during the most recent upgrade for the Plex server the output from terminal said the GPU was enabled. Plex was installed directly with no docker container. Yet when I try to go into the setting and choose what I want to use for encoding the GPU is not in the drop down menu. I purchased a Plex Pass and linked my account to this server. Ubuntu has the most recent Nvidia drivers for my card. I have been reading for weeks and can’t figure this out. Any suggestions on how to fix this. Attached is the most recent log file.
I put your log through Gemini, and it gave me some pointers.
How did you install the server? deb-file or the Ubuntu App Center (snap)? Snaps are sandboxed and might be blocked from seeing your hardware. Might need some connecting commands.
please forgive me I’m a noob to Linux and still having a lot to learn. The OS i’m running is pure command line driven no GUI. I followed a guide from you tube that helped me get it up and running. I believe you would classify my install a a deb file. Docker was not used and I can see and access the server with the web app and the plex apps on my fire sticks.
I have my server set to reboot once a day and after rebooting on the trans-coding screen my gpu is no longer visible again. I have to manual give it permission to use it again. How do I fix this by giving the permissions permanently?
I’m migrating from windows and always had my systems set to reboot in the middle of the night so I guess you could say just the normal thing I have always done with my servers.
the two commands I have been using are :
sudo usermod -aG video plex
sudo usermod -aG render plex
after restarting Plex I can now see and use the GPU for hardware transcoding. However once the computer reboots either by me doing it manually, a power outage, or a system commanded reboot Plex can no longer see nor use the GPU until those two commands are used. How do I get it to stay permanently? In addition maybe I’m using the phrase “give permission” for plex to have access to the GPU but not sure that the proper technical term that I should be used
Very good question.
The response, “use cron” is like the equivelent of telling someone on windows to “just run it as administrator after every reboot”…
Why does adding the user “plex” to the groups “video” & “render” not stay set?
THAT is what you should focus on.
This is basic unix stuff, has been for the past +30 years.
Ok??? Why should he have to add a user to a group after a reboot?!?
Sounds like a completely broken installation to me…
And again, why reboot a linux server every single day?!?
Does he also have to add himself to the sudo group after every reboot?
What about all other groups?
This could for example easily be a corrupted filesystem, so it gets mounted as readonly hence all changed settings only stays in memory and never gets written to disk…
It is NOT normal behavior and should raise massive red flags for op.
You add users to groups ONCE, then that is set FOREVER until removed MANUALLY.
Do you even know what those commands do?
Why are you running TWO commands?!?
Why outdated cron (ran as sudo) instead of a systemd service that is designed to run as root?
It makes my blood boil when seeing bs answers repeated from an AI…
Yes, you got op to falsely think this is a “solution”, it is absolutely not, it’s a disfavor to op and what you provide hurt rather than help.
I repeat: this is the equivalent of telling someone on windows to “just run it as administrator”, or giving a band aid to someone with a broken leg…
So you open up your device for anything to run (666 = full read/write access for ANYTHING), like a crypto miner malware f.ex… Sounds like GREAT advice…
No it’s not “what’s matters”. What matters is if the system is inherently broken, THAT has to be fixed. A band-aid is NOT A SOLUTION.
Correct, so stop giving OP bad advice.
Unless you have anything useful to op, stay silent.
OP should ask on ubuntu forums why adding a user to a group does not stay after a reboot.
Seems pretty self-explanatory to me, get off your high horse.
Telling a guy to spend three days learning GID mapping just to watch a movie is peak gatekeeping.
if your implying that my instillation is broken how do I go about confirming that? I’m assuming I would have to go a full reinstall?
If my install has become corrupt I fear I may be the issue. I’m new to Linux and have a lot to learn. And one issue I have am having with this build is getting more control over my GPU. I do not like the “stock” fan settings and have been trying alot of different guides on different forms and websites to no success.
Don’t be too bothered about the broken talk. @body_bedna is just jumping to the worst-case scenario. Run this to check if your disk is actually failing:
mount | grep "on / "
If it says rw in there, your hardware is fine and Ubuntu is just being stupid. Resets are likely fromcloud-init or some script overwriting your changes on boot.
