You are not logged in.

#1 2022-11-07 23:00:06

jsaxx
Member
Registered: 2022-11-07
Posts: 6

[SOLVED] EFISTUB / boot issue after kernel update

My EFISTUB boot entries (booth "standard" and fallback) are not working anymore on my Thinkpad W530 just after the latest kernel update. It just won't boot. Installing and switching to grub works just fine, so the issue is indeed within the boot-loader.

I have read it could have been related to the nvidia module being blacklisted at boot by new kernel (and it could have made sense, as on my desktop - with AMD graphics - EFISTUB works just fine), but the issue persists even after switching to LTS kernel, and adjusting the boot entries to match the new boot imgs.
Tried as well different nvdia packages (initially I had "nvidia-470xx-dkms" installed as per wiki), namely "nvidia", "nvidia-lts", "nvidia-dkms", and none of the seems to make a difference on this issue using either mainline or LTS kernels.

Anyone experiencing the same issue?

Any idea how to fix this up?


EDIT (additional details):

The specific kernel upgrade was  from "6.0.6arch1-1" to "6.0.7-arch-1"

And I can see the Boot entries, but trying to launch either "Arch Linux" or "Arch Linux Fallback", will simply flash for a short moment and get me back to the UEFI boot menu. (i.e. same behaviour that you'd see when not creating the entry correctly.)

Last edited by jsaxx (2022-11-08 20:09:28)

Offline

#2 2022-11-07 23:04:34

Scimmia
Fellow
Registered: 2012-09-01
Posts: 9,809

Re: [SOLVED] EFISTUB / boot issue after kernel update

"just won't boot" isn't enough, what do you see, exactly?

"latest kernel update" also isn't enough, what did you update from and to?

Last edited by Scimmia (2022-11-07 23:06:51)

Online

#3 2022-11-07 23:07:35

jsaxx
Member
Registered: 2022-11-07
Posts: 6

Re: [SOLVED] EFISTUB / boot issue after kernel update

Well, I can see the Boot entries, but trying to launch either "Arch Linux" or "Arch Linux Fallback", will simply flash for a short moment and get me back to the UEFI boot menu.

i.e. same behaviour that you'd see when not creating the entry correctly.

Offline

#4 2022-11-07 23:13:03

jsaxx
Member
Registered: 2022-11-07
Posts: 6

Re: [SOLVED] EFISTUB / boot issue after kernel update

updated from "6.0.6arch1-1" to kernel "6.0.7-arch-1"

Offline

#5 2022-11-07 23:25:52

Scimmia
Fellow
Registered: 2012-09-01
Posts: 9,809

Re: [SOLVED] EFISTUB / boot issue after kernel update

What does efibootmgr -u show?

Last edited by Scimmia (2022-11-07 23:26:17)

Online

#6 2022-11-07 23:41:43

jsaxx
Member
Registered: 2022-11-07
Posts: 6

Re: [SOLVED] EFISTUB / boot issue after kernel update

$ efibootmgr -u
BootCurrent: 0019
Timeout: 0 seconds
BootOrder: 001B,001A,0019,0000,0001,0002,0003,0010,0012,000D,000A,0008,0007,000C,0011,000F,000B,0009,000E
Boot0000  Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0001  Boot Menu     FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0002  Diagnostic Splash Screen      FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0003  Lenovo Diagnostics    FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0004  Startup Interrupt Menu        FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot0005  ME Configuration Menu FvFile(82988420-7467-4490-9059-feb448dd1963)
Boot0006  Rescue and Recovery   FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot0007* USB CD        VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0008* USB FDD       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0009* ATAPI CD0     VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35401)
Boot000A* ATA HDD0      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot000B* ATA HDD1      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f601)
Boot000C* ATA HDD2      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f602)
Boot000D* USB HDD       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot000E* PCI LAN       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot000F* ATAPI CD1     VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35404)
Boot0010  Other CD      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35406)
Boot0011* ATA HDD3      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f604)
Boot0012  Other HDD     VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f606)
Boot0013* IDER BOOT CDROM       PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,1,0)
Boot0014* IDER BOOT Floppy      PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,0,0)
Boot0015* ATA HDD       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
Boot0016* ATAPI CD:     VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
Boot0017* PCI LAN       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot0018  OEM Hot Key   FvFile(0b5a75d0-2793-4efa-bfa7-74689122fa55)
Boot0019* GRUB  HD(1,GPT,61e59eaf-d3eb-bd47-8e67-a0912a6278d0,0x800,0x96000)/File(\EFI\GRUB\grubx64.efi)
Boot001A* Arch Linux Fallback   HD(1,GPT,61e59eaf-d3eb-bd47-8e67-a0912a6278d0,0x800,0x96000)/File(\vmlinuz-linux-lts)root=PARTUUID=d434f16b-4e51-9545-b47c-dad6064b2d41 resume=PARTUUID=4dcd6abc-3729-1645-aed0-b378743567d6 rw initrd=\initramfs-linux-lts-fallback.img quiet loglevel=3 rd.systemd.show_status=auto rd.udev.log_level=3
Boot001B* Arch Linux    HD(1,GPT,61e59eaf-d3eb-bd47-8e67-a0912a6278d0,0x800,0x96000)/File(\vmlinuz-linux-lts)root=PARTUUID=d434f16b-4e51-9545-b47c-dad6064b2d41 resume=PARTUUID=4dcd6abc-3729-1645-aed0-b378743567d6 rw initrd=\initramfs-linux-lts.img quiet loglevel=3 rd.systemd.show_status=auto rd.udev.log_level=3 nvidia-drm.modeset=1 acpi_osi=! acpi_osi="Windows 2009" module_blacklist=iTCO_wdt,iamt_wdt nowatchdog

Tried as well to create a "clean" boot entry with no additional params, but still no luck

Arch Linux    HD(1,GPT,61e59eaf-d3eb-bd47-8e67-a0912a6278d0,0x800,0x96000)/File(\vmlinuz-linux-lts)root=PARTUUID=d434f16b-4e51-9545-b47c-dad6064b2d41 resume=PARTUUID=4dcd6abc-3729-1645-aed0-b378743567d6 rw initrd=\initramfs-linux-lts.img quiet loglevel=3

As a note: I did adjust "vmlinuz-linux(-lts)", "initramfs-linux(-lts).img" and "initramfs-linux(-lts)-fallback.img" params according to the kernel I was testing with.

Last edited by jsaxx (2022-11-07 23:51:02)

Offline

#7 2022-11-08 00:02:24

Scimmia
Fellow
Registered: 2012-09-01
Posts: 9,809

Re: [SOLVED] EFISTUB / boot issue after kernel update

As long as you have the ESP (PARTUUID=61e59eaf-d3eb-bd47-8e67-a0912a6278d0) mounted to /boot, that should work fine, both before and after the update.

Online

#8 2022-11-08 02:33:55

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 18,879

Re: [SOLVED] EFISTUB / boot issue after kernel update

Just a sanity check, you did not change from the LTS kernel to the mainline kernel, did you?  Your EFISTUB is looking for the LTS kernel, but we have not been talking about that kernel to this point.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Online

#9 2022-11-08 19:52:42

jsaxx
Member
Registered: 2022-11-07
Posts: 6

Re: [SOLVED] EFISTUB / boot issue after kernel update

I have been testing both the mainline kernel as well as lts, and the boot entries I have previously pasted are referring to the lts testing phase

Offline

#10 2022-11-08 20:08:45

jsaxx
Member
Registered: 2022-11-07
Posts: 6

Re: [SOLVED] EFISTUB / boot issue after kernel update

So looks like I have solved it: the issue was indeed with the "nvidia-470xx-dkms" driver not liking 6.0.7 kernel (I have tested the combo once again and I can confirm it won't work). There are patches applied for the kernel >6.0 to the driver, but -at least from what I could see- they stopped working on 6.0.7.

Switching to the LTS kernel was the right move, but when I actually tried I did the mistake of mounting "/dev/sda1" to "/boot" and not "/mnt/boot". And this is why I was not able to boot even after switching to LTS.

After mounting the boot partition correctly I was able to boot to LTS kernel with no issue.

Thank you Scimmia and ewaller for looking into this!

Offline

Board footer

Powered by FluxBB