#[ENDEAVOUR] System Unbootable, black screen

96 messages · Page 1 of 1 (latest)

flint scroll
#

As title states. Using Endeavour OS, system unbootable after pacman -Syu (pacman reported it as successful). No life signs of the system, no access to the other TTYs. Can arch-chroot into the system via recovery image.

Have tried:
Waiting
Using fallback boot image
Regenerating boot images via dracut via chroot
Running pacman -Syu via chroot

quaint eagle
#

.s q

rain ridgeBOT
# quaint eagle .s q

When requesting support, please include specific, detailed, and relevant information about your system and issue.

We need such information because we don't know what it's like inside your system, and it's unlikely that we know much about the issue you're facing. The more information you can provide, the better we can help you with your specific issue.

Some examples of frequently requested information include the steps you took before your issue occurred (such as system updates), the steps you took to resolve your issue and their results, and your environment (such as your display manager or desktop environment).

Vague or superficial questions lead to vague or superficial answers. False information leads to false solutions.

flint scroll
#

Well as I said it occurred after I rebooted after a successful pacman -Syu. System is intel based, running mostly stock endeavour, DE is cinnamon, DM is lightdm iirc, which afaik is also stock endeavour.

west dust
flint scroll
quaint eagle
#

what packages were updated?
What happens when u try to boot it?

west dust
# flint scroll systemd-boot, no encryption, UEFI

No signs of life on the system, no access to the other TTYs
Can you explain this in detail?

  • Did the vendor boot logo appear
  • Did the Arch boot logo appear?
  • Did the systemd message appear
  • Are there any text outputs
  • Or just blackscreen
flint scroll
#

The boot loader works, after I choose a boot image just black screen nothing else

#

vendor logo obv works too, no distro boot logo (I removed Plymouth anyway in fear it was preventing text outputs)
No text outputs

flint scroll
#

including linux-firmware and the like

#

don’t have the full output of what was updated anymore

west dust
#

We would like to know the URLs that curl outputs.

flint scroll
west dust
flint scroll
west dust
west dust
flint scroll
west dust
flint scroll
west dust
flint scroll
#

on a live usb

#

Would lsinitrd work?

#

Seems to be the dracut equivalent of lsinitcpio

west dust
#
lsinitrd /efi/f5c8b75f18d54a1c925748c586338498/6.4.8-arch1-1/initrd | curl -F 'f:1=<-' ix.io
flint scroll
west dust
west dust
# flint scroll http://ix.io/4CIn

Could you please try the following commands?

mkdir -p /efi/efi/LinuxTest
dracut --uefi --force --kernel-cmdline "root=UUID=f6206cad-2955-498c-b3c5-a9dd1110f957 rw" /efi/efi/LinuxTest/linux.efi
efibootmgr --create -d /dev/mmcblk1 -p 2 -L "Arch UKI" --loader 'EFI\LinuxTest\linux.efi'
  • from the chroot
#
  • Please install efibootmgr if it is not found.
#

When finished, please post the output of

efibootmgr
flint scroll
#

because it’s saying it can’t find 6.2.8

#

do I try and give it the newer kernel version?

west dust
# flint scroll do I try and give it the newer kernel version?

I've changed the following commands, please try again

mkdir -p /efi/efi/LinuxTest
dracut --uefi --force --kernel-cmdline "root=UUID=f6206cad-2955-498c-b3c5-a9dd1110f957 rw" /efi/efi/LinuxTest/linux.efi 6.4.8-arch1-1
efibootmgr --create -d /dev/mmcblk1 -p 2 -L "Arch UKI" --loader 'EFI\LinuxTest\linux.efi'
west dust
flint scroll
west dust
flint scroll
#

Don’t think my firmware supports it

west dust
# flint scroll Afaik no

Can you boot into Live OS and execute the following commands?

efibootmgr -b 0006 -B
efibootmgr --create -d /dev/mmcblk1 -p 2 -L "Arch UKI" --loader '\EFI\LinuxTest\linux.efi'
  • chroot is not required
flint scroll
#

same message as before, no os found

west dust
# flint scroll or rather this

Have you mounted the ESP during UKI generation?

mount -a
{
  findmnt /efi
  echo "==> /efi tree"
  ls -R /efi
} | curl -F 'f:1=<-' ix.io
#
  • Why does it have an eMMC? Is this a Chromebook?
flint scroll
#

ye, custom firmware, standard hadware

#

the firmware works though

#

i can boot a bunch of stuff but not my linux install

west dust
#

Would you like to post the output of the command I mentioned above in chroot?

flint scroll
#

yeah sorry im still booting the live env

west dust
flint scroll
west dust
# flint scroll http://ix.io/4CJp

Please execute the following command

dracut --uefi --force --kernel-cmdline "root=UUID=f6206cad-2955-498c-b3c5-a9dd1110f957 rw" /efi/efi/LinuxTest/linux.efi 6.4.8-arch1-1

Then post the output of

ls -R /efi/efi | curl -F 'f:1=<-' ix.io
west dust
# flint scroll http://ix.io/4CJu

Dracut did not generate an image, please run the following command.

script
dracut --uefi --force --kernel-cmdline "root=UUID=f6206cad-2955-498c-b3c5-a9dd1110f957 rw" /efi/efi/LinuxTest/linux.efi 6.4.8-arch1-1
exit
curl -F 'f:1=<-' ix.io < typescript
west dust
flint scroll
west dust
# flint scroll Could this also be the reason why the system is broken? Dracut not generating a ...
5932 [2023-08-07T09:21:28+0200] [ALPM-SCRIPTLET] dracut: *** Creating image file '/efi/f5c8b75f18d54a1c925748c586338
       498/6.4.8-arch1-1/initrd' ***
5933 [2023-08-07T09:21:37+0200] [ALPM-SCRIPTLET] dracut: *** Creating initramfs image file '/efi/f5c8b75f18d54a1c925
       748c586338498/6.4.8-arch1-1/initrd' done ***

Reading your pacman.log, it appears that dracut has correctly generated the initramfs images, but it is unexpected that it would fail to generate a UKI in the chroot, as there is not much difference in procedure.

#

The reason I suggested generating UKI is to test if the current Linux system can be booted.

west dust
#

Since any UEFI implementation, such as the mrchromebox playload, could theoretically boot them without a bootloader.

flint scroll
west dust
#

If so, please provide the following information.

  • Content of /etc/kernel/cmdline
flint scroll
west dust
flint scroll
west dust
# flint scroll afaik yes

Please install mkinitcpio, then execute the following commands

curl -s ix.io/4CJD > /etc/mkinitcpio.d/linux.preset
script
mkinitcpio -P
exit
curl -F 'f:1=<-' ix.io < typescript
flint scroll
#

returns error

west dust
#

Then please try the following commands again

script
mkinitcpio -P
exit
curl -F 'f:1=<-' ix.io < typescript
west dust
# flint scroll http://ix.io/4CJI

Please execute

script -c "efibootmgr --create -d /dev/mmcblk1 -p 2 -L \"arch-linux\" --loader '\EFI\Linux\arch-linux.efi'"
curl -F 'f:1=<-' ix.io < typescript
west dust
flint scroll
west dust
flint scroll
west dust
# flint scroll Does nothing

[ALPM] upgraded linux (6.3.7.arch1-1 -> 6.4.8.arch1-1)
As this incident occurs after a kernel upgrade, you might consider downgrading the kernel as a test.

#

The older version of the package can be installed from the Arch Linux archive.

pacman -U https://archive.archlinux.org/packages/l/linux/linux-6.3.7.arch1-1-x86_64.pkg.tar.zst
flint scroll
west dust
west dust
flint scroll