>About how old is the 3c509b in the non-working machine? On older and some
?newer 3c509b cards, the onboard clockchip has been known to fail. This can
>produce the symptoms you are describing here. You can be sure it's the
>clock chip if you've been having network troubles, such as many dropped
>packets, or the link light flickering at times.
I can't say off hand and the light is out of sight, but they should be no more
than 6 months apart and from the same source. I have no problems with it under
2.1.103.........
eth0 Link encap:Ethernet HWaddr 00:60:97:23:BC:ED
inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
txqueuelen:100
RX packets:7454 errors:0 dropped:0 overruns:0 frame:0
TX packets:4145 errors:0 dropped:0 overruns:0 carrier:0
Collisions:0
Interrupt:9 Base address:0x300
I do have one spare around, so I can try that and see, I also thought just that
I may also make sure that the IRQ is assigned to ISA in the bios in case there
is some such peculiar problem with 2.1.106 and that department. I've been
recently thinking hardware as both machines have had the exact same kernels and
networking software, compiation only differs for the CPU's, a Cyrix 233-MMX and
a PR200+.
I'll give it a try.
Thanks and Regards
--
... Sid Boyce...Amdahl(Europe)...44-121 422 0375
-----------------------------------
Any opinions expressed above are mine and do not necessarily represent
the opinions or policies of Amdahl Corporation.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu