@windg

That worked perfectly, thank you!

@mitu Yeah that would probably be the best idea for this problem.

Thanks for the help though, I might just do a clean install since it's a time sensitive project

I used sudo passwd hiryu and it allowed me to reset the password as that user. I checked the credentials with Firezilla and was able to login and see the folders. As always, thanks for the quick response.

The issue seems to be the mirror chosen supports IPv6 and the PI tries to connect via IPv6 to it, then fails. Changing the mirror may work, but you can also configure apt to use IPv4 only - see here.

@mitu nice one... My concern is about heavily customized setups (for example mine) where I have one directory per Arcade manufacturer (although they use the same emulator, they have a different theme setup for example), and directories do not necessarily match the system name, but I guess I can consider that as an edge case.

Thanks Again!

Ok figured it out.

First step, is to open your router and add your raspberry pi to the port forwarding. This is easy enough, you will want to use the internal IP of you pi, and open port 22 to tcp. you can usually access your router settings via http://192.168.0.1/ in your browser, providing you are wired directly into the router and not using wifi to connect.

Once this is done you will need the external ip. I found it by going on to my retropie under "retroarch netplay".

You will need this external ip to login from the internet.

this site has the steps on creating a new user:

https://humanwhocodes.com/snippets/2021/03/create-user-linux-ssh-key/

Once done you can open putty from any pc connected to the internet and ssh into your pi by using the external ip.

Expose your pi to the internet at your own risk.

If you don't want to use the line ssh pi@raspberrypi.local 'DISPLAY=:0 retropie' and still want to run my retropie script through SSH but NOT inside your established connection, then:

Do nano /usr/bin/retropie or nano /usr/bin/gamepad

And add this line below #!/bin/bash or wherever it works for you.

export DISPLAY=:0

Sometimes emulationstation crashes but I don't want to go that deep.

My job is completely done here. Have fun and stay safe.

@sleve_mcdichael Thanks!

@mitu ah perfect that worked too, thank you very much!

@themazingness
Hi!
Just for log information, I had this same problem today and I solved using this:

make a copy of /etc/network/interfaces
sudo cp /etc/network/interfaces /etc/network/interfaces.old

append to the file /etc/network/interfaces
allow-hotplug wlan0
iface wlan0 inet manual
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

enable the wpa_supplicant service and restart
sudo systemctl enable wpa_supplicant.service
sudo systemctl restart wpa_supplicant

*restart the system
sudo reboot now

@majorocd Heck of a point....

You've probably modified one of the start-up services which you shouldn't have. Post the contents of /etc/profile.d/10-retropie.sh file from your system.

@hairdyeguy said in Speeding up boot time and the necessary commands:

Tried it along side to disabeling bluetooth and rainbow splash screen + inserting the quiet flag to kernel. Booting time is now 28 seconds!
Are there more things you'd recommend?

The EmulationStation settings I mentioned in my first post - they should speed up dramatically the front-end startup.

Other services that are not strictly needed - raspi-config(?), hciuart (which you don't need if you disabled Bluetooth), rpi-eeprom-update (the Pi zero doesn't have an EEPROM).
You can also disable the swap service (dphys-swapfile) and test, but the Pi 0 has limited memory and swap may be useful if you want to install from source or run other things.

I'm not sure why the dev-mmcblk0p2.device takes so long, maybe the sdcard is not so fast (?).

There may be other - more radical - options

Is this solved already?

If not: I would run ssh -v pi@<address>, it should give you a hint.
If you are still puzzled: Mount the SD card of the clone in your Mac, look for a file /etc/hostname. Edit the file and change the hostname to something different e.g rpi-clone. Boot your Rpi with this SD card and try SSH'ing again.

HTH

If you have a spare USB stick, put a bootable Linux system like Ubuntu on it, boot your PC from the stick, and transfer the files using its so-called "live system".

See https://ubuntu.com/tutorials/create-a-usb-stick-on-windows for instructions how to create the bootable stick in Windows, and https://ubuntu.com/tutorials/try-ubuntu-before-you-install how to boot your PC into its live system.

Background: The live Linux should be able to write to your Windows partitions out of the box, whereas Windows can't read the Linux file system on your RetroPie card without third party software.

As always, be sure to backup any important data on your PC drive(s) before doing something with your PC that you never did before! Although Ubuntu's live image is known to be safe for many years, accidents or user mistakes can always happen.

@cyanxx. Will do Thanks