I have a brand new PC that’s been running EndeavourOS pretty fine for some months.
Today I updated the system and it’s now broken.
The system boots, flashes a bunch of lines (cannot see any erros, looks fine), but when the UI is about to load it just hangs, nothing shows.
So I booted from an EndeavourOS usb stick to see if that would work. It did, no problems there.
I then tried to reinstall the OS. First with online install with cinnamon. After all is done, I have the same problem.
Then I try offline install, and after it’s done it works fine and boots into UI desktop, BUT after updating the system again everything fails like before when booting…
System:
AMD Ryzen 7 7000
Gigabyte B650 Gaming x ax
32 GM ram
I’ve searched around to see if anyone else has this problem, but haven’t found anything recent…
Well, this happens after a “stock” install with only packages that is installed by the default system. The system is also broken, I cannot even get in.
I tried reinstalling with LTS and booting from it, but unfortunatly still same problem.
I’m assuming the bug you mentioned is not present in LTS, so then this must be some other problem?
(just checked archlinux.org, the LTS is 6.1.36, so this is not the problem)
There is just no signal sent to the monitors, so CTRL+ALT+F2 to get a shell doesn’t work
You made it sound as if that after a fresh “offline install” you reboot the system, then update and that you then run into the problem as well. Do you remember which packages you update before you reinstall your system?
you could chroot into your system and then install the appropriate kernel. It would be easier to reinstall(offline) your system and then ignore the kernel in the /etc/pacman.conf file.
e.g. like this
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
IgnorePkg = linux
#IgnoreGroup =
then you could update your system. so the kernel is ignored when updating
if a newer kernel fixes the problem, you can remove the kernel from pacman.conf again.
From within the arch-chroot you can run any command (its root by default) as you would run the installed system (inside the chrooted terminal only to make sure)
The issue mostlikely about the GPU driver and Mesa ?
Is the CPU equipped with GPU? or do you have dedicated GPU graphics card installed?
inxi -Gaz from live session would help to see details…
Sweet, this did the trick and confirms that the problem actually was with the kernel.
I added linux linux-headers linux-firmware to /etc/pacman.conf and the offline installer works after updating it.
Ok, so isn’t it pretty bad that the LTS kernel is updated to include this bug? Kind of defeats the purpose of LTS…
Anyway, thanks a lot! I will probably reinstall the system again and downgrade the kernel as instructed here. It will be something that is nice to learn
From the following comment from the link I posted earlier, I understand that the previous LTS version(6.1.35) was also affected. It would make sense not to update LTS so often, i.e. to put it in the IgnorePkg of pacman.conf.
