linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Dave <kilroyd@googlemail.com>
Cc: Howard Chu <hyc@highlandsun.com>, linux-wireless@vger.kernel.org
Subject: Re: orinoco_cs and WPA-EAP?
Date: Fri, 15 May 2009 19:12:50 -0400	[thread overview]
Message-ID: <1242429170.10933.30.camel@localhost.localdomain> (raw)
In-Reply-To: <4A0DD39D.6070001@gmail.com>

On Fri, 2009-05-15 at 21:42 +0100, Dave wrote:
> Howard Chu wrote:
> > Dave wrote:
> >> Howard Chu wrote:
> >>> Sigh, nothing's ever easy. After abandoning the CTX714 I mentioned in an
> >>> earlier email, I find that the Thinkpad T42 I got from eBay came with some
> >>> kind of Orinoco 802.11B mini-PCI card installed. Ubuntu Jaunty's 2.6.28 kernel
> >>> loads up the orinoco_cs driver for this card. It appears that this driver only
> >>> supports WPA-PSK, and I use WPA-EAP on my home wlan. Has anyone done any work
> >>> on supporting WPA-EAP for this card?
> >>
> >> Note that the card only supports TKIP, so it won't work if the AP
> >> doesn't offer it.
> > 
> > Thanks, that may have been the issue I was facing at first. My AP was 
> > configured for CCMP. I've now set it to TKIP and seem to be getting further. 
> > But now when I start wpa_supplicant I see a stream of "Information frame lost" 
> > messages in dmesg that pretty much never end (interspersed once in a while 
> > with ratelimit messages). I wonder if this laptop's mini-PCI slot is hosed or 
> > something.
> 
> 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
> 
> I'm interested in what it returns, and whether dmesg reports 'Ext scan
> results too large' or something similar.

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
Apple's firmware fixes that or something?  Would be interesting if the
reporter could boot up an old iBook with an Airport card and see if that
works.

Dan



  reply	other threads:[~2009-05-15 23:12 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 [this message]
2009-05-16  0:14           ` Howard Chu
2009-05-10  6:19             ` Dave
2009-05-16  1:35             ` Dan Williams

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=1242429170.10933.30.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).