+ lists
On 02/17/15 07:38, Sebastien Bourdeauducq wrote:
> Hi,
>
> have you been able to try out the driver on a brcm43241b4-sdio chip with
> the same revision as mine and reproduce the "HT avail timeout" bug? Just
> let me know if you would like me to test anything on my machine.
I received the vaio duo 13 laptop last friday. Unfortunately, it says:
chip 4324 rev 5 pmurev 17
So it is a one-off and not showing the issue you are seeing. Your issue
seems to be due to failing firmware so you may need b5 firmware. I will
look into this.
Thanks,
Arend
On Tuesday, February 17, 2015 03:49 AM, Arend van Spriel wrote:
> So it is a one-off and not showing the issue you are seeing. Your issue
> seems to be due to failing firmware so you may need b5 firmware.
Making some progress :)
I have extracted the firmwares from the Lenovo Windows driver, which
contains:
43241b4rtecdc.bin 4324b5rtecdc.bin 4330b2rtecdc.bin 43341b0rtecdc.bin
I have used 4324b5rtecdc.bin in place of brcmfmac43241b4-sdio.bin in
/lib/firmware. This time it goes further, and I can scan for networks,
associate (only tried without encryption so far), and transmit packets
(which are correctly received by another device in monitor mode).
However, the MAC address reported by ifconfig does not match the one in
brcmfmac43241b4-sdio.txt, and the brcmfmac device fails to correctly
receive packets.
The RX packets fall in three categories:
1) dropped at a lower level
2) reported as "dropped" by ifconfig
3) received but corrupted, shown with ethertype 0x886c and containing
the string "wl0" which I guess is related to the firmware and should not
be there.
I guess that the driver has bugs with decoding some of the data sent by
the card.
I'm sending you privately a log with debug=0x1416 (association + DHCP)
and a pcap trace showing packets of category 3.
Sebastien