Cannot load latest kernels

[Qqmike]

Until it gets fixed, people can always use their GRUB. Simply boot into Kubuntu (somehow), and issue the command
sudo grub-install
and that will place GRUB at the top of your UEFI boot list (check it using sudo efibootmgr). I'm sure you know this Rod J, just posting it for others who may bounce here.
After the kernel thing gets fixed, you can boot into Kubuntu and use sudo efibootmgr -o to change the BootOrder and put rEFInd back to the top of the boot list. See man efibootmgr -- scroll down to very end where they illustrate the -o switch.

[Rod J]

Until it gets fixed, people can always use their GRUB. Simply boot into Kubuntu (somehow), and issue the command
sudo grub-install
and that will place GRUB at the top of your UEFI boot list (check it using sudo efibootmgr). I'm sure you know this Rod J, just posting it for others who may bounce here.
After the kernel thing gets fixed, you can boot into Kubuntu and use sudo efibootmgr -o to change the BootOrder and put rEFInd back to the top of the boot list. See man efibootmgr -- scroll down to very end where they illustrate the -o switch.

I'm still booting via rEFInd but it points to Grub2 (which I still have installed as a backup booting method) instead of booting the kernel directly. rEFInd works fine that way

There's a simpler method of making sure rEFInd is at the top of the EFI boot order ... there's a little utility that comes with rEFInd called refind-mkdefault. Just execute sudo refind-mkdefault in a terminal.

[Qqmike]

I'm still booting via rEFInd but it points to Grub2

Yep, me too :-) In doing the how-to's and all my experimenting, I now have 12 partitions which include 3 ESPs. My rEFInd menu has many entries, I think 27 or something like that.

There's a simpler method of making sure rEFInd is at the top of the EFI boot order ... there's a little utility that comes with rEFInd called refind-mkdefault. Just execute sudo refind-mkdefault in a terminal.

Thanks for that tip, I've never used it. Just checked, and I don't have refind-mkedefault installed; I must have missed that along the way.

[Qqmike]

@Rod J ... I see now, refind-mkdefault is already included in the installed files for rEFInd (in /usr/sbin). I ran it, and, indeed, it did place rEFInd first in BootOrder. Thanks.

[Rod J]

I just installed the latest 3.13 kernel (3.13.0-106) which was in the list of updates today and it also fails to boot with rEFInd returning the original error message. I was hopeful that it might have worked but then I remembered that Rod Smith already tried 106 and reported that it failed here.

There doesn't seem to be any more news on progress with the problem and as there are still only three people registered on that bug report page ("This bug affects you and 2 other people") maybe it's a lost cause? I guess most people running K14.04 with the 3.13 kernel are just booting via grub and haven't been affected by it.

[Qqmike]

I didn't get the -106 update yet, probably will tomorrow. Yeah, looks like no changes yet in the bug thread. It is "confirmed" and has "High importance." What does that mean? Sounds like it should get some attention. Seems like with all the talk about UEFI and going grubless and booting by stub loader, that they would take this seriously. rEFInd depends on it. I know SteveRiley went Grubless using only the stub loader (perhaps through rEFInd or directly, not sure, but either way it is important that the stub loader works).

[Qqmike]

No-go on the vmlinux-3.13.0-106 kernel -- could not boot it directly by the stub loader method using UEFI firmware.

Tried to create a new NVRAM variable for it and boot it -- no go.
Tried to use my firmware boot override menu to boot it -- no go.
Tried to let rEFInd boot it directly -- no go.

Btw ... talk about my setup ...

My ESP is sda1 and is 500 MB in size, but it is using just 199 MB:

mike@mike-desktop:/boot/efi/EFI$ df -hT

Filesystem     Type      Size  Used Avail Use% Mounted on
...
/dev/sda1      vfat      500M  [B]199M[/B]  301M  40% /boot/efi
...

But look what's in it! Including my test subdirectory, /boot/efi/EFI/StubL (scroll down to see it, in bold-red), which now contains all the kernel files (and related) for five kernels. Plus all my other stuff in my ESP, 16 directories, 186 files (this is the output of the tree command):

mike@mike-desktop:/boot/efi/EFI$ [B]tree[/B]
.
├── debian
│   └── grubx64.efi
├── grub_sda5K1504
│   ├── grub.cfg
│   ├── grubx64.efi
│   ├── MokManager.efi
│   └── shimx64.efi
├── Mint_1
│   ├── grub.cfg
│   ├── grubx64.efi
│   ├── MokManager.efi
│   └── shimx64.efi
├── Mint_2
│   └── grubx64.efi
├── my_Backups_7-4-15
│   ├── grub.cfg
│   ├── grubx64.efi
│   ├── MokManager.efi
│   └── shimx64.efi
├── NotNeeded_ubuntu
│   ├── grub.cfg
│   ├── grubx64.efi
│   ├── MokManager.efi
│   └── shimx64.efi
├── refind
│   ├── drivers_x64
│   │   └── ext4_x64.efi
│   ├── icons
│   │   ├── arrow_left.png
│   │   ├── arrow_right.png
│   │   ├── boot_linux.png
│   │   ├── boot_win.png
│   │   ├── func_about.png
│   │   ├── func_csr_rotate.png
│   │   ├── func_exit.png
│   │   ├── func_firmware.png
│   │   ├── func_reset.png
│   │   ├── func_shutdown.png
│   │   ├── os_arch.png
│   │   ├── os_centos.png
│   │   ├── os_chakra.png
│   │   ├── os_chrome.png
│   │   ├── os_clover.png
│   │   ├── os_crunchbang.png
│   │   ├── os_debian.png
│   │   ├── os_elementary.png
│   │   ├── os_fedora.png
│   │   ├── os_freebsd.png
│   │   ├── os_frugalware.png
│   │   ├── os_gentoo.png
│   │   ├── os_gummiboot.png
│   │   ├── os_haiku.png
│   │   ├── os_hwtest.png
│   │   ├── os_kubuntu.png
│   │   ├── os_legacy.png
│   │   ├── os_linuxmint.png
│   │   ├── os_linux.png
│   │   ├── os_lubuntu.png
│   │   ├── os_mac.png
│   │   ├── os_mageia.png
│   │   ├── os_mandriva.png
│   │   ├── os_netbsd.png
│   │   ├── os_network.png
│   │   ├── os_opensuse.png
│   │   ├── os_redhat.png
│   │   ├── os_refind.png
│   │   ├── os_refit.png
│   │   ├── os_slackware.png
│   │   ├── os_suse.png
│   │   ├── os_ubuntu.png
│   │   ├── os_unknown.png
│   │   ├── os_win8.png
│   │   ├── os_win.png
│   │   ├── os_xubuntu.png
│   │   ├── README
│   │   ├── tool_apple_rescue.png
│   │   ├── tool_fwupdate.png
│   │   ├── tool_memtest.png
│   │   ├── tool_mok_tool.png
│   │   ├── tool_netboot.png
│   │   ├── tool_part.png
│   │   ├── tool_rescue.png
│   │   ├── tool_shell.png
│   │   ├── tool_windows_rescue.png
│   │   ├── transparent.png
│   │   ├── vol_external.png
│   │   ├── vol_internal.png
│   │   ├── vol_net.png
│   │   └── vol_optical.png
│   ├── icons-backup
│   │   ├── arrow_left.png
│   │   ├── arrow_right.png
│   │   ├── boot_linux.png
│   │   ├── boot_win.png
│   │   ├── func_about.png
│   │   ├── func_csr_rotate.png
│   │   ├── func_exit.png
│   │   ├── func_firmware.png
│   │   ├── func_reset.png
│   │   ├── func_shutdown.png
│   │   ├── os_arch.png
│   │   ├── os_centos.png
│   │   ├── os_chakra.png
│   │   ├── os_chrome.png
│   │   ├── os_clover.png
│   │   ├── os_crunchbang.png
│   │   ├── os_debian.png
│   │   ├── os_elementary.png
│   │   ├── os_fedora.png
│   │   ├── os_freebsd.png
│   │   ├── os_frugalware.png
│   │   ├── os_gentoo.png
│   │   ├── os_gummiboot.png
│   │   ├── os_haiku.png
│   │   ├── os_hwtest.png
│   │   ├── os_kubuntu.png
│   │   ├── os_legacy.png
│   │   ├── os_linuxmint.png
│   │   ├── os_linux.png
│   │   ├── os_lubuntu.png
│   │   ├── os_mac.png
│   │   ├── os_mageia.png
│   │   ├── os_mandriva.png
│   │   ├── os_netbsd.png
│   │   ├── os_network.png
│   │   ├── os_opensuse.png
│   │   ├── os_redhat.png
│   │   ├── os_refind.png
│   │   ├── os_refit.png
│   │   ├── os_slackware.png
│   │   ├── os_suse.png
│   │   ├── os_ubuntu.png
│   │   ├── os_unknown.png
│   │   ├── os_win8.png
│   │   ├── os_win.png
│   │   ├── os_xubuntu.png
│   │   ├── README
│   │   ├── tool_apple_rescue.png
│   │   ├── tool_fwupdate.png
│   │   ├── tool_memtest.png
│   │   ├── tool_mok_tool.png
│   │   ├── tool_netboot.png
│   │   ├── tool_part.png
│   │   ├── tool_rescue.png
│   │   ├── tool_shell.png
│   │   ├── tool_windows_rescue.png
│   │   ├── transparent.png
│   │   ├── vol_external.png
│   │   ├── vol_internal.png
│   │   ├── vol_net.png
│   │   └── vol_optical.png
│   ├── keys
│   │   ├── altlinux.cer
│   │   ├── canonical-uefi-ca.der
│   │   ├── centos.cer
│   │   ├── fedora-ca.cer
│   │   ├── microsoft-kekca-public.der
│   │   ├── microsoft-pca-public.der
│   │   ├── microsoft-uefica-public.der
│   │   ├── openSUSE-UEFI-CA-Certificate-4096.cer
│   │   ├── openSUSE-UEFI-CA-Certificate.cer
│   │   ├── refind.cer
│   │   ├── refind_local.cer
│   │   ├── refind_local.crt
│   │   └── SLES-UEFI-CA-Certificate.cer
│   ├── refind.conf
│   ├── refind.conf-sample
│   └── refind_x64.efi
├── [B][COLOR=#ff0000]StubL[/COLOR][/B]
│   ├── abi-3.13.0-100-generic
│   ├── abi-3.13.0-101-generic
│   ├── abi-3.13.0-103-generic
│   ├── abi-3.13.0-105-generic
│   ├── abi-3.13.0-106-generic
│   ├── config-3.13.0-100-generic
│   ├── config-3.13.0-101-generic
│   ├── config-3.13.0-103-generic
│   ├── config-3.13.0-105-generic
│   ├── config-3.13.0-106-generic
│   ├── initrd.img-3.13.0-100-generic
│   ├── initrd.img-3.13.0-101-generic
│   ├── initrd.img-3.13.0-103-generic
│   ├── initrd.img-3.13.0-105-generic
│   ├── initrd.img-3.13.0-106-generic
│   ├── System.map-3.13.0-100-generic
│   ├── System.map-3.13.0-101-generic
│   ├── System.map-3.13.0-103-generic
│   ├── System.map-3.13.0-105-generic
│   ├── System.map-3.13.0-106-generic
│   ├── vmlinuz-3.13.0-100-gen.efi
│   ├── vmlinuz-3.13.0-101-gen.efi
│   ├── vmlinuz-3.13.0-103-gen.efi
│   ├── vmlinuz-3.13.0-105-gen.efi
│   └── vmlinuz-3.13.0-106-generic.efi.signed
├── TestMint_sda8
│   └── grubx64.efi
├── tools
└── ubuntu
 ├── fw
 ├── fwupx64.efi
 ├── grub.cfg
 └── grubx64.efi

16 directories, 186 files

So what? So it tells you that making your ESP on the small side, at say 100 MB, could be too small. I make mine 500 MB. It also shows that you can pack a lot of boot files in an ESP that is 500 MB!

Too bad about this boot failure on the stub loader. I hope they fix it. I use GRUB, but I like to have the option of stub loading for backup/rescue and for experimenting.

[Qqmike]

No-go on the vmlinux-3.13.0-107 kernel -- could not boot it directly by the stub loader method using UEFI firmware.

Tried to create a new NVRAM variable for it and boot it -- no go.
Tried to use my firmware boot override menu to boot it -- no go.
Tried to let rEFInd boot it directly -- no go.

Well, shucks, huh?

[Rod J]

No-go on the vmlinux-3.13.0-107 kernel -- could not boot it directly by the stub loader method using UEFI firmware.

I updated to kernel 3.13.0-107 generic yesterday and I can confirm it still doesn't boot via rEFInd with the same error message as in post #1: "Error: Load error while loading ..."

It's nothing if not consistent I guess!

[Qqmike]

Thanks for checking on this, Rod J. Yep, I get that same error mess[age], too. I'll bet we are not as disappointed as Rod Smith might be, with his rEFInd depending on this kernel feature. Future kernels, as Rod Smith has pointed out, don't have this problem, so all is well there. Just have to adjust things while using 14.04. I've got GRUB installed, so for me, it's OK. And, fact is, you can always get booted somehow, even if using a live Boot-Repair disk to get some GRUB for you. Or, boot into an older kernel. Etc. As you know.

I guess I'm saying that it doesn't destroy the experience of using 14.04.

[Rod J]

I guess I'm saying that it doesn't destroy the experience of using 14.04.

Same here, this is just a minor hiccup ... K14.04 rocks!

[Qqmike]

Same here, this is just a minor hiccup ... K14.04 rocks!

I agree! Keeping life simple ... :-)

[Guest]

Just a quick "me too". I'm running 14.04 and refind on a macbook, exactly the same behaviour as everyone else has reported here, stuck on the .100 kernel.

[GKNByNW]

Apologies for resurrecting this old thread but after months of running the -100 kernel and waiting for a possible fix, I finally broke down and installed the 4.4 kernels via "sudo apt-get install linux-generic-lts-xenial" and as others (including Rod Smith himself) have reported, it works fine with rEFInd. However, rEFInd still automatically selects the 3.13 kernels, requiring me to hit F2 and scroll up to the 4.4 kernel at every boot. Is it possible to entirely remove the trusty kernel/header/image so that I can use only 4.4 from now on? I've tried the obvious like "sudo apt-get autoremove" and "sudo apt-get remove linux-generic-lts-trusty && sudo apt-get purge linux-generic-lts-trusty" but with no luck.

So... is what I want doable? Am I missing something stupidly obvious like not getting the correct package name? It's 2:30am here & my brain's half melted from fatigue, so it's probably something really simple that I'm gonna kick myself for later.

[GreyGeek]

You're probably not getting the name spelled exactly right. Use muon or synaptic and search for "kernel" and select the one you want to purge.


Sent from my iPhone using Tapatalk