Page 1 of 1

Wifi and Debian Stretch

Posted: Thu Jul 06, 2017 11:27 am
by polymorphism
Hello everybody,

I'm working with a Debian Stretch :)
And I think I have an issue with the Wifi.

It seem that the firmware have a problem :

Code: Select all

 $ dmesg | grep brcm
[    3.821078] usbcore: registered new interface driver brcmfmac
[    3.841684] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.txt failed with error -2
[    4.896124] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[    5.906271] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
And when I can't obtain a wlan0 device :

Code: Select all

$ sudo wpa_supplicant -Dnl80211 -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf
Successfully initialized wpa_supplicant
Could not read interface wlan0 flags: No such device
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Could not read interface wlan0 flags: No such device
wlan0: Failed to initialize driver interface
Thanks for your help.

Re: Wifi and Debian Stretch

Posted: Thu Jul 06, 2017 8:56 pm
by hommar
Please, read stretch release notes
2.2.8. New method for naming network interfaces
The installer and newly installed systems will use a new standard naming scheme for network interfaces instead of eth0, eth1, etc. The old naming method suffered from enumeration race conditions that made it possible for interface names to change unexpectedly and is incompatible with mounting the root filesystem read-only. The new enumeration method relies on more sources of information, to produce a more repeatable outcome. It uses the firmware/BIOS provided index numbers and then tries PCI card slot numbers, producing names like ens0 or enp1s1 (ethernet) or wlp3s0 (wlan). USB devices, which can be added to the system at any time, will have names based upon their ethernet MAC addresses.

Re: Wifi and Debian Stretch

Posted: Fri Jul 07, 2017 12:12 am
by polymorphism
Ok, but on my Stretch I have always :

Code: Select all

$ sudo ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
...  
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
and when I change the name wlan0 by the new name, the result is identical :

Code: Select all

$ sudo wpa_supplicant -Dnl80211 -iwlp3s0 -c /etc/wpa_supplicant/wpa_supplicant.conf
Successfully initialized wpa_supplicant
Could not read interface wlp3s0 flags: No such device
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
Could not read interface wlp3s0 flags: No such device
wlp3s0: Failed to initialize driver interface

Re: Wifi and Debian Stretch

Posted: Fri Jul 07, 2017 1:20 am
by asandford
You're on your own until an official version of Raspbian Stretch is released.

Re: Wifi and Debian Stretch

Posted: Fri Jul 07, 2017 1:54 am
by ericcooper
Does the file /lib/firmware/brcm/brcmfmac43430-sdio.txt that it's complaining about exist?

It should be part of the firmware-brcm80211 package; make sure you upgraded that (from the stretch portion of the raspberrypi.org repo) in addition to the rest of stretch from the raspbian.org repo.

Re: Wifi and Debian Stretch

Posted: Fri Jul 07, 2017 5:55 am
by hommar
polymorphism wrote:Ok, but on my Stretch I have always :

Code: Select all

$ sudo ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
...  
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
and when I change the name wlan0 by the new name, the result is identical :

Code: Select all

$ sudo wpa_supplicant -Dnl80211 -iwlp3s0 -c /etc/wpa_supplicant/wpa_supplicant.conf
"p3" in name is the third PCI card slot number :lol:
name is wlp3s0 for example only

PS if you update Jessie to Stretch, you have old names

Re: Wifi and Debian Stretch

Posted: Fri Jul 07, 2017 11:15 am
by polymorphism
My configuration :

Code: Select all

pi@fidji:~ $ cat /etc/debian_version 
9.0
pi@fidji:~ $ uname -a
Linux fidji 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
pi@fidji:~ $ cat /etc/apt/sources.list
deb http://mirrordirector.raspbian.org/raspbian/ stretch main contrib non-free rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://archive.raspbian.org/raspbian/ stretch main contrib non-free rpi
Interresting :

Code: Select all

pi@fidji:~ $ ls -l /lib/firmware/brcm/brcmfmac43430-sdio.txt
ls: cannot access '/lib/firmware/brcm/brcmfmac43430-sdio.txt': No such file or directory
But the issue is the same.

Re: Wifi and Debian Stretch

Posted: Fri Jul 07, 2017 6:13 pm
by DougieLawson

Re: Wifi and Debian Stretch

Posted: Tue Jul 18, 2017 5:33 am
by IAmARaspberryPi
DougieLawson wrote:Download this: http://archive.raspberrypi.org/debian/p ... i1_all.deb and install it.
Holy cow, that did the trick.

Code: Select all

pi@pi_model_3:~ $ sudo dpkg -i firmware-brcm80211_20161130-3+rpi1_all.deb 
(Reading database ... 36985 files and directories currently installed.)
Preparing to unpack firmware-brcm80211_20161130-3+rpi1_all.deb ...
Unpacking firmware-brcm80211 (20161130-3+rpi1) over (20161130-3) ...
Setting up firmware-brcm80211 (20161130-3+rpi1) ...
How did you know?! And why is the 20161130-3+rpi1 not the one used by default on an apt upgrade?

Re: Wifi and Debian Stretch

Posted: Thu Jul 20, 2017 12:02 am
by asandford
IAmARaspberryPi wrote: And why is the 20161130-3+rpi1 not the one used by default on an apt upgrade?
Because Raspbian stretch hasn't been released yet, so you'll get whatever the builders have released so far.

I'm not sure if this quote still holds true, but it might shed some light on why RPF packages aren't in Raspbian yet

From here
Note: Raspbian is not affiliated with the Raspberry Pi Foundation. Raspbian was created by a small, dedicated team of developers that are fans of the Raspberry Pi hardware, the educational goals of the Raspberry Pi Foundation and, of course, the Debian Project.

Re: Wifi and Debian Stretch

Posted: Thu Jul 20, 2017 4:55 pm
by DirkS
asandford wrote:I'm not sure if this quote still holds true, but it might shed some light on why RPF packages aren't in Raspbian yet
[/quote]
RPF has its own repo. Some packages in there may have a stretch version, but it's a work in progress.

Re: Wifi and Debian Stretch

Posted: Thu Jul 20, 2017 8:59 pm
by DougieLawson
IAmARaspberryPi wrote: How did you know?! And why is the 20161130-3+rpi1 not the one used by default on an apt upgrade?
I simply went looking for the latest available, regardless of distro version.
It should be part of the base build when Stretch is released for general availability.

Re: Wifi and Debian Stretch

Posted: Fri Jul 21, 2017 1:07 am
by asandford
DirkS wrote: RPF has its own repo. Some packages in there may have a stretch version, but it's a work in progress.
Indeed, that answers why an unreleased version isn't totally available or supported.

It'll be released when it's ready, why do people complain that unreleased, untested and unfixed things don't work?

If one wants to be at the cutting edge, expect to bleed.

Re: Wifi and Debian Stretch

Posted: Fri Jul 21, 2017 11:09 pm
by IAmARaspberryPi
asandford wrote:Indeed, that answers why an unreleased version isn't totally available or supported.

It'll be released when it's ready, why do people complain that unreleased, untested and unfixed things don't work?

If one wants to be at the cutting edge, expect to bleed.
Personally, I am not complaining about things not working. If I'm doing any complaining, it's only that there doesn't appear to be adequate documentation on helping oneself. For example, if I run into a problem on Debian testing or unstable, I know that I can hop on Debian's well-documented package search and look into what might be wrong myself. I can even submit patches to the maintainer and help out in my own way, as I have done in the past.

This may be a matter of me simply not knowing the Raspbian development process as well. If anyone would like to shed some light on how DougieLawson found the 20161130-3+rpi1 package so quickly, and how I could have found it for myself and how to view other package tracking information on the firmware-brcm80211 package, I am eager to learn.

I would appreciate your frustration if people in this thread were puling an XDA, but right now, your passive-aggressive comments seem like an overly harsh response.

Re: Wifi and Debian Stretch

Posted: Sat Jul 22, 2017 8:23 am
by rpdom
IAmARaspberryPi wrote:Personally, I am not complaining about things not working. If I'm doing any complaining, it's only that there doesn't appear to be adequate documentation on helping oneself. For example, if I run into a problem on Debian testing or unstable, I know that I can hop on Debian's well-documented package search and look into what might be wrong myself. I can even submit patches to the maintainer and help out in my own way, as I have done in the past.
One thing that is important: There is the Raspbian repo (raspbian.org), which is Debian recompiled for ARMv6 with some patches where required to make it work, and there is the Raspberry Pi repo (archive.raspberrypi.org) where any Pi specific packages and some with special fixes are housed.

If you have a problem with something from the Raspbian repo you should first check for bugs on the Debian site - they may not be Raspbian specific.

If you have problems with the Raspberry Pi repo then you can ask here.

The package Douge suggested is from the Raspberry Pi repo, not the Raspbian one. Specifically in the stretch release (which is available, just not quite ready for general use yet)

Re: Wifi and Debian Stretch

Posted: Thu Sep 10, 2020 11:01 am
by chimera
Wow, over 3 years later and my RPi 3b+ WiFi just dies out of the blue... I spend 5 hours troubleshooting why it doesn't work then stumble across this thread, one firmware download and dpkg command and WiFi is working again. I was just about to blow this away and re-image. Saved me more hours, THANKS!!!

Re: Wifi and Debian Stretch

Posted: Thu Sep 10, 2020 8:23 pm
by chimera
Spoke too soon, looks like this firmware isn't quite stable enough.

dmesg....

[ 20.820540] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled
[32967.394506] ieee80211 phy0: brcmf_fw_crashed: Firmware has halted or crashed
[32969.955200] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[32969.958755] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[32969.958959] brcmfmac: dongle trap info: type 0x3 @ epc 0x00000000
cpsr 0x20000003 spsr 0x20000010 sp 0x0006fc0c
lr 0x00009479 pc 0x00000000 offset 0x6fbb8
r0 0x0005c6cc r1 0x000367bc r2 0x00000021 r3 0x0007b420
r4 0x0006ad6c r5 0x00000000 r6 0x000367bc r7 0x0007b420
[32972.515197] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[32972.518562] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[32972.518725] brcmfmac: dongle trap info: type 0x3 @ epc 0x00000000
cpsr 0x20000003 spsr 0x20000010 sp 0x0006fc0c
lr 0x00009479 pc 0x00000000 offset 0x6fbb8
r0 0x0005c6cc r1 0x000367bc r2 0x00000021 r3 0x0007b420
r4 0x0006ad6c r5 0x00000000 r6 0x000367bc r7 0x0007b420
[32972.518739] ieee80211 phy0: brcmf_pno_clean: failed code -110
[32980.035252] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[32980.038843] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[32980.039100] brcmfmac: dongle trap info: type 0x3 @ epc 0x00000000
cpsr 0x20000003 spsr 0x20000010 sp 0x0006fc0c
lr 0x00009479 pc 0x00000000 offset 0x6fbb8
r0 0x0005c6cc r1 0x000367bc r2 0x00000021 r3 0x0007b420
r4 0x0006ad6c r5 0x00000000 r6 0x000367bc r7 0x0007b420
[32980.039122] ieee80211 phy0: brcmf_run_escan: error (-110)
[32980.039137] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
[32983.555226] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[32983.558597] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[32983.558759] brcmfmac: dongle trap info: type 0x3 @ epc 0x00000000
cpsr 0x20000003 spsr 0x20000010 sp 0x0006fc0c
lr 0x00009479 pc 0x00000000 offset 0x6fbb8
r0 0x0005c6cc r1 0x000367bc r2 0x00000021 r3 0x0007b420
r4 0x0006ad6c r5 0x00000000 r6 0x000367bc r7 0x0007b420
[32983.558773] ieee80211 phy0: brcmf_run_escan: error (-110)
[32983.558782] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
[32987.075355] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[32987.079013] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[32987.079296] brcmfmac: dongle trap info: type 0x3 @ epc 0x00000000
cpsr 0x20000003 spsr 0x20000010 sp 0x0006fc0c
lr 0x00009479 pc 0x00000000 offset 0x6fbb8
r0 0x0005c6cc r1 0x000367bc r2 0x00000021 r3 0x0007b420
r4 0x0006ad6c r5 0x00000000 r6 0x000367bc r7 0x0007b420
[32987.079322] ieee80211 phy0: brcmf_run_escan: error (-110)
[32987.079339] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
[32990.595249] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[32990.598619] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[32990.598781] brcmfmac: dongle trap info: type 0x3 @ epc 0x00000000
cpsr 0x20000003 spsr 0x20000010 sp 0x0006fc0c
lr 0x00009479 pc 0x00000000 offset 0x6fbb8
r0 0x0005c6cc r1 0x000367bc r2 0x00000021 r3 0x0007b420
r4 0x0006ad6c r5 0x00000000 r6 0x000367bc r7 0x0007b420
[32990.598795] ieee80211 phy0: brcmf_run_escan: error (-110)
[32990.598804] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
[32994.115337] ieee80211 phy0: brcmf_run_escan: error (-110)
[32994.115357] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
[32997.635290] ieee80211 phy0: brcmf_run_escan: error (-110)
[32997.635301] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
[33001.155298] ieee80211 phy0: brcmf_run_escan: error (-110)
[33001.155311] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
[33004.675375] ieee80211 phy0: brcmf_run_escan: error (-110)
[33004.675398] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
[33008.195323] ieee80211 phy0: brcmf_run_escan: error (-110)
[33008.195334] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)
[33011.715403] ieee80211 phy0: brcmf_run_escan: error (-110)
[33011.715426] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-110)

Re: Wifi and Debian Stretch

Posted: Fri Sep 11, 2020 3:02 am
by chimera
Tried the latest firmware, it fixed it but only for a certain amount of time. It runs, but then eventually just stops and IP address drops off. I have LAN connected, so I can ssh to the Rpi and check the logs. Really lost here...

pi@openhab2:~ $ iwlist wlan0 scan
wlan0 No scan results


pi@openhab2:~ $ ifconfig
wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether b8:27:eb:c7:02:e6 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


pi@openhab2:~ $ tail -1000f /var/log/syslog | grep brcmf
Sep 11 14:42:17 openhab2 kernel: [ 8.693062] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
Sep 11 14:42:17 openhab2 kernel: [ 8.707893] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
Sep 11 14:42:17 openhab2 kernel: [ 8.708238] usbcore: registered new interface driver brcmfmac
Sep 11 14:42:17 openhab2 kernel: [ 8.723374] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt failed with error -2
Sep 11 14:42:17 openhab2 kernel: [ 8.985009] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
Sep 11 14:42:17 openhab2 kernel: [ 8.985180] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
Sep 11 14:42:17 openhab2 kernel: [ 8.986112] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 22 2019 01:59:28 version 7.45.98.94 (r723000 CY) FWID 01-3b33decd
Sep 11 14:42:17 openhab2 kernel: [ 10.482598] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
Sep 11 14:42:27 openhab2 kernel: [ 20.532236] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled
Sep 11 14:53:00 openhab2 kernel: [ 8.842789] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
Sep 11 14:53:00 openhab2 kernel: [ 8.858312] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
Sep 11 14:53:00 openhab2 kernel: [ 8.859399] usbcore: registered new interface driver brcmfmac
Sep 11 14:53:00 openhab2 kernel: [ 8.899370] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt failed with error -2
Sep 11 14:53:00 openhab2 kernel: [ 9.097715] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
Sep 11 14:53:00 openhab2 kernel: [ 9.097865] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
Sep 11 14:53:00 openhab2 kernel: [ 9.099097] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 22 2019 01:59:28 version 7.45.98.94 (r723000 CY) FWID 01-3b33decd
Sep 11 14:53:01 openhab2 kernel: [ 10.782120] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
Sep 11 14:53:11 openhab2 kernel: [ 20.712604] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled


Help?!

Re: Wifi and Debian Stretch

Posted: Mon Sep 14, 2020 12:28 am
by chimera
Turns out it was a combo of brcm firmware on the rpi and also faulty firmware on my firewall not issuing dhcp correctly