Updated moments ago , and noticed several problems ranging from being unable to boot with kernel 4.19.190-2 by getting systemd.udev errors …
All the new ( 5.x) kernels are “Bootable” though …
Another annoying detail is , for example unable to play any of the Steam games like :
“./StarConflict: /usr/lib32/libcurl.so.4: version `CURL_OPENSSL_3’ not found (required by ./StarConflict)”
Any ideas how to solve this one ? as yesterday everything was OK …
Hello,
I have the same issue reported in the previous update, but I think I have found the responsible: systemd!
Here the steps I done before the update:
I concour with @zomberman …
All the hassle with this latest update is directly related to the systemd package .
If I downgrade manually to systemd version 247.7 the system executes and boots Kernel 4.19 correctly and none of the Steam errors appear …
Although if I simply downgrade to the systemd previous 248.2 version I still was not able to boot with kernel 4.19…
So you have proven it perfectly. Verified!
Unstable is no option, systemd is the same version as testing at this time.
And: I run a different system, kernel 510 and 512 at unstable - everything fine…
Can be magic.
Some more details related to the unbootable 4.19 kernel with systemd 248.y :
By analysing the journalctl I got an half dozen of this entries:
systemd-udevd.service : failed to set up mount namespacing: /run/systemd/unit-root/proc/sys/kernel/domainname: Device or resource busy
systemd-udevd.service : failed to step NAMESPACE spawning /usr/lib/systemd/systemd-udevd: Device or resource busy
systemd-udevd.service : Main process exited, code=exited, status=226/NAMESPACE
systemd-udevd.service : Failed with result 'exit-code'
Failed to start Rule-Based Manager for Device Events and Files.
Afterwards only a keyboard reboot request is the only option.
Idem on my journalctl that I shared on previous update thread: dozen of those entries.
I knew it, but for some minutes I wanted to switch to stable ,also to see which packages deffered. And seeing systemd to a prevoious version and seen my wife’s pc booted with 4.19 after last updated, I supposed that had to be systemd. Downgraded and so on…
Trackpad do not work anymore in my Laptop Dell. Just an Intel with integrated graphics, nothing fancy.
This happened with this machine in kernel 4x versions, then after going to versions 5 it never happened again, in fact the kernels were not changed version, 510 and 512 are what I was using, all good until after the update.
As it uses the integrated graphics of Intel the session is Wayland, I tried with X but there was no change either.
Tell me what log or data you need to see if someone can help me. Thanks in advance.
Latest kernel 5.13. I am getting random lockups ever since upgrading the kernel. The only thing different that I have done on this kernel is install Dogecoin Core Wallet. It takes a huge amount of time to update the blockchain, and I suspect it is locking up because of the Dogecoin software, however I just downgraded kernel to 5.12 and the lockups went away. Prior to this downgrade, system would lock up even if Dogecoin wasn’t running, but as soon as I ran Dogecoin, the system would lock up for sure. Now that I’m back to 5.12 the system runs fine. Just wanted to make devs aware, my system has ran flawlessly to this point, so there seems to perhaps be an issue with the kernel 5.13. Perhaps Doge related, perhaps not. The lockups didn’t start happening until Doge had been updating for a full day and had roughly 6 hours left to finish updating the blockchain. But like I said, I was getting lockups on 5.13 kernel before I would even have a chance to launch Doge sometimes.
That is a kernel still in its development phase. It has only reached rc3 (and testing only has an even older rc2 available) and will proably released (go stable) on 2021-07-04…
Verified!
