Return-path: Received: from cliff.cs.toronto.edu ([128.100.3.120]:35176 "EHLO cliff.cs.toronto.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751568Ab0BDWKw (ORCPT ); Thu, 4 Feb 2010 17:10:52 -0500 To: Dan Williams cc: Stanislaw Gruszka , linux-wireless@vger.kernel.org, stable@kernel.org, "John W. Linville" , Chris Siebenmann Subject: Re: [PATCH] airo: fix setting zero length WEP key In-reply-to: dcbw's message of Thu, 04 Feb 2010 13:44:55 -0800. <1265319895.4290.4.camel@localhost.localdomain> Date: Thu, 04 Feb 2010 17:10:49 -0500 From: Chris Siebenmann Message-Id: <20100204221049.717A72B0054@apps0.cs.toronto.edu> Sender: linux-wireless-owner@vger.kernel.org List-ID: | > That mentioned commit broke wireless on a Thinkpad T42 (running Fedora | > 11); from that commit onwards, the wireless system appeared to see no | > networks. The patch makes things work again. | > | > More details are in the Fedora bugzilla: | > https://bugzilla.redhat.com/show_bug.cgi?id=522530 | | You mean with iwlist? That's quite odd because setting WEP keys | doesn't have anything to do with the scanning stuff, even in the | firmware. Note that Airo has always been somewhat tempermental for | scans and you may or may not see any or all APs in any given scan. All I know is that the failure is total; in all situations I've tried where a good kernel sees one or more networks and APs, a bad kernel sees none at all (and 'iwlist wifi0 scanning' reports 'No scan results'). A good kernel sometimes reports different numbers of networks and sometimes has quality problems, but a bad kernel never sees anything. (Well, has never seen anything within a relatively modest amount of time. I have not let it sit for, say, an hour in order to see if something magically gets better; I have always rebooted into a kernel with working wireless.) - cks