FS#11904 - iwl3945 - no more monitor mode?

Attached to Project: Arch Linux
Opened by P. Baumgart (Baumi) - Monday, 27 October 2008, 22:42 GMT
Last edited by Thomas Bächler (brain0) - Friday, 05 December 2008, 10:44 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture i686
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After "must" switching to iwl3945 I can´t get my wlan in monitor mode.

I guess, I have nothing that special in my system that prevents something like that.

I use: "iwconfig wlan0 mode monitor"

and get: Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Device or resource busy.




Additional info:
kernel: 2.6.27.1-1
This task depends upon

Closed by  Thomas Bächler (brain0)
Friday, 05 December 2008, 10:44 GMT
Reason for closing:  Upstream
Additional comments about closing:  Intel is being an ass about monitor, AP and mesh mode in their driver and ucode. The linux wireless guys are unhappy about it, and so are the users, but apparently Intel's wireless people aren't.
Comment by P. Baumgart (Baumi) - Friday, 07 November 2008, 14:32 GMT
Still the same problem after kernel update to: 2.6.27.4-1
Comment by P. Baumgart (Baumi) - Tuesday, 18 November 2008, 16:27 GMT
Still the same problem in 2.6.27.6-1

iwconfig wlan0 mode monitor

Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Device or resource busy.
Comment by Thomas Bächler (brain0) - Friday, 05 December 2008, 10:42 GMT
Monitor mode is not supported in the iwl3945 driver, complain to Intel about it.

If you want monitor mode, I guess you can try ipwraw or patch ipw3945 to compile with the latest kernel (I won't do any of that, you have to do it yourself). The latest PKGBUILDs for ipw3945 are still in svn trunk (http://repos.archlinux.org/viewvc.cgi/ipw3945/trunk/). For 2.6.27 you probably need a patch similar to what I applied to rt2500 and some other wireless drivers when I updated to 2.6.27.

Loading...