Ok, made some more progress!!!<br><br>I patched the madwifi-source 0.9.4~rc2 with the diff file from <a href="http://madwifi-project.org/changeset/3696/madwifi/branches/madwifi-0.9.4">http://madwifi-project.org/changeset/3696/madwifi/branches/madwifi-0.9.4</a> so that it can compile under 2.6.26 and that fixed my "stuck beacon" problems. I haven't seen a single "stuck beacon" with this setup. It seems the wireless performance is quite slower than the same combination with 2.6.23, but I am still checking on this.<br>
<br><br><div class="gmail_quote">On Sat, Feb 21, 2009 at 11:25 PM, Panagiotis Malakoudis <span dir="ltr"><<a href="mailto:malakudi@gmail.com">malakudi@gmail.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;">
It certainly isn't a voyage problem. It's a madwifi problem, but since voyage is used in many wireless applications, it becomes a voyage problem too unfortunately.<br><br>Juergen 's settings didn't help me. I was struggling to find a solution, since I don't like the idea to stay in the old voyage version.<br>
I built voyage-kernel 2.6.23 with gcc 4.1.3 (2.6.23 doesn't compile with 4.3.2) and tried the madwifi-source of r3772. Again, I had stuck beacon errors and reboots.<br><br>Then I used the madwifi-source of 0.9.4~rc2 and that fixed the problem!!! Unfortunately, madwifi-source 0.9.4~rc2 does not compile 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 'ieee80211_pwrs<br> ave': <br>
/usr/src/modules/madwifi/net80211/ieee80211_power.c:240: error: 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 trying various older madwifi releases with 2.6.26 to see if I can find a working combination. <br><div><div></div>
<div class="Wj3C7c"><br><br><br><div class="gmail_quote">
On Sat, Feb 21, 2009 at 10:05 PM, Leigh Orf <span dir="ltr"><<a href="mailto:orf@mailbag.com" target="_blank">orf@mailbag.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;">
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>
<font color="#888888">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>
</font><div><div></div><div><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>
</div></div></blockquote></div><br>