Unable to put GTR Pro to sleep

sjfoong

I just received my GTR Pro. It is very good - fast and with great GPU and lots of RAM. However, I am unable to put it to sleep - it will turn off the monitor, but fan and front LED continues to be on. I have updated to the latest AMD drivers and also the Intel LAN driver. I have also updated to the latest Windows 11 cumulative update preview (26100.5074). It isn’t able to wake either from this state. Attempting to wake it results in a reboot.

Please is there any guidance on how to the GTR Pro to actually sleep and wake?

Thank you.

Beelink CS-George

sjfoong Hi there, please send us a picture of SN on the bottom of the PC

Troymills

Have you checked the BIOS settings for power management options, specifically related to S3 sleep states? Maybe something there is interfering with the process. This kind of glitch can be so frustrating when you are ready to play bloodmoney. I hope you find a solution soon!

sjfoong

Yes, I did check. It seems that for this system, Only S0 mode is supported and S3 mode is disabled due to S0 mode support. I did find a registry edit that disables S0 and S3 became available. That didn’t help as much - I managed to get it to sleep but when it woke, the fan would spin at max speed and it had to be long press power button to power off. Also the Gigabit Ethernet wired interface disappeared from the system (and from Device Manager too). Only hard power off (removing the cable), can I get back the Ethernet again.

PS C:\WINDOWS\system32> powercfg /a
The following sleep states are available on this system:
Standby (S0 Low Power Idle) Network Connected
Hibernate

The following sleep states are not available on this system:
Standby (S1)
The system firmware does not support this standby state.
This standby state is disabled when S0 low power idle is supported.

Standby (S2)
    The system firmware does not support this standby state.
    This standby state is disabled when S0 low power idle is supported.

Standby (S3)
    This standby state is **disabled** when S0 low power idle is supported.

Hybrid Sleep
    Standby (S3) is not available.
    The hypervisor does not support this standby state.

Fast Startup
    This action is disabled in the current system policy.

sjfoong

Beelink CS-George Image description

Thank you for your help. Here is the picture.

Beelink CS-George

sjfoong Hi there, the picture is not very clear. I think it is GTR9 395 , correct ?

About the Lan issue, please turn off the PC for a while, then plug it back, insert the network cable. Then go to device manager, you will have Lan driver, right click the driver, and update it . Here is the Lan driver https://url.bee-link.cn/Cp9O.

Also,currently GTR9 doesn’t support hibernation, but support sleep. It uses modern standby mode , but not S3.

sjfoong

Thank you for your advice.

Yes, this is GTR9 395. I updated the LAN driver (version 30.4) but unfortunately still unable to put the PC to S0 sleep. It will try (monitor turns off) but fan and LED continue to be on. Also, the GTR395 cannot be woken up successful. It will “wake” with the fan at max speed continously but does not wake. A full power down is required. The power cable needs to be unplugged as well or the LAN will be disabled on boot.

Beelink CS-George

Hello! Thank you very much for your patience as we worked to troubleshoot the sleep and wake-up issues with your GTR9 395. We apologize for the inconvenience this has caused to your usage. To help you better understand and use your device, we’d like to clarify the current function support of your unit:
Based on the hardware and system design of the GTR9 395, it currently does not support waking up from “Modern Standby” (also known as S0 mode, which you previously referenced). This is why when you attempted to put the device into S0 sleep, you encountered issues like “fans/LEDs remaining on” and “failure to wake up normally.” This is not a device defect or a setup error, but rather a limitation of the current model’s function support.
However, you can rest assured that the wake-up function works normally when the device is in the following states. You can choose the appropriate option based on your usage scenario:
S4 (Hibernation) State: If you need to step away temporarily while preserving your current work, you can use the “Hibernation” mode (you will need to enable this option in the system first). Later, you can wake up the device normally using the power button, and there will be no issues with abnormal fan speeds or LAN port malfunctions.
S5 (Shutdown) State: After the device is fully shut down, you can start and wake it up normally by pressing the power button.
Power Cycle (Shutdown + Reconnect Power) State: If you previously had to unplug the power cable due to wake-up issues, you can restart the device by reconnecting the power cable and pressing the power button. The device will wake up normally, and the LAN port will resume functioning (the LAN port disable issue you encountered earlier was mostly a temporary system cache problem caused by abnormal wake-up, which is automatically cleared after a power cycle).
Regarding the “max fan speed after wake-up” and “LAN port disable” issues you experienced earlier, they essentially stem from a temporary mismatch between the system and hardware power management when the device enters S0 standby. Currently, these issues can be avoided by not using S0 sleep mode and instead choosing Hibernation or Shutdown.
We will continue to optimize power management through future system firmware updates. If an upgrade plan that supports wake-up from S0 mode becomes available, we will notify you via official channels as soon as possible.
If you still encounter problems with wake-up when using Hibernation/Shutdown mode, or if you have other operational questions, please feel free to contact us at any time—we will continue to assist you!

jotapesse

Beelink CS-George I can confirm I experience the exact same issue on my GTR 9 Pro unit under NixOS Linux (kernel 6.17.1): it can enter Sleep (S0) state ok and wakes up from it but the following fan curve profile gets a much higher PWM rpm level making it too loud.

❌ However, as per your suggesttion, alternatively I did try to use the Hibernation (S4) state but it doesn’t seem to be working well at all. Whenever it wakes up I can notice that it previously did an unclean shutdown/hibernation stage and the boot filesystem check founds several orphaned inodes and it is required to recover the journal to clear them, every time. Not good!

out 14 16:27:43 beelink-gtr9pro stage-1-init: [Tue Oct 14 15:27:42 UTC 2025] fsck (busybox 1.36.1)
out 14 16:27:43 beelink-gtr9pro stage-1-init: [Tue Oct 14 15:27:42 UTC 2025] [fsck.ext4 (1) -- /mnt-root/] fsck.ext4 -a /dev/disk/by-uuid/69c4a952-bf32-4988-8377-db9368e748c3
out 14 16:27:43 beelink-gtr9pro stage-1-init: [Tue Oct 14 15:27:42 UTC 2025] /dev/disk/by-uuid/69c4a952-bf32-4988-8377-db9368e748c3: recovering journal
out 14 16:27:43 beelink-gtr9pro stage-1-init: [Tue Oct 14 15:27:42 UTC 2025] /dev/disk/by-uuid/69c4a952-bf32-4988-8377-db9368e748c3: Clearing orphaned inode 24544606 (uid=1000, gid=100, mode=0100644, size=16875624)
out 14 16:27:43 beelink-gtr9pro stage-1-init: [Tue Oct 14 15:27:42 UTC 2025] /dev/disk/by-uuid/69c4a952-bf32-4988-8377-db9368e748c3: Clearing orphaned inode 24554839 (uid=1000, gid=100, mode=0100644, size=840196)
out 14 16:27:43 beelink-gtr9pro stage-1-init: [Tue Oct 14 15:27:42 UTC 2025] /dev/disk/by-uuid/69c4a952-bf32-4988-8377-db9368e748c3: Clearing orphaned inode 75104325 (uid=1000, gid=100, mode=0100600, size=0)
out 14 16:27:43 beelink-gtr9pro stage-1-init: [Tue Oct 14 15:27:42 UTC 2025] /dev/disk/by-uuid/69c4a952-bf32-4988-8377-db9368e748c3: Clearing orphaned inode 75105109 (uid=1000, gid=100, mode=0100600, size=0)
out 14 16:27:43 beelink-gtr9pro stage-1-init: [Tue Oct 14 15:27:42 UTC 2025] /dev/disk/by-uuid/69c4a952-bf32-4988-8377-db9368e748c3: Clearing orphaned inode 24514507 (uid=1000, gid=100, mode=0100644, size=16875624)
out 14 16:27:43 beelink-gtr9pro stage-1-init: [Tue Oct 14 15:27:42 UTC 2025] /dev/disk/by-uuid/69c4a952-bf32-4988-8377-db9368e748c3: Clearing orphaned inode 75104327 (uid=1000, gid=100, mode=0100600, size=0)
out 14 16:27:43 beelink-gtr9pro stage-1-init: [Tue Oct 14 15:27:42 UTC 2025] /dev/disk/by-uuid/69c4a952-bf32-4988-8377-db9368e748c3: Clearing orphaned inode 75104733 (uid=1000, gid=100, mode=0100600, size=0)
out 14 16:27:43 beelink-gtr9pro stage-1-init: [Tue Oct 14 15:27:42 UTC 2025] /dev/disk/by-uuid/69c4a952-bf32-4988-8377-db9368e748c3: Clearing orphaned inode 75104836 (uid=1000, gid=100, mode=0100600, size=0)
out 14 16:27:43 beelink-gtr9pro stage-1-init: [Tue Oct 14 15:27:42 UTC 2025] /dev/disk/by-uuid/69c4a952-bf32-4988-8377-db9368e748c3: Clearing orphaned inode 75104840 (uid=1000, gid=100, mode=0100600, size=648854)
out 14 16:27:43 beelink-gtr9pro stage-1-init: [Tue Oct 14 15:27:42 UTC 2025] /dev/disk/by-uuid/69c4a952-bf32-4988-8377-db9368e748c3: Clearing orphaned inode 75105075 (uid=1000, gid=100, mode=0100600, size=0)
out 14 16:27:43 beelink-gtr9pro stage-1-init: [Tue Oct 14 15:27:42 UTC 2025] /dev/disk/by-uuid/69c4a952-bf32-4988-8377-db9368e748c3: Clearing orphaned inode 75104310 (uid=1000, gid=100, mode=0100600, size=1248)
out 14 16:27:43 beelink-gtr9pro stage-1-init: [Tue Oct 14 15:27:42 UTC 2025] /dev/disk/by-uuid/69c4a952-bf32-4988-8377-db9368e748c3: Clearing orphaned inode 75104312 (uid=1000, gid=100, mode=0100600, size=5127)
out 14 16:27:43 beelink-gtr9pro stage-1-init: [Tue Oct 14 15:27:42 UTC 2025] /dev/disk/by-uuid/69c4a952-bf32-4988-8377-db9368e748c3: clean, 2589336/122028032 files, 145343805/488111247 blocks

Attached the full system logs with entering the Hibernate (S4) state and the following wake up boot from it for your analysis:

beelink-gtr9pro-hibernation-fs-error.zip

41kB

We will continue to optimize power management through future system firmware updates. If an upgrade plan that supports wake-up from S0 mode becomes available, we will notify you via official channels as soon as possible.
If you still encounter problems with wake-up when using Hibernation/Shutdown mode, or if you have other operational questions, please feel free to contact us at any time—we will continue to assist you!

Could we please have an updated BIOS/UEFI fully supporting both Sleep (S0) and the Hibernatation (S4) states in a near future?