I tripped over the box with one or two spare Pi-zero's last night today or tomorrow depending on .. this is a busy weekend... I'll give a try to a brand new pi
"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 Sunday, June 6, 2021, 12:02:42 AM EDT, Justin Mann via groups.io <w9fyi@...> wrote:
Yep that is the same issue that I¡¯ve had, working with the wifi builder that is on the ?website. ?I was able to find another pi with an ethernet connection. ?However, I think were I in this situation again, I would find a usb-c ethernet adapter, and connect it to the pi-0 at least until you can get the wi-fi enabled. ?Then you can stick it back into the junk drawer until you need it the next time.
I hope this helps,
Justin
On Jun 5, 2021, at 6:23 PM, John F Davis <
wa8yxm@...> wrote:
The router seeds it. both routers see it depending on which wifi_Supplicant I use. But that's as far as it goes.
"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, 06:14:16 PM EDT, Justin Mann via <
w9fyi@...> wrote:
Trust me, I can totally relate, becuase I knew I had imaged the thing correctly, and yet it refused to connect to my wifi.
??
I fought for days trying to get this pi working for me¡ It wasn¡¯t fun
On Jun 5, 2021, at 3:45 PM, 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.
