I am beginning to suspect hardware but will double check the file name I've done it before with 'ssh' as the conts as well as the name but I've tried both ways with this and no joy.
Sadly the pi's do not respond to PING even the ones working
"Nothing adds excitement like something that is none of your business" Note I am not a doctor, I don't even play one on television John F Davis
On Saturday, June 5, 2021, 04:45:18 PM EDT, Tom Early <n7tae@...> wrote:
I agree, if you have a new OS on a Pi Zero W and can see it on your home router, then that pretty much has to mean it installed your wpa_supplicant.conf file okay, so there must be a problem with ssh. I don't think it particularly matters, but when I create the /boot/ssh file, it's just an empty file. Be careful not to add some trailing white-space on the filename, and, of course, no filename extensions that sometimes windows can help but adding.
Unfortunately, you only get one shot at this, once your system does it's initial boot, you can't do the /boot/ssh trick again to enable ssh on a card that has already booted. As a postmortem, you can pop the card and see if the /boot/ssh file is still there, because if it is, then maybe you can look it over carefully to try to figure out what went wrong.
Since you can't get in from either your Windows putty app or your chromebook, I think you have to start over again.
One more thing, according to your original message, it seems like you making the card a desktop OS. You should use the "lite" (no-gui) OS. Then after you've done all you need to do with raspi-config, you'll need to "sudo apt install build-essential git" to install git, g++ and make because not all of these are on the "lite" OS.
