You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
intel-microcode 3.20260210.0ubuntu0.24.04.1 causes hard freeze at boot after "Loading initial ramdisk" (Skylake, ASUS N552VW) #115
Title: intel-microcode 3.20260210.0ubuntu0.24.04.1 causes hard freeze at boot after "Loading initial ramdisk" (Skylake, ASUS N552VW)
Package: intel-microcode 3.20260210.0ubuntu0.24.04.1 (amd64)
Release: Ubuntu 24.04 LTS (noble)
Hardware: ASUS N552VW laptop, CPU: , Intel HD 530 + NVIDIA GTX 960M (Optimus)
BIOS version: <sudo dmidecode -s bios-version>
Microcode revision (when booting without the package): <grep -m1 microcode /proc/cpuinfo>
Summary:
With intel-microcode installed, the system freezes during early boot. The last
screen output is "Loading Linux ..." and "Loading initial ramdisk ...".
After that the screen stays frozen, no keyboard input works, and nothing else
is printed. A forced power-off is required.
Affected kernels:
6.8.0-149-generic
<7.x kernel version> (after upgrading from 6.x to 7.x, the same freeze returned)
Working configurations:
Kernel 5.15.0-122-generic boots normally
GRUB recovery mode boots normally (it adds dis_ucode_ldr and nomodeset)
Normal boot works after: sudo apt remove intel-microcode &&
sudo update-initramfs -u -k all
Kernel parameter dis_ucode_ldr also works around it
Steps to reproduce:
Install intel-microcode 3.20260210.0ubuntu0.24.04.1 on this machine
Run update-initramfs -u -k all
Boot kernel 6.8.0-149 or 7.x normally
System freezes after "Loading initial ramdisk ..."
Expected: system boots normally with the microcode update applied.
Actual: hard freeze in early boot.
Notes:
The freeze occurs before the kernel prints any messages, which is consistent
with the early microcode load from the initramfs.
NVIDIA driver 580.178.04 (DKMS) is installed, but the freeze happens before
it could load, so it appears unrelated.
Earlier microcode package versions did not cause this on kernel 5.15.
Activity