Using the default BIOS settings with Linux kernel 6.16.5-1-MANJARO (same for Fedora or Ubuntu Linux with kernel version 6.14), the dmesg output shows the below errors: journalctl | grep “ACPI BIOS Error” Sep 07 15:13:07 bee kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SBRG.EC0], AE_NOT_FOUND (20250404/dswload2-162) Sep 07 15:23:23 bee kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SBRG.EC0], AE_NOT_FOUND (20250404/dswload2-162) Sep 07 15:36:16 bee kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SBRG.ECOK], AE_NOT_FOUND (20250404/psargs-332) Sep 07 15:36:16 bee kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SBRG.EC0.GPO3], AE_NOT_FOUND (20250404/psargs-332) Could you please release a new BIOS version with the ACPI tables fixed for that great mini-PC?

mss Please provide a photo of the SN code located on the bottom of your machine and a screenshot of your machine’s BIOS main page so we can provide you with the correct link and tutorial.

Thank you for your prompt response! Here are the requested images: https://photos.app.goo.gl/3LmLGnevoHbkAvxs5 Kind regards, Marc

mss Thank you for your reply. Regarding your inquiry, I have consulted our R&D team and will keep you informed of any updates.

Some additional information: the errors show when trying to suspend the PC, issuing the systemctl suspend command. The suspension will fail, apparently due to the wireless NIC which is no longer working after issuing the above command. Rebooting or powering off the PC won’t help to get the wireless NIC working again. I have to cut the power from the PC for a couple of seconds. Only then everything returns back to normal. According to the kernel log, this must be related to the ACPI errors. I.e. due to the BIOS ACPI errors, the OS can’t put the wireless NIC into the proper sleep state and that’s why it won’t come back unless I cut the power from the PC. What is also interesting is that the moment I issue the systemctl suspend command, the fan starts to run at maximum speed. It’s easy to reproduce this on any recent Linux distribution. I tried Manjaro, Ubuntu and Fedora. They all behaved the same.

mss Thank you for the additional information. I have already informed our R&D team. They will conduct some tests. Thank you for your patience and for waiting.

mss Here is the link to the solution: https://url.bee-link.cn/LPoK

Thank you for the link. The linked document refers to how to enable Wake-on-LAN on the NIC. That’s unrelated to the BIOS problem that I’ve outlined in the first post. The kernel messages mean that the BIOS has a faulty/incomplete ACPI table. The fix will require a new BIOS version with an updated ACPI table. Please tell your R&D team to install Linux and then run the systemctl suspend command. You will see those errors in the dmesg output plus the following kernel panics, preventing the PC from going to sleep: Sep 10 21:54:17 bee kernel: Timeout waiting for hardware access (CSR_GP_CNTRL 0xffffffff) Sep 10 21:54:17 bee kernel: WARNING: CPU: 15 PID: 352 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2448 __iwl_trans_pcie_grab_nic_access+0x15c/0x170 [> Sep 10 21:54:17 bee kernel: Modules linked in: snd_seq_dummy rfcomm snd_hrtimer snd_seq ccm cmac algif_hash algif_skcipher af_alg bnep vfat fat snd_usb_audi> Sep 10 21:54:17 bee kernel: snd_rn_pci_acp3x polyval_clmulni snd_pcm ghash_clmulni_intel cfg80211 sha512_ssse3 sp5100_tco snd_acp_config sha1_ssse3 snd_tim> Sep 10 21:54:17 bee kernel: CPU: 15 UID: 0 PID: 352 Comm: kworker/u97:6 Not tainted 6.16.5-1-MANJARO #1 PREEMPT(full) d3b2b3e5b7f9926d152eb98481f4a8a1d1b46> Sep 10 21:54:17 bee kernel: Hardware name: AZW SER9/SER9, BIOS SER9T402 05/09/2025 Sep 10 21:54:17 bee kernel: Workqueue: async async_run_entry_fn Sep 10 21:54:17 bee kernel: RIP: 0010:__iwl_trans_pcie_grab_nic_access+0x15c/0x170 [iwlwifi] Sep 10 21:54:17 bee kernel: Code: ff ff be 03 00 00 00 48 89 df e8 2f fd ff ff eb de 89 c6 48 c7 c7 30 6e 01 c2 89 44 24 04 c6 05 10 de be 00 01 e8 84 b5 37> Sep 10 21:54:17 bee kernel: RSP: 0018:ffffd4b14198bc98 EFLAGS: 00010246 Sep 10 21:54:17 bee kernel: RAX: 0000000000000000 RBX: ffff8e77b6180028 RCX: 0000000000000027 Sep 10 21:54:17 bee kernel: RDX: ffff8e85c1fdcfc8 RSI: 0000000000000001 RDI: ffff8e85c1fdcfc0 Sep 10 21:54:17 bee kernel: RBP: 0000000000000001 R08: 0000000000000000 R09: 00000000ffffdfff Sep 10 21:54:17 bee kernel: R10: ffffffff96588880 R11: ffffd4b14198ba68 R12: 0000000000000000 Sep 10 21:54:17 bee kernel: R13: 0000000000000000 R14: 0000000000000008 R15: 0000000000000011 Sep 10 21:54:17 bee kernel: FS: 0000000000000000(0000) GS:ffff8e862badb000(0000) knlGS:0000000000000000 Sep 10 21:54:17 bee kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 10 21:54:17 bee kernel: CR2: 00007fbb8fcb83c0 CR3: 00000009a3224000 CR4: 0000000000f50ef0 Sep 10 21:54:17 bee kernel: PKRU: 55555554 Sep 10 21:54:17 bee kernel: Call Trace: Sep 10 21:54:17 bee kernel: <TASK> Sep 10 21:54:17 bee kernel: iwl_trans_pcie_grab_nic_access+0x1f/0x50 [iwlwifi 7df180072dd378e074c6c83e27dbdfa6238a0798] Sep 10 21:54:17 bee kernel: iwl_write_prph_delay+0x1f/0x60 [iwlwifi 7df180072dd378e074c6c83e27dbdfa6238a0798] Sep 10 21:54:17 bee kernel: iwl_pcie_rx_stop+0x2f/0xc0 [iwlwifi 7df180072dd378e074c6c83e27dbdfa6238a0798] Sep 10 21:54:17 bee kernel: iwl_trans_pcie_gen2_stop_device+0x39b/0x3c0 [iwlwifi 7df180072dd378e074c6c83e27dbdfa6238a0798] Sep 10 21:54:17 bee kernel: iwl_trans_stop_device+0x3e/0xd0 [iwlwifi 7df180072dd378e074c6c83e27dbdfa6238a0798] Sep 10 21:54:17 bee kernel: ? iwl_fw_dbg_stop_sync+0x25/0x50 [iwlwifi 7df180072dd378e074c6c83e27dbdfa6238a0798] Sep 10 21:54:17 bee kernel: iwl_op_mode_mvm_device_powered_off+0x64/0x90 [iwlmvm 09b327753ce6e8c51d7638b68bba32c8e173ee8b] Sep 10 21:54:17 bee kernel: _iwl_pci_resume.isra.0+0x9c/0x1b0 [iwlwifi 7df180072dd378e074c6c83e27dbdfa6238a0798] Sep 10 21:54:17 bee kernel: ? __pfx_pci_pm_resume+0x10/0x10 Sep 10 21:54:17 bee kernel: iwl_pci_resume+0x10/0x20 [iwlwifi 7df180072dd378e074c6c83e27dbdfa6238a0798] Sep 10 21:54:17 bee kernel: dpm_run_callback+0x47/0x150 Sep 10 21:54:17 bee kernel: device_resume+0x183/0x280 Sep 10 21:54:17 bee kernel: async_resume+0x21/0x30 Sep 10 21:54:17 bee kernel: async_run_entry_fn+0x33/0x140 Sep 10 21:54:17 bee kernel: process_one_work+0x190/0x350 Sep 10 21:54:17 bee kernel: worker_thread+0x2d7/0x410 Sep 10 21:54:17 bee kernel: ? __pfx_worker_thread+0x10/0x10 Sep 10 21:54:17 bee kernel: kthread+0xf9/0x240 Sep 10 21:54:17 bee kernel: ? __pfx_kthread+0x10/0x10 Sep 10 21:54:17 bee kernel: ? __pfx_kthread+0x10/0x10 Sep 10 21:54:17 bee kernel: ret_from_fork+0x197/0x1d0 Sep 10 21:54:17 bee kernel: ? __pfx_kthread+0x10/0x10 Sep 10 21:54:17 bee kernel: ret_from_fork_asm+0x1a/0x30 Sep 10 21:54:17 bee kernel: </TASK> Sep 10 21:54:17 bee kernel: ---[ end trace 0000000000000000 ]--- Sep 10 21:54:17 bee kernel: ------------[ cut here ]------------ Sep 10 21:54:17 bee kernel: Hardware became unavailable upon resume. This could be a software issue prior to suspend or a hardware issue. Sep 10 21:54:17 bee kernel: WARNING: CPU: 2 PID: 352 at net/mac80211/util.c:1818 ieee80211_reconfig+0x9a/0x15e0 [mac80211] Sep 10 21:54:17 bee kernel: Modules linked in: snd_seq_dummy rfcomm snd_hrtimer snd_seq ccm cmac algif_hash algif_skcipher af_alg bnep vfat fat snd_usb_audio mousedev joydev snd_usbmidi_li> Sep 10 21:54:17 bee kernel: snd_rn_pci_acp3x polyval_clmulni snd_pcm ghash_clmulni_intel cfg80211 sha512_ssse3 sp5100_tco snd_acp_config sha1_ssse3 snd_timer libphy psmouse amdxdna thunde> Sep 10 21:54:17 bee kernel: CPU: 2 UID: 0 PID: 352 Comm: kworker/u97:6 Tainted: G W 6.16.5-1-MANJARO #1 PREEMPT(full) d3b2b3e5b7f9926d152eb98481f4a8a1d1b46a27 Sep 10 21:54:17 bee kernel: Tainted: [W]=WARN Sep 10 21:54:17 bee kernel: Hardware name: AZW SER9/SER9, BIOS SER9T402 05/09/2025 Sep 10 21:54:17 bee kernel: Workqueue: async async_run_entry_fn Sep 10 21:54:17 bee kernel: RIP: 0010:ieee80211_reconfig+0x9a/0x15e0 [mac80211] Sep 10 21:54:17 bee kernel: Code: 03 00 00 41 c6 87 ad 05 00 00 00 4c 89 ff e8 3d 56 fb ff 41 89 c4 85 c0 0f 84 18 03 00 00 48 c7 c7 60 21 2a c2 e8 26 27 5e d1 <0f> 0b eb 31 84 c0 0f 85 5f> Sep 10 21:54:17 bee kernel: RSP: 0018:ffffd4b14198bcb0 EFLAGS: 00010246 Sep 10 21:54:17 bee kernel: RAX: 0000000000000000 RBX: ffff8e77ba430538 RCX: 0000000000000027 Sep 10 21:54:17 bee kernel: RDX: ffff8e85c1c9cfc8 RSI: 0000000000000001 RDI: ffff8e85c1c9cfc0 Sep 10 21:54:17 bee kernel: RBP: 0000000000000001 R08: 0000000000000000 R09: 00000000ffffdfff Sep 10 21:54:17 bee kernel: R10: ffffffff96588880 R11: ffffd4b14198ba80 R12: 00000000ffffffff Sep 10 21:54:17 bee kernel: R13: 0000000000000010 R14: 0000000000000000 R15: ffff8e77ba430900 Sep 10 21:54:17 bee kernel: FS: 0000000000000000(0000) GS:ffff8e862b79b000(0000) knlGS:0000000000000000 Sep 10 21:54:17 bee kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 10 21:54:17 bee kernel: CR2: 00007f0b781da000 CR3: 00000009a3224000 CR4: 0000000000f50ef0 Sep 10 21:54:17 bee kernel: PKRU: 55555554 Sep 10 21:54:17 bee kernel: Call Trace: Sep 10 21:54:17 bee kernel: <TASK> Sep 10 21:54:17 bee kernel: ? __queue_work+0xfe/0x430 Sep 10 21:54:17 bee kernel: ? queue_work_node+0xf9/0x110 Sep 10 21:54:17 bee kernel: ? __slab_free+0xe4/0x310 Sep 10 21:54:17 bee kernel: ? __async_schedule_node_domain+0xdd/0x140 Sep 10 21:54:17 bee kernel: wiphy_resume+0x82/0x1b0 [cfg80211 9c12353f8426a54e35f6db9b44bd6f08177d4ffd] Sep 10 21:54:17 bee kernel: ? __pfx_wiphy_resume+0x10/0x10 [cfg80211 9c12353f8426a54e35f6db9b44bd6f08177d4ffd] Sep 10 21:54:17 bee kernel: dpm_run_callback+0x47/0x150 Sep 10 21:54:17 bee kernel: device_resume+0x183/0x280 Sep 10 21:54:17 bee kernel: async_resume+0x21/0x30 Sep 10 21:54:17 bee kernel: async_run_entry_fn+0x33/0x140 Sep 10 21:54:17 bee kernel: process_one_work+0x190/0x350 Sep 10 21:54:17 bee kernel: worker_thread+0x2d7/0x410 Sep 10 21:54:17 bee kernel: ? __pfx_worker_thread+0x10/0x10 Sep 10 21:54:17 bee kernel: kthread+0xf9/0x240 Sep 10 21:54:17 bee kernel: ? __pfx_kthread+0x10/0x10 Sep 10 21:54:17 bee kernel: ? __pfx_kthread+0x10/0x10 Sep 10 21:54:17 bee kernel: ret_from_fork+0x197/0x1d0 Sep 10 21:54:17 bee kernel: ? __pfx_kthread+0x10/0x10 Sep 10 21:54:17 bee kernel: ret_from_fork_asm+0x1a/0x30 Sep 10 21:54:17 bee kernel: </TASK> Sep 10 21:54:17 bee kernel: ---[ end trace 0000000000000000 ]--- Sep 10 21:54:17 bee kernel: ------------[ cut here ]------------ Sep 10 21:54:17 bee kernel: WARNING: CPU: 2 PID: 352 at net/mac80211/driver-ops.c:41 drv_stop+0xfd/0x110 [mac80211] Sep 10 21:54:17 bee kernel: Modules linked in: snd_seq_dummy rfcomm snd_hrtimer snd_seq ccm cmac algif_hash algif_skcipher af_alg bnep vfat fat snd_usb_audio mousedev joydev snd_usbmidi_li> Sep 10 21:54:17 bee kernel: snd_rn_pci_acp3x polyval_clmulni snd_pcm ghash_clmulni_intel cfg80211 sha512_ssse3 sp5100_tco snd_acp_config sha1_ssse3 snd_timer libphy psmouse amdxdna thunde> Sep 10 21:54:17 bee kernel: CPU: 2 UID: 0 PID: 352 Comm: kworker/u97:6 Tainted: G W 6.16.5-1-MANJARO #1 PREEMPT(full) d3b2b3e5b7f9926d152eb98481f4a8a1d1b46a27 Sep 10 21:54:17 bee kernel: Tainted: [W]=WARN Sep 10 21:54:17 bee kernel: Hardware name: AZW SER9/SER9, BIOS SER9T402 05/09/2025 Sep 10 21:54:17 bee kernel: Workqueue: async async_run_entry_fn Sep 10 21:54:17 bee kernel: RIP: 0010:drv_stop+0xfd/0x110 [mac80211] Sep 10 21:54:17 bee kernel: Code: 48 85 c0 74 0e 48 8b 78 08 89 ea 48 89 de e8 6a 67 05 00 65 ff 0d f3 d1 5d d4 0f 85 38 ff ff ff e8 a8 e8 57 d1 e9 2e ff ff ff <0f> 0b 5b 5d c3 cc cc cc cc> Sep 10 21:54:17 bee kernel: RSP: 0018:ffffd4b14198bbe8 EFLAGS: 00010246 Sep 10 21:54:17 bee kernel: RAX: 0000000000000000 RBX: ffff8e77ba430900 RCX: 0000000000000000 Sep 10 21:54:17 bee kernel: RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff8e77ba430900 Sep 10 21:54:17 bee kernel: RBP: 0000000000000000 R08: 0000005deb37c501 R09: ffff8e77ba61a3b0 Sep 10 21:54:17 bee kernel: R10: ffff8e77ba431210 R11: 0000000000000246 R12: ffff8e77ba430900 Sep 10 21:54:17 bee kernel: R13: 0000000000000000 R14: ffffd4b14198bd48 R15: ffffd4b14198bc30 Sep 10 21:54:17 bee kernel: FS: 0000000000000000(0000) GS:ffff8e862b79b000(0000) knlGS:0000000000000000 Sep 10 21:54:17 bee kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 10 21:54:17 bee kernel: CR2: 00007f0b781da000 CR3: 00000009a3224000 CR4: 0000000000f50ef0 Sep 10 21:54:17 bee kernel: PKRU: 55555554 Sep 10 21:54:17 bee kernel: Call Trace: Sep 10 21:54:17 bee kernel: <TASK> Sep 10 21:54:17 bee kernel: ieee80211_do_stop+0x650/0x980 [mac80211 322d1418d176657aaba1b88464f946f8c76e733b] Sep 10 21:54:17 bee kernel: ? synchronize_rcu_expedited+0x1df/0x220 Sep 10 21:54:17 bee kernel: ieee80211_stop+0x62/0xe0 [mac80211 322d1418d176657aaba1b88464f946f8c76e733b] Sep 10 21:54:17 bee kernel: __dev_close_many+0xa8/0x220 Sep 10 21:54:17 bee kernel: dev_close_many+0xdc/0x1c0 Sep 10 21:54:17 bee kernel: netif_close+0x68/0xa0 Sep 10 21:54:17 bee kernel: dev_close+0x2a/0x80 Sep 10 21:54:17 bee kernel: cfg80211_shutdown_all_interfaces+0x46/0xf0 [cfg80211 9c12353f8426a54e35f6db9b44bd6f08177d4ffd] Sep 10 21:54:17 bee kernel: wiphy_resume+0xc1/0x1b0 [cfg80211 9c12353f8426a54e35f6db9b44bd6f08177d4ffd] Sep 10 21:54:17 bee kernel: ? __pfx_wiphy_resume+0x10/0x10 [cfg80211 9c12353f8426a54e35f6db9b44bd6f08177d4ffd] Sep 10 21:54:17 bee kernel: dpm_run_callback+0x47/0x150 Sep 10 21:54:17 bee kernel: device_resume+0x183/0x280 Sep 10 21:54:17 bee kernel: async_resume+0x21/0x30 Sep 10 21:54:17 bee kernel: async_run_entry_fn+0x33/0x140 Sep 10 21:54:17 bee kernel: process_one_work+0x190/0x350 Sep 10 21:54:17 bee kernel: worker_thread+0x2d7/0x410 Sep 10 21:54:17 bee kernel: ? __pfx_worker_thread+0x10/0x10 Sep 10 21:54:17 bee kernel: kthread+0xf9/0x240 Sep 10 21:54:17 bee kernel: ? __pfx_kthread+0x10/0x10 Sep 10 21:54:17 bee kernel: ? __pfx_kthread+0x10/0x10 Sep 10 21:54:17 bee kernel: ret_from_fork+0x197/0x1d0 Sep 10 21:54:17 bee kernel: ? __pfx_kthread+0x10/0x10 Sep 10 21:54:17 bee kernel: ret_from_fork_asm+0x1a/0x30 Sep 10 21:54:17 bee kernel: </TASK> Sep 10 21:54:17 bee kernel: ---[ end trace 0000000000000000 ]---

mss Hi there Please try some solutions here : 1. Disconnect built-in Speaker , Or uninstall the speaker drivers. See if you can make it into sleep. 2. Please go to BIOS advanced page >ACPI settings > enable ACPI auto configuration.

I’ve tried both and it did not help. This is a bug in the BIOS ACPI table, please ask your R&D Team to fix the ACPI table. They will be able to reproduce the problem on any recent Linux distribution. Please confirm that the R&D Team can reproduce this issue.

mss Hello there, We have already fed back your machine to our R&D personnel. We believe that the corresponding BIOS will soon be available to solve your machine’s malfunction issue. Please wait patiently. Have a nice day!

SER9 PRO AMD Pro Ryzen™ AI 9 HX 370 ACPI BIOS bugs

charles23pa

Hi, I have the same problem with linux. I tried Ubuntu, PopOS and Fedora. latest fedora version, and latest LTS in ubuntu.

The PC is unable to suspend from linux if I send the suspend instruction. It starts the suspend proces, fails and the networking becomes disabled. Both network adapters (wifi and ethernet). A full reboot restore the network adapters.

I have the SER9-PRo AMD Ryzen™ AI 9 HX 370 w/ Radeon™ 890M × 24 with 32Gb ram.

SN: DX375GG70129

I use the suspend function a lot to prevent losing active work.

Currently running Ubuntu 24.04.03LTS, Kernel 6.14.0-33-generic

Beelink CS-Rose

charles23pa

Please send us a picture of SN number（two lines） and BIOS version.So we would be able to know whether it is latest BIOS and send you files accordingly.

Here`s how to check your BIOS version:https://mega.nz/#F!yuISGa4I!s1bQQajKwnsEdzjqq4nopQ

charles23pa

Beelink CS-Rose
Image description

BIOS Version SER9T204
SN: DHX375GG70129

Beelink CS-June

charles23pa

Hello there,

I have sent the BIOS file for you, please check your PM.

Have a nice day~

charles23pa

Hi, i’m willing to try the SER9T405 update

thanks,

mss

Beelink CS-June I’m happy to test the new version, too, if you don’t mind sharing it with me.

S/N and BIOS screenshot are here: https://photos.app.goo.gl/3LmLGnevoHbkAvxs5

Beelink CS-June

mss

Hello there,

Sorry for your waiting.
The machine BIOS file we sent to the user charles23pa is not applicable to your machine.

At present, regarding the ACPI error issue of SER9, our R&D team is still actively seeking solutions.

Please wait patiently.

Have a nice day!

charles23pa

Hello there,

Sorry for your waiting.

We have already sent your feedback to the corresponding R&D personnel.

We will contact you as soon as we have a solution.

Have a nice day!

charles23pa

Hi, i was able to update the BIOS but the suspend problems are the same. I think ti has the same bios version but different build date and time.

The PC won’t go into suspend mode (it fails after a couple of seconds) and then the wifi and ethernet adapters are offline. A reboot fixes the networking.

I had to disable the automatic suspend (after x minutes) on my machine in the meanwhile. Image description

Ford

Just a reminder that it’s almost a year since AMD technical staff identified this as a Beelink BIOS bug, and offered your team support with fixing it.

Any updates?

Beelink CS-Rose

Ford

Is your current BIOS version T108?

Please send us a picture of SN on the bottom of the PC.

TrevinLC1997

Beelink CS-Rose Would you happen to have an update for mine?

Experiencing the same issues where WiFi and Ethernet drop out after a power event.
https://photos.app.goo.gl/E8p4MY27gXS2KTpQ9

Beelink CS-Rose

TrevinLC1997

Your current BIOS version is the latest and you don’t need to update.

First, Please turn off the PC , unplug the power supply, and press the CMOS button (if no CMOS button, please put the pin in the CMOS pinhole and press it ) for about 10 seconds , restart the PC after ten minutes. Here is the tutorial https://mega.nz/file/XypwTISY#DVT0BsjOgiPkZ-drQaj88JH9Z7f7qpKGP2E3nMHW8ms or https://url.bee-link.cn/5FdW

TrevinLC1997

Beelink CS-Rose Thanks for the response, while this does fix it temporarily, is the ACPI fixes mentioned above, does that fix the issue with the RTL8125 not waking up after a suspend? Journalctl shows

Nov 12 13:28:05 fedora kernel: PM: suspend devices took 0.083 seconds
Nov 12 13:28:05 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SBRG.ECOK], AE_NOT_FOUND (20250404/psargs-332)
Nov 12 13:28:05 fedora kernel: ACPI Error: Aborting method _SB.PCI0.GPP7.WOFF due to previous error (AE_NOT_FOUND) (20250404/psparse-529)
Nov 12 13:28:05 fedora kernel: ACPI Error: Aborting method _SB.PCI0.GPP7.P0WW.OFF due to previous error (AE_NOT_FOUND) (20250404/psparse-529)
Nov 12 13:28:05 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SBRG.EC0.GPO3], AE_NOT_FOUND (20250404/psargs-332)
Nov 12 13:28:05 fedora kernel: ACPI Error: Aborting method _SB.PCI0.GPP5.P_OF due to previous error (AE_NOT_FOUND) (20250404/psparse-529)
Nov 12 13:28:05 fedora kernel: ACPI Error: Aborting method _SB.PCI0.GPP5.PWSR.OFF due to previous error (AE_NOT_FOUND) (20250404/psparse-529)
Nov 12 13:28:05 fedora kernel: pcieport 0000:00:02.5: broken device, retraining non-functional downstream link at 2.5GT/s
Nov 12 13:28:05 fedora kernel: pcieport 0000:00:02.3: broken device, retraining non-functional downstream link at 2.5GT/s
Nov 12 13:28:05 fedora kernel: pcieport 0000:00:02.5: retraining failed
Nov 12 13:28:05 fedora kernel: pcieport 0000:00:02.3: retraining failed
Nov 12 13:28:05 fedora kernel: pcieport 0000:00:02.5: Data Link Layer Link Active not set in 100 msec
Nov 12 13:28:05 fedora kernel: pci 0000:c3:00.0: Unable to change power state from D3cold to D0, device inaccessible
Nov 12 13:28:05 fedora kernel: pcieport 0000:00:02.3: Data Link Layer Link Active not set in 100 msec
Nov 12 13:28:05 fedora kernel: r8169 0000:c2:00.0: Unable to change power state from D3cold to D0, device inaccessible

c2:00.0 - Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
c3:00.0 - Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)

Beelink CS-Rose

TrevinLC1997

The BIOS has been sent to your private message.

mss

Beelink CS-Rose does that mean there is a new BIOS version available now which fixes the NICs not waking up after a suspend?

Beelink CS-Rose

mss

You can try updating the BIOS file. (Already sent via private message)

mss

Beelink CS-Rose thank you! There is progress! After flashing version SER9T405, the NICs do continue to work after a suspend, indeed!

The fan keeps spinning, though, so apparently, we’re not reaching the desired sleep state. The kernel messages seems to confirm that:

[ 70.374463] amd_pmc AMDI000A:00: Last suspend didn't reach deepest state

That’s when I use systemctl suspend. When I use systemctl hibernate, the system does hibernate properly and turns off.

Can you please provide that feedback to the R&D Team? Something prevents the suspend to reach the desired sleep state now.

Ford

Your R&D department need to fully test the new BIOS, announce it here, and allow download via the existing portal https://dr.bee-link.cn/?dir=uploads/SER/SER9--AI-9-HX-370/BIOS (which isn’t actually working right now)

The way you’re asking people to PM their serial number, sending BIOS builds privately, and expecting customers to test themselves and feed back to you is a waste of time and clearly not working. I replied to your request to do this (again) 2 weeks ago, and haven’t even had a response yet.

Communication has been terrible, continuing to ask people to uninstall speaker drivers, reset the CMOS, etc., when the issue has been confirmed as a Beelink BIOS issue by AMD almost a year ago.

Beelink CS-Rose

charles23pa

Your BIOS version is T204, and T405 is not compatible with your current machine.Updating to the wrong BIOS can brick your machine.

You can try updating the BIOS file I sent you via private message.

« Previous Page