Sorry to be the party pooper, but I am removing the patch from this ticket until we know the origin of it, and the patch submitter has contacted the developers of this project to co-ordinate the availability of this new code for public consumption.

Scott Raynel has attempted to contact the two mail addresses from Atheros on this ticket in order to receive more information about the situation.

It is, in our opinion, not very responsible to allow an unknown blob to be made available like this. We have no way of knowing what this blob does, and we never will, because its not transparent. But we do _need_ to be informed by the blob vendor what changes it brings.

It is, in our opinion, not very responsible to allow an unknown blob to be made available like this. We have no way of knowing what this blob does, and we never will, because its not transparent. But we do _need_ to be informed by the blob vendor what changes it brings.

Not only that. If we apply patches to the HAL blob we got from our original HAL upstream, we divert from it and make it harder (if not impossible) to incorporate future updates from upstream (read: Sam). It's a similar issue as with the question of whether or not we should try to incorporate the HAL that comes with Asus' variant of MadWifi.

Bottom line: I second the objections to this practice. The only way to get AR5007 support into MadWifi is to make sure that our HAL upstream implements support for these chipsets in his sources and provides us with a updated binary.

It seems unnecessary to actually remove the patch -- especially since it's known to help in certain cases. Could the patch not stay up, but have a gigantic warning across it? Those of us who can legally use it and able too would appreciate a working system in the meantime until the proper fix surfaces.

It seems unnecessary to actually remove the patch... Could the patch not stay up...

The origin of the patch in question was doubtful, it didn't came through the channels we usually receive HAL updates from. The fact that the patch removes Sam's copyright notices from the patched files didn't help to make it look less suspicious.

In the past we had several incidents where users attached leaked HAL sources or other work that made use of illegally distributed files. Since we are responsible for stuff that is offered for download from our server and thus could probably be called to account for the distribution of "illegal files" it was necessary to remove the file. A big fat warning across the file obviously wouldn't have helped us if it turned out that the stuff was not kosher.

We have received feedback from other users stating that the removal of the file seems to them like an over-reaction. I hope the above helps to understand our rationales. We certainly would love to see AR5007 support in MadWifi rather sooner than later, but we have to make sure that this is done "the right way", without exposing ourselves to yet another series of claims about copyright infringements and thelike (even more now that we are working hard on ath5k). This should also be in the best interest of the users of our drivers, even if it means that AR5007 support gets delayed.

Last but not least: meanwhile it was approved that the patch was contributed by Atheros. We are currently talking to them about how to proceed in order to get AR5007 support into MadWifi properly (means: not just for i386, but for all platforms, to prevent ABI breakage). Please stay tuned, we will keep you updated.

12/03/07 15:09:58 changed by AR5007EG user =)

The patch works for me =) Thanks a lot madwifi team.

The only "problem" is in injection. In injection test works great, but when i try to send packets i got no luck :(

Any suggestion?

12/03/07 21:58:16 changed by mentor

This ticket isn't about injection.

12/04/07 22:50:51 changed by madwifi@atheros.com

After discussion with Madwifi team (Scott Raynel), the 32-bits x86 HAL attachment has been resubmitted. The attachment now has the appropriate copyright notice included.

Well, I tried the r2756 with the patch above cleanly applied. Followed the INSTALL instructions.
Checked that the lspci -d 168c:001c indeed gives the correct device. uname -i reports GenuineIntel?
This is with the official 2.6.23-gentoo-r3 kernel on 32bit Gentoo running on Core2 Duo.

Well, I tried the r2756 with the patch above cleanly applied. Followed the INSTALL instructions.
Checked that the lspci -d 168c:001c indeed gives the correct device. uname -i reports GenuineIntel?
This is with the official 2.6.23-gentoo-r3 kernel on 32bit Gentoo running on Core2 Duo.
Alas - same result as anakin (hal status 3).

Update: got it working after thoroughly cleaning up previous modules and rebooting.

12/09/07 16:49:07 changed by cogumbreiro@gmail.com

I tried installing by downloading (1) and applying patch (2) to the source as specified in the description of the bug.

The driver loads up (by calling "modprobe ath_pci"), and then an interface 'wlan0' and an interface 'wifi0' are created. However, no AP are discovered.

Any idea how can I find out what's wrong? Do you want me to send the log.

One interesting fact is that this is the second laptop I have with this wireless card, both laptops are of the same model. The first one I configured wireless with ndiswrapper, this one I cannot get it to work neither with ndiswrapper nor with madwifi.

Right, I've had to clear out the ticket. Again. Some of you clearly have issues following instructions, which does not bode well for your ability to use this patch, but it definitely does not bode well for your continued use of the ticket.

This is not a general support forum for the use of this patch, and it is definitely not a soap box. This ticket should be used for concise, general, and non-redundant information, not discussion. If in doubt, DO NOT POST.

For clarity, as I sometimes doubt there is, MadWiFi is an entirely separate entity to Atheros, which is none of: the owner, beneficial owner, nominee, trustee or any related or unrelated concept of ownership.

The wifi works great on my computer (Toshiba U305 - Gutsy Gibbon). However, it seems to have a bad interaction with the suspend to ram system. As the kernel in gutsy doesn't suspend properly on the toshiba, I am using the 2.6.24-2.4 kernel from Hardy which does suspend properly when the modules are not loaded. When they are loaded, attempting to suspend the computer kills the wifi connection and the computer is never suspended. The computer also fails to shutdown properly after a failed attempt to suspend it.

12/25/07 17:34:54 changed by anonymous

I believe the suspend to ram issues are related to the ATI drivers memory leak. Fixed in the latest release of the drivers from last Thursday.

When will/has this patch been incorporated into the version of MadWifi I can download from madwifi.org? I know I can get the patch and apply it myself (and get the kindly provided prepatched version!) but I'm just curious as to when I won't have to do that on a fresh install. Thanks.

When will/has this patch been incorporated into the version of MadWifi I can download from madwifi.org?

You obviously missed comment 55. However, if you are asking about when a new HAL version with AR5007 support will be available in a MadWifi release, the answer is: as soon as it's ready. Negotiations with Atheros in this regard are still in progress.

However, if you are asking about when a new HAL version with AR5007 support will be available in a MadWifi release, the answer is: as soon as it's ready. Negotiations with Atheros in this regard are still in progress.

Can you say by your experience how much time may it take? Will be a 64-bit version of the hal available during one-two monthes or it is better to me to sell my laptop?

I wouldn't mind using a limited feature temporary fix, if it could be done in a short timeframe, as long as it has support for 64bit OSes which some people must use. Seing as this bug has been going on for months I must ask, should I buy a new card, or should we wait?

01/23/08 11:15:27 changed by mrenzmann

01/28/08 16:53:12 changed by anonymous

this patched driver does not work with
IEEE 802.1X with Dynamic WEP Keys using EAP-PEAP/MSCHAPv2

using a recompiled wpa_supplicant v0.6.2 against this patched driver?

The hardware is

mini-pci AR5007EG
eee asus pc

Any Ideas?

01/30/08 08:45:54 changed by beechhorn@gmail.com

attachmentdmesg.txt added.

DMESG dump from kernel 2.6.24.

01/30/08 08:49:47 changed by beechhorn@gmail.com

Compiled this against 2.6.24 (not expecting it to work) however it does! Have attached a dmesg dump - just finding out if Atheros are being vocal about 5007 details - so that in an ideal work the 0.9.4 release would have support.

01/31/08 06:03:10 changed by mrenzmann

Please stop posting support requests to this already crowded ticket. They are expected to be carried to our regular support channels! All off-topic comments will be deleted from now on without further notice.

02/01/08 05:40:57 changed by anonymous

After some trouble initially manually patching a newer release, I uninstalled all madwifi builds and used the prepatched snapshot in the ticket description which worked perfectly with no issues (bye bye old cisco PCMCIA card :D :D). Please note that as explained in the ticket the ath5k module (if installed - it is on Fedora 8 and newer kernels I believe) needs to be blacklisted. Simply add blacklist ath5k to /etc/modprobe.conf

I do however have a question which I hope is classed as being in scope for this ticket (as per mrenzmann's coment above!) - can this patch be used with the latest snapshot and would there be any point in doing so? If so, would someone be able to create a prepatched version? I'd try it but after the trouble I have had I don't want to risk killing my config unless its worked for other people first!

Thanks.

02/03/08 16:47:22 changed by beechhorn@gmail.com

Added a new patch to remove dmesg errors in kernels 2.6.24+ - just copied the relevant changes from your existing changesets (searched for 2.6.24 in changesets). NOTE: Changesets 2814/5 add a trailing comma to the last parameter which causes and issue when you run patch-kernel/install.sh - the kernel fails to compile (using an ASUS eee with their Xandros 4 derivitive and GCC 4.1.2). Now to try the same with the power saving patches - keep up the good work!

02/06/08 12:48:05 changed by mrenzmann

From our IRC support channel:

12:45:52 < Tyczek> Just wanted to report that patch for atheros 5007 EG works with toshiba satellite a210-16f (it was reported as 5006 EG) :)

02/12/08 20:53:39 changed by mentor

description changed.

02/14/08 22:10:49 changed by migatxu

It works in a Toshiba A200 1NH with 2.6.23 kernel (Debian SID) with a 2.6.24-2 it doesn't compile (Debian SID)

02/15/08 09:56:15 changed by beechhorn@gmail.com

Migatxu - I've successfully compiled and used this (with the 2.6.24 patch) on kernel version 2.6.24.2.

02/15/08 11:45:23 changed by beechhorn@gmail.com

Omit the madwifi/ath/if_ath.c file from the patch as it is the packet injection part from aireplay-ng's patchset (my bad).

02/15/08 12:17:02 changed by mrenzmann

Sorry, I had to remove the patch, since it deleted the copyright notice from the patched HAL binary. We've been through that before.

02/17/08 01:12:06 changed by dodyrw@gmail.com

It work great in my toshiba u305. I was downloading the stable version, but get "HAL error 13".

But this patch work very nice. Just download this patch, then run make, make install.
And restart ubuntu. That's it. It should be able to detect any AP.

Note that neither the patch nor the prepatched snapshot tarball compile against kernel 2.6.24. This is a known issue, so no need to report this here. As soon as an update is available, it will be announced here.

02/21/08 04:21:04 changed by zhenyu.z.wang@intel.com

Hi, mine is asus eeepc. I've seen weird thing with atheros by using madwifi version here.
My pci id for atheros showed in 'lspci -n' is 168c:ff1b, which seems obviously wrong.
And only once, when I boot up, r2756 ath_pci load correctly and my wifi got working, then
pci id is 168c:001c, which is correct. I tried to reboot again, wifi failed to work again with
weird ff1b ids. I also reset bios and enable wlan option, no help.

Note that neither the patch nor the prepatched snapshot tarball compile against kernel 2.6.24. This is a known issue, so no need to report this here. As soon as an update is available, it will be announced here.

I haven't found this to be the case. It's compiled and installed without problem for me in in Fedora's Rawhide, running various versions of 2.6.24 and 2.6.25. (However, an update tonight, to their kernel 2.6.25-0.54.rc2.fc9 doesn't work with it. It compiles and installs, but doing modprobe ath_pci hangs the system.)

The one I had before that, 2.25-0.48.rc1.git2.fc9 worked without problem.

It's also worked without issue in the Ubuntu alphas, 2.6.24.5-generic and 2.6.24-8.generic.

Note that neither the patch nor the prepatched snapshot tarball compile against kernel 2.6.24. This is a known issue, so no need to report this here. As soon as an update is available, it will be announced here.

I haven't found this to be the case. It's compiled and installed without problem for me in in Fedora's Rawhide, running various versions of 2.6.24 and 2.6.25. (However, an update tonight, to their kernel 2.6.25-0.54.rc2.fc9 doesn't work with it. It compiles and installs, but doing modprobe ath_pci hangs the system.)
The one I had before that, 2.25-0.48.rc1.git2.fc9 worked without problem.
It's also worked without issue in the Ubuntu alphas, 2.6.24.5-generic and 2.6.24-8.generic.
Lastly, it's worked without issue in Arch, kernel 2.6.24-ARCH.

To add to this, the next day's Fedora update, to 2.6.25-0.64.rc2.git5.fc9 works again.

02/24/08 21:31:53 changed by ilredil@yahoo.com

The patch couldn't be cleanly applied to 0.9.4, however the tarball compiled and worked fine. I'm using an acer 5050-3785 with the AR5BXB63 card. I'm using the linux 2.6.24 kernel, and have 64-bit support enabled (Processor type and features -> 64 bit Memory and IO resources). Also, this tarball seems to include injection support (which is awesome) for those who were wondering.

Personally, I'm not worried about the error messages; the card works, and that's what's most important to me. Thanks for your hard work guys! If you think the errors are worth tracking down, e-mail me and I'll get you whatever information you need.

02/25/08 10:04:41 changed by anonymous

thank you

02/25/08 21:25:58 changed by Darksurf

Does this work for the Atheros AR5007-AP edition? (using an asus M3A32-MVP Deluxe/+Wifi)

I'm not really sure where this goes, but after a lot of trial and error with other posts, I got the patched version working with my Compaq Presario f750US, Fedora Core 7-i386. As mentioned before lspci listed my card as AR5006EG.

I'm not really sure where this goes, but after a lot of trial and error with other posts, I got the patched version working with my Compaq Presario f750US, Fedora Core 7-i386. As mentioned before lspci listed my card as AR5006EG.

Sorry as a followup: This worked before I installed the nvidia driver, but failed after words. I think it had to do with the new kernel. I had to make a symlink for the new /build file for the new kernel as I was getting a KERNELPATH error:

ln -s /usr/src/kernels/`uname -r`-i686 /lib/modules/`uname -r`/build

This allowed me to make / make install the patched source again. My module still didn't show up so I blacklisted the ath5k module:

echo "blacklist ath5k" >> /etc/modprobe.d/blacklist

Then I rebooted and iwconfig recognized it. Woohoo!

02/28/08 04:34:26 changed by kevmif@yahoo.com

Has anyone verified the latest patch?
I'm unable to try it at the moment but would like to know how much success others have had with it.

02/28/08 08:22:22 changed by beechhorn@gmail.com

Have just tried the latest r3365 patch and I get a HAL Status 13 message.

02/28/08 22:30:21 changed by lukassoftwares a t gmail.com

I've got a similar problem (laptop ASUS F3Ka ap031). Wifi module is detected as AR5006EG, rev 1. So far, I've tried several ways (ndiswrapper, madwifi, ath5k). However, best I was able to do was this status 13.

P.S. Sorry for my terrible english

02/29/08 07:35:21 changed by mrenzmann

description changed.

New prepatched tarball based on r3366 now available (see ticket description). This new tarball also compiles against kernel 2.6.24.

02/29/08 09:48:21 changed by beechhorn@gmail.com

Still getting HAL 13 with this r3365/6 - latest version I can get working is r3348 - something must of changed HAL wise between r3348 and r3365.

02/29/08 10:37:28 changed by beechhorn@gmail.com

The only differences I can see (beyond formatting/text) between r3348 and r3366 is in ath/if_ath.c and Minstrel (which I use).

For the record, the patch tarball I downloaded on 2/24 worked on my Acer, which has an AMD 64 in it. Model: AMD Turion(tm) 64 Mobile Technology MK-38. I get a ton of errors, as I mentioned above, but the driver functions properly. I'm using Slackware 12, custom kernel, and hal-0.5.9.1 (according to pkgtool). If you need tech support on this, please check the check regular support channels first (see link above). If you have a specific question about my system, you can e-mail me with a subject that is obviously not spam and I'll get back to you.

It has all been said: only experimental support so far for 32bit, the usual platform support is work in progress. As soon as the current situation changes we will notify folks here in this ticket and elsewhere.

Once again: refrain from asking for updates here, and move all support requests (including thins like "help, that stuff doesn't compile!!1") to our regular support channels.

For those with x86_64 machines: you guys can run x86 32-bit Linux distributions and apply this patch. That will work, and there won't be a significant (if any) performance hit for this. Everything will work pretty much the same, you just won't have the true 64-bitness -- and that essentially just means your numbers don't go quite as high. It also means you're susceptible to the Year 2038 problem, but hopefully the chipset support will be fixed for 64-bit by then. ;)

The OS is Debian sid with kernel 2.6.24 running on Asus EEE PC, and r2756 patched with madwifi-ng-0933.ar2425.20071130.i386.patch.

I'd like to post the segfault log (which only shows when 'modprobe -r ath_pci' is done in the "root terminal" before starting X, not in terminal emulators) but I can't record it (even with /usr/bin/script). I didn't find anything in /var/log/* neither.

For the record, the patch tarball I downloaded on 2/24 worked on my Acer, which has an AMD 64 in it. Model: AMD Turion(tm) 64 Mobile Technology MK-38. I get a ton of errors, as I mentioned above, but the driver functions properly. I'm using Slackware 12, custom kernel, and hal-0.5.9.1 (according to pkgtool). If you need tech support on this, please check the check regular support channels first (see link above). If you have a specific question about my system, you can e-mail me with a subject that is obviously not spam and I'll get back to you.

So are you using a 64-bit kernel or just a 64-bit processor with a i386 kernel?

For those with x86_64 machines: you guys can run x86 32-bit Linux distributions and apply this patch. That will work, and there won't be a significant (if any) performance hit for this. Everything will work pretty much the same, you just won't have the true 64-bitness -- and that essentially just means your numbers don't go quite as high. It also means you're susceptible to the Year 2038 problem, but hopefully the chipset support will be fixed for 64-bit by then. ;)

04/03/08 13:59:48 changed by beechhorn@gmail.com

Brilliant that there is ath5k support.

However the code could do with some code modularisation (the MVG complexity goes up to 64 for some functions). Looking at the bottom of ath5k_hw_reset for instance there is a duplicate "if (ah->ah_version == AR5K_AR5212)" - combining the two reduced code complexity to 63. Is it worth me trying to modularise the code and if so where should patches be sent?

sorry, been confused by name of interface and have't read whole post - ath0 is typical for VAP, last time i tried ath5k it created wlanX devices - what i have written about wlanconfig is only true if you use madwifi

sorry, been confused by name of interface and have't read whole post - ath0 is typical for VAP, last time i tried ath5k it created wlanX devices - what i have written about wlanconfig is only true if you use madwifi

mickflemm reported in ath5k-devel that the radio isn't being turned on and he's working at it.

04/07/08 07:49:15 changed by mpalencia at mgcreaciones.com

I can confirm it works, my laptop is an acer aspire 4520, turion x2 1.6ghz, atheros 5007eg
The older patches didnt work, but the current one, the 3366 works like a charm, much better than ndiswrapper which was giving me major headaches.
Distro: ubuntu 804 beta

04/08/08 21:32:59 changed by giovanni

Works perfectly on Samsung R60+ running Hardy on latest official kernel 2.6.24-15, it used to give me some error messages on bootup and segfault when trying to manually unload the module, but the patch solved everything. Great work!

04/09/08 10:59:34 changed by alan-jenkins@tuffmail.co.uk

There are some reports that this doesn't "work perfectly" (thats what the hardware compatability page says :-). forum.eeeuser.com/viewtopic.php?id=18158

Apparently the patch here doesn't work as well on the ASUS EEEPC as either the binary driver from ASUS (included with the installed OS), or the windows driver (which can be run using ndiswrapper). Signal strength is reduced and the connection drops out.

My experience is also that the driver from the installed OS seemed to have better range; I have to stay closer to the router now I've reinstalled using r3366+ar5007.

04/16/08 14:46:46 changed by anonymous

The latest patched snapshot, r3366+ar5007 doesn't work as well for me as did the earlier one r2756+ar5007. On Fedora rawhide, the 3366 version kept losing connectivity. Going back to r2756 fixed the problem. This is an Acer Aspire 4720z.

Mandriva's "one" CD and probably the other non-free ones, now offer out of the box support for this card.

did you have some freeze ?
sometimes i have like a kernel panic, nothing respond and the caps lock led blink

some other times, when using amule a long time, network freeze, no more connection, no ping possible ... the solution : need to click on the network monitor applet and tell the wifi to reconnect to the Acces point

I tried to download the snapshot
snapshots.madwifi.org/madwifi-ng/madwifi-ng-r2756-20071018.tar.gz
but unfortunately the link is broker
So I tried with the readily-patched snapshot (which link works), I tried with "make", at the beginning the program was unable to detect kernel version, so I replaced line

KERNELRELEASE := $(shell $(CC) -I $(KERNELPATH)/include -E $(TOP)/kernelversion.c | grep uts_release | cut -f2 -d'"')
with
KERNELRELEASE := /usr/src/linux-2.6.22.17-0.1
at that point exucuting again the program with "make" command I am having the following message:

at the beginning the program was unable to detect kernel version, so I replaced
line

You should not edit the Makefile until you know exactly what you do. The issue you describe is one that is not related to this ticket, so I have opened a new ticket (#1901) for it. Please follow up there.

04/22/08 14:40:09 changed by anonymous

Loaded the pre-compiled patch for ar5007eg on 8.04 rc1, This is on an Acer Extensa 5420 laptop. Works great! my wife is very happy!

thanks!

04/22/08 19:38:52 changed by ctrlaltca

Works under slamd64 (64 bit) with ndiswrapper 1.52 and the net5211 windows driver you can found at http: //www.freefilehosting.net/files/3blea (url obfuscated)

04/22/08 22:25:28 changed by professor

Does anyone know if the driver and the patch, can put the card in monitor mode, or is this a problem. I have tried with no sucess.

04/23/08 17:16:30 changed by anonymous

using Ubuntu Hardy, applied patch "madwifi-nr-r3366+ar5007" => it works -- BUT!!!
I can't connect WPA-wise. Without security works flawless.

Any idea?

04/23/08 23:46:02 changed by Martin

I downloaded snapshots.madwifi.org/madwifi-ng/madwifi-ng-r2756-20071018.tar.gz
execute the comand make
returned program execution that I get http: //madwifi.org/attachment/ticket/1679/terminal.pdf?format=raw

when executing the comand modprobe ath_pci a new blank command line is presented in the terminal
running iwconfig I have
l0 no wireless extensions.
eth0 no wireless extensions.

nothing appears in the network devices apart from the wired lan card

04/25/08 13:51:57 changed by jgxenite+madwifi@gmail.com

Snapshot r3366+ar5007 worked fine for me on my Sony Vaio VGN-NR21J (with the AR5007EG chipset). Thanks very much for this!

05/02/08 09:37:50 changed by Andro

This patch works perfect. My hardware is a fujitsu-siemens Amilo P2540. I am using Fedora 8 and had two different kernels in the meantime and it works just great.

05/04/08 14:30:21 changed by DaRK

Just upgraded to ubuntu hardy was using gutsy with 2.6.22-14-generic, which worked perfectly and like usual after a kernel upgrade i have to reinstall the patched madwifi but now when every time i install it gnome has issues (freezes for a couple mins with an error about gnome settings manager, desktop hasn't loaded yet, then after a while everything starts up fine and works)
Using 2.6.24-17-generic i believe this became available about 2 days ago and as far as i understand 2.6.24-16-generic didn't have any issues though haven't tested.
Any ideas as to whats happening?

I just installed the latest Debian unstable kernel (2.6.25-1) and did my usual "make/make install" ritual with the prepatched "r3366" driver above (which has worked for me on every kernel since 2.6.22). Unfortunately, it's met it's match with .25, which threw up errors during the make process. I double-checked that I was using the correct version of build-essential and the appropriate kernel headers, was sure to "make clean" beforehand, but still no dice.

OK, the kernel I used is in the unstable Debian branch, so I'm hoping whatever's wrong will be fixed before it percolates through to the testing branch, but I just thought I'd add my two cents here.

05/05/08 08:07:15 changed by anonymous

I run rawhide.... 2.6.25 has been working fine for me since the RC versions.

OK, the kernel I used is in the unstable Debian branch, so I'm hoping whatever's wrong will be fixed before it percolates through to the testing branch, but I just thought I'd add my two cents here.

A couple of new build tools came down the Debian unstable pipe today, so I installed them and tried compiling the madwifi driver again. It worked like a charm. Yippee! So all is well with this patch and the Debian 2.6.25-1 kernel.

05/06/08 09:12:26 changed by Gustavo

Anybody has tried to use this card with opensuse 11 beta 2? My opensuse 10.3 works just fine with the patched driver but i dont want to upgrade if the wireless wont work. Any comment would be appreciated. Thanks.

gus at ahivamos.net

05/06/08 18:03:50 changed by anonymous

Hi.
Does someone knows if the driver ath5k present in kernel 2.6.25.1 support this card?
168c:001c (rev 01)

Thanks.

05/07/08 03:03:58 changed by rmhmpt@gmail.com

Hello guys

Just to let you know I'm using Kubuntu 8.04 with KDE 4.0 on a Packard Bell EasyNote? MX-61. I've been struggling with the wifi board (it's the famous AR5007EG) and tried out the patched version 3366. It worked fined and am now, as we speak, inputing this information through wireless! ;)
I'm using the 32bit Kubuntu version. Just to let you know. And to give you my thanks! And to add one more laptop to the list.

05/07/08 07:07:17 changed by mrenzmann

We would like to thank all participants in their submissions of successful results. We now know that the patched 3366 version works on most of the recent linux distribution releases.

In order to maintain a smaller page size for this ticket, we would like to request that all submissions be related to a deficiency of the patched source code, or a possible improvement to the package.

Thank you for all your input and successes.

Thanks to "John Elsman" for his help with the wording of the statement above.

I am sorry to keep adding on this looong thread but, are there any plans to have this patch ported to the main version of the driver ? I only ask because I am a newbie and these kind of things keep other people I know and myself away from Linux.
I for one don't know how to apply the 3366 patch to my machine , an HP 6810 with Ubuntu 8.04 on it and am forced to boot lovely Vista every time I need wireless.

05/09/08 04:13:41 changed by jordy.vassily@gmail.com

Hello:
I've made everything to install r3366 on my laptop Lenovo R61 but does not work at all. I cannot scan any wireless network.
This release of MadWifi isn't supported in my laptop. Truly sorry, everything else works, even the fingerprint reader. No compatibility on Ubuntu Hardy 8.04...
Anyone had success with this scenario? Thanks a lot.

05/18/08 09:05:03 changed by mwg@mwg.dp.ua

There is madwifi-eeepc-source_0.9.4+r3366-1_i386.deb at eeepc.debian.net/pool/non-free/m/madwifi-eeepc/
which is installable by module-assistant in Debian/Ubuntu. It would be nice to rebase it back to r2756 and give off to us poor Atheros users :>

At the very least, if the 168c:001c is detected, the current drivers should not attempt to load.

So that users with AR5006-based cards will have no working driver, too? Obviously a bad idea.

However, a solution is on its way, one that will be available for all supported architectures and will be integrated well in MadWifi (no more patching required). It's been worked on very hard, to get rid of a few last bugs before the solution is made available. Please be patient for a little longer.

I wish to add my thanks for all your hard work. The latest kernels, 2.6.25, have the build fail with an skb error. There is a patch at madwifi.org/ticket/1935
but it doesn't compile with either r2756 or r3366. (I added a comment there as well.)

I wish to add my thanks for all your hard work. The latest kernels, 2.6.25, have the build fail with an skb error. There is a patch at madwifi.org/ticket/1935
but it doesn't compile with either r2756 or r3366. (I added a comment there as well.)
Again, many thanks for all the work you've done for all of us.

Sorry, I mistyped last night. I meant the 2.6.26 kernel.

Thanks

05/30/08 21:44:42 changed by wahjava@gmail.com

Hi all,

There is a good news. I'm able to use this wifi chipset, in my Gentoo GNU/Linux (amd64/hardened) box, in the native linux kernel driver mode. No ndiswrapper thingie required.

I'm that hal recently (on 28th May, 2008) posted by sam in his public_html directory at people.freebsd.org. I just replaced that hal with the madwifi's hal and now I'm running fine with no issues.

HTTP URL: people.freebsd.org/~sam/ath_hal-20080528.tgz

The site is unreachable at the moment on IPv4 internet, so I downloaded it by connecting to it over an IPv6 tunnel.

Hope to see a blob-free driver soon.

06/04/08 09:24:55 changed by proski

status changed from new to assigned.

owner set to proski.

The tarball referenced in the previous comment does not include any "patch from Sam". It doesn't even include any patches attached to this ticket. Nor would it download any patches. It's just a snapshot from Subversion with HAL replaced. But install.sh would permanently remove ndiswrapper with all configuration files, which is highly irresponsible. Please be careful about running software not hosted at madwifi.org and referenced by unregistered users.

06/04/08 14:29:01 changed by mrenzmann

Official snapshots which include the new HAL v0.10.5.6 are available for download here.

06/04/08 15:03:55 changed by schmolle

06/05/08 03:55:26 changed by proski

status changed from assigned to closed.

resolution set to duplicate.

It's turning into a soapbox despite all pleas to use regular support channels. I'm closing this bug as a duplicate of #1192. Please report any problems specific to the new HAL to the mailing lists. Any general questions, including compile problems that exist in the trunk, are not welcome here.

06/07/08 07:17:05 changed by mentor

status changed from closed to reopened.

resolution deleted.

06/07/08 07:19:58 changed by mentor

status changed from reopened to closed.

resolution set to invalid.

summary changed from Support for AR2425 (AR5007EG) chipset to Patch for AR2425 (AR5007EG) chipset.

Sorry, changing resolution.

This ticket concerns a patch for AR2425 support that is no longer relevant. The issue will be further handled in #1192.

I imagine further posts will probably be swiftly deleted.

06/12/08 22:03:08 changed by proski

The problem with sysctl was fixed r2814. Using obsolete snapshots means that problems fixed in later revisions will come up. Nobody is going to fix the snapshots, and the testing results are irrelevant at this point. Please stop posting in this ticket.

06/15/08 13:24:49 changed by anonymous

As this ticket will be found by people doing google searches on the card, the note to see ticket 1192 and links to the working snapshot should probably go in the note at the top. Otherwise, I suspect many people will read the summary and download the now somewhat out of date 2756 snapshot.

06/16/08 02:20:25 changed by proski

That's the whole point. Those who cannot read the whole ticket will comment here rather than pollute more useful tickets. Anyway, the long term solution is a release. Snapshots cannot be supported for general public. And tickets are not the place to ask for personal support.

08/20/08 20:56:36 changed by James Black

i followed the instructions and were able to get wireless workign on my laptop with the madwifi driver.
i have a toshiba p205d-s7438 amd x64 in hardy heron.
i did it using "madwifi-hal-0.10.5.6-r3835-20080801"
i didn't have the restricted drivers before doing this.
im using gnomes network manager and not wcid.
i dont not use a patch.
i hope this helps someone else.

08/20/08 20:58:24 changed by James Black

08/24/08 05:19:23 changed by [mad]Berry

11/28/08 11:46:14 changed by onee

thank's I will try this driver

12/28/08 22:43:50 changed by proski

keywords deleted.

cc deleted.

pending changed.

11/17/09 15:15:07 changed by junkert.ferenc@gmail.com

Hi, on ubuntu with kernel 2.6.28-16-generic #55-Ubuntu SMP Tue Oct 20 19:48:32 UTC 2009 x86_64 GNU/Linux. I have make the install steps, following the Madwifi first Steps guide. I tried install the driver like madberry's instructions, but working not. Any help? (If i know good, the right installed driver would be "Official snapshots which include the new HAL v0.10.5.6")