[SOLVED] -Syyu was the last thing I saw

fanda · 2025-05-25 18:27:11

I changed the mirrorlist. Somewhere on the wiki I came across the advice that after changing the mirrorlist it is a good idea to enter the command: pacman -Syyu. It updated the kernel and firmware. On reboot, ethernet and audio did not work. So I downgraded from linux-6.14.7 back to linux-6.14.6 with firmware. Now, when I normally upgrade with -Syu and install linux-6.14.7, the ethernet and audio are again non-functional. How to fix this so I can upgrade normally.

(-Syyuu didnt help either)

Last edited by fanda (2025-05-31 06:49:55)

seth · 2025-05-25 20:20:02

Sounds like the installed and booting kernels fall apart, typically because you either forgot to mount the /boot partition before installing the kernel or you're mounting a spurious boot partition but are actually booting from the root partition.

Check your older journals, if vmlinuz-linux is referecend relative to "=/boot/vmlin… " you're booting from the root partition, "…=/vmlinuz…" is from a boot partition.
Also inspect the files on the partition and mount paths.

fanda · 2025-05-26 17:26:43

seth wrote:

Sounds like the installed and booting kernels fall apart, typically because you either forgot to mount the /boot partition before installing the kernel or you're mounting a spurious boot partition but are actually booting from the root partition.
Check your older journals, if vmlinuz-linux is referecend relative to "=/boot/vmlin… " you're booting from the root partition, "…=/vmlinuz…" is from a boot partition.
Also inspect the files on the partition and mount paths.

Thank you for your reply. I didn't mount /boot partition properly. I have repeated part of the installing process and hoping for the best.

seth · 2025-05-26 20:17:24

And …?

fanda · 2025-05-27 14:52:22

seth wrote:

And …?

I dont know.

lsblk
nvme0n1     259:0    0 931.5G  0 disk 
├─nvme0n1p1 259:1    0   300M  0 part /boot
└─nvme0n1p2 259:2    0 931.2G  0 part /

cat /etc/fstab
# /dev/nvme0n1p2
UUID=5ddb4740-1d99-41b4-9906-caa10402ea9f       /               ext4            rw,relatime     0 1
# /dev/nvme0n1p1
UUID=C0F8-F466          /boot           vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro   0 2

sudo journalctl -b -1 | grep vmlinuz
May 26 18:29:13 archlinux kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=5ddb4740-1d99-41b4-9906-caa10402ea9f rw loglevel=3 quiet
May 26 18:29:13 archlinux kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=5ddb4740-1d99-41b4-9906-caa10402ea9f rw loglevel=3 quiet
May 26 18:29:13 archlinux kernel: Unknown kernel command line parameters "BOOT_IMAGE=/vmlinuz-linux", will be passed to user space.
May 26 18:29:13 archlinux kernel:     BOOT_IMAGE=/vmlinuz-linux

seth · 2025-05-27 15:02:24

You're booting from some boot partition (reasonably /dev/nvme0n1p1)
Did re-installing the kernel w/ that mounted not fix it?

There's a chance you might have /vmnlinux-* on the root partition which would then double-feature as your /boot partition?

fanda · 2025-05-27 16:09:47

seth wrote:

You're booting from some boot partition (reasonably /dev/nvme0n1p1)
Did re-installing the kernel w/ that mounted not fix it?
There's a chance you might have /vmnlinux-* on the root partition which would then double-feature as your /boot partition?

I dont know

Device          Start        End    Sectors   Size Type
/dev/nvme0n1p1   2048     616447     614400   300M EFI System
/dev/nvme0n1p2 616448 1953523711 1952907264 931.2G Linux filesystem

fanda archlinux ~ efibootmgr
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0001
Boot0000* GRUB  HD(1,GPT,99e81c86-edcb-45bc-81ee-ee9c4db50edb,0x800,0x96000)/\EFI\GRUB\grubx64.efi
Boot0001* UEFI OS       HD(1,GPT,d708cb3b-16ab-4e76-93bd-906f411830ed,0x800,0x100000)/\EFI\BOOT\BOOTX64.EFI0000424f

seth · 2025-05-27 20:16:20

What do you mean you don't know?
Does the system boot again?

findmnt -T /boot
ls -l / /boot
umount /boot
findmnt -T /boot
ls -l /boot

fanda · 2025-05-28 15:11:32

seth wrote:

What do you mean you don't know?
Does the system boot again?
findmnt -T /boot
ls -l / /boot
umount /boot
findmnt -T /boot
ls -l /boot

I mean everything works fine as far as I can see. But I don't know what will happen after new Linux version will arrive.

findmnt -T /boot
TARGET SOURCE         FSTYPE OPTIONS
/boot  /dev/nvme0n1p1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro

ls -l / /boot
/:
total 56
lrwxrwxrwx   1 root root     7 May  3 21:26 bin -> usr/bin
drwxr-xr-x   4 root root  4096 Jan  1  1970 boot
drwxr-xr-x  21 root root  4200 May 28 16:41 dev
drwxr-xr-x   2 root root  4096 May 23 22:10 efi
drwxr-xr-x  63 root root  4096 May 28 16:36 etc
drwxr-xr-x   3 root root  4096 May 24 09:04 home
lrwxrwxrwx   1 root root     7 May  3 21:26 lib -> usr/lib
lrwxrwxrwx   1 root root     7 May  3 21:26 lib64 -> usr/lib
drwx------   2 root root 16384 May 23 19:49 lost+found
drwxr-xr-x   2 root root  4096 May  3 21:26 mnt
drwxr-xr-x   3 root root  4096 May 24 18:52 opt
dr-xr-xr-x 356 root root     0 May 28 16:35 proc
drwxr-x---  17 root root  4096 May 26 20:03 root
drwxr-xr-x  18 root root   440 May 28 16:35 run
lrwxrwxrwx   1 root root     7 May  3 21:26 sbin -> usr/bin
drwxr-xr-x   4 root root  4096 May 23 20:08 srv
dr-xr-xr-x  13 root root     0 May 28 16:43 sys
drwxrwxrwt   9 root root   220 May 28 16:42 tmp
drwxr-xr-x   9 root root  4096 May 26 20:12 usr
drwxr-xr-x  12 root root  4096 May 27 16:37 var

/boot:
total 169148
drwxr-xr-x 3 root root      4096 May 23 21:58 EFI
drwxr-xr-x 6 root root      4096 May 26 18:13 grub
-rwxr-xr-x 1 root root    153600 May  9 21:22 amd-ucode.img
-rwxr-xr-x 1 root root 119011066 May 26 18:28 initramfs-linux-fallback.img
-rwxr-xr-x 1 root root  38560843 May 26 18:28 initramfs-linux.img
-rwxr-xr-x 1 root root  15462912 May 26 18:28 vmlinuz-linux

umount /boot
findmnt -T /boot
TARGET SOURCE         FSTYPE OPTIONS
/      /dev/nvme0n1p2 ext4   rw,relatime

ls -l /boot
total 168980
-rw-r--r-- 1 root root    153600 May 22 20:06 amd-ucode.img
-rw------- 1 root root 118929463 May 25 19:56 initramfs-linux-fallback.img
-rw------- 1 root root  38489163 May 25 19:56 initramfs-linux.img
-rw-r--r-- 1 root root  15450624 May 25 19:56 vmlinuz-linux

seth · 2025-05-28 18:48:55

Try to install and boot the lts kernel (you'll have to regenerate the grub config manually) - if that works, be confident

Arch Linux

#1 2025-05-25 18:27:11

[SOLVED] -Syyu was the last thing I saw

#2 2025-05-25 20:20:02

Re: [SOLVED] -Syyu was the last thing I saw

#3 2025-05-26 17:26:43

Re: [SOLVED] -Syyu was the last thing I saw

#4 2025-05-26 20:17:24

Re: [SOLVED] -Syyu was the last thing I saw

#5 2025-05-27 14:52:22

Re: [SOLVED] -Syyu was the last thing I saw

#6 2025-05-27 15:02:24

Re: [SOLVED] -Syyu was the last thing I saw

#7 2025-05-27 16:09:47

Re: [SOLVED] -Syyu was the last thing I saw

#8 2025-05-27 20:16:20

Re: [SOLVED] -Syyu was the last thing I saw

#9 2025-05-28 15:11:32

Re: [SOLVED] -Syyu was the last thing I saw

#10 2025-05-28 18:48:55

Re: [SOLVED] -Syyu was the last thing I saw

Board footer