Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 262761
Alias:
Product:
Component:
Status: NEW
Resolution:
Assigned To: Mobile Herd <mobile@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: pyrophobicman@gmail.com
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
madwifi-ng-0.9.4-r1.ebuild ebuild for the latest version in portage with the fix text/plain pyrophobicman@gmail.com 2009-03-17 03:14 0000 3.27 KB Details
2.6.29.patch-15260.out Error log for that patch text/plain Maxim Grechkin 2009-03-24 21:29 0000 28.67 KB Details
madwifi-ng-0.9.4-r2.diff <2.6.29 CHECK KMOD / >=2.6.29 patch r3907 patch Tobias Kral 2009-03-26 10:24 0000 973 bytes Details | Diff
madwifi-ng-0.9.4-2.6.29-r3907.patch upstream patch for 2.6.29 text/plain Tobias Kral 2009-03-26 10:25 0000 40.41 KB Details
madwifi-ng-0.9.4-r2-with-injection.diff Diff to use injection in madwifi with 0.9.4 with kernel 2.6.29 patch Draco Levanah 2009-04-09 21:13 0000 1.31 KB Details | Diff
madwifi-ng-r3925.patch Patch for injection for 2.6.29 patched sources patch Draco Levanah 2009-04-09 21:14 0000 1.22 KB Details | Diff
madwifi-ng-0.9.4-2.6.29-r3907.patch Upstream patch with corrected paths patch Ivan Kukharchuk 2009-04-12 13:54 0000 37.97 KB Details | Diff
madwifi-ng-0.9.4-r2.ebuild final version of ebuild text/plain Sergey Zolen 2009-05-30 10:31 0000 3.28 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 262761 depends on: Show dependency tree
Bug 262761 blocks: 264722
Votes: 40    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.








View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2009-03-17 03:10 0000
kernel 2.6.29 gets rid of CONFIG_KMOD...

a simple patch like this should work:

CONFIG_CHECK="CRYPTO WIRELESS_EXT SYSCTL"
kernel_is lt 2 6 29 && CONFIG_CHECK="${CONFIG_CHECK} KMOD"

------- Comment #1 From pyrophobicman@gmail.com 2009-03-17 03:14:25 0000 -------
Created an attachment (id=185252) [details]
ebuild for the latest version in portage with the fix

just replaced the old CONFIG_CHECK line with a new two.

------- Comment #2 From Lars Wendler (Polynomial-C) 2009-03-17 20:26:56 0000 -------
Please don't post full ebuilds but diffs showing the changes you did to the
ebuild. That would be much more handy for our devs.

------- Comment #3 From Mike Auty 2009-03-24 01:51:47 0000 -------
That alone won't solve all the problems.  You'll probably also need the
following patch (taken from the official madwifi-ng subversion repository)

http://madwifi-project.org/changeset/3902?format=diff&new=3902

Note, I haven't tested this yet, so I dunno if it'll solve all the problems
yet...

------- Comment #4 From Maxim Grechkin 2009-03-24 21:29:31 0000 -------
Created an attachment (id=186153) [details]
Error log for that patch

------- Comment #5 From Mike Auty 2009-03-24 22:04:06 0000 -------
I got a different error, fuzzy patching at the start, with failed blocks from
midway through to the end, but you're right the patch as it stands won't apply
cleanly.  I haven't had time to examine it further, and since 2.6.29 apparently
supports hostapd through the mac80211 interface, I'm going to be spending my
time on getting that going, rather than battling with the madwifi drivers. 
There will have been some changes in the subversion files between that patch
(r3902) and the 0.9.4 tarball.  I didn't think there were many, but obviously
there were enough to cause problems.  It might just be worth wrapping up the
latest checkout and compiling off of that (some kind of madwifi-ng-0.9.4_r3902
type ebuild).  It could either be based on subversion with a fixed revision, or
a snapshot.  Unfortunately, as I say, my time for this project is limited. 
Sorry...

------- Comment #6 From Steev Klimaszewski 2009-03-26 02:08:48 0000 -------
Yeah, I just updated to 2.6.29 and got bit - for the moment ath5k works for me,
although I do also apply the patch from aircrack-ng to be able to use monitor
mode, I still prefer madwifi-ng - I'm looking in to it now, so I should get
fixed soon, unless pva beats me to it :)

------- Comment #7 From Mike Auty 2009-03-26 10:06:16 0000 -------
I'd thought monitor mode (and injection) worked fine for ath5k out of the box
since 2.6.27_rc3 onwards, but fragmentation attacks under mac80211 needed a
patch?

------- Comment #8 From Tobias Kral 2009-03-26 10:24:07 0000 -------
Created an attachment (id=186313) [details]
<2.6.29 CHECK KMOD / >=2.6.29 patch r3907

------- Comment #9 From Tobias Kral 2009-03-26 10:25:46 0000 -------
Created an attachment (id=186314) [details]
upstream patch for 2.6.29

Here's the complete changeset for the 0.9.4 branch:
http://madwifi-project.org/changeset/3907?format=diff&new=3907

------- Comment #10 From Tobias Kral 2009-03-26 10:28:37 0000 -------
(From update of attachment 186314 [details])
Patch applies, but I get compiler errors in ieee80211.c 

(In reply to comment #7)
At least master mode doesn't work. That's whyt I need. (and the fixed sqlite
performance bug in 2.6.29)

------- Comment #11 From Mike Auty 2009-03-26 10:36:38 0000 -------
Tobias, thanks for the patches, I'll give them a go later on.  

You can't set it directly into master mode, no, but you should be able to run
it as an access point using hostapd (which has been updated to use cfg80211 to
do its stuff, see the wireless section of
http://kernelnewbies.org/Linux_2_6_29).  That's what I'm investigating at the
moment...

------- Comment #12 From Robin Bankhead 2009-03-26 12:31:22 0000 -------
Personally I'm still not getting a dickie-bird with ath5k, can't even connect
in station mode, so I hope these fixes can make their way to portage soon.

------- Comment #13 From Karol Czeryna 2009-03-31 16:23:55 0000 -------
With madwifi-ng-0.9.4-2.6.29-r3907.patch madiwfi-ng compiles and working fine,
just add it to portage and fix ebuild ;) greets...

------- Comment #14 From Draco Levanah 2009-04-09 21:13:17 0000 -------
Created an attachment (id=187820) [details]
Diff to use injection in madwifi with 0.9.4 with kernel 2.6.29

------- Comment #15 From Draco Levanah 2009-04-09 21:14:21 0000 -------
Created an attachment (id=187822) [details]
Patch for injection for 2.6.29 patched sources

------- Comment #16 From Draco Levanah 2009-04-09 21:18:45 0000 -------
(From update of attachment 187820 [details])
Using injection flag and the 2.6.29 patch ended in failure, i downloaded the
new patch (r3925) and adapted it so it could fit along with the 2.6.29 patch

------- Comment #17 From Ivan Kukharchuk 2009-04-12 13:54:43 0000 -------
Created an attachment (id=188087) [details]
Upstream patch with corrected paths

Corrected paths in the upstream patch to be used from portage.

------- Comment #18 From Jakub Novak 2009-04-14 08:13:34 0000 -------
I confirm that unpacking ebuild madwifi-ng-0.9.4-r1.ebuild and manually
patching with madwifi-ng-0.9.4-2.6.29-r3907.patch works for me (didn't try with
USE="injection").

------- Comment #19 From Jakub Novak 2009-04-14 08:14:17 0000 -------
Sorry, forgot to add:
Linux version 2.6.29-gentoo-r1 (root@hacktop) (gcc version 4.3.3 (Gentoo
4.3.3-r2 p1.1, pie-10.1.5) ) #4 SMP Mon Apr 13 22:45:39 CEST 2009

------- Comment #20 From Karol Czeryna 2009-05-01 08:55:21 0000 -------
with gcc4.4 madwifi-ng doesn't compile...
cc1: warnings being treated as errors
/var/tmp/portage/net-wireless/madwifi-ng-0.9.4-r1/work/madwifi-0.9.4/net80211/ieee80211_linux.c:
In function 'ieee80211_notify_sta_stats':
/var/tmp/portage/net-wireless/madwifi-ng-0.9.4-r1/work/madwifi-0.9.4/net80211/ieee80211_linux.c:260:
error: the frame size of 1060 bytes is larger than 1024 bytes
make[2]: ***
[/var/tmp/portage/net-wireless/madwifi-ng-0.9.4-r1/work/madwifi-0.9.4/net80211/ieee80211_linux.o]
Error 1
make[2]: *** Waiting for unfinished jobs....
cc1: warnings being treated as errors
/var/tmp/portage/net-wireless/madwifi-ng-0.9.4-r1/work/madwifi-0.9.4/net80211/ieee80211_wireless.c:
In function 'ieee80211_ioctl_iwaplist':
/var/tmp/portage/net-wireless/madwifi-ng-0.9.4-r1/work/madwifi-0.9.4/net80211/ieee80211_wireless.c:1468:
error: the frame size of 1288 bytes is larger than 1024 bytes
make[2]: ***
[/var/tmp/portage/net-wireless/madwifi-ng-0.9.4-r1/work/madwifi-0.9.4/net80211/ieee80211_wireless.o]
Error 1
make[1]: ***
[_module_/var/tmp/portage/net-wireless/madwifi-ng-0.9.4-r1/work/madwifi-0.9.4/net80211]
Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.29-gentoo-r2'
make: *** [all] Błąd 2

maybe needed some patch?

------- Comment #21 From Jakub Novak 2009-05-01 11:49:02 0000 -------
(In reply to comment #20)
> with gcc4.4 madwifi-ng doesn't compile...
> cc1: warnings being treated as errors
> /var/tmp/portage/net-wireless/madwifi-ng-0.9.4-r1/work/madwifi-0.9.4/net80211/ieee80211_linux.c:
> In function 'ieee80211_notify_sta_stats':
> /var/tmp/portage/net-wireless/madwifi-ng-0.9.4-r1/work/madwifi-0.9.4/net80211/ieee80211_linux.c:260:
> error: the frame size of 1060 bytes is larger than 1024 bytes
> make[2]: ***
> [/var/tmp/portage/net-wireless/madwifi-ng-0.9.4-r1/work/madwifi-0.9.4/net80211/ieee80211_linux.o]
> Error 1
> make[2]: *** Waiting for unfinished jobs....
> cc1: warnings being treated as errors
> /var/tmp/portage/net-wireless/madwifi-ng-0.9.4-r1/work/madwifi-0.9.4/net80211/ieee80211_wireless.c:
> In function 'ieee80211_ioctl_iwaplist':
> /var/tmp/portage/net-wireless/madwifi-ng-0.9.4-r1/work/madwifi-0.9.4/net80211/ieee80211_wireless.c:1468:
> error: the frame size of 1288 bytes is larger than 1024 bytes
> make[2]: ***
> [/var/tmp/portage/net-wireless/madwifi-ng-0.9.4-r1/work/madwifi-0.9.4/net80211/ieee80211_wireless.o]
> Error 1
> make[1]: ***
> [_module_/var/tmp/portage/net-wireless/madwifi-ng-0.9.4-r1/work/madwifi-0.9.4/net80211]
> Error 2
> make[1]: Leaving directory `/usr/src/linux-2.6.29-gentoo-r2'
> make: *** [all] Błąd 2
> 
> maybe needed some patch?
> 

Does it work with the patch I mentioned? (just add epatch line to the ebuild,
digest it, stick the patch into its files directory and try to emerge it). From
the backlog I got the impression this is already going upstream (portage or
madwifi ?), is it not ?

------- Comment #22 From Karol Czeryna 2009-05-01 13:55:50 0000 -------
I'm using funtoo and i send your patches to drobinns, he's added it, so i uses
your patch. With gcc4.3.3-r2 madwifi-ng compiles fine, dunno where is the
problem.

------- Comment #23 From Jakub Novak 2009-05-01 15:04:55 0000 -------
(In reply to comment #22)
> I'm using funtoo and i send your patches to drobinns, he's added it, so i uses
> your patch. With gcc4.3.3-r2 madwifi-ng compiles fine, dunno where is the
> problem.
> 

I see 'cc1: warnings being treated as errors'. Maybe it needs some option for
less strict error checking (or code sanity check from maintainers) ? I think
thats a probable thing to change with new version of gcc. I'm not good at this,
experts opinion please ?

------- Comment #24 From Daniel Drake 2009-05-16 15:18:32 0000 -------
ping... 2.6.29 is planned to go stable on 23rd may, would be nice to see this
fixed

------- Comment #25 From SATtva 2009-05-27 08:57:48 0000 -------
(In reply to comment #23)
> (In reply to comment #22)
> > I'm using funtoo and i send your patches to drobinns, he's added it, so i uses
> > your patch. With gcc4.3.3-r2 madwifi-ng compiles fine, dunno where is the
> > problem.
> > 
> 
> I see 'cc1: warnings being treated as errors'. Maybe it needs some option for
> less strict error checking (or code sanity check from maintainers) ? I think
> thats a probable thing to change with new version of gcc. I'm not good at this,
> experts opinion please ?
> 

(In reply to comment #23)
> (In reply to comment #22)
> > I'm using funtoo and i send your patches to drobinns, he's added it, so i uses
> > your patch. With gcc4.3.3-r2 madwifi-ng compiles fine, dunno where is the
> > problem.
> > 
> 
> I see 'cc1: warnings being treated as errors'. Maybe it needs some option for
> less strict error checking (or code sanity check from maintainers) ? I think
> thats a probable thing to change with new version of gcc. I'm not good at this,
> experts opinion please ?
> 

Right after emerge unpacks package source to tmpdir, look into
/var/tmp/portage/net-wireless/madwifi-ng-0.9.4-r1/work/madwifi-0.9.4/Makefile.inc.
Find the line starting with COPTS and remove -Werror flag. Then resume
compilation: compiler warning won't be treated as an error, and the package
will be built correctly.

------- Comment #26 From Robert T Childers 2009-05-27 22:47:32 0000 -------
I tried patching 0.9.4-r1 by hand and adding in the 0.9.4-2.6.29-r3907 patch
but I wasn't able to get it to properly compile. Jacob did you try patching the
ebuild or did you just manually patch it and run ./configure make to test that
it compiled?

------- Comment #27 From Jakub Novak 2009-05-28 07:07:54 0000 -------
(In reply to comment #26)
> I tried patching 0.9.4-r1 by hand and adding in the 0.9.4-2.6.29-r3907 patch
> but I wasn't able to get it to properly compile. Jacob did you try patching the
> ebuild or did you just manually patch it and run ./configure make to test that
> it compiled?
> 
I added epatch line to ebuild I think. I had old gcc at that time, I think it
had less strict error checking so it didn't die on some warnings. I'm pretty
sure theres either some cflag or pragma macro to lessen strict level although
fast google didn't turn up anything atm. Anyone who knows this off top of his
head could shoot perhaps ?

------- Comment #28 From Sergey Zolen 2009-05-30 10:31:40 0000 -------
Created an attachment (id=192965) [details]
final version of ebuild

Compile and work with or without injection on 2.6.29 kernel.

------- Comment #29 From Jason Komar 2009-06-01 00:18:31 0000 -------
This line:

kernel_is lt 2 6 29 && CONFIG_CHECK="${CONFIG_CHECK} KMOD"

in the posted madwifi-ng-0.9.4-r2 ebuild causes problems with Paludis. I posted
in the Paludis Trac and received this reply from ciaranm:

"The error occurs because the ebuild illegally displays information to stdout
during the metadata phase. That, in turn, happens because linux-mod.eclass
checks EBUILD_PHASE against 'depend' to see whether it should be quiet, but PMS
doesn't guarantee that EBUILD_PHASE will be set to that. So the fix is either
to stop calling horrible functions in global scope, or to fix qout in
linux-mod. Or preferably both."

Is there another way to do a CONFIG_CHECK conditionally dependant on kernel
version?

------- Comment #30 From Peter Volkov 2009-06-01 16:57:18 0000 -------
Thank you all, guys for your work. I decided to avoid patching of 0.9.4 release
to death and took upstream snapshot for 0.9.4 branch:
madwifi-ng-0.9.4.4030.20090529.ebuild.

It builds fine and seems to work. Please, test it ASAP as I'm going to request
stabilization in one week. I'm most interested if injection works or not, since
I've never used this feature. Leaving this bug open for stabilization...

------- Comment #31 From Robin Bankhead 2009-06-01 18:54:21 0000 -------
(In reply to comment #30)
> Thank you all, guys for your work. I decided to avoid patching of 0.9.4 release
> to death and took upstream snapshot for 0.9.4 branch:
> madwifi-ng-0.9.4.4030.20090529.ebuild.
> 
> It builds fine and seems to work. Please, test it ASAP as I'm going to request
> stabilization in one week. I'm most interested if injection works or not, since
> I've never used this feature. Leaving this bug open for stabilization...
> 

Forgive the inappropriate forum for asking, but the website confuses me
somewhat: will the snapshot you're taking include the AR242x support?

I dearly hope so, as ath5k support for this chipset is pitiful at present.

------- Comment #32 From Joël 2009-06-01 19:23:02 0000 -------
A BIG, BIG THANKS to Peter and others for their hard work !

Before today I couldn't upgrade to 2.6.29 + ath5k, because for me, the new
802.11 stack loses connection regularly. Most probably the stack's fault, since
it happens with different 802.11 drivers (intel 3945) too.

So, today madwifi compiles out of the box with 2.6.29, and runs great ! (I only
had to disable the "injection" use flag, because a patch file was seemingly
missing).

Again, great work !

------- Comment #33 From Devin Fallak 2009-06-04 04:31:58 0000 -------
Works fine on my Acer Aspire 5610Z, Atheros AR2413 802.11bg NIC. This is a
great improvement - just switched to kernel 2.6.29 today because of this! :)

------- Comment #34 From Robin Bankhead 2009-06-04 13:01:48 0000 -------
AR5007 (Netgear WPN511 CardBus adapter): works
AR2425 (MiniPCIe in Samsung NC10 netbook): does not work (I assume this answers
my question above).

------- Comment #35 From Sérgio Durigan Júnior 2009-06-17 20:51:48 0000 -------
Hello,

I'm having this problem using a 2.6.30 kernel (directly from kernel.org, not
using Gentoo's one).  Any news about it?

Thanks.

------- Comment #36 From Sérgio Durigan Júnior 2009-06-17 20:54:31 0000 -------
Ok, sorry, my question was more about "do you have any plans to make
madwifi-ng-0.9.4.4030.20090529.ebuild stable?".  Thanks.

------- Comment #37 From xo0ox 2009-07-10 18:03:17 0000 -------
AR2413 Mini-PCI Access-Point - works fine with madwifi-ng-0.9.4.4030.20090529
and Vanilla-Kernel 2.6.30.1

Thank you!

------- Comment #38 From Xander Hoogendoorn 2009-08-22 16:50:05 0000 -------
For some reason madwifi-ng-0.9.4.4030.20090529 fails to compile against 2.6.30.
The ebuild seems to figure out the kernel version correctly, but the actual
build script cannot and aborts with an error.

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug