From: Sebastien Bourdeauducq <sb@m-labs.hk>
To: Arend van Spriel <arend@broadcom.com>
Cc: brcm80211 development <brcm80211-dev-list@broadcom.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Simon Raffeiner (SCC)" <simon.raffeiner@kit.edu>
Subject: Re: brcmfmac43241b4-sdio / Thinkpad Tablet 10 issues
Date: Fri, 20 Feb 2015 11:12:09 -0700 [thread overview]
Message-ID: <54E778F9.1000500@m-labs.hk> (raw)
In-Reply-To: <54E31CD5.70901@broadcom.com>
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
next prev parent reply other threads:[~2015-02-20 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54E2E1CD.5020203@m-labs.hk>
2015-02-17 10:49 ` brcmfmac43241b4-sdio / Thinkpad Tablet 10 issues Arend van Spriel
2015-02-20 18:12 ` Sebastien Bourdeauducq [this message]
2015-02-25 12:23 ` Jocky Wilson
2015-02-25 19:54 ` Arend van Spriel
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=54E778F9.1000500@m-labs.hk \
--to=sb@m-labs.hk \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=simon.raffeiner@kit.edu \
/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).