Compact wireless driver linux

Aircrack-ng

User Tools

Site Tools

Table of Contents

compat-wireless — DEPRECATED

UPDATE: DO NOT USE ANYMORE. If successful, it is a downgrade from the curent version of your existing drivers UPDATE: compat-wireless is now known as backports

Compat-wireless is a package which contains the development and stable versions (pulled from the kernel’s git repository) of the in-kernel wireless drivers and the mac80211 wireless stack. New packages are released pretty much every day.

Additionally, the development versions of the drivers have one particular advantage : they’re being constantly improved. It is not uncommon to see that they support more hardware, have better performance, or simply contain fixes to various bugs — in contrast to their stable versions. However, you should always remember that development versions may be incomplete or contain even more bugs than the stable ones.

We distinguish two versions of compat-wireless, development (bleeding edge) and stable. The development version may include more drivers, supported hardware and bug-fixes but may not be as stable as the ‘stable’ version which implies its nature. With minor exceptions, both versions will suffice in your bid to enable aircrack-ng support for your card/driver. For the majority of the users the stable version is the preferred one to use

The home page of the package is here. Visit the compat-wireless forum thread to share your experience if you need assistance.

Package requirements

In order to install this package, you need to have a few things :

Installing the package

If you meet the requirements of the package, you can try installing it.

Kernels 2.6.24 or higher

The installation process is as follows:

note: the exact filename of the tarball depends on which version you have downloaded, substitute the example filename with the one corresponding to the file you downloaded

note: the next two steps are only required for compat-wireless versions before v3.3-rc1-2

Before compiling, take a look at “driver-select” down the page

Reboot, if you’re unsure.

Kernels 2.6.22 — 2.6.24

If you’re using an ancient kernel, currently lower than 2.6.24, you won’t have much success enabling aircrack-ng. There used to be a package called compat-wireless-old which is no longer supported. You could try and dig in to Orbit’s archives for older releases, be warned, the likelihood of you succeeding is very slim. Your best bet to enable compat-wireless, thus aircrack-ng, is to install a supported kernel version. An other convenient option is to utilize linux Live CD with preconfigured settings for easy aircrack-ng operation.

Uninstalling the package

Should you be in any way dissatisfied with the new drivers, you can uninstall them very easily and return to your default wireless kernel drivers:

Then reboot or sudo modprobe your-desired-driver to complete the process.

Driver Select

compat-wireless offers one very useful script, called driver-select, which allows you to save time when compiling your preferred driver. Currently not all drivers are available via driver-select but the most common ones are. Its useful if you install compat-wireless frequently or if you have one card on your computer. Enter the compat-wireless directory and issue:

to see all of the available drivers and options. An example of installing singular module would be

Refer to the linux-wireless driver-select page for more details.

Troubleshooting

Compilation problems

If you encounter compilation problems, please make sure you’ve got kernel headers installed and that the system knows where to look for them. Generally, there should be a symlink under

which points to the directory containing the kernel headers.

Compilation errors

Every now and then, you may stumble upon errors during compilation and the process may end because of them. Its not necessarily your fault. Sometimes, the compat-wireless tar balls do come out with compile errors built in, which are usually resolved in the next few releases. Should this happens to you, simply download an older version from the previous days and try again. If your problem persists and you’re stuck, share your difficulties with the community in this forum thread

Module loading problems

Firstly, make sure that the compat-wireless package was compiled with GCC whose minor version is the same as the minor version of the GCC with which the kernel was compiled. For example, if you compiled your kernel with GCC 4.3.2, but you compiled compat-wireless with GCC 4.4.1, you might run into “Invalid module format” problems. These will also occur if you’ve built the package for a different kernel than the one you’re currently running.

Secondly, as shown above, it is imperative to unload ALL wireless modules before you attempt to load your newly compiled ones. While in the compat-wireless directory

will make sure all of the wireless modules are unloaded, which will pave the way for your new driver take its place. Reboot if you’re unsure.

Источник

Linux Wireless

User Tools

Site Tools

Sidebar

Table of Contents

compat-wireless-old

We started providing compatibility support since 2.6.22 as that is when mac80211 was introduced onto the stock kernel but we have now added initial support for older kernels, starting at 2.6.21.

Requirements

You will need at least of these kernels:

Additionally, the kernel you’re building for needs a valid “.config” file, if it isn’t present compat will assume you have PCI, USB and PCMCIA built into your kernel and if not, fail building.

Release notes

Later kernels got WMM supported redesigned for mac80211, when using compat-wireless old we will build our own WMM support for you without usage of the new kernel QOS features. This is exactly how WMM was handled in mac80211 on 2.6.22, but keep in mind 2.6.22 didn’t come with any mac80211 drivers, it came just with mac80211 itself. Since you get a custom WMM support you also get 802.11n support, which requires WMM support.

Its worth noting compat-wireless-old currently does not get any attention from any developer as such its not getting further updates. Patches are always welcomed though.

Where to download

You can get compat-wireless-old from:

Building and installing

Extract:

Extract the content of the package:

Build:

Build the latest Linux wireless subsystem:

Install:

We use the updates/ directory so your distribution’s drivers are left intact.

Uninstall:

This nukes our changes to updates/ so you can go back to using your distribution’s supported drivers.

Unload:

Since you might be replacing your old mac80211 drivers you should first try to unload all existing mac80211 and related drivers. Note also that broadcom, zydas, and atheros devices have old legacy drivers which you need to be sure are removed first. We provide a mechanism to unload all old and legacy drivers first so you should run to be sure:

Load:

Before loading modules you must first unload your old wireless subsystem modules. Read above how to do this. If you know what module you need you can simply load the module using modprobe. If you simply are not sure you can use, just reboot the box.

Drivers

Here is the list of all the drivers we support in this package.

Known issues

On distribution releases with old udev rules you may end up with strange network device names, for example, wlan0_rename. You may also end up with master device names such as eth3, when this was actually intended to be named wmaster0. This happens because master interface has the same MAC address as the real interface, and it is created first. The old udev rule, which keys on the MAC addres, may rename it to device names like eth3, for example. Then the real interface is created, udev sees that it has already renamed an interface with that MAC and gives it the wlan0_rename name.

If you delete the generated rename rules, it should create the correct ones on the next boot. Alternately, you could add:

selector to your current rule. Debian puts these autogenerated udev rules in /etc/udev/rules.d/z25_persistent-net.rules. Other distributions may vary slightly.

Kernels ⇐ 2.6.22 now get nl80211 support, however, genl_multicast_group won’t work. This compatibility cannot be extended to older kernels as the struct genl_family was extended on 2.6.23 to add the struct list_head mcast_groups. Without this you will not be able to use nl80211 events which uses this heavily. The compat-wireless-old release does not have nl80211 events though so you should not care about this.

To revert back to bcm43xx you can run:

If MadWifi is present the build system will detect this and disable it. It does this by simply renaming ath_pci.ko to ath_pci.ko.ignore. This lets us disable the MadWifi driver without blacklisting it which could cause issues with users later. If you would like to enable MadWifi at a later time and disable ath5k you can run:

To revert back to ath5k you can run:

Building for external kernels

If you have a kernel you do not have installed but yet want to build the compat-wireless-old drivers for it you can use this syntax:

If you’ve found a bug you are expected to fix it as this is not being actively developed. Patches are always welcomed of course.

How about compatibility work for kernels older than 2.6.21 ?

Sure, feel free to send patches. The main work was designed to support kernels >= 2.6.22 as that was when mac80211 was introduced. Some drivers are available for 2.6.21 but not all drivers can work on that kernel due to an CRC-ITU-T algorithm dependency.

ChangeLog

compat-wireless-old ChangeLog

See the compat-wireless-old ChangeLog to view changes made necessary in order to keep advancing this package.

License

This work is a subset of the Linux kernel as such we keep the kernel’s Copyright practice. Some files have their own copyright and in those cases the license is mentioned in the file. All additional work made to building this package is licensed under the GPLv2.

Developers

Hacking on compat-wireless-2.6-old

The old compat-wireless tree is used for kernels ⇐ 2.6.26. We don’t have an automatic script to update it. It is updated manually, as such if you want it updated please send patches to linux-wireless mailing list and hack on it as you would with the kernel using git on its own tree.

RHEL5, Centos5, and Debian etch seems to be stuck on 2.6.18. Patches are welcomed.

Patches for compatibility work

For kernels >= 2.6.27 please send patches against

Checking out compat-wireless-2.6-old.git tree

To checkout the compat-wireless-2.6.git tree you do:

Note: you do not need a wireless-testing clone to use or hack on this tree.

Источник

Thread: compact-wireless driver issue | tl-wn722n | atheros chipset — 9271

Thread Tools

Display

compact-wireless driver issue | tl-wn722n | atheros chipset — 9271

After installation my original wifi driver iwl3945 become disabled and I cannot modprobe it back!

/tl-wn722n$ sudo modprobe iwl3945
[sudo] password for majo:
FATAL: Error inserting iwl3945 (/lib/modules/2.6.32-38-generic/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko): Unknown symbol in module, or unknown parameter (see dmesg)

I bought a new TP-link usb wifi adapter. tl-wn722n.
I had several issues during installation. But then installed it.
followed this page:
http://dwiel.net/blog/tp-link-tl-wn7. -ubuntu-10-04/

I have downloaded and installed
compat-wireless-2.6.38.2-2.tar.bz2

my current kernel is:
2.6.32-38-generic
Ubuntu 10.04.4 LTS \n \l

I am attaching some show commands and DMESG file.
Please help.

root@laptop:/home/majo/airtest# lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 0b05:1712 ASUSTek Computer, Inc. BT-183 Bluetooth 2.0+EDR adapter
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 0cf3:9271 Atheros Communications, Inc.
Bus 001 Device 004: ID 174f:a311 Syntek 1.3MPixel Web Cam — Asus A3A, A6J, A6K, A6M, A6R, A6T, A6V, A7T, A7sv, A7U
Bus 001 Device 002: ID 1e3d:2092
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

————————————————————————-
root@laptop:/home/majo/airtest# hwinfo —wlan
16: PCI 300.0: 0282 WLAN controller
[Created at pci.318]
UDI: /org/freedesktop/Hal/devices/pci_8086_4222
Unique ID: svHJ.voNJAxCYCzB
Parent ID: Z7uZ.f4r+Yl3RyX5
SysFS ID: /devices/pci0000:00/0000:00:1c.3/0000:03:00.0
SysFS BusID: 0000:03:00.0
Hardware Class: network
Model: «Intel PRO/Wireless 3945ABG Network Connection»
Vendor: pci 0x8086 «Intel Corporation»
Device: pci 0x4222 «PRO/Wireless 3945ABG [Golan] Network Connection»
SubVendor: pci 0x8086 «Intel Corporation»
SubDevice: pci 0x1001 «PRO/Wireless 3945ABG Network Connection»
Revision: 0x02
Features: WLAN
Memory Range: 0xfe1ff000-0xfe1fffff (rw,non-prefetchable)
IRQ: 3 (no events)
Module Alias: «pci:v00008086d00004222sv00008086sd00001001bc02sc8 0i00»
Driver Info #0:
Driver Status: iwl3945 is not active
Driver Activation Cmd: «modprobe iwl3945»
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #5 (PCI bridge)
———————————————————————-
hwinfo —usb
16: USB 00.0: 0000 Unclassified device
[Created at usb.122]
UDI: /org/freedesktop/Hal/devices/usb_device_cf3_9271_12345_if0
Unique ID: Uc5H.7OI4S6n4RF2
Parent ID: k4bc.9T1GDCLyFd9
SysFS ID: /devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4:1.0
SysFS BusID: 1-4:1.0
Hardware Class: unknown
Model: «Atheros USB2.0 WLAN»
Hotplug: USB
Vendor: usb 0x0cf3 «Atheros Communications, Inc.»
Device: usb 0x9271 «USB2.0 WLAN»
Revision: «1.08»
Serial ID: «12345»
Driver: «ath9k_hif_usb»
Driver Modules: «ath9k_htc»
Speed: 480 Mbps
Module Alias: «usb:v0CF3p9271d0108dcFFdscFFdpFFicFFisc00ip00 »
Driver Info #0:
Driver Status: ath9k_htc is active
Driver Activation Cmd: «modprobe ath9k_htc»
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #6 (Hub)
—————————————————————————

$ sudo modprobe iwl3945
FATAL: Error inserting iwl3945 (/lib/modules/2.6.32-38-generic/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko): Unknown symbol in module, or unknown parameter (see dmesg)

FATAL: Error inserting iwlagn (/lib/modulroot@laptop:/home/majo/airtest# lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 0b05:1712 ASUSTek Computer, Inc. BT-183 Bluetooth 2.0+EDR adapter
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 0cf3:9271 Atheros Communications, Inc.
Bus 001 Device 004: ID 174f:a311 Syntek 1.3MPixel Web Cam — Asus A3A, A6J, A6K, A6M, A6R, A6T, A6V, A7T, A7sv, A7U
Bus 001 Device 002: ID 1e3d:2092
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

————————————————————————-
root@laptop:/home/majo/airtest# hwinfo —wlan
16: PCI 300.0: 0282 WLAN controller
[Created at pci.318]
UDI: /org/freedesktop/Hal/devices/pci_8086_4222
Unique ID: svHJ.voNJAxCYCzB
Parent ID: Z7uZ.f4r+Yl3RyX5
SysFS ID: /devices/pci0000:00/0000:00:1c.3/0000:03:00.0
SysFS BusID: 0000:03:00.0
Hardware Class: network
Model: «Intel PRO/Wireless 3945ABG Network Connection»
Vendor: pci 0x8086 «Intel Corporation»
Device: pci 0x4222 «PRO/Wireless 3945ABG [Golan] Network Connection»
SubVendor: pci 0x8086 «Intel Corporation»
SubDevice: pci 0x1001 «PRO/Wireless 3945ABG Network Connection»
Revision: 0x02
Features: WLAN
Memory Range: 0xfe1ff000-0xfe1fffff (rw,non-prefetchable)
IRQ: 3 (no events)
Module Alias: «pci:v00008086d00004222sv00008086sd00001001bc02sc8 0i00»
Driver Info #0:
Driver Status: iwl3945 is not active
Driver Activation Cmd: «modprobe iwl3945»
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #5 (PCI bridge)
———————————————————————-
hwinfo —usb
16: USB 00.0: 0000 Unclassified device
[Created at usb.122]
UDI: /org/freedesktop/Hal/devices/usb_device_cf3_9271_12345_if0
Unique ID: Uc5H.7OI4S6n4RF2
Parent ID: k4bc.9T1GDCLyFd9
SysFS ID: /devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4:1.0
SysFS BusID: 1-4:1.0
Hardware Class: unknown
Model: «Atheros USB2.0 WLAN»
Hotplug: USB
Vendor: usb 0x0cf3 «Atheros Communications, Inc.»
Device: usb 0x9271 «USB2.0 WLAN»
Revision: «1.08»
Serial ID: «12345»
Driver: «ath9k_hif_usb»
Driver Modules: «ath9k_htc»
Speed: 480 Mbps
Module Alias: «usb:v0CF3p9271d0108dcFFdscFFdpFFicFFisc00ip00 »
Driver Info #0:
Driver Status: ath9k_htc is active
Driver Activation Cmd: «modprobe ath9k_htc»
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #6 (Hub)
—————————————————————————

$ sudo modprobe iwl3945
FATAL: Error inserting iwl3945 (/lib/modules/2.6.32-38-generic/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko): Unknown symbol in module, or unknown parameter (see dmesg)

Источник