@Juergen Adolph: If I am not mistaken, the madwifi-modules from Punky require the new kernel from voyage 0.6.1, which is built with gcc 4.3.2. So you need to update your kernel.<br><br>@Punky: I'll try the r3942 and let you know, though before trying older versions I think I tried the <a href="http://snapshots.madwifi-project.org/madwifi-trunk/madwifi-trunk-r3941-20090205.tar.gz">http://snapshots.madwifi-project.org/madwifi-trunk/madwifi-trunk-r3941-20090205.tar.gz</a> and I also had stuck beacons. Are you testing in an alix board too?<br>
<br><br><div class="gmail_quote">On Mon, Feb 23, 2009 at 9:38 AM, Kim-man 'Punky' TSE <span dir="ltr"><<a href="mailto:punkytse@punknix.com">punkytse@punknix.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all,<br>
<br>
Forgot to mention, please post your constructive feedback after testing these different branches. <br>
Right now, I am running a simple AP download test using hal-testing branch without any stuck bacon for almost 15 hours.<br>
<br>
To me, going back to 0.9.4rc2 is not my best option, unless at the end we have no stable madwifi. <br>
Regards,<br><font color="#888888">
Punky</font><div><div></div><div class="Wj3C7c"><br>
<br>
<br>
Kim-man 'Punky' TSE wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all,<br>
<br>
Apart from backport 0.9.4rc2, I have built whole lots of madwifi from different branches for testing, and they are now in<br>
<br>
<a href="http://www.voyage.hk/dists/experimental/madwifi/" target="_blank">http://www.voyage.hk/dists/experimental/madwifi/</a><br>
<br>
The branches are:<br>
hal-testing (openwrt/dd-wrt) : madwifi-modules-2.6.26-486-voyage_0.9.4+r3942.20090205haltesting-1+6.0-3_i386.deb <br>
hal-0.10.5.6 : madwifi-modules-2.6.26-486-voyage_0.9.4+r3942.20090205hal0.10.5.6-1+6.0-3_i386.deb <br>
hal-free : madwifi-modules-2.6.26-486-voyage_0.9.4+r3952.20090213free-1+6.0-3_i386.deb <br>
<br>
Regards,<br>
Punky<br>
<br>
Juergen Adolph wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br>
I installed the latest pkg from 22-Feb-2009:<br>
madwifi-modules-2.6.26-486-voyage_0.9.4~rc2-1+6.0-3_i386.deb<br>
<br>
and now, it works without any stuck beacon error - great!<br>
<br>
many thanks!<br>
<br>
regards,<br>
juergen<br>
<br>
----- "Panagiotis Malakoudis" <<a href="mailto:malakudi@gmail.com" target="_blank">malakudi@gmail.com</a>> schrieb:<br>
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ok, made some more progress!!!<br>
<br>
I patched the madwifi-source 0.9.4~rc2 with the diff file from<br>
<a href="http://madwifi-project.org/changeset/3696/madwifi/branches/madwifi-0.9.4" target="_blank">http://madwifi-project.org/changeset/3696/madwifi/branches/madwifi-0.9.4</a> <br>
so that it can compile under 2.6.26 and that fixed my "stuck beacon"<br>
problems. I haven't seen a single "stuck beacon" with this setup. It<br>
seems the wireless performance is quite slower than the same<br>
combination with 2.6.23, but I am still checking on this.<br>
<br>
<br>
<br>
On Sat, Feb 21, 2009 at 11:25 PM, Panagiotis Malakoudis <<br>
<a href="mailto:malakudi@gmail.com" target="_blank">malakudi@gmail.com</a> > wrote:<br>
<br>
<br>
It certainly isn't a voyage problem. It's a madwifi problem, but since<br>
voyage is used in many wireless applications, it becomes a voyage<br>
problem too unfortunately.<br>
<br>
Juergen 's settings didn't help me. I was struggling to find a<br>
solution, since I don't like the idea to stay in the old voyage<br>
version.<br>
I built voyage-kernel 2.6.23 with gcc 4.1.3 (2.6.23 doesn't compile<br>
with 4.3.2) and tried the madwifi-source of r3772. Again, I had stuck<br>
beacon errors and reboots.<br>
<br>
Then I used the madwifi-source of 0.9.4~rc2 and that fixed the<br>
problem!!! Unfortunately, madwifi-source 0.9.4~rc2 does not compile<br>
with 2.6.26. I get the following error:<br>
<br>
CC [M] /usr/src/modules/madwifi/net80211/ieee80211_power.o<br>
/usr/src/modules/madwifi/net80211/ieee80211_power.c: In function<br>
'ieee80211_pwrs<br>
ave':<br>
/usr/src/modules/madwifi/net80211/ieee80211_power.c:240: error:<br>
implicit declara<br>
tion of function '__skb_append'<br>
<br>
__skb_append became obsolete in 2.6.26.<br>
<br>
So, for now I'll be using 2.6.23 + madwifi 0.9.4~rc2 and I'll keep<br>
trying various older madwifi releases with 2.6.26 to see if I can find<br>
a working combination.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
On Sat, Feb 21, 2009 at 10:05 PM, Leigh Orf < <a href="mailto:orf@mailbag.com" target="_blank">orf@mailbag.com</a> > wrote:<br>
<br>
<br>
I just wanted to chime in as another person who has an alix 2d3<br>
running voyage 0.6.0 who has had the same problems with the stuck<br>
beacons, NETDEV watchdog timeout message, etc. Also, sometimes hostapd<br>
gets stuck in an infinite loop of auth/death which is only fixed bring<br>
ath0 down and up again. I subscribed to this list partially to see if<br>
these problems had a solution. I do not believe it is a voyage linux<br>
only problem. I look forward to trying out ath5k in access point mode<br>
- it isn't there yet.<br>
<br>
I have managed 8 days uptime max before the board reboots itself<br>
suddenly after a trickle of stuck beacons and NETDEV WATCHDOG: wifi0:<br>
transmit timed out messages. I will soon update to 0.6.1.<br>
<br>
Leigh<br>
-- <br>
Leigh Orf<br>
Assistant Professor of Atmospheric Science<br>
Room 130G Engineering and Technology<br>
Department of Geology<br>
Central Michigan University<br>
Mount Pleasant, MI 48859<br>
(989)774-1923<br>
Amateur radio callsign: KG4ULP<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Voyage-linux mailing list<br>
<a href="mailto:Voyage-linux@list.voyage.hk" target="_blank">Voyage-linux@list.voyage.hk</a><br>
<a href="http://list.voyage.hk/mailman/listinfo/voyage-linux" target="_blank">http://list.voyage.hk/mailman/listinfo/voyage-linux</a><br>
<br>
<br>
<br>
_______________________________________________<br>
Voyage-linux mailing list<br>
<a href="mailto:Voyage-linux@list.voyage.hk" target="_blank">Voyage-linux@list.voyage.hk</a><br>
<a href="http://list.voyage.hk/mailman/listinfo/voyage-linux" target="_blank">http://list.voyage.hk/mailman/listinfo/voyage-linux</a><br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
<br>
-- <br>
Regards,<br>
Punky<br>
<br>
Voyage Solutions (<a href="http://solution.voyage.hk" target="_blank">http://solution.voyage.hk</a>)<br>
* Embedded Solutions and Systems<br>
- Mesh Networking, Captive Portal, IP Surveillance, VoIP/PBX<br>
- Network Engineering, Development Platform and Consultation<br>
<br>
<br>
<br>
_______________________________________________<br>
Voyage-linux mailing list<br>
<a href="mailto:Voyage-linux@list.voyage.hk" target="_blank">Voyage-linux@list.voyage.hk</a><br>
<a href="http://list.voyage.hk/mailman/listinfo/voyage-linux" target="_blank">http://list.voyage.hk/mailman/listinfo/voyage-linux</a><br>
</div></div></blockquote></div><br>