[SOLVED] latest kernel unable to boot

jostber · 02-02-2016, 07:39 AM

Be careful that you copy the correct vmlinuz to /boot/efi/EFI/Slackware as well as the correct initrd.gz. Check that you enter the correct path to your root partition. My elilo.conf looks like this:

chooser=simple
delay=1
timeout=1
#
image=vmlinuz
label=vmlinuz
initrd=initrd.gz
read-only
append="root=/dev/sda3 vga=normal ro"

qunying · 02-02-2016, 11:44 AM

Quote:

Originally Posted by jheengut

rEFInd is a boot manager,I need a boot loader that can accept a new shiny 4.4 kernel

When you have EFI stub loader built into the kernel, it could load the kernel without problem (by default, Slackware build its kernel with EFI stub loader), I have use it for all my EFI capable machines without any extra boot loader.

Ref: http://www.rodsbooks.com/refind/linux.html

jheengut · 02-03-2016, 04:59 AM

Quote:

Originally Posted by Didier Spaier

We can't know for sure if this is a bug with the information provided. I suggest that you use efibootmgr alone to check all firmware menu entries.

Other than that, did you try having a single entry in elilo.conf with only the 4.4 kernel? as we don't know how the efi image provided in the elilo package was compiled, maybe it accepts just the first entry in the config file?

This a new install of slackware 14.1 with no modifications. I then upgraded the slackbox. The 4.4 kernel has been copied to /boot/efi/EFI/Slackware/vmlinuz. Also, I'm using the huge kernel so an initrd is not needed for the moment.

Nothing else was done.

I tested grub2. It works even with the new kernels, and those that I compiled myself, ie 4.5.0-rc2 is booting.

I think that the elilo of slackware 14.1 cannot boot a above certain version of the linux kernel.

Attached is a sample of how the UEFI Aptio BIOS had been reading the boot entries though efibootmgr and the MSI efi boot manager are recogninzing the boot entries correctly. The boot entries are read correctly everywhere now, no worries of your part on this particular problem, I have a way to resolve it.

Didier Spaier · 02-03-2016, 05:35 AM

I don't see any attachment.

I doubt that elilo care for a kernel version, but you can check that upgrading to 3.16. Just grab the source stuff in Slacwkare64 current and rebuild the package in 14.1. I will also try to reproduce later today or tomorrow.

jostber · 02-03-2016, 06:19 AM

Any relevance to this thread?

http://www.linuxquestions.org/questi...-a-4175568840/

jheengut · 02-04-2016, 04:48 AM

Quote:

Originally Posted by jostber

Any relevance to this thread?

http://www.linuxquestions.org/questi...-a-4175568840/

nope , mine is a haswell processor.

Code:

CPU 0:
   vendor_id = "GenuineIntel"
   version information (1/eax):
      processor type  = primary processor (0)
      family          = Intel Pentium Pro/II/III/Celeron/Core/Core 2/Atom, AMD Athlon/Duron, Cyrix M2, VIA C3 (6)
      model           = 0xc (12)
      stepping id     = 0x3 (3)
      extended family = 0x0 (0)
      extended model  = 0x3 (3)
      (simple synth)  = Intel Core i5-4000 / i7-4000 / Mobile Core i3-4000 / i5-4000 / i7-4000 / Mobile Core i3-4000 / Mobile Core i5-4000 / Mobile Core i7-4000 / Pentium G3000 / Celeron G1800 / Mobile Pentium 3
500U / Mobile Celeron 2900U / Xeon E3-1200 v3 (Haswell), 22nm

And my laptop does not even boot the kernel, it just reboots and drop to the Aptio UEFI BIOS or sometimes just reboots.

And grub boots the kernel cleanly with no apparent problems or issues related to hardware.

And only elilo refuses to boot new kernels.

I will continue to use elilo for the 14.1 but 14.2 will surely be grub. The grub-mkconfig is fine by me to update W.R.T. latest kernel available in /boot.

jheengut · 02-04-2016, 04:52 AM

Quote:

Originally Posted by Didier Spaier

I don't see any attachment.

I doubt that elilo care for a kernel version, but you can check that upgrading to 3.16. Just grab the source stuff in Slacwkare64 current and rebuild the package in 14.1. I will also try to reproduce later today or tomorrow.

There is a ssd plus a hard disk, so one efi partition for each drive that's why you see slackware14.1 and slackware

Bertical · 02-04-2016, 05:25 AM

I had the same problem after upgrading today. Looks like eliloconfig was updating /boot/efi but the EFI partition wasn't actually mounted. I solved it by booting into the installer, mounting all my partitions on a temporary directory and chrooting. After making sure the EFI partition was indeed mounted and running eliloconfig my system now boots normally.