Neteasy DRP-32TXD ethernet problems on FreeBSD 6.0

[M. Warner Losh]

In message: <44140E09.3000203 at aruba.it>
            Lila <liladude at aruba.it> writes:
: Hello!
: I'm tring to have my Neteasy DRP-32TXD PCMCIA ethernet working on my 
: Omnibook 900 laptop: the card seems to be recognized and prompt:
: 
: TUPLE: LINKTARGET [3]: 43 49 53
: Manufacturer ID: d11302ab
: Functions: Network Adaptor, Memory
: Function Extension: 0102
: Function Extension: 0280969800
: Function Extension: 0200e1f505
: Function Extension: 0301
: Product version: 5.0
: Product name: Neteasy | DRP-32TXD Cardbus PC Card | V1.0 |  |
: TUPLE: Unknown(0x04) [6]: 03 01 2a 00 00 00
: cardbus0: Opening BAR: type=IO, bar=10, len=0100
: cardbus0: Opening BAR: type=MEM, bar=14, len=0400
: CIS reading done
: cardbus0: Non-prefetchable memory at 88000000-880003ff
: cardbus0: IO port at 1000-10ff
: found->	vendor=0x1186, dev=0x1561, revid=0x11
: 	bus=2, slot=0, func=0
: 	class=02-00-00, hdrtype=0x00, mfdev=0
: 	cmdreg=0x0000, statreg=0x0290, cachelnsz=8 (dwords)
: 	lattimer=0xa8 (5040 ns), mingnt=0xff (63750 ns), maxlat=0xff (63750 ns)
: 	intpin=a, irq=10
: 	powerspec 2  supports D0 D1 D2 D3  current D0
: cardbus0: <network, ethernet> at device 0.0 (no driver attached)
: 
: but no driver attached and it's not displayed with ifconfig -a:
: 
: plip0: flags=108810<POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT> mtu 1500
: lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
: 	inet6 ::1 prefixlen 128
: 	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
: 	inet 127.0.0.1 netmask 0xff000000
: 
: I'm using i386/GENERIC kernel, so de driver (tulip) should be present.
: This card is listed in /usr/share/misc/pci_vendors under D-Link
: 
: 1186	D-Link System Inc
: 	...
: 	1561	DRP-32TXD CardBus PC Card
: 
: Any idea on how I can have this card working?
: all I can add is this card has driver attached (and is apparentely 
: activated)each time I kldload snd_emu10k1 ... but I think this is a pure 
: coincidence.

It is.  Each time you load a device driver, all unprobed devices are
presented to the newly loaded device driver....

I'd try the following drivers: dc, rl, re, fxp to see if any of them
work.  One should.  It is hard to know which one, but I'm guessing rl.

Warner