Kernel panic after update to kernel generic.efi.signed

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Post Reply
Tnix
Level 1
Level 1
Posts: 30
Joined: Sat Feb 14, 2015 2:29 pm

Kernel panic after update to kernel generic.efi.signed

Post by Tnix »

Hi all,

recently I installed LM 17.1 in my PC MSI AG240 in legacy mode (UEFI install doesn't work) and after run Boot-Repair to get a dual boot with Windows 8.1 in UEFI mode. Everything worked fine and system booted from GRUB by default into LM (the first label was "Ubuntu" and I think the kernel was 3.13.0-37-generic).
As I said everything was fine until the last kernel update to 3.13.0-46. Now when I boot GRUB menu has changed and first entry is labeled "Linux Mint 17.1 Cinnamon 64-bit, 3.13.0-46-generic.efi.signed (/dev/sda4)" but when I choose it throws me "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)". I only boot through "Previous Linux versions" -> "Linux Mint 17.1 Cinnamon 64-bit, 3.13.0-46-generic (/dev/sda4)" or whatever.
I think when I installed LM in legacy mode, setup process detected that there's no UEFI mode and installed a generic kernel. But now when I'm working in UEFI mode, LM update detects it and install a generic.efi.signed kernel by default alongside generic kernel.
Another fact is I can't see any initrd and attached files to vmlinuz-3.13.0-46-generic.efi.signed in /boot but it's true for vmlinuz-3.13.0-46-generic:

Code: Select all

a@a /boot $ ls -lt
total 83276
drwxr-xr-x 5 root root     4096 mar  3 19:41 grub
-rw------- 1 root root  5816408 mar  3 19:41 vmlinuz-3.13.0-46-generic.efi.signed
-rw-r--r-- 1 root root 28859782 mar  3 19:41 initrd.img-3.13.0-46-generic
-rw-r--r-- 1 root root  1164852 mar  2 20:17 abi-3.13.0-46-generic
-rw-r--r-- 1 root root   165748 mar  2 20:17 config-3.13.0-46-generic
-rw------- 1 root root  3389458 mar  2 20:17 System.map-3.13.0-46-generic
-rw------- 1 root root  5814496 mar  2 20:17 vmlinuz-3.13.0-46-generic
-rw-r--r-- 1 root root 28959725 feb 27 21:40 initrd.img-3.13.0-37-generic
drwxr-xr-x 4 root root     4096 feb 27 21:40 grub.bak
-rw-r--r-- 1 root root  5808832 nov 26 23:54 vmlinuz-3.13.0-37-generic
-rw-r--r-- 1 root root  1164489 sep 23 00:24 abi-3.13.0-37-generic
-rw-r--r-- 1 root root   165712 sep 23 00:24 config-3.13.0-37-generic
-rw------- 1 root root  3386945 sep 23 00:24 System.map-3.13.0-37-generic
-rw-r--r-- 1 root root   176500 mar 12  2014 memtest86+.bin
-rw-r--r-- 1 root root   178176 mar 12  2014 memtest86+.elf
-rw-r--r-- 1 root root   178680 mar 12  2014 memtest86+_multiboot.bin
drwxr-xr-x 4 root root     4096 ene  1  1970 efi
How can I boot with the generic.efi.signed kernel without "break" :lol: GRUB/EFI?

Thanks.
User avatar
Pjotr
Level 22
Level 22
Posts: 15930
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland)
Contact:

Re: Kernel panic after update to kernel generic.efi.signed

Post by Pjotr »

Have you tried booting from the original kernel (3.13.0-37)? It should be still there, and it's still bootable then.
Tip: 10 things to do after installing Linux Mint 20 Ulyana
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
Tnix
Level 1
Level 1
Posts: 30
Joined: Sat Feb 14, 2015 2:29 pm

Re: Kernel panic after update to kernel generic.efi.signed

Post by Tnix »

Yes, I boot fine with 3.13.0-37-generic and 3.13.0-46-generic but no with 3.13.0-46-generic.efi.signed.

Next my menuentry sections from /boot/grub/grub.cfg:

Code: Select all

menuentry 'Linux Mint 17.1 Cinnamon 64-bit, 3.13.0-46-generic.efi.signed (/dev/sda4)' --class ubuntu --class gnu-linux --class gnu --class os {
        recordfail
        gfxmode $linux_gfx_mode
        insmod gzio
        insmod part_gpt
        insmod ext2
        set root='hd0,gpt4'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4  2bb86e18-1548-483d-b281-32ebbe9359bc
        else
          search --no-floppy --fs-uuid --set=root 2bb86e18-1548-483d-b281-32ebbe9359bc
        fi
        linux   /boot/vmlinuz-3.13.0-46-generic.efi.signed root=/dev/sda4 ro   quiet splash $vt_handoff
}
menuentry 'Linux Mint 17.1 Cinnamon 64-bit, 3.13.0-46-generic.efi.signed (/dev/sda4) -- recovery mode' --class ubuntu --class gnu-linux --class gnu --class os {
        recordfail
        insmod gzio
        insmod part_gpt
        insmod ext2
        set root='hd0,gpt4'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4  2bb86e18-1548-483d-b281-32ebbe9359bc
        else
          search --no-floppy --fs-uuid --set=root 2bb86e18-1548-483d-b281-32ebbe9359bc
        fi
        echo    'Cargando Linux 3.13.0-46-generic.efi.signed ...'
        linux   /boot/vmlinuz-3.13.0-46-generic.efi.signed root=/dev/sda4 ro recovery nomodeset 
}
submenu "Previous Linux versions" {
menuentry 'Linux Mint 17.1 Cinnamon 64-bit, 3.13.0-46-generic (/dev/sda4)' --class ubuntu --class gnu-linux --class gnu --class os {
        recordfail
        gfxmode $linux_gfx_mode
        insmod gzio
        insmod part_gpt
        insmod ext2
        set root='hd0,gpt4'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4  2bb86e18-1548-483d-b281-32ebbe9359bc
        else
          search --no-floppy --fs-uuid --set=root 2bb86e18-1548-483d-b281-32ebbe9359bc
        fi
        linux   /boot/vmlinuz-3.13.0-46-generic root=UUID=2bb86e18-1548-483d-b281-32ebbe9359bc ro   quiet splash $vt_handoff
        initrd  /boot/initrd.img-3.13.0-46-generic
}
menuentry 'Linux Mint 17.1 Cinnamon 64-bit, 3.13.0-46-generic (/dev/sda4) -- recovery mode' --class ubuntu --class gnu-linux --class gnu --class os {
        recordfail
        insmod gzio
        insmod part_gpt
        insmod ext2
        set root='hd0,gpt4'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4  2bb86e18-1548-483d-b281-32ebbe9359bc
        else
          search --no-floppy --fs-uuid --set=root 2bb86e18-1548-483d-b281-32ebbe9359bc
        fi
        echo    'Cargando Linux 3.13.0-46-generic ...'
        linux   /boot/vmlinuz-3.13.0-46-generic root=UUID=2bb86e18-1548-483d-b281-32ebbe9359bc ro recovery nomodeset 
        echo    'Cargando el disco RAM inicial...'
        initrd  /boot/initrd.img-3.13.0-46-generic
}
menuentry 'Linux Mint 17.1 Cinnamon 64-bit, 3.13.0-37-generic (/dev/sda4)' --class ubuntu --class gnu-linux --class gnu --class os {
        recordfail
        gfxmode $linux_gfx_mode
        insmod gzio
        insmod part_gpt
        insmod ext2
        set root='hd0,gpt4'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4  2bb86e18-1548-483d-b281-32ebbe9359bc
        else
          search --no-floppy --fs-uuid --set=root 2bb86e18-1548-483d-b281-32ebbe9359bc
        fi
        linux   /boot/vmlinuz-3.13.0-37-generic root=UUID=2bb86e18-1548-483d-b281-32ebbe9359bc ro   quiet splash $vt_handoff
        initrd  /boot/initrd.img-3.13.0-37-generic
}
menuentry 'Linux Mint 17.1 Cinnamon 64-bit, 3.13.0-37-generic (/dev/sda4) -- recovery mode' --class ubuntu --class gnu-linux --class gnu --class os {
        recordfail
        insmod gzio
        insmod part_gpt
        insmod ext2
        set root='hd0,gpt4'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4  2bb86e18-1548-483d-b281-32ebbe9359bc
        else
          search --no-floppy --fs-uuid --set=root 2bb86e18-1548-483d-b281-32ebbe9359bc
        fi
        echo    'Cargando Linux 3.13.0-37-generic ...'
        linux   /boot/vmlinuz-3.13.0-37-generic root=UUID=2bb86e18-1548-483d-b281-32ebbe9359bc ro recovery nomodeset 
        echo    'Cargando el disco RAM inicial...'
        initrd  /boot/initrd.img-3.13.0-37-generic
}
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###

### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/25_custom ###

menuentry "Windows UEFI bootmgfw.efi" {
search --fs-uuid --no-floppy --set=root F1BF-8EB0
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
}

menuentry "Windows Boot UEFI loader" {
search --fs-uuid --no-floppy --set=root F1BF-8EB0
chainloader (${root})/EFI/Boot/bootx64.efi
}

menuentry "EFI/ubuntu/MokManager.efi" {
search --fs-uuid --no-floppy --set=root F1BF-8EB0
chainloader (${root})/EFI/ubuntu/MokManager.efi
}

menuentry "EFI/MSI/Boot/bootmgfw.efi" {
search --fs-uuid --no-floppy --set=root F1BF-8EB0
chainloader (${root})/EFI/MSI/Boot/bootmgfw.efi
}
### END /etc/grub.d/25_custom ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (en /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-efi-F1BF-8EB0' {
        insmod part_gpt
        insmod fat
        set root='hd0,gpt1'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  F1BF-8EB0
        else
          search --no-floppy --fs-uuid --set=root F1BF-8EB0
        fi
        chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
set timeout_style=menu
if [ "${timeout}" = 0 ]; then
  set timeout=10
fi
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
menuentry 'System setup' $menuentry_id_option 'uefi-firmware' {
        fwsetup
}
### END /etc/grub.d/30_uefi-firmware ###


User avatar
Pjotr
Level 22
Level 22
Posts: 15930
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland)
Contact:

Re: Kernel panic after update to kernel generic.efi.signed

Post by Pjotr »

Well, then the practical solution is simple: boot from -37, remove -46 and live happily ever after. :)
Tip: 10 things to do after installing Linux Mint 20 Ulyana
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
Tnix
Level 1
Level 1
Posts: 30
Joined: Sat Feb 14, 2015 2:29 pm

Re: Kernel panic after update to kernel generic.efi.signed

Post by Tnix »

Pjotr wrote:Well, then the practical solution is simple: boot from -37, remove -46 and live happily ever after. :)
Of course I said 46-generic boots fine but I want to know if 46-generic.efi.signed is capable to boot.

Thanks.
User avatar
Pjotr
Level 22
Level 22
Posts: 15930
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland)
Contact:

Re: Kernel panic after update to kernel generic.efi.signed

Post by Pjotr »

Tnix wrote:
Pjotr wrote:Well, then the practical solution is simple: boot from -37, remove -46 and live happily ever after. :)
Of course I said 46-generic boots fine but I want to know if 46-generic.efi.signed is capable to boot.

Thanks.
Normally, you don't see this "signed" entry in Grub, in a normal installation on an UEFI machine in full UEFI mode. This is probably caused by Boot Repair doing some Frankenstein stuff to a Grub that was originally installed for an UEFI running in legacy (BIOS) mode. Because you've installed Linux Mint with your machine in legacy mode...

This could turn into a time consuming effort, with real risk of heavy collateral damage to your system. So I advise to ignore this problem and just work around it, as described in my previous message. It's unimportant anyway.... After all, why would you want kernel 3.13.0-46 when 3.13.0-37 is working well on your machine? :mrgreen:
Tip: 10 things to do after installing Linux Mint 20 Ulyana
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
Tnix
Level 1
Level 1
Posts: 30
Joined: Sat Feb 14, 2015 2:29 pm

Re: Kernel panic after update to kernel generic.efi.signed

Post by Tnix »

Hi pjotr,

the problem isn't between 37 and 46 kernel versions but between generic and generic.efi.signed kernel. If I can't solve boot with generic.efi.signed I will put 46-generic in default boot entry in GRUB.
thorbur
Level 1
Level 1
Posts: 10
Joined: Fri Feb 20, 2015 6:59 am

Re: Kernel panic after update to kernel generic.efi.signed

Post by thorbur »

I have the same problem as Tnix on an Thinkpad Edge E130, but without having Windows installed; just still an old Mint 16 installation beside since it has all packets for a project installed.
I also installed Mint in legacy mode, but switching between legacy and uefi doesn't make a change to that problem.

I worked around the problem by just moving the signed kernels from /boot to /root and running "update-grub".
But the signed kernels appear again on every kernel update, thus it is a bit annoying.
One solution would be of course just unmarking the singed kernel to update, but it still feels a bit nasty.
Does anybody know a clean permanent solution to be not bugged by this anymore - uninstalling something, hold signed kernel updates back, etc.? Thanks.

PS: uname -a

Code: Select all

Linux ThinkPad-Edge-E130 3.13.0-52-generic #86-Ubuntu SMP Mon May 4 04:32:59 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
User avatar
JOPETA
Level 17
Level 17
Posts: 7227
Joined: Thu Nov 20, 2014 6:10 am
Location: En un lugar de cuyo nombre no quiero acordarme

Re: Kernel panic after update to kernel generic.efi.signed

Post by JOPETA »

Maybe nasty but It works. Next time when a new update appears in mintupdates window you can right click on it. There's an option to do not show anymore updates of this package or so. Do you notice this kernels come from Canonical? Perhaps it is the problem when trying to boot Mint with it (I do not have problem booting Ubuntu Studio with such kernels only with Mint).
A kernel image for generic. This version of it is signed with Canonical's UEFI signing key.
Any way as Pjotr said there is no reason to update kernels, wherever they come from, when Mint is working flawlessly.
thorbur
Level 1
Level 1
Posts: 10
Joined: Fri Feb 20, 2015 6:59 am

Re: Kernel panic after update to kernel generic.efi.signed

Post by thorbur »

@ Jopeta: Thanks for the hint with the update option. I think this might be the easiest way to get rid of it.
But why shouldn't kernels be updated? Couldn't new kernels include bug and security fixes or performance improvements?
User avatar
JOPETA
Level 17
Level 17
Posts: 7227
Joined: Thu Nov 20, 2014 6:10 am
Location: En un lugar de cuyo nombre no quiero acordarme

Re: Kernel panic after update to kernel generic.efi.signed

Post by JOPETA »

thorbur wrote:But why shouldn't kernels be updated? Couldn't new kernels include bug and security fixes or performance improvements?
I don't know much about this ( there are topics in the forum treating this matter). Look for them and take your own conclusions. Only have to think why are 5th level updates and Mint's good stability/release balanced for me (I'm not an advanced user). In my experience, it is depending on time for wasting. You can try updates/upgrades, different distro ( as I do) trying to getting better. If something goes wrong can go back and uninstall or reinstall if any. If have no time (or knowlege) and everything works smooth...
thorbur
Level 1
Level 1
Posts: 10
Joined: Fri Feb 20, 2015 6:59 am

Re: Kernel panic after update to kernel generic.efi.signed

Post by thorbur »

Unfortunately it turned out that even if I mark the 'linux-signed' package to hold back, it will still be installed by the 'linux' package as dependency -.-
Very annoying.
Any new suggestions how to prevent that piece of broken security?
User avatar
JOPETA
Level 17
Level 17
Posts: 7227
Joined: Thu Nov 20, 2014 6:10 am
Location: En un lugar de cuyo nombre no quiero acordarme

Re: Kernel panic after update to kernel generic.efi.signed

Post by JOPETA »

Why do you need to update the kernel (that is "linux" package) all the time? It is a 5th level update and you don't need when all is working.
nusch
Level 1
Level 1
Posts: 1
Joined: Tue Nov 17, 2015 11:09 am

Re: Kernel panic after update to kernel generic.efi.signed

Post by nusch »

Hello
The problem is with grub and packages like linux-signed-image-xxxxxxx-generic which in opposite to packages linux-image-xxxxxx-generic aren't fully propagated with grub menu entry.
For unsigned images the entry is:
linux /vmlinuz-xxxxxx-generic root=zzzz
initrd yyyyyyy
while for signed it doesn't contain initrd line
linux /vmlinuz-xxxxxx-generic.efi.signed root=zzzz
I reported it few months ago, but if you want this solved confirm by "This bug affects me too" here https://bugs.launchpad.net/linuxmint/+bug/1478188
User avatar
JOPETA
Level 17
Level 17
Posts: 7227
Joined: Thu Nov 20, 2014 6:10 am
Location: En un lugar de cuyo nombre no quiero acordarme

Re: Kernel panic after update to kernel generic.efi.signed

Post by JOPETA »

Even I'm not using signed kernel (couldn't boot with such kernel, so I've never tried it again but I really don't need it neither secure boot) but can confirm there's no init line in GRUB generic.efi.signed menuentry.
Post Reply

Return to “Installation & Boot”