• highball@lemmy.world
    link
    fedilink
    English
    arrow-up
    17
    ·
    3 days ago

    That’s what the tty is for, or at worst a bootable thumbdrive, CD, or Floppy. If I can’t switch to a tty, I boot a bootable drive, mount my harddrive, and chroot my install. No second machine required. It’s rare that I fuck something up though. Rest assured it was some bullshit I was trying, zero to do with Linux itself. But I do remember Windows would just bork itself randomly for no reason at all. I’m sure Microsoft has all that resolved now, but man back in the day it was painfully often.

      • Luma@feddit.org
        link
        fedilink
        arrow-up
        4
        ·
        2 days ago

        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.

        • Focal@pawb.social
          link
          fedilink
          arrow-up
          1
          ·
          2 days ago

          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.

          • Luma@feddit.org
            link
            fedilink
            arrow-up
            2
            ·
            2 days ago

            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.

            • Focal@pawb.social
              link
              fedilink
              arrow-up
              2
              ·
              2 days ago

              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

              • Luma@feddit.org
                link
                fedilink
                arrow-up
                2
                ·
                edit-2
                2 days ago

                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:

                nvidia_drm.fbdev=0

                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!

                • Focal@pawb.social
                  link
                  fedilink
                  arrow-up
                  1
                  ·
                  1 day ago

                  **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 )

            • Focal@pawb.social
              link
              fedilink
              arrow-up
              1
              ·
              2 days ago

              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

      • highball@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 days ago

        Looks like /u/Luma got you sorted. Awesome feature right? It’s been there for a long as I can remember. This is the best part about Linux. People who use Linux created features that helped them solve problems or made their daily work easier. And you can do the same if you are feeling motivated one day.

        • Focal@pawb.social
          link
          fedilink
          arrow-up
          2
          ·
          1 day ago

          I am a teacher by trade, so I absolutely love helping others. I’ll absolutely pass it forward! This is also how you build a healthy community, I think :D