You are not logged in.

#1 2018-11-17 18:42:46

rubystallion
Member
Registered: 2018-05-05
Posts: 6

[SOLVED] "modules.devname not found" - Unbootable after update to 4.19

After running pacman -Syu, xfce crashed to an unresponsive command line and I cut off power to reboot. After reboot, the laptop boots into an unresponsive terminal with the following text:

Additional errors with ACPI on

...
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-221)
ACPI Error: Skip parsing opcode Method (20180810/psloop-542)
ACPI BIOS Error (bug): Failure creating [\_SB.PCIO.XHC.RHUB.SS09._PLD], AE_ALREADY_EXISTS (20180810/dswload2-316)
ACPI Error: Skip parsing opcode Method (20180810/psloop-542)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-221)
ACPI Error: Skip parsing opcode Method (20180810/psloop-542)
ACPI Bios Error (bug): Failure creating [\_SB.PCIO.XHC.RHUB.SS10._PLD], AE_ALREADY_EXISTS (20180810/dswload2-316)
ACPI Error: AE_ALREADY_EXISTS, During anme lookup/catalog (20180810/psobject-221)
ACPI Error: Skip parsing opcode Method (20180810/psloop-542)

Following errors

:: running early hook [udev]
Warning: /lib/modules/4.19.1-arch1-1-ARCH/modules.devname not found - ignoring
starting version 239
:: running early hook [lvm2]
:: running hook [udev]
:: Triggering uevents...
:: performing fsck on `/dev/nvme0n1p2`
/dev/nvme0n1p2: clean, 1737368/7782400 files, 20711612/31127377 blocks
************* WARNING *****************************
*                                                 *
* The root device is not configured to be mounted *
* read-write! It may be fsck'd again later.       *
***************************************************
:: mounting `/dev/nvme0n1p2` on real root
mount: /new_root: unknown filesystem type `ext4`.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs  ]#

When booting from the Arch ISO I can still access my files and a dd backup completed without errors. Running lspci makes the system unresponsive with ACPI error messages, so I booted with acpi=off. After that lspci works and wifi too, so I ran pacman -Syu again, which didn't change my problem. My laptop keyboard doesn't cause output any more after the update, but a USB keyboard works. When running startxfce4 as root after chroot to my disk (/dev/nvme0n1p2) I get an unresponsive GUI dialog:

Unable to contact settings server 
Unable to connect to socket /run/user/0/bus: No such file or directory

And when changing to my user with su - jo and running startxfce4, I get the following errors.

What steps could I try to get xfce4 to start and hopefully also be able to boot from disk again?
dmesg output after booting to Arch ISO
pacman log from running pacman -Syu yesterday and today. Note that yesterday the kernel got updated 4.18 -> 4.19, whereas acpid only got updated today after the problems appeared.
Xorg.0.log after running startxfce4 as unprivileged user

Last edited by rubystallion (2018-11-17 20:22:51)

Offline

#2 2018-11-17 18:47:43

Scimmia
Bug Wrangler
Registered: 2012-09-01
Posts: 7,086

Re: [SOLVED] "modules.devname not found" - Unbootable after update to 4.19

Looks like a mismatched initramfs. Regenerate it.

Offline

#3 2018-11-17 19:26:26

rubystallion
Member
Registered: 2018-05-05
Posts: 6

Re: [SOLVED] "modules.devname not found" - Unbootable after update to 4.19

Thanks for the quick reply! I ran

mkinitcpio -k 14.9.2-arch1-1-ARCH -g /boot/initramfs-linux.img

, which successfully created a new image file, but I still get the same issues after a reboot. The Arch ISO on my USB drive (and therefore shown in uname -a) is 4.18.16-arch1-1-ARCH.

Last edited by rubystallion (2018-11-17 19:27:57)

Offline

#4 2018-11-17 19:35:01

Scimmia
Bug Wrangler
Registered: 2012-09-01
Posts: 7,086

Re: [SOLVED] "modules.devname not found" - Unbootable after update to 4.19

14.9.2-arch1-1-ARCH isn't the kernel you're booting, even accounting for the typo

Offline

#5 2018-11-17 20:21:08

rubystallion
Member
Registered: 2018-05-05
Posts: 6

Re: [SOLVED] "modules.devname not found" - Unbootable after update to 4.19

Everything works again! You were right about the kernel version, I forgot that I had set up a separate partition for that. I'm overjoyed that you could find the solution so quickly, thank you!

Offline

Board footer

Powered by FluxBB