From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Michael Buesch <mb@bu3sch.de>
Cc: bcm43xx-dev@lists.berlios.de, LKML <linux-kernel@vger.kernel.org>,
discuss@x86-64.org
Subject: Re: 2.6.17-rc1: bcm43xx problems with BCM4306 on x86_64
Date: Fri, 7 Apr 2006 23:08:37 +0200 [thread overview]
Message-ID: <200604072308.38233.rjw@sisk.pl> (raw)
In-Reply-To: <200604072105.53994.mb@bu3sch.de>
On Friday 07 April 2006 21:05, Michael Buesch wrote:
> On Friday 07 April 2006 18:59, Rafael J. Wysocki wrote:
> > 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
>
> You should probably report that to the x86_64 people.
I'll try -mm first and report if this still happens there.
> > 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.
>
> PIO does not work, yet. Give me some other few weeks, please.
Oops. Sorry for the noice then. ;-)
Greetings,
Rafael
prev parent reply other threads:[~2006-04-07 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 16:59 2.6.17-rc1: bcm43xx problems with BCM4306 on x86_64 Rafael J. Wysocki
[not found] ` <200604072105.53994.mb@bu3sch.de>
2006-04-07 21:08 ` 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=200604072308.38233.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
/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.