Re: Installation problem with Peabird card

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

Oh, I had _replaced_ config.opts by those lines. Now I _added_ the lines 
to the original config.opts, but it does not load anything at insertion: 
I get the same messages:

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

>>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.)
>
Actually, this time I don't seem to get any error:
Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed 
multicast|bytes    packets errs drop fifo colls carrier compressed
    lo:    7556      67    0    0    0     0          0         0     
7556      67    0    0    0     0       0          0
  eth0:       0       0    0    0    0     0          0         0      
900      15    0    0    0     0       0          0

>  
>
>>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?
>  
>
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.
 The RTL8139 does not use a MII transceiver.
 It does have internal MII-compatible registers:
   Basic mode control register   0x1100.
   Basic mode status register    0x782d.
   Autonegotiation Advertisement 0x01e1.
   Link Partner Ability register 0x41e1.
   Autonegotiation expansion     0x0001.
   Disconnects                   0x0000.
   False carrier sense counter   0xffff.
   NWay test register            0x0004.
   Receive frame error count     0x086d.

>>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
>  
>
This works fine: the count does increase regularly during a ping, and it 
does increase after each insertion of the card.


>  
>
>>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.
>  
>
Well, I did not manage to do that. What could possibly be wrong ?

Thanks very much for your help !

Vincent.