Re: Device busy error

2008-01-02 Thread Michael Buesch
On Wednesday 02 January 2008 21:18:29 David Ellingsworth wrote:
 
 While using the b43legacy driver with my 4306 card, wpa_supplicant and 
 iwconfig both report that the device is busy when trying to switch from 
 monitor mode to managed mode after having used kismet or airodump-ng. So far 
 the only resolution to the issue has been to rmmod and then modprobe the 
 driver again. Any help in finding the cause of the error would be appreciated.

ifconfig wlanX down
before switching modes.

-- 
Greetings Michael.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev


Re: Device busy error

2008-01-02 Thread Michael Buesch
You have a bogus
Reply-To: [EMAIL PROTECTED]
inside of your mailheaders, which confuses mailclients.
See the attached bounce.

-- 
Greetings Michael.
This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  [EMAIL PROTECTED]
Unrouteable address

-- This is a copy of the message, including all the headers. --

Return-path: [EMAIL PROTECTED]
Received: from t1fa0.t.pppool.de ([89.55.31.160] helo=powermac.local)
by vs166246.vserver.de with esmtpa (Exim 4.63)
(envelope-from [EMAIL PROTECTED])
id 1JAAl5-0004Yv-Ft; Wed, 02 Jan 2008 21:04:15 +
From: Michael Buesch [EMAIL PROTECTED]
To: bcm43xx-dev@lists.berlios.de,
 [EMAIL PROTECTED]
Subject: Re: Device busy error
Date: Wed, 2 Jan 2008 22:03:40 +0100
User-Agent: KMail/1.9.6
References: [EMAIL PROTECTED]
In-Reply-To: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: text/plain;
  charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: [EMAIL PROTECTED]

On Wednesday 02 January 2008 21:18:29 David Ellingsworth wrote:
 
 While using the b43legacy driver with my 4306 card, wpa_supplicant and 
 iwconfig both report that the device is busy when trying to switch from 
 monitor mode to managed mode after having used kismet or airodump-ng. So far 
 the only resolution to the issue has been to rmmod and then modprobe the 
 driver again. Any help in finding the cause of the error would be appreciated.

ifconfig wlanX down
before switching modes.

-- 
Greetings Michael.

___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev