You are not logged in.

#1 2021-04-01 10:35:23

femeref
Member
From: Stockholm :: Berlin
Registered: 2010-04-07
Posts: 15

Blank screen after selecting Arch from gummiboot menu

Hi guys,

I have a Lenovo Thinkpad X260 on which I installed Arch back in 2016. I have been regularly updating with last working full system update the 8th of March.
I performed another full system upgrade yesterday and now the machine boots to the UEFI menu, I select arch, and I am presented with a blank screen.
No changes were made to the BIOS.


I tried the following:
- loaded up a USB stick with an arch ISO (21-03-01 and 21-02-01) and booting from the USB stick leads to the same result.
- loaded up a USB stick with an arch ISO from 20-10-01 and I can chroot into the machine.

journalctl shows no output after I've shutdown the machine yesterday evening.

Downgrading the kernel to the last working one doesn't fix the problem.

Does anyone have any hints on how I can go about fixing this?

Last edited by femeref (2021-04-01 13:45:25)

Offline

#2 2021-04-01 11:48:17

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 12,505

Re: Blank screen after selecting Arch from gummiboot menu

What's supposed to start? If a graphical session rule out early KMS: https://wiki.archlinux.org/index.php/Ke … _KMS_start

Offline

#3 2021-04-01 12:32:25

femeref
Member
From: Stockholm :: Berlin
Registered: 2010-04-07
Posts: 15

Re: Blank screen after selecting Arch from gummiboot menu

I'm supposed to be dropped into Gnome.


My mkinitcpio.conf is pretty barebones, empty MODULES, BINARIES and FILES. I've only got some

HOOKS=(base udev autodetect medconf block filesystem keyboard fsck)

Last edited by femeref (2021-04-01 12:33:13)

Offline

#4 2021-04-01 12:39:35

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 12,505

Re: Blank screen after selecting Arch from gummiboot menu

Try setting up early KMS, if it is stuck regardless, check from a chroot whether a journal was written, if it wasn't add loglevel=7 to the kernel parameters to see whether you get error messages during early boot (... and remove a potentially present quiet parameter)

Offline

#5 2021-04-01 13:22:39

femeref
Member
From: Stockholm :: Berlin
Registered: 2010-04-07
Posts: 15

Re: Blank screen after selecting Arch from gummiboot menu

No luck with setting up early KMS.

After adding loglevel=7, journalctl doesn't log any boot (last official boot is from 2021-03-08), last message in journalctl is about shutting down on 2021-03-31. There was no quiet kernel parameter.

Offline

#6 2021-04-01 13:47:56

femeref
Member
From: Stockholm :: Berlin
Registered: 2010-04-07
Posts: 15

Re: Blank screen after selecting Arch from gummiboot menu

Some additional information: I am using gummiboot it seems, not grub.

Offline

#7 2021-04-01 14:07:36

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 12,505

Re: Blank screen after selecting Arch from gummiboot menu

I'm not expecting journalctl to log something if you don't get to a point where it starts logging something but the attempt of a kernel start should put "something" on the screen during bootup. It might also be that the issue is due to modesetting in the first place so try a nomodeset on the params as well.

Offline

#8 2021-04-01 14:14:54

femeref
Member
From: Stockholm :: Berlin
Registered: 2010-04-07
Posts: 15

Re: Blank screen after selecting Arch from gummiboot menu

Adding nomodeset has no effect, still just a blank screen after picking "arch" from the gummiboot menu.

Thanks for the responses btw!

Some additional things I've tried, with no effect:
- downgrading the kernel as far back as July 2019 (seems like I never cleaned out /var/cache/pacman, the packages for all 38 times I did a full system upgrade are still there)
- downgrading systemd to the previous version

Offline

#9 2021-04-01 19:44:41

femeref
Member
From: Stockholm :: Berlin
Registered: 2010-04-07
Posts: 15

Re: Blank screen after selecting Arch from gummiboot menu

Alright, I managed to boot he machine as usual by downgrading everything I had upgraded the 29th:

#!/usr/bin/env bash

PACKAGES=
while read LINE; do
	if [[ $LINE != *upgraded* ]]; then continue; fi
	if [[ $LINE != *21-03-29* ]]; then continue; fi
	PACKAGE=$(echo $LINE | cut -d' ' -f4)
	VERSION=$(echo $LINE | cut -d' ' -f5)
	VERSION=${VERSION:1}
	FPACKAGE=$(ls /var/cache/pacman/pkg/${PACKAGE}-${VERSION}*)
	PACKAGES="${PACKAGES} ${FPACKAGE}"
done < $1

pacman -U $PACKAGES

... and feeding it /var/log/pacman.log

it's roughly 250 upgraded packages. Time to install them one by one or anyone with a better suggestion?

Offline

Board footer

Powered by FluxBB