From: Dan Williams <dcbw@redhat.com>
To: Howard Chu <hyc@highlandsun.com>
Cc: Dave <kilroyd@googlemail.com>, linux-wireless@vger.kernel.org
Subject: Re: orinoco_cs and WPA-EAP?
Date: Fri, 15 May 2009 21:35:03 -0400 [thread overview]
Message-ID: <1242437703.10933.55.camel@localhost.localdomain> (raw)
In-Reply-To: <4A0E0579.70507@highlandsun.com>
On Fri, 2009-05-15 at 17:14 -0700, Howard Chu wrote:
> Dan Williams wrote:
> > On Fri, 2009-05-15 at 21:42 +0100, Dave wrote:
> >> That message is printed in response to a firmware interrupt. It
> >> indicates "an unsolicited Frame Structure cannot be generated... because
> >> there is not enough Frame Structure buffer space available".
> >>
> >> I suspect that the beacons/probe responses/scan results are either too
> >> large/too frequent for the card to handle, or the firmware can't
> >> decipher them.
> >>
> >> Before enabling wpa_supplicant, can you try scan for your AP (as root):
> >>
> >> iwlist ethX scan essid YYYYY
>
> That works fine. In fact, just "iwlist scan" returns the same result - only
> the info for my AP is returned. (There are at least 6 APs visible from an
> another laptop sitting nearby.)
>
> >> I'm interested in what it returns, and whether dmesg reports 'Ext scan
> >> results too large' or something similar.
>
> No, it just continues with the stream of "frame lost" messages:
>
> eth2: Information frame lost. (10 times, followed by 1
> __ratelimit: 2 callbacks suppressed (then 10 more frame lost messages, and so on)
>
> The number in "callbacks suppressed" varies pretty widely, from 2 to 32.
>
> > Yeah a lot of APs will stuff a ton of info into the IEs these days,
> > including WPS, WPA, 11d, blah blah. It's not out of the question that
> > the firmware writers didn't anticipate or handle large numbers of IEs in
> > the beacons. That said, what firmware version is he using? Maybe
>
> Using 9.48, I so far haven't found 9.52 for download anywhere.
9.52 AFAIK is only available from Apple Airport drivers if you cut it
out of the .kext on a PPC Mac.
Dan
prev parent reply other threads:[~2009-05-16 1:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-10 4:41 CTX714 to a good home Howard Chu
2009-05-15 9:48 ` orinoco_cs and WPA-EAP? Howard Chu
2009-05-15 18:12 ` Dave
2009-05-15 19:38 ` Howard Chu
2009-05-15 20:42 ` Dave
2009-05-15 23:12 ` Dan Williams
2009-05-16 0:14 ` Howard Chu
2009-05-10 6:19 ` Dave
2009-05-16 1:35 ` Dan Williams [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1242437703.10933.55.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=hyc@highlandsun.com \
--cc=kilroyd@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).