uname -r incorrect after upgrade under qemu

[shaughan]

Under qemu:
After upgrading (pacman -Syu) linux-aarch64,
I have
$this->bbcode_second_pass_code('', '
pacman -Qs linux-aarch64
local/linux-aarch64 5.6.11-1
')
but
$this->bbcode_second_pass_code('', '
uname -r
5.5.7-1-ARCH
')
As a result, modules do not load and (among other things) no nic. And yes—I did remember to reboot.

[moonman]

You boot partition is not mounted during upgrade, or mounted at a wrong mount point.

[shaughan]

Thank you for replying.
$this->bbcode_second_pass_code('', 'ls /boot
Image Image.gz dtbs initramfs-linux-fallback.img initramfs-linux.img
')
so it seems to be mounted. However, there is no boot entry in /etc/mtab. My fstab has no entries. I'm confused about what all that means.

[summers]

Use $this->bbcode_second_pass_code('', 'fdisk') on your disk, and see what $this->bbcode_second_pass_code('', 'p') says ...

[shaughan]

$this->bbcode_second_pass_code('', '
fdisk -l
')
shows /dev/vda and /dev/loop0.
$this->bbcode_second_pass_code('', '
fdisk /dev/vda
p
')
shows "Device does not contain a recognized partition table."
as does
$this->bbcode_second_pass_code('', '
fdisk /dev/loop0
p
')

[summers]

I'd check through $this->bbcode_second_pass_code('', 'dmesg') for the disks found, its probably where the root partition is, that can be seen probably in $this->bbcode_second_pass_code('', 'cat /proc/cmdline')also $this->bbcode_second_pass_code('', 'df') should show what root is ... $this->bbcode_second_pass_code('', 'lsblk') also helps, and so on ...

[shaughan]

Thanks!
$this->bbcode_second_pass_code('', '
cat /proc/cmdline
root=/dev/vda rw

df
/dev/vda … /

lsblk
vda 252:0 … disk /
')

[summers]

Ah so it's a virtual machine. Alas that's beyond my experience. I've no idea how uboot would find the boot partition under such a machine.

[shaughan]

Well, thanks for trying. I've added qemu to the title of the top post now. That's been my problem—I know nothing about how qemu boots, and not much comes up on a search.

[summers]

Did few minutes research on qemu over breakfast. Whats important is how you bring qemu up on the host machine, e.g. how you boot. If you use the linux/multiboot set up: https://www.qemu.org/docs/master/system/invocation.html#hxtool-8 then you need to update the parameters passed to the new kernel version.

If you are booting from an iso, then you should be able to fdisk the iso, and see whats on it (I think, been few years since I last did this).

But this then takes you back to how did you install arch linux arm in qemu in the first place, usually arch comes as tar file of root + some actions you do to get uboot to boot into arch. This is what you'll need to look at, whatever you did at install is what you'll need to change to point to the new kernel.