Any Sluggers care to comment on why I had to perform the following 'dirty hack'
I rolled my own kernel (even used debian Kernel-package! ) and discovered it wasn't
finding my modules on boot up. I'd done update-modules and all that stuff, and it was
finding some of the modules... i.e
It found smbfs.o in /lib/modules/2.4.0-test7/fs/smb/
but wouldn't find sb and soundcore in /lib/modules/2.4.0-test7/drivers/sound/
Depmod wasn't searching those directories for some reason. Uname -r reported the right
name. /lib/modules/2.4.0-test7/modules.dep only listed the smbfs modules.
Intially I got the modules to load by including /lib/modules/2.4.0-test7/ in
/etc/modules.conf and this worked. Then I looked at the setup for the plain Vanilla
debian 2.2.17 kernel and found that by renaming my /lib/modules/2.4.0-test7/drivers to
be /lib/modules/2.4.0-test7/misc everything (depmod and subsequent bootup) worked fine
without having to explicitly put the path in modules.conf.
Is this just an incompatibility between the stable depmod and the newer kernel
source/modules setup?
Anyway, it works, I just thought I ask why it didn't in the first place? I need to
get my head around all this modules stuff as I will be installing a nvidia tnt2 with
its kernel drivers, and 'rolling my own' again in the near future.
Steve
<==============================================>
Never argue with idiots - they'll bring you down to their
level and then beat you with experience.
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
