The 4.13.x kernels does not boot [closed]
Clash Royale CLAN TAG#URR8PPP up vote
2
down vote
favorite
I have 3 4.13.0 kernels in my Grub menu, -26, -31, -32. None of the boot at all. I am directed back to bios to choose either Windows or the external HDD I have Ubuntu on. However my 4.10.0 -28 works perfect.
I can manage with the old kernel but it is annoying not to be able to use newer kernels.
/ Gunnar
Ps I bit more info about it. I have been working with Ubuntu the last 15-20 years but never had any problem updating. This time my previous HDD broke so I had to buy a new one. Installing Ubuntu from scratch on a new HDD. It took me some time to get it on the disk. Mostly I ended up with black screen. Finally I got it working on a fresh partition. The working image is the first one in Grub. The first installation from the installation Image.
30/1
I am not much of OS guy but what I understand from Grub config file the "non working "images are referenced. Here is a piece of it
menuentry 'Ubuntu, with Linux 4.13.0-32-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.13.0-32-generic-advanced-caff7239-a5be-41cd-a216-a654f23aab5a'
recordfail
savedefault
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
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 caff7239-a5be-41cd-a216-a654f23aab5a
else
search --no-floppy --fs-uuid --set=root caff7239-a5be-41cd-a216-a654f23aab5a
fi
echo 'Loading Linux 4.13.0-32-generic ...'
linux /boot/vmlinuz-4.13.0-32-generic root=UUID=caff7239-a5be-41cd-a216-a654f23aab5a ro
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.13.0-32-generic
menuentry 'Ubuntu, with Linux 4.13.0-32-generic (upstart)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.13.0-32-generic-init-upstart-caff7239-a5be-41cd-a216-a654f23aab5a' {
recordfail
etc
My interpretation is that some how the link between the menu entry and the actual booting piece of code is somehow incorrect.
May be this can help you futher.
/ Gunnar Please tell me how to proceed to get more trace information
boot kernel
asked Jan 27 at 15:59
Gunnar Furugård
19113
closed as off-topic by N0rbert, karel, Eric Carvalho, user364819, muru Feb 3 at 5:08
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – N0rbert, karel, Eric Carvalho, Community, muru
add a comment |Â
up vote
2
down vote
favorite
I have 3 4.13.0 kernels in my Grub menu, -26, -31, -32. None of the boot at all. I am directed back to bios to choose either Windows or the external HDD I have Ubuntu on. However my 4.10.0 -28 works perfect.
I can manage with the old kernel but it is annoying not to be able to use newer kernels.
/ Gunnar
Ps I bit more info about it. I have been working with Ubuntu the last 15-20 years but never had any problem updating. This time my previous HDD broke so I had to buy a new one. Installing Ubuntu from scratch on a new HDD. It took me some time to get it on the disk. Mostly I ended up with black screen. Finally I got it working on a fresh partition. The working image is the first one in Grub. The first installation from the installation Image.
30/1
I am not much of OS guy but what I understand from Grub config file the "non working "images are referenced. Here is a piece of it
menuentry 'Ubuntu, with Linux 4.13.0-32-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.13.0-32-generic-advanced-caff7239-a5be-41cd-a216-a654f23aab5a'
recordfail
savedefault
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
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 caff7239-a5be-41cd-a216-a654f23aab5a
else
search --no-floppy --fs-uuid --set=root caff7239-a5be-41cd-a216-a654f23aab5a
fi
echo 'Loading Linux 4.13.0-32-generic ...'
linux /boot/vmlinuz-4.13.0-32-generic root=UUID=caff7239-a5be-41cd-a216-a654f23aab5a ro
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.13.0-32-generic
menuentry 'Ubuntu, with Linux 4.13.0-32-generic (upstart)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.13.0-32-generic-init-upstart-caff7239-a5be-41cd-a216-a654f23aab5a' {
recordfail
etc
My interpretation is that some how the link between the menu entry and the actual booting piece of code is somehow incorrect.
May be this can help you futher.
/ Gunnar Please tell me how to proceed to get more trace information
boot kernel
asked Jan 27 at 15:59
Gunnar Furugård
19113
closed as off-topic by N0rbert, karel, Eric Carvalho, user364819, muru Feb 3 at 5:08
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – N0rbert, karel, Eric Carvalho, Community, muru
I think you should report bug to launchpad withapport-bug linux. Do your symptoms look like in this 1745118 bugreport, or bug 1742721?
– N0rbert
Jan 27 at 16:20
Well the bug 1742721? seems to have been corrected in -21 And I have got 13.0 -26, -31, -32 in my menu.
– Gunnar Furugård
Jan 30 at 13:11
The other one 1745118 bugreport seems to loop. Mine does not loop. Only falls back to bios .
– Gunnar Furugård
Jan 30 at 13:13
"working with Ubuntu the last 15-20 years" The first Ubuntu was released in 2004.
– fkraiem
Jan 30 at 13:37
Right I'll try to bug report it! Thanks
– Gunnar Furugård
Feb 5 at 14:01
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I have 3 4.13.0 kernels in my Grub menu, -26, -31, -32. None of the boot at all. I am directed back to bios to choose either Windows or the external HDD I have Ubuntu on. However my 4.10.0 -28 works perfect.
I can manage with the old kernel but it is annoying not to be able to use newer kernels.
/ Gunnar
Ps I bit more info about it. I have been working with Ubuntu the last 15-20 years but never had any problem updating. This time my previous HDD broke so I had to buy a new one. Installing Ubuntu from scratch on a new HDD. It took me some time to get it on the disk. Mostly I ended up with black screen. Finally I got it working on a fresh partition. The working image is the first one in Grub. The first installation from the installation Image.
30/1
I am not much of OS guy but what I understand from Grub config file the "non working "images are referenced. Here is a piece of it
menuentry 'Ubuntu, with Linux 4.13.0-32-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.13.0-32-generic-advanced-caff7239-a5be-41cd-a216-a654f23aab5a'
recordfail
savedefault
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
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 caff7239-a5be-41cd-a216-a654f23aab5a
else
search --no-floppy --fs-uuid --set=root caff7239-a5be-41cd-a216-a654f23aab5a
fi
echo 'Loading Linux 4.13.0-32-generic ...'
linux /boot/vmlinuz-4.13.0-32-generic root=UUID=caff7239-a5be-41cd-a216-a654f23aab5a ro
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.13.0-32-generic
menuentry 'Ubuntu, with Linux 4.13.0-32-generic (upstart)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.13.0-32-generic-init-upstart-caff7239-a5be-41cd-a216-a654f23aab5a' {
recordfail
etc
My interpretation is that some how the link between the menu entry and the actual booting piece of code is somehow incorrect.
May be this can help you futher.
/ Gunnar Please tell me how to proceed to get more trace information
boot kernel
asked Jan 27 at 15:59
Gunnar Furugård
19113
I have 3 4.13.0 kernels in my Grub menu, -26, -31, -32. None of the boot at all. I am directed back to bios to choose either Windows or the external HDD I have Ubuntu on. However my 4.10.0 -28 works perfect.
I can manage with the old kernel but it is annoying not to be able to use newer kernels.
/ Gunnar
Ps I bit more info about it. I have been working with Ubuntu the last 15-20 years but never had any problem updating. This time my previous HDD broke so I had to buy a new one. Installing Ubuntu from scratch on a new HDD. It took me some time to get it on the disk. Mostly I ended up with black screen. Finally I got it working on a fresh partition. The working image is the first one in Grub. The first installation from the installation Image.
30/1
I am not much of OS guy but what I understand from Grub config file the "non working "images are referenced. Here is a piece of it
menuentry 'Ubuntu, with Linux 4.13.0-32-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.13.0-32-generic-advanced-caff7239-a5be-41cd-a216-a654f23aab5a'
recordfail
savedefault
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
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 caff7239-a5be-41cd-a216-a654f23aab5a
else
search --no-floppy --fs-uuid --set=root caff7239-a5be-41cd-a216-a654f23aab5a
fi
echo 'Loading Linux 4.13.0-32-generic ...'
linux /boot/vmlinuz-4.13.0-32-generic root=UUID=caff7239-a5be-41cd-a216-a654f23aab5a ro
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.13.0-32-generic
menuentry 'Ubuntu, with Linux 4.13.0-32-generic (upstart)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.13.0-32-generic-init-upstart-caff7239-a5be-41cd-a216-a654f23aab5a' {
recordfail
etc
My interpretation is that some how the link between the menu entry and the actual booting piece of code is somehow incorrect.
May be this can help you futher.
/ Gunnar Please tell me how to proceed to get more trace information
boot kernel
boot kernel
asked Jan 27 at 15:59
Gunnar Furugård
19113
asked Jan 27 at 15:59
Gunnar Furugård
19113
edited Jan 30 at 13:30
asked Jan 27 at 15:59
Gunnar Furugård
19113
asked Jan 27 at 15:59
Gunnar Furugård
19113
asked Jan 27 at 15:59
Gunnar Furugård
19113
19113
closed as off-topic by N0rbert, karel, Eric Carvalho, user364819, muru Feb 3 at 5:08
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – N0rbert, karel, Eric Carvalho, Community, muru
closed as off-topic by N0rbert, karel, Eric Carvalho, user364819, muru Feb 3 at 5:08
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – N0rbert, karel, Eric Carvalho, Community, muru
I think you should report bug to launchpad withapport-bug linux. Do your symptoms look like in this 1745118 bugreport, or bug 1742721?
– N0rbert
Jan 27 at 16:20
Well the bug 1742721? seems to have been corrected in -21 And I have got 13.0 -26, -31, -32 in my menu.
– Gunnar Furugård
Jan 30 at 13:11
The other one 1745118 bugreport seems to loop. Mine does not loop. Only falls back to bios .
– Gunnar Furugård
Jan 30 at 13:13
"working with Ubuntu the last 15-20 years" The first Ubuntu was released in 2004.
– fkraiem
Jan 30 at 13:37
Right I'll try to bug report it! Thanks
– Gunnar Furugård
Feb 5 at 14:01
add a comment |Â
I think you should report bug to launchpad withapport-bug linux. Do your symptoms look like in this 1745118 bugreport, or bug 1742721?
– N0rbert
Jan 27 at 16:20
Well the bug 1742721? seems to have been corrected in -21 And I have got 13.0 -26, -31, -32 in my menu.
– Gunnar Furugård
Jan 30 at 13:11
The other one 1745118 bugreport seems to loop. Mine does not loop. Only falls back to bios .
– Gunnar Furugård
Jan 30 at 13:13
"working with Ubuntu the last 15-20 years" The first Ubuntu was released in 2004.
– fkraiem
Jan 30 at 13:37
Right I'll try to bug report it! Thanks
– Gunnar Furugård
Feb 5 at 14:01
I think you should report bug to launchpad with
apport-bug linux. Do your symptoms look like in this 1745118 bugreport, or bug 1742721?– N0rbert
Jan 27 at 16:20
I think you should report bug to launchpad with
apport-bug linux. Do your symptoms look like in this 1745118 bugreport, or bug 1742721?– N0rbert
Jan 27 at 16:20
Well the bug 1742721? seems to have been corrected in -21 And I have got 13.0 -26, -31, -32 in my menu.
– Gunnar Furugård
Jan 30 at 13:11
Well the bug 1742721? seems to have been corrected in -21 And I have got 13.0 -26, -31, -32 in my menu.
– Gunnar Furugård
Jan 30 at 13:11
The other one 1745118 bugreport seems to loop. Mine does not loop. Only falls back to bios .
– Gunnar Furugård
Jan 30 at 13:13
The other one 1745118 bugreport seems to loop. Mine does not loop. Only falls back to bios .
– Gunnar Furugård
Jan 30 at 13:13
"working with Ubuntu the last 15-20 years" The first Ubuntu was released in 2004.
– fkraiem
Jan 30 at 13:37
"working with Ubuntu the last 15-20 years" The first Ubuntu was released in 2004.
– fkraiem
Jan 30 at 13:37
Right I'll try to bug report it! Thanks
– Gunnar Furugård
Feb 5 at 14:01
Right I'll try to bug report it! Thanks
– Gunnar Furugård
Feb 5 at 14:01
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
I think you should report bug to launchpad with
apport-bug linux. Do your symptoms look like in this 1745118 bugreport, or bug 1742721?– N0rbert
Jan 27 at 16:20
Well the bug 1742721? seems to have been corrected in -21 And I have got 13.0 -26, -31, -32 in my menu.
– Gunnar Furugård
Jan 30 at 13:11
The other one 1745118 bugreport seems to loop. Mine does not loop. Only falls back to bios .
– Gunnar Furugård
Jan 30 at 13:13
"working with Ubuntu the last 15-20 years" The first Ubuntu was released in 2004.
– fkraiem
Jan 30 at 13:37
Right I'll try to bug report it! Thanks
– Gunnar Furugård
Feb 5 at 14:01