Launch your installation media again, get your internet connection set up, mount your current install, chroot into it, finish installing the things you forgot, reboot, profit.
this post was submitted on 27 Jul 2023
36 points (97.4% liked)
Arch Linux
7781 readers
9 users here now
The beloved lightweight distro
founded 4 years ago
MODERATORS
This. Always have a spare arch usb laying around for times like these.
How don't you have any tty?
Maybe your function keys are set to be multimedia at the bios.
Try ctrl+alt+fn+F{Key}
Another alternative is to boot from usb, chroot and install a terminal
Thanks, checked that already. Yeah, booting from USB is a good solution. But now, I'm determined to fix this from within ;)
That's basically the one universal solution... And after chrooting, you are "inside" your system cough
Then chroot from usb and install a terminal
Absolutely try some function key combos - I did something similar this week by setting my keyboard to “ma” and not “mao” this week and got an Arabic script instead of te reo Māori and all of a sudden none of my keybinds worked, but hitting fn+alt+f2 got me to a tty and saved me.
Alt-F2 or similar maybe gets you a run dialog or alternatively pass the “init=/bin/bash” option to the kernel.
Alt-F2 launches a program search window.
It seems the KDE folks have hijacked all the standard key combos.
But that gave me an idea: I might be able to configure key-combos to launch bash commands from within the system setting tools...
Try ctrl alt f2. This also should work at the login screen if you have one
It's ctrl alt and t for me btw..
I see you got it fixed and other people told you about chroot, so you're all good for now. FYI, next time you install, follow the wiki. There's a package that they tell you to install during the initial setup that includes all the basic things you'll need, like terminal, a browser, etc. If you skip that then you will definitely have issues like this.
That Plasma is not letting you move to a new tty is "interesting"....bad KDE!.....no cookie for you!
Definitely an issue with their setup, not with Plasma in general. I can move to a new tty without any issues.
Not super familiar with Plasma but, I'd suspect that has to be the case. Weird they can't get a new terminal open. At least it's Arch though....arch-chroot to the rescue ;)
You should still have vi installed by default. I would go the arch-chroot route, but if you can use alt+F2 to search programs, perhaps you can find vi. If yes, ! executes terminal commands. So either you can leave yourself a line in .xprofile to halt you before x loads sddm (or some other tricky thing like that) OR you could do :!pacman -S
I'm a suckless-st guy myself, but you'll need a browser to get to it one way or another.
It's been a long time since I ran arch, forgot how good arch-chroot was for unfucking things I fucked.
Can I just say we're proud of you?
You can always boot back into your live environment (install USB) and chroot into your install to grab missing packages.
Launch Dolphin if you have it installed and press F4.
Edit grub at boot time if you are using it, wrote emergency at the end of the line.
If you have installed X, then check to see if you can select another session in sddm to launch X own window.
There are other ways to do it as well, f.eks. with kdesu and alt + f2
Do you have GRUB or another bootloader that lets you directly set kernel parameters on boot? You could try replacing "quiet splash" or whatever you have there with "text"
Hold on, I think that parameter is ancient. I think this is a more modern way to do it: https://www.linuxuprising.com/2020/01/how-to-boot-to-console-text-mode-in.html?m=1
view more: next ›