Wow. I've never seen this one before. The problem is that the kernel is doing multiple initializations of your EEPro NIC. It's right here in the boot/init messages:
> id: 0x74 io: 0x300 eth0: Intel EtherExpress Pro/10 ISA at 0x300, >00:aa:00:6b:26:13, IRQ 10, 10BaseT. > id: 0x74 io: 0x300 eth1: Intel EtherExpress Pro/10 ISA at 0x300, >00:aa:00:6b:26:13, IRQ 10, 10BaseT. > id: 0x74 io: 0x300 eth2: Intel EtherExpress Pro/10 ISA at 0x300, >00:aa:00:6b:26:13, IRQ 10, 10BaseT. > id: 0x74 io: 0x300 eth3: Intel EtherExpress Pro/10 ISA at 0x300, >00:aa:00:6b:26:13, IRQ 10, 10BaseT. > id: 0x74 io: 0x300 eth4: Intel EtherExpress Pro/10 ISA at 0x300, >00:aa:00:6b:26:13, IRQ 10, 10BaseT. > id: 0x74 io: 0x300 eth5: Intel EtherExpress Pro/10 ISA at 0x300, >00:aa:00:6b:26:13, IRQ 10, 10BaseT. > id: 0x74 io: 0x300 eth6: Intel EtherExpress Pro/10 ISA at 0x300, >00:aa:00:6b:26:13, IRQ 10, 10BaseT. > id: 0x74 io: 0x300 eth7: Intel EtherExpress Pro/10 ISA at 0x300, >00:aa:00:6b:26:13, IRQ 10, 10BaseT. >ne.c:v1.10 9/23/94 Donald Becker ([EMAIL PROTECTED]) >NE*000 ethercard probe at 0x320: 00 80 c8 1e fc d7 >eth8: NE2000 found at 0x320, using IRQ 11. >eth0: set Rx mode to 1 address. >eth1: unable to get IRQ 10. After assigning eth0 to eth7 to the same NIC, the kernel can't make eth1 work because the IRQ is already in use (by eth0). Your NE2000 is way down at eth8, as you can see near the end of the excerpt I quoted above. All of this behavior is sufficiently unusual that I don't know what to make of it offhand. Do you have more than one entry for the eepro module in /etc/modules? Is there something unusual about the NIC itself? Does reversing the order of the modules --so the NE2000 NIC gets configured first and made eth0 -- help any? I'm just fishing around here ... perhaps someone else has seen this bahavior before and will be able to suggest a specific fix. At 01:48 PM 2/10/02 -0800, Demian & Fiona Marshall wrote: >Trying to run Dachstein v1.0.2-1680 > >On boot, system recognizes and finds NICs >Receives DHCP configuration from Shaw cable service >On boot, get message: > Starting interface: eth1: unable to get IRQ 10 > SIOCSIFFLAGS: Resource temporarily unavailable > eht1 > >When trying to ping internal network, >system uses eth0 instead of eth1 > >Any idea what I am doing wrong? [diagnostics deleted] -- ------------------------------------"Never tell me the odds!"--- Ray Olszewski -- Han Solo Palo Alto, CA [EMAIL PROTECTED] ---------------------------------------------------------------- _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
