Hi, I've just stumbled over the fact, that a recompilation of the kernel (with modules_install) has deleted modules from additional packages (in my case alsa-driver). So I think such modules should go to /lib/modules/2.x-mykernel/misc and not to /lib/modules/2.x-mykernel/kernel/anywhere.
I'll look at it. good point.
but note, you need to recompile modules when you recompile a kernel anyways.
Why?
Make modules_install only kills those modules who have kernel symbols made from a different run of make dep, therefore they will need to be recompiled regardless of whether the physical files are left behind.
Why do I need to recompile additional modules, when I have changed something in the kernel (same kernel)? I've lived for years without recompiling every module (not included in the kernel) after every change of my kernelconfig.
As I dont't see the point why modules_install should delete external (not kernel) modules, I've reopened this bug. Why should I recompile alsa if internal kernel dependencies have changed?
To add to Alexander's comments, the Kernel option SET_VERSION_INFORMATION negates the need to recompile all modules every time the kernel is recompiled, and modutils has a nice way of searching for modules (when set up properly, which it should be) that takes modules built for the current kernel, the current version of the kernel, the current series, and generic modules. I don't think the ALSA install should put its modules where the kernel will wipe them... And I don't think it'd break anything to do that.
FYI I'm still waiting on the re-arrangement of the portage db stuff before I can solve this bug officially... kernel modules will be installed with SLOT=KV and will be able to be uninstalled then on a per-slot-basis by the user.
Excellent brandon, I was just going to post a bug about alsa-driver and lirc and multiple kernel versions. My problems was when I emerged the modules for one kernel, it uninstalls them for another. This improvement should fix that, perhaps portage needs a cavat for packages that have kernel modules... Tony
Why was this bug re-assigned from x86-kernel@gentoo.org to sound@gentoo.org? This problem is not alsa- or sound-specific, and concerns all kernel modules that are installed by ebuilds. Since x86-kernel don't seem to want this bug, I'm reassigning it to bug-wranglers for now.
*** Bug 30971 has been marked as a duplicate of this bug. ***
I'm resolving this as this is *not* a kernel problem. It is up to ebuild developers to get their ebuilds to a) utilize slots to allow multiple modules to be installed for multiple kernel versions and b) to use /lib/modules/${KV}/..., not /lib/modules/${KV}/kernel/... Most module ebuilds do that anyway, by now.