From: Pavel Roskin <proski@gnu.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Broadcom card totally not visible for system (lspci)
Date: Tue, 30 Mar 2010 15:41:19 -0400 [thread overview]
Message-ID: <1269978079.4938.21.camel@mj> (raw)
In-Reply-To: <b170af451003301206p593cbe3ew582823c75dc06f11@mail.gmail.com>
On Tue, 2010-03-30 at 21:06 +0200, Rafa? Mi?ecki wrote:
> You mean dmesg, don't you?
Yes.
> I've attached it, but it was stopped by b43
> ML. You can see dmesg on marc archive for linux-wireless:
> http://marc.info/?l=linux-wireless&m=126996817625998&w=2
>
> Unfortunately I don't have dmesg from some more-debugging kernel.
Indeed, there is no list of SSB devices. The current kernels will
output that list even if CONFIG_SSB_DEBUG is disabled, but older kernels
required CONFIG_SSB_DEBUG for that.
Installing compat-wireless should help. Also, ask the user to run
"modprobe b43". It might just work.
--
Regards,
Pavel Roskin
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Roskin <proski@gnu.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: Broadcom card totally not visible for system (lspci)
Date: Tue, 30 Mar 2010 15:41:19 -0400 [thread overview]
Message-ID: <1269978079.4938.21.camel@mj> (raw)
In-Reply-To: <b170af451003301206p593cbe3ew582823c75dc06f11@mail.gmail.com>
On Tue, 2010-03-30 at 21:06 +0200, Rafał Miłecki wrote:
> You mean dmesg, don't you?
Yes.
> I've attached it, but it was stopped by b43
> ML. You can see dmesg on marc archive for linux-wireless:
> http://marc.info/?l=linux-wireless&m=126996817625998&w=2
>
> Unfortunately I don't have dmesg from some more-debugging kernel.
Indeed, there is no list of SSB devices. The current kernels will
output that list even if CONFIG_SSB_DEBUG is disabled, but older kernels
required CONFIG_SSB_DEBUG for that.
Installing compat-wireless should help. Also, ask the user to run
"modprobe b43". It might just work.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-03-30 19:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 16:56 Broadcom card totally not visible for system (lspci) Rafał Miłecki
2010-03-30 16:56 ` Rafał Miłecki
2010-03-30 17:19 ` Larry Finger
2010-03-30 17:19 ` Larry Finger
2010-03-30 17:31 ` Rafał Miłecki
2010-03-30 17:31 ` Rafał Miłecki
2010-03-30 17:48 ` Larry Finger
2010-03-30 17:48 ` Larry Finger
2010-03-30 19:02 ` Pavel Roskin
2010-03-30 19:02 ` Pavel Roskin
2010-03-30 19:06 ` Rafał Miłecki
2010-03-30 19:06 ` Rafał Miłecki
2010-03-30 19:41 ` Pavel Roskin [this message]
2010-03-30 19:41 ` Pavel Roskin
2010-03-30 19:29 ` Johannes Berg
2010-03-30 19:29 ` Johannes Berg
2010-03-31 6:39 ` Holger Schurig
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=1269978079.4938.21.camel@mj \
--to=proski@gnu.org \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.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 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.