Dropped Into TTY At Boot Immeduately After Changing Kernel

Oceanarium · 2021-06-05 02:17:18

Hello, I just installed arch and ran -Syu and it installed 5.12, so I changed the kernel to lts 5.10 but when I rebooted I was immediately drooped into tty. What could have caused this?

seth · 2021-06-05 06:54:04

You made some mistake.
https://bbs.archlinux.org/viewtopic.php?id=57855

…

Let's start with

installed 5.12, so I changed the kernel

What's was the motivation here? Did the "5.12" (there's certainly a release number as well) cause similar issues?
How did you "change" the kernel? Did you remove linux and install linux-lts? Was linux-lts already installed?

The typical cause for "I did an update and can't boot anymore" is that you forgot to mount the /boot partition or are botting from the root partition.
Either way, the kernel you boot is not the installed one (check "uname -a") and can't load modules from the disk, resorting to a rescue shell.

tucuxi · 2021-06-05 07:22:48

Describe your boot loader setup.

Oceanarium · 2021-06-05 08:31:49

This person had the same problem as me:
https://bbs.archlinux.org/viewtopic.php?id=266832

When I tried to boot with 5.12 it dropped me into tty and said my kernel modules failed to load. At the end of the page someone said what Seth just did above. I don't know how to do that permanently so I just figured I'd use a different kernel. Every time I've used the latest kernel when I used Manjaro before it broke my system so I've made it a habit to stay 2 versions behind lol.

Is it easy to do what you've just said to do? I'm coming straight from Manjaro so I'm a little lost lol.

seth · 2021-06-05 08:34:52

Add your /boot partition to /etc/fstab.
In doubt, post the output of "lsblk -f" and your present fstab.

Oceanarium · 2021-06-06 00:11:13

I tried to do it on my own but I can't get it with both ways.

lsblk -f

NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
|-sda1 vfat FAT32 E50C-28D2
Lsda2 ext4 1.0 e8addbef-3b92-47f3-b54e-693c411a6230 422G 3%. /

sudo nano /etc/fstab

# Boot Partition
/dev/sda1 none vfat defaults 0 1
# Root Partition
/dev/sda2 / ext4 defaults 0 2

loqs · 2021-06-06 00:22:01

/dev/sda1 none vfat defaults 0 1

First field is what you want to mount so that is valid, second field is where you want to mount it, here you have none which would work for swap which is not mounted anywhere.
In this case you want to mount the ESP to /boot. Skipping to the sixth field, did you make a mistake copying the two entries? / should use 1 and everything else should use 2 or 0.
See man 5 fstab for more details. See also Persistent_block_device_naming for the issues with using /dev/sda and alternatives.
Also please use code tags

Last edited by loqs (2021-06-06 00:25:58)

Oceanarium · 2021-06-06 00:37:50

Okay I set sda1 to /boot and the sixth field is 0 and sda2 is set to 1. It still doesn't boot o:

loqs · 2021-06-06 00:41:48

How far did the boot progress before it stopped? Was this booting with the old or new kernel installed?

Oceanarium · 2021-06-06 00:43:57

I just boot into grub from reboot, pick the LTS kernel then it says something about cleaning and then immediately drops me into tty

loqs · 2021-06-06 00:48:21

At that point can you login? If so check the output of mount to see if /boot is now mounted. It probably is not if the boot is failing.
Still from that login downgrade the kernel to the old version. Then without restarting try

mount /boot

If that works it means the kernel and modules are now synced but on the old version. Now that /boot is mounted update the kernel package.
Then try rebooting and check if the issue is fixed and all that is left is clean up.

Oceanarium · 2021-06-06 00:55:06

"/dev/sda1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro"

loqs · 2021-06-06 00:59:15

So /boot is mounted. What failed and stopped the boot? See Systemd#Investigating_failed_services.

Oceanarium · 2021-06-06 01:10:19

I ran systemctl --state=failed and it says "0 loaded units failed."

loqs · 2021-06-06 01:19:47

Were you still dropped to the rescue shell on boot?
If so check the journal for what failed.

Oceanarium · 2021-06-06 02:04:02

I'm not in rescue shell, I'm in tty. As soon as it starts I get dropped into tty and then log in, there's no error messages or anything on screen.

However when I boot into kernel 5.12 I get dropped into emergency shell and it says:

[FAILED] Failed to start Load Kernel Modules
[FAILED] Failed to mount /Boot
[DEPEND] Dependency failed for Local File System

In the journal for 5.12 there's a few lines in red:

DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR
DMAR: Your BIOS is broken; bad RMRR

And:
systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
systemd-modules-load.service: Failed with result 'exit-code'.

Also:
systemd-modules-load[194] Failed to look up module alias : 'crypto_user': Function not implemented
systemd-modules-load[194] Failed to look up module alias : 'pkcs8_key_parser': Function not implemented
Systemd-random-seed[199]: Kernel entropy pool is not initialized yet, waiting until it is.

systems[1]: boot.mount: Failed with result 'exit-code'.
systems[1]: Failed to mount /boot.
systems[1]: Dependency failed for Local File Systems

systems[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.

seth · 2021-06-06 07:51:26

systemctl is-active multi-user.target
uname -a

Adding /boot to the fstab will just mount it, but if your kernel is out of sync, that alone won't fix it.
You'll have¹ to re-install the kernel package w/ the /boot partition mounted - in doubt from a chroot

[1] Technically you don't "have" to, but it's the simplest way.

As soon as it starts I get dropped into tty and then log in

Unless you've installed/configured a graphical.target, that's normal.

What guidance did you follow to install archlinux?

Oceanarium · 2021-06-06 11:47:04

I used this guide:
https://itsfoss.com/install-arch-linux/

seth · 2021-06-06 12:23:30

So sda1 is likely your ESP, maybe re-consult the tutorial and read what you should have actually done, which is https://wiki.archlinux.org/title/Installation_guide - try to understand what that tutorial made you do.
I understand that this can feel overwhelming but if you've no interest in understanding what you do, you're better of sticking w/ an arch derivate like manjaro than following one of the silly "today i'll show you how to wanna be cool" tutorials.

Also nb. that yetanothershittytutorialonhwotonotinstallarchlinux kinda skipped the part where you mount the boot partition when not installing in UEFI mode so it's a bit important to know which path you actually followed.

ANd you've not addressed the other questions in #17.

Oceanarium · 2021-06-06 12:54:34

Well the arch wiki talks in an advanced language I don't quite understand yet; I've only been using Linux for a little over a year, though that entire time I've always tried to do things through the terminal instead of a GUI, so using other guides that simplify the language helps a lot; but seeing that it left out an important step, that's not good either lol.

Also I installed the kernel again after mounting my boot and when I try to update it I get the error "invalid or corrupted (PGP signature)

I ran:
# rm -R /etc/pacman.d/gnupg/
# rm -R /root/.gnupg/
# gpg --refresh-keys
# pacman-key --init && pacman-key --populate archlinux
# pacman-key --refresh-keys

From this page:
https://bbs.archlinux.org/viewtopic.php?id=244976

However that didn't change anything apparently, I still get the same error.

seth · 2021-06-06 13:20:44

Ensure to mount it into the location you used at the installation - the guide suggests that was /boot/efi?

There's a chance the package in the cache is corrupted (partial download) - remove it from the cache and if the error repmains, please post the actual message.

Oceanarium · 2021-06-06 23:36:06

I mounted to boot/efi and it gave me the same error so I removed it from a cache and ran:

pacman -S Linux
to reinstall it and when I run:

ls /var/cache/pacmman/pkg/linux*
it shows the file is there but when I run:

pacman -U
to that file it gives me:

"error: 'var/cache/pacman/pkg/linux-5.12.8.arch1-1-x86_64.pkg.tar.zst' : could not find or read package"

skunktrader · 2021-06-07 01:39:36

Oceanarium wrote:

"error: 'var/cache/pacman/pkg/linux-5.12.8.arch1-1-x86_64.pkg.tar.zst' : could not find or read package"

It seems you missed the leading / when specifying the file

Oceanarium · 2021-06-07 04:04:54

I did it right this time, it installs but when I reboot it drops me into tty for 5.12.9 now with no error messages. I ran the update cache for 5.12.9 again and in the install messages it says:

WARNING: Possibly missing firmware for module: aic94xx
WARNING: Possibly missing firmware for module: wd719x
WARNING: Possibly missing firmware for module: xhci_pci

These are the only warnings I get, could this be the problem?

seth · 2021-06-07 06:21:16

could this be the problem?

No. Unless you've some rather exotic HW.

but when I reboot it drops me into tty for 5.12.9

You're not being dropped anywhere. Unless you've configured a graphical.targt, that's exactly what's supposed to happen.
Run

find /etc/systemd -type l -exec test -f {} \; -print | curl -F 'f:1=<-' ix.io

and post the returned link.

Arch Linux

#1 2021-06-05 02:17:18

Dropped Into TTY At Boot Immeduately After Changing Kernel

#2 2021-06-05 06:54:04

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#3 2021-06-05 07:22:48

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#4 2021-06-05 08:31:49

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#5 2021-06-05 08:34:52

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#6 2021-06-06 00:11:13

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#7 2021-06-06 00:22:01

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#8 2021-06-06 00:37:50

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#9 2021-06-06 00:41:48

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#10 2021-06-06 00:43:57

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#11 2021-06-06 00:48:21

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#12 2021-06-06 00:55:06

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#13 2021-06-06 00:59:15

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#14 2021-06-06 01:10:19

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#15 2021-06-06 01:19:47

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#16 2021-06-06 02:04:02

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#17 2021-06-06 07:51:26

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#18 2021-06-06 11:47:04

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#19 2021-06-06 12:23:30

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#20 2021-06-06 12:54:34

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#21 2021-06-06 13:20:44

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#22 2021-06-06 23:36:06

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#23 2021-06-07 01:39:36

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#24 2021-06-07 04:04:54

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

#25 2021-06-07 06:21:16

Re: Dropped Into TTY At Boot Immeduately After Changing Kernel

Board footer