You are not logged in.

#1 2020-11-07 06:41:50

cygosw
Member
Registered: 2020-09-28
Posts: 5

uname and pacman show different kernel version

Hey,

I'm having issues with virtualbox, and after a lot of tinkering I noticed there is a difference between the output of the two commands, and I wonder if that is related to the problem (can't load virtualbox kernel modules):

$uname -r
5.9.2-arch1-1

$sudo pacman -Q linux linux-headers                     
linux 5.9.4.arch1-1
linux-headers 5.9.4.arch1-1


And when I try to update it:

$sudo pacman -Syyu     
:: Synchronizing package databases...
core                   129.3 KiB   158 KiB/s 00:01 [##########################] 100%
extra                 1630.6 KiB   199 KiB/s 00:08 [##########################] 100%
community                5.2 MiB   218 KiB/s 00:25 [##########################] 100%
multilib               155.1 KiB   378 KiB/s 00:00 [##########################] 100%
sublime-text          1824.0   B  0.00   B/s 00:00 [##########################] 100%
sublime-text.sig       543.0   B  0.00   B/s 00:00 [##########################] 100%
:: Starting full system upgrade...
there is nothing to do


And I did reboot the system several time, so that didn't help.

Offline

#2 2020-11-07 07:41:16

waitnsea
Member
From: France
Registered: 2013-02-10
Posts: 67

Re: uname and pacman show different kernel version

Hi,
Only reboot...

Offline

#3 2020-11-07 07:46:55

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,697

Re: uname and pacman show different kernel version

cygosw wrote:

And I did reboot the system several time, so that didn't help.

The common cause is that you forgot to mount the boot partition when updating or the reverse, that you mounted a /boot partition but actually boot from the root partition.
Please
a) use code tags when posting shell I/O
b) post the outputs of "mount" and "file /boot/vmlinuz-linux"
c) assuming the /boot partition is mounted, unmount it and check whether there's a vmlinuz-linux in the unmounted /boot path - testing it w/ "file" will probably show the updated kernel?

Offline

#4 2020-11-07 09:18:43

cygosw
Member
Registered: 2020-09-28
Posts: 5

Re: uname and pacman show different kernel version

seth wrote:
cygosw wrote:

And I did reboot the system several time, so that didn't help.

The common cause is that you forgot to mount the boot partition when updating or the reverse, that you mounted a /boot partition but actually boot from the root partition.
Please
a) use code tags when posting shell I/O
b) post the outputs of "mount" and "file /boot/vmlinuz-linux"
c) assuming the /boot partition is mounted, unmount it and check whether there's a vmlinuz-linux in the unmounted /boot path - testing it w/ "file" will probably show the updated kernel?

Mount:

$mount                                                            
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=8126620k,nr_inodes=2031655,mode=755,inode64)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755,inode64)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
/dev/sda2 on / type ext4 (rw,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,size=4096k,nr_inodes=1024,mode=755,inode64)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=12436)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,nr_inodes=409600,inode64)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1626904k,nr_inodes=406726,mode=700,uid=1000,gid=1000,inode64)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000

file

$file /boot/vmlinuz-linux                          
/boot/vmlinuz-linux: Linux kernel x86 boot executable bzImage, version 5.9.4-arch1-1 (linux@archlinux) #1 SMP PREEMPT Wed, 04 Nov 2020 21:41:09 +0000, RO-rootFS, swap_dev 0x8, Normal VGA

So what should I do next?

Offline

#5 2020-11-07 09:26:04

loqs
Member
Registered: 2014-03-06
Posts: 19,042

Re: uname and pacman show different kernel version

Check unmounted filesystems for one containing vmlinuz-linux in its root directory then check if that kernel is version 5.9.2 using file.

Last edited by loqs (2020-11-07 09:26:13)

Offline

#6 2020-11-07 15:46:30

cygosw
Member
Registered: 2020-09-28
Posts: 5

Re: uname and pacman show different kernel version

loqs wrote:

Check unmounted filesystems for one containing vmlinuz-linux in its root directory then check if that kernel is version 5.9.2 using file.

Can you explain in noob's term what do I need to do?

Offline

#7 2020-11-07 15:53:16

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,697

Re: uname and pacman show different kernel version

Output of "lsblk -f"?

Offline

#8 2020-11-07 15:58:01

cygosw
Member
Registered: 2020-09-28
Posts: 5

Re: uname and pacman show different kernel version

seth wrote:

Output of "lsblk -f"?

$lsblk -f 
NAME   FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda                                                                           
├─sda1 vfat   FAT32       FEF0-D307                                           
└─sda2 ext4   1.0         9a846085-5e86-48a1-9b06-9fa941b8b22d  755.2G    12% /
sdb                                                                           
sr0             

Offline

#9 2020-11-07 15:59:37

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,697

Re: uname and pacman show different kernel version

Mount sda1 and look at its contents.

Offline

Board footer

Powered by FluxBB