Just a data point, that I have been unable to run locally built or stock Fedora kernels for a couple of weeks now. I have opened a bugzilla against dracut for this, but I'm not sure that it really is dracut at fault. It is all documented in
https://bugzilla.redhat.com/show_bug.cgi?id=2109194
I can't think what is causing this on my system, since a Fedora kernel I built and installed from a src.rpm on 20220703 is running fine. And rawhide is up to date with the latest packages.
How can a stock Fedora kernel not boot on a Fedora system? Really puzzling.
On Tue, 2022-08-02 at 13:46 -0700, stan via test wrote:
Just a data point, that I have been unable to run locally built or stock Fedora kernels for a couple of weeks now. I have opened a bugzilla against dracut for this, but I'm not sure that it really is dracut at fault. It is all documented in
https://bugzilla.redhat.com/show_bug.cgi?id=2109194
I can't think what is causing this on my system, since a Fedora kernel I built and installed from a src.rpm on 20220703 is running fine. And rawhide is up to date with the latest packages.
How can a stock Fedora kernel not boot on a Fedora system? Really puzzling.
Not sure what's going on in your case, but FWIW, I'm on current Rawhide and not seeing any such problem...
On Tue, 02 Aug 2022 14:07:24 -0700 Adam Williamson adamwill@fedoraproject.org wrote:
Not sure what's going on in your case, but FWIW, I'm on current Rawhide and not seeing any such problem...
Thanks for the confirmation. I was assuming this was the case, as it seemed too major for it not to be widely reported if it was common. There were hundreds of updates in the time frame that whatever is causing this occurred. And, since the mass rebuild, they have rolled off. Maybe it is some arcane system setting I have enabled or disabled, but I don't recall changing anything that could cause this. I'll just keep plugging away. I'll probably focus on trying to boot without an initramfs, as that seems pretty straightforward, and would conclusively point or not point at dracut as the issue. That early boot process is difficult to debug because it is so minimal.
On Tue, 2 Aug 2022 14:58:16 -0700 stan upaitag@zoho.com wrote:
On Tue, 02 Aug 2022 14:07:24 -0700 Adam Williamson adamwill@fedoraproject.org wrote:
Not sure what's going on in your case, but FWIW, I'm on current Rawhide and not seeing any such problem...
Thanks for the confirmation. I was assuming this was the case, as it seemed too major for it not to be widely reported if it was common. There were hundreds of updates in the time frame that whatever is causing this occurred. And, since the mass rebuild, they have rolled off. Maybe it is some arcane system setting I have enabled or disabled, but I don't recall changing anything that could cause this. I'll just keep plugging away. I'll probably focus on trying to boot without an initramfs, as that seems pretty straightforward, and would conclusively point or not point at dracut as the issue. That early boot process is difficult to debug because it is so minimal.
The problem was missing libraries in the initramfs. When I added all the libraries back manually (about 80), the stock Fedora kernel booted successfully. My custom kernels still don't boot, but that is probably just a tweak to their configuration or dracut configuration.