Redhat 7.1 'eepro100' and 'e100' drivers won't see 10BaseT network

Redhat 7.1 'eepro100' and 'e100' drivers won't see 10BaseT network

Post by Rahul Dhe » Fri, 07 Sep 2001 01:15:27



I have a Dell 1550 machine which supposedly contains an OEM Intel LAN
interface.  I installed Redhat Linux 7.1 on it.  (Actually the updated
one from www.tummy.com/krud.)  During installation the LAN interfaces
were recognized as needing eepro100 drivers.  Following Dell's
instructions, I replaced the reference to eepro100 in /etc/modules.conf
with e100 and rebooted.  But neither before or after doing the above
will the machine talk in any way with a 10BaseT hub, even though the
boot-time scripts show '[OK]' for eth0 (and eth1).

This machine is currently at a location with no 100BaseT, so I haven't
tested to see if it will do 100BaseT.

Is there any known problem with these machines related to 10BaseT?

Note that 'man eepro100' and 'man e100' turned up nothing, so it appears
that these particular device drivers are undocumented.  Nor did various
searches for e100 and eepro100 at www.redhat.com and www.dell.com turn
up anything relevant to this problem.

Nor could I find any argument to 'ifconfig' that was able to force the
LAN interface into 10BaseT mode.  I had figured that all LAN interfaces
described as 10/100 would autonegotiate, but this one apparently does
not.

Suggestions would be welcome.  Please post or email as you consider
appropriate, but not both. Thank-you.
--
Rahul

 
 
 

Redhat 7.1 'eepro100' and 'e100' drivers won't see 10BaseT network

Post by Kimmo Koivis » Fri, 07 Sep 2001 03:17:05


Quote:

>Note that 'man eepro100' and 'man e100' turned up nothing, so it appears
>that these particular device drivers are undocumented.  Nor did various
>searches for e100 and eepro100 at www.redhat.com and www.dell.com turn
>up anything relevant to this problem.

>Nor could I find any argument to 'ifconfig' that was able to force the
>LAN interface into 10BaseT mode.  I had figured that all LAN interfaces
>described as 10/100 would autonegotiate, but this one apparently does
>not.

Try modinfo -p driver
to find out which options can be passed to the driver with modprobe
more information:
man modinfo
man modprobe

br Kimmo Koivisto

 
 
 

Redhat 7.1 'eepro100' and 'e100' drivers won't see 10BaseT network

Post by Rahul Dhe » Fri, 07 Sep 2001 04:24:42



Quote:Koivisto) writes:
>>Note that 'man eepro100' and 'man e100' turned up nothing, so it
>>appears that these particular device drivers are undocumented....
>Try modinfo -p driver
>to find out which options can be passed to the driver with modprobe

Cool!  I got some info.  But I don't see any mention of 10BaseT.

  # modinfo -p eepro100
  debug int
  options int array (min = 1, max = 8)
  full_duplex int array (min = 1, max = 8)
  congenb int
  txfifo int
  rxfifo int
  txdmacount int
  rxdmacount int
  rx_copybreak int
  max_interrupt_work int
  multicast_filter_limit int

  # modinfo -p e100
  TxDescriptors int array (min = 1, max = 8)
  RxDescriptors int array (min = 1, max = 8)
  XsumRX int array (min = 1, max = 8)
  e100_speed_duplex int array (min = 1, max = 8)
  PhoneLinePower int array (min = 1, max = 8)
  PhoneLineSpeed int array (min = 1, max = 8)

Could it be that these drivers support only 100BaseTX connections?
--
Rahul

 
 
 

Redhat 7.1 'eepro100' and 'e100' drivers won't see 10BaseT network

Post by Bodo Egger » Fri, 07 Sep 2001 05:30:51



>   # modinfo -p eepro100
[...]
> Could it be that these drivers support only 100BaseTX connections?

---/usr/src/linux/drivers/net/eepro100.c---
/* 'options' is used to pass a transceiver override or full-duplex flag
   e.g. "options=16" for FD, "options=32" for 100mbps-only. */

if ((option >= 0) && (option & 0x70)) {
        printk(KERN_INFO "  Forcing %dMbs %s-duplex operation.\n",
                                   (option & 0x20 ? 100 : 10),
                                   (option & 0x10 ? "full" : "half"));
---
options=64 seems to be debug.

HTH
--
I know what I'm doing... can you please teach me?

 
 
 

Redhat 7.1 'eepro100' and 'e100' drivers won't see 10BaseT network

Post by Rahul Dhe » Fri, 07 Sep 2001 10:09:20



Quote:>---/usr/src/linux/drivers/net/eepro100.c---
>/* 'options' is used to pass a transceiver override or full-duplex flag
>   e.g. "options=16" for FD, "options=32" for 100mbps-only. */
>if ((option >= 0) && (option & 0x70)) {
>        printk(KERN_INFO "  Forcing %dMbs %s-duplex operation.\n",
>                                   (option & 0x20 ? 100 : 10),
>                                   (option & 0x10 ? "full" : "half"));

Great!  So I see that there is a bit that forces 100 Mbps or 10 Mbps
operation.  Thanks for that pathname reference -- I would not have
easily found it, since I don't believe I have the source tree populated
on this machine.  I assume I will also find an e100.c file somewhere
nearby.

The Micrososft people are clearly wrong.  Linux *IS* well-documented,
once you know where to go. :-)
--
Rahul

 
 
 

Redhat 7.1 'eepro100' and 'e100' drivers won't see 10BaseT network

Post by suresh kodat » Fri, 07 Sep 2001 12:42:31



> I have a Dell 1550 machine which supposedly contains an OEM Intel LAN
> interface.  I installed Redhat Linux 7.1 on it.  (Actually the updated
> one from www.tummy.com/krud.)  During installation the LAN interfaces
> were recognized as needing eepro100 drivers.  Following Dell's
> instructions, I replaced the reference to eepro100 in /etc/modules.conf
> with e100 and rebooted.  But neither before or after doing the above
> will the machine talk in any way with a 10BaseT hub, even though the
> boot-time scripts show '[OK]' for eth0 (and eth1).

If it shows that the interface is up it could have loaded proper drivers
and initialization is ok.
Can u provide the output of /sbin/ifconfig ?.

what exactly do u mean by 'talk' ?, is your machine is not able to access
any other machine connected to the same hub?
One reason  for this could be the subnet mask. check you have proper
default gateway and subnetmask .
-suresh

 
 
 

Redhat 7.1 'eepro100' and 'e100' drivers won't see 10BaseT network

Post by Rahul Dhe » Fri, 07 Sep 2001 15:03:03



>I have a Dell 1550 machine which supposedly contains an OEM Intel LAN
>interface.  I installed Redhat Linux 7.1 on it.  (Actually the updated
>one from www.tummy.com/krud.)  During installation the LAN interfaces
>were recognized as needing eepro100 drivers.  Following Dell's
>instructions, I replaced the reference to eepro100 in /etc/modules.conf
>with e100 and rebooted.  But neither before or after doing the above
>will the machine talk in any way with a 10BaseT hub, even though the
>boot-time scripts show '[OK]' for eth0 (and eth1).
>This machine is currently at a location with no 100BaseT, so I haven't
>tested to see if it will do 100BaseT.

More info:  When plugged into a 10BaseT hub, the link light on the hub
for that port remains off;  or sometimes flashes very briefly.

So I got a 10/100 switch and plugged the machine into that.  The link
light came on on the hub for that port and the machine was suddenly on
the network.

I am concluding for now that either the hardware or the software is
broken, and will do 100BaseTX but not 10BaseT.
--
Rahul

 
 
 

Redhat 7.1 'eepro100' and 'e100' drivers won't see 10BaseT network

Post by Bodo Egger » Fri, 07 Sep 2001 23:37:56



> The Micrososft people are clearly wrong.  Linux *IS* well-documented,
> once you know where to go. :-)

May the source be with you
--
I know what I'm doing... can you please teach me?
 
 
 

1. 2.5.47: Fix e100 driver bug on STL2 motherboard -- 'e100: hw init failed'

It seems e100 device on STL2 board is slower than other siblings.

Regards,
Louis Zhuang,
My opinions are my own and NEVER the opinions of Intel Corporation.

diff -Nur -X /root/dontdiff 47-kp/drivers/net/e100/e100.h
47-kp-fi/drivers/net/e100/e100.h
--- 47-kp/drivers/net/e100/e100.h       Mon Nov 11 11:28:07 2002

 #define E100_MAX_NIC 16

-#define E100_MAX_SCB_WAIT      100     /* Max udelays in wait_scb */
+#define E100_MAX_SCB_WAIT      5000    /* Max udelays in wait_scb */
 #define E100_MAX_CU_IDLE_WAIT  50      /* Max udelays in wait_cus_idle */

 /* HWI feature related constant */
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. Looking for /etc/services port monitoring tool

3. EEpro100/eepro module fails...attempting intel's e100 tarball but can't make kernel!

4. Job Opportunity-Atlanta, GA

5. 'ping' sees route but 'telnet' doesn't??

6. Best CD-RW drive?

7. RH 7.1 Cannot Find CDROM Even Though It Sees It as 'hdb'

8. W2K sweeps all before it...

9. 'make' won't work w/o '-f Makefile', which sucks.

10. m80 will 'boot' but won't 'reboot'

11. logon not seen by 'w' and 'who'?

12. Odd Solaris problem: file is seen by 'vi' but not 'ls' ???

13. Redhat 5.2 + kde- won't let me change to 'kwm'