this post was submitted on 02 Oct 2023
2223 points (98.1% liked)
linuxmemes
20880 readers
2 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If only Linux wouldn't Bork my whole install when I try to switch to 144hz on my monitor.
You're not supposed to run "rm -rf /" to change refresh rate
That’s a weird one. I’ve been running a 165hz primary monitor and a 144hz secondary for a while on AMD, Nvidia, and Intel GPUs. I’ve never had any trouble with them.
Were you using Wayland or X11?
Honestly don't remember which I was running. Was a new install of testing Endevour OS with an Nvidia card. Changed the refresh rate through the display settings to 144 and it went black and never came back. Fixed it back to 60 through cli boot eventually but it never liked changing it off that.
I can verify I’ve had this exact problem. Never found a solution. My Linux box has been changed to Manjaro so it’ll work now
Are you using some weird video setup? I’ve had some issues with DisplayLink but never anything worse than needing to reboot before it will work again.
Borking an entire install by pressing buttons on a monotor is pretty difficult. What exactly were you doing? Did you ask your OS' community for support?
All I did was on first install go to display settings and change to 144hz in the OS and screen then goes black and never came back. Force a shutdown and boots back to a black screen after login.
I was eventually able to change things back to 60hz and working through booting to cli but 144 never wanted to work (am admittedly using Nvidia card).
So not completely borked but not ideal at all.
Ah yeah nvidia can be painful, especially if you want wayland. But this seems to be a simple modesetting issue, I'm sure there are some known workarounds. You can also report driver bugs directly to nvidia, but I don't know if that will do much.
Yeah, sounds like a PEBKAC problem to me. 😁
Well even if the user doesn't really know what they're doing, things shouldn't easily break, that's just bad.
I'm not convinced this is a valid statement:
If he says his install is borked I believe him. If he says it's "just" because he tried to switch to 144hz on his monitor, eh...
Edit: Also sounds like nvidia binary blob driver. Odd to me that he didn't get the "do you want to keep these settings" prompt, and that it didn't revert when he didn't click yes though.
Setting any of my monitors to 4k or 144hz just resulted in a completely black screen that persisted through reboots. Only solution I found was to plug into a completely separate, lower resolution monitor.
No clue what caused it, but it’s not isolated to just op
Out of curiosity, nvidia blob driver also? (I, too, run the blob driver, but I'm just curious if it's a common denominator)
I think so. It’s been a while since I set it up.
Since I can’t remember setting up the proprietary ones, I’d assume it’s the blob