ramdisk as root filesystem causes eth carrier errors -- SOLVED (interesting issue)
A while back I posted an issue about getting carrier errors on eth1 when using ramdisk as root filesystem, but it working perfectly when using an nfs-mounted root filesystem.
Well, it seems that the culprit is the tulip driver. After replacing it with the latest and greatest from scyld, the problem seems to have gone away. Apparently some of the tulip drivers had issues with reporting full duplex when the chip was really only at half duplex.
I am still at a loss to explain why the problem only showed up when using a ramdisk root filesystem, when the identical kernel and an identical nfs-mounted filesystem worked perfectly. Anyone have any ideas?
Chris
Signature · 4 lines
Chris Friesen | MailStop: 043/33/F10 Nortel Networks | work: (613) 765-0557 3500 Carling Avenue | fax: (613) 765-2986 Nepean, ON K2H 8E9 Canada | email: [email protected]