ridgekuhn / arklone-retropie

rclone cloud syncing utility for RetroPie
GNU General Public License v3.0
8 stars 0 forks source link

Raspberry Pi Zero W #3

Open lalofwa opened 3 months ago

lalofwa commented 3 months ago

Is there any way to make it work on a Raspberry Pi Zero W with Retropie v4.8 installed? I use it on my GPI Case, but can't make it work.

ridgekuhn commented 3 months ago

Hello, the project was written and tested using RetroPie 4.8 and should be device-agnostic as far as which model Pi you're using. Could you please elaborate on "can't make it work"?

lalofwa commented 3 months ago

Hello! I have done a clean installation of RetroPie v4.8 on my RPI Zero W, which I use in a RetroFlag GPI Case. I successfully install the script, include my rclone file, but when I open the application either from the EmulationStation menu or from RetroPie-Setup, it says that I haven't configured any rclone server. I check the arklone.cfg file and manually add the server name (in my case, I named it 'retropie') between the empty quotation marks. I open arklone again and at no point do I get the message to change the RetroArch settings to the recommended ones. If I choose the 'regenerate retroarch path units' option, it simply doesn't do it, and if I try to sync manually, it destroys my RetroPie installation. It's not the first time thatI install Arklone, I installed it on my RPI 3B+ without any problem.

ridgekuhn commented 3 months ago

if I try to sync manually, it destroys my RetroPie installation

I'm not exactly sure what you mean by "destroys", but I'm sorry to hear this. Aside from config files, Arklone is self-contained to its installation directory, and as far as I know, shouldn't be able to do something like that. (Although, rclone certainly can.)

it says that I haven't configured any rclone server

Could you confirm that your rclone.conf exists at ~/.config/rclone/rclone.conf?

If I choose the 'regenerate retroarch path units' option, it simply doesn't do it

Can you confirm that the retroarchCfg setting in your arklong.cfg contains the correct path to retroarch.cfg?

retroarchCfg = "/opt/retropie/configs/all/retroarch.cfg"

Also, Arklone's "recommended settings" simply set these values in your retroarch.cfg:

(note: this is from the readme, but I think I forgot to update it. Arklone might actually set savefile_directory and savestate_directory to "/opt/retropie/configs/all/retroarch/saves".)

savefile_directory = "~/.config/retroarch/saves"
savefiles_in_content_dir = "false"
sort_savefiles_enable = "false"
sort_savefiles_by_content_enable = "true"

savestate_directory = "~/.config/retroarch/saves"
savestates_in_content_dir = "false"
sort_savestates_enable = "false"
sort_savestates_by_content_enable = "true"

When you run Arklone on multiple Pis, your settings for savefiles_in_content_dir, sort_savefiles_enable, sort_savefiles_by_content_enable, savestates_in_content_dir, sort_savestates_enable, and sort_savestates_by_content_enable must match in each Pi's retroarch.cfg.

I check the arklone.cfg file and manually add the server name (in my case, I named it 'retropie')

Are you trying to sync the Pi Zero to your Pi 3B+? Does the Pi 3B+ sync to the cloud? I am actually not sure how well Arklone works with rclone's local sync options, if at all. It's best to sync each Pi to the cloud, so the cloud copy is your "single source of truth".

Hope that helps!

lalofwa commented 3 months ago

Could you confirm that your rclone.conf exists at ~/.config/rclone/rclone.conf

Yes it looks like this: [retropie] type = mega user = lalxxxxxxom pass = PMxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

arklone.cfg looks like this retroarchContentRoot = "~/RetroPie/roms" retroarchCfg = "/opt/retropie/configs/all/retroarch.cfg" log = "/dev/shm/arklone.log" rcloneConf = "~/.config/rclone/rclone.conf" remote = "retropie" <-- I had to manually add here

Are you trying to sync the Pi Zero to your Pi 3B+? Does the Pi 3B+ sync to the cloud? I am actually not sure how well Arklone works with rclone's local sync options, if at all. It's best to sync each Pi to the cloud, so the cloud copy is your "single source of truth".

No I used Mega to sync my files. Everything works normal on mi 3B+ but I cant make it work on Zero W

lalofwa commented 3 months ago

Also after adding the name manually, keeps saying "It looks like you have't configures any rclone..."

2 1
ridgekuhn commented 3 months ago

Looks like this is the problem:

 rcloneConf = "/.config/rclone/rclone.conf"

It should be:

rcloneConf = "~/.config/rclone/rclone.conf"
ridgekuhn commented 3 months ago

Oh wait, do u actually have that in your config, but GitHub's markdown parser is interpreting it as a ~strikeout~ in your comment?

ridgekuhn commented 3 months ago

Now that I'm thinking about it, I think rclone might not have gotten installed. If you run this command, do you get a "Command not found" error?

rclone listremotes

If so, could you share the output of this terminal command, please?

uname -m
lalofwa commented 3 months ago

Oh wait, do u actually have that in your config, but GitHub's markdown parser is interpreting it as a ~strikeout~ in your comment?

Yeah, sorry

ridgekuhn commented 3 months ago

No worries, that's my fault, I saw the strikeout and didn't question why it was there!

lalofwa commented 3 months ago

Now that I'm thinking about it, I think rclone might not have gotten installed. If you run this command, do you get a "Command not found" error?

rclone listremotes

If so, could you share the output of this terminal command, please?

uname -m

Yeah, command not found

armv61

lalofwa commented 3 months ago

pi@retropie:~ $ rclone listremotes -bash: rclone: command not found pi@retropie:~ $ uname -m armv6l

ridgekuhn commented 3 months ago

Thanks! Found the problem, rclone changed their download URLs. Run these commands to install the current version:

wget "https://downloads.rclone.org/v1.67.0/rclone-v1.67.0-linux-arm-v6.deb" -O "~/rclone-v1.67.0-linux-arm-v6.deb"

sudo dpkg --force-overwrite -i "~/rclone-v1.67.0-linux-arm-v6.deb"

rm "~/rclone-v1.67.0-linux-arm-v6.deb"
lalofwa commented 3 months ago

That did the trick!, Thank you very much. I think the error must have shown up at some point during the installation, but since I was installing from the GPI case and the screen is very small, I couldn't see it. I appreciate the time you took to answer my question; you are the best!

ridgekuhn commented 3 months ago

Glad it worked out! Please leave this issue open so I can hopefully remember to fix the install script this weekend!