this post was submitted on 31 Oct 2025
61 points (93.0% liked)

Linux

13795 readers
162 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 2 years ago
MODERATORS
MigratingtoLemmy@lemmy.world
61
Ok, how do we actually fix the linux bluetooth issues? (sh.itjust.works)
submitted 3 days ago* (last edited 3 days ago) by bridgeenjoyer@sh.itjust.works to c/linux@lemmy.world
30 comments fedilink hide all child comments
 

I have read about so many issues regarding Bluetooth and Linux its ridiculous. Usually its random disconnecting, not auto reconnecting, not disconnecting properly, basically every issue possible. And ive had them too. I would really love it if i could just have my ps4 controller hook up right when I turn it on for example. Or have my shared speaker system actually disconnect when I turn off blnluetooth (it doesnt).

I've mostly only used mint with Bluetooth. Some popos but it had the same issues ofc. Only really used desktops, but also have issues on an atari vcs with mint and Bluetooth, exact same issues my desktop has.

Anyone know some real fixes? This is one of those things that makes it very hard to get people to switch when windows handles bluetooth devices perfectly (in my experience) and linux has just sucked so bad on that front.

you are viewing a single comment's thread
view the rest of the comments
[–] Lodespawn@aussie.zone 4 points 3 days ago* (last edited 3 days ago) (1 children)

Have you added:

options nvidia NVreg_PreserveVideoMemoryAllocations=1

options nvidia NVregTemporaryFilePath=/var/tmp

to /etc/modprobe.d/nvidia-graphics-drivers-kms.conf?

This was the fix found here that worked for me, the file in the fix didn't exist but this one was the only nvidia related conf file in modprobe.d and the fix worked and has persisted despite multiple driver updates.

I'm running kubuntu 25.04.

[–] paper_moon@lemmy.world 1 points 2 days ago* (last edited 2 days ago) (1 children)

Thanks for trying! But that didn't seem to work. My file had both of those lines but on the 2nd line had /var instead of /var/tmp. I added the /tmp and rebooting, but still doesn't sleep. I guess I'm on the nvidia 580 drivers now, I think what had worked for the 470 drivers was the following bellow. I think doing a kernel upgrade messed me up, but I got rid of the previous kernel so not sure which I have to go back to to get it working again.

I actually did the opposite of this guide to see if that would work and it didn't. Without the nvidia power management services , the device doesn't sleep it comes right back on after a second of back screen, but with the services the device has a black screen, but is still on, not asleep and I can't wake it so I have to hard reboot.

"Good news for affected users! I found a fix!

A LITTLE BACKGROUND You may already know that NVIDIA drivers on Linux rely on either of two different methods for power management ( as described here 68 ), which include:

Kernel Driver Callback: Works out of the box with no configuration required, but lacks advanced power management features and preserves only a portion of the video memory.

systemd (/proc/driver/nvidia/suspend): Provides advanced power management features and preserves complete video memory, but requires configuration and setup.

THE CAUSE Having mentioned the above, upon further inspection I found out the 470 driver migrated to systemd method while previous versions relied on Kernel Driver Callback. Apparently this is broken on some setups and kernels.

THE WORKAROUND Now it’s obvious we have to revert back to Kernel Driver Callback method for now that the systemd method is broken, and here’s how you can do that:

Disable NVIDIA systemd services
sudo systemctl stop nvidia-suspend.service
sudo systemctl stop nvidia-hibernate.service
sudo systemctl stop nvidia-resume.service



sudo systemctl disable nvidia-suspend.service
sudo systemctl disable nvidia-hibernate.service
sudo systemctl disable nvidia-resume.service 



Remove NVIDIA systemd script



sudo rm /lib/systemd/system-sleep/nvidia

Reboot and you should be able to suspend and resume properly with driver version 470.xx.

NOTE: Backup your configuration just in case, or downgrade the driver if this does not work on your setup. This was tested on Kubuntu 21.04 with GeForce GT 710."

[–] Lodespawn@aussie.zone 1 points 2 days ago (1 children)

I gotta say, after my last post I promptly upgraded my PC to 25.10 which immediately broke my Nvidia suspend, after a bit more investigation I found restarting the services you listed above fixed the issue. The fix persisted across restarts. I'm running an RTX 3060 so along with the 25.10 it's a bit of a different setup from yours.

[–] paper_moon@lemmy.world 2 points 1 day ago

Glad that helped ya out!