From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 8 02:30:34 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E53CC16A41C for ; Wed, 8 Jun 2005 02:30:34 +0000 (GMT) (envelope-from dcp1990@neptune.atopia.net) Received: from neptune.atopia.net (neptune.atopia.net [209.128.231.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id A982843D1D for ; Wed, 8 Jun 2005 02:30:34 +0000 (GMT) (envelope-from dcp1990@neptune.atopia.net) Received: by neptune.atopia.net (Postfix, from userid 1034) id 057514153; Tue, 7 Jun 2005 22:30:34 -0400 (EDT) Date: Tue, 7 Jun 2005 22:30:33 -0400 From: Dan Ponte To: freebsd-hardware@freebsd.org Message-ID: <20050608023033.GA50562@neptune.atopia.net> Mail-Followup-To: freebsd-hardware@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline User-Agent: Mutt/1.5.8i Subject: extremely odd wi(4) scenario X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 02:30:35 -0000 --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all. I posted quite a while back about some problems I was having with firmware v1.4.9. So, tonight I decided to try other versions. Using my windows machine (which also dual boots FreeBSD), I upgraded the card to 1.8.2. It worked fine in windows, and also in FreeBSD on that machine. I then put the card back in the server. This time, however, status was always "no carrier," and with hw.wi.debug=3D1, it would always go from state "INIT -> INIT." Now for the very weird part: if I ran dstumbler with the -o option, the link light turned on, it displayed "INIT -> RUN", and it saw my AP, but I still could not connect. Upon quitting dstumbler, status went back to INIT. If I put the card in monitor or hostap mode, it goes to RUN but I obviously cannot do anything since this is a BSS network. This same thing happens on 1.5.6 and 1.7.4. I am currently using 1.3.4, which I had ok luck with before I went to 1.4.9. I'm stumped. Maybe you aren't. -Dan --=20 Dan Ponte http://www.theamigan.net/ All of the true things I am about to tell you are shameless lies. -- The Book of Bokonon / Kurt Vonnegut Jr. --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCplhJ8dUD8SpKFR8RAsQgAJ9jiilVaeN5yHy9Pc6rwyEDJZO3bwCdE72G 3xcdf/wYjGAvNO2AiavNPu0= =HkkL -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l--