after entering into KDE Plasma, open konsole and provide the output of:
Last boot log:
journalctl -k -b -1 --no-pager
Current bootlog:
journalctl -k --no-pager
The GRUB menu itself does not freeze — I can select entries and edit parameters normally. The freeze happens during the boot process, right after I select a kernel option.
Without acpi=off , the system freezes before reaching the LUKS password prompt.
The docs say it changes the idle states not the number of cores - I read CPU Idle Time Management — The Linux Kernel documentation
Please, provide the outputs of the last and current boot log
Last boot log:
journalctl -k -b -1 --no-pager
Current boot log:
journalctl -k 0 --no-pager
I collected the logs, but they have too many lines. Should I post them here anyway? Can I attach a .txt file with the logs here?
You can post the logs on pastebin.com
But, no you can upload a .txt file as far as i know.
If you need all of those parameters to actually get a booting system, I really do fear for whatever is running as a BIOS.
Do you get any additional information when booting with rhgb and quiet removed from the boot parameters with everything removed apart from the stuff that gets you past the LUKS password?
How did you manage to installed an ISO onto this thing - did you have to add all of that stuff just to get the Live USB to boot?
Others seem to have it working ok.
@dustin0202
You can either post the logs on pastebin.com and provide the pastebin links here
or do CTRL + E and paste the logs in the preformated text
Power supply is certainly a prime suspect given the diverse array of issues. In addition to the PSU, there could be failing components on the system board such as electrolytic capacitors.
@dustin0202
Try this kernel parameter without acpi=off to see if it freezes or not.
selinux=0
if “selinux=0” kernel argument does not work, then boot into the kernel without any extra kernel args and then provide the output of:
journalctl -k -b -1
I only used all those parameters while testing different combinations to find what would get the system past the boot freeze. After several attempts, I discovered that the only parameter actually needed to boot is acpi=off . The others (nomodeset , irqpoll , usbcore.autosuspend=-1 , processor.max_cstate=1 ) were just part of my testing process and are not all required. I’ve also updated the BIOS to the latest version available from Biostar: BIOSTAR: Motherboard Manufacturer
From what I observed during testing, the system freezes before any visible error message appears on screen. There’s no kernel panic or specific error that I can capture — it just hangs.
I only added these kernel parameters after the problem started. Initially, I installed Fedora normally without any issues. The boot parameters were only introduced when my system began freezing during boot.*
So to summarize: the system worked fine initially, the boot freeze started later, and acpi=off is the only parameter that actually gets it past the freeze (though it still leaves me with only 1 CPU core and no graphics acceleration). The BIOS is up to date, and I don’t see any visible error messages when it hangs.
Ahhh - that puts a bit of a different spin on things. When did you install this machine - do you happen to recall which kernel it was (or roughly when you first installed this box)
So you see grub.
Did you try removing rhgb and quiet? It is not clear from your response if you did that.
Here’s what I tested:
-
Booted with only selinux=0 → system froze during boot.
-
Booted with no extra kernel arguments at all → system froze again.
-
Booted with acpi=off (the only parameter that works), got into the system, and ran: sudo journalctl -k -b -1
output:
i remove rhgb and quiet but frozen with no apparent error, i guest frozen before showing it.
sorry the log i post before was incomplete
the full log: new sudo journalctl -k -b -1 - Pastebin.com
You could try replacing the nuclear option of turning all power management off with acpi=off with these in order:
Remove acpi=off and try the following, one by one.
pci=noacpi
acpi=noirq
amd_iommu=off
irqpoll
These are slightly smaller hammers than the sledgehammer of turning everything off and running on one core.