(02-01-2020, 10:47 AM)Der Geist der Maschine Wrote: Kernel Updates

I installed a small program and that triggered pacman to update the whole system including the kernel. During this process, I realized kernel updates could be handled better:

Kernel updates delete the old modules and so the newly installed modules don't match the running kernel. The running kernel can't now load any further modules. I believe modules should never be deleted by the system (or at least in a much smarter way).

(02-07-2020, 06:35 PM)Der Geist der Maschine Wrote:

(02-01-2020, 10:47 AM)Der Geist der Maschine Wrote: Kernel Updates

I installed a small program and that triggered pacman to update the whole system including the kernel. During this process, I realized kernel updates could be handled better:

Kernel updates delete the old modules and so the newly installed modules don't match the running kernel. The running kernel can't now load any further modules. I believe modules should never be deleted by the system (or at least in a much smarter way).

This becomes quite annoying. How do you guys work around this issue?

I can't even insmod a new module with the right path to it  in the old, running, kernel as it refuses to load modules from another kernel version.

(02-08-2020, 05:06 AM)Idaho Wrote: Has the sound output bug been fixed by an update yet or will it be fixed in a future release?

(02-08-2020, 08:28 AM)llsf Wrote:

(02-07-2020, 06:35 PM)Der Geist der Maschine Wrote:

(02-01-2020, 10:47 AM)Der Geist der Maschine Wrote: Kernel Updates

I installed a small program and that triggered pacman to update the whole system including the kernel. During this process, I realized kernel updates could be handled better:

Kernel updates delete the old modules and so the newly installed modules don't match the running kernel. The running kernel can't now load any further modules. I believe modules should never be deleted by the system (or at least in a much smarter way).

This becomes quite annoying. How do you guys work around this issue?

I can't even insmod a new module with the right path to it  in the old, running, kernel as it refuses to load modules from another kernel version.

Well… a new kernel means you gotta reboot to remain up to date – probably a good way to nudge you in the right direction with regards to having things as recent as possible no matter what

More seriously, though: You can either downgrade the kernel again until you've loaded the modules you need (if this doesn't happen too often), or see if one of the pre-made solutions work for you, like: https://aur.archlinux.org/packages/kernel-modules-hook (haven't tested that one, no guarantees for anything).

--

On servers, I like only allowing pre-signed modules in my precious kernels anyway – this would probably make this all more hellish. I should fiddle around with that on a desktop Arch someday, just for shits and giggles

/edit

Btw, this might be as good a place as any (as in: it's the Manjaro-Thread): I've finally managed to collect some odds and ends and PKGBUILDS I've made / modified for my own use on the PBP with Manjaro/Arch at https://github.com/lsfxz/pinebookpro-things. They might be of use to someone else but me, so I thought I'd share them.

(02-01-2020, 06:43 AM)agD0i7rY Wrote: for those using the KDE version, updates to the Qt libraries should be avoided.
See this topic on the Manjaro forum: https://forum.manjaro.org/t/new-qt5-es2-packages-break-everything/121892/3?u=lushoutherif

(02-09-2020, 01:53 PM)flgram Wrote: What version of LibreOffice and Thunderbird is default in Manjaro ARM 19.12? (or how do I find out without installing :-)
I am not completely satisfied with the default Debian OS of my pbp, as LibreOffice is old and thunderbird not working.

(02-09-2020, 01:53 PM)flgram Wrote: Hi,
What version of LibreOffice and Thunderbird is default in Manjaro ARM 19.12? (or how do I find out without installing :-)
I am not completely satisfied with the default Debian OS of my pbp, as LibreOffice is old and thunderbird not working.

Regards