Sun Aug 24 09:42:39 PDT 2003
I'm attempting to get hostap-0.0.4 working with RedHat 9 using the
2.4.20-20.9 kernel (which at the moment is the latest offered through
up2date). This was working with 2.4.20-19.9 and hostap-0.0.3, but when
I upgraded the kernel I had trouble compiling. I immediatedly grabbed
the latest hostap release to avoid struggling with old bugs. And indeed
the changelog says:
* fixed number of compilation issues (RH9 kernel, *.mod files to local
directory, 2.4.x compilation with CONFIG_MODVERSIONS, external
Unfortunately while the hostap driver builds and installs with no
trouble, modprobe reports unresolved symbols when attempting to load it.
As far as I can tell the problem is that only some kernel symbols used
by the hostap driver are converted according to the modversions system.
For example, from "nm /lib/modules/2.4.20-20.9/net/hostap.o":
The first routine shows up in /proc/ksyms, but the second doesn't. Or
rather it does, but as add_wait_queue_R53621d0f. Somehow add_timer was
correctly adapted for CONFIG_MODVERSIONS=y, but add_wait_queue wasn't.
All of the symbols modprobe claims are missing lack modversions tags in
hostap.o, while those unresolved in nm output but not modprobe have
them. This seems quite strange to me. I checked the output of "make
-n" but each gcc line has -DMODVERSIONS and the associated -include
option to pull in the modversions.h file. I've not yet discovered any
pattern that would make sense of this. What could be going wrong?
The following symbols don't have modversions tags and are listed as
unresolved by modprobe (the __this_module symbol is listed as unresolved
in hostap.o but doesn't trouble modprobe):
The following appear as unresolved in the hostap.o file, but with
appropriate modversions tags (these are not reported as unresolved by
Does this make sense to anyone? What might I be doing wrong here? Or
is this a bug caused by the interation of hostap and the latest RedHat
More information about the Hostap