Re: [PLUG] Compiling modules on Debian

[sean finney <seanius@seanius.net>]

hi jon,

On Mon, Jan 12, 2004 at 01:41:20PM -0500, Jon Nelson wrote:
> Running 'update-modules' after the install give me the same unresolved
> symbols errors.

i think i may have misunderstood a previous post.  are you only
compiling/installing the modules package?  if so, that could be the
cause of your problem.  when you compile a module, function symbols
are constructed with a checksum of the original source code into them.
that is, a function like net_foo would be net_foo_ca35e1 or somesuch.
if you compiled these modules with anything but the _exact same_ kernel
source and/or headers, you can get mismatched module names.  sometimes
you can still force insert them, but that's kind of a Bad Idea.

if this is the case, you have a couple options as i see it.  

- you can compile a whole new kernel, which would make all of this moot,
  but then again it would also make the point of a dynamically loadable
  module moot too
- get the original source/headers used to make your kernel and compile
  against that.  if the broadcom module only needs the kernel headers,
  that should be relatively painless, because the headers are available
  as a debian package (kernel-headers-2.4.18-bf2.4).  if it needs the
  source, it looks like there might be something funny going on, because
  if i understand correctly that's what you did in the first place,
  right?

by the way, what were those configure questions it asked you when you
didn't run it with --config=menuconfig?  that might provide some
insight if you can't build against the headers.



	sean

Attachment: signature.asc
Description: Digital signature