From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
bcm43xx devel <Bcm43xx-dev@lists.berlios.de>,
netdev <netdev@vger.kernel.org>
Subject: Re: bcm43xx from 2.6.20-rc1-mm1 on HPC nx6325 (x86_64)
Date: Sat, 23 Dec 2006 14:41:49 +0100 [thread overview]
Message-ID: <200612231441.49949.rjw@sisk.pl> (raw)
In-Reply-To: <458C1633.1040606@lwfinger.net>
Hi,
On Friday, 22 December 2006 18:30, Larry Finger wrote:
> I'm trying to make the bcm43xx driver out of the 2.6.20-rc1-mm1 kernel work on
> an HPC nx6325, with no luck, so far, although I'm using a firmware that has
> been reported to work with these boxes
> (http://gentoo-wiki.com/HARDWARE_Gentoo_on_HP_Compaq_nx6325#Onboard_Wireless_.28802.11.29).
>
> The driver loads and seems to operate the hardware to some extent, but there
> seems to be a problem with interrupts. Namely, the chip doesn't seem to
> generate any.
> Raphael J. Wysocki wrote:
>
> > Right after a fresh 'modprobe bcm43xx' I get the following messages in dmesg:
>
> > bcm43xx driver
> > ACPI: PCI Interrupt 0000:30:00.0[A] -> GSI 18 (level, low) -> IRQ 18
> > PCI: Setting latency timer of device 0000:30:00.0 to 64
> > bcm43xx: Chip ID 0x4311, rev 0x1
> > bcm43xx: Number of cores: 4
> > bcm43xx: Core 0: ID 0x800, rev 0x11, vendor 0x4243
> > bcm43xx: Core 1: ID 0x812, rev 0xa, vendor 0x4243
> > bcm43xx: Core 2: ID 0x817, rev 0x3, vendor 0x4243
> > bcm43xx: Core 3: ID 0x820, rev 0x1, vendor 0x4243
> > bcm43xx: PHY connected
> > bcm43xx: Detected PHY: Version: 4, Type 2, Revision 8
> > bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
> > bcm43xx: Radio turned off
> > bcm43xx: Radio turned off
> > PM: Adding info for No Bus:eth1
> > printk: 3 messages suppressed.
> > SoftMAC: ASSERTION FAILED (0) at: >
> net/ieee80211/softmac/ieee80211softmac_wx.c:306:ieee80211softmac_wx_get_rate()
> >
> > but, strangely enough, eth1 does not appear, but eth2 appears instead:
> >
>
> Usually the problem generates an oops, but I think your problem is due to the changes in the work
> struct in 2.6.20-rc1. There is a fix in the pipeline, but it has not propagated through the system.
>
> You should apply the work_struct2 patch attached. If your computer has a switch to kill the RF, you
> may also wish to apply the radio_hwenable patch, which should cause the radio LED to be turned on.
>
> The selection of eth2 rather than eth1 is probably due to the rules in
> /etc/udev/rules.d/30-net_persistent_names.rules.
Ah, I'll check that, thanks. It used to be eth1, though, and I haven't changed
the udev configuration myself.
> When I boot a softmac version, my bcm43xx device is
> wlan0, but when I boot the d80211 version, it is eth1. I have a second bcm43xx card, which becomes
> eth2 under softmac.
Thanks for the patch. In the meantime I've browsed the bcm43xx-dev archives
and found some other interesting patches for me to try. ;-)
Greetings,
Rafael
--
If you don't have the time to read,
you don't have the time or the tools to write.
- Stephen King
prev parent reply other threads:[~2006-12-23 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-22 17:30 bcm43xx from 2.6.20-rc1-mm1 on HPC nx6325 (x86_64) Larry Finger
2006-12-23 13:41 ` Rafael J. Wysocki [this message]
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=200612231441.49949.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).