Cubic

How to deal with vmlinuz and initrd version mismatch on the ISO Boot Kernel tab?

Asked by Cubic PPA

After executing `apt upgrade`, the vmlinuz and initrd versions shown on the Boot Kernels tab do not match

For example, for Ubuntu 18.04, the vmlinuz version is 4.18.0-18, but the initrd version os 4.18.0-15.

     Version name........................... 4.18.0-18
    • Index................................ 0 of 1
    • Vmlinuz filename..................... vmlinuz-4.18.0-18-generic
    • New vmlinuz filename................. vmlinuz
    • Initrd filename...................... initrd.img-4.18.0-15-generic
    • New initrd filename.................. initrd

How can this issue be solved?

Question information

Language:
English Edit question
Status:
Solved
For:
Cubic Edit question
Assignee:
No assignee Edit question
Solved by:
Cubic PPA
Solved:
Last query:
Last reply:
Revision history for this message
Cubic PPA (cubic-wizard) said : 		#1

Bug #1827157 was opened to address this issue.
However, until the fix is released, here is an easy work-around...

Click the Back button to return to Cubic's chroot terminal.
Use `apt install --reinstall` to install the missing vmlinuz file.
Be sure to use the "--reinstall" flag.

For example, the package that contains "vmlinuz-4.18.0-15-generic" is "linux-image-4.18.0-15-generic"...

(1)
In Cubic's chroot environment, execute...

    $ apt install --reinstall linux-image-4.18.0-15-generic

(3)
Verify that you have matching vmlinuz and initrd files...

In Cubic's chroot environment, execute...

    $ ls -1 /boot/{vmlinuz,initrd}*
        /boot/initrd.img-4.18.0-15-generic
        /boot/initrd.img-4.18.0-18-generic
        /boot/vmlinuz-4.18.0-15-generic
        /boot/vmlinuz-4.18.0-18-generic

(4)
Now, click the Next button to return to the ISO Boot Kernel tab, and Cubic should display the correct files and versions.

Revision history for this message
Cubic PPA (cubic-wizard) said : 		#2

This work-around is no longer necessary.

Bug #1827157 was fixed in release version 2019.05-55-release.

Revision history for this message
Cubic PPA (cubic-wizard) said : 		#3

Update:

This work-around is no longer necessary.

Bug #1827157 was fixed in release version 2019.05-56-release.