From: Christian Schaefer <schaefer@rostlab.org>
To: b43-dev@lists.infradead.org
Subject: New device in MacBook Pro, yet unsupported?
Date: Mon, 28 Mar 2011 14:29:35 +0200 [thread overview]
Message-ID: <4D907F2F.4020801@rostlab.org> (raw)
In-Reply-To: <AANLkTinkbFTQ+PHL=T7=ghiC3L6PgrdrhXeDpZw4JZyC@mail.gmail.com>
On 03/28/2011 01:42 PM, Rafa? Mi?ecki wrote:
>>> modprobe b43
>>> dmesg | grep b43
>>> dmesg | grep ssb
>> returns nothing. The modprobe however produces the following:
> Try brcm80211
This doesn't seem to be very fruitful either:
brcm80211: module is from the staging directory, the quality is unknown,
you have been warned.
btw, uname -r gives:
2.6.38-7-generic
Perhaps support for the device is included in recent development kernels?
Thanks,
Chris
--
Dipl.-Bioinf. Christian Schaefer
Technical University Munich
Department for Bioinformatics / Rostlab
http://www.rostlab.org/~schaefer
http://gsish.tum.edu/
next prev parent reply other threads:[~2011-03-28 12:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 9:23 New device in MacBook Pro, yet unsupported? Christian Schäfer
2011-03-27 9:42 ` Rafał Miłecki
2011-03-27 9:43 ` Rafał Miłecki
2011-03-28 9:06 ` Christian Schaefer
2011-03-28 11:42 ` Rafał Miłecki
2011-03-28 12:29 ` Christian Schaefer [this message]
2011-03-27 10:12 ` Jonas Gorski
2011-03-30 18:20 ` Rafał Miłecki
2011-04-05 23:54 ` Rafał Miłecki
2011-04-07 10:09 ` Christian Schaefer
2011-04-07 10:32 ` Rafał Miłecki
2011-04-08 19:17 ` Rafał Miłecki
2011-04-10 9:16 ` Andy Botting
2011-04-10 9:20 ` Rafał Miłecki
2011-06-10 22:23 ` David Woodhouse
2011-06-10 22:35 ` Rafał Miłecki
2011-06-11 9:36 ` Rafał Miłecki
2011-06-11 10:09 ` David Woodhouse
2011-06-12 15:40 ` Darren
-- strict thread matches above, loose matches on Subject: below --
2011-04-07 18:45 Andy Botting
2011-04-07 18:51 ` Rafał Miłecki
[not found] <BANLkTinooer0aFqJfn0ui+QXpLO6YkPhEg@mail.gmail.com>
2011-04-16 4:37 ` Darren
2011-04-16 13:41 ` 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=4D907F2F.4020801@rostlab.org \
--to=schaefer@rostlab.org \
--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).