Redhat have this anal boot system where they have a file in
/lib/modules/2.2.x-xx
that the script that executes depmod goes looking for. If found it goes and
does depmod -a on THAT directory of modules rather than the freshly compiled
ones that matches your new kernel. Go and have a look in /etc/rc.d/rc.boot?
and have a look for a grep for this file in the place where depmod is executed
from..... That may explain everything....
Cheers,
Matthew Grant
>
>
> Christopher Thompson wrote:
>
> > Sanity check:
> >
> > When you recompiled your kernel, did you also do:
> > make modules
> > make modules_install
>
> Yes - I did. The build looked okay, and subsequent hammering on the
> kernel shows no obvious problems in compiled-in modules. Something's fishy with
> depmod... but I don't have the experience to troubleshoot the problem.
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jun 15 2000 - 21:00:20 EST