Hi, I've been setting up a Seawolf installation for a friend who has gotten sick of XP and 98... All has gone well except I can't get it to recognise his NIC.
Some careful hunting turned up the fact that the DFE-530TX (not the + version) uses the Via-Rhine I,II driver... but when I tried this driver, though the system tried a lot longer during boot to init eth0, it still was unsuccessful. The installation CD contains a 2.4.2-2 install, and I'm wondering if this is where the problem lies... I went to Donald Becker's driver site at http://www.scyld.com/network/ where I found source-code for new Via-Rhine drivers, which compiled successfully, but left me with a new question.. His new drivers separate the pci-scan code from the main driver code. If I use the newly compiled via-rhine.o and pci-scan.o, will RH know to use the pci-scan code, since every other net driver in the system incorporates its own pci-scanning code? Puzzling over this at 2am, I decided to search further before messing with things I don't really understand.. From D-Link's UK ftp site, I located source for a driver which incorporated the pci-scan code into the driver, as per 'normal'. However, attempts to compile this were unsuccessful. I ran the included makefile, which issues the following command... gcc -DMODULE -D__KERNEL__ -Wall -Wstrict-prototypes -O6 -I/usr/source/linux/ include -c via-rhine.c This results in the following output: In file included from via-rhine.h:16, from via-rhine.c:26: /usr/include/linux/modversions.h:1:2: #error Modules should never use kernel-headers system header /usr/include/linux/modversions.h:1:2: #error but headers from an appropriate kernel-source make: *** [via-rhine.o] Error 1 I am a total newbie in this area, and am uncertain of how to proceed from here. Can anybody help, or even throw some light on the subject? Garryck _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
