From: "Eddy Petrișor" <eddy.petrisor@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: weird issues with b43 - and an oops
Date: Tue, 12 Feb 2008 01:09:49 +0200 [thread overview]
Message-ID: <47B0D5BD.5040109@gmail.com> (raw)
In-Reply-To: <200802111520.36105.mb@bu3sch.de>
Michael Buesch wrote:
> On Monday 11 February 2008 12:08:43 Eddy Petri=C8=99or wrote:
>> Feb 11 03:32:12 bounty kernel: b43-phy0 ERROR: Microcode not respond=
ing
>> Feb 11 03:32:12 bounty kernel: b43-phy0 ERROR: You must go to=20
>> http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and=20
>> download the correct firmware (version 4).
>=20
> Do this.
Already did, as noted in the initial mail, thanks.
>> Feb 11 03:32:12 bounty dhclient: wmaster0: unknown hardware address =
type 801
>> Feb 11 03:32:12 bounty kernel: input: b43-phy0 as /class/input/input=
17
>> Feb 11 03:32:12 bounty kernel: WARNING: at drivers/ssb/main.c:883=20
>> ssb_tmslow_reject_bitmask()
>=20
> And use the b43 driver from wireless-2.6
I assume I must use the 'everything' branch, right?
/me is still waiting for 'clone' to finish
(I hope this kernel doesn't have suspend-to-ram and suspend-to-disk=20
issues, I just got them back with 2.6.24)
--=20
Regards,
EddyP
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
"Imagination is more important than knowledge" A.Einstein
-
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-02-11 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 11:08 weird issues with b43 - and an oops Eddy Petrișor
2008-02-11 14:20 ` Michael Buesch
2008-02-11 23:09 ` Eddy Petrișor [this message]
2008-02-12 7:19 ` Eddy Petrișor
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=47B0D5BD.5040109@gmail.com \
--to=eddy.petrisor@gmail.com \
--cc=linux-wireless@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).