Re: wpa supplicant/ipw3945, ESSID last char missing

["Alessandro Suardi" <alessandro.suardi@gmail.com>]

On 10/3/06, Dan Williams <dcbw@redhat.com> wrote:
> On Tue, 2006-10-03 at 00:08 +0200, Alessandro Suardi wrote:
> > On 10/2/06, Theodore Tso <tytso@mit.edu> wrote:
> > > On Mon, Oct 02, 2006 at 05:00:31PM -0400, Dan Williams wrote:
> > > > Distributions _are_ shipping those tools already.  The problem is more
> > > > with older distributions where, for example, the kernel gets upgraded
> > > > but other stuff does not.  If a kernel upgrade happens, then the distro
> > > > needs to make sure userspace works with it.  That's nothing new.
> > >
> > > Um, *which* distro's are shipping it already?  RHEL4?  SLES10?  I
> > > thought we saw a note saying that even Debian **unstable** didn't have
> > > a new enough version of the wireless-tools....
> >
> > That was my point initially. FC5-latest is apparently carrying
> >  tools which are "too old"... and I yum update twice or thrice
> >  a week. Not that *I* minded building packages from source,
> >  but this is likely a bit too much for a good slice of the userbase.
>
> And that's my fault.  I was made aware of this issue last week and am
> currently testing out the newer wireless-tools with the intention of
> pushing them to FC5-updates.  Had I actually been tracking the
> wireless-tools release cycle more closely, I would have pushed the
> wireless-tools-28 final version when it came out.
>
> But, as far as I know (please correct me if I'm wrong), that 2.6.18
> doesn't actually include WE-21! [1]  Somebody is trying to run
> out-of-kernel ipw3945 drivers using a 2.6.18 kernel from FC5 that's
> WE-20 only, but the driver uses WE-21?
>
> ipw3945 isn't in the upstream kernel, and Fedora certainly isn't going
> to go out of its way to make sure every piece of software under the sun
> that's not included in the distro works with it [2].  Distros try to
> make sure they are internally consistent, not globally consistent.  If
> somebody uses out-of-kernel drivers, they take that responsibility.  The
> solution to the problem is to make sure that ipw3945 gets in the kernel
> as quickly as possible, something I think we'd all like to have happen.
>
> Dan
>
> [1] /lib/modules/2.6.18-1.2708.fc6/build/include/linux/wireless.h
> defines WIRELESS_EXT = 20
>
> [2] Yeah it would be nice; but go out of the way to have Skype w/ OSS,
> Nvidia binary drivers, ATI binary drivers, ndiswrapper,
> out-of-kernel-drivers?  No.

While strongly agreeing with the above reasoning, I'd just
point out that the two current reports were

mine -> FC5, in-kernel ipw2200, wpa_supplicant and wireless-tools "too old",
  rebuild userspace from recent sources => all fine and dandy

Norbert's -> Debian unstable, out-of-kernel ipw3945, wpa_supplicant okay,
  wireless-tools "too old", rebuild these from recent sources =>
still a few issues

so it was only myself running FC5, and with a WE-21 capable Torvalds kernel
as I test at least 4 -git snapshots per week (and yes, 2.6.18 doesn't
have WE-21,
which is the root of the reports - WE-21 went in in 2.6.18-git9).


Indeed the in-kernel driver appeared to be the easily solved case, as
expected...

Thanks, ciao,

--alessandro

"Well a man has two reasons for things that he does
 the first one is pride and the second one is love
 all understandings must come by this way"

    (Husker Du, 'She Floated Away')
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/