Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 3120 - Additional kernel modules should be preserved at kernel recompilation
Summary: Additional kernel modules should be preserved at kernel recompilation
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: x86-kernel@gentoo.org (DEPRECATED)
URL:
Whiteboard:
Keywords:
: 30971 (view as bug list)
Depends on:
Blocks: 1477
  Show dependency tree
 
Reported: 2002-05-28 12:52 UTC by Alexander Holler
Modified: 2003-10-19 13:21 UTC (History)
6 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Holler 2002-05-28 12:52:39 UTC
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.
Comment 1 Michael Cohen (RETIRED) gentoo-dev 2002-06-05 08:57:16 UTC
I'll look at it. good point.
Comment 2 Michael Cohen (RETIRED) gentoo-dev 2002-06-05 08:58:17 UTC
but note, you need to recompile modules when you recompile a kernel anyways.
Comment 3 Alexander Holler 2002-06-05 09:31:06 UTC
Why? 
Comment 4 Brandon Low (RETIRED) gentoo-dev 2002-09-06 17:45:23 UTC
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.  
Comment 5 Alexander Holler 2002-09-11 14:51:05 UTC
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.  
Comment 6 Alexander Holler 2002-09-23 07:34:53 UTC
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?  
  
  
Comment 7 Andrew Aylett 2002-09-28 11:00:09 UTC
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.
Comment 8 Brandon Low (RETIRED) gentoo-dev 2003-01-09 14:43:56 UTC
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.
Comment 9 Tony Murray 2003-10-01 05:39:23 UTC
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
Comment 10 Arcady Genkin (RETIRED) gentoo-dev 2003-10-03 14:02:39 UTC
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.
Comment 11 Martin Holzer (RETIRED) gentoo-dev 2003-10-12 09:22:41 UTC
*** Bug 30971 has been marked as a duplicate of this bug. ***
Comment 12 Tim Yamin (RETIRED) gentoo-dev 2003-10-19 13:21:13 UTC
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.