faq or archive available ? - 8139b problem

Thu Mar 23 16:42:38 2000

hello everybody !

is there a faq or list archive available ?
sorry i'm not yet subscribed, please cc: me. thanks a lot !
if this *is* a faq, just ignore the rest and point me to some source
of enlightenment. :)

i have problems to get my lantech fastlink (based on the 8139b chip)
detected under 2.2.14.
no eth0: line in dmesg, ifconfig reports only loopback. when i
modprobe by hand, the module is labelled "unused" by lsmod and
ifconfig still doesn't find it. 
i have tried passing the address (0xa800) and the irq (10) to
modprobe, but without success.

on another box running a 2.2.10 kernel with the suse 6.3 hacks, the
card is listed when i run ifconfig. haven't been able to test it
further, though, since i only have these two hosts...

*one more strange thing:
when i run the DOS-based setup and test utility on both boxes, i get
rx errors on my 2.2.14 box.
(the number of packets sent = no. of packets received = no. of
receive errors) what does this tell me ?? (i have tried auto-detect
mode on both cards and all other modes - the problem only vanishes
when both are set to 10mbit and no duplex.)

i would appreciate any hints or clues....
find attached some diagnostics.

yours,

jörn

donald becker's diagnosis tool yields:

./rtl8139-diag -aa
rtl8139-diag.c:v1.01 4/30/99 Donald Becker
(becker@cesdis.gsfc.nasa.gov)
Index #1: Found a RealTek RTL8139 adapter at 0xa800.
RealTek chip registers at 0xa800
 0x000: d91c0000 000058df 00000000 00000000 00002000 00002000
00002000 00002000
 0x020: 00800400 00000044 00000010 00000240 00040000 01000000
0000fff0 00000000
 0x040: 78000000 00000000 c6cadf69 00000000 000f10c6 00000000
0001c100 00100000
 0x060: 1000000f 05e1782d 000140a1 00000000 00000004 000517c8
58fab388 a438d843.  No interrupt sources are pending.
 The chip configuration is 0x10 0x0f, MII half-duplex mode.  

./rtl8139-diag -e
rtl8139-diag.c:v1.01 4/30/99 Donald Becker
(becker@cesdis.gsfc.nasa.gov)
Index #1: Found a RealTek RTL8139 adapter at 0xa800.
Parsing the EEPROM of a RealTek chip:
  PCI IDs -- Vendor 0x10ec, Device 0x8139, Subsystem 0x10ec.
  PCI timer settings -- minimum grant 32, maximum latency 64.
  General purpose pins --  direction 0xc1  value 0x10.
  Station Address 00:00:1C:D9:DF:58.
  Configuration register 0/1 -- 0x4c / 0xc2.
 EEPROM active region checksum is 0898.    

./rtl8139-diag -mm
rtl8139-diag.c:v1.01 4/30/99 Donald Becker
(becker@cesdis.gsfc.nasa.gov)
Index #1: Found a RealTek RTL8139 adapter at 0xa800.
 The RTL8139 does not use a MII transceiver.
 It does have internal MII-compatible registers:
   Basic mode control register   0x782d.
   Basic mode status register    0x1000.
   Autonegotiation Advertisement 0x05e1.
   Link Partner Ability register 0x40a1.
   Autonegotiation expansion     0x0001.
   Disconnects                   0x0000.
   False carrier sense counter   0x0000.
   NWay test register            0x0004.
   Receive frame error count     0x0000.
 MII PHY #-1 transceiver registers:
   0000 0000 0000 0000 0000 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000.
 Basic mode control register 0x0000: Auto-negotiation disabled!
   Speed fixed at 10 mbps, half-duplex.
 Basic mode status register 0x0000 ... 0000.
   Link status: not established.
   Capable of <Warning! No media capabilities>.
   Unable to perform Auto-negotiation, negotiation not complete.
 This transceiver has no vendor identification.
 I'm advertising 0000:
   Advertising no additional info pages.
   Using an unknown (non 802.3) encapsulation.
 Link partner capability is 0000:.
   Negotiation did not complete.           

-- 
Jörn Nettingsmeier     
Kurfürstenstr. 49        
45138 Essen, Germany
 | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the
 |  body of the mail, include only the text:
 |   unsubscribe this-list-name youraddress@wherever.org
 | You will be unsubscribed as speedily as possible.