Download Compat Wireless Drivers Install Update
We started providing compatibility support since 2. Later kernels got WMM supported redesigned for mac, 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 mac on 2. Since you get a custom WMM support you also get 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. Since you might be replacing your old mac drivers you should first try to unload all existing mac 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:. 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. 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.
If you delete the generated rename rules, it should create the correct ones on the next boot. Alternately, you could add:. Other distributions may vary slightly. Without this you will not be able to use nl events which uses this heavily. The compat-wireless-old release does not have nl events though so you should not care about this.
If MadWifi is present the build system will detect this and disable it. 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:. 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. Sure, feel free to send patches. Some drivers are available for 2. See the compat-wireless-old ChangeLog to view changes made necessary in order to keep advancing this package. 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.
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. Sidebar Users main page. Table of Contents compat-wireless-old. How about compatibility work for kernels older than 2. You will need at least of these kernels: Note that if you are on a kernel between 2.
You can get compat-wireless-old from: Extract the content of the package: Build the latest Linux wireless subsystem: We provide a mechanism to unload all old and legacy drivers first so you should run to be sure: Here is the list of all the drivers we support in this package.
If a developer is interested in older kernels they'll have to add compatibility support for it. Strange wireless device names: Lets clarify device names first. Regularly you should only see two new device names:. The master device is an internal master device used only by mac It should be ignored by users. If possible we will try to hide it from users later. Since there was an old softmac broadcom driver we provide a load script for this driver.
To load the new generation drivers b43 and b43legacy you can run:. We don't provide prism54 in this package because distributions already provide it. Should prism54 get any new updates we'll start packaging it here. If your driver needs firmware please be sure to check the driver page for that driver here:.
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: Compatibilty work for 2.
To checkout the compat-wireless Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.
Compat-Wireless for Linux 2.6.25+
This section deals with development details of compat-wireless and the other trees it uses. If you want to make your own compat-wireless tarballs, or if you see something busted with compat-wireless or just want to add something new or an enhancement this is the guide for you. To be able to synchronize backporting the latest and greatest the linux-next. General Linux kernel compatibility is addressed through a general kernel compatibility tree, compat. You will then need to checkout three trees to start hacking on compat-wireless:. So if the current rc kernel is 2. The compat git tree is a general kernel compatibility layer which can be shared amongst different compatibility projects, or drivers. Provides all exported symbols implemented in each respective kernel compat
We started providing compatibility support since 2. Later kernels got WMM supported redesigned for mac, 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 mac on 2. Since you get a custom WMM support you also get 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.