From: "Rafał Miłecki" <zajec5@gmail.com>
To: b43-dev@lists.infradead.org
Subject: Problems with b43 wirelesss
Date: Sat, 19 Jun 2010 11:33:39 +0200 [thread overview]
Message-ID: <AANLkTimvdtruvFaugHTYcSNhL5pBZXPYtzEF3qolO_qW@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimIkTaIrdXHulE6YVnB3ZwWrMBCNnCK1SKdyctL@mail.gmail.com>
2010/6/18 Magnus Therning <magnus@therning.org>:
> I've just bought a new laptop, and it has a broadcom wireless device.
> I was, foolishly it seems, hoping that all serious problems with
> broadcom devices had been dealt with already and that there wouldn't
> be any problems to get acceptable connectivity nowadays. ?Alas that
> isn't the case, despite the excellent job the devs on this mailing
> list are doing.
>
> The behaviour I see is that I manage to associate with the wireless
> router, but soon after I start using the connection it dies and all
> attempts to re-connect fails. ?I've seen a few similar reports from
> b43 users but without any really good work-around (some say that
> switching down to 802.11b works (and that would be acceptable) but I
> don't see any way of doing that).
>
> So, the current situation is that this laptop without wireless working
> is nearly useless, so I'll do anything in my power to get this
> working. ?My experience in writing drivers is nearly non-existant, and
> my knowledge of wireless devices is zero, so I'm not sure I'd be very
> good at actually figuring out what changes to the code are necessary.
> However, I'll be happy to help out with testing any and all patches
> that are sent my way. ?Just let me know how I can help!
>
> Here's some info about the system I have:
>
> # uname -a
> Linux ohann 2.6.33-ARCH #1 SMP PREEMPT Thu May 13 11:32:37 CEST 2010
> x86_64 Intel(R) Core(TM) i5 CPU M 430 @ 2.27GHz GenuineIntel GNU/Linux
> # lspci -vnn | grep 14e4
> 03:00.0 Network controller [0280]: Broadcom Corporation BCM4312
> 802.11b/g [14e4:4315] (rev 01)
>
> I'm currently running the b43 driver out of compat-wireless
> (2010-06-17 downloaded from
> http://wireless.kernel.org/download/compat-wireless-2.6/, I understand
> this is the latest daily snapshot of the bleeding edge version).
>
> I've attached the output of 'lspci -vvn|grep 43 -A7' and 'dmesg'
>
> Please let me know what else I can do to help out with getting this fixed.
You can Google for b43 & DMA errors. Simply try "pio" option for b43
module. Or switch to newer kernel, which will pick up pio for you
after first DMA error.
--
Rafa?
next prev parent reply other threads:[~2010-06-19 9:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 21:51 Problems with b43 wirelesss Magnus Therning
2010-06-19 9:33 ` Rafał Miłecki [this message]
2010-06-19 12:35 ` Magnus Therning
2010-06-19 13:26 ` Larry Finger
2010-06-20 16:57 ` Magnus Therning
2010-06-20 0:59 ` William Bourque
2010-06-20 17:02 ` Magnus Therning
2010-06-20 18:18 ` Gábor Stefanik
2010-06-20 18:31 ` Magnus Therning
2010-06-20 18:37 ` Gábor Stefanik
2010-06-24 22:27 ` Magnus Therning
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=AANLkTimvdtruvFaugHTYcSNhL5pBZXPYtzEF3qolO_qW@mail.gmail.com \
--to=zajec5@gmail.com \
--cc=b43-dev@lists.infradead.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).