From owner-freebsd-arch@FreeBSD.ORG Tue Mar 14 11:10:12 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D933116A425 for ; Tue, 14 Mar 2006 11:10:12 +0000 (UTC) (envelope-from liladude@aruba.it) Received: from vsmtp21.tin.it (vsmtp21.tin.it [212.216.176.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18D4643D53 for ; Tue, 14 Mar 2006 11:10:12 +0000 (GMT) (envelope-from liladude@aruba.it) Received: from [192.168.1.2] (87.2.251.219) by vsmtp21.tin.it (7.2.072.1) id 4405C90700A2AE88; Tue, 14 Mar 2006 12:09:42 +0100 Message-ID: <4416A49A.6070206@aruba.it> Date: Tue, 14 Mar 2006 12:10:18 +0100 From: Lila User-Agent: Mozilla Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: "M. Warner Losh" References: <44140E09.3000203@aruba.it> <20060313.134509.25161363.imp@bsdimp.com> In-Reply-To: <20060313.134509.25161363.imp@bsdimp.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-arch@freebsd.org Subject: Re: Neteasy DRP-32TXD ethernet problems on FreeBSD 6.0 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2006 11:10:13 -0000 Thanks for your answer. I tried to kldload some if_ drivers, but all of them already exist, because I am using the GENERIC kernel where all of them are already setted. I was waiting to find the good one before actually recompiling kernel. I thought good one should be if_de, since my card is setted under the tulip driver on linux... Maybe I just need to find a way to tell kernel what driver my card need... but I don't know where I should start. I wonder if having this card stated as D-Link insted of NetEasy in pci_vendors list can be the problem. If I could find a way to tell kernel they are the same thing I may be able to solve this problem. Any idea? Lila M. Warner Losh ha scritto: > In message: <44140E09.3000203@aruba.it> > Lila 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: at device 0.0 (no driver attached) > : > : but no driver attached and it's not displayed with ifconfig -a: > : > : plip0: flags=108810 mtu 1500 > : lo0: flags=8049 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 >