Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
Anyone besides Jonas seen this problem?
Since so many different wireless cards work fine w/ the soekris, linux 2.4.28,
NL5354+ Aries 2 as master, I really want to blame the windows w/ atheros driver
and NL5354+ card.
I know what stuck beacon is now, and it's not that problem.
I will keep searching for different drivers for windows -- I've tried
3 or 4 different ones w/ no solution.
It's unfortunate windows users will suffer these issues.
One other note -- it seems if the soekris AP already has 1 or 2 non-NL5354+
windows clients associated with it (such as a linux NL5354+ client (madwifi)
or a prism based client on windows or linux), it helps the windows/NL5354+
card get out of it's bad state, get associated, and lease an address.
Kind of desparate for a solution, next step is to try the new HAL madwifi
code recently checked in and if that or something else doesn't solve it,
we'll have to ditch any atheros based cards on windows that have this
problem and replace them w/ intel, prism, etc. cards. I'd prefer not to
do that if possible.
copying the devel list in hopes of reaching a wider audience.
> Hi all-
> I've got a soekris board w/ Senao NL5354+ aries2 card (atheros 5213 chip)
> with madwifi driver that is current w/ the exception of the recent HAL
> changes just committed. It acts as an AP (master 54M auto channel 1) and
> most things can connect to it no problem (linux madwifi Senao card,
> linksys prism card, intel cards, etc running windows or linux in managed
> However -- Windows XP w/ a Senao NL5354+ aries2 w/ the stock driver from
> Senao or even the latest Atheros driver gets in a state where it can transmit
> frames, but not receive them. It stresses the DHCP server doing discovers
> w/ offers going out, but windows doesn't get the offers so it's just discover
> and offers every second or two.
> "iwlist ath1 peers" on the AP soekris shows the client appearing once in a
> while w/ varying signal level near the noise (-95). I have to run iwlist
> ath1 peers over and over quickly to "catch" the client listed w/ the
> weak signal.
> With the senao driver, it seems to talk 108M / 54M and keeps flip-flopping
> during this condition.
> Sometimes after several minutes of this behaviour, the windows client will
> finally get "in sync" w/ the soekris AP and leases an address and all is well
> it will work great until windows is restarted and the same problem occurs.
> Is this the stuck beacon problem or something else? I don't know how to
> recognize the stuck beacon problem -- a lot of people talk about it, but
> I haven't found a description of what it is / how to check for it.
> I think it's an issue w/ the windows driver since winXP w/ the NL5354 aries2
> is the only of many different clients that we've tried that has this type
> of issue.
> Any ideas?
> When I get some time I'll try it w/ the new HAL code that was just committed.
> Thanks for any info,
> -Eric Malkowski