this post was submitted on 02 Oct 2023
2195 points (98.0% liked)
linuxmemes
21223 readers
96 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo in Windows.
- No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
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