mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Miles Lane" <miles.lane@gmail.com>,
	Bcm43xx-dev@lists.berlios.de, Michael Buesch <mb@bu3sch.de>,
	"John W. Linville" <linville@tuxdriver.com>
Cc: "Andrew Morton" <akpm@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Larry.Finger@lwfinger.net
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	[thread overview]
Message-ID: <200611152116.30734.rjw@sisk.pl> (raw)
In-Reply-To: <a44ae5cd0611141521pd342109jaae9e27aca3d2200@mail.gmail.com>

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

  reply	other threads:[~2006-11-15 20:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14 23:21 Miles Lane
2006-11-15 20:16 ` Rafael J. Wysocki [this message]
2006-11-16  2:16   ` Larry Finger
2006-11-16  2:26     ` John W. Linville
2006-11-16  5:45     ` Miles Lane
2006-11-16  3:04   ` Miles Lane

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200611152116.30734.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=Bcm43xx-dev@lists.berlios.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    --cc=miles.lane@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome