Re: depmod: *** Unresolved symbols in /lib/modules (????huh)

2004-03-09 Thread Roger Chrisman
Side note. I wanted to mention here that the kernel-source-xxx/Documentation/Changes file lists 'module-init-tools' in Current Minimal Requirements. (It also warns *against* the use of 'the /usr/src/linux area' for compiling kernels in. I figure that warning does not apply to the meathod I am u

Re: depmod: *** Unresolved symbols in /lib/modules (????huh)

2004-03-09 Thread Roger Chrisman
> > When custom compiling kernel 2.6.3, I got all these depmod *** notices: > > > > depmod: *** Unresolved sybmols in /lib/modules/2.6.3.20040305-orca > > /kernel/drivers/acpi/thermal.ko > >  Are you sure you have module-init-tools installed, preferably from deb? Aha, I did *not* have module-init

Re: depmod: *** Unresolved symbols in /lib/modules (????huh)

2004-03-09 Thread David
On Mon, Mar 08, 2004 at 11:18:37PM -0800, Roger Chrisman wrote: > Hi all, > > When custom compiling kernel 2.6.3, I got all these depmod *** notices: > > depmod: *** Unresolved sybmols in /lib/modules/2.6.3.20040305-orca > /kernel/drivers/acpi/thermal.ko > > I read 'man depmod' and don't underst

Re: depmod: *** Unresolved symbols in /lib/modules (????huh)

2004-03-09 Thread GCS
On Mon, Mar 08, 2004 at 11:18:37PM -0800, Roger Chrisman <[EMAIL PROTECTED]> wrote: > When custom compiling kernel 2.6.3, I got all these depmod *** notices: > > depmod: *** Unresolved sybmols in /lib/modules/2.6.3.20040305-orca > /kernel/drivers/acpi/thermal.ko Are you sure you have module-init-

RE: depmod: *** Unresolved symbols in ...

2001-02-06 Thread Jason Mogavero
It sounds like you probably didn't move your old modules directory before installing your newly compiled modules. Do this move /lib/modules/2.2.17 to something like /lib/modules/2.2.17.old and go back to your kernel source tree and do 'make modules_install' again. This should clear up that