sudomod

So I havent really updated my system since I built it roughly 2-3 years ago. I see the premade image on the Super AIO github hasnt been updated since either. I'd like to get updated to latest RetroPie but will that break anything with the Super AIO (battery/wifi overlay, safe shutdown, etc.)?

"It probably won't break anything" ! Make a complete backup of your current image is the best idea.. and give it a go. In theory nothing should break, there are no special drivers or anything special compiled in. The battery icon is a background service, the only exception is that the autostart script, which you can easily fix by doing:
If you get permission denied, run the above but with 'sudo ' at the start of it

Hmm. The first obstacle seems to be getting the screen to show anything. When I turn it on the yellow STATUS led is flickering so it seems to have booted and is doing SOMETHING.

I started with a new Retropie 4.5.1 image and did the following steps :
Perhaps this is no longer a valid config for raspbian stretch?

Also a quick search for stretch using a DPI display which I assume this is seems to suggest the way it was used in Jessie is different and at the last post in this thread he suggests he found a fixed but didnt explain it at ALL: https://www.raspberrypi.org/forums/view ... p?t=218522

The safe shut off seems to no work either. I can only do the force power off button combo.

Yeh maybe not follow those.. if you use the config.txt from the 'settings/config.txt' in the github repo, that should work.. safe shutdown will only work when the software is running, an image not made by me won't have the software installed yet

kite wrote: ↑

Thu Feb 06, 2020 2:01 am

Yeh maybe not follow those.. if you use the config.txt from the 'settings/config.txt' in the github repo, that should work.. safe shutdown will only work when the software is running, an image not made by me won't have the software installed yet

Awesome got the screen going. However, the OSD script appears to no longer work. This is the output when I try to test it:

you need to make the osd executable, see this readme: https://github.com/kiteretro/Super-AIO/ ... README.txt

If you follow only the "cd" commands and "chmod" it should work, the other commands set up the USB sound and auto starting of the OSD

I'm in need of doing this too. (I think Retroarch has a bug which is preventing game settings from saving.) Is there confirmation that updating works? The instructions above look a little daunting too. Is there a way to maybe streamline them a bit?

I'm surprised that there isn't more interest in doing this? The build for kite's boards is nearly 3 years old now. Surely aio owners want to update their Retropie to run the latest build?

kite wrote: ↑

Tue Feb 18, 2020 1:52 am

you need to make the osd executable, see this readme: https://github.com/kiteretro/Super-AIO/ ... README.txt

If you follow only the "cd" commands and "chmod" it should work, the other commands set up the USB sound and auto starting of the OSD

Man, I dropped the ball finishing this. I'm far to easily distracted....

Anywho, I just started performing these steps on a clean install of Retropie v4.6. Hit a roadblock again at the line "python saio-osd.py". This time with the follwing error: A quick google suggests that the python script is relying on a missing or outdated library. I skimmed the .py and dont find where the library is called. I only have cursory experience with reading python code. I know the SAIO is pretty old and i guess unsupported now but if you could let me know what I need to tweak to get thus working I'd greatly appreciate it.

Updated 3/13/2021 for Retropie 4.7.1 to add extra step to fix sound


NEVERMIND! I got it sorted.

gizmo wrote: ↑

Fri Jul 24, 2020 1:30 am

I'm in need of doing this too. (I think Retroarch has a bug which is preventing game settings from saving.) Is there confirmation that updating works? The instructions above look a little daunting too. Is there a way to maybe streamline them a bit?

I'm surprised that there isn't more interest in doing this? The build for kite's boards is nearly 3 years old now. Surely aio owners want to update their Retropie to run the latest build?

Happy to report I got this working SO FAR on the latest build of RetroPie. At this time 4.6.

Steps:

1) Flash a fresh Retropie image to your SD card and remount the SD card on your computer and open the boot folder.

2) Download the config.txt from here https://github.com/kiteretro/Super-AIO/ ... lease/saio and replace the one in the boot folder with it. That will get your screen working. You should then also be able boot retropie and see "gamepad detected" and set up your buttons in retropie.

3) Connect to wifi and enable SSH to make the rest easier.

4) Do an update of retropie in Retropie Setup and elect to update the kernel/os as well. This make take a WHILE and appear to hang. It hasn't but one step may take about 30 mins to finish up. Reboot when done.

(I did the rest via SSH)

5) run "sudo apt-get install libpng12-0" (remove quotes). The SAIO script relies upon this library but is outdated and no longer installed with retropie. So far installing it manually hasn't broken anything. Not sure if any update in the future will remove this. If the OSD/shutdown stops working probably just run this again.


6) Copy, paste and run each command:

1. git clone https://github.com/geebles/Super-AIO/
2. cd Super-AIO/release/saio
3. sudo dpkg -i python-serial_2.6-1.1_all.deb
4. sudo chmod +x ../tester/pngview
5. sudo chmod +x osd/saio-osd
6. sudo chmod +x rfkill/rfkill
7. sudo chmod +x flash/flash.sh
8. python saio-osd.py (NOTE: this tests the OSD, if you see it on screen you are almost there. CTRL-C to exit it)
9. crontab cronSAIO.txt
10. sudo cp asound.conf /etc/
11. sudo cp config.txt /boot/config.txt
12. sudo cp config-saio.txt /boot/config-saio.txt
13. sudo mv /opt/retropie/configs/all/autostart.sh /opt/retropie/configs/all/autostart_OLD.sh
14. sudo cp autostart.sh /opt/retropie/configs/all/autostart.sh
15. sudo reboot



7) To get sound workig you also need to do the following:
1. SSH into pi
2. you should be in the default pi directory. enter: sudo nano .asoundrc
3. copy and paste the following into the file then save it.
pcm.!default {
type hw
card 1
}

ctl.!default {
type hw
card 1
}

4.save and reboot

8) When back in retropie press select then open Sound Settings set Volume to 100, Audio Card to Default, Audio Device to PCM and OMX Player Device to ALSA.

You should end up with fully working sound, OSD and safe shutdown via the power switch and Mode switch shortcuts!

Edit: If you use video splashscreens with sound. You may need to do the following fix:

1) Run: cd /opt/retropie/supplementary/splashscreen
2) Run: sudo nano asplashscreen.sh
3)
find the line: omxplayer –no-osd -o both -b --layer 10000 "$line" and change to: omxplayer –no-osd -o alsa -b --layer 10000 "$line"
(the change is 'both' to 'alsa')
4) save and reboot.

Huge huge thanks for going to all the trouble of detailing that! I did an "update all installed packages" and selected 'NO' to anything regarding updating the kernal. The process threw up a few errors but completed and did seem to update Retroarch. It didn't solve my bug issue though unfortunately.

I think I'd still rather have a proper clean Retropie install so I'll be giving your guide a pop soon! Just to clarify though, Step 6 mentions following kite's instructions.. so I do the following EXACTLY, right? From the command line?

FROM A BLANK RETROPIE:
1. git clone https://github.com/geebles/Super-AIO/
2. cd Super-AIO/release/saio
3. sudo dpkg -i python-serial_2.6-1.1_all.deb
4. sudo chmod +x ../tester/pngview
5. sudo chmod +x osd/saio-osd
6. sudo chmod +x rfkill/rfkill
7. sudo chmod +x flash/flash.sh
8. python saio-osd.py #(to test)
9. crontab cronSAIO.txt
10. sudo cp asound.conf /etc/
11. sudo cp config.txt /boot/config.txt
12. sudo cp config-saio.txt /boot/config-saio.txt
13. sudo mv /opt/retropie/configs/all/autostart.sh /opt/retropie/configs/all/autostart_OLD.sh
14. sudo cp autostart.sh /opt/retropie/configs/all/autostart.sh
15. sudo reboot