Fedora KDE x86_64 LIVE will not start on Samsung Galaxy Book6 Pro

I tried to install Fedora Linux KDE (latest) on my Samsung Galaxy Book 6 Pro, but whenever I try to start the LIVE mode from the boot menu, I get a kernel panic error and I have to hard power-off.

These are the specs of my laptop:

Device name XXXXXXX
Processor Intel(R) Core™ Ultra 7 356H (1.90 GHz)
Installed RAM 32.0 GB (31.4 GB usable)
Graphics card Intel(R) Graphics (128 MB)
Storage 166 GB of 954 GB used
Product ID 00330-80000-00000-AA057
System type 64-bit operating system, x64-based processor
Pen and touch Touch support with 10 touch points

The USB drive that I boot from is using VenToy 1.1.4 and has secure boot mode enabled, so I do get to the boot menu. I have tried these ISO files with the same sad result:

  • F44-KDE-x86_64-LIVE-20260513.iso
  • Fedora-KDE-Desktop-Live-44-1.7.x86_64.iso
  • Fedora-Workstation-Live-44-1.7.x86_64.iso

Anyone have any idea why these will not boot successfully?

Thanks!

The kernel panic will have important clues to why this system does not work with linux.
Can you post screen shot of the panic?

Hi Barry and thanks for replying!

There are three screenshots:

  1. Test and start LIVE KDE (2nd menu option)
  2. Start LIVE KDE (1st menu option)
  3. Troubleshoot

The ‘out of memory’ error is perplexing because at that point nothing has started up, but is this a case of memory being protected somehow?

The kernel panic only happens when I choose the Troubleshooting option.

Regards,
Marc



This is an issue we see sporadically with some hardware / firmware - as far as I understand it, at boot time the BIOS has limited access to memory, and in some cases it can’t find big enough contiguous blocks for GRUB.

I’m sure someone with more technical knowledge can make that more precise.

Some things that help in some cases are:

I looked at my BIOS settings and I have neither of the settings you mentioned.

It is interesting that I can test Zorin OS and Mint Cinnamon with no issue from the same USB device.

Is there anything I can add/change in the startup scripts? As a reference point, this is the Test & Start Fedora menu option’s script:

Bit of a shot in the dark but as this thing has integrated graphics, I wonder if it’s getting in the way when the kernel fires up.

I doubt this will make any difference, but trying it is free, which is my favourite cost… edit the kernel params as in your screenshot and add nomodeset to the param list - I’d remove rhgb and quiet, and stick nomodeset in there as your cursor will be in the correct place. Try to boot that with F10 or Ctrl-X

Sadly the change had no effect.

Incidentally, my BIOS is AMI (American Megatrends Inc.) if that makes any difference.

Update:

I have successfully installed Fedora KDE onto my laptop in a (temporary) dual boot configuration with Win11!!

First, thanks to everyone who jumped in to help solve my issue, you all truly make this community awesome!

The solution:

It seems that the Ventoy environment was using up the memory and was not a hardware or BIOS issue at all. I found a similar post here on the forums which described using the Fedora Media Writer to create a bootable KDE LIVE environment on a USB drive. Much to my surprise it worked flawlessly!

Now, I am on my way to becoming completely Windows 11 free.

Long live Linux!!! :heart_eyes: