Raspberry "dtoverlay=gpio-shutdown" (on/off switch) feature vanished after omv installation

Hi Reini8020,
have you already solved your problem. I´m very interested in this because I´m planning in to build my NAS with raspberry pi 4 and OMV. My old NAS is dying now. I was able to trigger the boot process and shutting it down (ACPI) by pressing a light switch paired with a relay. So I was able to do so from different locations in my house. I also would like to do so with my planned raspberry NAS.

Greetings to the beautiful town of Graz from the far north Waidhofen an der Thaya.

Hi Reini8020,
I just found this. (https://bitreporter.de/raspber…ng-fuer-den-raspberry-pi/)
It´s a ready to use hardware solution,. Maybe not what you wanted but if nothing helps this thing should help.
Greetings from WT.

Hello people

I can confirm that the gpio-shutdown (short gpio3 to 0V) works on a fresh install of lite, but vanishes after omv install.

The reason I'd like to use it is that have power supply with incoming supply fail alert which might, just might, allow the thing to shut down gracefully. At present I get a corrupted data disk on a power interruption. I think the disk goes down before the Pi.

Zitat von Reini8020

Just to close the post. In version 5.6.13-1 this option does work. With a simple push-botton the rasberry can be turned on / off.

Thank you.

Reini

Hi,

How to install a specific version of OMV (5.6.13-1) ??

I am following the common advice on installing OMV on raspberry pi: download the install file from https://github.com/OpenMediaVa…Script/raw/master/install and run it with sudo.

I have the exact same problem on raspberry-pi 4b 8GB RAM purchased just recently. I have tried this with bullseye and also buster, same behavior with both, once OMV is installed, it kills /boot/config.txt functionality, specifically the gpio-shutdown option.

This is a dealbreaker for me as I need to be absolutely certain that power is not abruptly and the gpio-shutdown option works. I have built a custom PCB with Li-Ion battery backup for this.

Thanks in advance,

Indian.

Zitat von Indian

I have tried this with bullseye and also buster, same behavior with both, once OMV is installed, it kills /boot/config.txt functionality, specifically the gpio-shutdown option.

????

The OMV script doesn't do anything on the /boot/config.txt

If the option is not there, just edit the file and add the line.

dtoverlay=gpio-shutdown,gpio_pin=3

Details:

firmware/README at master · raspberrypi/firmware (github.com)

Name:   gpio-shutdown
Info:   Initiates a shutdown when GPIO pin changes. The given GPIO pin
        is configured as an input key that generates KEY_POWER events.

        This event is handled by systemd-logind by initiating a
        shutdown. Systemd versions older than 225 need an udev rule
        enable listening to the input device:

                ACTION!="REMOVE", SUBSYSTEM=="input", KERNEL=="event*", \
                        SUBSYSTEMS=="platform", DRIVERS=="gpio-keys", \
                        ATTRS{keys}=="116", TAG+="power-switch"

        Alternatively this event can be handled also on systems without
        systemd, just by traditional SysV init daemon. KEY_POWER event
        (keycode 116) needs to be mapped to KeyboardSignal on console
        and then kb::kbrequest inittab action which is triggered by
        KeyboardSignal from console can be configured to issue system
        shutdown. Steps for this configuration are:

            Add following lines to the /etc/console-setup/remap.inc file:

                # Key Power as special keypress
                keycode 116 = KeyboardSignal

            Then add following lines to /etc/inittab file:

                # Action on special keypress (Key Power)
                kb::kbrequest:/sbin/shutdown -t1 -a -h -P now

            And finally reload configuration by calling following commands:

                # dpkg-reconfigure console-setup
                # service console-setup reload
                # init q

        This overlay only handles shutdown. After shutdown, the system
        can be powered up again by driving GPIO3 low. The default
        configuration uses GPIO3 with a pullup, so if you connect a
        button between GPIO3 and GND (pin 5 and 6 on the 40-pin header),
        you get a shutdown and power-up button. Please note that
        Raspberry Pi 1 Model B rev 1 uses GPIO1 instead of GPIO3.
Load:   dtoverlay=gpio-shutdown,<param>=<val>
Params: gpio_pin                GPIO pin to trigger on (default 3)
                                For Raspberry Pi 1 Model B rev 1 set this
                                explicitly to value 1, e.g.:

                                    dtoverlay=gpio-shutdown,gpio_pin=1

        active_low              When this is 1 (active low), a falling
                                edge generates a key down event and a
                                rising edge generates a key up event.
                                When this is 0 (active high), this is
                                reversed. The default is 1 (active low).

        gpio_pull               Desired pull-up/down state (off, down, up)
                                Default is "up".

                                Note that the default pin (GPIO3) has an
                                external pullup. Same applies for GPIO1
                                on Raspberry Pi 1 Model B rev 1.

        debounce                Specify the debounce interval in milliseconds
                                (default 100)

Zitat von Soma

????

The OMV script doesn't do anything on the /boot/config.txt

If the option is not there, just edit the file and add the line.

dtoverlay=gpio-shutdown,gpio_pin=3

Details:

firmware/README at master · raspberrypi/firmware (github.com)

Code

Name:   gpio-shutdown
Info:   Initiates a shutdown when GPIO pin changes. The given GPIO pin
        is configured as an input key that generates KEY_POWER events.

        This event is handled by systemd-logind by initiating a
        shutdown. Systemd versions older than 225 need an udev rule
        enable listening to the input device:

                ACTION!="REMOVE", SUBSYSTEM=="input", KERNEL=="event*", \
                        SUBSYSTEMS=="platform", DRIVERS=="gpio-keys", \
                        ATTRS{keys}=="116", TAG+="power-switch"

        Alternatively this event can be handled also on systems without
        systemd, just by traditional SysV init daemon. KEY_POWER event
        (keycode 116) needs to be mapped to KeyboardSignal on console
        and then kb::kbrequest inittab action which is triggered by
        KeyboardSignal from console can be configured to issue system
        shutdown. Steps for this configuration are:

            Add following lines to the /etc/console-setup/remap.inc file:

                # Key Power as special keypress
                keycode 116 = KeyboardSignal

            Then add following lines to /etc/inittab file:

                # Action on special keypress (Key Power)
                kb::kbrequest:/sbin/shutdown -t1 -a -h -P now

            And finally reload configuration by calling following commands:

                # dpkg-reconfigure console-setup
                # service console-setup reload
                # init q

        This overlay only handles shutdown. After shutdown, the system
        can be powered up again by driving GPIO3 low. The default
        configuration uses GPIO3 with a pullup, so if you connect a
        button between GPIO3 and GND (pin 5 and 6 on the 40-pin header),
        you get a shutdown and power-up button. Please note that
        Raspberry Pi 1 Model B rev 1 uses GPIO1 instead of GPIO3.
Load:   dtoverlay=gpio-shutdown,<param>=<val>
Params: gpio_pin                GPIO pin to trigger on (default 3)
                                For Raspberry Pi 1 Model B rev 1 set this
                                explicitly to value 1, e.g.:

                                    dtoverlay=gpio-shutdown,gpio_pin=1

        active_low              When this is 1 (active low), a falling
                                edge generates a key down event and a
                                rising edge generates a key up event.
                                When this is 0 (active high), this is
                                reversed. The default is 1 (active low).

        gpio_pull               Desired pull-up/down state (off, down, up)
                                Default is "up".

                                Note that the default pin (GPIO3) has an
                                external pullup. Same applies for GPIO1
                                on Raspberry Pi 1 Model B rev 1.

        debounce                Specify the debounce interval in milliseconds
                                (default 100)

Alles anzeigen

Alles anzeigen

Actually that is the strange part. Initially I thought omv install messes up /boot/config.txt. But not so. That file remains unchanged, byte for byte. But the actual functionality of gpio-shutdown does not work.

Other GPIO outputs work. I have a GPIO controlled cooling fan, which works perfectly even after installing OMV. Reading GPIO via a shell command also works. Just that the ability to trigger a shutdown when GPIO 27 goes low is lost post OMV install.

If I take out the micro SD card, zap it with buster-lite or bullseye-lite, and add the dtoverlay line in boot/config.txt, then gpio-shutdown works. I have tested this dozens of times. But install OMV and boom, gpio-shutdown does not work anymore.

Very strange.

Zitat von Indian

GPIO 27

According to what I posted above, is NOT GPIO 27, but GPIO3 to 0v (pin 5 to 6)

Zitat von Soma

According to what I posted above, is NOT GPIO 27, but GPIO3 to 0v

It is configurable. You specify the pin# thru gpio-shutdown option dtoverlay, and arrange to assert (active-low) that pin to signal shutdown. I designed my own little UPS with 2 LiIon cells and a custom designed/manufactured PCB to do this and few other things like a little LCD display, cooling fan & GPS. It all works perfectly w/o OMV.

I don't use pin #3 because it is multiplexed with I2c, which I need too. Hence pin #27 which is not in the way of anything else.

The moment I install OMV and only the gpio-shutdown part of the goodness is gone. I can live w/o the little SPI interfaced display, or the GPS. But not auto-shutdown and cooling fan.

Maybe activate the "3 Interface Options" on the raspi-config?!?

Now, either don't run OMV or get an Argon Case (the button functions work out of the box) or check the Argon script to see if you can adapt to your case.

Sorry, can't remember anything else

How do I run previous version of the install ?

If everything worked in 5.6.13-1, I would try with it and confirm / refute that it works. If it does work as reported on this forum, then it should be a simple matter to find out what changed in 5.6.14 (or any later version) and fix.

Zitat von Indian

How do I run previous version of the install ?

If everything worked in 5.6.13-1, I would try with it and confirm / refute that it works. If it does work as reported on this forum, then it should be a simple matter to find out what changed in 5.6.14 (or any later version) and fix.

I'm considering other possibility:

Not the update of OMV but the update of the kernel that breaks the GPIO.

If you can try it:

Flash a previous version of Buster and set the kernel on hold.

Then run the script for OMV and see what happens.

The script to install OMV runs automatically, and will download the latest version (AFAIK) and will also updates the kernel.

So, who knows?

If you know what to look, see the script and try to figure what can be changed to install a previous version.

The part that deals with the OMV install is this one:

installScript/install at master · OpenMediaVault-Plugin-Developers/installScript (github.com)

# install openmediavault if not installed already
omvInstall=$(dpkg -l | awk '$2 == "openmediavault" { print $1 }')
if [[ ! "${omvInstall}" == "ii" ]]; then
  echo "Installing openmediavault required packages..."
  if ! apt-get --yes --no-install-recommends install postfix; then
    echo "failed installing postfix"
    exit 2
  fi

  echo "Adding openmediavault repo and key..."
  echo "deb ${omvRepo} ${omvCodename} main" > ${omvSources}
  wget -O "${omvKey}" ${omvRepo}/archive.key
  apt-key add "${omvKey}"

  echo "Updating repos..."
  if ! apt-get update; then
    echo "failed to update apt repos."
    exit 2
  fi

  echo "Install openmediavault-keyring..."
  if ! apt-get --yes install openmediavault-keyring; then
    echo "failed to install openmediavault-keyring package."
    exit 2
  fi

  monitInstall=$(dpkg -l | awk '$2 == "monit" { print $1 }')
  if [[ ! "${monitInstall}" == "ii" ]]; then
    if ! apt-get --yes --no-install-recommends install monit; then
      echo "failed installing monit"
      exit 2
    fi
  fi

  echo "Installing openmediavault..."
  aptFlags="--yes --auto-remove --show-upgraded --allow-downgrades --allow-change-held-packages --no-install-recommends"
  cmd="apt-get ${aptFlags} install openmediavault"
  if ! ${cmd}; then
    echo "failed to install openmediavault package."
    exit 2
  fi

  omv-confdbadm populate
fi

If it was done as an apt install probably should be something like:

apt install openmediavault-5.6.13-1 -y

I'm just speculating but maybe ryecoaaron can give an input.

Zitat von Soma

I'm considering other possibility:

Not the update of OMV but the update of the kernel that breaks the GPIO.

If you can try it:

Flash a previous version of Buster and set the kernel on hold.

Then run the script for OMV and see what happens.

The script to install OMV runs automatically, and will download the latest version (AFAIK) and will also updates the kernel.

So, who knows?

If you know what to look, see the script and try to figure what can be changed to install a previous version.

The part that deals with the OMV install is this one:

installScript/install at master · OpenMediaVault-Plugin-Developers/installScript (github.com)

Spoiler anzeigen

Code

# install openmediavault if not installed already
omvInstall=$(dpkg -l | awk '$2 == "openmediavault" { print $1 }')
if [[ ! "${omvInstall}" == "ii" ]]; then
  echo "Installing openmediavault required packages..."
  if ! apt-get --yes --no-install-recommends install postfix; then
    echo "failed installing postfix"
    exit 2
  fi

  echo "Adding openmediavault repo and key..."
  echo "deb ${omvRepo} ${omvCodename} main" > ${omvSources}
  wget -O "${omvKey}" ${omvRepo}/archive.key
  apt-key add "${omvKey}"

  echo "Updating repos..."
  if ! apt-get update; then
    echo "failed to update apt repos."
    exit 2
  fi

  echo "Install openmediavault-keyring..."
  if ! apt-get --yes install openmediavault-keyring; then
    echo "failed to install openmediavault-keyring package."
    exit 2
  fi

  monitInstall=$(dpkg -l | awk '$2 == "monit" { print $1 }')
  if [[ ! "${monitInstall}" == "ii" ]]; then
    if ! apt-get --yes --no-install-recommends install monit; then
      echo "failed installing monit"
      exit 2
    fi
  fi

  echo "Installing openmediavault..."
  aptFlags="--yes --auto-remove --show-upgraded --allow-downgrades --allow-change-held-packages --no-install-recommends"
  cmd="apt-get ${aptFlags} install openmediavault"
  if ! ${cmd}; then
    echo "failed to install openmediavault package."
    exit 2
  fi

  omv-confdbadm populate
fi

Alles anzeigen

If it was done as an apt install probably should be something like:

apt install openmediavault-5.6.13-1 -y

I'm just speculating but maybe ryecoaaron can give an input.

Alles anzeigen

It is not kernel update.

I used the "legacy" buster images released by raspberrypi.com dated Dec-1 2021. Everything is good after the install, including gpio-shutdown functionality. Then installing OMV using the install script from
wget -O - https://github.com/OpenMediaVa…Script/raw/master/install | sudo bash

breaks gpio-shutdown. Same kernel before and after the OMV install thru this script. i am doubting if the plumbing of handling of the GPIO event is broken during OMV install.

Which kernel is on the legacy?

Haven't tried it yet but i'm confident that is 5.10.63

Kernel on Legacy is

uname -a
Linux rpi4b 5.10.63-v7l+ #1496 SMP Wed Dec 1 15:58:56 GMT 2021 armv7l GNU/Linux

This remains same before/after OMV install. I downloaded it from raspberrypi.com https://www.raspberrypi.com/software/operating-systems/ released on 2nd Dec after they realized the issues with Bullseye require people to have an updated buster.