Issues with Mausberry shutdown script.
-
Retropie 4.7.1
RPi 3b+
updatd to latest setup scriptNo other issues I can tell in the build. I've checked my wiring to the correct GPIO 23/24 pins on the Pi3b+ as required by the default Mausberry script setup/website.
When the Power switch is selected to "off", Retropie closes and looks like it goes into a shutdown sequence. I can't tell because I have everything discreet.
However... power remains on, screen goes all black but this is displayed in the upper left corner...
|[ 54.919926] reboot: Power down
I've even gone so far as to test CyberGhosts shutdown scripts, and I still get the same message when I shutdown.
Nothing happens unless I unplug the unit. I've never seen this issue before on my other sets I have Mausberrys in use.
What is this from and why doesn't the unit power down? Any other info, let me know.
Thanks a mil!
JR
-
@jamrom2 said in Issues with Mausberry shutdown script.:
|[ 54.919926] reboot: Power down
Enable the boot messages again - if you disabled them with the
quietoption - and see where the power off stops. -
Ok. Did that and here is the response on shutdown... I have no idea what's causing this to happen.
Stopped Dispatch Password Requests to Console Directory Watch
Stopped Forward Password Requests to Wall Directory Watch
Stopping Network Time Synchronization... Stopping Update UTMP about System Boot/Shutdown...
Stopping Load/Save Random Seed...
Stopped Load Kernel Modules.
Stopped Load/Save Random Seed.
Stopped Update UTMP about System Boot/Shutdown.
Stopped Network Time Synchronization.
Stopped Create Volatile Files and Directories. Stopped target Local File Systems.Unmounting /boot...
Unnounted /boot.Reached target Unmount All Filesystems. System Check on /dev/disk/by-partuuid/97a6378b-01.
Removed slice system-systemd\x2dfsck.slice.
Stopped target Local File Systems (Pre).
Stopped Create Static Device Nodes in /dev
Stopped Create System Users.
Stopped Remount Root and Kernel File Systems.
Stopped File System Check on Root Device. Reached target Shutdown.
Reached target Final Step.
Started Power-off.
Reached target Power-Off.
Stopping Restore / save the current clock... 59.9899221 reboot: Power downI've removed all the "OK" statements. All said "OK" until the last "Stopping Restore / save..." statement. It looks like the problem is there ..but no idea what that's in reference to.
-
I don't see anything that would stop the shutdown in the log you posted. Is the shutdown working fine without the Mauseberry connected ?
-
@mitu I tried this.. I used an older stretch build Retopie (4.6.7) and it worked without issue.
Then I tried the same new build on another machine I have with a Mausberry installed and that stopped the shutdown at the same point.
I don't think the Mausberry is the issue. Any other logs or build info I can give you? Things to test? I've had this issue since day one of building this machine with the latest Retropie build, but just figured I'd leaving it low on my punch list.
-
I don't see what RetroPie has to do with this - we don't modify the default Raspberry Pi OS on which RetroPie is built.
Try to reproduce the issue with the latest Raspberry Pi OS Lite - maybe the Mausberry switch is not compatible with it. -
@mitu makes a lot of sense. I can take this up with the support team of Mausberry and see what they say. What O/S is running with the latest image of Retropie vs the previous version that I might be able to pass on to them?
-
@jamrom2 said in Issues with Mausberry shutdown script.:
What O/S is running with the latest image of Retropie vs the previous version that I might be able to pass on to them?
RetroPie is using Raspberry Pi OS Lite - so the same version as the Raspberry Pi Foundation releases.
The 4.7 version used the image based on Linux kernel 4.19, 4.7.1 uses the image based on Linux kernel 5.4. Updating your RetroPie installation will get you the latest kernel and firmware - so you can try using the latest Raspberry PI OS image - released on Dec. 2 - https://www.raspberrypi.org/software/operating-systems/#raspberry-pi-os-32-bit. -
@mitu ok. I'll play around with this. I think it's thier script that's either missing something or not correct for the new version O/S.
I asked Cyberghost if he wouldn't mind having a look at the Mausberry script to see if there was anything noticably wrong. A long shot, but you never know. I just read everywhere that Mausberry support is non-existent. Trying to avoid that.
My systems both use stock switches that came with the original cases, so they are both standard on/off switches. Not momentary like the Pi GPIO requires to use a simple script.
Thanks for the info!
-
@mitu Hiya... two things.. .
Cyberghost found that I had an extra statement active in my \boot\config.txt file relating to a dtoverlay command (whatever that is... lol).
I just wanted to pass this on to you. It was because I had both his and the Mausberry shutdown scripts active. This build I made is for 3 different boxes I have. Two use a Mausberry the other is a MegaPi case from Retroflag. Here is the statement that caused my issue... I just turned it off "#".
dtoverlay=gpio-poweroff,gpiopin=4,active_low=1,input=1
The 2nd thing...
Happy New Year! Thanks for being the go-to-guy for so many of the issues I had this year. I really appreciate it. Have a safe and prosperous New Year!
Regards,
JR
-
@jamrom2 said in Issues with Mausberry shutdown script.:
Have a safe and prosperous New Year!
Glad you sorted it out and thank you for the nice words - Happy New Year to you too !
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.