[Bug 913996] Applying Critical Updates Causes System to no longer boot (ucode-intel / ucode-amd problem?)
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=913996
--- Comment #102 from Peter Kirchgeßner
Disabling the modules ucode-intel and ucode-amd in the Software Manager was not sufficient to prevent a catatonic system. It is a necessary requirement to include "dis_ucode_ldr" in the kernel parameters at boot time (GRUB2).
I assume that uninstalling ucode-amd is missing to run an mkinitrd. When I install ucode-amd using yast, this takes quite a while to run the mkinitrd for the installed kernels. Uninstalling ucode-amd instead is finished within a second. And the system still hangs after reboot, when dis_ucode_ldr is not used. I have to run an mkinitrd manually to be able to boot without dis_ucode_ldr. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com