Your message dated Sun, 2 May 2021 13:26:04 +0200 with message-id <yi6mtdil2ne+f...@eldamar.lan> and subject line Re: Bug#908438: Still there on 5.4.19-1~bpo10+1 (Was: Bug#908438: cubietruck wifi reversion) has caused the Debian Bug report #908438, regarding cubietruck wifi reversion 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.) -- 908438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: linux Version: 4.17.17-1 Severity: normal On a cubietruck board, the linux-image-4.17.0-3-armmp-lpae kernel kernel fails to enable the builtin wifi: Sep 09 17:52:52 honeybee kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43362-sdio for chip BCM43362/1 Sep 09 17:52:52 honeybee kernel: usbcore: registered new interface driver brcmfmac Sep 09 17:52:52 honeybee kernel: brcmfmac mmc1:0001:1: firmware: direct-loading firmware brcm/brcmfmac43362-sdio.bin Sep 09 17:52:52 honeybee kernel: brcmfmac mmc1:0001:1: firmware: direct-loading firmware brcm/brcmfmac43362-sdio.txt Sep 09 17:52:55 honeybee kernel: brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout Sep 09 17:52:55 honeybee kernel: brcmfmac: brcmf_bus_started: failed: -110 Sep 09 17:52:55 honeybee kernel: brcmfmac: brcmf_attach: dongle is not responding: err=-110 Sep 09 17:52:55 honeybee kernel: brcmfmac: brcmf_sdio_firmware_callback: brcmf_attach failed This was working using linux-image-4.14.0-3-armmp-lpae and earlier kernels including stable's, so seems to be a reversion. I have firmware-brcm80211 installed. I tried downgrading it to the same version I was using with the older kernel (20170823-1), but that did not help, so I don't think it's a problem with the firmware. Here it is working with the older kernel, for comparison: Sep 09 18:06:10 honeybee kernel: brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43362-sdio.bin for chip 0x00a962(43362) rev 0x000001 Sep 09 18:06:10 honeybee kernel: usbcore: registered new interface driver brcmfmac Sep 09 18:06:10 honeybee kernel: brcmfmac mmc1:0001:1: firmware: direct-loading firmware brcm/brcmfmac43362-sdio.bin Sep 09 18:06:10 honeybee kernel: brcmfmac mmc1:0001:1: firmware: direct-loading firmware brcm/brcmfmac43362-sdio.txt Sep 09 18:06:10 honeybee kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Apr 22 2013 14:50:00 version 5.90.195.89.6 FWID 01-b30a427d -- see shy jo
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---Source: linux Source-Version: 5.5.13-1 Hi, On Tue, Apr 21, 2020 at 02:14:54PM +0200, Jakob Haufe wrote: > On Sat, 21 Dec 2019 23:04:30 +0100 Salvatore Bonaccorso <car...@debian.org> > wrote: > > > > Helmut was reporting to see the issue on buster, but we would need > > confirmation that the issue is seen still at least on 5.4.6 or ideally > > as well on 5.5-rc2. > > As stated in the subject: This is still an issue on 5.4.19-1~bpo10+1. > Patching the DT as mentioned earlier makes Wifi work. Looking through the upstream commit it looks that the issue finally got fixed with 8c8e60fb86a9 ("brcmfmac: sdio: Fix OOB interrupt initialization on brcm43362") in 5.6-rc1, 5.5.6 and 5.4.22. Regards, Salvatore
--- End Message ---
