eth0 detection problems (RH7, SMC EtherPower II PCI (9432))

eth0 detection problems (RH7, SMC EtherPower II PCI (9432))

Post by Bobo Jon » Sat, 30 Dec 2000 08:21:39



Hi,

I'm having problems getting my network card, an SMC EtherPower II PCI,
working properly under Redhat Linux 7.0. I downloaded then compiled the
required driver (epic100) from Donald Becker's web site
(http://www.scyld.com) using kgcc (instead of gcc because of well-known
problems with gcc in RH7). Next, I used `insmod` to insert the module into
my kernel, then I installed the driver using:

install -m 644 pci-scan.o epic100.o /lib/modules/`uname -r`/net/

Next, I modified my "/etc/modules.conf" file by adding the following:

alias eth0 epic100

These are the instructions I found in the Ethernet-HOWTO and associated
documents for the driver. However, during boot up, while linux runs the
"network" service it fails to detect my network card and times-out after
about 1 minute (that is, in prints [FAILED] rather than [OK] when trying to
detect eth0). I thought that I'd followed the instructs exactly, but
something is obviously wrong. I plan to use either pump or dhcpc after my
ethernet card is detected to connect to the internet -- is that relevant?

Here are the last few lines of what `dmesg` outputs:


eth0: SMSC EPIC/100 83c170 at 0xcc07d000, IRQ 11, 00:e0:29:0a:85:a3.
eth0: MII transceiver #3 control 3000 status 7809.
eth0:  Autonegotiation advertising 01e1 link partner 0001.

I'm new to linux and networking, but it seems as if the card *is* detected.
I don't know why at boot time the device detection is said to fail though.
In an effort to provide as much information as possible, I'll write all the
technical information I know how to retrieve from linux regarding my
devices:

`cat /dev/ioports` prints:

0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
02f8-02ff : serial(auto)
0376-0376 : ide1
03c0-03df : vga+
03f0-03f5 : floppy
03f6-03f6 : ide0
03f7-03f7 : floppy DIR
03f8-03ff : serial(auto)
d400-d413 : usb-uhci
d800-d807 : ide0
d808-d80f : ide1
cc040000-cc0400ff : 4
cc07d000-cc07d0ff : eth0

and `cat /proc/pci` contains this entry:

  Ethernet controller: SMC 9432 TX (rev 6).
      Fast devsel.  Fast back-to-back capable.  IRQ 11.  Master Capable.  
Latency=32.  Min
Gnt=8.Max Lat=28.
      I/O at 0xd000 [0xd001].
      Non-prefetchable 32 bit memory at 0xdf800000 [0xdf800000].

and `cat /proc/modules` contains:

epic100                10768   0
pci-scan                2616   0 [epic100]
ide-cd                 23628   0 (autoclean)
nls_cp437               3876   2 (autoclean)
vfat                    9404   1 (autoclean)
fat                    30688   1 (autoclean) [vfat]
lockd                  31176   1 (autoclean)
sunrpc                 52964   1 (autoclean) [lockd]
agpgart                18600   0 (unused)
mousedev                3660   0 (unused)
hid                    11424   0 (unused)
input                   2972   0 [mousedev hid]
usb-uhci               19052   0 (unused)
usbcore                42088   1 [hid usb-uhci]

That is all the information I can think of to supply. My system
configuration is such that Windows2000 and Linux run on the same machine (in
separate partitions). Windows reports the following information in the
device driver information tab (for the device's properties):

I/O Range: D000-D0FF
Mem Range: DF800000-DF800FFF
IRQ      : 11

(This information seems similar to that which Linux reports except that the
memory ranges are different. Is this a problem?)

If you have any ideas how resolve this problem please do write me. Any help
would be greatly appreciated. Thanks (and happy holidays)

Bobo

 
 
 

eth0 detection problems (RH7, SMC EtherPower II PCI (9432))

Post by Donald Beck » Sat, 30 Dec 2000 15:13:20




>I'm having problems getting my network card, an SMC EtherPower II PCI,
>working properly under Redhat Linux 7.0. I downloaded then compiled the
>required driver (epic100) from Donald Becker's web site
>(http://www.scyld.com) using kgcc (instead of gcc because of well-known
>problems with gcc in RH7). Next, I used `insmod` to insert the module into
...
>documents for the driver. However, during boot up, while linux runs the
>"network" service it fails to detect my network card and times-out after
>about 1 minute (that is, in prints [FAILED] rather than [OK] when trying to
>detect eth0). I thought that I'd followed the instructs exactly, but
>something is obviously wrong. I plan to use either pump or dhcpc after my
>ethernet card is detected to connect to the internet -- is that relevant?

>Here are the last few lines of what `dmesg` outputs:


>eth0: SMSC EPIC/100 83c170 at 0xcc07d000, IRQ 11, 00:e0:29:0a:85:a3.
>eth0: MII transceiver #3 control 3000 status 7809.
>eth0:  Autonegotiation advertising 01e1 link partner 0001.

This report means that the card isn't getting link beat.
The likely problem is with the cabling.

You can run 'mii-diag' to verify this:
  http://www.scyld.com/diag/index.html

--

Scyld Computing Corporation             http://www.scyld.com
410 Severn Ave. Suite 210               Beowulf Clusters / Linux Installations
Annapolis MD 21403

 
 
 

eth0 detection problems (RH7, SMC EtherPower II PCI (9432))

Post by Bobo Jone » Sun, 31 Dec 2000 05:49:29




> >eth0: SMSC EPIC/100 83c170 at 0xcc07d000, IRQ 11, 00:e0:29:0a:85:a3.
> >eth0: MII transceiver #3 control 3000 status 7809.
> >eth0:  Autonegotiation advertising 01e1 link partner 0001.

> This report means that the card isn't getting link beat.
> The likely problem is with the cabling.

> You can run 'mii-diag' to verify this:
>   http://www.scyld.com/diag/index.html

Donald, thanks for the reply. The first time I ran mii-diag I did get output
stating that the card wasn't getting link beat. But after I ran it again, I
got this output using "./mii-diag -v":


 http://www.scyld.com/diag/index.html
Using the default interface 'eth0'.
 MII PHY #3 transceiver registers:
   1000 782d 0181 4401 01e1 0021 0000 ffff
   ffff ffff ffff ffff ffff ffff ffff ffff
   0040 0018 ffff ffff ffff ffff ffff ffff
   ffff ffff ffff 003e ffff 0040 0000 1dc4.
 Basic mode control register 0x1000: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
   This transceiver is capable of  100baseTx-FD 100baseTx 10baseT-FD
10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Your link partner is generating 10baseT link beat  (no autonegotiation).
 MII PHY #3 transceiver registers:
   1000 782d 0181 4401 01e1 0021 0000 ffff
   ffff ffff ffff ffff ffff ffff ffff ffff
   0040 0018 ffff ffff ffff ffff ffff ffff
   ffff ffff ffff 003e ffff 0040 0000 1dc4.
 Basic mode control register 0x1000: Auto-negotiation enabled.
 Basic mode status register 0x782d ... 782d.
   Link status: established.
   Capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Vendor ID is 00:60:51:--:--:--, model 0 rev. 1.
   Vendor/Part: Quality Semiconductor (unknown type).
 I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 0021: 10baseT.
   Negotiation did not complete.

I can't decipher what this output means, so any help you can give will be
appreciated. Also, I'm not sure what you mean when you say that you believe
this is a cabling problem. Do you mean that there is an external physical
problem (such as a bad connector) from my modem to my ethernet card? Or,
instead, some hardware configuration problem? My system dual boots Windows
and Linux and I'm in Windows now -- so I don't think that the problem is
with any external physical contacts.

Thanks for your help,
Bobo

p.s. Happy new year!