From owner-freebsd-net@FreeBSD.ORG Wed Feb 18 16:13:29 2009 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 D4B5010656DC for ; Wed, 18 Feb 2009 16:13:29 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from spamfish.visualtech.com (h-67-102-187-40.phlapafg.covad.net [67.102.187.40]) by mx1.freebsd.org (Postfix) with ESMTP id 69DBF8FC14 for ; Wed, 18 Feb 2009 16:13:28 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from mailstore.visualtech.com (unknown [67.102.187.41]) by spamfish.visualtech.com (Postfix) with ESMTPS id 8BCA81F4419; Wed, 18 Feb 2009 11:07:37 -0500 (EST) Received: from memory.visualtech.com (h-67-103-204-242.phlapafg.covad.net [67.103.204.242]) by mailstore.visualtech.com (Postfix) with ESMTP id 615A2ADC25E; Wed, 18 Feb 2009 11:22:28 -0500 (EST) Date: Wed, 18 Feb 2009 11:12:23 -0500 From: Adam K Kirchhoff To: "Paul B. Mahol" Message-ID: <20090218111223.4483b923@memory.visualtech.com> In-Reply-To: <3a142e750902180733o679b050ck8d9287f0bdd860e7@mail.gmail.com> References: <200902171720.n1HHKkIf071491@freefall.freebsd.org> <20090217133404.22275b25@memory.visualtech.com> <3a142e750902171414p438d184bl54a1569e27490634@mail.gmail.com> <200902171727.53156.adamk@voicenet.com> <3a142e750902180306x390fd549led076474f4fae06b@mail.gmail.com> <20090218080420.681788d2@memory.visualtech.com> <3a142e750902180733o679b050ck8d9287f0bdd860e7@mail.gmail.com> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-visualtech-MailScanner: Found to be clean Cc: freebsd-net@freebsd.org Subject: Re: kern/131781: [ndis] ndis keeps dropping the link 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: Wed, 18 Feb 2009 16:13:30 -0000 On Wed, 18 Feb 2009 16:33:56 +0100 "Paul B. Mahol" wrote: > On 2/18/09, Adam K Kirchhoff wrote: > > On Wed, 18 Feb 2009 12:06:21 +0100 > > "Paul B. Mahol" wrote: > > > >> On 2/17/09, Adam K Kirchhoff wrote: > >> > On Tuesday 17 February 2009 17:14:07 Paul B. Mahol wrote: > >> >> On 2/17/09, Adam K Kirchhoff wrote: > >> >> > On Tue, 17 Feb 2009 19:22:22 +0100 > >> >> > > >> >> > "Paul B. Mahol" wrote: > >> >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=131781 > >> >> >> > >> >> >> This one should not happen, 108 rate should get recognized. > >> >> >> I will try to reproduce it on CURRENT. > >> >> >> > >> >> >> To OP, could you try 7 STABLE after 31 Jan? I guess it should not > >> >> >> change anything but you never know. > >> >> > > >> >> > Sorry, I must have copied and pasted the uname output from the wrong > >> >> > machine. This is actually FreeBSD 7.1-STABLE #4: Mon Feb 16 16:37:18 > >> >> > EST 2009 :-) > >> >> > >> >> miniport dump NDIS_STATUS_UNSUPPORTED_MEDIA for error in > >> >> ndis_setstate() for setting OID_802_11_CONFIGURATION. > >> > > >> > Sorry if I seem slow, but are you asking me to check something there, or > >> > just > >> > stating what you think the problem is? :-) > >> > >> You can add printf() before "ndis_set_info(sc, > >> OID_802_11_CONFIGURATION, &config, &len);" in ndis_setstate_80211() to > >> check what value for config.nc_dsconfig is by default. > > > > I'll try that shortly. > > > >> Also try changing "sysctl debug.ndis=1" and post console debug ouput > >> again. > > > > This was strange. If I boot up and enable debugging before I try to > > run '/etc/rc.d/netif start ndis0' everything works just fine. I get an > > IP address and stay connected (at least under a light load). This is > > the output: > > > > ndis_newstate: INIT -> INIT > > ndis0: NDIS ERROR: c00013a7 (unknown error) > > ndis0: NDIS ERROR: c0001392 (unknown error) > > these two errors means: > > EVENT_NDIS_ADAPTER_CHECK_ERROR > EVENT_NDIS_INVALID_VALUE_FROM_ADAPTER > > Looks like minport driver doesnt like your card. > Are you absolutly sure that you are using right miniport driver? Frankly, no. This laptop came with a broadcom minipci card. I replaced it with the intel one that I'm now using since intel network cards have native drivers under FreeBSD :-) I've downloaded the latest drivers from the intel website ( http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&Inst=Yes&ProductID=1637&DwnldID=17228&strOSs=45&OSFullName=Windows*%20XP%20Home%20Edition&lang=eng ) and used them to generate the driver with ndisgen. Is there a recommended windows driver to use with ndis for this intel network card? > > Setting BSSID to ff:ff:ff:ff:ff:ff > > Setting ESSID to "" > > ndis0: no matching rate for: 108 > > ndis_newstate: INIT -> RUN > > ndis0: link state changed to UP > > ndis_newstate: RUN -> INIT > > Setting channel to 2412000kHz > > ndis0: couldn't change DS config to 2412000kHz: 19 > > Setting BSSID to ff:ff:ff:ff:ff:ff > > Setting ESSID to "Mckella280Front" > > ndis0: link state changed to DOWN > > ndis0: no matching rate for: 108 > > ndis_newstate: INIT -> RUN > > ndis0: link state changed to UP > > > > If I then stop the network on that device, disable debug, and try to > > start it up again, I get the same problem as before: > > > > ndis0: couldn't change DS config to 2412000kHz: 19 > > ndis0: link state changed to DOWN > > ndis0: no matching rate for: 108 > > ndis0: link state changed to UP > > ndis0: couldn't change DS config to 2412000kHz: 19 > > ndis0: link state changed to DOWN > > ndis0: no matching rate for: 108 > > ndis0: link state changed to UP > > ndis0: link state changed to DOWN > > > > If I then stop the network, enable debugging, and start up the network, > > the problem persists. > > > > You are starting ndis0 in same way in both cases? Yes. I booted up with the ifconfig_ndis0 line commented out in /etc/rc.conf. I then uncommented the line, enabled debugging, and started the network with '/etc/rc.d/netif start ndis0'. I then brought the network down, disabled debugging, and started the network with the same command. After stopping the interface, and re-enabling networking, I started the interface with the same command the third time. Adam -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.