this post was submitted on 27 May 2025
1394 points (98.9% liked)
linuxmemes
25136 readers
1270 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 users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- 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.
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
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
TTY is short for Teletypewriter. Basically it is the terminal that you see if you don't boot into a graphical environment. You can access the TTY from anywhere by pressing CTRL+ALT+F1-7 (will throw you into tty 1,2,...7, depending on which F key you pressed) You can switch between TTYs either by pressing CTRL+ALT+,F? again, where the F-key determins on which TTY you will land, or by using CTRL+ALT+arrow keys to go back and forth one at a time.
The TTY is a terminal so you can do stuff like run commands here. If your graphical environment is broken, you will probably end up here and can often fix the problem.
Oooh! I see, thank you!
Yesterday, I tried booting into Wayland on Linux Mint, and I got NOTHING.
I rebooted and got nothing again. I tried the Ctrl+alt+F(x) key combo, but that didn't work either. From your explanation, it sounds like I should've been able to at least get a terminal for that, but it didn't seem to work. Could that be because graphically, it WAS displaying something after all?
Ended up unplugging the screens from the GPU and tried plugging it straight into the mobo instead, and it ended up working after all.
Hmm... What does nothing mean exactly? Did your monitor turn on during boot? If so, did it turn off again at some point or did it display a completely black image?
Since the mobo connection worked (which usually uses the integrated GPU chip on your CPU as far as I know), maybe it was an issue with your gpu? Or the connector or something?
I once had a broken setup where got stuck on a black screen, unable to switch to a tty. If I started spamming CTRL+ALT+Fsomething right after Grub was done, I managed to escape the black screen before it appeared, maybe you could try spamming the key combo early on and see if that opens a tty for you. If that is the case then you can be pretty certain that the problem is related to your desktop environment.
Alright, I've managed to open the TTY when trying to boot into Mint(wayland). You were right! It's probably an issue with my nvidia drivers. I'll see what I can do. Thanks
Nice! Since your installation is showing similar symptoms to my installation when I updated my nvidia drivers a while ago, I'm just gonna tell you how I fixed my issue on my computer, and maybe it's gonna work for you too. If you want, you can try this:
Boot your PC. After your Motherboard is done showing its logo or whatever it shows, you should see grub. If you press 'e' before grub proceeds to boot into linux, you will be thrown into a simple editor that will let you temporarily change what grub boots. There is a line with the kernel image and arguments, it probably starts with 'linux'. Go to the end of the line (line might span multiple rows, so end of line might be on the next row) and add this:
Then press F10 to boot. That's it.
This fixed the issue for me. If it will fix the issue for you as well, you can consider adding it to your kernel parameters permanently or making sure the nvidia kernel module gets the parameter by other means.
Hope this helps!
**I appreciate the help immensely. ** First thing I needed to do was figure out how to get grub to show, and to do that, I changed a file in /etc/default/grub to have the menu style be "menu" instead of "hidden".
Second I tried adding the nvidia_drm.fbdev=0, but it would boot directly into the default version of Mint (x11). I then had to disable auto-login in the lightdm.conf found in /etc/lightdm/
After that, I finally booted into Wayland again after adding the temporary parameters and... I get a black screen again, sadly. At least the TTY works so I can get out, no problem.
I did a bunch more tinkering that I found online, but after a lot of trying and failing and trying and failing, I went back to x11, only to realize that the driver manager was well and truly messed up. Could not get it to start at all. Ended up feeling pretty happy I took a snapshot of the system before I started all this, cause I could just rollback everything and now it works like before. (Still no wayland though, but whatever :P )
Interesting. I'll see if I can figure something out.
Answering your question, it booted to a black screen. The screen was "on", it wasn't complaining about not recognising a signal or anything, so SOMETHING must've transmitted. I'll try spamming some keys to see if I get a reaction. Thanks for the tip