Multi Switch Shutdown Script!

Efriim

@cyperghost
Thanks. I got the rc.local to work again, I left one of these ">" when I deleted /dev/null.

When I made reicast from source with /dev/null added to the rc.local I didn't notice any build errors, though when I ran reicast.sh it did give me an error about /dev/null and wouldn't work. I recompiled it and it is not working still. So I guess I was dumb and it had not to do with that.

I don't know what is up with reicast, the controller used to work without ever setting it up, and then it stopped and the joyconfig didn't work and now the emulator wont even start.

Efriim

@cyperghost
Sorry for blaming you. It looked to me that way but I didn't think. They were concatenated in my head as I went from that to this and I apologize.

The reicast binary installation still works, maybe building has trouble with my environment or maybe it is just broke. The PS3 controller needed to be removed from the bluetooth and resynced because of the alternative driver, it is working again. And now I just might try to add the > /dev/null 2>&1 for the third time.

On top of that my powersupply was halfway falling out of the surge protector, and I couldn't figure out why I was getting low voltage errors, and I got experimental settings going on with 667 sdram_freq. And I couldn't even think of all the things that can't go wrong with /dev/null.

Yes the Reicast source is broken and the binary is somewhat broken, there is the older binary in the "working dreamcast games" thread somewhere and I'm using that now. The updated binary works for a while and then crashes on the second round. The errors are a gl get error 0x500 on start and about 15 OMX buffer underruns, which existed with the old version and persist if using "oss"

I thought about creating a new thread, it will probably get fixed eventually. Or is it more sensible to add to the github?

cyperghost

@Efriim said in Multi Switch Shutdown Script!:

Sorry for blaming you. It looked to me that way but I didn't think. They were concatenated in my head as I went from that to this and I apologize.

There is no need for an apologize, I never felt offended. But nice you sorted this out.

Maybe you can give feedback how we can get rid off some error messages.

Ranma

Hi, hope I'm OK asking this here. My Google-fu has failed me, and searching has proved complicated.

I'm using the Mega-Pi case with your shutdown script and it works brilliantly. However I'd really like to hide the console text on shutdown for cosmetic reasons. I understand that sometimes things go wrong and output is needed when this happens, but I have a backup image and do not intend updating my system. I feel like I've finished my project now and would like to wrap it up with the addition.

I did find a comment somewhere that suggested to add >/dev/null 2>&1 to /etc/profile.d/10-retropie.sh. I did this and it removed the "terminated 671" line, but the console prompt remains. This is pretty much what displays before shutting down - alt text

I'd like it to simply go to a black screen if possible before shutting off. If you can help that would be very much appreciated. many thanks.!

lostless

@Ranma you need to edit the cmdline.txt file in the /boot directory.
I use this for all my pi projects and it hides all text during bootup and shutdown.

dwc_otg.lpm_enable=0 console=serial0,115200 console=tty3 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait usbhid.quirks=0x0079:0x1801:0x40 quiet loglevel=3 consoleblank=0 plymouth.enable=0 quiet logo.nologo

put it in all as one line.

Ranma

@lostless Hi thanks for replying. I've already got all that in my cmdline.txt file. I'd already followed a guide to silence the Pi during boot and shutdown, but it doesn't completely work. If I shutdown Retropie via the menu, it's completely quiet, but if I use the button on the Mega-Pi I get the console as above.

cyperghost

@Ranma you can try to edit $HOME/.bashrc and play around with it a bit.
The reason for showing the terminal is that the multi_switch script terminates ES and you will be set back to terminal. Maybe it helps to just add a clear command at the end of .bashrc

Ranma

@cyperghost Thanks so much for replying. Could I ask, what would be the best way to do this? I can find a number of commands on the internet but I'm not sure of the best one to try. I've been using Linux for some time but never had to edit ./bashrc at any time in the past so my knowledge is non-existent I'm afraid.

cyperghost

@Ranma To be true I have not a real clue about this topic, too. I never ran RetroPie as complete hidden software.
Best way to accomplish this task is to use nano $HOME/.bashrc
then add clear as last command. This will likely reduce your screen to just the prompt. Maybe @mitu can tell how to redirect the complete terminal tty1 to tty3 or so ;)

The clear command gots the advantage that it does not break anything on your current setup. So I consider it as ("breakfail"-)save solution.

Ranma

@cyperghost Excellent, thanks for replying. I added a simple clear at the end of the file and you're right - there's just the login prompt onscreen now. If there's a way to hide that too, that would be even better. Many thanks for your help. :-)

mrnebu

@cyperghost hello, i use the nespi+ case, 3b+ but no retropie. the scripts i found so far only work with emulationstation but not if you run console. could you add shutdown now for power and reboot for reset with the led? i tried myself but too much stuff going on in the nespi case for me to finish it within a year and i dont want to mess up your script.

would it be possible to add a function in case shutdown is stuck cause no es is running? it could work down other shutdown / reboot options and your script your get even more universal?

cyperghost

@mrnebu said in Multi Switch Shutdown Script!:

would it be possible to add a function in case shutdown is stuck cause no es is running?

That's already possible within the script. For the NESPi+ you see the lines


    # Initiate Shutdown per ES
    es_action --ES-CLOSEEMU
    es_action --ES-POWEROFF

    # If ES isn't running use regular shutoff
sudo poweroff

So indeed if ES is not running it already uses the regular poweroff. On the other hand you can use this script to read status of ES or running emulators and can then decide on your own what to do. So I think it is as flexible as you descripe and will cover a lot of usescases if you know how to use. So I made created a usecase for python here and also RetroFlag mentioned the script.

Rion

@Ranma I have been wondering about that to. @mitu Do you have any taughts, ideas?

mitu

@Rion said in Multi Switch Shutdown Script!:

taughts

The early bird catches the ... something.

Now, if you want the prompt to disappear and you already modified the .bashrc file, just add as last lines of the file:

export PS1=""
tput civis

and then logout.

Rion

@mitu Thank you Mr Bash Shell Wizard!

Ranma

@mitu I'll add my love here too. This works! Awesome! Thanks so much for replying.

You always know the answer @mitu

Superstar!

janderclander14

I've modified the python script from this post, which calls the Multiswitch script, to add several reset behaviors with generic buttons connected to the GPIO.

Assuming two buttons, the behavior is as follows:

One button (connected to GPIO 3) acts as shutdown (and power up)
The other button resets the system. One short press, quits the current emulator or restarts emulationstation. One long press (3 sec) restarts the system.

I attach here the code just in case someone finds it useful (it assumes multi_switch.sh is in /home/pi). You may add this as a python call to /opt/retropie/configs/all/autostart.sh

#!/usr/bin/env python3
from gpiozero import Button, LED
import os 
from signal import pause
import subprocess
import time

powerPin = 3 
resetPin = 2 

resetMinSeconds = 2

#functions that handle button events
def when_pressed():
 output = int(subprocess.check_output(['/home/pi/multi_switch.sh', '--es-pid']))
 
 if output:
     os.system("/home/pi/multi_switch.sh --es-poweroff")
 else:
     os.system("sudo shutdown -h now")

def reboot():
 start_time=time.time()
 diff=0

 while rebootBtn.is_active and (diff < resetMinSeconds):
     now_time=time.time()
     diff=-start_time+now_time

 output = int(subprocess.check_output(['/home/pi/multi_switch.sh', '--es-pid']))
 output_rc = int(subprocess.check_output(['/home/pi/multi_switch.sh', '--rc-pid']))
 if (diff > resetMinSeconds):
     if output:
         os.system("/home/pi/multi_switch.sh --es-reboot")
     else:
         os.system("sudo reboot")
 else:
     if output_rc:
         os.system("/home/pi/multi_switch.sh --closeemu")
     elif output:
         os.system("/home/pi/multi_switch.sh --es-restart")
     else:
         os.system("sudo reboot")
 
btn = Button(powerPin)
rebootBtn = Button(resetPin)
rebootBtn.when_pressed = reboot 
btn.when_pressed = when_pressed
pause()

cyperghost

@janderclander14 Hehe ;) Nicely done

cyperghost

@janderclander14 I've done some changes to the python script for some other system. To get rid of the pathes I added

#get script directory
scriptDir = os.path.dirname(os.path.realpath(__file__))

So the directory from the python script is catched. Assuming the python and the bash script are stored in the same directory we can use....

os.chdir(scriptDir)
..
..
     elif output:
         os.system("./multi_switch.sh --es-restart")

I was fixed to to /opt/RetroFlag because RetroFlag use as default in the installer and so I use this path to overwrite their script. But congrats you are the first one who activly uses the provided output to create a new shutdown script. Such it was intended to do ;)

janderclander14

@cyperghost Certainly, using relative directories is always better. And thanks to you for the script! It just had all the functionalities one would need.