[vortex] cannot activate eth0 (3c59x [duh]) in RH8.0 dual boo t system

ZIGLIO Frediano Frediano.Ziglio@vodafoneomnitel.it
Mon Feb 3 11:28:01 2003


> 
> > > If you want to *force* your network to a certain speed 
> you NEED to do
> > > the same on BOTH sides. One side forced and the other on
> > > auto-negotiation will cause ongoing grief. IT'S BAD. 
> DON'T DO THAT. :)
> > > 
> > > Please read
> > >    http://www.cisco.com/warp/public/473/46.html
> > > for a detailed discussion of problems, failures and very 
> > > little succes.
> > > 
> > 
> > I know that this cause problems (our catalyst is setted 
> 100/Full, my card
> > should be 100/Full too instead of autonegotiate) but I 
> think that problem is
> > the driver.
> 
> Yes and no. The driver does what the EEPROM tells it to. The
> windows-driver ignores the EEPROM-config, and forces his own
> preferences. Which makes the EEPROM a worthless feature. 
> 

Windows driver use default setting from eeprom by default. If you impose
other preference it use setted preferences.

> The driver you're using looks in the EEPROM for it's config.
> 
> Using mii-tool doesn't change the config of the card. It modifies what
> the hardware advertises to it's link-partner. 
> 
> do a rmmod 3c59x ; modprobe 3c59x options=[x] to force a preference.
> 

It do not work. I used modprobe options=0x204,0x204 but with eeprom card
configured with 100/Full (with 3Com tools) the driver say "cable not
present" or similar (card setted with dhcp).

> 
> >  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.
> 
> I used to have some 200+ machines with various 3c905*-cards and Cisco
> catalyst switches. Lot's of trouble, until we removed all forced
> connections, replaced the 'bad' cables and let 
> auto-negotiation do it's
> job. 
> 
> If a correctly configured link doesn't choose to use 100Mbit, most of
> the times the cable is miswired. Many cables have their pairs laid out
> as 1&2, 3&4, 5&6, and 7&8. That's not right. It should be 
> 1&2, 3&6, 4&5,
> 7&8. EIA 568B is the right mapping, and 
> 
> http://www.ge.infn.it/calcolo/faq/rete/cat5cable.htm
> 
> gives you the right mapping. In Italian. :)
> 

This is not a big problem.. I'm Italian :)
However we use only bought patchs and the only problem I have is using
Linux.
All I want to do is setting card fixed to 100/Full (all network, about
thousand machines, are setted 100/Full)...
I'm not the network administrator but I don't think the problem is the wire.

Cards are all 3c905c. Follow partial "lspci -vn"

00:0f.0 Class 0200: 10b7:9200 (rev 6c)
	Subsystem: 10b7:1000
	Flags: bus master, medium devsel, latency 64, IRQ 10
	I/O ports at e400 [size=128]
	Memory at e9102100 (32-bit, non-prefetchable) [size=128]
	Expansion ROM at e7000000 [disabled] [size=128K]
	Capabilities: [dc] Power Management version 2

00:10.0 Class 0200: 10b7:9200 (rev 6c)
	Subsystem: 10b7:1000
	Flags: bus master, medium devsel, latency 64, IRQ 9
	I/O ports at e800 [size=128]
	Memory at e9101100 (32-bit, non-prefetchable) [size=128]
	Expansion ROM at e8000000 [disabled] [size=128K]
	Capabilities: [dc] Power Management version 2

freddy77

=================================
"STRICTLY PERSONAL AND CONFIDENTIAL

This message may contain confidential and proprietary material for the sole
use of the intended recipient. Any review or distribution by others is
strictly prohibited. If you are not the intended recipient please contact
the sender and delete all copies.
The contents of this message that do not relate to the official business of
our company shall be understood as neither given nor endorsed by it."

=================================