Universal Blue•2mo ago

Gigabyte mobo sleep bug

Hello. I'm new to bazzite and linux in general. I became aware of the known issue with gigabyte motherboards waking the system from sleep immediately, and i found this script (https://github.com/DAK404/OpenSUSE-Setup-Scripts/blob/main/Scriptlets/Fixes-and-Tweaks/Fix-GigabyteDesktopSleepFix.sh ) on github that should disable the device causing the issue, but i can't seem to run it; terminal returns "failed to enable unit: unit biosWakeupWorkaround.service does not exist". can anyone offer some insight into what's preventing it from working?

GitHub

OpenSUSE-Setup-Scripts/Scriptlets/Fixes-and-Tweaks/Fix-GigabyteDesk...

A set of useful scripts that can help in setting up and maintaining OpenSUSE Tumbleweed systems - DAK404/OpenSUSE-Setup-Scripts

25 Replies

biebel•2mo ago

Have a look at the fixes from archwiki. https://wiki.archlinux.org/title/Power_management/Wakeup_triggers#Gigabyte_motherboards Which motherboard do you have?

chailinerOP•2mo ago

b550 aorus pro ax, sorry I should've mentioned that I tried the command in that section and tried to sleep and my monitors and peripherals turned off but the PC remained on. monitors wouldn't turn back on so I had to hold the power button to shut down

biebel•2mo ago

The script from opensuse also only does the echo GPP0 > /proc/acpi/wakeup thing, same as the arch wiki. Not sure why it's not creating the systemd service for you, but that's the errormessage https://wiki.archlinux.org/title/Power_management/Suspend_and_hibernate#PC_will_not_wake_from_sleep_on_A520I_and_B550I_motherboards has some more diagnosing steps for those last symptoms

CheckYourFax•2mo ago

yep that script is fine also, check what gpp0 is by just running cat /proc/acpi/wakeup it likely will tell you what sysfs node it is or disabled

chailinerOP•2mo ago

it's enabled. under sysfs node it lists pci:0000:00:01.1 also when i try to run echo GPP0 > /proc/acpi/wakeup i get permission denied. not sure how to get elevated perms for this as i'm not being prompted for my password

biebel•2mo ago

You'll need sudo. In linux guides things with $ are user # is root

CheckYourFax•2mo ago

what does it state in lspci? if its a pci bridge then its probably safe to disable wakeup if you do the wrong one, you will lock waking up at all

chailinerOP•2mo ago

how do i check this?

CheckYourFax•2mo ago

lspci sorry just without -t doesn't show the pci number check the first few numbers when running lspci and you know what is waking up the system if its just a "GPP bridge" or something, its ok to disable

chailinerOP•2mo ago

yea 00:01:1 says gpp bridge

CheckYourFax•2mo ago

it likely is the chipset* you can check this by doing lspci -v it shows more info to be fair just give a try, see if it works. make sure to test whether you can still wake the system by keyboard&mouse and by power button and then you're good and hopefully it doesn't lock the system up

chailinerOP•2mo ago

i'm not sure if the command to disable it worked properly, still shows as enabled when i run cat /proc/acpi/wakeup

CheckYourFax•2mo ago

need to enable the service after you run the script

chailinerOP•2mo ago

i couldn't get the script to run though let me try again

CheckYourFax•2mo ago

systemctl enable biosWakeupWorkaround.service you can also just do it manually run this: sudo nano /etc/systemd/system/toggle-gpp0-to-fix-wakeup.service add this:

Description="Disable GPP0 to fix suspend issue"

[Service]
ExecStart=/bin/sh -c "/bin/echo GPP0 > /proc/acpi/wakeup"

[Install]
WantedBy=multi-user.target

Description="Disable GPP0 to fix suspend issue"

[Service]
ExecStart=/bin/sh -c "/bin/echo GPP0 > /proc/acpi/wakeup"

[Install]
WantedBy=multi-user.target