Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030653AbWKOUT1 (ORCPT ); Wed, 15 Nov 2006 15:19:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030709AbWKOUT1 (ORCPT ); Wed, 15 Nov 2006 15:19:27 -0500 Received: from ogre.sisk.pl ([217.79.144.158]:21126 "EHLO ogre.sisk.pl") by vger.kernel.org with ESMTP id S1030653AbWKOUT0 (ORCPT ); Wed, 15 Nov 2006 15:19:26 -0500 From: "Rafael J. Wysocki" To: "Miles Lane" , Bcm43xx-dev@lists.berlios.de, Michael Buesch , "John W. Linville" Subject: Re: 2.6.19-rc5-mm2 -- bcm43xx busted (backing out the bcm43xx patches fixes it) Date: Wed, 15 Nov 2006 21:16:30 +0100 User-Agent: KMail/1.9.1 Cc: "Andrew Morton" , LKML , Larry.Finger@lwfinger.net References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611152116.30734.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2688 Lines: 70 On Wednesday, 15 November 2006 00:21, Miles Lane wrote: > Hello, > > The last three MM kernels have fail to give me a working bcm43xx driver. > The odd thing is that dmesg output seems to indicate that the driver > is working okay. NetworkManager doesn't see the driver, though. > "iwlist scan" fails to find any access points, too. iwconfig shows > "Access Point: invalid". I can confirm the symptoms, I see them too on my test boxes. > I tried backing out the following patches, and it fixes the problem: > > drivers/net/wireless/bcm43xx/bcm43xx.h > drivers/net/wireless/bcm43xx/bcm43xx_main.c > drivers/net/wireless/bcm43xx/bcm43xx_power.c > drivers/net/wireless/bcm43xx/bcm43xx_wx.c > > drivers/net/wireless/bcm43xx/bcm43xx_xmit.c You list the files in which there are offending changes. Could you please list the patches you have reverted? > After backing out the patches, dmesg shows: > > bcm43xx driver > bcm43xx: Chip ID 0x4306, rev 0x3 > bcm43xx: Number of cores: 5 > bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243, enabled > bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled > bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243, enabled > bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243, disabled > bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243, enabled > bcm43xx: PHY connected > bcm43xx: Detected PHY: Version: 2, Type 2, Revision 2 > bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) > bcm43xx: Radio turned off > bcm43xx: Radio turned off > bcm43xx: PHY connected > bcm43xx: Microcode rev 0x127, pl 0xe (2005-04-18 02:36:27) > bcm43xx: Radio turned on > bcm43xx: Chip initialized > bcm43xx: 30-bit DMA initialized > bcm43xx: Keys cleared > bcm43xx: Selected 802.11 core (phytype 2) > > Also, iwconfig shows: > eth2 IEEE 802.11b/g ESSID:"loftywifi" Nickname:"Broadcom 4306" > Mode:Managed Frequency=2.412 GHz Access Point: 00:06:25:54:A2:0C > Bit Rate=11 Mb/s Tx-Power=19 dBm > RTS thr:off Fragment thr:off > Encryption key:23F8-49CF-201A-4334-1210-7C3E-0A Security mode:open > Link Quality=76/100 Signal level=-53 dBm Noise level=-72 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > Thanks, > Miles Greetings, Rafael -- You never change things by fighting the existing reality. R. Buckminster Fuller - 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/