Alright arch-chroot
saves the day again and sudo pacman -S $(pacman -Qqn) --overwrite '*'
made things work again.
But at this point I’m afraid now to use sudo pacman -Syu
. At least while I still have a work to do without free time available.
Weekend is coming so then you hopefully time to update.
I’d suggest updating with
eos-update
or
eos-update --aur
if you have AUR packages installed.
That reminds me that sometimes a poorly maintained AUR package can cause issues too, so might be a good idea to check them too. Something like
pacman -Qm
would list foreign installed packages.
Thank you.
I have just 2 AUR packages and they’re not updating oftenly, so I doubt that they’re causing all this trouble -
pacman -Qm
digimend-kernel-drivers-dkms-git 11.r27.gb6b7b29-1
ttf-ms-fonts 2.0-12
Note that both are many years old. And digimend is a kernel module, so might be interesting to try rebuild it with the latest kernel headers. Might not be compatible?
Edit: looks like digimend has rather recent changes. When did you rebuild it last time?
Today, after a fresh os reinstall.
After I’ve rebooted everything was fine.
But then when some x11 and video related packages got new updates everything gone wrong.
Can you see any clues in journal?
Edit: must call it a day, it is way past my bedtime already.
Nope, nothing.
Yeah, mine is too, goodnight!
exact same thing happened to me the other day, and i had to fix it the exact same way too.
I had the same issue! I wish I found this post sooner, because I spent quite some time figuring out what to do. At the end, I did almost the same, but I didn’t reinstall all the packages. I was able to find only the broken ones first using paccheck
.
I wrote down more details on what I did, and some observation/questions about why this might have happened. See my post here
Well, that’s something new. I’ve had no kernel panic, yet still after update my system crashed. Even kernels to choose are missing in the systemd-boot.
At this point I have this kind of a system breakages that there are 2 options:
1 - To try and change a distro, maybe PopOS, though I hate GNOME with passion it’s seems to be the best for a hybrid laptops.
2 - Perhaps problem is dying RAM/SSD so I need to spend around 200 euro for replacing them. But besides system crashes there’s no signs of their malfunction nor in benchmarks, nor in health-tests.
I’ve tried PopOS.
Well no, it’s just terrible, even with KDE.
I’d better will reinstall EndeavourOS every time than use PopOS.
could be this issue.try the creating the file mentioned in the first solution in this link
Well, if systemd or Nvidia are truly for some reason causing all this trouble recently… I have a something to say.
Fuck you Nvidia.
Fuck you RedHat, Lennart Poettering specifically.
AUR build https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=digimend-drivers-git-dkms
if i build it with yay i got:
11.r28.g3a5d2ad-1
Thats latest commit:
Also i would questioning if this drivers are really needed on newer kernels?
This is a collection of graphics tablet drivers for the Linux kernel, produced and maintained by the DIGImend project. We maintain this package to provide newer drivers for older kernel versions which don’t have them, and to allow users to test new drivers before we contribute them to the mainline kernel.
Sadly, my Gaomon m106k is not working without Digimend.
Also, not the best wording but if you have Nvidia proprietary drivers BLOB! in use… Consider try to not use it, there are currently some strange issues with it.
I mean, you may rely on it, but you should try booting without it to see if the panics happen too.
Be it using in Kernel open source Nouveau modesetting driver or xf86-video-nouveau or even nvk: https://aur.archlinux.org/packages/vulkan-nouveau-git
All of it can be somehow a little challenging to set up, and you need to make sure to remove all the bits and bytes from one to use the other… But that’s how it can work bail out one after the other.
could be the modules are inside the kernel tree but disabled and only would need to force loading in modprobe config or using force drivers in dracut …
Alright last several system updates were fine, also system finally stopped freezing randomly(there’s even no caps blinking so it’s not kernel panic, but system is ignoring everything completely including attempts to enter TTY).
- As recommended by @mayhem I did this -
sudo touch /etc/systemd/do-not-udevadm-trigger-on-update
- I downgraded nvidia drivers
IgnorePkg = nvidia-dkms lib32-nvidia-utils nvidia-settings nvidia-utils
down to version545.29.06
warning: lib32-nvidia-utils: ignoring package upgrade (545.29.06-1 => 550.76-1)
warning: nvidia-dkms: ignoring package upgrade (545.29.06-4 => 550.76-1)
warning: nvidia-settings: ignoring package upgrade (545.29.06-1 => 550.67-1)
warning: nvidia-utils: ignoring package upgrade (545.29.06-4 => 550.76-1)
-
Uninstalled Digimend, the only AUR packages that I have now -
ttf-ms-fonts
andenvycontrol
-
Just in case of any other surprises from NoVidya I’ve used
envycontrol
to switch into the integrated-graphics mode, so rtx 3050ti not involved in any processes at all.
sudo envycontrol -s integrated
- I decided not to use Wayland session for testing it on KDE Plasma, I’d better stick with X11 for a next year.
Hello Matvey!
Did it stop happening to you? My system freeze and caps lock starts blinking. Can’t use REISUB and i’m forced to do a force shutdown. It happened a couple times already. Mostly when I shutdown/reboot sometimes, and other times randomly while using the laptop. I also tested using linux-lts, but it was the same. I am using GNOME 46.2 | WM: Mutter (X11) | Kernel: Linux 6.9.6-arch1-1 currently.