No Wifi connection to Pi Zero W after Raspbian update

[carriba]

I've done this morning a "sudo apt-get update ; sudo apt-get -y upgrade" on a Raspberry Pi Zero W and from have been able to witness during the update that certain firmware packages have been installed as well.

Once the update has been completed, a simply rebooted the device with a "sudo shutdown -r now ; exit", however the device never comes up again (meaning, I cannot access it via SSH and cannot find it in my Wifi client llist).

After a power recycle, I see the green activity LED blinking, and then after a while it stays steady greem.

Still, I cannot connect to the device, and a wireless device scanner installed on my PC does not find the Raspberry Pi Zero W in the list of Wifi clients (note: it's been always connected fine to my Wifi network in teh past, and nothing has changed here).

I've followed the sticky post viewtopic.php?t=58151#p850218, and can confirm with Raspbian Desktop on my PC, it can recognise the device as a GPIO expansion board, when the SD card is removed from the device.

I went ahead and formatted the SD card and burned again the latest Raspbian Stretch image file of November 2017 available under https://www.raspberrypi.org/downloads/raspbian, created an "ssh" file and the "wpa_supplicant.conf" file with the same configuration content for my Wifi network (as before), inserted the SD card into the Raspberry Pi Zero W card reader, and plugged the device to power with the usual power adapter.

From the green activity LED, I can conclude that it is booting normal. However, still no access via SSH to the device, and my Wifi radar does not show up the Raspberry Pi Zero W as a Wifi client.

Í've done several power recycles, still the same issue: no Wifi connectivity to the Raspberry Pi Zero W.

I removed the SD card form the device, and plugged it in the PC, and see that the "ssh" file and the "wpa_supplicant.conf" file are no longer available on the SD card's top level directory. This means, during 1st boot these files have been copied over to the OS partition.

I formatted again the SD card with the formatter tool https://www.sdcard.org/downloads/format ... etupEN.exe and then flashed again the image file with the image writer tool https://sourceforge.net/projects/win32d ... t/download, have put again the "ssh" file and the same (!) "wpa_supplicant.conf" file on the top-level directory of teh SD card, and gently inserted the SD card into the Raspberry Pi Zero W's card reader.

After powering on, the same situation, Raspberry Pi Zero W not in the list of my Wifi clients and I cannot ping or connect to the device

Question: What have the Raspbian Stretch packages updates done today to my device?

[pcmanbob]

Just done the update on my pi zero w running stretch lite no problems at all.

As with any problem like this first thing is post your wpa_supplicant.conf file.

[carriba]

Here the contents of the "wpa_supplicant.conf" file masking confidential information:

Code: Select all

network={
    ssid="MyWifiNetworkSSID"
    psk="password"
    key_mgmt=WPA-PSK
}

I read the post viewtopic.php?f=63&t=203508&start=25#p1270662, which confirms that as part of the OS packages updates, the firmware is being updated as well.

What implications do the firmware updates have with today's Raspbian packages updates on my Raspberry Pi Zero W device?

Another point: I've started again with a plain vanilla image file on my SD card. Thus, ought to be able to work from there without any OS packages updates offered today, or?

[hippy]

The easiest option may be to temporarily connect your Zero W to a monitor and keyboard then you can directly interact with it.

[pcmanbob]

Your wpa_supplicant.conf file is missing the first 3 lines

Code: Select all

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=GB

network={
	ssid="MyWifiNetworkSSID"
	psk="password"
	key_mgmt=WPA-PSK
}

you may need to change the country code..

[JacobRask]

I have experienced the same issue today.
- and have currently not solved it.

A1: Updated (apt-get update/upgrade) Raspbian on my rPi-ZW.
A2: After a reboot the wlan0 interface is missing.
A3: I can only connect to the rPi-ZW through a microUSB-to-Ethernet-adapter.

I grabbed new SD-card and flashed a fresh image of Stretch (not Lite) (the 'November 29th 2017' version).
B1: Added ssh-file to /boot/.
B2: Connected the microUSB-to-Ethernet-adapter and booted up.
B3: ifconfig showed only 'eth0' and 'lo' interfaces.
B4: After shutdown I moved the SD card to a Raspberry Pi 3 and performed an update (apt-get update/upgrade) through Ethernet.
B5: On the rPi-3 all the interfaces are available (including 'wlan0').
B6: Moved the SD card back to rPi-ZW - but still no 'wlan0' interface.

BTW:
My wpa_supplicant.conf already contained the first 3 lines from above.

[carriba]

Sorry, I've forgotten to mention the 1st 3 lines in my previous post about the "wpa_supplicant.conf" file contents. In my case they look like this:

Code: Select all

country=GB
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

[MrEngman]

Strange, just tried apt-get update/upgrade on my Pi 0 W and then rebooted and wifi is working OK. Running Raspbian Stretch Lite upgraded to kernel 4.9.77+ #1081.

apt-get upgrade installed new versions of packages

Code: Select all

firmware-atheros firmware-brcm80211 firmware-libertas firmware-misc-nonfree firmware-realtek libtasn1-6 pi-bluetooth

I am connected to my Pi 0 W via the built in Broadcom wifi using SSH from my Win7 laptop. The Pi 0 W also has a second wifi adapter connected to the USB port, a TP-Link TL-WN725N, which also shows a connection to my network.

[carriba]

I started again: This time I used a Raspberry Pi 1 B+ device, which uses the same CPU as the Raspberry Pi Zero W device. Flashed the Raspbian Stretch "full" image of November 2017 (not the "lite" one) on a newly formatted SD card.

Created an "ssh" file and the "wpa_supplicant.conf" file with the same configuration content as before.

Put the SD card it in the Raspberry Pi 1 B+ device and started just fine and could connect to the device through its Ethernet interface hooked up on my LAN.

I've done the usual sudo "apt-get update ; sudo apt-get -y upgrade", and updated all the OS packages as published today (8 February 2018), I have checked that the same “/etc/wpa/wpa_supplicant.conf” is intact as copied during the boot (which is the case!).

After shutting down the Raspberry Pi 1 B+ device, I ejected the SD card and gently inserted it into the card reader of the Raspberry Pi Zero W device. I powered up the Raspberry Pi Zero W device, saw some LED activity during its booting, and also the LED of the Wifi adapter was flashing temporarily (meaning a Wifi client wants to connect).

Waited a while, the green coloured LED of the Raspberry Pi Zero W device stayed steady on all time, no flashing whatsoever.

With different Wifi scanner applications on my PC, I could find the Raspberry Pi Zero W device, could not ping it with the previous registered IP address, and no connection possible with SSH.

Thus, I removed power from the Raspberry Pi Zero W device, removed the SD card and inserted the same into the Raspberry Pi 1 B+ device, which came up when powered on.

Connected through the LAN interface to the Raspberry Pi 1 B+ device, I examined the messages entries in the “/var/log/syslog” file, and could find the following:

Code: Select all

Feb  8 17:05:18 pibox kernel: [    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:9E:23:52 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet plymouth.ignore-serial-consoles
...
Feb  8 17:05:21 pibox systemd[1]: Started Load/Save RF Kill Switch Status.
Feb  8 17:05:21 pibox systemd-udevd[128]: Process '/sbin/crda' failed with exit code 249.
Feb  8 17:05:21 pibox dhcpcd-run-hooks[351]: wlan0: starting wpa_supplicant
Feb  8 17:05:21 pibox systemd-udevd[128]: Process '/sbin/crda' failed with exit code 249.
Feb  8 17:05:22 pibox kernel: [   25.175178] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb  8 17:05:22 pibox kernel: [   25.175195] brcmfmac: power management disabled
Feb  8 17:05:22 pibox kernel: [   25.810409] Bluetooth: Core ver 2.22
...
Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: waiting for carrier
Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: carrier acquired
Feb  8 17:05:23 pibox bluetoothd[375]: Bluetooth daemon 5.43
Feb  8 17:05:23 pibox dhcpcd[265]: DUID 00:01:00:01:21:b0:de:68:b8:27:eb:cb:76:07
Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: IAID eb:cb:76:07
Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: adding address fe80::e149:f0b0:7b12:bf57
Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: carrier lost

From these error messages, I can determine that after today's update, the device cannot connect to an AP anymore when using Wifi

[hippy]

TLDR: Works for me

I have been meaning to work on my Zero W so powered it up, connected headless via telnet using the on-board WiFi. Last time it was used was in September so quite a lot to update and upgrade. Did that, took a deep breath, then 'sudo reboot'; it reconnected to my router and I'm back in. No problems so far.

For the record ...

Code: Select all

pi@Pi0W:~$ sudo cat /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
        ssid="VM250xxx-2G"
        psk="xxxxxxxx"
}
pi@Pi0W:~$

[HawaiianPi]

There is no upgradeable firmware on the Raspberry Pi computer itself. All firmware is stored on the SD card, so writing a fresh image to the card will remove any changes the update applied (including firmware). If your system worked previously but no longer does, even with a fresh image, then either your Pi has gone bad (unlikely unless you've been mucking about with GPIO and connected something wrong), or the problem is external to the Pi.

Have you made any changes to your network setup since the Pi last worked?
Have you made any changes to your Pi setup since it last worked (moved it, added or removed accessories, new PSU, etc.)?
Are you trying to set a static IP for your Pi0W (and if so, why)?
Have you verified the sha265 checksum of your Raspbian download?
Do you use Etcher to both extract and write the SD card (write the .zip file directly)?
Have you tried a different SD card?
What are you using for a power supply (make/model/volts/amps)?

I powered up the Raspberry Pi Zero W device, saw some LED activity during its booting, and also the LED of the Wifi adapter was flashing temporarily (meaning a Wifi client wants to connect).

What "LED of the Wifi adapter" are you referring to?

With different Wifi scanner applications on my PC, I could find the Raspberry Pi Zero W device, could not ping it with the previous registered IP address, and no connection possible with SSH.

If you can find it on your network with a network scanner, then it's connected. And why would you attempt to use a "previous registered IP address" if you now have the correct address from your network scan? Also, if you have powered down the Pi without a proper shutdown, SSH key generation might have gotten messed up, so start over with a fresh image to be sure.

And for the record, I just did a full update/dist-upgrade on my Pi0W running the November 2017 Raspbian Stretch, and it's still working fine. So the problem isn't Raspbian. Sorry you're still having trouble. Hopefully with some additional troubleshooting we'll be able to get you up and running again.

[pcmanbob]

I examined the messages entries in the “/var/log/syslog” file, and could find the following:

Code: Select all

Feb  8 17:05:18 pibox kernel: [    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:9E:23:52 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet plymouth.ignore-serial-consoles
...
Feb  8 17:05:21 pibox systemd[1]: Started Load/Save RF Kill Switch Status.
Feb  8 17:05:21 pibox systemd-udevd[128]: Process '/sbin/crda' failed with exit code 249.
Feb  8 17:05:21 pibox dhcpcd-run-hooks[351]: wlan0: starting wpa_supplicant
Feb  8 17:05:21 pibox systemd-udevd[128]: Process '/sbin/crda' failed with exit code 249.
Feb  8 17:05:22 pibox kernel: [   25.175178] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb  8 17:05:22 pibox kernel: [   25.175195] brcmfmac: power management disabled
Feb  8 17:05:22 pibox kernel: [   25.810409] Bluetooth: Core ver 2.22
...
Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: waiting for carrier
Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: carrier acquired
Feb  8 17:05:23 pibox bluetoothd[375]: Bluetooth daemon 5.43
Feb  8 17:05:23 pibox dhcpcd[265]: DUID 00:01:00:01:21:b0:de:68:b8:27:eb:cb:76:07
Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: IAID eb:cb:76:07
Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: adding address fe80::e149:f0b0:7b12:bf57
Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: carrier lost

From these error messages, I can determine that after today's update, the device cannot connect to an AP anymore when using Wifi

I think your log entries are a red herring, I have the same entries in my “/var/log/syslog” and yet my pi zreo w connects to my wifi no problem.

Code: Select all

Feb  8 20:01:29 zeropi systemd[1]: Starting Load/Save RF Kill Switch Status...
Feb  8 20:01:29 zeropi systemd[1]: Started LSB: Autogenerate and use a swap file.
Feb  8 20:01:29 zeropi systemd[1]: Started Load/Save RF Kill Switch Status.
Feb  8 20:01:30 zeropi dhcpcd[246]: wlan0: starting wpa_supplicant
Feb  8 20:01:30 zeropi systemd-udevd[143]: Process '/sbin/crda' failed with exit code 249.
Feb  8 20:01:30 zeropi dhcpcd-run-hooks[343]: wlan0: starting wpa_supplicant
Feb  8 20:01:30 zeropi kernel: [   30.516484] random: crng init done
Feb  8 20:01:30 zeropi kernel: [   30.517618] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb  8 20:01:30 zeropi kernel: [   30.517631] brcmfmac: power management disabled
Feb  8 20:01:31 zeropi dhcpcd[246]: wlan0: waiting for carrier
Feb  8 20:01:31 zeropi dhcpcd[246]: wlan0: carrier acquired
Feb  8 20:01:31 zeropi dhcpcd[246]: DUID 00:01:00:01:21:44:28:6a:b8:27:eb:58:7e:0f
Feb  8 20:01:31 zeropi dhcpcd[246]: wlan0: IAID eb:58:7e:0f
Feb  8 20:01:31 zeropi dhcpcd[246]: wlan0: adding address fe80::3478:89c6:6927:9f12
Feb  8 20:01:31 zeropi dhcpcd[246]: wlan0: carrier lost
Feb  8 20:01:31 zeropi dhcpcd[246]: wlan0: deleting address fe80::3478:89c6:6927:9f12
Feb  8 20:01:31 zeropi kernel: [   31.840382] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Feb  8 20:01:31 zeropi dhcpcd[246]: wlan0: carrier acquired
Feb  8 20:01:31 zeropi dhcpcd[246]: wlan0: IAID eb:58:7e:0f
Feb  8 20:01:31 zeropi dhcpcd[246]: wlan0: adding address fe80::e860:2dd0:b714:57f5
Feb  8 20:01:32 zeropi dhcpcd[246]: wlan0: soliciting an IPv6 router
Feb  8 20:01:32 zeropi kernel: [   32.343043] Bluetooth: Core ver 2.22
Feb  8 20:01:32 zeropi kernel: [   32.343238] NET: Registered protocol family 31
Feb  8 20:01:32 zeropi kernel: [   32.343249] Bluetooth: HCI device and connection manager initialized
Feb  8 20:01:32 zeropi kernel: [   32.343281] Bluetooth: HCI socket layer initialized
Feb  8 20:01:32 zeropi kernel: [   32.343301] Bluetooth: L2CAP socket layer initialized
Feb  8 20:01:32 zeropi kernel: [   32.343362] Bluetooth: SCO socket layer initialized
Feb  8 20:01:32 zeropi kernel: [   32.359699] Bluetooth: HCI UART driver ver 2.3
Feb  8 20:01:32 zeropi kernel: [   32.359720] Bluetooth: HCI UART protocol H4 registered
Feb  8 20:01:32 zeropi kernel: [   32.359727] Bluetooth: HCI UART protocol Three-wire (H5) registered
Feb  8 20:01:32 zeropi kernel: [   32.359931] Bluetooth: HCI UART protocol Broadcom registered
Feb  8 20:01:32 zeropi btuart[239]: bcm43xx_init
Feb  8 20:01:32 zeropi btuart[239]: Flash firmware /lib/firmware/BCM43430A1.hcd
Feb  8 20:01:32 zeropi btuart[239]: Set BDADDR UART: b8:27:eb:a7:81:f0
Feb  8 20:01:32 zeropi btuart[239]: Set Controller UART speed to 3000000 bit/s
Feb  8 20:01:32 zeropi btuart[239]: Device setup complete
Feb  8 20:01:32 zeropi dhcpcd[246]: wlan0: rebinding lease of 192.168.1.160

[carriba]

Please check again my "/var/log/syslog" entries after yesterday's Raspbian OS packages update, where it writes:

Code: Select all

Feb  8 17:05:21 pibox systemd-udevd[128]: Process '/sbin/crda' failed with exit code 249.
Feb  8 17:05:21 pibox dhcpcd-run-hooks[351]: wlan0: starting wpa_supplicant
Feb  8 17:05:21 pibox systemd-udevd[128]: Process '/sbin/crda' failed with exit code 249.
Feb  8 17:05:22 pibox kernel: [   25.175178] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[...]
Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: waiting for carrier
Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: carrier acquired
Feb  8 17:05:23 pibox bluetoothd[375]: Bluetooth daemon 5.43
Feb  8 17:05:23 pibox dhcpcd[265]: DUID 00:01:00:01:21:b0:de:68:b8:27:eb:cb:76:07
Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: IAID eb:cb:76:07
Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: adding address fe80::e149:f0b0:7b12:bf57
Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: carrier lost

Flashing the Raspbian Stretch image of November 2017 on the SD card (without any OS packages updates) works fine with the Raspberry Pi Zero W device and gets conncted to the same Wifi AP device. A SSH session works fine!

Thus, IMHO I may be able to conclude that the Wifi AP device does not have any problems, and nothing has changed in the past pertaining to its setup. The SD card ought to be fine, too, as it works just fine with my other Raspberry PI devices.

[pcmanbob]

Please check again my "/var/log/syslog" entries after yesterday's Raspbian OS packages update, where it writes:

Yes those log entries exist and if you look they exist in my log to but my pi zero connects no problem.

they also refer to IPv6 were the link is not ready.

pulled just the relevant lines from both log contents.

Code: Select all

carriba /var/log/syslog

Feb  8 17:05:21 pibox dhcpcd-run-hooks[351]: wlan0: starting wpa_supplicant

Feb  8 17:05:22 pibox kernel: [   25.175178] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: waiting for carrier
Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: carrier acquired

Feb  8 17:05:23 pibox dhcpcd[265]: DUID 00:01:00:01:21:b0:de:68:b8:27:eb:cb:76:07
Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: IAID eb:cb:76:07
Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: adding address fe80::e149:f0b0:7b12:bf57
Feb  8 17:05:23 pibox dhcpcd[265]: wlan0: carrier lost



pcmanbob /var/log/syslog

Feb  8 20:01:30 zeropi dhcpcd-run-hooks[343]: wlan0: starting wpa_supplicant

Feb  8 20:01:30 zeropi kernel: [   30.517618] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

Feb  8 20:01:31 zeropi dhcpcd[246]: wlan0: waiting for carrier
Feb  8 20:01:31 zeropi dhcpcd[246]: wlan0: carrier acquired
Feb  8 20:01:31 zeropi dhcpcd[246]: DUID 00:01:00:01:21:44:28:6a:b8:27:eb:58:7e:0f
Feb  8 20:01:31 zeropi dhcpcd[246]: wlan0: IAID eb:58:7e:0f
Feb  8 20:01:31 zeropi dhcpcd[246]: wlan0: adding address fe80::3478:89c6:6927:9f12
Feb  8 20:01:31 zeropi dhcpcd[246]: wlan0: carrier lost

[hippy]

Flashing the Raspbian Stretch image of November 2017 on the SD card (without any OS packages updates) works fine with the Raspberry Pi Zero W device and gets conncted to the same Wifi AP device. A SSH session works fine!

In your OP you wrote ...

I went ahead and formatted the SD card and burned again the latest Raspbian Stretch image file of November 2017 ... However, still no access via SSH to the device, and my Wifi radar does not show up the Raspberry Pi Zero W as a Wifi client.

So did it not work, but is now working, or what ? I am utterly confused.

[carriba]

Okay, let’s start again as I’m getting confused with all your valuable feedback.

The PSU used and the SD are OK and they’re also working fine with a Raspberry Pi 1 B+ device. Thus, I may exclude any hardware problems here.

I flashed the SD card again with the Raspbian Stretch image of November 2017, just put the “ssh” and the same “wpa_supplicant.conf” files on the top level directory of the SD card.

Gently put the SD card in the reader of the Raspberry Pi Zero W device, and powered it on with the same PSU as used before with the Raspberry Pi 1 B+ device.

The green LED is flashing, thus some activity is going on there (i.e. partition resizing), after I while I can discover the device with my Wifi radar application on my PC and can connect to the Raspberry Pi Zero W device (maybe I missed to mention this somewhere in the initial post, but hey, the device always worked fine for me in the past) using SSH.

As proof, here the relevant entries of the “/var/log/syslog” file:

Code: Select all

Nov 29 02:56:34 raspberrypi kernel: [    0.000000] OF: fdt:Machine model: Raspberry Pi Zero W Rev 1.1
[...]
Nov 29 02:56:43 raspberrypi dhcpcd-run-hooks[382]: wlan0: starting wpa_supplicant
[...]
Nov 29 02:56:49 raspberrypi dhcpcd[355]: wlan0: waiting for carrier
Nov 29 02:56:49 raspberrypi dhcpcd[355]: wlan0: carrier acquired
[...]
Nov 29 02:56:52 raspberrypi dhcpcd[355]: DUID 00:01:00:01:21:b0:de:74:b8:27:eb:cb:76:07
Nov 29 02:56:52 raspberrypi dhcpcd[355]: wlan0: IAID eb:cb:76:07
Nov 29 02:56:52 raspberrypi dhcpcd[355]: wlan0: adding address fe80::a43f:84bf:ab99:1d32
Nov 29 02:56:52 raspberrypi dhcpcd[355]: wlan0: carrier lost
Nov 29 02:56:52 raspberrypi dhcpcd[355]: wlan0: deleting address fe80::a43f:84bf:ab99:1d32
[...]
Nov 29 02:57:30 raspberrypi dhcpcd[355]: wlan0: IAID eb:cb:76:07
Nov 29 02:57:30 raspberrypi dhcpcd[355]: wlan0: adding address fe80::26c6:2f1b:ecd0:ca9e
Nov 29 02:57:30 raspberrypi dhcpcd[355]: wlan0: soliciting an IPv6 router
Nov 29 02:57:31 raspberrypi dhcpcd[355]: wlan0: soliciting a DHCP lease
Nov 29 02:57:31 raspberrypi dhcpcd[355]: wlan0: offered 192.168.0.31 from 192.168.0.254
Nov 29 02:57:31 raspberrypi dhcpcd[355]: wlan0: probing address 192.168.0.31/24
Nov 29 02:57:31 raspberrypi avahi-daemon[285]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::26c6:2f1b:ecd0:ca9e.
Nov 29 02:57:31 raspberrypi avahi-daemon[285]: New relevant interface wlan0.IPv6 for mDNS.
Nov 29 02:57:31 raspberrypi avahi-daemon[285]: Registering new address record for fe80::26c6:2f1b:ecd0:ca9e on wlan0.*.
[...]
Nov 29 02:57:35 raspberrypi dhcpcd[355]: wlan0: leased 192.168.0.31 for 864000 seconds
Nov 29 02:57:35 raspberrypi avahi-daemon[285]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.31.
Nov 29 02:57:35 raspberrypi dhcpcd[355]: wlan0: adding route to 192.168.0.0/24
Nov 29 02:57:35 raspberrypi dhcpcd[355]: wlan0: adding default route via 192.168.0.254
Nov 29 02:57:35 raspberrypi avahi-daemon[285]: New relevant interface wlan0.IPv4 for mDNS.
Nov 29 02:57:35 raspberrypi avahi-daemon[285]: Registering new address record for 192.168.0.31 on wlan0.IPv4.

Note: The date & time mention in the logs above are correct, as it is the 1st time boot of the image and the OS has not yet synchronised with an NTP source via Internet.

And here the relevant entries of the “/var/log/kern.log” file:

Code: Select all

Nov 29 02:56:46 raspberrypi kernel: [   26.953253] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[...]
Nov 29 02:57:30 raspberrypi kernel: [   70.654854] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

Albeit my Wifi AP does not provide IPv6 services, the Raspberry Pi Zero W device connects correctly to my Wifi AP, and I can collect above log files with SSH through a Wifi connection.

On the same SSH prompt, I’m firing now the command “sudo apt-get update ; sudo apt-get –y upgrade”, which shows the following output:

Code: Select all

Get:1 http://archive.raspberrypi.org/debian stretch InRelease [25.3 kB]
Get:2 http://mirrordirector.raspbian.org/raspbian stretch InRelease [15.0 kB]
Get:3 http://archive.raspberrypi.org/debian stretch/main armhf Packages [139 kB]
Get:4 http://archive.raspberrypi.org/debian stretch/ui armhf Packages [28.0 kB]
Get:5 http://mirrordirector.raspbian.org/raspbian stretch/main armhf Packages [11.7 MB]
Get:6 http://mirrordirector.raspbian.org/raspbian stretch/contrib armhf Packages [56.8 kB]
Get:7 http://mirrordirector.raspbian.org/raspbian stretch/non-free armhf Packages [95.2 kB]
Fetched 12.0 MB in 34s (349 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  wolfram-engine
The following packages will be upgraded:
  base-files bind9-host bluez-firmware curl dbus dbus-user-session dbus-x11 erlang-base erlang-crypto erlang-syntax-tools firmware-atheros firmware-brcm80211
  firmware-libertas firmware-misc-nonfree firmware-realtek gir1.2-gdkpixbuf-2.0 gstreamer1.0-omx gstreamer1.0-omx-rpi gstreamer1.0-omx-rpi-config gtk2-engines-clearlookspix
  idle-python2.7 iproute2 libavcodec57 libavfilter6 libavformat57 libavresample3 libavutil55 libbind9-140 libcurl3 libcurl3-gnutls libdbus-1-3 libdns-export162 libdns162
  libfm-data libfm-extra4 libfm-gtk-data libfm-gtk4 libfm-modules libfm4 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libicu57 libisc-export160 libisc160 libisccc140
  libisccfg140 liblwres141 libobrender32v5 libobt2v5 libpoppler64 libpostproc54 libpython2.7 libpython2.7-dev libpython2.7-minimal libpython2.7-stdlib libsqlite3-0
  libssl1.0.2 libswresample2 libswscale4 libtasn1-6 libtiff5 libxcursor1 libxkbcommon-x11-0 libxkbcommon0 libxml2 lxpanel lxpanel-data lxplug-bluetooth lxplug-network
  lxplug-ptbatt openbox openssh-client openssh-server openssh-sftp-server pcmanfm pi-bluetooth pipanel pishutdown poppler-utils python-scrollphathd python2.7 python2.7-dev
  python2.7-minimal python3-scrollphathd raspberrypi-sys-mods raspberrypi-ui-mods raspi-config rc-gui rpd-icons rpi-chromium-mods rsync sensible-utils ssh tzdata
94 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 91.4 MB of archives.
After this operation, 1,169 kB of additional disk space will be used.
[...]

I reboot the device, once the all above cited OS packages updates have been completed. Some LED flashing activity is going on, then the LED stays steady lit.

Waited a while, however my Wifi radar cannot discover the device, a ping or SSH with the same known IP address not possible.

I unplug the PSU, remove the SD card from Raspberry Pi Zero W device, and insert it on the card reader of a Raspberry Pi 1 B+ device.

Powered it on, and it comes up without any problems allow me to connect via SSH to the device using Ethernet LAN.

Checking backwards the history of the “/var/log/syslog” entries, I find the following:

Code: Select all

Feb  9 11:45:33 raspberrypi kernel: [    0.000000] OF: fdt:Machine model: Raspberry Pi Zero W Rev 1.1
[...]
Feb  9 11:45:38 raspberrypi dhcpcd[283]: wlan0: waiting for carrier
Feb  9 11:45:38 raspberrypi dhcpcd[283]: wlan0: carrier acquired
Feb  9 11:45:38 raspberrypi dhcpcd[283]: DUID 00:01:00:01:21:b0:de:5a:b8:27:eb:93:6e:e8
Feb  9 11:45:38 raspberrypi dhcpcd[283]: wlan0: IAID eb:cb:76:07
Feb  9 11:45:38 raspberrypi dhcpcd[283]: wlan0: adding address fe80::dfb7:9c3:7432:8e
Feb  9 11:45:39 raspberrypi dhcpcd[283]: wlan0: carrier lost
Feb  9 11:45:39 raspberrypi dhcpcd[283]: wlan0: deleting address fe80::dfb7:9c3:7432:8e
[...]

And here the relevant entries of the “/var/log/kern.log” file:

Code: Select all

Feb  9 11:45:37 pibox kernel: [   17.902183] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

Please let me know your observations…

[pcmanbob]

OK so i see what you are saying but what I am saying is that your failed connection may not be related to these lines

Code: Select all

Feb  9 11:45:33 raspberrypi kernel: [    0.000000] OF: fdt:Machine model: Raspberry Pi Zero W Rev 1.1
[...]
Feb  9 11:45:38 raspberrypi dhcpcd[283]: wlan0: waiting for carrier
Feb  9 11:45:38 raspberrypi dhcpcd[283]: wlan0: carrier acquired
Feb  9 11:45:38 raspberrypi dhcpcd[283]: DUID 00:01:00:01:21:b0:de:5a:b8:27:eb:93:6e:e8
Feb  9 11:45:38 raspberrypi dhcpcd[283]: wlan0: IAID eb:cb:76:07
Feb  9 11:45:38 raspberrypi dhcpcd[283]: wlan0: adding address fe80::dfb7:9c3:7432:8e
Feb  9 11:45:39 raspberrypi dhcpcd[283]: wlan0: carrier lost
Feb  9 11:45:39 raspberrypi dhcpcd[283]: wlan0: deleting address fe80::dfb7:9c3:7432:8e
[...]

because in your working pi zero example ( and in mine ) these lines still exist

Nov 29 02:56:34 raspberrypi kernel: [ 0.000000] OF: fdt:Machine model: Raspberry Pi Zero W Rev 1.1
[...]
Nov 29 02:56:43 raspberrypi dhcpcd-run-hooks[382]: wlan0: starting wpa_supplicant
[...]
Nov 29 02:56:49 raspberrypi dhcpcd[355]: wlan0: waiting for carrier
Nov 29 02:56:49 raspberrypi dhcpcd[355]: wlan0: carrier acquired
[...]
Nov 29 02:56:52 raspberrypi dhcpcd[355]: wlan0: IAID eb:cb:76:07
Nov 29 02:56:52 raspberrypi dhcpcd[355]: wlan0: adding address fe80::a43f:84bf:ab99:1d32
Nov 29 02:56:52 raspberrypi dhcpcd[355]: wlan0: carrier lost
Nov 29 02:56:52 raspberrypi dhcpcd[355]: wlan0: deleting address fe80::a43f:84bf:ab99:1d32
[...]
Nov 29 02:57:30 raspberrypi dhcpcd[355]: wlan0: IAID eb:cb:76:07
Nov 29 02:57:30 raspberrypi dhcpcd[355]: wlan0: adding address fe80::26c6:2f1b:ecd0:ca9e
Nov 29 02:57:30 raspberrypi dhcpcd[355]: wlan0: soliciting an IPv6 router
Nov 29 02:57:31 raspberrypi dhcpcd[355]: wlan0: soliciting a DHCP lease
Nov 29 02:57:31 raspberrypi dhcpcd[355]: wlan0: offered 192.168.0.31 from 192.168.0.254
Nov 29 02:57:31 raspberrypi dhcpcd[355]: wlan0: probing address 192.168.0.31/24
Nov 29 02:57:31 raspberrypi avahi-daemon[285]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::26c6:2f1b:ecd0:ca9e.
Nov 29 02:57:31 raspberrypi avahi-daemon[285]: New relevant interface wlan0.IPv6 for mDNS.
Nov 29 02:57:31 raspberrypi avahi-daemon[285]: Registering new address record for fe80::26c6:2f1b:ecd0:ca9e on wlan0.*.
[...]
Nov 29 02:57:35 raspberrypi dhcpcd[355]: wlan0: leased 192.168.0.31 for 864000 seconds
Nov 29 02:57:35 raspberrypi avahi-daemon[285]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.31.
Nov 29 02:57:35 raspberrypi dhcpcd[355]: wlan0: adding route to 192.168.0.0/24
Nov 29 02:57:35 raspberrypi dhcpcd[355]: wlan0: adding default route via 192.168.0.254
Nov 29 02:57:35 raspberrypi avahi-daemon[285]: New relevant interface wlan0.IPv4 for mDNS.
Nov 29 02:57:35 raspberrypi avahi-daemon[285]: Registering new address record for 192.168.0.31 on wlan0.IPv4.


Hence my red herring comment, its the lines after were your pi gets its IPv4 address that you want to look for in your failed attempt to connect to the wireless network, starting at Nov 29 02:57:31

[carriba]

Yes, they may not be related, however I'm not getting any further line entries in the "/var/log/syslog" file that allows me to compare.

This said, the line entries in the "/var/log/kern.log" file are different.

[hippy]

Checking backwards the history of the “/var/log/syslog” entries, I find the following:

I think I understand now; what you are saying is that lines which would be expected to appear in the log are not appearing.

I can't explain that. I can only add that, from what I recall when I looked yesterday, I get very similar to what pcmanbob posts above, including "carrier lost", "deleting address" and the like, but eventually a "wlan0: offered 192.168.0.x" and the rest.

That is on a Zero W. Stretch which was previously installed, last booted in September, 'apt-get upgrade' yesterday, after a reboot.

I would agree with pcmanbob that what you are seeing is probably a red herring, not indicative of a problem; is what would be expected. It's what isn't there which is inexplicable at this time.

Perhaps the full syslog from "wlan0: starting wpa_supplicant" needs posting so so it can be compared to one where it works to see where any subtle differences may lie.

[hippy]

Yes, they may not be related, however I'm not getting any further line entries in the "/var/log/syslog" file that allows me to compare.

Do you mean no lines at all, or no lines related to dchcpd / wlan / avahi ?

[MrEngman]

Hi,

I've been running my PI 0 W without problems but I have the built in Broadcom wifi and another wifi adapter connected to the USB port. I disconnected the USB wifi and the Pi 0 W wifi still connected to my network OK.

I then did an update/upgrade and my Pi 0 W then refused to connect to my network. Very strange. I then noticed the the update/upgrade installed a new version of the Broadcom firmware.

So started from scratch and created a new SD card using 2017-11-29-raspbian-stretch-lite. Copied wpa_supplicant.conf and ssh files to the boot partition and plugged the SD card into my Pi 0 W and it booted and connected to my network.

I then did an update/upgrade and rebooted the Pi 0 W and it refused to connect to my network. The update/upgrade installed 41 packages including a new version of the Broadcom wifi firmware.

I then re-installed 2017-11-29-raspbian-stretch-lite on the SD card again and the Pi 0 W was able to connect to my network again. I then did update/upgrade but this time did not install the Broadcom firmware. After rebooting the Pi 0 W connected to my network without problems, so seems like an issue with the new firmware.

I reconnected the USB wifi adapter to the USB port and rebooted and both wifis connected to my network and I then updated the Broadcom firmware and rebooted. Strangly both wifis connected to my network. I then disconnected the USB wifi and rebooted and the Broadcom wifi refused to connect to my network again. Really wierd. Reconnected the USB wifi and restarted the Pi 0 W and both wifis connected to my network. Really,really wierd.

Checking the logs and they looked similar to yours with apparently issues with IPV6. My network uses an old Windows domain controller and it doesn't like IPV6 so I decided to disable IPV6.

I took the SD card from the Pi 0 W and mounted it on another Pi and edited file /etc/modprobe.d/ipv6.conf and added the line

Code: Select all

blacklist ipv6

to the start of the file. I disconnected the usb wifi on the Pi 0 W and plugged the SD card back into the Pi 0 W and restarted it and the built in wifi connected without issues.

So it seems disabling IPV6 fixed the problem.

A really wierd issue. With the new Broadcon firmware installed and IPV6 enabled the built in wifi will not connect, but then if I connect a wifi adapter to the usb port the USB wifi and the built in Broadcom wifi both connect. Very strange.

[carriba]

I started again with a brand new SD card, and next to firing “sudo apt-get update ; sudo apt-get –y upgrade”, I also executed the command "sudo rpi-update" to bump up the kernel version.

Same symptoms with fresh image: connectivity to the Raspberry Pi Zero W device with SSH is working fine using Wifi.

After the OS packages update: the Raspberry Pi Zero W device comes up (LED flashing, then stays pn all time), however the device cannot connect to the Wifi AP. I cannot find it with my Wifi radar, cannot ping to the known IP address.

Removing the SD card from the Raspberry Pi Zero W device and inserting it into the Raspberry Pi 1 B+ device, I’m able to find the following “/var/log/syslog” entries:

Code: Select all

Feb  9 14:29:28 raspberrypi kernel: [    0.000000] Linux version 4.9.79+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #1091 Tue Feb 6 12:58:13 GMT 2018
[...]
Feb  9 14:29:28 raspberrypi kernel: [    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:9E:23:52 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTUUID=e7f04ac3-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[...]
Feb  9 14:29:30 raspberrypi systemd-udevd[134]: Process '/sbin/crda' failed with exit code 249.
Feb  9 14:29:30 raspberrypi dhcpcd-run-hooks[335]: wlan0: starting wpa_supplicant
[...]
Feb  9 14:29:30 raspberrypi systemd-udevd[134]: Process '/sbin/crda' failed with exit code 249.
[...]
Feb  9 14:29:31 raspberrypi kernel: [   17.185928] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb  9 14:29:31 raspberrypi kernel: [   17.185948] brcmfmac: power management disabled
Feb  9 14:29:32 raspberrypi dhcpcd[268]: wlan0: waiting for carrier
Feb  9 14:29:32 raspberrypi dhcpcd[268]: wlan0: carrier acquired
[...]
Feb  9 14:29:32 raspberrypi dhcpcd[268]: DUID 00:01:00:01:21:b0:de:74:b8:27:eb:cb:76:07
Feb  9 14:29:32 raspberrypi dhcpcd[268]: wlan0: IAID eb:cb:76:07
Feb  9 14:29:32 raspberrypi dhcpcd[268]: wlan0: adding address fe80::a43f:84bf:ab99:1d32
Feb  9 14:29:32 raspberrypi dhcpcd[268]: wlan0: carrier lost
[...]
Feb  9 14:29:32 raspberrypi dhcpcd[268]: wlan0: deleting address fe80::a43f:84bf:ab99:1d32

So, here I'm stuck to move further

[pcmanbob]

So does your log file stop at the line

Code: Select all

Feb  9 14:29:32 raspberrypi dhcpcd[268]: wlan0: deleting address fe80::a43f:84bf:ab99:1d32

if not post what comes after for the same boot date/time.

[carriba]

So does your log file stop at the line

Code: Select all

Feb  9 14:29:32 raspberrypi dhcpcd[268]: wlan0: deleting address fe80::a43f:84bf:ab99:1d32

if not post what comes after for the same boot date/time.

Pertaining to "dhcpcd" and "kernel" messages, yes. Other logs entries are intact and the same.

[pcmanbob]

So does your log file stop at the line

Code: Select all

Feb  9 14:29:32 raspberrypi dhcpcd[268]: wlan0: deleting address fe80::a43f:84bf:ab99:1d32

if not post what comes after for the same boot date/time.

Pertaining to "dhcpcd" and "kernel" messages, yes. Other logs entries are intact and the same.

if you post the log in its entirety for the boot relating to this date/time Feb 9 14:29:32 then we can compare it to our logs to see if we can find what's different other wise we are just guessing, we need data to work with..............