GPI case / raspberry pi Zero (no W) - can't establish SSH connection

mitu

What makes you think that plugging the 'case' to your PC will make the PI be networked ? The USB is not a dedicated network interface connector, you need an USB network adapter (wired or wireless) in order to make the Pi get a network address via USB - and have SSH working.

SSH is not authorized by adding something to config.txt- but by creating an empty/blank files named ssh (no extension) to the Boot partition.

mitu

Since the networking connection does not work, try to copy the script to the /boot partition - which you can access from the PC. Afterwards, you can try and run the script with a keyboard connected via USB.

cyperghost

@mitu This will not work. The Retroflag script makes use of gpiozero libary so there is need to install it. Imho the best way would be to utlilze the script for recalbox this should work out of the box becasue all libaries are already installed. Instead of the os.system call shutdown -h me would use killall -w emulationstation && poweroff
Then it should work....

About the SSH thing.... SSH into Pi0 over USB never tried but it could work. Ever heard about that?

mitu

@cyperghost said in GPI case / raspberry pi Zero (no W) - can't establish SSH connection:

About the SSH thing.... SSH into Pi0 over USB never tried but it could work. Ever heard about that?

No, but it might work :).

dyspho

@mitu
Thanks a lot for your answer.

I think the pi Zero just need a USB mini to USB cable to be recognized as a USB/Ethernet gadget by windows.
Not sure a 100% as it's not working on my side but I think it's what the documentation says.

Although, if using a USB network adaptor will fix my connectivity issue I will buy it right away !

Before I buy it any other opinion / reaction on this solution ?

mitu

@dyspho said in GPI case / raspberry pi Zero (no W) - can't establish SSH connection:

I think the pi Zero just need a USB mini to USB cable to be recognized as a USB/Ethernet gadget by windows.

Not out-of-the-box - see @cyperghost's reply with what you need to modify so that it works like you expected. Check the page he linked and make sure those configurations are in-place and then try again.

dyspho

@cyperghost
Thanks for your answer as well.

In my description I wasn't too much into the details but yes I've already tried the blank ssh file + cmdline.txt + config.txt solution.
It's the regular way to do it seems, but it doesn't give any result on my side except not booting retropie until the menu as I've explained (no error then but it's like retropie doesn't recognize the hardware if I boot with those modifications).

mitu

@dyspho Post the configurations you've done on the files.
Make sure you use something like Notepad++ to edit those files, regular Windows Notepad is not - yet - formatting them properly.

dyspho

@mitu
I did as described on this link (previously posted by @cyperghost ), of course, using notepad++

https://desertbot.io/blog/ssh-into-pi-zero-over-usb

mitu

@dyspho Did you use the RetroPie image ? Because the hostname should be retropie.local, not raspberrypi.local, in this case.

dyspho

@mitu just to be sure, in case I missed it, I just tried but unfortunately it doesn't work either.

gtoal

Another thing that can go wrong in this process... saving the wpa_supplicant.conf file to the boot partition - if you use Notepad, it is likely to add a hidden ".txt" extension and save the file as wpa_supplicant.conf.txt which you don't notice because windows hides the .txt extension.

mitu

@gtoal I don't see how this applies to the topic at hand - the poster specifically said it's a non-W(ifi) model and they don't try to use wireless at all.