I'm an idiot! I was getting this output when I loaded the module: PCI: Found IRQ 9 for device 01:07.0 PCI: Sharing IRQ 9 with 00:01.0 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html 01:07.0: 3Com PCI 3c900 Boomerang 10baseT at 0xecc0. Vers LK1.1.18 eth0: Dropping NETIF_F_SG since no checksum feature. PCI: Found IRQ 5 for device 01:0c.0 01:0c.0: 3Com PCI 3c905C Tornado at 0xec00. Vers LK1.1.18
I seen eth0 and assumed it meant it had configured eth0 but not eth1. Looking at it again now, it's clear that was a warning about the driver configuration for eth0. I never ran ip ad to verify which interfaces were configured and wasted a bunch of time looking for a bug that didn't exist. I guess I should have gone to bed when I first found the problem instead of pushing on in my sleep deprived state. Probably would have noticed I didn't actually have a problem a lot sooner! :( For the record, I had booted with the System Rescue CD from sysresccd.org and was able to configure both NICS without a problem on it, so I new it wasn't a hardware issue. I just assumed it was a 2.6 vs 2.4 kernel issue or a module option issue. As it turns out, it was a code id10t issue. At any rate, thanks everyone who responded. I guess at the least I've learned to double check with ip ad before assuming the worst. Oh, and I've learned that you can't use module aliases on Bering-uclib. ...Izzy Erkki Lintunen wrote: > > You can't because there isn't modutils tools of 2.4 kernel included in > Bering-uClibc or, what I can tell, in any of its ancestors for size > reasons, I guess. > > I have a box with two NICs run by 3c59x drivers on Bering-uClibc 3.1. > What I can remember, there wasn't any problems getting them > operational. Loading the module once was able to find both NICs. > > What about running some Linux LiveCD system on your box and checking, > if it can find the NICs? If it can't, then your problem is in hardware. > > Which reminds me of couple problems, I had with PCI-bus configurations > and 2.4 kernels. The last one was with PCI parity feature enabled in > BIOS, what prevented the second NIC to operate The second problem was > related to irq sharing (commonly IRQ 11) on PCI-bus, but can't > remember the fix. > > Kernels and modules do have extensive options by which most problems > can be solved ie. if hardware works ok, and even if it doesn't in case > of faulty/nonexistent defaults in BIOS, there is many kernel options > to get the hardware operational. The problem is that often it has been > most work in digging what available options are. > > Erkki > > on 25.7.2008 10:23 Izzy Blacklock wrote: >> I'm trying to configure a new router using Bering-uClibc 3.1. I have >> two nics that use the same driver 3c59x. Typing: >> >> insmod 3c59x >> >> loads the module, but only configures eth0. The output from insmod >> seems to indicate it found two cards though. All the docs I've found >> seem to say I need to set to module aliases to get the driver to load >> for both cards. >> >> alias eth0 3c59x >> alias eth1 3x59x >> >> The question is where do I put these lines on a leaf router? >> ...Izzy >> >> ------------------------------------------------------------------------- >> >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win >> great prizes >> Grand prize is a trip for two to an Open Source event anywhere in the >> world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> ------------------------------------------------------------------------ >> leaf-user mailing list: leaf-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/leaf-user >> Support Request -- http://leaf-project.org/ > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
