Upgrading kernel from 4.9.235-antix to 4.9.0-264-antix

[Member blur13]

Hi!

Running antix 19.3 with all the latest updates. Trying to upgrade the kernel from 4.9.235-antix to 4.9.0-264-antix using cli-aptix. Installed 3) linux-image-4.9.0-264-antix.1-amd64-smp. Im still running 4.9.235. Cli-aptix shows that both 4) (I) linux-image-4.9.235-antix.1-amd64-smp and 3) (I) linux-image-4.9.0-264-antix.1-amd64-smp are installed. Is there anything more I have to do to start using the latest kernel?

I’ve searched through the old forums and found no guidance.

Thanks!

[Member blur13]

Helpful

Up

0

::

Tried it on another computer with the same setup and got the exact same result, ie no result. Got a similar looking “error report” from apt:

Installing linux-image-4.9.0-264-antix.1-amd64-smp
=> apt-get install linux-image-4.9.0-264-antix.1-amd64-smp linux-headers-4.9.0-264-antix.1-amd64-smp
Reading package lists… Done
Building dependency tree
Reading state information… Done
Suggested packages:
linux-firmware-image-4.9.0-264-antix.1-amd64-smp
The following NEW packages will be installed:
linux-headers-4.9.0-264-antix.1-amd64-smp linux-image-4.9.0-264-antix.1-amd64-smp
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 49.8 MB of archives.
After this operation, 259 MB of additional disk space will be used.
Get:1 http://chuangtzu.ftp.acc.umu.se/mirror/mxlinux.org/packages/antix/buster buster/main amd64 linux-headers-4.9.0-264-antix.1-amd64-smp amd64 4.9.0-264-antix.1-amd64-smp-1 [10.8 MB]
Get:2 http://gemmei.ftp.acc.umu.se/mirror/mxlinux.org/packages/antix/buster buster/main amd64 linux-image-4.9.0-264-antix.1-amd64-smp amd64 4.9.0-264-antix.1-amd64-smp-1 [39.0 MB]
Fetched 49.8 MB in 4s (11.8 MB/s)
Selecting previously unselected package linux-headers-4.9.0-264-antix.1-amd64-smp.
(Reading database … 321770 files and directories currently installed.)
Preparing to unpack …/linux-headers-4.9.0-264-antix.1-amd64-smp_4.9.0-264-antix.1-amd64-smp-1_amd64.deb …
Unpacking linux-headers-4.9.0-264-antix.1-amd64-smp (4.9.0-264-antix.1-amd64-smp-1) …
Selecting previously unselected package linux-image-4.9.0-264-antix.1-amd64-smp.
Preparing to unpack …/linux-image-4.9.0-264-antix.1-amd64-smp_4.9.0-264-antix.1-amd64-smp-1_amd64.deb …
Unpacking linux-image-4.9.0-264-antix.1-amd64-smp (4.9.0-264-antix.1-amd64-smp-1) …
Setting up linux-headers-4.9.0-264-antix.1-amd64-smp (4.9.0-264-antix.1-amd64-smp-1) …
Setting up linux-image-4.9.0-264-antix.1-amd64-smp (4.9.0-264-antix.1-amd64-smp-1) …
Warning: Unable to find an initial ram disk that I know how to handle.
Will not try to make an initrd.
update-initramfs: Generating /boot/initrd.img-4.9.0-264-antix.1-amd64-smp
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
nor crypto modules. If that’s on purpose, you may want to uninstall the
‘cryptsetup-initramfs’ package in order to disable the cryptsetup initramfs
integration and avoid this warning.
I: The initramfs will attempt to resume from /dev/sda7
I: (UUID=a2d4565a-d90e-43d4-a297-d2a63ee2c0ef)
I: Set the RESUME variable to override this.
Generating grub configuration file …
Found background: /usr/share/wallpaper/grub/back.png
Found background image: /usr/share/wallpaper/grub/back.png
Found linux image: /boot/vmlinuz-4.9.235-antix.1-amd64-smp
Found initrd image: /boot/initrd.img-4.9.235-antix.1-amd64-smp
Found linux image: /boot/vmlinuz-4.9.0-264-antix.1-amd64-smp
Found initrd image: /boot/initrd.img-4.9.0-264-antix.1-amd64-smp
Found mtest-64.efi image: /boot/uefi-mt/mtest-64.efi
Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
Found ArcoLinux (rolling) on /dev/sda5
done
install took 56.79 seconds
Updating database …
database update took 0.10 seconds
Press <Enter> to continue

[Member blur13]

Helpful

Up

0

::

Using Advanced options in Grub I can load the new kernel just fine. How do I make that the default? Is it a simple matter of removing the old kernel using apt?

[Member blur13]

Helpful

Up

0

::

sudo apt remove seemed to do the trick, now its loading the new kernel on startup.

[Moderator Brian Masinick]

Helpful

Up

0

::

@blur13:. Thank you for sharing the activity you went through to figure out what to do.

Hopefully it will be helpful to someone else. I’m happy that you figured it out and shared with us.

Enjoy antiX!

Thanks!

--
Brian Masinick

[Anonymous]

Helpful

Up

0

::

I’ve searched through the old forums and found no guidance.

That’s probably because grub configuration in antiX doesn’t doesn’t involve any special or proprietary details.

From commandline, “man -k grub” or “apropos grub” will lead you to the onboard documentation.

If questions remain, answers to questions like this are typically immediately available via websearch.
startpage.com:
grub set default kernel
or
debian grub set default kernel

https://wiki.debian.org/Grub2
https://unix.stackexchange.com/questions/198003/set-default-kernel-in-grub
https://serverfault.com/questions/427564/how-to-force-debian-to-boot-new-kernel

[Forum Admin Dave]

Helpful

Up

0

::

Easiest way would be to boot the newer kernel from the advanced menu, make sure it works good, then remove the old one.
It does not automatically set to newer because of the naming convention needed to get around the 155 limit of libc if I recall correctly. So it shows up to grub as an older kernel version.

Other than that you can set the new one to be default boot option via the /etc/default/grub and running update-grub.
There are various documents available explaining grub boot configuration as skidoo mentioned / linked to.

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Moderator Brian Masinick]

Helpful

Up

0

::

… partial notes from https://unix.stackexchange.com/questions/198003/set-default-kernel-in-grub – READ it and try the approaches there, and see if you 1) understand it and 2) get the suggestions to actually work:
…

Comment out your current default grub in /etc/default/grub:
#GRUB_DEFAULT=0

Add two lines to /etc/default/grub
GRUB_SAVEDEFAULT=true
GRUB_DEFAULT=saved
…

Do the sudo update-grub, reboot, get into your grub menu and select whichever menu or submenu item you need. The choice will be saved every time and then your computer will boot into it automatically. When you manually choose a different entry, that becomes the new default.

Again, please also read the Web page cited so that you actually learn more about this; if it doesn’t work, the page also shows you how to revert to the previous behavior.

…

--
Brian Masinick

[Author]

Posts