3

OS: Arch Linux x86_64
Host: 81Y3 IdeaPad L3 15IML05
Kernel: 6.8.1-arch1-1

~ λ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sr0 11:0 1 1024M 0 rom nvme0n1 259:0 0 476.9G 0 disk ├─nvme0n1p1 259:1 0 2G 0 part /boot ├─nvme0n1p2 259:2 0 12G 0 part [SWAP] ├─nvme0n1p3 259:3 0 100G 0 part / └─nvme0n1p4 259:4 0 362.9G 0 part /home

I have updated the UEFI to the latest version "EJCN31WW"

Information about the EFI partition:

File System: fat32 Flags: boot, esp

Grub configuration file:

GRUB_DEFAULT=0 GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR="Arch" GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3" GRUB_CMDLINE_LINUX="" GRUB_PRELOAD_MODULES="part_gpt part_msdos" GRUB_TIMEOUT_STYLE=menu GRUB_TERMINAL_INPUT=console GRUB_GFXMODE=1920x1080 GRUB_GFXPAYLOAD_LINUX=keep GRUB_DISABLE_RECOVERY=true

I have tried missing with the UEFI settings, but with no success.
I have noticed that if i entered the boot menu and selected grub the first time it turns on, it will boot grub right away.

So, what I think that it could be caused by (I'm probably wrong XD):

  1. The EFI partition is too large (2Gb).
  2. The EFI partition doesn't have the right format.
  3. It tries to boot grub, but it fails.

What is the solution?

This is the boot partition tree:

/boot ├── EFI │   └── GRUB │   └── grubx64.efi ├── grub

Edit No.2:

~ λ efibootmgr BootCurrent: 0000 Timeout: 0 seconds BootOrder: 0000,2001,2002,2003 Boot0000* GRUB HD(1,GPT,dbf925d5-a5c8-4bc3-8327-abdccf9b4036,0x800,0x400000)/\EFI\GRUB\grubx64.efi Boot2001* EFI USB Device RC Boot2002* EFI DVD/CDROM RC Boot2003* EFI Network RC

Block id:

~ λ doas blkid /dev/nvme0n1p3: UUID="ce1f67f3-1e62-45ad-b5c3-2b0bfedbe19b" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="e320fb70-dd33-4e4a-9cf2-48ea4d91630d" /dev/nvme0n1p1: UUID="F7CC-1B87" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="dbf925d5-a5c8-4bc3-8327-abdccf9b4036" /dev/nvme0n1p4: UUID="0c764fa9-8209-4e80-bdd5-a11c56bf2bde" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="86879a61-1e57-489f-9210-528ed4f8760b" /dev/nvme0n1p2: UUID="badec528-15b0-4cd5-8e7f-eb6452fb4de3" TYPE="swap" PARTUUID="7e028323-a22e-45d2-96a2-2615c8879aa7"

file system table

~ λ cat /etc/fstab # Static information about the filesystems. # See fstab(5) for details. # <file system> <dir> <type> <options> <dump> <pass> # /dev/nvme0n1p3 UUID=ce1f67f3-1e62-45ad-b5c3-2b0bfedbe19b / ext4 rw,relatime 0 1 # /dev/nvme0n1p1 UUID=F7CC-1B87 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2 # /dev/nvme0n1p5 UUID=0c764fa9-8209-4e80-bdd5-a11c56bf2bde /home ext4 rw,relatime 0 2 # /dev/nvme0n1p2 UUID=badec528-15b0-4cd5-8e7f-eb6452fb4de3 none swap defaults 0 0

firmware bug from dmesg

~ λ doas dmesg ... [ 0.000000] [Firmware Bug]: TSC ADJUST: CPU0: -1306247588 force to 0 ...
Improve this question
11
  • Surprised it works at all! I have a fstab which refers to a /boot/efi partition which has a EFI subdirectory (Case is important here) which contains 3 directories { Boot debian Microsoft }. Have to say I don't know what its doing, but the /boot/efi/EFI/{ Boot debian Microsoft } structure is probably important. Do you have a time delay in your BIOS, so you can see if it powers up and does anything, such as trying to find an efi configuration anywhere? Commented Apr 1, 2024 at 23:17
  • the screen just turns on and off 3 times, without any text. the post was edited to show the /boot partition tree Commented Apr 1, 2024 at 23:46
  • Have you tried booting from a 'live' version of Linux, from USB? Commented Apr 2, 2024 at 0:50
  • yeah, it works fine, i had kali linux before it also worked fine back then. Commented Apr 4, 2024 at 2:48
  • Is grub a file or directory in the tree output? Commented Apr 7, 2024 at 6:44

2 Answers 2

Reset to default
1
+50

Booting looks fine to me from a technical standpoint.

I think this is happening:

The resolution of the display gets changed for a split second to another resolution. As this is sooo early in the boot process it has no other way as to turn the display on and off.

My guess is that the Boot images you see like Lenovo Logo etc have a different resolution than your grub menu. Most pictures have 800x600.

As you do not get the changes when you halt "fancy" booting with pictures and directly boot the grub menu with the correct size.

I think its like this:

  • Initial Power on Resolution -->> Maybe 480x600 don't know really ->> Initial Blank
  • Lenovo Logo shows ->> Resolution needs to change for this ->> Resoultion gets changed to show Pic. Second blank
  • Grub begins booting and request to change to 1920x1080 ->> Third Blank to show correct Grub resolution.

So my first advice would be lower the grub resolution to 800x600 and test if some of the blanks vanish. Also you could try to boot in debug mode so no picutes and logos are shown.

To answer your questions:

So, what I think that it could be caused by (I'm probably wrong XD):

The EFI partition is too large (2Gb).

  • Thats fine. 512GB would be enough tho if you want to save some space

    The EFI partition doesn't have the right format.

  • It does otherwise booting would not succeed. You would see and EFI shell if this would be the case.

    It tries to boot grub, but it fails.

  • Then you would see a shell and would not be able to boot.

Improve this answer
4
  • Thabks for the answer, but that didn't solve it for my i tried multiple resolutions for grub, with no success, i even tried removing the whole ssd, it still flashes three times before saying no bootable device. Commented Apr 8, 2024 at 15:26
  • This is a video of what exactly happens on startup streamable.com/lcy2hw Commented Apr 8, 2024 at 15:26
  • When i switch to legacy mode it boots normally but I don't understand how, i have gpt table, the settings are legacy, use uefi first Commented Apr 8, 2024 at 15:27
  • I looked at the video, It indeed seems very odd. Your guess with the firmware looks likely. However, if it works and you can access the bios and so on. Its still a useable device i think. Commented Apr 9, 2024 at 7:01
1

I didn't find an answer, so at last, I gone to the bios settings.

choose Legacy boot,

and Try UEFI first,

and that worked fine.

but still it won't work when I choose UEFI instead of legacy boot. I think it's something wrong with the firmware Lenovo shipped.

Thanks

Improve this answer

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.