dev.4openid
New Member
Hi,
I refer to the issue stated in:
https://www.linux.org/threads/new-to-linux-nobara-cant-boot.69060/
I also get a dracut message once I invoke the maintenance option.
There seems to be a bug in the init processes. I am using Ubuntu 26.04 and have installed it on a SSD and USB stick (Ventoy). I can boot up either on PC no 2 - no problem. Whereas on PC no 1 it goes into a Kernel Panic if I boot into kernel 7.1/7.2/7.3 OR if I boot into 7.0.1.12/7.0.1.13 it goes to the same screen as the original post (dracut.....etc.). This seemingly started with a boot sector error where the boot sector was out of sync with the hidden bsckup version (which, by the way, has booted up over all the Ubuntu upgrades to date until this problem). I suspect that the move to 7.0+ where the removal of 32-bit code has now disabled to boot process for older PCs. I could be wrong here of course.
BTW PC no 1 is. mac mini 2014 and has been running Ubuntu since then.
I have spent a lot of time trying to resolve this but to no avail and even reverting in grub to older version has not helped.
Are there any more folks with this problem?
Perhaps there is a bug in kernel 7.0+.....Note My original upgrade to Ubuntu 26.04 worked fine but now if I reinstall I get the same error.
Any ideas anyone?
I refer to the issue stated in:
https://www.linux.org/threads/new-to-linux-nobara-cant-boot.69060/
I also get a dracut message once I invoke the maintenance option.
There seems to be a bug in the init processes. I am using Ubuntu 26.04 and have installed it on a SSD and USB stick (Ventoy). I can boot up either on PC no 2 - no problem. Whereas on PC no 1 it goes into a Kernel Panic if I boot into kernel 7.1/7.2/7.3 OR if I boot into 7.0.1.12/7.0.1.13 it goes to the same screen as the original post (dracut.....etc.). This seemingly started with a boot sector error where the boot sector was out of sync with the hidden bsckup version (which, by the way, has booted up over all the Ubuntu upgrades to date until this problem). I suspect that the move to 7.0+ where the removal of 32-bit code has now disabled to boot process for older PCs. I could be wrong here of course.
BTW PC no 1 is. mac mini 2014 and has been running Ubuntu since then.
I have spent a lot of time trying to resolve this but to no avail and even reverting in grub to older version has not helped.
Are there any more folks with this problem?
Perhaps there is a bug in kernel 7.0+.....Note My original upgrade to Ubuntu 26.04 worked fine but now if I reinstall I get the same error.
Any ideas anyone?
