I didn't have any problems compiling madwifi-driver against kernel 2.6.7, but with recent 18.104.22.168 (development-sources) this is the error message:
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c: In function `ath_sysctl_handler':
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3389: error: too few arguments to function `proc_dointvec'
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c: At top level:
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3417: warning: initialization from incompatible pointer type
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3420: warning: initialization from incompatible pointer type
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3422: warning: initialization from incompatible pointer type
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3424: warning: initialization from incompatible pointer type
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3426: warning: initialization from incompatible pointer type
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3428: warning: initialization from incompatible pointer type
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3430: warning: initialization from incompatible pointer type
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3432: warning: initialization from incompatible pointer type
/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.c:3434: warning: initialization from incompatible pointer type
distcc ERROR: compile on localhost failed
make: *** [/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver/if_ath.o] Error 1
make: *** [_module_/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver] Error 2
make: Leaving directory `/usr/src/linux-22.214.171.124'
make: *** [all] Error 2
make: Leaving directory `/var/tmp/portage/madwifi-driver-0.1_pre20040726/work/driver'
make: *** [all] Fehler 2
!!! ERROR: net-wireless/madwifi-driver-0.1_pre20040726 failed.
!!! Function src_compile, Line 43, Exitcode 2
!!! (no error message)
By the way: I used the same config to compile kernel 2.6.7 and 126.96.36.199
Steps to Reproduce:
1. emerge, compile & install kernel 188.8.131.52 (development-sources) & boot with new kernel
2. try emerging madwifi-driver
compile madwifi cleanly
You might want to see a bug filed on the project homepage:
I have the exact same problems as you. madwifi-driver-0.1_pre20040726.ebuild compiled fine in 2.6.7 (official vanilla sources), but it fails with the error you mentioned above with 184.108.40.206 (official vanilla sources).
I'm also having the identical problem with gentoo-dev-sources-2.6.8-r1
same problem with gentoo-dev-sources-2.6.8 here.
Same problem here. I have found a patch on https://sourceforge.net/tracker/index.php?func=detail&aid=1008185&group_id=82936&atid=567755, but I don't know how to patch the ebuild.
Created attachment 38225 [details, diff]
Cleaned up the patch originating at the SourceForge site (linked from a
previous comment) by removing unneeded/mistakenly included stuff. It should now
apply cleanly to madwifi-driver-0.1_pre20040824 (without any line relocations).
*** Bug 60626 has been marked as a duplicate of this bug. ***
Created attachment 38228 [details, diff]
Fixed the madwifi ebuild to apply the previous patch.
Don't know if anybody needs this, but here are the instructions on how to apply the previous two patches (simple but dirty way):
1. cp proc_dointvec.patch /usr/portage/net-wireless/madwifi-driver/files
2. cd /usr/portage/net-wireless/madwifi-driver
3. patch -p0 < madwifi-driver-0.1_pre20040824.ebuild.patch
4. ebuild madwifi-driver-0.1_pre20040824.ebuild digest
5. ACCEPT_KEYWORDS=~x86 emerge madwifi-driver-0.1_pre20040824
Hope it works for you too!
Also occurs on 2.6.8-r3. Patch works to resolve.
Things work now with gentoo-dev-sources 2.6.8-r3 and madwifi-driver 0.1_pre20040824-r1. I don't know if that patch was merged or what, but thanks for whomever fixed it...
Compiles, but in use tells me that the card cannot go into scan mode.
Mobile Herd: Seems solar has fixed this but not marked this bug as resolved:
29 Aug 2004; <firstname.lastname@example.org>
update for 2.6.8 kernels
reillyp: I suspect that the problem you mention in comment #11 is not related to this bug or the resolution. The patch applied in the new ebuild seems only to adjust for a Linux driver API change.
Maybe you should open another bug describing the exact problems you have? Also, you might want to check the SourceForge bug tracker (although I couldn't find anything similar from a quick look):
I was not on the CC: of this bug.
Are we happy with madwifi-driver now? Any reason to not mark 0.1_pre20040824-r1 stable? Who has tested on 2.4.x kernels?
changing resolution to TEST-REQUEST
Stable? Not really 100%, but (it seems) it is the only option for this hardware. I have experienced total hangs when combining with iproute2 (used by wondershaper) from time to time. Irritating but not frequent enough to merit further investigation (not sure it is even this driver).
2.4 kernels? Works on Debian with CVS from sometime in March, but I haven't tested on Gentoo with a 2.4 kernel.
it works for me in gentoo-dev-sources-2.6.8-r3. No hitches whatsoever.
Closing as per comment #16.