Can not get Fedora based OS to boot/install

plwnmaster

New Member
Joined
May 3, 2025
Messages
3
Reaction score
2
Credits
41
Hello, I am attempting to dual-boot a Fedora based version (Fedora KDE, Fedora Workstation, Nobara, Bazzite) of Linux on my desktop, specs of pc attached. No matter what I change in BIOS, or how/which program (Rufus, Balena, Ventoy, Fedora Media writer) I format the USB with. Once I boot off the USB and start the OS, I get an out of memory error, press any key to continue followed by a kernel panic 'Unable to mount root fs on unkown-block(0,0).

My BIOS is on the latest version and I have changed every setting I could find listed on every site so far including, disabling CSM, setting secure boot to 'Other OS' and secure boot mode to, 'custom,' along with clearing they keys in key management. I have tried disabling 'VT-d' and Intel virtualization technology to no avail. I have disabled fastboot and resizable bar.. I have tried resetting my BIOS to factory recommenced settings only to see no change.

Additionally, I have tried editing the boot parameters of all 4 installations using nomodeset, dis_ucode_ldr, pci=nomsi, acpi=off, or noapic in different pairs and combinations also to no avail. I have tried both USB ports on the front and back of the desktop with no change along with trying different USB sticks.

The only change I have seen despite trying all these different combinations was using Ventoy with GRUB2 when launching Fedora, editing the boot parameters would yield me a 'can't allocate kernel' followed by 'you need to load the kernel first' in lieu of just being out of memory and proceeding to kernel panic.

I have been beating my head against the wall just trying every little change I see listed on every website, or that chatgpt has suggested and I am getting nowhere. Any help would be greatly apprecaited. Please let me know if I need to include any more information. Thank you in advance.



1746329278556.png
 


Once I boot off the USB and start the OS, I get an out of memory error, press any key to continue followed by a kernel panic 'Unable to mount root fs on unkown-block(0,0).
Normally it doesn't require a lot of effort to boot from a flash drive. As a test, what happens when you try to boot Ubuntu or Linux Mint off of the same usb flash drive? Have you tried using a different usb flash drive? I also remember a recent post of someone having an IMPI module on their motherboard which was causing an issue, do you have non-standard hardware features in your motherboard or other hardware components that aren't that mainstream?
 
Hello @plwnmaster
Welcome to the Linux.org forum, I don't know that I can help with your problem as I have never had a problem booting and installing Fedora. But give us as much info as you an on you hardware and we will see if we can give you guidance.
 
I did some digging with a search engine, rooting through a dozen or so links and resulting information.

The following is for Ubuntu but is not all that dated and may apply here.

 
Normally it doesn't require a lot of effort to boot from a flash drive. As a test, what happens when you try to boot Ubuntu or Linux Mint off of the same usb flash drive? Have you tried using a different usb flash drive? I also remember a recent post of someone having an IMPI module on their motherboard which was causing an issue, do you have none-standard hardware features in your motherboard or other hardware components that aren't that mainstream?
So, I did try putting PopOS on Ventoy and was able to boot off that with Grub2... I actually use PopOS on my Homekit server... I just really dont understand why I can not get any Fedora based OS to even boot off USB.

I double checked the manual and this mobo has no reference of IMPI, unless I am missing something. It was actually that exact thread I found through search that lead to me posting here.
 
Hello @plwnmaster
Welcome to the Linux.org forum, I don't know that I can help with your problem as I have never had a problem booting and installing Fedora. But give us as much info as you an on you hardware and we will see if we can give you guidance.
@kc1di Hello! Other than the hardware listed in the screenshot, I suppose it is relevant to mention that 990 Pro has Windows 11 on it and I was attempting to put some Fedora based Linux on the 970 Evo.. Which has landed me here, despite my best efforts.
 
I would almost bet it's the Nvidia card causing the problems but that should not cause it to not boot live since most Distro revert to open source driver for that.
 
I format the USB with. Once I boot off the USB and start the OS, I get an out of memory error, press any key to continue followed by a kernel panic 'Unable to mount root fs on unkown-block(0,0).

I have seen this with Rufus, but not usually with the others. My first thought here, is you downloaded a bad image.
disabling CSM, setting secure boot to 'Other OS' and secure boot mode to, 'custom,' along with clearing they keys in key management. I have tried disabling 'VT-d' and Intel virtualization technology to no avail. I have disabled fastboot and resizable bar.. I have tried resetting my BIOS to factory recommenced settings only to see no change.

You shouldn't have to do any of this. EFI mode is usually recommended, but Legacy BIOS mode works fine.
Additionally, I have tried editing the boot parameters of all 4 installations using nomodeset, dis_ucode_ldr, pci=nomsi, acpi=off, or noapic in different pairs and combinations also to no avail. I have tried both USB ports on the front and back of the desktop with no change along with trying different USB sticks.

You shouldn't have to do any of this either. But since you are getting an "out of memory" error, you can try this.
Code:
 mem=4096M

Fedora can be more picky about hardware errors than other distro's. I see you have the exact same RAM modules I am using while typing this, so I don't really think that's the problem.

I would almost bet it's the Nvidia card causing the problem

Possibly, but plenty of people are running newer nvidia cards under fedora. This system is Radeon, but I do have a system with a 2080 GeForce, it should use the same drivers as the 4090. Normally fedora will default to the nouveau drivers.

Ventoy with GRUB2 when launching Fedora, editing the boot parameters would yield me a 'can't allocate kernel' followed by 'you need to load the kernel first' in lieu of just being out of memory and proceeding to kernel panic.

Fedora uses grub2 also, so I don't see how that would make a difference. It's been a long time since I've used Ventoy, but if I remember it has it's own bootloader. I see you made some changes to secure boot. I'm not sure what "custom" means.
But fedora doesn't like to mix signed and unsigned boot kernels. I've seen this error when kickstarting and trying to mix them. I used to have a AlmaLinux kickstart server, I was using the boot kernel for that. But fedora uses a newer kernel so I had to switch to a fedora kickstart server. I've found the newer boot kernels will usually support older kernels, but not the other way around.
Old boot kernels don't support newer kernels.

As a last resort you can try...
Code:
systemd.mask=systemd-oomd.service
in your boot parms. (You really shouldn' need this)
 
Last edited:
Using a tool like Fedora Media Writer could help ensure the media is correctly written.

That is fine if you have a Linux already onboard, but no good if you are trying to install from Windows?

Welcome to linux.org, BTW :)

Chris Turner
wizardfromoz
 
Hello, I am attempting to dual-boot a Fedora based version (Fedora KDE, Fedora Workstation, Nobara, Bazzite) of Linux on my desktop, specs of pc attached. No matter what I change in BIOS, or how/which program (Rufus, Balena, Ventoy, Fedora Media writer) I format the USB with. Once I boot off the USB and start the OS, I get an out of memory error, press any key to continue followed by a kernel panic 'Unable to mount root fs on unkown-block(0,0).

My BIOS is on the latest version and I have changed every setting I could find listed on every site so far including, disabling CSM, setting secure boot to 'Other OS' and secure boot mode to, 'custom,' along with clearing they keys in key management. I have tried disabling 'VT-d' and Intel virtualization technology to no avail. I have disabled fastboot and resizable bar.. I have tried resetting my BIOS to factory recommenced settings only to see no change.

Additionally, I have tried editing the boot parameters of all 4 installations using nomodeset, dis_ucode_ldr, pci=nomsi, acpi=off, or noapic in different pairs and combinations also to no avail. I have tried both USB ports on the front and back of the desktop with no change along with trying different USB sticks.

The only change I have seen despite trying all these different combinations was using Ventoy with GRUB2 when launching Fedora, editing the boot parameters would yield me a 'can't allocate kernel' followed by 'you need to load the kernel first' in lieu of just being out of memory and proceeding to kernel panic.

I have been beating my head against the wall just trying every little change I see listed on every website, or that chatgpt has suggested and I am getting nowhere. Any help would be greatly apprecaited. Please let me know if I need to include any more information. Thank you in advance.



View attachment 25818

look at that link and redo the dual boot that way. You will never regret it and never have to fix grub again. Never have to worry about windows screwing the pooch again.
 
I get the feeling that your kernel boot string might not be getting interpreted correctly.
Maybe something bad is happening to the initial RAMdisk that linux usually creates during kernel boot. Hopefully somebody else can elaborate on this?
 
Hello, this is a week or so back, but I happened to see your post when I was looking for solutions to my own "Fedora won't install" issues with a Dell , in all my reading I remember something about an "out of memory" error related to the video memory! There was some talk of changing that number in the BIOS, but mine doesn't allow that so I can't give you any guidance on how to go about fixing it, but ...you might look into that, if you haven't found a solution already.
 
I had a similar issue. The solution for me was to turn on Above 4G Decoding in my motherboard BIOS options. For me, this option was under the Boot menu. If you have this option, try toggling it.

This item enables or disables 64-bit capable devices to be decoded in above 4G address space if your system supports 64-bit PCI Decoding.
 


Follow Linux.org


Top