Your message dated Wed, 21 Oct 2015 04:39:30 +0100
with message-id <1445398770.10397.50.ca...@decadent.org.uk>
and subject line Re: Bug#797779: brcmfmac4330-sdio.txt from OpenElec fixes the 
issue
has caused the Debian Bug report #797779,
regarding firmware-brcm80211: failed to load brcm/brcmfmac4330-sdio.txt
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 ow...@bugs.debian.org
immediately.)


-- 
797779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-brcm80211
Version: 0.43
Severity: normal


Dear Maintainer,

I installed linux-image-4.2.0-trunk-armmp on a cubox-i with an imx.6 CPU.

For the first time the wireless interface should be supported by a stock kernel.

Installing the Debian package results in the error in the modprobe of the 
brcmfmac_sdio during boot and there is no wireless module visible:

rd@home:~$ dmesg |grep brcm
[    2.092789] brcm_reg: disabling
[    6.744194] usbcore: registered new interface driver brcmfmac
[    6.798042] brcmfmac_sdio mmc0:0001:1: firmware: direct-loading firmware 
brcm/brcmfmac4330-sdio.bin
[    6.816911] brcmfmac_sdio mmc0:0001:1: firmware: failed to load 
brcm/brcmfmac4330-sdio.txt (-2)
[    6.847619] brcmfmac_sdio mmc0:0001:1: Direct firmware load for 
brcm/brcmfmac4330-sdio.txt failed with error -2
[    6.847627] brcmfmac_sdio mmc0:0001:1: Falling back to user helper
[    7.876909] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 
0x50
[    8.888865] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 
0x50
rd@home:~$ /sbin/ifconfig -a
eth1      Link encap:Ethernet  Hardware Adresse d0:63:b4:00:2b:ac  
          inet Adresse:192.168.178.29  Bcast:192.168.178.255  
Maske:255.255.255.0
          inet6-Adresse: fd00::d263:b4ff:fe00:2bac/64 Gültigkeitsbereich:Global
          inet6-Adresse: fe80::d263:b4ff:fe00:2bac/64 
Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX packets:1561 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1222 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000 
          RX bytes:246316 (240.5 KiB)  TX bytes:1150073 (1.0 MiB)

lo        Link encap:Lokale Schleife  
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:65536  Metrik:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0 
          RX bytes:2718 (2.6 KiB)  TX bytes:2718 (2.6 KiB)

rd@home:~$ 



-- System Information:
Debian Release: 8.1
  APT prefers stable
  APT policy: (500, 'stable'), (400, 'testing'), (300, 'unstable'), (250, 
'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.2.0-trunk-armmp (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

firmware-brcm80211 depends on no packages.

firmware-brcm80211 recommends no packages.

Versions of packages firmware-brcm80211 suggests:
ii  initramfs-tools  0.120

-- no debconf information

--- End Message ---
--- Begin Message ---
On Wed, 2 Sep 2015 23:10:42 +0200 Stefan Lippers-Hollmann <s....@gmx.de> wrote:
[...]
> > On Wednesday 02 September 2015 19:37:13 Stefan Lippers-Hollmann wrote:
> > > On 2015-09-02, Rainer Dorsch wrote:
> [...]
> > Are you saying that I opened the bugreport against the wrong package or 
> > that 
> > this is not a bug at all?
> 
> As far as I see it, this is not a /software/ bug and not actionable 
> from within Debian, the data blob in question can only be provided
> by the OEM/ systems integrator manufacturing the devboard or the 
> vendor producing the wlan card in question (e.g. AMPAK for the AP6120
> wlan/ BT daughterboard using the Broadcom BCM4329 SDIO chipset found 
> on many armhf devboards). It is calibration data for your particular 
> wlan card and not a generic firmware image. 
[...]

Exactly.  These board-specific blobs have not been submitted to linux-
firmware.git and are also unsuitable for inclusion in firmware-nonfree.

Ben.

-- 
Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---

Reply via email to