linux-kernel - Re: Some issues/regression when upgrading to 3.1-rc5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAOULuOax5OX-oZKBdEuBGVQaSX55sQY8tbKAPD-WFKEr7fRNtQ@mail.gmail.com>
Date:	Wed, 7 Sep 2011 07:58:41 -0400
From:	Parag Warudkar <parag.lkml@...il.com>
To:	Francis Moreau <francis.moro@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Some issues/regression when upgrading to 3.1-rc5

Hi

On Wed, Sep 7, 2011 at 2:51 AM, Francis Moreau <francis.moro@...il.com> wrote:
> Hello,
>
> On Wed, Sep 7, 2011 at 12:24 AM, Parag Warudkar <parag.lkml@...il.com> wrote:
>> On Tue, Sep 6, 2011 at 5:15 PM, Francis Moreau <francis.moro@...il.com> wrote:
>>>
>>> [   13.335961] cfg80211: Calling CRDA to update world regulatory domain
>>> [   13.386127] b43-phy0: Broadcom 4313 WLAN found (core revision 24)
>>> [   13.510112] bcma: PLL enable timeout
>>> [   13.510125] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 10, Type
>>> 8, Revision 1)
>>> [   13.510148] b43: probe of bcma0:0 failed with error -95
>>> [   13.510194] Broadcom 43xx driver loaded [ Features: PMNLS,
>>> Firmware-ID: FW13 ]

>
> unloading b43/bcma and loading brcmsmac doesn't help. Looks like the
> latter doesn't support my card anymore.
>
> From dmesg:
>
> [ 3828.183927] brcmsmac: module is from the staging directory, the
> quality is unknown, you have been warned.
>
> and that's it.

4313 is supported in brcmsmac - are you sure the firmware is at the
right place and getting loaded?
I recall for example having to deal with firmware in kernel specific
directory - /lib/`uname -r`/firmware for example which means you will
need to copy the firmware to new kernel specific directory.

Secondly try to make sure b43/bcma are blacklisted and never loaded at all.

Can't think of any other reason why it would suddenly stop working.

Hope this helps,

Parag
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/