Date: Wed, 23 Nov 2005 23:38:28 -0900 From: Beecher Rintoul <akbeech@gmail.com> To: freebsd-current@freebsd.org Cc: Bill Paul <wpaul@freebsd.org>, Jeremie Le Hen <jeremie@le-hen.org> Subject: Re: Lasted NDIS wrapper for D-Link DWL-520+ on RELENG_6 Message-ID: <200511232338.43455.akbeech@gmail.com> In-Reply-To: <20051124062836.1558016A421@hub.freebsd.org> References: <20051124062836.1558016A421@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1138347.1Nv7pN153P Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 23 November 2005 09:28 pm, Bill Paul wrote: > Ok, there's something I just have to know: what the hell did you mean > in the Subject: line when you said "Lasted?" > > > Hi, > > > > I'm trying to use my PCI Wireless card with NDISulator from Bill Paul. > > I have tried to gather as much details as possible browsing through > > recent wpaul's posts, I hope this will be enough. If misfortune made me > > forget some details, I apologize for it and please, be indulgent and ask > > them. > > Fortune has nothing to do with it. > > I think you picked the wrong driver. > > Your device's PCI vendor/device/subsystem ID says: > > % none0@pci0:8:0: class=3D0x028000 card=3D0x3b041186 chip=3D0x9066104c = rev=3D0x00 > > hdr=3D0x00 % vendor =3D 'Texas Instruments (TI)' > > % device =3D 'TNETW1130(ACX111) 802.11b/g Wireless Cardbus/PCI > > Adapter' % class =3D network > > And you said you used the driver from: > > I'm trying to use the lastest driver for this card provided by D-Link : > > ftp://ftp.dlink.com/Wireless/dwl520+/Driver/dwl520+_drivers_307.zip > > Now, The first thing you should have done is to actually inspect the > .INF file. Like the self-documenting ndisgen(8) script tells you, this > is the file that actually contains the device ID information that the > Windows Plug & Play Mangler will use when trying to match a device > to a driver. The AIRPLUS.INF file says: > > [D-Link] > %AIRPLUS.DeviceDesc1% =3D AIRPLUS.8400, PCI\VEN_104C&DEV_8400&SUBSYS_3B00= 1186 > %AIRPLUS.DeviceDesc2% =3D AIRPLUS.8400, PCI\VEN_104C&DEV_8400&SUBSYS_3B01= 1186 > > Note that the PCI vendor ID (0x104c) matches your device, but the > device ID (0x8400) does not (yours is 0x9066). > > In this case, the .INF file tells Windows to look for two possible > devices. In reality, both devices use the same chip (vendor 0x104c, > device 0x8400), but there are two board variants (one with 0x3b001186, > the other 0x3b011186). The subsystem ID is really another vendor/device > ID combination (0x1186 is D-Link's vendor ID, 0x3b00 and 0x3b01 are > the device codes D-Link has assigned to their boards). Exactly what > the differences are between the board revs is anyone's guess. Maybe > they use the same Texas Instruments chip, but with slightly different > RF circuitry. Maybe they're really the same electronically, but D-Link > decided to give each production run their own ID code because they're > funny that way. > > In any case, not only do the vendor ID and device ID not match your board, > the subsystem IDs don't match yours either (0x3b041186). So this driver > is not the one that goes with your card. > > > I have to say that I'm quite puzzled by the fact that there seem to be > > multiple versions of the DWL-520+ card (at least two, one with an Ather= os > > chipset and one with a T.I. chipset) but strangely there is only one > > driver. Even stranger, the Drivers/WinXP/ directory contains only one > > .SYS file. I guess there must be some magic in it. > > Oh, _you're_ puzzled that there's multiple versions of the same card. > Welcome to _my_ world, buster. > > I want you to explain, in precise detail, why you're trying to download > a driver instead of using the one on the CD that came with the card. If > the reason is that you lost the CD, then you're being appropriately > punished for your carelessness. > > It's entirely possible that D-Link hasn't put the driver for your card > on their FTP server yet. > > "So what do I do now?" I hear you ask. > > You look on other vendors' sites for other cards based on the on > the Texas Instruments chipset and check their .INF files until you > find one where the vendor and device ID matches yours. And you remind > yourself to keep better track of your driver CDs in the future. > > -Bill I'm using the AG-530 with ndis and everything works correctly. I'll be happ= y=20 to send you the .inf and .sys files that I use if you want them. Beech =2D------------------------------------------------------------------------= =2D------------- Beech Rintoul - System Administrator - akbeech@gmail.com /"\ ASCII Ribbon Campaign | NorthWind Communications \ / - NO HTML/RTF in e-mail | 201 East 9th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \=20 =2D------------------------------------------------------------------------= =2D------------- --nextPart1138347.1Nv7pN153P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDhXwTVq19LUoGB+MRAu9mAJ9jCERvfhmQ0sMHWgw8MN0PJFWwygCgm9He 71eBdlBUFRxjD/CzL0YnE5c= =CdR4 -----END PGP SIGNATURE----- --nextPart1138347.1Nv7pN153P--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200511232338.43455.akbeech>