Mircea Luca wrote:
<snip>
>Usually this is not the kerenl against libc6 was compiled.in the
>specific case of hail it does match.
<snip>
> basically what I did since I recompile my kernel anyway immediately
> after any install was (as root)
>
> apt-get update
> apt-get install kernel-source-2.2.16-storm
> cd /usr/src
> ln -s kernel-source-2.2.16-storm linux
hmmmmmmm...
I installed the kernel source (I guessed non-ide), unpacked it into
/usr/src and refrained from linking the kernel source as indicated, out
of paranoia, mostly. The information that I have from the scyld site
recommends making a version.h file while in /usr/src/linux:
make include/linux/version.h
This results (surprise) in a version.h in
/usr/src/kernel-source-2.2.16-storm/include/linux/version.h
Anyway, the tulip.c file indicates that it should be compiled as so:
gcc -DMODULE -Wall -Wstrict-prototypes -O6 -c tulip.c
However, it struck me that there should be a way to indicate the path
for includes, so I compiled it as follows:
gcc -DMODULE -Wall -Wstrict-prototypes -O6 -c tulip.c
-I/usr/src/kernel-source-2.2.16-storm/include/
It now compiled happily, and without the usual 64K of error spew (when
stderr was redir'd into a file). However, the tulip driver apparently
wants something called pci-scan.o to be compiled and installed also.
These things are supposed to be compiled against the kernel headers, and
the kern_compat.h & pci-scan.h headers which are avail on the scyld
site. So I compiled pci-scan.c as I did for tulip.c above.
At this point the resulting object files are supposed to be installed
into their rightful location with:
install -m 644 pci-scan.o tulip.o /lib/modules/`uname -r`/net/
Again there were no apparent problems, but the next step failed
miserably. When (as directed) I did a insmod tulip.o, I got this:
tulip.o: unresolved symbol pci_drv_unregister
tulip.o: unresolved symbol pci_drv_register
Any guesses what I might have done wrong, before I forward this to
Donald Becker et al? There is some mention of compiling support for
pci-scan into the kernel. eek! Is this right? Can somebody at Storm
give me some feedback as to what the deal is with the tulip driver and
its support layer. If I want to load this as a module, do I have to
compile the pci-scan.o support into the kernel myself? I have been
referring to the various html pages available on the scyld site at:
http://www.scyld.com/network/
Perhaps someone at Storm is keeping track of the struggles with the LNE
cards and could shed some light on how the information on the
afformentioned site (allegedly _the_ source for the tulip drivers)
applies to the Storm2000 distro.
Time to render myself unconscious...
Thanks in advance for any and all help!
Mike
_______________________________________________
Stormlinux-users-list mailing list
[EMAIL PROTECTED]
http://www.stormix.com/community/lists/listinfo/stormlinux-users-list
