On a system running SuSE SLES7.2 (2.4.7-19) with an Intel EtherPro 100 and a 4-port Adaptec Quartet66 card, I'm running into a problem where the network on the EtherPro works just fine, but none of the networks on the Adaptec work. The starfire driver loads fine and recognizes all 4 ports, based on the following output in messages: Aug 19 10:49:31 lsca0133 kernel: starfire.c:v1.03 7/26/2000 Written by Donald Becker <becker@scyld.com> Aug 19 10:49:31 lsca0133 kernel: Updates and info at http://www.scyld.com/network/starfire.html Aug 19 10:49:31 lsca0133 kernel: (unofficial 2.2/2.4 kernel port, version 1.03+LK1.3.3, July 05, 2001) Aug 19 10:49:31 lsca0133 kernel: eth1: Adaptec Starfire 6915 at 0xf8d18000, 00:00:d1:ef:f8:bd, IRQ 17. Aug 19 10:49:31 lsca0133 kernel: eth1: MII PHY found at address 1, status 0x7809 advertising 01e1. Aug 19 10:49:31 lsca0133 kernel: eth2: Adaptec Starfire 6915 at 0xf8d99000, 00:00:d1:ef:f8:be, IRQ 18. Aug 19 10:49:31 lsca0133 kernel: eth2: MII PHY found at address 1, status 0x7809 advertising 01e1. Aug 19 10:49:31 lsca0133 kernel: eth3: Adaptec Starfire 6915 at 0xf8e1a000, 00:00:d1:ef:f8:bf, IRQ 17. Aug 19 10:49:31 lsca0133 kernel: eth3: MII PHY found at address 1, status 0x7809 advertising 01e1. Aug 19 10:49:31 lsca0133 kernel: eth4: Adaptec Starfire 6915 at 0xf8e9b000, 00:00:d1:ef:f8:c0, IRQ 18. Aug 19 10:49:31 lsca0133 kernel: eth4: MII PHY found at address 1, status 0x7809 advertising 01e1. The ifconfig output shows the following: eth0 Link encap:Ethernet HWaddr 00:B0:D0:B0:32:CC inet addr:xxx.yyy.zzz.www Bcast:xxx.yyy.yyy.255 Mask:255.255.255.0 inet6 addr: fe80::2b0:d0ff:feb0:32cc/10 Scope:Link UP BROADCAST NOTRAILERS RUNNING MTU:1500 Metric:1 RX packets:2602437 errors:0 dropped:0 overruns:0 frame:0 TX packets:1973728 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:237982170 (226.9 Mb) TX bytes:175253138 (167.1 Mb) Interrupt:16 Base address:0x1000 eth1 Link encap:Ethernet HWaddr 00:00:D1:EF:F8:BD inet addr:aaa.bbb.ccc.ddd Bcast:aaa.bbb.ccc.255 Mask:255.255.255.0 inet6 addr: fe80::200:d1ff:feef:f8bd/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:14 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:17 Base address:0x8000 eth2 Link encap:Ethernet HWaddr 00:00:D1:EF:F8:BE inet addr:fff.ggg.hhh.iii Bcast:fff.ggg.hhh.255 Mask:255.255.255.0 inet6 addr: fe80::200:d1ff:feef:f8be/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:18 Base address:0x9000 When trying to ping another host on the private network (eth1), no packets arrive and the following shows up in messages: Aug 19 10:49:54 lsca0133 kernel: NETDEV WATCHDOG: eth1: transmit timed out Aug 19 10:49:54 lsca0133 kernel: eth1: Transmit timed out, status 00000000, resetting... Aug 19 10:49:54 lsca0133 kernel: Rx ring f6c5e000: 36c6d011 36c5d811 ...[excess data deleted] Aug 19 10:49:54 lsca0133 kernel: Tx ring f6c5f000: b10103d4 b10103d4 ...[excess data deleted] Any ideas on how to address this problem or what I may have missed on this setup? Thanks, Frank - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
