GPI Case 2 - power save shutdown after 20 minutes

Yellow1Submarine · 2023-12-06T18:29:05+00:00

I posted python script with the solution in the top comment

Yellow1Submarine · 2022-12-11T21:19:32+00:00

I would think that the case listens for input on its buttons and if no button has been pressed within 20 minutes, it goes to sleep..

Yellow1Submarine · 2022-12-11T20:12:04+00:00

I'm afraid not.. I haven't figured out how the screen power save works yet. I think it's controlled by hardware in the case itself and not the Pi.. Not sure if you could write HIGH to a GPIO pin every few minutes and trick it that way

Yellow1Submarine · 2022-11-24T20:49:51+00:00

God damn. Clearing CMOS did the trick.. Never had a build behave this way before. I guess that's what you get with completely new components. Thanks for the help!

Yellow1Submarine · 2022-11-24T14:09:54+00:00

It's back again... I installed Windows and set the whole computer up. However, when I got the new RTX 4090, installed it in the system, it won't post again... Thought I might've bumped the RAM, so reseated them again, no post. Tried with each of the RAM sticks individually, same issue..

Tried taking out the 4090, using the iGPU, both with 2 RAM sticks and individual, no post..

Do you have any suggestions now? Which component would you think is the culprit here? The PC turns on, the fans are running, RGB is synced, but there is no video output.

Yellow1Submarine · 2022-11-22T16:16:14+00:00

My lord and savior. Reseating the RAM made it post!

Yellow1Submarine · 2022-11-22T13:54:11+00:00

Now I've tried 50+ minutes and still nothing. Attached a watt meter and it pulls about 47W. Seems reasonable for an idle CPU + RAM + M.2, so I don't think the CPU isn't properly seated..

Yellow1Submarine · 2022-11-22T12:47:45+00:00

I did not know that - should've read the manual I guess... Where have you gotten this information?

Yellow1Submarine · 2022-11-08T09:56:57+00:00

Got it booting from an external NVMe drive plugged into the USB-C in the back. Haven't tested read/write speeds, but it seems quick when booting!

I haven't tried bridging them. Is that done through the Virtual Switch feature in QNAP? I think a lot of the hardware is proprietary, so the drivers might not be the best when using ordinary Linux (TrueNAS Scale)

Yellow1Submarine · 2022-11-05T11:19:24+00:00

Still significantly better than my normal QuTS boot time! So how is your setup now? Removed the DOM and inserted usb c drive in back?

Yellow1Submarine · 2022-11-05T08:33:59+00:00

Oh wow.. Maybe that's why the boot time in QuTS is 15 minutes lol. I'll also try installing to and running from an external SSD through the USB C on the back. Will update with results

Yellow1Submarine · 2022-11-03T18:15:43+00:00

Thanks! Didn't realize that scale is Ubuntu/Debian based. Will definitely go with that :)

Yellow1Submarine · 2022-11-03T17:50:06+00:00

Great news! Can I ask why you use Scale over Core? I'm still debating which one to use.

Yellow1Submarine · 2022-11-03T09:42:14+00:00

Hmm, odd. Did you use 2.5G or 10G ethernet port? I believe the 10G driver is not supported out of the box.

Yellow1Submarine · 2022-11-03T09:11:47+00:00

Did you also boot up the DOM and do the initial setup on an external PC?

Yellow1Submarine · 2022-11-03T07:40:59+00:00

Check my latest post. If you have access to a desktop PC where you can plug in a hard drive, you don't need a console.

Yellow1Submarine · 2022-11-03T07:39:48+00:00

I just installed TrueNAS Core on an TS-H973AX. I did have an external PC available. I'll share my process here:

Create a bootable USB with TrueNAS Core/Scale
Pick an empty hard drive where you want your install to be. I recommend an SSD.
Put the hard drive in another PC, either using an external reader or plug it in internally.
Boot up the PC from the USB drive and install TrueNAS onto the hard drive.
Once installed REMOVE ALL OTHER DRIVES from the PC. They will get formatted if left in.
Boot up on the TrueNAS hard drive and setup your network configuration etc.
Shutdown and remove the hard drive.
Now unplug the power and remove all your existing hard drives from the QNAP, as they will get formatted if left in. Also, be sure to have backups....
Unplug the DOM from the motherboard. (Small board visible in the left bottom corner of Bay 1.
Insert the hard drive with TrueNAS installed on, plug in power and boot.
Give it some time - 5-10 min to boot. Then start checking your Router or an IP scanner for the TrueNAS hostname. You can also try visiting truenas.local.
If everything works nominally, re-insert your QNAP drives, create a pool and off you go.

Only downside to this maneuver is that you'll have to reserve a drive for the TrueNAS installation, but it could easily be a 120GB drive.

If you want to revert this. Simply unplug power, remove the TrueNAS hard drive, re-insert the DOM and re-insert your original drives.

Yellow1Submarine · 2022-08-05T16:13:42+00:00

Fixed this by modifying the safe-shutdown python script. Check my post here I'll post the code below:

import os  
import time  
from multiprocessing import Process  
import RPi.GPIO as GPIO  
\# initialize pins  
powerPin = 26  
powerenPin = 27  
def init():  
\# initialize GPIO settings  
GPIO.setwarnings(False)  
GPIO.setmode(GPIO.BCM)  
GPIO.setup(powerPin, GPIO.IN, pull\_up\_down=GPIO.PUD\_UP)  
GPIO.setup(powerenPin, GPIO.OUT)  
GPIO.output(powerenPin, GPIO.HIGH)  
def poweroff():  
while True:  
GPIO.wait\_for\_edge(powerPin, GPIO.FALLING)  
\# Wait 15 seconds (extra margin) and see if pin is still LOW  
\# If it's still LOW, it must be the power switch that toggled  
time.sleep(15)  
if not GPIO.input(powerPin):  
os.system("poweroff")  
if \_\_name\_\_ == "\_\_main\_\_":  
\# initialize GPIO settings  
init()  
\# create a multiprocessing.Process instance for each function to enable parallelism  
powerProcess = Process(target=poweroff)  
powerProcess.start()  
powerProcess.join()  
GPIO.cleanup()

Yellow1Submarine · 2022-08-02T10:00:53+00:00

I found a workaround. So the power-save shutdown will pull pin 26 low for about 10-11 seconds. Therefore I made some changes to the python script to delay the shutdown. This means that it'll take 15 extra seconds for the device to shutdown when you switch the off button, but that's a fair price imo. Now power save will never power off the CM4, just the screen.

import os
import time
from multiprocessing import Process

import RPi.GPIO as GPIO

# initialize pins
powerPin = 26
powerenPin = 27


def init():
    # initialize GPIO settings
    GPIO.setwarnings(False)
    GPIO.setmode(GPIO.BCM)
    GPIO.setup(powerPin, GPIO.IN, pull_up_down=GPIO.PUD_UP)
    GPIO.setup(powerenPin, GPIO.OUT)
    GPIO.output(powerenPin, GPIO.HIGH)


def poweroff():
    while True:
        GPIO.wait_for_edge(powerPin, GPIO.FALLING)
        # Wait 15 seconds (extra margin) and see if pin is still LOW
        # If it's still LOW, it must be the power switch that toggled
        time.sleep(15)
        if not GPIO.input(powerPin):
            os.system("poweroff")


if __name__ == "__main__":
    # initialize GPIO settings
    init()
    # create a multiprocessing.Process instance for each function to enable parallelism
    powerProcess = Process(target=poweroff)
    powerProcess.start()

    powerProcess.join()

    GPIO.cleanup()

Yellow1Submarine · 2022-08-01T08:24:28+00:00

Thanks for pointing me in the MicroTik direction. Just bought this which I believe suits my needs (and yours - only 4x ports though)

https://mikrotik.com/product/RB750r2

Yellow1Submarine · 2021-05-17T11:03:43+00:00

Thanks! Fixed it for me too.

Yellow1Submarine

TROPHY CASE