bgodden
asked on
Forcing 10BaseT for eepro100
I've just installed Red Hat 5.1 on a Pentium Pro and can't get eth0 to intialize. I am using an Intel EtherExpress Pro 100B network card. I think, from reading lots of docs, that my problem may to two-pronged:
1. eepro100 driver uses the same IRQ as the Adaptec 2940.
2. I am using 10BaseT and I may need to load the driver as a module and force use of 10 MB ethernet because the NWay autonegotiation is not working.
I have read up on the documentation(Ethernet HOWTO) and there appears to be a solution, but I am too much of a newbie to figure it out.
Can anyone give me some advice to get the eth0 up and running?
Thanks much!
1. eepro100 driver uses the same IRQ as the Adaptec 2940.
2. I am using 10BaseT and I may need to load the driver as a module and force use of 10 MB ethernet because the NWay autonegotiation is not working.
I have read up on the documentation(Ethernet HOWTO) and there appears to be a solution, but I am too much of a newbie to figure it out.
Can anyone give me some advice to get the eth0 up and running?
Thanks much!
ASKER
Well, I got impatient and bought RH 5.2 and it appears auto-sensing for this has been fixed so it worked after install. This, however, is a excellent answer and I think would be helpful if anyone else digs it up.
One thing I would like you to add to it though is the answer to: "Are the options for the built-in driver used at the boot: prompt during boot-up or hard-coded somewhere else?"
Request acceptance for you answer and I will.
Cheers!
One thing I would like you to add to it though is the answer to: "Are the options for the built-in driver used at the boot: prompt during boot-up or hard-coded somewhere else?"
Request acceptance for you answer and I will.
Cheers!
ASKER
Well, I got impatient and bought RH 5.2 and it appears auto-sensing for this has been fixed so it worked after install. This, however, is a excellent answer and I think would be helpful if anyone else digs it up.
One thing I would like you to add to it though is the answer to: "Are the options for the built-in driver used at the boot: prompt during boot-up or hard-coded somewhere else?"
Request acceptance for you answer and I will.
Cheers!
One thing I would like you to add to it though is the answer to: "Are the options for the built-in driver used at the boot: prompt during boot-up or hard-coded somewhere else?"
Request acceptance for you answer and I will.
Cheers!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks vx
In most cases no transceiver override option need be set. A notable exception is when connecting to a older ethernet switch that operates in full-duplex mode but does not do NWay autonegotation. The driver options flags are recognized:
Hex Decimal Meaning
0x10 16 Force Full-Duplex operation (must be used with 0x20 or 0x40)
0x20 32 Force 100mbps-only operation
0x40 64 Force 10mbps-only
i.e.:
The option flags are passed as follows when loading the driver as a module
insmod eepro100.o debug=1 options=0x20,0,0x50
The option flags are passed as follows when using the driver as a built-in
ether=0,0,0x20,eth0 ether=0,0,0,eth1 ether=0,0,0x50,eth2
About the IRQ's: I don't think it really matters, I believe a have some double IRQ's in my system (with Intel EtherExpress100B!) as well.