On Fri, Oct 31, 2014 at 10:37 AM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
On Fri, Oct 31, 2014 at 11:28 AM, Robert Munteanu <robert.munteanu@gmail.com> wrote:
On Fri, Oct 31, 2014 at 10:11 AM, Robert Munteanu <robert.munteanu@gmail.com> wrote:
On Fri, Oct 31, 2014 at 10:08 AM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
On Fri, Oct 31, 2014 at 10:33 AM, Robert Munteanu <robert.munteanu@gmail.com> wrote:
Hi,
I just upgraded from 13.1 to 13.2 using zypper dup. I am running a W520 with encrypted LVM. Bootloader is grub2.
Booting now gets stuck with the message in $SUBJECT. The root/path to initrd are correct, I've verified them with the grub2 console. The linux line correctly contains pci=noacpi, which is required to boot with this laptop.
Keyboard input is still available, as I can press 'Caps Lock' and the corresponding LED lights up or down, but nothing is echoed on the console.
How can I debug/fix the boot process?
Something similar was reported in forums. Edit grub.cfg, add "echo Initrd loaded" after initrd command - this will show whether grub fails to read it or it at least goes further.
I could not find anything in the first pages of
http://forums.opensuse.org/forumdisplay.php/677-Pre-Release-Beta
Do you have a link at hand?
https://forums.opensuse.org/showthread.php/501584-Sort-of-solved-Grub2-UEFI-...
Thanks, I'll take a look but I'm not too optimistic as I don't have UEFI enabled.
Robert
Initrd gets loaded for me.
Then either something wrong happens during handover to kernel or it is stuck when running kernel. Do you have chance to test different kernel version?
I initially tried 3.16.4-9, with 3.16.3.1-1 I get the same behaviour. However (!) I booted the old 3.11.10 kernel and that worked, as in the boot process continued and I could log in to KDE but no network is available. Robert -- http://robert.muntea.nu/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org