Feel free to move this post to another section if it belongs there!
I found a problem (potentially a bug) while upgrading kernels in manjaro. (I did use trizen, but think this may be a general problem)
But i am at a loss where to post this one.
and the actual running kernel has to be updated too. There is the following process:
- kernel(s) are replaced with the new kernel(s)
- modules-dir in /lib/modules are replaced by new modules-dir
- initramfs(s) are replaced with newly generated initramfs(s)
- because the actual running kernel does need access to its own (old) modules (while running), this modules-dir is not removed until after the next boot
- after the next successful boot this (old) modules-dir is deleted
To achieve this there is a file
/lib/modules/.old that keeps the name of the old module-dir that has to be removed.
In some situations there seems to be created an
.old file, when it should not. Then at next boot the dir
/lib/modules/5.14.10-1-MANJARO will be deleted. After that you can´t boot with this kernel any more.
This has happened to me at least 2 times in the last year. Each time i was at a loss why the dir
/lib/modules/x.x.x-xMANJARO suddenly was missing. But every time
- in the snapshot before the problem there was this
- And in the next snapshot the dir
I would like to discuss this with someone who knows the code. This can´t be upstream ? But where is the right place ? Development ? mhwd ?
This is update-related (trizen / pacman), but may be some script of MANJARO, and not of pacman.