What | Removed | Added |
---|---|---|
Flags | needinfo?(nwr10cst-oslnx@yahoo.com) |
Responding to Michael at comment #12 Note that I originally reported this as a kernel bug, so Takashi is on the CC list for this bug. Let me give a few more details that I may have missed. I have both Tumbleweed and Leap 15.2 installed in the same VM. Currently, Leap 15.2 controls the booting. But it is easy to switch to have Tumbleweed control the booting. Whichever controls the booting, the grub menu includes an entry to boot Tumbleweed and an entry to boot Leap 15.2. When I said that the Tumbleweed grub would not boot the 5.3 kernel, I was referring to booting Leap 15.2 from the Tumbleweed grub menu. I could try installing that kernel in Tumbleweed, but it wouldn't make any difference since the problem seems to be a failure to load the kernel. I did install a 5.8 kernel into Leap 15.2, and that was able to boot. Using the working grub2-i386-efi (the previous version), I did try booting using "linuxefi" rather than "linux". And that successfully boots Tumbleweed (5.8.x kernel) but fails to boot Leap 15.2 (5.3.x kernel). I have noticed, from another bug report, that Takashi has a repo with old Tumbleweed kernels back to 5.4.x. I may try some of those to see where the kernel behavior changes with "linuxefi". I have already tested kernel 5.7.11, which I still have in the Tumbleweed system. And that boots fine with "linuxefi".