dustin0202
June 26, 2026, 11:20am
1
Problem: My Fedora system won’t boot. It freezes at the GRUB menu regardless of which kernel I select. I managed to get it working with the following kernel parameters:
acpi=off irqpoll usbcore.autosuspend=-1 nomodeset processor.max_cstate=1
But this isn’t a permanent solution because:
Video resolution is stuck at 1024x768
System is laggy and slow
Power management is broken (CPU stuck at full speed)
It crashes/hangs on shutdown
What I’ve already tried:
Updated GRUB config to make the working parameters permanent (temporary fix)
Updated system packages (kernel, firmware, etc.) via sudo dnf update
Updated BIOS to latest version
Tried alternative parameters:
acpi=noirq / pci=noacpi / noapic (crashed)amdgpu.dc=0 / modprobe.blacklist=amdgpu (didn’t help)iommu=off / pci=nommconf (crashed)
What the logs show (journalctl):
/dev/sda (HDD 1TB) has persistent I/O errors:ata1.00: exception Emask 0x10 SAct 0x2400140 SErr 0x40d0002 action 0xe frozen
I/O error, dev sda, sector 1950530592 op 0x0:(READ) flags 0x80700 phys_seg 20 prio class 2
/dev/sdc has 8 pending/uncorrectable sectorsamdgpu fails to initialize:libEGL warning: failed to get driver name for fd -1
MESA: error: ZINK: failed to choose pdev
ACPI errors detected:ACPI: Interpreter disabled
APIC: ACPI MADT or MP tables are not detected
TSC clocksource instability warnings:clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable
My goal: Boot without acpi=off and without nomodeset to get proper graphics acceleration and power management.
Any suggestions? Could the failing HDD be causing the boot freezes even though the system is installed on the SSD (/dev/sdb)? Is there a way to disable the faulty HDD temporarily just to test? Or is this purely an ACPI/GPU firmware issue that needs a BIOS update?
Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.0
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1
Kernel Version: 7.0.12-201.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processor: 1 × AMD Ryzen 5 3350G with Radeon Vega Graphics
Memory: 16 GiB of RAM (5.7 GiB usable)
Graphics Processor: llvmpipe
Manufacturer: BIOSTAR Group
Product Name: A320MH
Please post the output of inxi -Fzxx (you will have to install inxi) as it will give us a lot more details on your hardware.
Can you remove any of the kernel command line options you added?
dustin0202
June 26, 2026, 11:40am
3
Yes, currently they are all strictly necessary for the system to boot at all. Without acpi=off, it freezes before reaching the LUKS password prompt. Without nomodeset, it freezes during the amdgpu initialization. I tried replacing them with specific alternatives like amdgpu.dc=0, pci=noacpi, and iommu=off, but they either caused different kernel panics or froze at the same spot. processor.max_cstate=1 is the only reason it doesn’t reboot itself after entering the password with acpi=off.
Output of “inxi -Fzxx”:
System:
Kernel: 7.0.12-201.fc44.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
Desktop: KDE Plasma v: 6.7.0 tk: Qt v: N/A wm: kwin_wayland dm: N/A
Distro: Fedora Linux 44 (KDE Plasma Desktop Edition)
Machine:
Type: Desktop Mobo: BIOSTAR model: A320MH serial: <superuser required>
Firmware: UEFI vendor: American Megatrends LLC. v: 5.17 date: 08/31/2025
CPU:
Info: single core model: AMD Ryzen 5 3350G with Radeon Vega Graphics
bits: 64 type: UP arch: Zen/Zen+ note: check rev: 1 cache: L1: 96 KiB
L2: 512 KiB L3: 4 MiB
Speed (MHz): 3893 min/max: N/A core: 1: 3893 bogomips: 7186
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
ssse3 svm
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Picasso/Raven 2 [Radeon Vega
Series / Radeon Mobile Series] vendor: Biostar Microtech Intl Corp
driver: N/A arch: GCN-5 pcie: speed: 8 GT/s lanes: 16 bus-ID: 08:00.0
chip-ID: 1002:15d8
Display: wayland server: Xwayland v: 24.1.12 compositor: kwin_wayland
driver: N/A display-ID: 0
Monitor-1: Unknown-1 res: 1024x768 hz: 60 dpi: 96 diag: 338mm (13.3")
API: EGL v: 1.5 platforms: device: 0 drv: swrast surfaceless: drv: swrast
wayland: drv: swrast x11: drv: swrast inactive: gbm
API: OpenGL v: 4.6 vendor: mesa v: 26.1.3 glx-v: 1.4 direct-render: yes
renderer: llvmpipe (LLVM 22.1.7 256 bits) device-ID: ffffffff:ffffffff
display-ID: :0.0
API: Vulkan v: 1.4.341 surfaces: N/A device: 0 type: cpu
driver: mesa llvmpipe device-ID: 10005:0000
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: amdgpu_top wl: wayland-info
x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP
Audio driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
bus-ID: 08:00.1 chip-ID: 1002:15de
Device-2: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: Biostar
Microtech Intl Corp driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s
lanes: 16 bus-ID: 08:00.6 chip-ID: 1022:15e3
API: ALSA v: k7.0.12-201.fc44.x86_64 status: kernel-api
Server-1: PipeWire v: 1.6.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Biostar Microtech Intl Corp driver: r8169 v: kernel pcie:
speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 03:00.0 chip-ID: 10ec:8168
IF: enp3s0 state: down mac: <filter>
Device-2: Realtek RTL8192EE PCIe Wireless Network Adapter
driver: rtl8192ee v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e000
bus-ID: 07:00.0 chip-ID: 10ec:818b
IF: wlp7s0 state: up mac: <filter>
IF-ID-1: docker0 state: down mac: <filter>
IF-ID-2: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Drives:
Local Storage: total: 2.08 TiB used: 197.61 GiB (9.3%)
ID-1: /dev/sda vendor: Western Digital model: WD10SPZX-75Z10T3
size: 931.51 GiB speed: 3.0 Gb/s serial: <filter> temp: 31 C
ID-2: /dev/sdb vendor: Pichau model: PG256X size: 238.47 GiB
speed: 6.0 Gb/s serial: <filter> temp: 48 C
ID-3: /dev/sdc vendor: Seagate model: ST1000LM035-1RK172 size: 931.51 GiB
speed: 6.0 Gb/s serial: <filter> temp: 29 C
ID-4: /dev/sdd model: N/A size: 29.42 GiB type: USB rev: 2.0 spd: 480 Mb/s
lanes: 1 serial: <filter>
Partition:
ID-1: / size: 235.87 GiB used: 196.97 GiB (83.5%) fs: btrfs dev: /dev/dm-0
mapped: luks-38d1b7e1-6b04-490d-a36f-5ef5a77af739
ID-2: /boot size: 1.9 GiB used: 632 MiB (32.5%) fs: ext4 dev: /dev/sdb2
ID-3: /boot/efi size: 598.8 MiB used: 20 MiB (3.3%) fs: vfat
dev: /dev/sdb1
ID-4: /home size: 235.87 GiB used: 196.97 GiB (83.5%) fs: btrfs
dev: /dev/dm-0 mapped: luks-38d1b7e1-6b04-490d-a36f-5ef5a77af739
Swap:
ID-1: swap-1 type: zram size: 5.72 GiB used: 1.1 GiB (19.3%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 44.8 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 6 GiB available: 5.72 GiB used: 3.64 GiB (63.7%)
Processes: 264 Power: uptime: 52m wakeups: 0 Init: systemd v: 259
default: graphical
Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 58
Compilers: gcc: 16.1.1 Shell: Bash v: 5.3.9 running-in: konsole inxi: 3.3.40
Luiz Eduardo Araujo Brayner:
/dev/sda (HDD 1TB) has persistent I/O errors:
ata1.00: exception Emask 0x10 SAct 0x2400140 SErr 0x40d0002 action 0xe frozen
I/O error, dev sda, sector 1950530592 op 0x0:(READ) flags 0x80700 phys_seg 20 prio class 2
Failing hardware seems likely.
pg-tips
June 26, 2026, 11:57am
5
Don’t know if it’s related to the problem, but that output is a bit weird.
That’s a 4C/8T processor so you would expect to see 8 x there, rather than 1 x.
And similarly, inxi is reporting it as single core:
CPU:
Info: single core model: AMD Ryzen 5 3350G with Radeon Vega Graphics
bits: 64 type: UP arch: Zen/Zen+ note: check rev: 1 cache: L1: 96 KiB
L2: 512 KiB L3: 4 MiB
Speed (MHz): 3893 min/max: N/A core: 1: 3893 bogomips: 7186
dustin0202
June 26, 2026, 12:09pm
7
lscpu output:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 43 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 1
On-line CPU(s) list: 0
Vendor ID: AuthenticAMD
Model name: AMD Ryzen 5 3350G with Radeon Vega Graphics
CPU family: 23
Model: 24
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
Stepping: 1
BogoMIPS: 7186,31
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush m
mx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep
_good nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ss
se3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_leg
acy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tc
e topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate ssbd ibp
b vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt
xsavec xgetbv1 clzero xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb
_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgi
f overflow_recov succor smca sev sev_es
Virtualization features:
Virtualization: AMD-V
Caches (sum of all):
L1d: 32 KiB (1 instance)
L1i: 64 KiB (1 instance)
L2: 512 KiB (1 instance)
L3: 4 MiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0
Vulnerabilities:
Gather data sampling: Not affected
Ghostwrite: Not affected
Indirect target selection: Not affected
Itlb multihit: Not affected
L1tf: Not affected
Mds: Not affected
Meltdown: Not affected
Mmio stale data: Not affected
Old microcode: Not affected
Reg file data sampling: Not affected
Retbleed: Mitigation; untrained return thunk; SMT disabled
Spec rstack overflow: Mitigation; SMT disabled
Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2: Mitigation; Retpolines; IBPB conditional; STIBP disabled; RSB filling; PBRSB-eIBR
S Not affected; BHI Not affected
Srbds: Not affected
Tsa: Not affected
Tsx async abort: Not affected
Vmscape: Mitigation; IBPB before exit to userspace
dustin0202
June 26, 2026, 12:13pm
8
I think it’s because of the acpi=off parameter.
As @pg-tips said it odd that you have only 1 CPU core on line.
Your hardware seem really broken.
Can you boot a live USB image and see if it shows you hardware working?
pg-tips
June 26, 2026, 12:16pm
10
Haven’t tried this myself, but looks like libata.force on the kernel command line might achieve this (search in the docs for the syntax).
I would physically unplug the drive from the system. No way to know what harm it is doing.
But make sure you remove that drive from /etc/fstab or the system will fail to boot when it is removed.
If you have not done so set a root passwd so that you can login to emergency mode if that becomes required.
dustin0202
June 26, 2026, 1:10pm
13
I really don’t want to do this, but would it be worth reinstalling Fedora from scratch (wiping all data) to see if it fixes the issue? I know it’s drastic, but at this point it’s better than not being able to use the computer at all.
I’m not optimistic—but I’m running out of ideas.
Before installing from scratch try the nuclear reinstall option:sudo dnf reinstall \*
I think you have more hardware issues the the HDD failing.
Given the live image still shows 1 CPU there is something badly wrong.
I’d be thinking power supply issues?
It could be old firmware on the motherboard maybe?
What does the BIOS think is your hardware?
dustin0202
June 26, 2026, 1:38pm
17
the bios looks like recognize the cpu 4 cores
acpi=off irqpoll usbcore.autosuspend=-1 nomodeset processor.max_cstate=1
You added “processor.max_cstate=1” to kernel arguments which limits to only 1 cpu core
@dustin0202
dustin0202
June 26, 2026, 1:48pm
20
I don’t think that’s the case. I’ve tested it, and processor.max_cstate=1 was never required to get past the boot freeze. The only parameter that makes any difference is acpi=off — without it, the system freezes regardless of whether processor.max_cstate=1 is present or not.
Also, the live USB (which has no processor.max_cstate=1 ) still shows only 1 CPU core and requires acpi=off to boot.