Arch Linux

rbaj

Member

Registered: 2016-01-27

Posts: 36

[SOLVED] uname -r gives the wrong kernel number after upgrading

I reinstalled Arch in order to encrypt my harddrive using LUKS on LVM. My system worked fine both before and immediately after the reinstall. A couple of days later I ran $pacman -Syu and upgraded the kernel from 4.13.5 to 4.13.6. On reboot Xorg failed saying it can't find a screen (paste, started via exec i3 in .xinitrc), my external hdd isn't recognised and there were no interfaces in $ip link. Downgrading to 4.13.5 fixes everything.

I tried updating again today to 4.13.7 with the same results. Using 4.13.7 Xorg says it can't load the module i915 so

modprobe i915
modprobe: FATAL: Module i915 not found in directory /lib/modules/4.13.5-1-ARCH

probably because that directory doesn't exist! Also

uname -r
4.13.5-1-ARCH

Any pointers on where I can look to diagnose the problem? The only major change to my setup has been adding encryption.

Last edited by rbaj (2017-10-19 13:01:49)

Slithery

Administrator

From: Norfolk, UK

Registered: 2013-12-01

Posts: 5,776

Re: [SOLVED] uname -r gives the wrong kernel number after upgrading

Your /boot partition wasn't mounted when you upgraded the kernel.

Check your fstab and add the appropriate line.

---

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

rbaj

Member

Registered: 2016-01-27

Posts: 36

Re: [SOLVED] uname -r gives the wrong kernel number after upgrading

https://bbs.archlinux.org/viewtopic.php?id=230847 has the same problem (mismatch between $pacman -Q and $uname -r). Suggests its to do with /boot not being mounted during the upgrade. https://bbs.archlinux.org/viewtopic.php?id=226200 has the solution. Sorry for the noise!

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,764

Re: [SOLVED] uname -r gives the wrong kernel number after upgrading

Boot into a liveCD mount your system partition to /mnt mount your /boot resp. ESP partition on /mnt/boot chroot in, reinstall the linux package, fix your fstab so that your  ESP is always mounted to /boot so you won't have to do this again.

Edit:
Whoops, I should be hitting refresh more before submit Please mark as [SOLVED] by editing the title in your intial post.

Last edited by V1del (2017-10-19 10:29:26)

rbaj

Member

Registered: 2016-01-27

Posts: 36

Re: [SOLVED] uname -r gives the wrong kernel number after upgrading

Thanks, you beat me to it.

rbaj

Member

Registered: 2016-01-27

Posts: 36

Re: [SOLVED] uname -r gives the wrong kernel number after upgrading

EDIT: original problem solved so I'll make a new post.

Ok one minor complication: I'm dual booting Arch with macos, so I have an ESP partition at /dev/sda1 but for some reason when setting up LUKS I also added an unencrypted boot partition to /dev/sda5, ahead of the encrypted partition /dev/sda6. I guess this is the source of the problem..

Presumably I should do something like

grub-install --target=x86_64-efi --efi-directory=/dev/sda1 --boot-directory=/dev/sda1 --bootloader-id=arch

and then add to fstab

/dev/sda1 /boot fat32

to sort everything out?

Is there any way to then merge the 200MB /boot partition on /dev/sda5 back into another partition? I'm actually using LVM on LUKS (my original post was incorrect) so perhaps not..

EDIT: clearly I tried something like this a couple of times when I was reinstalling..

$tree /boot
.
├── EFI <--- from /dev/sda1
│   ├── APPLE
│   │   └──  ...
│   │
│   ├── arch
│   │   └── grubx64.efi
│   ├── arch_grub
│   │   └── grubx64.efi
│   └── grub
│       └──  ...
│
├── grub <--- from /dev/sda5
│  └──  ...
...

Last edited by rbaj (2017-10-19 13:02:07)