Re: Installation problem with Peabird card

On Wed, 3 Dec 2003, vincent wrote:

> 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 ?])

It's normal for _some_ distributions, but not all.  It's in there for a
reason, after all.  A warning message in 90% of the cases is better
than breaking in 10% of the cases.

> 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)

You are trying to use the 8139cp driver, which does not support your
chip.

> Then I manually insmod pci-scan and rtl8139

For CardBus cards, the PCMCIA subsystem *must* trigger the card scan.
Otherwise the "resources" (I/O,memory regions and IRQ) may not be
allocated correctly.

See
  http://www.scyld.com/network/updates.html
for the line to add to the /etc/pcmcia/config.opts file to make this happen

> 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

This looks OK.

> 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

What does /proc/net/dev report?
 (The 'ifconfig' program reads and summarizes /proc/net/dev info.  We
 need the raw numbers.)

> 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.

What does 'mii-diag' or 'rtl8139-diag -m' report?

> 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...
...
>  10:         17          XT-PIC  Texas Instruments PCI1211, eth0

Hmmm, doesn't look good.  Make certain that the count is increasing
  - once per packet.
  - at least once per card insert/eject

> 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) ?

That message (and perhaps the IRQ problem) will go aways when you load
the driver with the PCMCIA subsystem.

-- 
Donald Becker				[email protected]
Scyld Computing Corporation		http://www.scyld.com
914 Bay Ridge Road, Suite 220		Scyld Beowulf cluster system
Annapolis MD 21403			410-990-9993