Multi Switch Shutdown Script!
-
@vwgolfman You are using the "wrong" script for this. Please visit https://github.com/crcerror/ES-generic-shutdown
There is a dedicated command line option for a single GPIO button. The Retroflag script is just a small subset of the one linked above.
Edit:
Did forget, I wrote small walk-through already here: https://retropie.org.uk/forum/topic/17415/multi-switch-shutdown-script -
On resetting games with the reset button I'm getting the following error:
/home/pi/RetroPie/scripts/multi_switch.sh: line 63: kill: (####) - No Such ProcessWhere #### is the process number.
It also producses the following message on closing the process:
KilledAs it looks messy having persistant messages like these show between screens is there a clean way to hide them?
I don't want to completely prevent error messages showing as sometimes I do screw up so just these ones specifically. If it's all or nothing though I'll just have to accept that.
-
@cyperghost
Thank you so much, your coding is fantastic and I am now using your safe shutdown script successfully!Could I please ask, is there a version which monitors the shutdown button continuously rather than polling it every second or so?
-
@cyperghost I just used this script for a generic button on a zero 2 with no luck. Would anything be different about the pi zero 2?
-
-
@cyperghost Hi sweet man :v, I wanted to know if you think that by modifying the paths in your install instructions I could make your script work on batocera, since it's emulation station same as retropie, I have a generic button I want to use to save shut down, any help is appreciated
-
-
I have got this error on my Raspberry pi 3b+:
DTOVERLAY[error]: failed to open 'RetroFlag_pw_io.dtbo'
Failed to read 'RetroFlag_pw_io.dtbo'
What Can I do?
The file is installed in the correct place, in fact, I installed it with the installer and checked that everything was correct, but the dto does not load it.
-
@BlackDraGoN-0 That error is not from @cyperghost's script, the script doesn't have any references to that
.dtbo
file. -
My pins are always level=0 fsel=0 func=INPUT how can I change level 1 when I press a button?
-
@mitu I have done a clean installation of RetroPie, and I have installed the multiswitch, but every time the leds come on and it turns off. I have a Nespicase+ and a Raspberry Pi 3B+. I have also tried with the original retroflag script and the same thing happens.
-
When I install the script, the nespicase+ always turns off. My Nespicase has a Reset button that is a push button, but the Off button is one of those that stays pressed when pressed, and I have to press it again to get it out.
-
@BlackDraGoN-0 I'm not familiar with the case, but I remember you had to activate a switch in order to have the script functional - https://retroflag.com/download/NESPi_CASE+_Manual.pdf mentions this switch and I presume it has to be switched ON (default is OFF).
-
@mitu I have got the switch in ON.
-
@BlackDraGoN-0 said in Multi Switch Shutdown Script!:
Off button
You meant the "Power"-Button, or (pressed=On, unpressed=Off)?
-
@Ashpool
Exactly (pressed = on, not pressed = off), that's my button.I no longer know what to do to make the script work.
-
@BlackDraGoN-0 I had no problems with the script on my superpi and nespi+ cases, was that a fresh setup you installed the script on to? If possible (spare sd card), maybe you should check with a fresh retropie install/image and retroflags own shutdown-script.
And on @cyberghosts GIT-repo there is a newer script version 0.86 (# v0.86 Added Switch check to NESPi+ cases), but that's labeled as -testing and i don't know what the changes exactly do (and as cyberghost wasn't on the forum for over a year ...), and as the older version worked (for me) - best to on a fresh install and with retroflags script 1st and if that works on a fresh install with the multi-switch script. -
@Ashpool
This is my boot config# For more options and information see # http://rpf.io/configtxt # Some settings may impact device functionality. See link above for details # uncomment if you get no picture on HDMI for a default "safe" mode #hdmi_safe=1 # uncomment this if your display has a black border of unused pixels visible # and your display can output without overscan disable_overscan=1 # uncomment the following to adjust overscan. Use positive numbers if console # goes off screen, and negative if there is too much border #overscan_left=16 #overscan_right=16 #overscan_top=16 #overscan_bottom=16 # uncomment to force a console size. By default it will be display's size minus # overscan. #framebuffer_width=1280 #framebuffer_height=720 # uncomment if hdmi display is not detected and composite is being output hdmi_force_hotplug=1 # uncomment to force a specific HDMI mode (this will force VGA) hdmi_group=2 hdmi_mode=82 # uncomment to force a HDMI mode rather than DVI. This can make audio work in # DMT (computer monitor) modes #hdmi_drive=2 # uncomment to increase signal to HDMI, if you have interference, blanking, or # no display #config_hdmi_boost=4 # uncomment for composite PAL #sdtv_mode=2 #uncomment to overclock the arm. 700 MHz is the default. #arm_freq=800 # Uncomment some or all of these to enable the optional hardware interfaces #dtparam=i2c_arm=on #dtparam=i2s=on #dtparam=spi=on # Uncomment this to enable infrared communication. #dtoverlay=gpio-ir,gpio_pin=17 #dtoverlay=gpio-ir-tx,gpio_pin=18 # Additional overlays and parameters are documented /boot/overlays/README # Enable audio (loads snd_bcm2835) dtparam=audio=on [pi4] # Enable DRM VC4 V3D driver on top of the dispmanx display stack dtoverlay=vc4-fkms-v3d max_framebuffers=2 [all] #dtoverlay=vc4-fkms-v3d gpu_mem_256=128 gpu_mem_512=256 gpu_mem_1024=256 #overscan_scale=1 disable_splash=1 boot_delay=3
I have got a Raspberry Pi 3B +
-
This is my /etc/modules :
# /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored. uinput
-
Version 0.86 is for me nespicase+, but when I press the buttons nothing happens. Do I have to have uart active or something like that?
-
@BlackDraGoN-0 I too have a nespi+ and used scripts pre 0.86 ones without problems (maybe retroflag changed something and came up with a new revision?), have you tried a fresh install with retroflags own script? FYI cyberghost/crcerr also has, besides his multiswitch shutdown script, a fork from retroflags official one on his git-pages wich offers a more graphical readme then the one on retroflags behalve.
In previous times doing the steps which are now offered via the install.sh from the repo worked OOB, you may try out that one - but either do it on a fresh install, or make sure you uninstalled any leftovers from previous tryouts. -
@cyperghost Hi, Thank you for your great work with this script, but I have the Issue with the Raspberry Pi Zero 2 W.
I have installed you script and I have Connectet to Pin 5 (GPIO3) and GND a momentary switch. I also preformed the comamnd:raspi-gpio set PIN3 ip pu
The shut down sequenze works fine but the zero dosn't power up again.
Is this a zero related issue?raspi-gpio get
returns:
GPIO 3: level=1 fsel=0 func=INPUTBest Regards
Predator2k4
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.