einfach_orangensaftchroot is still black magic
I never understood these. Arch has always been rock solid for me and in 10 years or so I have never had to chroot to fix an issue. The most annoying issues have been related to PGP signatures or old certificates but those have been easily fixed.
What is it you people do to your arch installs that fucks them up so much?
forcing reboot when mid update cause u think the system froze
• I’m in this picture and I don’t like it
Drop to tty when in doubt
always go for the tty if u need a sense of safety
I redownload and reinstall all packages if an update is interrupted. Sometimes a pacman -Syu completes the upgrade but usually it is not enough.
wiki.archlinux.org/title/Pacman/Tips_and_tricks#R…
EavolutionThe only time is during setup once I forgot to download iwd so I had to chroot back in to install that from within the installer.
ZarosOnly time I’ve had to do it so far was due to dual booting Windows and it overriding boot thingies. Apart from that it has been running more or less flawlessly for a few years now.
X11 had some breaking updates in the past, my monolithic multi monitor config was suddenly in the wrong spot. Or packages I was supposed to delete before an upgrade according to the newspage, but I updated impulsively bam chroot times. That was years ago and made me switch, maybe it has become better?
SpaceCadetArch has always been rock solid for me and in 10 years or so I have never had to chroot to fix an issue
For me it has usually been boot related things or when I’m doing planned deep surgery on my system. I can recall a few times that I used arch-chroot through the years:
- When the grub package was updated and generated a config file that was incompatible with the earlier grub version that was installed on my EFI partition.
- There was one time a kernel that wouldn’t boot on my hardware, so went back in to install linux-lts
- There was once a bug in netctl that caused it to hang indefinitely on boot, so I had to go in to disable the service so that I could at least boot to troubleshoot it.
- After every BIOS update of my Gigabyte motherboard, I have to re-add grub to the nvram entries by running
grub-installfrom a chroot environment. On my ASUS system I don’t have to do this, don’t ask me why. - When I moved my installation to a new SSD and made a typo in
/etc/fstab - When I was switching over to a LUKS encrypted root filesystem it was handy that I could boot into the installer to do a clean copy of my root filesystem and make all the
grub,mkinitcpio,/etc/fstabchanges viaarch-chroot. It was also good to know that I could always go back in that way to make additional changes as it can be tricky to get it all right on the first try.
oshitwaddupI recently had to when sbupdate wasn’t compatible with the latest systemd
I’ve fucked up my grub install before, that’s the only time I’ve needed to use it, and it was an easy fix
Using Manjaro+Nvidia. About a 20% of kernel or driver updates leaves me with a black screen. Then I do rollback and wait for a bit more stable version ¯_(ツ)_/¯
Your mistake was using manjaro
And/or nvidia
s4if- Nvidia driver (not me, I’m poor)
- dubious/niche AUR packages
- Wrong settings on BIOS/UEFI
- Windows Update on dual-boot setup (sometimes)
I don’t know why, but my archlinux bootloader always disappear if I connet bootable disk when my computer is booting, lol…
It’s possible your uefi has a thing about default EFI boot names. I ended up changing mine to just boot because if I update the bios it clears everything and doesn’t automatically pick up any EFI except boot.
Hmm may be, I’ll try to check that. Thx…
My advice is that you make sure you use a full unblemished calf for sacrifice with gilded horns of gold.
If you don’t gild the horns and burn the fatty thigh parts in the fire then it will never boot.
What the hell are people finding on the AUR? I just need it to install like… Discord and Lutrus?
Some custom or git version of application. Once a time I need to use sddm git to fix bug with my hylrland.
I personally had my Arch install broke 2 times from standard updates about 5 years ago. Jumped ship and never installed Arch again.