From owner-freebsd-mobile@FreeBSD.ORG Sat Aug 9 07:43:16 2003 Return-Path: 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 19DCD37B401 for ; Sat, 9 Aug 2003 07:43:16 -0700 (PDT) Received: from andrea.pop4.net (216-234-109-11.ded.det2.hexcom.net [216.234.109.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 0C67243FA3 for ; Sat, 9 Aug 2003 07:43:15 -0700 (PDT) (envelope-from vev@michvhf.com) Received: (qmail 29391 invoked by uid 1008); 9 Aug 2003 14:43:11 -0000 Received: from vev@michvhf.com by www.pop4.net with qmail-scanner-0.96 (uvscan: v4.1.40/v4156. . Clean. Processed in 0.52492 secs); 09 Aug 2003 14:43:11 -0000 Received: from unknown (HELO paprika.michvhf.com) (67.36.71.182) by 0 with SMTP; 9 Aug 2003 14:43:10 -0000 Received: (qmail 44334 invoked by uid 1001); 9 Aug 2003 14:43:13 -0000 Date: Sat, 9 Aug 2003 10:43:13 -0400 (EDT) From: Vince Vielhaber To: Daniel Eischen In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "Christoph P. Kukulies" cc: freebsd-mobile@freebsd.org Subject: Re: wi0_cmd: busy bit won't clear X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Aug 2003 14:43:16 -0000 On Sat, 9 Aug 2003, Daniel Eischen wrote: > On Sat, 9 Aug 2003, Christoph P. Kukulies wrote: > > > On Fri, Aug 08, 2003 at 03:38:42PM -0400, Daniel Eischen wrote: > > > On Fri, 8 Aug 2003, Christoph Kukulies wrote: > > > > > > > > > I just got that (wi0_cmd: busy bit won't clear) today when > > > booting with my DWL-650H inserted. I've seen it before also, > > > so I wasn't sure if it was an issue with recent changes or not. > > > > > > I worked around it by removing it and then reinserting it > > > and manually ifconfig'ing it. My normal setup is to have > > > dhclient run on it at boot up. So try rebooting without > > > the card inserted and then insert it and manually configuring > > > it (if you haven't already tried). > > > > You mean remove the card totally ? > > Yes, physically remove it then boot. Once the system is > up, then reinsert it. ifconfig is supposed to be used > now instead of wicontrol. Try setting the ssid first, > then check to see that it got set, then give it its > address and netmask: The older prism firmware would lock up so hard it would take a powerdown reboot or as you indicate above, remove and reboot. Make sure the lastest available firmware is in that card. I have a card around here somewhere with that old firmware. If I get a chance later I'll dig it out and get the firmware rev. and post it. Vince. -- Fast, inexpensive internet service 56k and beyond! http://www.pop4.net/ http://www.meanstreamradio.com http://www.unknown-artists.com Internet radio: It's not file sharing, it's just radio.