Comment 78 for bug 1788997

Revision history for this message
Heribert Heckhoff (hheckhoff) wrote :

hmm, well...I'm not sure what happened...

the kernel created of the packages from https://people.canonical.com/~khfeng/lp1788997/ (post #75) just works great.

However, I run an update as well later this day and that included (supposingly) the very same packages. However the kernel generated from those packages does not work at all. Strange, as both kernel packages have the very same version number ...

The generated kernel files do as well differ ( first column as of #75, second column as of update )

initrd.img-4.15.0-46-generic /boot/initrd.img-4.15.0-46-generic differ: byte 5, line 1
System.map-4.15.0-46-generic /boot/System.map-4.15.0-46-generic differ: byte 11352, line 334
vmlinuz-4.15.0-46-generic /boot/vmlinuz-4.15.0-46-generic differ: byte 159, line 4

I guess it's normal that initrd.img differ, as there seems to be a time stamp at the beginning of the image ....

uname reveals for the kernel as of post #75 reveals:

Linux heri-hp-pc 4.15.0-46-generic #49 SMP Fri Mar 8 13:21:42 CST 2019 x86_64 x86_64 x86_64 GNU/Linux

uname for the kernel after the update reveals:

Linux heri-hp-pc 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

pretty weird :-(