All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Bordug <vitb@kernel.crashing.org>
To: "John W. Linville" <linville@redhat.com>
Cc: bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: b43: regression on bcm4318
Date: Sat, 13 Oct 2007 12:17:30 +0400	[thread overview]
Message-ID: <20071013121730.1eef0d93@kernel.crashing.org> (raw)

Hello John et al,
(previous email had a typo in ML addr, sorry for the extra noise)

Both b43 and b43legacy fail to load on bcm4318 for a while now, while it used to work (with known issues) more or less
fine. The issue started happening not long before ssb united the support of b44 as well. Therefor, I noticed the difference
soon, because I am not able to use ndiswrapper instead anymore (it does not like ssb, and my NIC, b44, does not like
ssb missing either).

dmesg looks like the below:

b43-phy1: Broadcom 4318 WLAN found
b43-phy1 debug: Found PHY: Analog 3, Type 2, Revision 7
b43-phy1 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8
phy1: Failed to select rate control algorithm
phy1: Failed to initialize rate control algorithm
b43: probe of ssb0:0 failed with error -2

Currently this is latest rawhide kernel, but has been happening for awhile
(since, at least, 2.6.22.5, where ssb was not yet merged and I still able to use ndiswrapper.

Any hint to debug/investigate it appreciated. It does not look like hw malfunction, since ndiswrapper,
when able to load, still works fine.

-- 
Sincerely, Vitaly

             reply	other threads:[~2007-10-13  8:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-13  8:17 Vitaly Bordug [this message]
2007-10-13  8:24 ` b43: regression on bcm4318 Michael Buesch
2007-10-13 14:14   ` Vitaly Bordug
2007-10-13 15:22     ` Michael Buesch
2007-10-14  9:48     ` Johannes Berg

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=20071013121730.1eef0d93@kernel.crashing.org \
    --to=vitb@kernel.crashing.org \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.