From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: My test for bcm4213
Date: Sat, 17 Jul 2010 14:14:33 -0500 [thread overview]
Message-ID: <4C420119.4090109@lwfinger.net> (raw)
In-Reply-To: <AANLkTinodxB2RDKnHoHlzSDvC2xbL-J78z0O8TX59JDb@mail.gmail.com>
On 07/14/2010 08:15 AM, Kevyn-Alexandre Par? wrote:
> Hi,
>
> Here my test for bcm4213
>
> vostro at vostro:~$ lspci -n | grep 14e4
> 06:00.0 0280: 14e4:4315 (rev 01)
>
> vostro at vostro:~$ uname -a
> Linux vostro 2.6.35-rc3-wl+ #1 SMP Sat Jul 3 20:37:05 EDT 2010 x86_64 GNU/Linux
>
> On top ubuntu 10.04
>
> After booting error happen and I fallow instruction, see DMESG-WIRELESS
Please post the error messages in-line. It is a real pain to have to create a
file to see the errors. If you cannot do that, then name the attached file
xxxx.txt. That way I can see it inline.
> didn't work with sudo apt-get install b43-fwcutter // it was downloading
> on 12 that was failling... didn't investigate more..
>
> wget http://bu3sch.de/b43/fwcutter/b43-fwcutter-013.tar.bz2
> tar xjvf b43-fwcutter-013.tar.bz2
> cd b43-fwcutter-013/
> make
> cd ..
>
> export FIRMWARE_INSTALL_DIR="/lib/firmware"
> wget http://downloads.openwrt.org/sources/broadcom-wl-4.178.10.4.tar.bz2
> tar xjf broadcom-wl-4.178.10.4.tar.bz2
> cd broadcom-wl-4.178.10.4/
> sudo ../b43-fwcutter-013/b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" wl_apsta.o
>
> see DMESG file attach for log.
>
> next step try it with last 2.6.35-rc4 or later...
It will not help. For all the others reading this list, the error message is the
old, familiar
b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000, 0x00000000, 0x00000000,
0x00000000, 0x00000000
b43-phy0 ERROR: This device does not support DMA on your system. It will now be
switched to PIO.
b43-phy0: Controller RESET (DMA error) ...
If you had done any searching at all, you would have seen this error discussed
many, many times. We do not yet have a fix. If you load b43 with the options
"pio=1 qos=0 nohwcrypt=1" b43 will then work. No I do not know how to input
those options on your system.
Larry
next prev parent reply other threads:[~2010-07-17 19:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinHyR4ho_Ti6xB1dggpOBX1uJ_hZn7WXX_mgWlc@mail.gmail.com>
2010-07-14 13:15 ` My test for bcm4213 Kevyn-Alexandre Paré
2010-07-17 19:14 ` Larry Finger [this message]
2010-07-18 0:22 ` Rafał Miłecki
2010-07-18 2:09 ` Kevyn-Alexandre Paré
2010-07-18 3:00 ` Larry Finger
2010-08-11 12:41 ` Kevyn-Alexandre Paré
2010-07-17 19:15 ` Rafał Miłecki
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=4C420119.4090109@lwfinger.net \
--to=larry.finger@lwfinger.net \
--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 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.