RE: cannot activate eth0 (3c59x [duh]) in RH8.0 dual boo t system
Bogdan Costescu <[email protected]>
| Newsgroups | gmane.linux.drivers.vortex.devel |
|---|---|
| Message-ID | <Pine.LNX.4.44.0302031547030.27729-100000@kenzo.iwr.uni-heidelberg.de> |
On Mon, 3 Feb 2003, ZIGLIO Frediano wrote: > > Please read > > http://www.cisco.com/warp/public/473/46.html > I know that this cause problems (our catalyst is setted 100/Full, my card > should be 100/Full too instead of autonegotiate) Well, maybe after reading it you might reconsider and set everything (yes, including the Cisco device) to autonegotiate. > but I think that problem is the driver. I experience many problems with > cards not in autonegotiate (driver say no cable or other, it work > ramdomly). The same card with eeprom setted correctly work perfectly > under windows. In my experience, the Windows driver ignores the EEPROM settings and tries to be smart; plus, the driver might be written with more information about the hardware than the one 3Com is giving us. The Linux driver uses the EEPROM settings because the EEPROM was put there exactly to keep these settings. -- Bogdan Costescu IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868 E-mail: [email protected] _______________________________________________ vortex mailing list [email protected] http://www.scyld.com/mailman/listinfo/vortex