From owner-freebsd-net@FreeBSD.ORG Sun Mar 16 09:42:40 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E34F10656C1 for ; Sun, 16 Mar 2008 09:42:40 +0000 (UTC) (envelope-from tedm@toybox.placo.com) Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [65.75.192.90]) by mx1.freebsd.org (Postfix) with ESMTP id E909D8FC14 for ; Sun, 16 Mar 2008 09:42:39 +0000 (UTC) (envelope-from tedm@toybox.placo.com) Received: from TEDSDSK (nat-rtr.freebsd-corp-net-guide.com [65.75.197.130]) by mail.freebsd-corp-net-guide.com (8.13.8/8.13.8) with SMTP id m2G9C87j085734; Sun, 16 Mar 2008 02:12:09 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Glen Barber" , , Date: Sun, 16 Mar 2008 01:13:21 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914 In-Reply-To: <200803132256.01197.glen.j.barber@gmail.com> Importance: Normal X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (mail.freebsd-corp-net-guide.com [65.75.192.90]); Sun, 16 Mar 2008 02:12:09 -0700 (PDT) Cc: Subject: RE: ndis0 no link on 6.3-RELEASE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Mar 2008 09:42:40 -0000 > -----Original Message----- > From: owner-freebsd-questions@freebsd.org > [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Glen Barber > Sent: Thursday, March 13, 2008 6:56 PM > To: freebsd-net@freebsd.org; freebsd-questions@freebsd.org > Subject: ndis0 no link on 6.3-RELEASE >=20 >=20 > Hello everyone. =20 >=20 > First off, sorry for the double post, but I'm not 100% certain at=20 > where this=20 > post belongs. =20 >=20 > I've found via Google many problems with ndis0 and failure to=20 > find a link in=20 > 6.3-RELEASE, without resolution. So here's my setup. >=20 > I'm using a Broadcom 4318 chipset, with drivers created from=20 > ndisgen. If you=20 > need more specific information on the drivers, I'll be more than happy = to=20 > provide information, however I believe it to be irrelevant at=20 > this moment, as=20 > I have used more than one driver version, with the same results. =20 >=20 > In 6.3-RC1 and below (tested in 6.2-RELEASE, and all -STABLE releases = in=20 > between), my ndis0 adapter works as exptected, using WPA and=20 > DHCP. I can't=20 > pinpoint exaclty what changed (I've check in /usr/src/UPDATING,=20 > as it seemed=20 > to be most relevant), with no avail to finding anything regarding=20 > either wpa=20 > or dhclient. =20 >=20 > Since an upgrade to 6.3-RELEASE (both, via csup and a fresh=20 > install off of=20 > cd), I generate my ndis module, create an /etc/wpa_supplicant.conf,=20 > leaving /etc/dhclient as default, and am prompted with: > ndis0: no link.......... giving up >=20 > Upon 'kldunload bcmwl5.ko; kldload bcmwl5.ko', my ndis0 card=20 > looses all WPA=20 > capabilities. =20 >=20 > What seems to me to be the interesting part is this: > If I 'csup' to 6.3-RELEASE from -RC1, and build a kernel, the=20 > problem does not=20 > occur -- as long as I do not 'buildworld'. However, once I = 'buildworld;=20 > installworld', I am faced with the same problems as if I had installed = > 6.3-RELEASE from cd. =20 >=20 > I would really like to figure out what is causing this (both for=20 > myself, and=20 > the other affected ndis0 victims), but I'm not sure where to look --=20 > dhclient, wpa_supplicant or ndis itself. Any other information I = could=20 > provide, please let me know. =20 >=20 Hi Glen, I just setup my laptop with a wireless card a couple weeks ago and FreeBSD 6.3-RELEASE. (it's an older Toshiba) I went through a total of 5 different wireless cards before I found one that I was able to get working ndis drivers from ndisgen. Fortunately there's a used computer place near here (freegeek.org) that had a box of pcmcia wireless cards of all different makes and models, which kindly allowed me to plunk down my laptop (which dual-boots between Windows 98 and FreeBSD) and they have wireless. So I would pick a card out of their bin, boot into Windows, download the Windows driver, make sure the card worked under Windows, then boot into FreeBSD and mount the Windows partition, copy over the Windows driver and inf file to the FreeBSD side, run ndisgen and then try loading the driver. With some cards, the driver wouldn't even activate the card. With other cards, the driver would allow me to list the wireless nodes then panic the system when I tried associating. The card that did work was a Realtek-based card. And, it did not work with the most current Windows drivers from the Realtek website, it worked with the Windows drivers that were from a couple years ago. (I found this out quite by accident) Fortunately, they DID also have a number of the Wavelan cards - these are supported natively with the wi0 driver - that worked out of the box. Those cards are only 802.11b though so I kept at it with ndisgen and the newer cards. The interesting thing is that the original wireless card I had in the Toshiba - a Texas Instruments-based chipset model - never really quite worked properly in the Toshiba under Windows. I put it into a different laptop I owned - a Thinkpad, and it worked great in that. Unfortunately, in your case, nothing has changed with ndisgen since 2006 (see = http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/ndiscvt/ ) so it's not that, it's something else in the system that changed. Start with the basics. Copy your bcmwl5.ko into /boot/modules then in loader.conf put bcmw15_load=3D"YES" and reboot the system, check dmesg, and see if it's even loading Next put in /etc/rc.conf "ifconfig_ndis0=3D"inet 192.168.1.1 ssid = myssid" and see if it even comes up at all and you can ping out (obviously you will have to temporairly turn off wpa on your wireless node, set the correct ssid, and set the correct IP address to hard-code an IP address) If that doesen't work, regen the bcmw15.ko file using the "old" method: # cp foo.sys foo.inf /sys/modules/if_ndis # cd /sys/modules/ndis # make; make load # cd /sys/modules/if_ndis # ndiscvt -i foo.inf -s foo.sys -o ndis_driver_data.h # make; make load You need to isolate the problem to see if the driver is simply just not working at all under 6.3, or if it is working, but it's a scripting or turnup out of sequence error. And you need to see if wpa has anything to do with it. Ted