abrer

joined 2 years ago
[–] [email protected] 0 points 2 years ago* (last edited 2 years ago) (3 children)

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.

[–] [email protected] 9 points 2 years ago* (last edited 2 years ago) (11 children)

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,
    • where -1 was the prior boot, -2, the one before that, etc

-- If you are booting into a live environment or are otherwise mounting the disk:

  • journalctl -D /var/log/journal/ID_GOES_HERE
  • example path: /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.

[–] [email protected] 6 points 2 years ago

I read that with Guga cadence.

[–] [email protected] 2 points 2 years ago

++ for no bar.

[–] [email protected] 14 points 2 years ago

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.

[–] [email protected] 1 points 2 years ago

Draw.io is pretty amazing.

[–] [email protected] 2 points 2 years ago

RHEL> AD:

I haven't had time for root cause analysis, but a recent patch cycle (last few months of patches) in our environment broke RHEL7/8 AD integration with via SSSD.

Did anyone run into this? I'll post the fix when I get home should any other admins run into this gem.

[–] [email protected] 4 points 2 years ago

This is the way

[–] [email protected] 0 points 2 years ago (2 children)

This looks awesome!

Do you have a recipe? I've been thinking about trying this a lot.

[–] [email protected] 1 points 2 years ago (1 children)

I agree. Jerboa is pleasantly functional.

view more: ‹ prev next ›