[opensuse-factory] After upgrade from 13.1 boot process is stuck at 'Loading initial ramdisk...'

older
[opensuse-factory] .changes file...

Robert Munteanu

31 Oct 2014 31 Oct '14

07:33

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? Thanks, 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

Show replies by thread

Andrei Borzenkov

31 Oct 31 Oct

08:08

On Fri, Oct 31, 2014 at 10:33 AM, Robert Munteanu 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. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Robert Munteanu

08:11

On Fri, Oct 31, 2014 at 10:08 AM, Andrei Borzenkov wrote:

...

On Fri, Oct 31, 2014 at 10:33 AM, Robert Munteanu 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.

Initrd gets loaded for me. 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

Robert Munteanu

08:28

On Fri, Oct 31, 2014 at 10:11 AM, Robert Munteanu wrote:

...

On Fri, Oct 31, 2014 at 10:08 AM, Andrei Borzenkov wrote:

...
On Fri, Oct 31, 2014 at 10:33 AM, Robert Munteanu 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? Robert

...

Initrd gets loaded for me.

Robert

-- http://robert.muntea.nu/

-- http://robert.muntea.nu/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Andrei Borzenkov

08:37

On Fri, Oct 31, 2014 at 11:28 AM, Robert Munteanu wrote:

...

On Fri, Oct 31, 2014 at 10:11 AM, Robert Munteanu wrote:

...
On Fri, Oct 31, 2014 at 10:08 AM, Andrei Borzenkov wrote:

...
On Fri, Oct 31, 2014 at 10:33 AM, Robert Munteanu 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-...

...

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? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Robert Munteanu

08:43

On Fri, Oct 31, 2014 at 10:37 AM, Andrei Borzenkov wrote:

...

On Fri, Oct 31, 2014 at 11:28 AM, Robert Munteanu wrote:

...
On Fri, Oct 31, 2014 at 10:11 AM, Robert Munteanu wrote:

...
On Fri, Oct 31, 2014 at 10:08 AM, Andrei Borzenkov wrote:

...
On Fri, Oct 31, 2014 at 10:33 AM, Robert Munteanu 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

Robert Munteanu

08:50

On Fri, Oct 31, 2014 at 10:43 AM, Robert Munteanu wrote:

...

On Fri, Oct 31, 2014 at 10:37 AM, Andrei Borzenkov wrote:

...
On Fri, Oct 31, 2014 at 11:28 AM, Robert Munteanu wrote:

...
On Fri, Oct 31, 2014 at 10:11 AM, Robert Munteanu wrote:

...
On Fri, Oct 31, 2014 at 10:08 AM, Andrei Borzenkov wrote:

...
On Fri, Oct 31, 2014 at 10:33 AM, Robert Munteanu 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.

I take that back, network is indeed available now. But the question stands - why don't the new kernel versions work? Does not seem to be a grub2 config problem. Here's what I have for the main entry and the working entry in /boot/grub2/grub.cfg menuentry 'openSUSE 12.3' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-4e9f336c-8bc2-46f8-b209-84bf6e0eab64' { load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' a0f1d3bc-ef4e-44a6-8347-2cc3256a980a else search --no-floppy --fs-uuid --set=root a0f1d3bc-ef4e-44a6-8347-2cc3256a980a fi echo 'Loading Linux 3.16.4-9.g7a8842b-desktop ...' linux /vmlinuz-3.16.4-9.g7a8842b-desktop root=UUID=4e9f336c-8bc2-46f8-b209-84bf6e0eab64 elevator=deadline pci=noacpi resume=/dev/system/swap splash=silent quiet showopts echo 'Loading initial ramdisk ...' initrd /initrd-3.16.4-9.g7a8842b-desktop } menuentry 'openSUSE 12.3, with Linux 3.11.10-21-desktop' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.11.10-21-desktop-advanced-4e9f336c-8bc2-46f8-b209-84bf6e0eab64' { load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' a0f1d3bc-ef4e-44a6-8347-2cc3256a980a else search --no-floppy --fs-uuid --set=root a0f1d3bc-ef4e-44a6-8347-2cc3256a980a fi echo 'Loading Linux 3.11.10-21-desktop ...' linux /vmlinuz-3.11.10-21-desktop root=UUID=4e9f336c-8bc2-46f8-b209-84bf6e0eab64 elevator=deadline pci=noacpi resume=/dev/system/swap splash=silent quiet showopts echo 'Loading initial ramdisk ...' initrd /initrd-3.11.10-21-desktop } Robert

...

Robert

-- http://robert.muntea.nu/

-- http://robert.muntea.nu/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Andrei Borzenkov

09:23

On Fri, Oct 31, 2014 at 11:50 AM, Robert Munteanu wrote:

...

On Fri, Oct 31, 2014 at 10:43 AM, Robert Munteanu wrote:

...
On Fri, Oct 31, 2014 at 10:37 AM, Andrei Borzenkov wrote:

...
On Fri, Oct 31, 2014 at 11:28 AM, Robert Munteanu wrote:

...
On Fri, Oct 31, 2014 at 10:11 AM, Robert Munteanu wrote:

...
On Fri, Oct 31, 2014 at 10:08 AM, Andrei Borzenkov wrote:

...
On Fri, Oct 31, 2014 at 10:33 AM, Robert Munteanu 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.

I take that back, network is indeed available now. But the question stands - why don't the new kernel versions work? Does not seem to be a grub2 config problem. Here's what I have for the main entry and the working entry in /boot/grub2/grub.cfg

menuentry 'openSUSE 12.3' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-4e9f336c-8bc2-46f8-b209-84bf6e0eab64' { load_video set gfxpayload=keep

Could you try disabling graphic in grub (as long as you can boot you can do it using yast) and boot in text mode?

...

insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' a0f1d3bc-ef4e-44a6-8347-2cc3256a980a else search --no-floppy --fs-uuid --set=root a0f1d3bc-ef4e-44a6-8347-2cc3256a980a fi echo 'Loading Linux 3.16.4-9.g7a8842b-desktop ...' linux /vmlinuz-3.16.4-9.g7a8842b-desktop root=UUID=4e9f336c-8bc2-46f8-b209-84bf6e0eab64 elevator=deadline pci=noacpi resume=/dev/system/swap splash=silent quiet showopts echo 'Loading initial ramdisk ...' initrd /initrd-3.16.4-9.g7a8842b-desktop }

menuentry 'openSUSE 12.3, with Linux 3.11.10-21-desktop' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.11.10-21-desktop-advanced-4e9f336c-8bc2-46f8-b209-84bf6e0eab64' { load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' a0f1d3bc-ef4e-44a6-8347-2cc3256a980a else search --no-floppy --fs-uuid --set=root a0f1d3bc-ef4e-44a6-8347-2cc3256a980a fi echo 'Loading Linux 3.11.10-21-desktop ...' linux /vmlinuz-3.11.10-21-desktop root=UUID=4e9f336c-8bc2-46f8-b209-84bf6e0eab64 elevator=deadline pci=noacpi resume=/dev/system/swap splash=silent quiet showopts echo 'Loading initial ramdisk ...' initrd /initrd-3.11.10-21-desktop }

Robert

...
Robert

-- http://robert.muntea.nu/

-- http://robert.muntea.nu/

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Robert Munteanu

09:36

On Fri, Oct 31, 2014 at 11:23 AM, Andrei Borzenkov wrote:

...

On Fri, Oct 31, 2014 at 11:50 AM, Robert Munteanu wrote:

...
On Fri, Oct 31, 2014 at 10:43 AM, Robert Munteanu wrote:

...
On Fri, Oct 31, 2014 at 10:37 AM, Andrei Borzenkov wrote:

...
On Fri, Oct 31, 2014 at 11:28 AM, Robert Munteanu wrote:

...
On Fri, Oct 31, 2014 at 10:11 AM, Robert Munteanu wrote:

...
On Fri, Oct 31, 2014 at 10:08 AM, Andrei Borzenkov wrote: > On Fri, Oct 31, 2014 at 10:33 AM, Robert Munteanu > 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.

I take that back, network is indeed available now. But the question stands - why don't the new kernel versions work? Does not seem to be a grub2 config problem. Here's what I have for the main entry and the working entry in /boot/grub2/grub.cfg

menuentry 'openSUSE 12.3' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-4e9f336c-8bc2-46f8-b209-84bf6e0eab64' { load_video set gfxpayload=keep

Could you try disabling graphic in grub (as long as you can boot you can do it using yast) and boot in text mode?

Bingo! Text mode does the trick, I get a text-only message to enter my passphrase and boot succeeds. Thanks a lot for your help! I guess there's a bug to file here, but I'm not sure against what ... any hints? Robert

...

...
insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' a0f1d3bc-ef4e-44a6-8347-2cc3256a980a else search --no-floppy --fs-uuid --set=root a0f1d3bc-ef4e-44a6-8347-2cc3256a980a fi echo 'Loading Linux 3.16.4-9.g7a8842b-desktop ...' linux /vmlinuz-3.16.4-9.g7a8842b-desktop root=UUID=4e9f336c-8bc2-46f8-b209-84bf6e0eab64 elevator=deadline pci=noacpi resume=/dev/system/swap splash=silent quiet showopts echo 'Loading initial ramdisk ...' initrd /initrd-3.16.4-9.g7a8842b-desktop }

menuentry 'openSUSE 12.3, with Linux 3.11.10-21-desktop' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.11.10-21-desktop-advanced-4e9f336c-8bc2-46f8-b209-84bf6e0eab64' { load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' a0f1d3bc-ef4e-44a6-8347-2cc3256a980a else search --no-floppy --fs-uuid --set=root a0f1d3bc-ef4e-44a6-8347-2cc3256a980a fi echo 'Loading Linux 3.11.10-21-desktop ...' linux /vmlinuz-3.11.10-21-desktop root=UUID=4e9f336c-8bc2-46f8-b209-84bf6e0eab64 elevator=deadline pci=noacpi resume=/dev/system/swap splash=silent quiet showopts echo 'Loading initial ramdisk ...' initrd /initrd-3.11.10-21-desktop }

Robert

...
Robert

-- http://robert.muntea.nu/

-- http://robert.muntea.nu/

-- http://robert.muntea.nu/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Andrei Borzenkov

10:20

On Fri, Oct 31, 2014 at 12:36 PM, Robert Munteanu wrote:

...

...
...
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,

...

...
...
set gfxpayload=keep

Could you try disabling graphic in grub (as long as you can boot you can do it using yast) and boot in text mode?

Bingo! Text mode does the trick, I get a text-only message to enter my passphrase and boot succeeds. Thanks a lot for your help!

I guess there's a bug to file here, but I'm not sure against what ... any hints?

I tentatively suggest that if previous kernel works under the same conditions this is kernel issue. I remember patch for grub posted on grub-devel recently that disables graphic handover (thus forcing kernel to start in text mode), but it looks more like a workaround. Anyway, Cc'ing opensuse-kernel seems appropriate as first step here ... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

3459

Age (days ago)

3459

Last active (days ago)

List overview

Download

9 comments

2 participants

participants (2)

Andrei Borzenkov
Robert Munteanu

[opensuse-factory] After upgrade from 13.1 boot process is stuck at 'Loading initial ramdisk...'

tags

participants (2)