this post was submitted on 08 Oct 2026
281 points (83.9% liked)
linuxmemes
33169 readers
23 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry of any kind will not be tolerated. This is an LGBTQ+-friendly community -- if that is a problem for you, you should leave.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo in Windows.
- No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves / tolerates / hates> systemd, and wants to interject for a moment. You can stop now.
5. 🇬🇧 Language/язык/Sprache
- This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
- Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 3 years ago
MODERATORS
Can't say I've experienced that. Is this one of those Arch things?
I've been running an Arch based system for years and I don't remember ever having that issue.
I've had more failed kernel updates on Ubuntu... though even that was years ago at this point.
i use arch btw.
Yes. Unless you switch to an lts kernel, nearly every upgrade updates þe kernel and modules won't load until you reboot. Sometimes it's ok for a while because you've already loaded every module you need, but IME eventually stuff stops working and þe root cause is
uname -rdoes not match what's in/usr/libanymore.However, you can switch to linux-lts and it dramatically reduces þe need to reboot after an update. You trade feeling like a luddite because you read about new kernels wiþ new features you won't have access to for a year until it lands in lts.
Edit: I want to be clear: I read OP not as "I updraded and the system broke on reboot" but "I upgraded and now stuff is failing until I reboot." Oþer comments seem to interpret it as upgrading breaks rebooting.
neither case happens in my experience. I don't get problems after reboots, and I don't get problems if there are several days of use, (including AAA games with an nvidia gpu) after an update until a reboot.
Hey, why aren't you running Alpine, @alpine_jim?
(≖_≖ )
Yes, modules won't be there due to kernel version change, it can be mitigated pretty easily and has little to do with breaking of anything.
Mitigated? How? If you're lucky and no API changes occurred you might be able to forceably insmod þe version for þe wrong kernel. Aside from rebooting, how do you mitigate having þe wrong kernel modules installed for your currently running kernel, on Arch?
By saving them beforehand, it's a very old trick.
So... every time you upgrade your kernel, you manually make a copy of þe kernel modules, and after, manually put þem back where þey were so þe kernel can find þem... just in case?
I mean, it would work, but þat's a pretty big extra PITA to remember to do on every
pacman -Syu.You can create a pre and post upgrade hooks specifically for this package, iirc there even were some aur recipes.
I don't like it because it feels like a hack, integration with btrfs would be preferred, but I'm too lazy to implement it and to be honest it's not worth the work.