Bug#821400: firmware-brcm80211: brcmfmac_sdio wants brcm/brcmfmac43340-sdio .bin and .txt, only .bin supplied

[Daniel Kahn Gillmor]

Package: firmware-brcm80211
Version: 20160110-1
Severity: normal

On an Asus X205T, dmesg says:

brcmfmac_sdio mmc1:0001:1: firmware: direct-loading firmware brcm/brcmfmac43340-sdio.bin
brcmfmac_sdio mmc1:0001:1: firmware: failed to load brcm/brcmfmac43340-sdio.txt (-2)
brcmfmac_sdio mmc1:0001:1: firmware: Direct firmware load for brcm/brcmfmac43340-sdio.txt failed with error -2
brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50

and no network interface appears for the device.

It looks to me like the brcmfmac_sdio kernel module is expecting this
.txt file is supposed to be shipped alongside the .bin, but it isn't
present.

--dkg


-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing'), (200, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

[Ben Hutchings]

Control: tag -1 wontfix

Post by Daniel Kahn Gillmor
Package: firmware-brcm80211
Version: 20160110-1
Severity: normal
brcmfmac_sdio mmc1:0001:1: firmware: direct-loading firmware brcm/brcmfmac43340-sdio.bin
brcmfmac_sdio mmc1:0001:1: firmware: failed to load brcm/brcmfmac43340-sdio.txt (-2)
brcmfmac_sdio mmc1:0001:1: firmware: Direct firmware load for brcm/brcmfmac43340-sdio.txt failed with error -2
brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
and no network interface appears for the device.
It looks to me like the brcmfmac_sdio kernel module is expecting this
.txt file is supposed to be shipped alongside the .bin, but it isn't
present.

That's board-specific configuration, not really firmware.  I don't know
where you're supposed to get it from.

Ben.

[Daniel Kahn Gillmor]

Version: 20160110-1

Thanks for the quick response, Ben.

Post by Daniel Kahn Gillmor
It looks to me like the brcmfmac_sdio kernel module is expecting this
.txt file is supposed to be shipped alongside the .bin, but it isn't
present.

That's board-specific configuration, not really firmware.  I don't know
where you're supposed to get it from.

hm, https://wiki.debian.org/InstallingDebianOn/Asus/X205TA#WiFi
suggests:

cp /sys/firmware/efi/efivars/nvram-74b00bd9-805a-4d61-b51f-43268123d113 /lib/firmware/brcm/brcmfmac43340-sdio.txt

and indeed, after doing that, and then removing and re-loading the
kernel module with:

modprobe -v -r brcmfmac
modprobe -v brcmfmac

then the device is found correctly.

--dkg

[Ben Hutchings]

Post by Daniel Kahn Gillmor
Version: 20160110-1
Thanks for the quick response, Ben.

Post by Ben Hutchings

Post by Daniel Kahn Gillmor
It looks to me like the brcmfmac_sdio kernel module is expecting this
.txt file is supposed to be shipped alongside the .bin, but it isn't
present.

That's board-specific configuration, not really firmware.  I don't know
where you're supposed to get it from.

hm, https://wiki.debian.org/InstallingDebianOn/Asus/X205TA#WiFi
   cp /sys/firmware/efi/efivars/nvram-74b00bd9-805a-4d61-b51f-43268123d113 /lib/firmware/brcm/brcmfmac43340-sdio.txt
and indeed, after doing that, and then removing and re-loading the
 modprobe -v -r brcmfmac
 modprobe -v brcmfmac
then the device is found correctly.

Ah, I dimly remembered that this information could be stashed in the
system firmware somewhere.  It seems like the driver ought to look
there first if EFI support is enabled (there is an in-kernel API for
reading EFI variables).  That will have to be developed upstream
though.

Ben.

[Daniel Kahn Gillmor]

Post by Ben Hutchings
Ah, I dimly remembered that this information could be stashed in the
system firmware somewhere.  It seems like the driver ought to look
there first if EFI support is enabled (there is an in-kernel API for
reading EFI variables).  That will have to be developed upstream
though.

Agreed that this would make sense as an upstream change. I'm asking
about it over on #linux-wireless on freenode, to see if i can interest
any uptsream developers.

regards,

--dkg

[Debian Bug Tracking System]

This post might be inappropriate. Click to display it.

[Debian Bug Tracking System]

Your message dated Mon, 18 Apr 2016 14:57:57 -0400
with message-id <***@alice.fifthhorseman.net>
and subject line Re: Bug#821400: firmware-brcm80211: brcmfmac_sdio wants brcm/brcmfmac43340-sdio .bin and .txt, only .bin supplied
has caused the Debian Bug report #821400,
regarding firmware-brcm80211: brcmfmac_sdio wants brcm/brcmfmac43340-sdio .bin and .txt, only .bin supplied
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)