I think I may have found how to make it work. I tried a couple older drivers for 8139too.o. I tried the module from the 2.4.26 modules and 2.4.32 modules. The xx.26 version failed completely, but the 2.4.32 worked. I now have connection through my NEW system. The file sizes for the 2.4.32 and the 2.4.34 versions are the same, so I thought there wouldn't be a difference, but being desperate, I tried it anyway, and it loaded good, and I was able to get IP connectivity both ways through the router, and shorewall was able to start up.
I'm still getting an error when I try to ping eth1 eth2 interfaces, even though I can ping the devices on that network. The devices on the eth1 segment can ping the interface too. The error is "ping: send to: Invalid argument". So far it doesn't seem to be disrupting anything, but I'd like to figure it out if I can. The ping error appears both prior to starting shorewall as well as after starting shorewall. _____ From: Brad Klinghagen [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2008 1:14 AM To: 'leaf-user@lists.sourceforge.net' Subject: RE: [leaf-user] RealTek RTL8100 NIC Driver Well I tried once again to get my new system working, and I've tried several different things to make it happen, and I've been stymied each time. I've attached some new config, debug, error, and log data to try and give you as complete a picture as I can. To help understand what I'm trying to do, I'll give a little background. I'm trying to move >From OLD system: PII 300MHz, 128 MB RAM Standard CDROM drive 1GB hardrive 2 NICs: Intel Etherpro 10/100 cards (using mii & eepro100 drivers) Eth0: conection to ISP, collects IP via dhcpcd (has been working for years) Eth1: static IP address 10.0.0.1 network 10.0.0.0/24 IDE to Compact Flash socket To NEW system: Acrosser AR-M9952 (micro box embedded PC) AMD GX466 Chipset NS Geode CS5535 256 MB RAM BIOS: Award (supported OS included varieties of Windows, Linux 6.5 and above) 3 NICs: Realtek RTL8100C (10/100) x 3 1 compact flash socket: 2 USB Ports USB 1.1 The hardware configuration are a little different, but I was able to use the same LEAF config for both installations, except for the differences in LEAFCFG location (syslinux.cfg), PKGPATH (LEAF.cfg), and /etc/modules (different NIC drivers). I used a compact flash in the OLD system, and copied the LEAF config to it, booted off that configuration with the OLD system, made the necessary changes for the NEW system, then removed the compact flash from the OLD and installed it into the NEW. The LEAF configuration works perfectly on the old system. But when I place it on the new system, I am unable to get network connectivity. When looking at the drivers (crc32,mii,8139too), it appears that they load properly and are able to identify (MAC address, and IRQ assignment) and drive the NICs. However when it comes to "attaching" and IP address to them, it seems to fail, whether it's using dhcpcd for eth0, or static for eth1 & eth2. I've tried the different drivers, but the NICs aren't even recognized. I've also tried stripping the LEAF packages down to a minimum, and it still doesn't work. I changed dhcpcd to pump just to make sure there wasn't a problem with dhcpcd. Pump didn't work either (dhcpcd works well in the OLD system). For awhile, Erich pointed out I was using the wrong version of Linux, so I corrected that, but to no avail. I also found the RJ45 ports were mislabeled on the outside, they were in reverse order (2 was 0, 1 was 1, and 0 was 2); I corrected for that, and still doesn't work. There is one possibility - though I think it's remote. I just noticed Acrosser's docs state the NIC is RTL8100C but when the 8139too driver loaded, it recognized as 8100D. Could that be a problem? Would I possibly need an older driver (I tried the 8139cp and it didn't work at all). I'd really like to get this working if I can - it's getting to crunch time. I need to find a small embedded system such as this to install for a few friends. I thought this would work (and still hope for a Hail Mary). If it doesn't, I need to find alternatives (one that is known to work with LEAF, and looks professionally manufactured). Does anyone know of any alternatives? Thanks for any help, bpk ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
