Sign up using Facebook. Sign up using Facebook. How-to compile madwifi and the patch. With the updated version from wireless. Please visit this page to clear all LQ-related cookies.
|Date Added:||24 November 2015|
|File Size:||10.89 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
They wake up CPU excessively making the whole system slow and unresponsive.
If you’d like to contribute content, let us know. Find More Posts by Drakeo.
This project is no longer active. Which driver is the card using ath5k or ath9k? Atheros AR not working properly Ask Question. Registration is quick, simple and atueros free.
Share this on del. AR Wireless Network Adapter [c: Trying to wakeup ubuntu with dynamic IP.
ath9k – Debian Wiki
Now, both the ndiswrapper and ath9k drivers give me a very strange problem: Works absolutely perfect in BT4, just have to manually raise txpower and get way more APs than with any other wireless adapter I had, plus the speed and bandwidth is doubled than with other adapters.
I can confirm that this chipset works great with the madwifi-ng drivers on Debian Testing. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Are you new to LinuxQuestions.
Home Questions Tags Users Unanswered. Works with madwifi 0.
However the kbuntu must first be turned on using a software switch as explained hereelse it will not transmit or receive anything. Host not found http: Here is some ndis wrapper help. Working perfectly as of on an Acer Aspire I use NetworkManager 0. I have made this: As the other bug report doesn’t relate to this hardware, I’ll just report here my findings.
Atheros 802.11n PCI/PCI-E devices (ath9k)
Switching to a mbps resolves all speed issues, when the difference shouldn’t be that noticeable. Subsequent reboots will fix this issue “magically”. Please visit this page to clear all Athedos cookies. It works OK with Slackware I can confirm also that I’m having the same problem described in this bug report: This makes me hopeful that a fixed version of the driver will eventually make its way into the kernel.