Installation problem with Peabird card

vincent <[email protected]> Wed, 03 Dec 2003 23:32:00 +0100
Newsgroups gmane.linux.drivers.realtek.devel
Message-ID <[email protected]>
Hello,

I don't manage to install a Peabird 10/100 ethernet PC card ``FP32TX'' 
which is a realtek 8139-based card, with cardbus connector.
The compilation of the modules against kernel 2.4.22 was OK (except that 
cb_shim gave an ``unresolved symbol'', but I understood from a previous 
message in this mailing list that this is somehow normal [am I correct ?])

When I insert the card: no beep is heard and no module loads.
dmesg says:
cs: cb_alloc(bus 2): vendor 0x10ec, device 0x8139
PCI: Enabling device 02:00.0 (0000 -> 0003)
8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
8139cp: pci dev 02:00.0 (id 10ec:8139 rev 10) is not an 8139C+ 
compatible chip
8139cp: Try the "8139too" driver instead.

Then I manually insmod pci-scan and rtl8139
[ I understood that these actually are the only modules I need. Am I 
right ? It seems that config.opts mentions cb_shim and cb_enabler but 
the first one gives an unresolved symbol and the second one is not found 
by insmod.]
This works fine.  dmesg shows:

pci-scan.c:v1.12 7/30/2003  Donald Becker <[email protected]> 
http://www.scyld.com/linux/drivers.html
rtl8139.c:v1.23a 8/24/2003 Donald Becker, [email protected].
 http://www.scyld.com/network/rtl8139.html
  The PCI BIOS has not enabled the device at 2/0!  Updating PCI command 
0003->0007.
eth0: RealTek RTL8139C Fast Ethernet at 0x4000, IRQ 10, 00:08:a1:53:f7:f8.
PCI: Setting latency timer of device 02:00.0 to 64

Now, I setup the ethernet device:
ifconfig eth0 192.168.1.2 up
and this still works fine: the ethernet device appears in the result of 
the command ifconfig.

Now, ping 192.168.1.1 (which is a valid IP number, which works with my 
other ethernet card)
says ``Destination host unreachable''
Moreover, the ifconfig shows some errors in RX packets:
eth0      Link encap:Ethernet  HWaddr 00:08:A1:53:F7:F8 
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:30 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:0 (0.0 b)  TX bytes:540 (540.0 b)
          Interrupt:10 Base address:0x4000

So here, I don't really know what to do.
Here is the output of the diagnostic program:
_root_# ./rtl8139-diag
rtl8139-diag.c:v2.11 4/22/2003 Donald Becker ([email protected])
 http://www.scyld.com/diag/index.html
Index #1: Found a RealTek RTL8139 adapter at 0x4000.
Realtek station address 00:08:a1:53:f7:f8, chip type 'rtl8139C'.
  Receiver configuration: Normal unicast and hashed multicast
     Rx FIFO threshold 256 bytes, maximum burst 256 bytes, 32KB ring
  Transmitter enabled with normal settings, maximum burst 256 bytes.
  Flow control: Tx disabled  Rx disabled.
  The chip configuration is 0x10 0x4d, MII full-duplex mode.
  No interrupt sources are pending.
 Use '-a' or '-aa' to show device registers,
     '-e' to show EEPROM contents, -ee for parsed contents,
  or '-m' or '-mm' to show MII management registers.

I read in the ethernet Howto that errors in the ``ifconfig'' output come 
most often from IRQ problem, so here is the /proc/interrupts showing IRQ 
10 assigned to eth0...
_root_# cat /proc/interrupts
           CPU0      
  0:      34833          XT-PIC  timer
  1:        675          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  5:          0          XT-PIC  ESS Solo1
 10:         17          XT-PIC  Texas Instruments PCI1211, eth0
 12:       1172          XT-PIC  PS/2 Mouse
 14:       8210          XT-PIC  ide0
 15:         13          XT-PIC  ide1
NMI:          0
LOC:          0
ERR:          0
MIS:          0

Where should I start ? What should I do to find out what the problem is 
more precisely ?
Could it be related to this message given by pci-scan ``The PCI BIOS has 
not enabled the device at 2/0! '' (but I didn't find anything related in 
the BIOS) ?

In any case, many thanks.

V.G.