raspberrypi-ua-netinst: Cannot establish wifi connection on pi zero w

Trying to install on a pi zero w using wifi, the install fails after less than 1 minute having failed to establish a connection.

Log (sanitised)

==================================================
raspberrypi-ua-netinst
==================================================
Revision v1.5.1 (bd078c1)
Built on Wed Jan 25 12:41:03 CET 2017
Running on Raspberry Pi version unknown (9000c1)
==================================================
https://github.com/FooDeas/raspberrypi-ua-netinst/
==================================================
Starting HWRNG... OK
Mounting boot partition... OK
Copying boot files... OK
Executing installer-config.txt... OK

Checking if config.txt needs to be modified before starting installation...
OK

Unmounting boot partition... OK

Network configuration:
  ifname = wlan0
  ip_addr = dhcp
  wlan_ssid = layby
  wlan_psk = ok, pass the word.
  online_config = 

Waiting for wlan0... 1.. 2.. 3.. 4.. 5.. 6.. 7.. 8.. 9.. FAILED

Oh noes, something went wrong!
You have 10 seconds to hit ENTER to get a shell...

installer-config.txt

packages=apt-transport-https
release=wheezy
username=david
userpw=password
user_is_admin=1
hostname=pie
domainname=dbr
ifname=wlan0
wlan_country=GB
wlan_ssid="layby"
wlan_psk="ok, pass the word."
timezpne="Europe/London"
keyboard_layout=gb
locales=en_GB.UTF-8
system_default_locale=en_GB.UTF-8
gpu_mem=16
rootfstype=ext4
boot_volume_label=pieboot


I suspect that wifi hasn’t been exercised very much. Where it is possible, if wifi fails, most people would plug in a cable and sort out wifi later. This, of course, isn’t possible with the 0w.

I notice that my pi zero w isn’t recognised by the install script. The script isn’t up to date with the source quoted. This may well not matter, but it does indicate that I may be breaking new ground.

I’ve tried a few times with a few variations and I can’t think what to try next. I even tried an scS script with some debugging before I realised that the failure was before the custom script was loaded.

Help would be most appreciated, whether I’ve found a bug or I’m just being thick.

(edited to remove duplicate config)

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 21 (21 by maintainers)

Most upvoted comments

Thank you for testing the pi zero w!

Thank you for fixing the bug first time. Please close.

The follow-on was all my fault - I relied on my poor memory for debian/raspbian release names and got it wrong. I should have checked. I was thinking wheezy followed jessie. (If only they used numbers - 7, 8, 9, or even oldstable, stable, testing).

I did a dist-upgrade to jessie on the B a year or two ago and it’s been running happily ever since (with cron housekeeping) syncing to a usb drive.

The zero is destined for my son’s house to provide some off-site backup.

I apologise for wasting your time and thank you for continuing to provide support to an old man who should know better.

@dinosore Please test v1.5.2 beta and report. It is tagged with beta but 100% stable. Just a few new features that will come with the release are missing.

Good spot. @thijstriemstra .

You’re right. Just checked the file to make sure.

I’ve removed duplicate in original post.