GPi Zero 2 v1.52 & GPi Zero v1.15(Retropie Images for Pi Zero/Zero2 + GPi Case 1 & GPi Case 2W)
-
@sliver-x i update the ES and if its good i still using the v1.3. The problem is the time time needed to replace the roms.
The ssh connection i get acess dennied , you have this problems with the version 1.3? -
The WiFi performance in the Zero 2 is so slow (I get 2MB/s if I'm lucky sitting a foot from a decent 802.11ac access point) I don't even bother using it for ROM transfers beyond one-off additions to a set.
Using a USB3 internal card reader on my Linux desktop, I can rsync 130GB of ROMs and all their respective metadata to my Sandisk Extreme cards in about 38 minutes.
You could use a utility like Rufus or YUMI to create a Linux Live USB drive from a downloaded ISO and boot your PC or Mac off it: You'll get full access to the SD card and won't touch anything on your Windows/MacOS install (Though you will still be able to access the OS drive and any other drives/partitiions on your system). If you're not familiar with using Linux, I would recommend using Linux Mint; It's a very simply laid out interface as far as Linux DE's go.
If you don't mind installing drivers into your OS, another option would be to install an Ext4 driver like Paragon Linux File Systems for Windows, but it's not free and I can't vouch for how stable it actually is.
No, I never had SSH problems (Aside from timeouts and disconnnects that disabling the WLAN power saving mode and IPV6 seems to have resolved).
You may want to remove PermitRootLogon=yes from /etc/ssh/ssh_config, as that was a testing remnant I left in 1.3 and below that apparently can cause issues for some people?
Another thing to remember is that SSH uses host keys to determine the identify of the server: If those changed (Either due to another flash, or manually deleting them and having my SSH script recreate them), whatever SSH client you're using may still have cached keys from before and will refuse to connect as they don't match what's currently on the server's side. You would need to purge the cached keys and have it pull down the new ones.
I just did a clean flash of v1.3, connected to WiFi via the Retropie menu/OSK, enabled SSH in Advanced Settings and am now pushing several GB of data to it with no issues.
-
@sliver-x said in GPi Zero 2 v1.4 (Retroflag GPi Image for Pi Zero 2 W):
I've released v1.4: This addresses some things that were seriously bothering me up to this point (WiFi problems and EmulationStation's instability at times). This will probably be the last time I update it, unless something major is found that I've missed.
Thanks a lot for the v1.4 update, it's working very well and I like the looks and responsiveness!
-
@sliver-x hello, thank you so much for this package. But after flashing this build, I met a problem about instant saving. The hot-keys for instant saving, L+select for save and R+select for read, are not working when I press them. Can you please help to confirm how can I make the instant saving setting? Thank you!
-
Reconfigure the controls via EmulationStation's config menu and make sure Select is bound to Hotkey.
-
Hey this is awesome having an easy to run image for the retroflag and pi0 w 2, no ppsspp or drastic though? I know they're both far from perfect, but can be setup with xboxdrv and for certain games in the library run pretty well. Probably as good as you got out of the pi3 anyway?
-
@sliver-x thank you bro, I will try it.
-
I only set up N64, even, due to a lot of requests: The performance on it is not very good and can only really be played with a bluetooth controller with more buttons anyway.
You can add emulators as usual in Retropie on my image if you really want to run PSP or DS.
-
Is there something in this image that is disabled that prevents connecting via SSH using the hostname? Connecting using IP works fine, but using the hostname it never connects.
-
@sliver-x Thanks for this marvelous image!!
I found something about the malfunction of the d-pad. If you try to do a restart from the emustation menu, the emulatiostation config file of the pad change, change the dpad for an axis input. That's my case, I have to change the configuration manually to work again.
[ 8.283290] input: Microsoft X-Box 360 pad as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1:1.0/input/input0 [ 8.283847] usbcore: registered new interface driver xpad
Working file:
pi@gpizero2:~/.emulationstation $ cat es_input.cfg <?xml version="1.0"?> <inputList> <inputAction type="onfinish"> <command>/opt/retropie/supplementary/emulationstation/scripts/inputconfiguration.sh</command> </inputAction> <inputConfig type="joystick" deviceName="Microsoft X-Box 360 pad" deviceGUID="030000005e0400008e02000014010000"> <input name="pageup" type="button" id="4" value="1"/> <input name="up" type="hat" id="0" value="1"/> <input name="left" type="hat" id="0" value="8"/> <input name="select" type="button" id="6" value="1"/> <input name="right" type="hat" id="0" value="2"/> <input name="pagedown" type="button" id="5" value="1"/> <input name="y" type="button" id="3" value="1"/> <input name="x" type="button" id="2" value="1"/> <input name="down" type="hat" id="0" value="4"/> <input name="start" type="button" id="7" value="1"/> <input name="b" type="button" id="1" value="1"/> <input name="a" type="button" id="0" value="1"/> </inputConfig> </inputList>
Unconfigured file:
root@gpizero2:/home/pi/.emulationstation# cat es_input.cfg <?xml version="1.0"?> <inputList> <inputAction type="onfinish"> <command>/opt/retropie/supplementary/emulationstation/scripts/inputconfiguration.sh</command> </inputAction> <inputConfig type="joystick" deviceName="Microsoft X-Box 360 pad" deviceGUID="030000005e0400008e02000014010000"> <input name="pageup" type="button" id="4" value="1"/> <input name="up" type="axis" id="1" value="-1"/> <input name="left" type="axis" id="0" value="-1"/> <input name="select" type="button" id="6" value="1"/> <input name="right" type="axis" id="0" value="1"/> <input name="pagedown" type="button" id="5" value="1"/> <input name="y" type="button" id="3" value="1"/> <input name="x" type="button" id="2" value="1"/> <input name="down" type="axis" id="1" value="1"/> <input name="start" type="button" id="7" value="1"/> <input name="b" type="button" id="1" value="1"/> <input name="a" type="button" id="0" value="1"/> </inputConfig> </inputList>
I checked that this only happends when do a restart from the emulestation menu, If you do a poweroff/poweron via power button works correctly.
It also happend with the retropie config file:
Not working file:root@gpizero2:/opt/retropie/configs/all/retroarch-joypads# cat Microsoft\ X-Box\ 360\ pad.cfg input_device = "Microsoft X-Box 360 pad" input_driver = "udev" input_enable_hotkey_btn = "6" input_l_btn = "4" input_load_state_btn = "4" input_up_axis = "-1" input_left_axis = "-0" input_state_slot_decrease_axis = "-0" input_select_btn = "6" input_right_axis = "+0" input_state_slot_increase_axis = "+0" input_r_btn = "5" input_save_state_btn = "5" input_y_btn = "3" input_y_btn_label = "Square" input_x_btn = "2" input_menu_toggle_btn = "2" input_down_axis = "+1" input_start_btn = "7" input_exit_emulator_btn = "7" input_b_btn = "1" input_reset_btn = "1" input_a_btn = "0"
Working file:
pi@gpizero2:~/.emulationstation $ cat /opt/retropie/configs/all/retroarch-joypads/Microsoft\ X-Box\ 360\ pad.cfg input_device = "Microsoft X-Box 360 pad" input_driver = "udev" input_enable_hotkey_btn = "h0down" input_l_btn = "4" input_load_state_btn = "4" input_up_btn = "h0up" input_up_btn_label = "D-Pad Up" input_left_btn = "h0left" input_left_btn_label = "D-Pad Left" input_state_slot_decrease_btn = "h0left" input_select_btn = "6" input_right_btn = "h0right" input_right_btn_label = "D-Pad Right" input_state_slot_increase_btn = "h0right" input_r_btn = "5" input_save_state_btn = "5" input_y_btn = "3" input_y_btn_label = "Square" input_x_btn = "2" input_menu_toggle_btn = "2" input_down_btn = "h0down" input_down_btn_label = "D-Pad Down" input_start_btn = "7" input_exit_emulator_btn = "7" input_b_btn = "1" input_reset_btn = "1" input_a_btn = "0"
Regards
-
The hostname is "gpizero2" by default.
I ran into this a few times myself, but doing Safe Shutdown with the power switch then turning it back on would always fix it. I tried to find a way to remove the shutdown and restart options from the menu, but short of recompiling ES I didn't see a way to do that.
I like ES, but it gave me more problems than anything doing all this.
-
@sliver-x But under ssh login user are: pi and pass: rasperry this the same as the default .
There are no changes here right? i can't connect using ssh always get acess denied. -
The credentials are the same, yes. You have to enable SSH out of the box. I made a script under "Advanced Settings" that will handle enabling and disabling it from EmulationStation.
edit Also note that the image has no SSH keys on a clean flash: When you enable it via my script, it generates new ones. If you have cached keys from a previous flash your client will think it's being spoofed and refuse to connect until they are cleared on the client.
-
@sliver-x Unfortunately that didn't work; I have also already updated the hostname via raspi-config (where it was pi by default). Would updating here break something?
-
This post is deleted! -
No, it won't break anything. I just changed the hostname, and I can connect to it. Reflashed a clean install, default hostname is reachable after connecting it to WiFi and enabling SSH. Changed the hostname after this, can connect to the new hostname.
Not sure what's going on for you, but it sounds like it's something to do with hostname resolution in whatever is handling DNS in your LAN. Or the machine you're trying to reach it from. Try flushing the DNS cache?
-
@sliver-x I ended up adding an entry to /etc/hosts on my Mac for it to work. Thanks for your help.
-
If you're using a Mac, they use mDNS to do hostname resolution: You need to enable Avahi from "Advanced Settings". Once you do that you shouldn't need a static HOSTS entry.
-
@sliver-x Great, thank you once again.
-
Just had an idea. With some experimentation, the overclocking script could become an undervolting tool as well. I am currently experimenting with stock 1000MHz freq and an over_voltage value of -1 (negative values are indeed possible for those who didn't know)
If it's stable, I'll keep going down to see if -2 works on my board. The thing is, (and I'm not sure if this is the case or not) if the voltage value is the same as the Pi 3, but the CPU is running underclocked vs the Pi 3, there should be a fairly decent amount of undervolting headroom.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.