From owner-freebsd-mobile@FreeBSD.ORG Thu Jun 22 02:14:26 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2FE816A479 for ; Thu, 22 Jun 2006 02:14:25 +0000 (UTC) (envelope-from mraught@acm.org) Received: from sccrmhc14.comcast.net (sccrmhc14.comcast.net [63.240.77.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F36143D46 for ; Thu, 22 Jun 2006 02:14:25 +0000 (GMT) (envelope-from mraught@acm.org) Received: from www.raught.net (raught.net[68.36.102.177]) by comcast.net (sccrmhc14) with ESMTP id <2006062202142301400aon1ne>; Thu, 22 Jun 2006 02:14:24 +0000 Received: from [10.0.1.2] ([10.0.0.55]) by www.raught.net (8.12.9/8.12.9) with ESMTP id k5M1pLGS023696; Wed, 21 Jun 2006 21:51:21 -0400 (EDT) Message-ID: <4499FC84.5090205@acm.org> Date: Wed, 21 Jun 2006 22:12:20 -0400 From: "Mark A-J. Raught" User-Agent: Thunderbird 1.5.0.2 (X11/20060501) MIME-Version: 1.0 To: Colin Faber References: <4498A387.9040303@ruckusmail.com> In-Reply-To: <4498A387.9040303@ruckusmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-mobile@freebsd.org Subject: Re: Broadcom bcmwl5 NDIS driver and Dell D610 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2006 02:14:26 -0000 Colin Faber wrote: > Hello Folks, > > I'm having trouble getting my Dell D610 to recognize my Broadcom/Dell > miniPCI b/g wireless card. > > What I've done so far is as follows: > > 1) I copied the drivers that windows was using successfully from my > windows slice to my freebsd slice. > 2) I made sure that the .inf file was ascii, after that I generated > bcmwl5_sys.ko with ndisgen. > 3) I loaded the module generated, it loaded successfully. > > At this point I expected to see a ndis0 device popup, however sadly > this wasn't the case. > > Running after running pciconf -lv I think I've successfully identified > the miniPCI card as PCI:3:3:0 and the driver appears to see it, > however that's it. > > Below is the snippit of my system log after attaching the driver. > Below that is the pciconf -lv output > > pci0: driver added > pci1: driver added > pci2: driver added > pci3: driver added > found-> vendor=0x104c, dev=0x8038, revid=0x00 > bus=3, slot=1, func=5 > class=07-80-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0102, statreg=0x0210, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=19 > powerspec 2 supports D0 D1 D2 D3 current D0 > pci3:1:5: reprobing on driver added > found-> vendor=0x14e4, dev=0x4318, revid=0x02 > bus=3, slot=3, func=0 > class=02-80-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0106, statreg=0x0000, cachelnsz=0 (dwords) > lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=17 > pci3:3:0: reprobing on driver added > pci0: driver added > pci1: driver added > pci2: driver added > pci3: driver added > found-> vendor=0x104c, dev=0x8038, revid=0x00 > bus=3, slot=1, func=5 > class=07-80-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0102, statreg=0x0210, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=19 > powerspec 2 supports D0 D1 D2 D3 current D0 > pci3:1:5: reprobing on driver added > found-> vendor=0x14e4, dev=0x4318, revid=0x02 > bus=3, slot=3, func=0 > class=02-80-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0106, statreg=0x0000, cachelnsz=0 (dwords) > lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > intpin=a, irq=17 > pci3:3:0: reprobing on driver added > > > Now the pciconf -lv output: > > hostb0@pci0:0:0: class=0x060000 card=0x01821028 chip=0x25908086 > rev=0x03 hdr=0x00 > vendor = 'Intel Corporation' > device = '82915PM/GM/GMS, 82910GML Host Bridge' > class = bridge > subclass = HOST-PCI > pcib1@pci0:1:0: class=0x060400 card=0x00000088 chip=0x25918086 > rev=0x03 hdr=0x01 > vendor = 'Intel Corporation' > device = '82915PM/GM PCI Express Graphics Port' > class = bridge > subclass = PCI-PCI > pcib2@pci0:28:0: class=0x060400 card=0x00000040 chip=0x26608086 > rev=0x03 hdr=0x01 > vendor = 'Intel Corporation' > device = '82801FB/FR/FW/FRW PCI Express Port 1' > class = bridge > subclass = PCI-PCI > uhci0@pci0:29:0: class=0x0c0300 card=0x01821028 chip=0x26588086 > rev=0x03 hdr=0x00 > vendor = 'Intel Corporation' > device = '82801FB/FR/FW/FRW USB UHCI Controller' > class = serial bus > subclass = USB > uhci1@pci0:29:1: class=0x0c0300 card=0x01821028 chip=0x26598086 > rev=0x03 hdr=0x00 > vendor = 'Intel Corporation' > device = '82801FB/FR/FW/FRW USB UHCI Controller' > class = serial bus > subclass = USB > uhci2@pci0:29:2: class=0x0c0300 card=0x01821028 chip=0x265a8086 > rev=0x03 hdr=0x00 > vendor = 'Intel Corporation' > device = '82801FB/FR/FW/FRW USB UHCI Controller' > class = serial bus > subclass = USB > uhci3@pci0:29:3: class=0x0c0300 card=0x01821028 chip=0x265b8086 > rev=0x03 hdr=0x00 > vendor = 'Intel Corporation' > device = '82801FB/FR/FW/FRW USB UHCI Controller' > class = serial bus > subclass = USB > ehci0@pci0:29:7: class=0x0c0320 card=0x01821028 chip=0x265c8086 > rev=0x03 hdr=0x00 > vendor = 'Intel Corporation' > device = '82801FB/FR/FW/FRW USB 2.0 EHCI Controller' > class = serial bus > subclass = USB > pcib3@pci0:30:0: class=0x060401 card=0x00000050 chip=0x24488086 > rev=0xd3 hdr=0x01 > vendor = 'Intel Corporation' > device = '82801BAM/CAM/DBM (ICH2-M/3-M/4-M) Hub Interface to PCI > Bridge' > class = bridge > subclass = PCI-PCI > pcm0@pci0:30:2: class=0x040100 card=0x01821028 chip=0x266e8086 > rev=0x03 hdr=0x00 > vendor = 'Intel Corporation' > device = '82801FB/FR/FW/FRW AC '97 Audio Controller' > class = multimedia > subclass = audio > isab0@pci0:31:0: class=0x060100 card=0x01821028 chip=0x26418086 > rev=0x03 hdr=0x00 > vendor = 'Intel Corporation' > device = '82801FBM ICH6M LPC Interface Bridge' > class = bridge > subclass = PCI-ISA > atapci0@pci0:31:2: class=0x010180 card=0x01821028 chip=0x26538086 > rev=0x03 hdr=0x00 > vendor = 'Intel Corporation' > device = '82801FBM ICH6M SATA Controller' > class = mass storage > subclass = ATA > drm0@pci1:0:0: class=0x030000 card=0x20061028 chip=0x54601002 > rev=0x00 hdr=0x00 > vendor = 'ATI Technologies Inc' > device = 'Mobility Radeon X300' > class = display > subclass = VGA > bge0@pci2:0:0: class=0x020000 card=0x01821028 chip=0x167714e4 > rev=0x01 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'BCM5750A1 NetXtreme Gigabit Ethernet PCI Express' > class = network > subclass = ethernet > cbb0@pci3:1:0: class=0x060700 card=0x01821028 chip=0x8036104c > rev=0x00 hdr=0x02 > vendor = 'Texas Instruments (TI)' > class = bridge > subclass = PCI-CardBus > none0@pci3:1:5: class=0x078000 card=0x01821028 chip=0x8038104c > rev=0x00 hdr=0x00 > vendor = 'Texas Instruments (TI)' > device = '01821028 GemCore based SmartCard container' > class = simple comms > none1@pci3:3:0: class=0x028000 card=0x00051028 chip=0x431814e4 > rev=0x02 hdr=0x00 > vendor = 'Broadcom Corporation' > class = network > > > Any advice would is welcome. If I can get the wireless card working > and resolve an ACPI video issue I have, I will have just about > everything that I'm interested in, fully functional. > > Thank you > > -cf > > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" > I am currently running linux on my laptop with the broadcom card in it, but I had a couple problems when I first set it up in FreeBSD. Here are some tips I can give, hopefully they'll help. First I had 2 inf files available and I needed to use the ascii one (bcmwl5a.inf) and the sys file (bcmwl5.sys) with the other file (bcmwl5.inf) it appeared to work, but no love. This was about a year ago, so it may not matter now. The other main thing is to make sure your wireless is physically on. On my laptop I need to hold the Fn button and hit F2. That turns the wireless on and off. However, the first time I needed to go into the BIOS and set it to ON instead of Last Used (or LAST STATE, or somesuch) that leaves it in the last state it was in. After it started once, I could then change the BIOS back and it worked properly after that. Finally, make sure you are following the correct directions, the last time I needed to use NDIS I set it all up and it seemed to be correct, but you needed to use some wizard instead of the "classic" way. This also may have changed since then (again about a year ago). -mark