I have since my last update the problem (I think latest kernel and radeon driver where updated) that when booting before the DM starts: The monitor loses its video signal.
I already tried to enter the TTY with CTRL+ALT+F2(F3/F4/F5) but that doesn’t seem to work either, the screen stays black.
If the video drivers are broken, you should try to boot to TTY straight from the boot menu, editing the boot entry and add 3 in the kernel parameters line (actual method depends on which bootloader is used, grub, systemd-boot, refind, etc.).
This shouldn’t be related to the current issue, which is supposed to relate to package updating). You may experience a different issue, so maybe create a new topic?
I added systemd.unit=multi-user.target to my kernel parameter line and finally am greeted by a TTY login. But one second later, before I can login, the screen goes black again.
I also have the original USB drive from the installation, after choosing the boot option it suddenly also boots into a dead screen.
I was finally able to create another bootable USB device with Ubuntu.
The normal boot option would also send me to a black screen, but: the “safe graphics” option finally booted to the live system.
I could now chroot into my system and run a pacman -Syyu, but after a reboot my screen was again black.
So here is my inxi output with errors:
[root@ubuntu /]# inxi -Faz
12System:
12Kernel 5.15.0-43-generic 12arch x86_64 12bits 64 12compiler N/A 12Console N/A 12Distro EndeavourOS
12base Arch Linux
12Machine:
12Message No machine data: try newer kernel. Is dmidecode installed? Try -M --dmidecode.
Can't use an undefined value as an ARRAY reference at /usr/sbin/inxi line 10498.
This doesn’t gives us any useful information. If you were able to arch-chroot and run an update this makes no sense that you can’t get the full output of the command. It is way longer than this which is basically one line. It 's asking if dmidecode is installed? You can install it or check if it’s installed. It should have been already installed.
Edit: We need to see the hardware output in order to be able to help.
Okay, my bad. There is a difference between chroot and arch-chroot.
I had to install the Ubuntu package ‘arch-install-scripts’ which includes arch-chroot.
So I did a proper arch-chroot and this is the inxi output:
It’s been so long i have forgotten most of the previous issue. Are you able to boot on the live ISO? Or it is installed and you can’t boot?
On the live ISO you need to add this kernel parameter and try. If it works you could install. Once installed you would need to add this kernel parameter to the default grub command line if you install with grub. Then grub needs to be updated also. For now i don’t know the details as it’s been too long.
thanks for your patience, yeah you are right this was really a dragging process as I mostly have an hour in the evening to deal with this.
I may resolved this, have to do some more testing later.
So I try to brake this down, maybe it’s helping someone who runs into this problem.
After update the EOS system could not boot into the DM, no cursor, monitor loses signal.
The same install medium that was used for installing my system could also not boot into a live system, same problem (still a ??? for me)
So I opted for another distribution to boot into a live system, the latest Ubuntu.
Same behavior, but booting the “safe graphics” mode finally worked.
Here I could arch-chroot into my system after installing the Ubuntu package ‘arch-install-scripts’ which includes arch-chroot (arch-chroot script does apparently way more than a chroot, learned that)
Run pacman -Syyu and the system boots normally again…
Lessons learned: Move ASAP to BTRF + timeshift to prevent a total lockout. This combination works flawless on my notebook.
Well at least you were able to arch-chroot another way and update which fixed the problem. I don’t know if it was a partial update previously that caused the problem but that would be my guess. I’ve never run into these kind of issues but there’s always tomorrow. Glad it’s working for you.