Re: kernel compile problem -- unresolved symbols

On Tue, Mar 12, 2002 at 11:24:22AM +, Alan James wrote: > This may be a daft question but when you load modules are you using inmod or Sorry I meant "insmod" there of course. Still modprobe is the one to use.

Re: kernel compile problem -- unresolved symbols

On Mon, Mar 11, 2002 at 04:53:52PM -0600, Christopher M. Jones wrote: > I'm compiling for a K7/Athlon/Duron system. As far as I can tell, -all- > modules come up with unresolved symbols. In other words, any module I try to > load comes up with unresolved symbols, whether part of the kernel, or >

Re: kernel compile problem -- unresolved symbols

I'm compiling for a K7/Athlon/Duron system. As far as I can tell, -all- modules come up with unresolved symbols. In other words, any module I try to load comes up with unresolved symbols, whether part of the kernel, or standalone. Clearly, I am doing something very wrong, though I haven't chang

kernel compile problem -- unresolved symbols

I am having a problem compiling from source 2.4.17 packaged for Debian. Using make-kpkg kernel_image in the source dir, all my modules come up with unresolved symbols. What causes this? What am I doing wrong? What should I do to fix it? Using gcc 2.95.4