Re: [Fwd: Kernel 2.4 problem with 3C905B NIC]
Edward Tandi <[email protected]>
| Newsgroups | gmane.linux.drivers.vortex.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 2003-07-10 at 21:40, Bogdan Costescu wrote: > On 10 Jul 2003, Edward Tandi wrote: > > > Is this not something "reserved" in the EEPROM ROM info? > > Yes. But do you have any means of interpreting "reserved" ? :-) No. But I think it means we can safely ignore it. > > The card failed to link with the hub. No connection whatsoever. So > > either the card or the driver is taking the full-duplex eeprom setting > > as gospel. > > For a hub you might try half-duplex, as this would have chances to > succeed. In any case, when the combination is not working, you should look > at the output from the diag tools to see if the MII registers look normal > (in which case the driver should do its job) or not (like your initial > situation). OK, this e-mail thread is getting a bit long in the tooth. Is there some driver improvement that can be achieved out of this, or should we close this now, perhaps updating the documentation to tell people to use the 3com tool if they have problems? > > Also, it looks like the latest version of the 3com tool will not allow > > me to set the eeprom back to how I had it before. > > If you really want to, you can use vortex-diag. But I don't think that > there is of any value... I've not found vortex-diag to be the most friendly of tools. Powerful tool for the device driver folks no doubt. Let me know if you need more info, otherwise, so long and thanks for all the fish. Ed-T. _______________________________________________ vortex mailing list [email protected] http://www.scyld.com/mailman/listinfo/vortex