From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: LKML <linux-kernel@vger.kernel.org>
Cc: bcm43xx-dev@lists.berlios.de
Subject: 2.6.17-rc1: bcm43xx problems with BCM4306 on x86_64
Date: Fri, 7 Apr 2006 18:59:23 +0200 [thread overview]
Message-ID: <200604071859.23452.rjw@sisk.pl> (raw)
Hi,
I've just tried the version of the driver included in 2.6.17-rc1 on an x86_64
box (Asus L5D) with a built-in PCI BCM4306 adapter (Broadcom Corporation
BCM4306 802.11b/g Wireless LAN Controller (rev 03)), and unfortunately
it doesn't seem to work.
The driver loads and seems to initialize the adapter, but that's all,
apparently.
First, I compiled the driver with DMA and PIO support, but it hanged my box
solid when I tried "iwconfig eth1 essid on" on it. On the next boot I noticed
it caused the following messages to appear in dmesg:
nommu_map_single: overflow 58ee7010+2404 of device mask 3fffffff
nommu_map_single: overflow 53669010+2404 of device mask 3fffffff
nommu_map_single: overflow 50180010+2404 of device mask 3fffffff
and so on, down to 455aa010. Then I thought the adapter might be unable
to DMA for some reason and compiled it with PIO support only. It did not
hang the box any more, but I couldn't make it work.
It causes the following messages to appear in dmesg:
bcm43xx: set security called
bcm43xx: .level = 0
bcm43xx: .enabled = 0
bcm43xx: .encrypt = 0
bcm43xx: PHY connected
bcm43xx: Radio turned on
bcm43xx: Chip initialized
bcm43xx: PIO initialized
bcm43xx: 80211 cores initialized
bcm43xx: Keys cleared
ADDRCONF(NETDEV_UP): eth1: link is not ready
bcm43xx: FATAL ERROR: BCM43xx_IRQ_XMIT_ERROR
bcm43xx: FATAL ERROR: BCM43xx_IRQ_XMIT_ERROR
bcm43xx: FATAL ERROR: BCM43xx_IRQ_XMIT_ERROR
bcm43xx: ASSERTION FAILED (0) at: drivers/net/wireless/bcm43xx/bcm43xx_pio.c:167:parse_cookie()
bcm43xx: ASSERTION FAILED (packetindex >= 0 && packetindex < BCM43xx_PIO_MAXTXPACKETS) at: drivers/net/wireless/bcm43xx/bcm43xx_
pio.c:170:parse_cookie()
bcm43xx: ASSERTION FAILED (queue) at: drivers/net/wireless/bcm43xx/bcm43xx_pio.c:482:bcm43xx_pio_handle_xmitstatus()
bcm43xx: FATAL ERROR: BCM43xx_IRQ_XMIT_ERROR
bcm43xx: FATAL ERROR: BCM43xx_IRQ_XMIT_ERROR
bcm43xx: FATAL ERROR: BCM43xx_IRQ_XMIT_ERROR
bcm43xx: ASSERTION FAILED (0) at: drivers/net/wireless/bcm43xx/bcm43xx_pio.c:167:parse_cookie()
bcm43xx: ASSERTION FAILED (packetindex >= 0 && packetindex < BCM43xx_PIO_MAXTXPACKETS) at: drivers/net/wireless/bcm43xx/bcm43xx_
pio.c:170:parse_cookie()
bcm43xx: ASSERTION FAILED (queue) at: drivers/net/wireless/bcm43xx/bcm43xx_pio.c:482:bcm43xx_pio_handle_xmitstatus()
and so on.
I used fwcutter 004 to extract the firmvare from the Windows file delivered
with the machine (BCMWL5.SYS).
If you need/want any more information from me, please let me know.
Greetings,
Rafael
next reply other threads:[~2006-04-07 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 16:59 Rafael J. Wysocki [this message]
[not found] ` <200604072105.53994.mb@bu3sch.de>
2006-04-07 21:08 ` 2.6.17-rc1: bcm43xx problems with BCM4306 on x86_64 Rafael J. Wysocki
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=200604071859.23452.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-kernel@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 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.