2013-09-11 20:49:35

by Jan-Oliver Kaiser

[permalink] [raw]
Subject: brcmfmac, BCM43241

Hi,

I am trying to get a BCM43241 card running on a 3.11-amd64 kernel.
[1] lists the device as supported but gives no instructions on how to
install it. I managed to extract the firmware from the git binary patch
contained in [2].

I copied the firmware to /lib/firmware/brcm/brcmfmac-sdio.bin and copied
the content of /dev/nvram to /lib/firmware/brcm/brcmfmac-sdio.txt.

Previously, `dmesg` would list error that indicated missing files.
Currently, the output is as follows:

[12865.299503] brcmfmac: brcmf_sdio_chip_drivestrengthinit: No SDIO
Drive strength init done for chip 4324 rev 5 pmurev 17
[12866.393551] brcmfmac: brcmf_sdbrcm_htclk: HT Avail timeout (1000000):
clkctl 0x50
[12867.402386] brcmfmac: brcmf_sdbrcm_htclk: HT Avail timeout (1000000):
clkctl 0x50
[12867.409143] brcmfmac: brcmf_proto_cdc_query_dcmd: brcmf_proto_cdc_msg
failed w/status -5
[12867.409149] brcmfmac: brcmf_fil_cmd_data: Failed err=-5
[12867.409153] brcmfmac: brcmf_c_preinit_dcmds: Retreiving cur_etheraddr
failed, -5
[12867.409157] brcmfmac: brcmf_bus_start: failed: -5
[12867.409167] brcmfmac: brcmf_sdbrcm_probe: dongle is not responding
[12868.416890] brcmfmac: brcmf_sdbrcm_htclk: HT Avail timeout (1000000):
clkctl 0x50
[12869.426308] brcmfmac: brcmf_sdbrcm_htclk: HT Avail timeout (1000000):
clkctl 0x50

I have not been able to find anything to help with debugging this.

There was some discussion in response to [2] that I don't understand. Is
there something wrong with the firmware itself?

I would be very grateful for any help. I can provide all additional
information if something is missing from this report. (I can also be
reached via IRC, 'Eruquen' on freenode)

Thanks in advance,
Jan-Oliver

[1] http://wireless.kernel.org/en/users/Drivers/brcm80211
[2] http://www.spinics.net/lists/linux-wireless/msg107754.html


2013-09-13 17:41:29

by Jan-Oliver Kaiser

[permalink] [raw]
Subject: Re: brcmfmac, BCM43241

Hi Franky,

The nvram file is attached to this mail. I am using aptosid, based on
Debian unstable.

Best regards,
Jan-Oliver


On 09/13/2013 07:16 PM, Franky Lin wrote:
> On 09/11/2013 01:35 PM, Jan-Oliver Kaiser wrote:
>> I copied the firmware to /lib/firmware/brcm/brcmfmac-sdio.bin and copied
>> the content of /dev/nvram to /lib/firmware/brcm/brcmfmac-sdio.txt.
> Hi Jan-Oliver,
>
> Could you share me the nvram file you retrieve through /dev/nvram? Which
> distro are you using?
>
> Thanks,
> Franky
>


Attachments:
nvram (114.00 B)

2013-09-12 00:18:58

by Franky Lin

[permalink] [raw]
Subject: Re: brcmfmac, BCM43241

Hi Jan-Oliver,

I think the problem is from the firmware since the 43241 used here is
quite different from the one we published firmware for. We are preparing
a new firmware and will release it soon.

Regards,
Franky

On 09/11/2013 04:39 PM, Jan-Oliver Kaiser wrote:
> Hi Franky,
>
> Thank you for your response. I'll attach the full dmesg output. The
> device is a Sony Vaio Duo 13 laptop (SVD1321C5E).
>
> The dmesg part I posted in the first mail is (as far as I can tell) the
> only part related to the built-in wireless adapter. I have another
> wireless adapter attached via USB, which is responsible for earlier
> output related to wireless stuff.
>
> The dmesg entries about brcmfmac are triggered simply by `modprobe
> brmcfmac`.
>
> Best regards,
> Jan-Oliver
>
> P.S.:
> I read somewhere that the wireless adapter and the touchscreen, which is
> also not working, are both connected via an Intel GPIO Controller but I
> can't seem to find the source. I don't know what that means or if it is
> true. Maybe somebody here can make use of this information.
>
>
> On 09/12/2013 12:41 AM, Franky Lin wrote:
>> Hi Jan-Oliver,
>>
>> Could you please send us the full log? Also please share more details
>> about the hardware platform you are using. We need to figure out how to
>> get the nvram file.
>>
>> Regards,
>> Franky
>>
>> On 09/11/2013 01:35 PM, Jan-Oliver Kaiser wrote:
>>> Hi,
>>>
>>> I am trying to get a BCM43241 card running on a 3.11-amd64 kernel.
>>> [1] lists the device as supported but gives no instructions on how to
>>> install it. I managed to extract the firmware from the git binary patch
>>> contained in [2].
>>>
>>> I copied the firmware to /lib/firmware/brcm/brcmfmac-sdio.bin and copied
>>> the content of /dev/nvram to /lib/firmware/brcm/brcmfmac-sdio.txt.
>>>
>>> Previously, `dmesg` would list error that indicated missing files.
>>> Currently, the output is as follows:
>>>
>>> [12865.299503] brcmfmac: brcmf_sdio_chip_drivestrengthinit: No SDIO
>>> Drive strength init done for chip 4324 rev 5 pmurev 17
>>> [12866.393551] brcmfmac: brcmf_sdbrcm_htclk: HT Avail timeout (1000000):
>>> clkctl 0x50
>>> [12867.402386] brcmfmac: brcmf_sdbrcm_htclk: HT Avail timeout (1000000):
>>> clkctl 0x50
>>> [12867.409143] brcmfmac: brcmf_proto_cdc_query_dcmd: brcmf_proto_cdc_msg
>>> failed w/status -5
>>> [12867.409149] brcmfmac: brcmf_fil_cmd_data: Failed err=-5
>>> [12867.409153] brcmfmac: brcmf_c_preinit_dcmds: Retreiving cur_etheraddr
>>> failed, -5
>>> [12867.409157] brcmfmac: brcmf_bus_start: failed: -5
>>> [12867.409167] brcmfmac: brcmf_sdbrcm_probe: dongle is not responding
>>> [12868.416890] brcmfmac: brcmf_sdbrcm_htclk: HT Avail timeout (1000000):
>>> clkctl 0x50
>>> [12869.426308] brcmfmac: brcmf_sdbrcm_htclk: HT Avail timeout (1000000):
>>> clkctl 0x50
>>>
>>> I have not been able to find anything to help with debugging this.
>>>
>>> There was some discussion in response to [2] that I don't understand. Is
>>> there something wrong with the firmware itself?
>>>
>>> I would be very grateful for any help. I can provide all additional
>>> information if something is missing from this report. (I can also be
>>> reached via IRC, 'Eruquen' on freenode)
>>>
>>> Thanks in advance,
>>> Jan-Oliver
>>>
>>> [1] http://wireless.kernel.org/en/users/Drivers/brcm80211
>>> [2] http://www.spinics.net/lists/linux-wireless/msg107754.html
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe
>>> linux-wireless" in
>>> the body of a message to [email protected]
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>



2013-09-13 17:16:31

by Franky Lin

[permalink] [raw]
Subject: Re: brcmfmac, BCM43241

On 09/11/2013 01:35 PM, Jan-Oliver Kaiser wrote:
> I copied the firmware to /lib/firmware/brcm/brcmfmac-sdio.bin and copied
> the content of /dev/nvram to /lib/firmware/brcm/brcmfmac-sdio.txt.
Hi Jan-Oliver,

Could you share me the nvram file you retrieve through /dev/nvram? Which
distro are you using?

Thanks,
Franky


2013-09-11 22:41:44

by Franky Lin

[permalink] [raw]
Subject: Re: brcmfmac, BCM43241

Hi Jan-Oliver,

Could you please send us the full log? Also please share more details
about the hardware platform you are using. We need to figure out how to
get the nvram file.

Regards,
Franky

On 09/11/2013 01:35 PM, Jan-Oliver Kaiser wrote:
> Hi,
>
> I am trying to get a BCM43241 card running on a 3.11-amd64 kernel.
> [1] lists the device as supported but gives no instructions on how to
> install it. I managed to extract the firmware from the git binary patch
> contained in [2].
>
> I copied the firmware to /lib/firmware/brcm/brcmfmac-sdio.bin and copied
> the content of /dev/nvram to /lib/firmware/brcm/brcmfmac-sdio.txt.
>
> Previously, `dmesg` would list error that indicated missing files.
> Currently, the output is as follows:
>
> [12865.299503] brcmfmac: brcmf_sdio_chip_drivestrengthinit: No SDIO
> Drive strength init done for chip 4324 rev 5 pmurev 17
> [12866.393551] brcmfmac: brcmf_sdbrcm_htclk: HT Avail timeout (1000000):
> clkctl 0x50
> [12867.402386] brcmfmac: brcmf_sdbrcm_htclk: HT Avail timeout (1000000):
> clkctl 0x50
> [12867.409143] brcmfmac: brcmf_proto_cdc_query_dcmd: brcmf_proto_cdc_msg
> failed w/status -5
> [12867.409149] brcmfmac: brcmf_fil_cmd_data: Failed err=-5
> [12867.409153] brcmfmac: brcmf_c_preinit_dcmds: Retreiving cur_etheraddr
> failed, -5
> [12867.409157] brcmfmac: brcmf_bus_start: failed: -5
> [12867.409167] brcmfmac: brcmf_sdbrcm_probe: dongle is not responding
> [12868.416890] brcmfmac: brcmf_sdbrcm_htclk: HT Avail timeout (1000000):
> clkctl 0x50
> [12869.426308] brcmfmac: brcmf_sdbrcm_htclk: HT Avail timeout (1000000):
> clkctl 0x50
>
> I have not been able to find anything to help with debugging this.
>
> There was some discussion in response to [2] that I don't understand. Is
> there something wrong with the firmware itself?
>
> I would be very grateful for any help. I can provide all additional
> information if something is missing from this report. (I can also be
> reached via IRC, 'Eruquen' on freenode)
>
> Thanks in advance,
> Jan-Oliver
>
> [1] http://wireless.kernel.org/en/users/Drivers/brcm80211
> [2] http://www.spinics.net/lists/linux-wireless/msg107754.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>



2013-09-11 23:50:33

by Jan-Oliver Kaiser

[permalink] [raw]
Subject: Re: brcmfmac, BCM43241

Hi Franky,

Thank you for your response. I'll attach the full dmesg output. The
device is a Sony Vaio Duo 13 laptop (SVD1321C5E).

The dmesg part I posted in the first mail is (as far as I can tell) the
only part related to the built-in wireless adapter. I have another
wireless adapter attached via USB, which is responsible for earlier
output related to wireless stuff.

The dmesg entries about brcmfmac are triggered simply by `modprobe
brmcfmac`.

Best regards,
Jan-Oliver

P.S.:
I read somewhere that the wireless adapter and the touchscreen, which is
also not working, are both connected via an Intel GPIO Controller but I
can't seem to find the source. I don't know what that means or if it is
true. Maybe somebody here can make use of this information.


On 09/12/2013 12:41 AM, Franky Lin wrote:
> Hi Jan-Oliver,
>
> Could you please send us the full log? Also please share more details
> about the hardware platform you are using. We need to figure out how to
> get the nvram file.
>
> Regards,
> Franky
>
> On 09/11/2013 01:35 PM, Jan-Oliver Kaiser wrote:
>> Hi,
>>
>> I am trying to get a BCM43241 card running on a 3.11-amd64 kernel.
>> [1] lists the device as supported but gives no instructions on how to
>> install it. I managed to extract the firmware from the git binary patch
>> contained in [2].
>>
>> I copied the firmware to /lib/firmware/brcm/brcmfmac-sdio.bin and copied
>> the content of /dev/nvram to /lib/firmware/brcm/brcmfmac-sdio.txt.
>>
>> Previously, `dmesg` would list error that indicated missing files.
>> Currently, the output is as follows:
>>
>> [12865.299503] brcmfmac: brcmf_sdio_chip_drivestrengthinit: No SDIO
>> Drive strength init done for chip 4324 rev 5 pmurev 17
>> [12866.393551] brcmfmac: brcmf_sdbrcm_htclk: HT Avail timeout (1000000):
>> clkctl 0x50
>> [12867.402386] brcmfmac: brcmf_sdbrcm_htclk: HT Avail timeout (1000000):
>> clkctl 0x50
>> [12867.409143] brcmfmac: brcmf_proto_cdc_query_dcmd: brcmf_proto_cdc_msg
>> failed w/status -5
>> [12867.409149] brcmfmac: brcmf_fil_cmd_data: Failed err=-5
>> [12867.409153] brcmfmac: brcmf_c_preinit_dcmds: Retreiving cur_etheraddr
>> failed, -5
>> [12867.409157] brcmfmac: brcmf_bus_start: failed: -5
>> [12867.409167] brcmfmac: brcmf_sdbrcm_probe: dongle is not responding
>> [12868.416890] brcmfmac: brcmf_sdbrcm_htclk: HT Avail timeout (1000000):
>> clkctl 0x50
>> [12869.426308] brcmfmac: brcmf_sdbrcm_htclk: HT Avail timeout (1000000):
>> clkctl 0x50
>>
>> I have not been able to find anything to help with debugging this.
>>
>> There was some discussion in response to [2] that I don't understand. Is
>> there something wrong with the firmware itself?
>>
>> I would be very grateful for any help. I can provide all additional
>> information if something is missing from this report. (I can also be
>> reached via IRC, 'Eruquen' on freenode)
>>
>> Thanks in advance,
>> Jan-Oliver
>>
>> [1] http://wireless.kernel.org/en/users/Drivers/brcm80211
>> [2] http://www.spinics.net/lists/linux-wireless/msg107754.html
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-wireless" in
>> the body of a message to [email protected]
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
>


Attachments:
dmesg.log (64.87 kB)