New to Linux, Nobara Can't boot

[LuminusDreams]

Hello! I'm new to Linux and I've been wanting to try and use it for gaming purposes and after searching which one is best, I found Nobara suitable for me, after watching some tutorials. I ended up running on a problem. For some reason Nobara just can't boot after pressing enter on Test on media > Run Nobara 43. It does it's thing before saying that it failed? And then shuts down my entire PC. Can anyone help??

Just to add more notes, I'm switching from Linux Mint, and my computers specs are NVIDIA 50 Series, AMD Ryzen 5. At least that's what I think that I only need to list, feel free to tell me on what to add more onto this.

 

[osprey]

Hello! I'm new to Linux and I've been wanting to try and use it for gaming purposes and after searching which one is best, I found Nobara suitable for me, after watching some tutorials. I ended up running on a problem. For some reason Nobara just can't boot after pressing enter on Test on media > Run Nobara 43. It does it's thing before saying that it failed? And then shuts down my entire PC. Can anyone help??

Just to add more notes, I'm switching from Linux Mint, and my computers specs are NVIDIA 50 Series, AMD Ryzen 5. At least that's what I think that I only need to list, feel free to tell me on what to add more onto this.
View attachment 32696

Welcome.
It looks like you are trying to boot a live disk of nobara, but it's failing. This suggests an issue with the iso file on the media. In that case, the iso is best checked using the sha256sum checksum about which details can be found here: https://wiki.nobaraproject.org/en/new-user-guide-general-guidelines. After the checksum shows no issues with the iso, then that issue can be discounted as a problem, but it really needs to be eliminated as an issue.

Nobara actually appear to recommend using ventoy which is mentioned on this page: https://nobaraproject.org/download.html, so that's worth considering.

There's also a consideration in relation to downloading isos for handling intel, amd and nvidia, so that's probably worth a bit of research too.

 

[LuminusDreams]

Oh yeah, I did all those things and it didn't work. But I did manage to figure out how to fix the problem myself.

So, for some reason, using Rufus instead of Ventoy worked out for me. (I had to use a different laptop to reformat my USB Stick from Ventoy to Rufus, and of course the Laptops OS had to be Windows for Rufus to work.) And judging from all the videos that I've watched, they've all switched from Windows to Linux, so I assume Ventoy only works if you're switching from Windows? I haven't tested it out myself, but it seemed to be a case in this Reddit Thread.

https://www.reddit.com/r/NobaraProject/comments/1gm3tiw/issue_with_liveiso_cant_find_root

Though, I'd like to learn a way for me to Switch from Linux to Linux instead of having to use a different computer to do it. And I find having to switch from Linux to Windows and then doing the same thing, but the opposite an annoying task.
P.S doing it in a virtualbox doesn't really work since it wouldn't register the USB, unless there's a way to do that, in which is also like to learn how.

 

[dev.4openid]

There seems to be a bug in the init processes. I am using Ubuntu 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?