From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752558AbZBNSq3 (ORCPT ); Sat, 14 Feb 2009 13:46:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751269AbZBNSqT (ORCPT ); Sat, 14 Feb 2009 13:46:19 -0500 Received: from wa-out-1112.google.com ([209.85.146.179]:20835 "EHLO wa-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751079AbZBNSqS (ORCPT ); Sat, 14 Feb 2009 13:46:18 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Na2CtOYYvlVmudzpBOkwzuQFriSvfBlLw9U7lmPYqcrjvVPrSwcC/dp4MIh2pUJvfX vzP4JJPtVKioOXygsWyyE2M0r/j71xwZTxylWOBFrGMuHWKHjfOpkD4C4nVyOekEfu6j Gtpi2oXTnbiE+ZflIfI6zSjcFBwWgNk72DoKk= MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 15 Feb 2009 02:46:16 +0800 Message-ID: Subject: Re: [Bug #12414] iwl4965 cannot use "ap auto" on latest 2.6.28/29? From: Jeff Chua To: "Rafael J. Wysocki" Cc: Linux Kernel Mailing List , Kernel Testers List , reinette.chatre@intel.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Feb 14, 2009 at 7:41 PM, Jeff Chua wrote: > On Wed, Feb 4, 2009 at 6:23 PM, Rafael J. Wysocki wrote: >> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12414 >> Subject : iwl4965 cannot use "ap auto" on latest 2.6.28/29? >> Submitter : Jeff Chua >> Date : 2009-01-05 4:13 (31 days old) >> References : http://marc.info/?l=linux-kernel&m=123112882127823&w=4 > > I applied the patch > http://marc.info/?l=linux-wireless&m=123320213115108&w=2 and it seems > better now. One instant of not association out of 20 tries, but > reloading the modules seems to make it work again. So, let's just > close the case? I tested on another AP (WAG200G ), and this one, it's failing to associate more often. And I noticed that when it does associate, I don't get these two lines ... iwlagn: TX Power requested while scanning! iwlagn: Error sending TX power (-11) Here's a good run ... iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks iwlagn: Copyright(c) 2003-2008 Intel Corporation iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 iwlagn 0000:03:00.0: setting latency timer to 64 iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4 iwlagn: Tunable channels: 11 802.11bg, 13 802.11a channels wmaster0 (iwlagn): not using net_device_ops yet phy0: Selected rate control algorithm 'iwl-agn-rs' wlan0 (iwlagn): not using net_device_ops yet iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 iwlagn 0000:03:00.0: irq 28 for MSI/MSI-X iwlagn 0000:03:00.0: firmware: requesting iwlwifi-4965-2.ucode iwlagn loaded firmware version 228.57.2.23 Registered led device: iwl-phy0:radio Registered led device: iwl-phy0:assoc Registered led device: iwl-phy0:RX Registered led device: iwl-phy0:TX wlan0: authenticate with AP xxxxxxxxxxxxx wlan0: authenticate with AP xxxxxxxxxxxxx wlan0: authenticate with AP xxxxxxxxxxxxx wlan0: authenticated wlan0: associate with AP xxxxxxxxxxxx wlan0: RX AssocResp from xxxxxxxxxxxx (capab=0x471 status=0 aid=1) wlan0: associated Thanks, Jeff.