I’m upgrading my builds and I decided to get a new monitor so I splurged on the Samsung G9 49" Curved OLED.
My personal and work ARM MBP’s require significant tweaking to get the G9 working with a good DPI and font rendering.
I finally booted up my desktop tonight and it just works. I literally didn’t have to touch anything.
It’s not Silverblue specific, it’s the Linux Kernel.
Can verify, use Silverblue and it was plug and play for me back when I first used it around January.
Updated the kernel to 6.13 around February/March and broke Bluetooth for me. I have no idea how to fix it besides rolling back to a prev update.
I use Silverblue and MacOS daily, I enjoy the former so much more.
Unfortunately my relatively new Lenovo laptop has a small but also major driver bug that hasn’t been fixed in all the time I’ve had it. Bad to the point I got the Mac to have actual working hardware. But I do not enjoy MacOS in the slightest. At best I can say it harasses you less than Windows and respects the user a few degrees more than Windows.
What’s the driver bug? Chances are I can’t help unless it’s one very specific one, but I figured I’d ask.
The touchpad would be very unresponsive for several minutes after waking from sleep. It would still work, but had a crazy latency. Happened in both Windows and Linux.
I believe I could’ve hacked around it with this command.
If it works, you can add the rmmod and modprobe to your login. Either to your Display Manager (login screen) or, since Silverblue uses Systemd and that command needs to be run as root, create a before-login service.
Laptops specifically have been such an Achilles heel for Linux due to driver issues and battery issues. I honestly would just rather stick with OSX and containerize. The thing that might test that is X86 support lapsing at least for some of my MBPs.
