You are not logged in.
I have an issue with 4.13 kernels and I don't belive it is a IMMO issue.
After upgrades from 4.12 to 4.13.1 or, as of today, to 4.13.4, the system freezes at either the lightdm login screen or slightly before, with no hardware input (keyboard/mouse) possible. Only a hard reset works, whereafter the kernel needs to be downgraded to 4.12 to regain a working system.
The most prominent issue that pops up during boot is a failiure to connect the wifi subsystem and it times out after 1.5 minutes. Here is the jounal entry:
https://pastebin.com/k5mvcDsB
I have no idea what the issue is here.
Interesting also that on the top of the journal, the kernel is still reported as 4.12.8 although it was updated. I have tried to set intel_iommu=off but this did not help.
Any ideas?
Thanks!
Last edited by YesMen (2018-02-10 20:48:24)
Offline
Welcome to the arch linux forums YesMen. Boot into the system using live / install media. Mount the systems filesystem hierarchy under /mnt.
Then post the output of the following
# file /mnt/boot/vmlinuz-linux
# pacman -r /mnt -Q linux
# blkid
See the tip box from List_of_applications#Pastebin_clients to paste the output from the console.
Offline
Thanks loqs.
Here is the respective output:
file /mnt/boot/vmlinuz-linux
mnt/boot/vmlinuz-linux: Linux kernel x86 boot executable bzImage, version 4.13.4-1-ARCH (builduser@tobias) #1 SMP PREEMPT Thu Sep 28 08:3, RO-rootFS, swap_dev 0x5, Normal VGA
pacman -r /mnt -Q linux
linux 4.13.4-1
blkid
/dev/sda1: LABEL="Wiederherstellung" UUID="B82CF9AF2CF96930" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="8a11a174-e31d-4753-b7a2-86c603caac0c"
/dev/sda2: UUID="FAF9-F5C6" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="8084e514-113d-4158-b04f-36afde8a7314"
/dev/sda4: UUID="2CA65F5AA65F241C" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="e7e3bee6-abd8-42d9-b977-a2cbd074f71f"
/dev/sda5: UUID="27d45830-0f12-434f-8de0-fdbf276febb4" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="e102d845-3697-4499-bc09-3f2d7efed5be"
/dev/sda6: UUID="3e6948da-4cda-4e34-bd4b-de04dfb657f6" TYPE="swap" PARTLABEL="Linux swap" PARTUUID="58b7b216-171c-4d16-af73-8a70428acfe9"
/dev/sda7: UUID="48d4197a-6ae1-4df4-9b7f-39c2cf4bb408" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="8392b9b6-8e23-4aa1-aec1-e02e1ee00fb0"
/dev/sda8: UUID="10fbc502-d7f3-445b-82c6-ae032321e6ee" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="6e0800f7-92e1-4f20-996e-3038dd584de4"
/dev/sda9: LABEL="Volume" UUID="525414C65414AF2B" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="c9663836-2223-4c2c-87a7-57d695e9509c"
/dev/sdb1: LABEL="ARCH_201608" UUID="F67B-6FBE" TYPE="vfat" PARTUUID="00116d72-01"
/dev/loop0: TYPE="squashfs"
/dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="c6d340f2-7520-4666-9941-8b9602fbbdb8"
Last edited by YesMen (2017-10-07 22:21:52)
Offline
Thank you for the outputs just to be certain /dev/sda2 was mounted at /mnt/boot when you ran the file command?
If so there is no kernel mismatch but the journal entry is from a 4.12.8-2 boot so not the boot where the issue occurred therefore there is no information to diagnose the cause of the issue.
Offline
No it was not. /dev/sda2 was not mounted to /mnt but /dev/sda7 was.
The reason is that when I do mount /dev/sda2 and try to revert to 4.12.8, it is not working automatically via pacman. I will mount /dev/sda2 though and supply the info momentarily.
Offline
You want the root filesystem of the install (/dev/sda7?) mounted to /mnt then mount the systems boot partition (/dev/sda2?) to /mnt/boot
Edit:
/dev/sda5 and /dev/sda8 are ext4 as well if they are also part of the arch install then they should be mounted as well you can skip the swap partiton.
Last edited by loqs (2017-10-07 22:37:40)
Offline
You guessed right there is a mismatch here:
file /mnt/boot/vmlinuz-linux
/mnt/boot/vmlinuz-linux: Linux kernel x86 boot executable bzImage, version 4.12.8-2-ARCH (builduser@foutrelis) #1 SMP PREEMPT Fri Aug 18 1, RO-rootFS, swap_dev 0x5, Normal VGA
pacman -r /mnt -Q linux
linux 4.13.4-1
What I don't understand is how the EFI partition gets updated in the first place. It is not mounted at the moment while I am running the 4.12.8 kernel. And I am not aware that it was mounted to /boot in the past at all...
Edit2: what is further puzzling is the fact that /dev/sda2 is full. So if I mount it to /boot now and try to update I get an error stating that.
Last edited by YesMen (2017-10-07 22:54:07)
Offline
It must have been mounted at some point for the kernel to placed there. Arch does not have automation scripts that would mount the ESP automatically.
Reinstall the linux package with the EFI mounted then an entry to the systems fstab for /boot.
To clean up the mismatching kernel files unmount /boot and remove all the files left in the /boot directory which should be an empty mount point.
Edit:
How did you try and reinstall the linux package?
Last edited by loqs (2017-10-07 22:57:56)
Offline
Well, that's what I tried basically. But as mentioned in my edit, I cannot update /dev/sda2 when mounted to /boot since it is full:
df -h
/dev/sda2 95M 95M 0 100% /boot
95M seems very small in the first place. Is that a usual size for a EFI partition?
Last edited by YesMen (2017-10-07 22:59:47)
Offline
I noticed I had linux-lts in there which I simply deleted. After that the update to 4.13.4 worked (am using it now).
Thanks a lot!
Last edited by YesMen (2017-10-07 23:04:05)
Offline
Ideally you want to resize the ESP to 200+M but that is outside my area of expertise.
Offline