On Mon, Mar 21, 2011 at 3:04 AM, James <bjlockie@xxxxxxxxx> wrote: > On 03/20/11 17:04, James wrote: >> $ dmesg | grep phy >> BIOS-provided physical RAM map: >> modified physical RAM map: >> phy0: Selected rate control algorithm 'ath9k_rate_control' >> Registered led device: ath9k-phy0::radio >> Registered led device: ath9k-phy0::assoc >> Registered led device: ath9k-phy0::tx >> Registered led device: ath9k-phy0::rx >> phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81 >> mem=0xffffc90001900000, irq=17 >> >> This is kernel-2.6.36.2. >> The wireless doesn't work on any later kernel that I have tried. >> It is very interesting the IRQ is 17 on this kernel but 18 on 2.6.37.3. >> >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at Âhttp://vger.kernel.org/majordomo-info.html >> > I tried > http://www.orbit-lab.org/kernel/compat-wireless-2.6-stable/v2.6.36/compat-wireless-2.6.36-4.tar.bz2 > but it doesn't work in the 2.6.36.2 kernel or the 2.6.38 kernel. > > Where can I get the compat-wireless that is the exact code that is in > the 2.6.36.2 kernel and then I can try it in the 2.6.38 kernel? > The idea of compat-wireless is to make new wifi drivers & features accessible for older host-kernel, not the other way around. It also makes no sense to have same versions of host kernel and c-w version (both 2.6.36 for example, it is the same codebase). Did you try one of the bleeding-edge compat-wireless [1] tarball (it is updated daily, but can be broken)? Furthermore, [2] has informations about stable releases and detailed build instructions. Please provide full dmesg and lspci/lsusb output - not truncated one. Which user-space do you use? Network-Manager, wpasupplicant, etc.? - Sedat - [1] http://wireless.kernel.org/en/users/Download/#Where_to_download_bleeding_edge [2] http://wireless.kernel.org/en/users/Download/stable/ -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
