Comment 6 for bug 1877088

------- Comment From <email address hidden> 2020-06-02 07:57 EDT-------
I usually compile on a development machine and then
scp a tar archive of the modules and the vmlinuz e.g. to a z/VM
guest with less memory and CPU.
Previously this worked the same across all distros which makes
this very practical for us.

That said, I've now tried with a locally build Kernel
(from the focal Kernel repository master branch)
with the following sequence:

(As build dependencies I installed
build-essential, bison, flex, and libssl-dev)

$ make defconfig
(defconfig is what we usually use internally
but I don't think this changes anything)
$ make -j $(nproc)
$ sudo make modules_install
$ sudo make install

With this I also see the same issue /boot/vmlinuz is
freshly symlinked but /boot/initrd.img keeps pointing
to the previous kernel installed as a deb.

E.g. below that was the PPA Kernel from the other issue:

$ ls -l /boot/initrd.img
lrwxrwxrwx 1 root root 37 Jun 2 04:37 /boot/initrd.img -> initrd.img-5.4.0-31.35ubuntu2-generic
$ ls -l /boot/vmlinuz
lrwxrwxrwx 1 root root 14 Jun 2 05:57 /boot/vmlinuz -> vmlinuz-5.4.27