Return-path: Received: from mga02.intel.com ([134.134.136.20]:21440 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750751AbYDRWfW convert rfc822-to-8bit (ORCPT ); Fri, 18 Apr 2008 18:35:22 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: RE: iwl3945 problem with 2.6.25-rc9 Date: Fri, 18 Apr 2008 15:35:21 -0700 Message-ID: (sfid-20080418_233527_245462_09B925D8) In-Reply-To: <20080418232358.000fbdf7@peterson.fenrir.org.uk> References: <1208376292.27708.3.camel@localhost.localdomain><1208555842.4848.56.camel@johannes.berg> <20080418232358.000fbdf7@peterson.fenrir.org.uk> From: "Chatre, Reinette" To: "Brian Morrison" , Sender: linux-wireless-owner@vger.kernel.org List-ID: On , Brian Morrison wrote: > Not wishing to muddy the waters, but I've found that the iwlwifi > driver with a 3945 card is only reliable for scanning and associating > for > my laptop (x86_64) with disable_hw_scan=1 set, this is with > 2.4.24.4-64.fc8 kernel. Driver version is 1.2.26. I agree that your problem is related (no scanning results from driver), but it does seem to be different from what we are trying to debug here. In this case the user is not receiving scanning results when using sw scanning while the driver should have been using hw scanning because the user is not using that driver parameter as you are. Reinette