linux-kernel - Re: 2.6.19-rc5-mm2 -- bcm43xx busted (backing out the bcm43xx patches fixes it)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 15 Nov 2006 21:16:30 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	"Miles Lane" <miles.lane@...il.com>, Bcm43xx-dev@...ts.berlios.de,
	Michael Buesch <mb@...sch.de>,
	"John W. Linville" <linville@...driver.com>
Cc:	"Andrew Morton" <akpm@...l.org>,
	LKML <linux-kernel@...r.kernel.org>, Larry.Finger@...inger.net
Subject: Re: 2.6.19-rc5-mm2 -- bcm43xx busted (backing out the bcm43xx patches fixes it)

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/