From: "John W. Linville" <linville@tuxdriver.com>
To: "René Bolldorf" <xsecute@googlemail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: [BUG] No SPROM available!
Date: Mon, 29 Mar 2010 15:47:46 -0400 [thread overview]
Message-ID: <20100329194745.GH4984@tuxdriver.com> (raw)
In-Reply-To: <4BB10110.9090202@googlemail.com>
On Mon, Mar 29, 2010 at 09:35:44PM +0200, René Bolldorf wrote:
> On 03/29/10 21:20, Larry Finger wrote:
>> Ren�,
>>
>> When you have a wireless problem, please post it to
>> linux-wireless@vger.kernel.org. The Linux Kernel Mailing List may or may not be
>> appropriate.
>>
>> To help in diagnosing your problem, please apply this patch and post the output
>> line that it produces. On my system, it shows
>>
>> ssb: chip_id 0x4312, status 0x10
>>
> and on my: ssb: chip_id 0x4312, status 0x12
>> Please also post the output of 'lspci -nnv | grep 14e4'.
> Yep:
> 01:00.0 Network controller [0280]: Broadcom Corporation BCM4312
> 802.11b/g [14e4:4315] (rev 01)
OK, I'm new to the thread -- what exactly is the issue? Was your
device working previously?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-03-29 20:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 19:20 [BUG] No SPROM available! Larry Finger
2010-03-29 19:35 ` René Bolldorf
2010-03-29 19:47 ` John W. Linville [this message]
2010-03-29 20:04 ` John W. Linville
2010-03-29 20:14 ` Larry Finger
2010-03-29 20:48 ` John W. Linville
2010-03-29 20:55 ` John W. Linville
2010-03-29 21:28 ` Larry Finger
2010-03-29 21:53 ` René Bolldorf
2010-03-29 23:01 ` Larry Finger
2010-03-29 23:21 ` René Bolldorf
2010-03-29 23:43 ` Larry Finger
2010-03-29 23:45 ` René Bolldorf
2010-03-29 20:19 ` René Bolldorf
2010-03-29 20:30 ` John W. Linville
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=20100329194745.GH4984@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=xsecute@googlemail.com \
/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).