Remco Poelstra wrote:
Yes, tried that and it's the same here. But now it seems that it was not the combination of both drivers that rendered my network useless, but it was the eepro100 driver on it's own. I get a load of:
Mar 1 15:38:59 t-1-131 kernel: eth0: wait_for_cmd_done timeout!
Hm, you shouldn't rule out a hardware problem.
I use the eepro100 module in some cases instead of the e100, because e100 doesn't work with VPN (can't change MTU size), and I havn't had any problems with the eepro100 driver.
Mogens
-- Mogens Kjaer, Carlsberg A/S, Computer Department Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark Phone: +45 33 27 53 25, Fax: +45 33 27 47 08 Email: mk@xxxxxx Homepage: http://www.crc.dk
