Have you tried the old_tulip.o driver?
As to the compile errors, it might be to do with the way the kernel
sources are installed. I havn't ever compiled modules outside the
kernel - all my hardware has just worked :-)
In any case, the 2.2.19 kernel is out, and contains many bug-fixes,
including local root exploits. Try upgrading to that, as a lot of
driver updates have gone in over the last little while.
Andrew Bartlett
David Rankin wrote:
>
> I need serious help! I can't compile the tulip.c driver I obtained from
> scyld.com. (I must be a complete idiot) I am not too familiar with gcc,
> so I think my problem may be not having the -I[location] information
> right or possibly a problem with header version conflicts.
>
> My setup:
>
> AMD K6 233/64M ram
> Fresh Install - Linux Mandrake 7.2 (odessy) Stock distro 2.2.17 kernel
> Linksys NC100 "network anywhere" 10/100 NIC
> tulip.c v0.92 4/17/200, downloaded from scyld.com
>
> ... NIC works fine in windoze ...
>
> The tulip.o that ship with LM7.2 doesn't work. The NIC documentation,
> mailing list archive info, and info at scyld.com say to download the
> current tulip.c driver file, along with pci-scan.c and kern_compat.h and
> then compile tulip.o and pci-scan.o and it should work.
>
> I CAN'T GET tulip.c or pci-scan.c TO COMPILE! --- I NEED HELP!
>
> What I've done:
>
> (1) downloaded tulip.c, pci-scan.c and kern_compat.h to
> /usr/src/linux/modules
> (2) tried to compile with the suggested options of:
> gcc -DMODULE -D__KERNEL__ -I/usr/src/linux/modules -Wall
> -Wstrict-prototypes -O6 -c tulip.c '[ -f
> /usr/src/linux/include/linux/modversion.h ] && echo -DMODVERSIONS'
>
> also tried many other combination, including
>
> gcc -DMODULE -D__KERNEL__ -O6 -c tulip.c
>
> All I get is a ton of error messages and I don't know enough to know
> what I'm doing wrong, but do know enough to know I need to ask for help
> with this one.
>
> The first few lines of the errors I get are shown below. I have attached
> a large dump of the errors to this message. I know it must be something
> simple, but I can't tell where things are going wrong. Basically, this
> is what happens:
--snip GCC barf--
GCC does that too you. The code and options need to be perfect...
I'd try the new kernel and see how that works.
Hope this helps,
Andrew Bartlett
--
Andrew Bartlett
[EMAIL PROTECTED]
