You are not logged in.
Hello all,
I've been an arch user for a few months now and have ran into an issue on boot. Two nights ago I did a
sudo pacman -Syu and woke up unable to boot into my machine.
On boot I'm met with tons fat/wide text that I've never experienced before. An example of this is:
[ 2.6991321] usb 1-10.1: New USB device found... It slowly procedes until it hangs up and I notice the error (subject of post) near the end of the log.
I've entered into a live environment via USB, mounted / and /boot, chrooted in, and found the output of
uname -a and
pacman -Q linux to not be the same.
I've noticed this is hardly a novel issue, but, as per a similar posts, I've tried reinstalling linux in the live environment to no avail.
Any help would be much appreciated. My bootloader is grub. Thanks!
Last edited by muddytimbs (2022-06-16 19:17:17)
Offline
In a live USB environment, `uname -a` and `pacman -Q linux` can't be the same. one is the kernel from the USB booted, the other is the kernel package installed on the hard drive.
paste the whole journalctl from the last boot that's on the hard drive. (see arguments --file and --boot 0)
Offline
The 'file' command can be used on /boot/vmlinuz* to determine the version installed in the /boot partition. Compare that to /usr/lib/modules/ — they need to match. If they don't then re-install the kernel with /boot mounted correctly and review /etc/fstab to make sure the /boot entry is correct.
Jin, Jîyan, Azadî
Offline
@head_on_a_stick: The version of /boot/vmlinuz-linux and /lib/modules is the same. My boot entry of fstab is:
# /dev/nvme1n1p1
UUID=CFA6-EB13 /boot vfat 0 2 @damjan: makes sense. I had a hunch that may have been the case. Here is a pastebin with the most recent boot off of the hard drive: https://pastebin.com/TGyUbAGN
Offline
Jun 16 11:50:28 bigrig kernel: traps: Missing ENDBR: _nv011433rm+0x0/0x10 [nvidia]Offline
@loqs, that was the issue. ibt=off did the trick. Thanks.
Offline