Arch Linux

Keyhaku

Member

Registered: 2012-02-22

Posts: 1

Compat-wireless -1 channel patch not working !

Hello there,

I've recently bought a usb wireless adapter (ALFA AWUS036NEH) in order to use the aircrack-ng suite.

Unfortunately, the kernel drivers have the channel -1 bug, so I install AUR package compat-wireless-3.2.5-1, which is supposed to be patched for this bug.

I modified the PKGBUILD to only install rt2x00 group driver.

Once the install is done, i reboot or do

 modprobe rt2800usb 

and the card is working fine for conventionnal use.

But when I use it for airodump, i've still the fixed channel : -1 bug...

My pci card (Broadcom) has the same bug... (even after applied the patch ofc)

Can anybody help me? (for example tell me how to manually install it?)

Thanks in advance.

Some command that may help :

 $ lsusb -v
Bus 001 Device 004: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter

$ uname -r
3.2.9-1-ARCH

$ lsmod
Module                  Size  Used by
rt2800usb              14400  0 
rt2x00usb               9172  1 rt2800usb
rt2800lib              40420  1 rt2800usb
rt2x00lib              35407  3 rt2800lib,rt2x00usb,rt2800usb
crc_ccitt               1363  1 rt2800lib
cordic                  1073  1 brcmsmac
crc8                    1186  1 brcmsmac
brcmutil                3617  1 brcmsmac
mac80211              234450  4 brcmsmac,rt2x00lib,rt2800lib,rt2x00usb
cfg80211              174596  3 mac80211,brcmsmac,rt2x00lib
rfkill                 15498  3 cfg80211,bluetooth
ext4                  418044  3 
crc16                   1359  2 ext4,bluetooth
jbd2                   71243  1 ext4
mbcache                 5881  1 ext4
sd_mod                 28307  5 
ohci_hcd               21631  0 
ehci_hcd               40698  0 
usbcore               146113  7 ehci_hcd,ohci_hcd,btusb,uvcvideo,rt2x00usb,rt2800usb
...

Last edited by Keyhaku (2012-03-13 13:47:42)

lf88

Member

Registered: 2009-12-09

Posts: 4

Re: Compat-wireless -1 channel patch not working !

Have you tried downgrading your kernel a couple of versions... maybe to the 3.2.5 version? And of course, re-building and re-installing the package.