Any recipes you would recommend I start with? I’ve heard of but never tried this dish and I’d like to experiment :D
Any recipes you would recommend I start with? I’ve heard of but never tried this dish and I’d like to experiment :D
No worries. When checking that output, it is for the working 6.4.8-arch1-1 kernel. The broken kernel boot attempt would be most useful, but I don’t want to make you suffer to get it, if you are back to a working system. I think at this point it is safe to say your laptop isn’t a fan of the newer kernels.
I would :
/etc/pacman.conf
to ignore updates to packages linux
and linux-lts
Ideally: You could (from a working system) install a known working LTS image (pkg linux-lts
), and exclude that from updates until you land on a working kernel release (keep an eye on testing
and core
repos once a week or so). in this way, you’ll have a working LTS, and can upgrade/downgrade mainline kernels as you please, booting back into LTS to correct issues should they arise.
edit: minor
Does EndeavourOS use pacman?
You might consider modifying /etc/pacman.conf
to include the option IgnorePkg=linux linux-lts
until this is resolved. 6.4.12.arch1-1
was added ~4 days ago. If you check the releases arch linux kernel releases here, they have nearly a weekly cadence. This may be a case you can ride out until a newer kernel is released that might solve your issue.
If you need access to older releases, see the archive.
For root cause analysis – is it possible for you to extract/view the journal logs now that you have upgraded the kernel causing the issue? – /var/log/journal
is a good start. My time is limited, but I’m curious to see what’s going on in there. In any case per your and Illecors’ testing, it seems you have isolated the issue to the linux
package.
I just realized you’re also on systemd-boot (I am too). I’ll check into a way to revert back to prior kernels (for I also may run into a similar issue).
edit: updated IgnorePkg line to include both your mainline and LTS kernel (Pacman -Syu updates both) if you opt to hold them for updates.
So this occurs after an update. Is it not possible to boot into the prior kernel?
If possible to boot into the prior kernel, can you inspect logs or the journal to see where your error is cropping up?
This issue sounds like a regression of sorts with a driver, but log/debug would help confirm. This would be one worth reporting to upstream if you can rescue some logs (I gather you can if you can boot the disk from another enclosure).
If you can boot into the machine, investigate note from the journal:
journalctl --list-boots
journalctl -b -1
,– If you are booting into a live environment or are otherwise mounting the disk:
journalctl -D /var/log/journal/ID_GOES_HERE
/var/log/journal/2dff8304d5114c44bfb1311357a3cd87
– Keep us posted.
If truly a driver regression, but you can boot from the prior kernel (if you don’t have it, install it via livecd or so), definitely report this one and remain on the prior kernel until resolved. Bleeding edge things.
I read that with Guga cadence.
RIP and thanks for all the hard work I’ve benefited from over the last decade.
I’ll think of this man while explaining vim to my new hire next week.
Draw.io is pretty amazing.
Moves like this are rather inspirational. Quality submission OP.