[KLUG Members] 2.4.13 and tulip/8139 ethernet cards, was [Re: SGI XFS 2.4.9-7PR3, updated mkfs.xfs for >1TB]
Adam Tauno Williams
members@kalamazoolinux.org
Fri, 26 Oct 2001 13:00:49 -0400 (EDT)
>>Since we are in the reporting mood, I've got a tidbit to throw out.
>>I've been stuck on 2.4.3 on machines connected via either tulip or
>>8139 (SMC?) ethernet cards. Attempts to go to 2.4.11/2.4.12 failed as
>>these cards would work for awhile and then blow chunks.
>>Unloading/reloading the modules would make the cards work for awhile.
>>I've now tested 2.4.13 and the tulip driver seems stable (again),
>>not to mention the much smoother VM. Haven't checked the 8139 yet, but
>>I hope to get to that today.
>You may get a mis-leading error message when you do try it. I was using
A boot error message would have been nice. They ran for awhile and then "Lost
interrupt" and tossed the packets.
>the 8139too as a module under 2.4.3 and then moved forward to
>compiled-in 8139too under 2.4.12. At that point, all connection to the rest
>of the world was lost. Comparing dmesg's between the old kernel and the new
>one showed a version difference in 8139too and that led me to posting on the
>topic on LUGWASH. Sure enough, one of their tech-savvy crew volunteered
>a sincere, but ineffective, response.
>Last night, after trying out the above-mentioned suggestion, I resolved
>the matter entirely by issuing the command "dhcpcd".
>Doh!!!!!!! Instant network card!
Did you discover why dhcpcd not start automatically under 2.4.12?
Systems and Network Administrator
Morrison Industries
1825 Monroe Ave NW
Grand Rapids, MI. 49505