I am trying to install Leap 42.1 from DVD on a 6-year-old Toshiba laptop with a 64-bit AMD chip. When installation is completed and the machine automatically reboots, I get the messages
Loading Linux 4.1.12-1-default
Loading initial ramdisk …
and it does not advance past this point. Initially I tried to select the XFCE interface, and when this failed, I tried KDE. Both give the same result. I am trying to install into 215 Gb of disk space.
Run the media check from the install DVD
Make sure the DVD is good
In bootloader menu press ‘e’ on menu entry and remove “splash=silent” and “quiet” from line starting with linux (or linuxef). Press F10 to boot. It may give more verbose output.
I did run the media check and the disk was fine.
As you have suggested, arvidjaar, I edited the Linux command in the boot procedure to remove “quiet” and “splash=silent”. No more information is given. There is an initial line “Booting a command list” before the two “loading” messages and then silence.
Try adding “dis_ucode_ldr” to the kernel command line in the same way instead.
You can also try adding earlyprintk=vga or earlyprintk=efi (depending on whether you are booting legacy BIOS or EFI). It may show something.
If all the above fails you can try also to boot like so
In the grub2 login screen press “e”, at the end of the kernel lines add the word
single
then if your machine is successful in reaching the single-user mode.
Type your root password then type the command
journalctl -xb
to see the logs.
Maybe you can post it here and those expert in grub2 will be able to give you an advice.
That has got me going, thanks.
I have installed a basic editor and done a “zypper up”. On rebooting, I find that I still have to add the “dis_ucode_ldr” to successfully boot. Should I add this permanently to the boot script? I have placed the output from “dmesg” on my website, and also the output from “journalctl -xb” in case someone can identify a different solution. **
That, or uninstall ucode-amd.
According to 913996 – Applying Critical Updates Causes System to no longer boot (ucode-intel / ucode-amd problem?) a fix should be in the next kernel update…
If not, you should consider reopening the bug report.
I have no idea when that will be released though.
I have issued the command
zypper rm ucode-amd
and then in YaST made the change permanent through YaST->System->Boot Loader. This seems to have been a bad idea. I can no longer boot the machine to Linux. It stops at “Loading initial ramdisk…”, even if I have added “dis_ucode_ldr” to the Linux line during boot.
Will I have to reinstall everything to overcome this problem?
Hm, to my knowledge it should work when you uninstall that, and I don’t see why “dis_ucode_ldr” wouldn’t work any more either.
Will I have to reinstall everything to overcome this problem?
Does it maybe work if you try to boot an older kernel in “Advanced Options”?
If you use btrfs, you should also be able to boot a different snapshot and revert back.
Otherwise, you’d have to boot from a Live or installation CD/DVD, switch to your system and maybe reinstall ucode-amd.
Or reinstall, an “Upgrade” should work too and not lose any installed packages.