Re: modules not found after kernel recompile
On Wed, 21 Jul 2004 17:02:07 -0400, Wayne Topa <brittman@capital.net> wrote:
>
>
> Wim De Smet(kromagg@gmail.com) is reported to have said:
> > On Wed, 21 Jul 2004 12:17:40 -0600, CW Harris <charris@rtcmarketing.com> wrote:
> > > On Wed, Jul 21, 2004 at 07:55:27PM +0200, Wim De Smet wrote:
> > > > Hi,
> > > >
> > > [...]
> > > >
> > > > You normally don't need a modprobe.conf, everything should be in
> > > > /etc/modprobe.d. modprobe.conf is just an empty file on my system. I'm
> > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > Is this true? Mine (a mostly Sarge with module-init-tools 3.0-pre2-1) has:
> > >
> > > # This line loads the part of the modprobe configuration managed with
> > > # update-modules(8) and built from the contents of /etc/modprobe.d/.
> > > include /lib/modules/modprobe.conf
> > > ^^^^^^^^^^^^^^^^^^
> > > Which seems very important to me (not a GURU here).
> > >
> >
> > module-init-tools in sarge is 3.1-pre5. Maybe it has something to do
> > with the older version, or maybe you need this if you use udev or
> > something else. I haven't really looked around for info on the subject
> > but in any case I don't need it and that means with a somewhat typical
> > setup it shouldn't be required (I never pull any fancy stuff and I
> > have hardly ever messed with my modules config)
> >
> > cheers,
> > Wim
> >
> > P.S.: I think we're all waiting here for somebody with a bit more
> > knowledge to explain it to us after which we can say "ooooh, like
> > that" :-)
>
> aptitude show module-init-tools
> Description: tools for managing Linux kernel modules
> This package contains a set of programs for loading, inserting, and
> removing kernel modules for Linux (versions 2.5.48 and above). It
> serves the same function that the "modutils" package serves for Linux 2.4.
>
> NOTE: I am running testing with a bit of unstable with a 2.6.7
> kernel.
>
> dpkg -l ii module-init-tools 3.1-pre5-1 tools for managing Linux kernel modules
>
> less /etc/modules.conf
> ### This file is automatically generated by update-modules"
> #
> # Please do not edit this file directly. If you want to change or add
> # anything please take a look at the files in /etc/modutils and read
> # the manpage for update-modules.
> [ snip]
> ###############################################################################
> # Generic section: do not change or copy
> #
> # All HDDs
> probeall /dev/discs scsi_hostadapter sd_mod ide-probe-mod ide-disk ide-floppy DAC960
> alias /dev/discs/* /dev/discs
>
> # All CD-ROMs
> probeall /dev/cdroms scsi_hostadapter sr_mod ide-probe-mod ide-cd cdrom
> alias /dev/cdroms/* /dev/cdroms
> alias /dev/cdrom /dev/cdroms
>
> # All tapes
> probeall /dev/tapes scsi_hostadapter st ide-probe-mod ide-tape
> alias /dev/tapes/* /dev/tapes
>
> {snip many pages }
>
> If you are trying to use the 2.6.s kernels you 'do' need to load module-init-tools.
>
> :-) HTH, YMMV, HAND :-)
I don't know what you are trying to say. Yes, he needs
module-init-tools for a 2.6 kernel, that's what he is trying to
install. No he does not need a modprobe.conf (AFAIK).
See:
$ cat modprobe.conf
$
(eg nothing in there)
You can safely remove the modutils if you run a 2.6.x kernel.
In any case I have some more ideas (to the OP):
- modprobe checks for your modules in /lib/modules/`uname -r`. So
check uname -r to see if it does indeed correspond to the directory
name, as something might have gone wrong when setting an extraversion
or whatever.
- check in that directory to see that there is a modules.dep file,
maybe something went wrong in this stage.
greets,
Wim
Reply to: