Page MenuHomeSolus

Unable to boot Solus Lenovo N22
Closed, ResolvedPublic

Description

Since a few months ago every time I upgrade the kernel I have a black screen after reboot, In order to solve this I have to boot from usb and replace the file /EFI/Boot/BOOTX64.EFI with the file from the old Solus 3.0 iso.

I attached it here.


Thanks in advance.

Event Timeline

Herald removed carlix as the assignee of this task. · View Herald TranscriptDec 2 2018, 7:53 PM

What is the output if you run the following command?

efibootmgr -v

BootCurrent: 0012
Timeout: 0 seconds
BootOrder: 0014,0012,0006,0005,0000,0002,0003,0013,0015,0016,0001,0004,0007
Boot0000* ubuntu HD(1,GPT,81d86849-4a21-4bf2-a3f8-5c0e2d71663f,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* Windows Boot Manager HD(1,MBR,0x58840353,0x88,0xf000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0002* Linux Boot Manager HD(1,GPT,cf7b6f9d-b7c3-46e0-b0d0-578de0f1c302,0x40,0xf4240)/File(\EFI\goofiboot\goofibootx64.efi)
Boot0003* Linux Boot Manager HD(1,GPT,a08706f5-ef4d-428e-a8c3-81d5468f4834,0x40,0xf4240)/File(\EFI\goofiboot\goofibootx64.efi)
Boot0004* Linux Boot Manager HD(1,GPT,c72ce238-55d5-44d2-832f-1093ab9d2408,0x40,0xf4240)/File(\EFI\goofiboot\goofibootx64.efi)
Boot0005* Linux Boot Manager HD(1,GPT,55a14299-fba4-433c-9eed-b07d9aea86de,0x40,0xf4240)/File(\EFI\goofiboot\goofibootx64.efi)
Boot0006* Fedora HD(1,GPT,7013c201-9ffa-451e-856b-8af51f05c580,0x800,0x100000)/File(\EFI\fedora\shimx64.efi)
Boot0007* Linux Boot Manager HD(1,GPT,99583650-6007-4084-b263-018299258ac0,0x800,0x100000)/File(\EFI\goofiboot\goofibootx64.efi)
Boot0010 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011 Boot Menu FvFile(86488440-41bb-42c7-93ac-450fbf7766bf)
Boot0012* eMMC Disk: Samsung 64GB PciRoot(0x0)/Pci(0x10,0x0)/Ctrl(0x0)..]3.K.L......2.
Boot0013* USB FDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0014* USB HDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot0015* USB CD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0016* PCI LAN: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)

Currently I just have Solus installed and I'm using the efi file from the Solus 3 iso image that I uploaded here

xulongwu4 added a comment.EditedDec 4 2018, 2:30 AM

I see you have a lot of efi files in your EFI partition. That is probably why your boot process is messed up.

Most importantly, Solus is using systemd-boot for boot management. Normally you should be able to see a file named as \EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI, which does not show up in your list.

I would thus suggest you reinstall systemd-boot as follows:

First mount your esp partition. Suppose your esp partition is at dev/sda1, run the following command:

mkdir -p ~/mnt/efi
sudo mount /dev/sda1 ~/mnt/efi

Reinstall systemd-boot to your esp partition as follows:

sudo bootctl --path=/home/xxx/mnt/efi install

where xxx should be your user name.

Check whether /home/xxx/mnt/efi/EFI/systemd/systemd-bootx64.efi exists.

Delete the boot entries created by previous linux distros you ever installed but NOT existed on your disk any more, including all these entries of goofibootx64.efi:
sudo efibootmgr -b xxxx -B
where xxxx is the four digit number corresponding to the entry you want to delete (such as 0001 in the line Boot0001* Windows Boot Manager HD(1,MBR,0x58840353,0x88,0xf000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................).

Create a boot entry for the new systemd-bootx64.efi as follows:
sudo efibootmgr --create --disk /dev/sda --part 1 --label "Linux Boot Manager" --loader "\EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI" --verbose.

After these steps, rerun efibootmgr -v to check whether \EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI shows up. If it does, record its four-digit boot number.

Set Solus as the first OS to boot from:
sudo efibootmgr -o xxxx, yyyy, zzzz
Here xxxx denotes the four-digit boot number for Solus. The other numbers can be the four-digit numbers for other remaining boot options.

Run sudo clr-boot-manager update.

Reboot and see if you can see Solus as the boot option.

BootCurrent: 0012
Timeout: 0 seconds
BootOrder: 0012,0000,0013,0014,0015,0016
Boot0000* Linux Boot Manager HD(1,GPT,99583650-6007-4084-b263-018299258ac0,0x800,0x100000)/File(\EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI)
Boot0010 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011 Boot Menu FvFile(86488440-41bb-42c7-93ac-450fbf7766bf)
Boot0012* eMMC Disk: Samsung 64GB PciRoot(0x0)/Pci(0x10,0x0)/Ctrl(0x0)..]3.K.L......2.
Boot0013* USB FDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0014* USB HDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot0015* USB CD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0016* PCI LAN: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)

That is my current configuration, I will wait until a new kernel update to see if it worked

This looks good to me. I am not sure about your boot option 0012. I might just set 0000 as the first boot option. Good luck with the next kernel update and let us know whether it works.

DataDrake triaged this task as Normal priority.Dec 11 2018, 5:05 AM
DataDrake edited projects, added Hardware; removed Lacks Project.

I upgraded and It happened again

After Solus 4.1 the problem was solved

carlix closed this task as Resolved.Apr 24 2020, 5:37 PM