From: "Arend van Spriel" <arend@broadcom.com>
To: "Brent Roman" <brent@mbari.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: After Kernel 3.3, brcmsmac won't work on mid-2010 Mac Mini
Date: Wed, 9 May 2012 09:25:35 +0200 [thread overview]
Message-ID: <4FAA1BEF.10704@broadcom.com> (raw)
In-Reply-To: <4FA9A8FE.5000102@mbari.org>
On 05/09/2012 01:15 AM, Brent Roman wrote:
> Hi,
>
> When I updated to Linux Kernel 3.3.5 on my mid-2010 Aluminum Unibody Mac
> Mini,
> its built-in wireless was no longer recognized:
>
> 03:00.0 Network controller [0280]: Broadcom Corporation BCM43224
> 802.11a/b/g/n [14e4:4353] (rev 01)
> Subsystem: Apple Computer Inc. Device [106b:0093]
> Flags: bus master, fast devsel, latency 0, IRQ 22
> Memory at d3300000 (64-bit, non-prefetchable) [size=16K]
> Capabilities: [40] Power Management version 3
> Capabilities: [58] Vendor Specific Information: Len=78 <?>
> Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
> Capabilities: [d0] Express Endpoint, MSI 00
> Capabilities: [100] Advanced Error Reporting
> Capabilities: [13c] Virtual Channel
> Capabilities: [160] Device Serial Number 54-70-4b-ff-ff-0c-60-33
> Capabilities: [16c] Power Budgeting <?>
> Kernel driver in use: brcmsmac
>
> I tried kernel 3.3.0 with the same negative result.
> When I reverted to 3.2.16, the chip was immediately recognized.
> The driver in 3.3+ is loading the bcma module.
>
> I've fine with running 3.2.16 for now.
> Is this a known problem? A configuration error on my part?
>
> Just let me know if you'd like me to try anything to help debug this
> (possible) regression.
>
Any log on 3.3 kernel may help. Do you have bcma blacklisted in your
system? Do you have built the kernel yourself? Can you sent the .config
for both kernels?
Gr. AvS
next prev parent reply other threads:[~2012-05-09 7:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 23:15 After Kernel 3.3, brcmsmac won't work on mid-2010 Mac Mini Brent Roman
2012-05-09 7:25 ` Arend van Spriel [this message]
2012-05-10 0:38 ` Brent Roman
2012-05-10 11:01 ` Arend van Spriel
2012-05-10 18:10 ` Brent Roman
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=4FAA1BEF.10704@broadcom.com \
--to=arend@broadcom.com \
--cc=brent@mbari.org \
--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).