The Ryzen AI 9 HX 370 on the SER9 is very new processor and needs some very recent parts to get running on Linux. The requirements are: Linux 6.10 or later. Mesa 24.2 or later Linux Firmware 20240811 ONLY (At the time of this writing any newer firmware causes amdgpu to hang). Sadly, manjaro, ubuntu 24.10, bazzite and others that roll the latest stuff come with newer firmware that won’t work with the 890m. You can specify nomodeset for the command line to get an install done, then downgrade to Linux Firmware 20240811. My successful build is using Mageia Cauldron with linux 6.11.4, mesa-24.2.5 and radeon-firmware-20240811. I was able to get the build working with Mageia 9 plus Linux 6.11.4 and mesa 2.4.4 but I did not have 3D acceleration. The firmware tarballs are here: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/

HI there , Thanks for sharing . Please let me know, if you have any query , i am glad to help. Your satisfaction is our top priority !

Same problem here. Tried the latest endeavouros doesn’t boot with the latest release without nomodeset. Also tried installing on a 6900HX on usb drive updated everything moved the usb drive to SER9 and hangs on boot. Is that a bios problem or amdgpu driver problem? And how come AMD doesn’t fix this problem? P.S. also tried ubuntu desktop 24.10 to double check with the same results.

It’s the firmware, if you check the site: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ You’ll see that there are two firmwares after 20240811 and on both of those the system, or amdgpu more specifically, will hang, prior to 20240811, the GPU won’t initialize but at least you’ll get a text screen or a vesa display at 1024×768. I worked around the problem by looking at how mageia did their firmware and rebuilt the firmware package, in this case radeon-firmware-YYYYMMDD.rpm and used that. I’ve looked for a way to file a bug report with the firmware guys but I couldn’t find any way to do so. I saw that ETA prime and Techtablets on the YouTube were able to get Linux running which sent me down the rabbit hole for chasing the firmware issue. I don’t know about other distributions but you should, hopefully, be able to get an older firmware rpm/deb/apk that has 20240811. And you’re right, AMD should straighten out the firmware problem, pronto.

EndeavourOS is arch based. I installed a fresh copy and downgraded the linux-firmware to the august release and upgraded everything else. This worked for now but it’s a bypass of the problem. It’s not a solution. Let’s hope the next linux-firmware release will solve this problem.

Well at least you have a working system and it verifies that the firmware is the root cause of the problem. Thanks for following through and posting your results.

ximejo HI there You can email us with pictures of BIOS version and SN picture. Here`s how to check your BIOS version: https://mega.nz/#F!yuISGa4I!s1bQQajKwnsEdzjqq4nopQ See if updating BIOS would improve that situation .

I don’t know about uploading a picture but here’s the output from “dmidecode”: SMBIOS 3.7.0 present. Table at 0×78256000. Handle 0×0000, DMI type 0, 26 bytes BIOS Information Vendor: American Megatrends International, LLC. Version: STX.3xx.SER9.V103.P8C0M0C15.54.Link.GID Release Date: 09/10/2024 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 32 MB Characteristics: It would be nice to be able to use a more up to date amdgpu firmware.

Beelink CS-Ian Chan I have updated the bios to the latest release from https://dr.bee-link.cn/ . It still doesn’t boot without nomodset. Have you tested the latest ubuntu desktop release (24.10)? Does it boot on your test machine without nomodeset? Is it our problem? or a general problem? What are the steps to solve this issue?

This is my dimdecode output: # dmidecode 3.6 Getting SMBIOS data from sysfs. SMBIOS 3.7.0 present. Table at 0x78256000. Handle 0x0000, DMI type 0, 26 bytes BIOS Information Vendor: American Megatrends International, LLC. Version: STX.3xx.SER9.V103.P8C0M0C15.55.Link.GID.90 Release Date: 09/26/2024 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 32 MB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported ACPI is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 0.0 if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); }

To try to get a little more information about this matter I did the following steps: I removed radeon-firmware (Mageia packages it separately from linux-firmware) I booted my system normally, and got the expected error messages: [Fri Oct 25 08:11:47 2024] amdgpu 0000:65:00.0: amdgpu: Fetched VBIOS from VFCT [Fri Oct 25 08:11:47 2024] amdgpu: ATOM BIOS: 113-STRIXEMU-001 [Fri Oct 25 08:11:47 2024] amdgpu 0000:65:00.0: Direct firmware load for amdgpu/psp_14_0_0_toc.bin failed with error -2 [Fri Oct 25 08:11:47 2024] [drm:amdgpu_device_init.cold [amdgpu]] ERROR early_init of IP block <psp> failed -19 [Fri Oct 25 08:11:47 2024] amdgpu 0000:65:00.0: Direct firmware load for amdgpu/dcn_3_5_dmcub.bin failed with error -2 [Fri Oct 25 08:11:47 2024] [drm:amdgpu_device_init.cold [amdgpu]] ERROR early_init of IP block <dm> failed -19 [Fri Oct 25 08:11:47 2024] amdgpu 0000:65:00.0: Direct firmware load for amdgpu/gc_11_5_0_pfp.bin failed with error -2 [Fri Oct 25 08:11:47 2024] [drm:amdgpu_device_init.cold [amdgpu]] ERROR early_init of IP block <gfx_v11_0> failed -19 [Fri Oct 25 08:11:47 2024] amdgpu 0000:65:00.0: Direct firmware load for amdgpu/sdma_6_1_0.bin failed with error -2 [Fri Oct 25 08:11:47 2024] [drm:amdgpu_device_init.cold [amdgpu]] ERROR early_init of IP block <sdma_v6_0> failed -19 [Fri Oct 25 08:11:47 2024] amdgpu 0000:65:00.0: Direct firmware load for amdgpu/vcn_4_0_5.bin failed with error -2 [Fri Oct 25 08:11:47 2024] [drm:amdgpu_device_init.cold [amdgpu]] ERROR early_init of IP block <vcn_v4_0_5> failed -19 [Fri Oct 25 08:11:47 2024] amdgpu 0000:65:00.0: Direct firmware load for amdgpu/gc_11_5_0_mes_2.bin failed with error -2 [Fri Oct 25 08:11:47 2024] amdgpu 0000:65:00.0: amdgpu: try to fall back to gc_11_5_0_mes.bin [Fri Oct 25 08:11:47 2024] amdgpu 0000:65:00.0: Direct firmware load for amdgpu/gc_11_5_0_mes.bin failed with error -2 [Fri Oct 25 08:11:47 2024] [drm:amdgpu_device_init.cold [amdgpu]] ERROR early_init of IP block <mes_v11_0> failed -19 [Fri Oct 25 08:11:47 2024] amdgpu 0000:65:00.0: amdgpu: VPE: collaborate mode false [Fri Oct 25 08:11:47 2024] amdgpu 0000:65:00.0: amdgpu: Fatal error during GPU init [Fri Oct 25 08:11:47 2024] amdgpu 0000:65:00.0: amdgpu: amdgpu: finishing device. The system then came all the way up into multi-user mode and as expected sddm didn’t start but I could access the system from ssh. I opened two ssh sessions, one I did a “dmesg -Tw” and the other I left for entering commands. Next, I installed the latest radeon-firmware, then did a “rmmod amdgpu” followed by “modprobe amdgpu” at which point the output from the SER9 went black and the following output from “dmesg -Tw” came through from my remote session: [Fri Oct 25 08:14:58 2024] [drm] amdgpu kernel modesetting enabled. [Fri Oct 25 08:14:58 2024] amdgpu: Virtual CRAT table created for CPU [Fri Oct 25 08:14:58 2024] amdgpu: Topology: Add CPU node [Fri Oct 25 08:14:58 2024] [drm] initializing kernel modesetting (IP DISCOVERY 0×1002:0×150E 0×1F66:0×0030 0xC1). [Fri Oct 25 08:14:58 2024] [drm] register mmio base: 0xDC400000 [Fri Oct 25 08:14:58 2024] [drm] register mmio size: 524288 [Fri Oct 25 08:14:58 2024] [drm] add ip block number 0 <soc21_common> [Fri Oct 25 08:14:58 2024] [drm] add ip block number 1 <gmc_v11_0> [Fri Oct 25 08:14:58 2024] [drm] add ip block number 2 <ih_v6_1> [Fri Oct 25 08:14:58 2024] [drm] add ip block number 3 <psp> [Fri Oct 25 08:14:58 2024] [drm] add ip block number 4 <smu> [Fri Oct 25 08:14:58 2024] [drm] add ip block number 5 <dm> [Fri Oct 25 08:14:58 2024] [drm] add ip block number 6 <gfx_v11_0> [Fri Oct 25 08:14:58 2024] [drm] add ip block number 7 <sdma_v6_0> [Fri Oct 25 08:14:58 2024] [drm] add ip block number 8 <vcn_v4_0_5> [Fri Oct 25 08:14:58 2024] [drm] add ip block number 9 <jpeg_v4_0_5> [Fri Oct 25 08:14:58 2024] [drm] add ip block number 10 <mes_v11_0> [Fri Oct 25 08:14:58 2024] [drm] add ip block number 11 <vpe_v6_1> [Fri Oct 25 08:14:58 2024] amdgpu 0000:65:00.0: amdgpu: Fetched VBIOS from VFCT [Fri Oct 25 08:14:58 2024] amdgpu: ATOM BIOS: 113-STRIXEMU-001 [Fri Oct 25 08:14:58 2024] amdgpu 0000:65:00.0: amdgpu: VPE: collaborate mode false [Fri Oct 25 08:14:58 2024] Console: switching to colour dummy device 80×25 [Fri Oct 25 08:14:58 2024] amdgpu 0000:65:00.0: amdgpu: Trusted Memory Zone (TMZ) feature disabled as experimental (default) [Fri Oct 25 08:14:58 2024] [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit [Fri Oct 25 08:14:58 2024] amdgpu 0000:65:00.0: amdgpu: VRAM: 512M 0×0000008000000000 - 0×000000801FFFFFFF (512M used) [Fri Oct 25 08:14:58 2024] amdgpu 0000:65:00.0: amdgpu: GART: 512M 0×00007FFF00000000 - 0×00007FFF1FFFFFFF [Fri Oct 25 08:14:58 2024] [drm] Detected VRAM RAM=512M, BAR=512M [Fri Oct 25 08:14:58 2024] [drm] RAM width 128bits LPDDR5 [Fri Oct 25 08:14:58 2024] [drm] amdgpu: 512M of VRAM memory ready [Fri Oct 25 08:14:58 2024] [drm] amdgpu: 15550M of GTT memory ready. [Fri Oct 25 08:14:58 2024] [drm] GART: num cpu pages 131072, num gpu pages 131072 [Fri Oct 25 08:14:58 2024] [drm] PCIE GART of 512M enabled (table at 0×0000008000300000). [Fri Oct 25 08:14:58 2024] [drm] Loading DMUB firmware via PSP: version=0×09000500 [Fri Oct 25 08:14:58 2024] [drm] Found VCN firmware Version ENC: 1.22 DEC: 9 VEP: 0 Revision: 1 [Fri Oct 25 08:14:58 2024] amdgpu 0000:65:00.0: amdgpu: reserve 0×8900000 from 0×8010000000 for PSP TMR [Fri Oct 25 08:14:58 2024] amdgpu 0000:65:00.0: amdgpu: RAS: optional ras ta ucode is not available [Fri Oct 25 08:14:58 2024] amdgpu 0000:65:00.0: amdgpu: RAP: optional rap ta ucode is not available [Fri Oct 25 08:14:58 2024] amdgpu 0000:65:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [Fri Oct 25 08:14:58 2024] amdgpu 0000:65:00.0: amdgpu: SMU is initialized successfully! [Fri Oct 25 08:14:58 2024] [drm] Seamless boot condition check passed [Fri Oct 25 08:14:58 2024] [drm] Display Core v3.2.291 initialized on DCN 3.5 [Fri Oct 25 08:14:58 2024] [drm] DP-HDMI FRL PCON supported [Fri Oct 25 08:14:58 2024] [drm] Wait for DMUB auto-load failed: 3 [Fri Oct 25 08:14:58 2024] [drm] DMUB hardware initialized: version=0×09000500 The system remained accessible from ssh but my “modprobe amdgpu” never finished it ran away at 100% CPU. If I boot the system with the newer firmware installed, it eventually comes up, after several minutes, in multi-user mode but the screen output is black and getting in via ssh shows that “udev-worker” is running 100%, X did not initialize. Reverting back to the 20240811 firmware the system comes up in a functional state; I guess we’re very lucky we have 20240811. I don’t know if this is unique to the beelink SER9 but I did see one poster said that he was unable to get any distribution working on a AI HX 370, which I assumed was probably due to the firmware issue. I have seen that the system seems to have another issue: If it’s not kept busy, it spontaneously reboots, I am assuming that it goes into a very low power usage mode that Linux doesn’t handle and causes a reboot. Enough for this post.

Linux on SER9.

Joba

Hi I just installed latest stable ununtu on my new ser9. Wifi isn’t working. Is this related to bios? It works if I connect external wifi adapter through usb.

Minipc 8b.024120843n10
sn:BHX375IG60046

Beelink CS-Ian Chan

Joba
Hi there
Please send us a picture of SN number 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:

Prese : Win + R ,
Type : msinfo32
Send us the screen.

or try this
https://mega.nz/#F!yuISGa4I!s1bQQajKwnsEdzjqq4nopQ

Joba

Beelink CS-Ian Chan
I already gave SN right?
sn:BHX375IG60046

Image description

Beelink CS-Bettie

Joba
Your machine’s BIOS is already up to date and does not need to be updated.
Have you tried reinstalling the WiFi driver?
The following are the drivers compatible with your machine’s SN serial number（BHX375IG60046）: https://url.bee-link.cn/8MYI

mfornasa

@Beelink CS-Rose @Beelink CS-Bettie

I’ve done some additional testing on suspending the Beelink SER9 with the HX 370. Results are here: https://gitlab.freedesktop.org/drm/amd/-/issues/4519. The most likely cause appears to be the BIOS not configuring the devices properly. So, this seems to require a fix from Beelink. Can we have a timeline on this?

Beelink CS-Ian Chan

mfornasa
Hi, there
May I know Have you tried this solution yet ?
See if you can go into Deep mode by disconnecting internal speaker or uninstall speaker driver.

We will come out with later BIOS to improve the situation .

mfornasa

@Beelink CS-Ian Chan currently the bios does not advertise deep mode, so I am not able to initiate deep suspend. Are you saying that physically disconnecting the speaker is going to activate deep mode on the bios? Can you confirm?

Beelink CS-Ian Chan

mfornasa
Hi there
Sorry for the confusion ,I meant uninstalling the speaker driver to go to sleep mode .

JohnRambo

Hello mfornasa,

I can assure you that hibernation works perfectly with my Beelink SER 9 (BIOS STX.3xx.SER9.V103.P8COMO, 32 GB RAM) under Ubuntu 24.04.3 LTS. (Suspend-to-RAM AND Suspend-to-Disk)

However, it was a very lengthy process to get it working!

It also worked with CachyOS (Arch-based) and KDE/Plasma. (But at least for me, it currently does not work with CachyOS and Gnome).

If you (or anyone else) would like a detailed description of the steps required for Ubuntu 24.04.3 LTS, I can publish it here (or elsewhere?).
But as I said, it’s a long road…

mfornasa

JohnRambo Thanks for the details. Hibernation works for me without issues (I simply applied the procedure recommended in the Arch wiki). But I am trying to achieve a suspension to RAM. Support is suggesting deep suspend, which in my understanding is not supported on my Beelink (only suspend-to-idle s2idle mode is advertised as supported).

mfornasa

Beelink CS-Ian Chan can you provide instructions to uninstall the speaker driver in Linux?

Beelink CS-Ian Chan

mfornasa
Hi，there
Please use this command to list all the modules
lsmod | grep snd

And send us a picture to find speaker driver.

mfornasa

Beelink CS-Ian Chan

❯ lsmod | grep snd snd_seq_dummy 12288 0 snd_hrtimer 12288 1 snd_seq 135168 7 snd_seq_dummy snd_acp70 12288 0 snd_acp_i2s 20480 1 snd_acp70 snd_acp_pdm 12288 1 snd_acp70 snd_acp_pcm 16384 1 snd_acp70 snd_sof_amd_acp70 16384 0 snd_sof_amd_acp63 16384 0 snd_sof_amd_vangogh 16384 0 snd_sof_amd_rembrandt 16384 0 snd_sof_amd_renoir 16384 0 snd_sof_amd_acp 73728 5 snd_sof_amd_acp70,snd_sof_amd_rembrandt,snd_sof_amd_vangogh,snd_sof_amd_acp63,snd_sof_amd_renoir snd_sof_pci 24576 5 snd_sof_amd_acp70,snd_sof_amd_rembrandt,snd_sof_amd_vangogh,snd_sof_amd_acp63,snd_sof_amd_renoir snd_sof_xtensa_dsp 16384 1 snd_sof_amd_acp snd_sof 475136 2 snd_sof_amd_acp,snd_sof_pci snd_sof_utils 16384 1 snd_sof snd_pci_ps 36864 0 snd_soc_acpi_amd_match 12288 2 snd_sof_amd_acp63,snd_pci_ps snd_amd_sdw_acpi 16384 2 snd_sof_amd_acp,snd_pci_ps soundwire_amd 45056 2 snd_sof_amd_acp,snd_pci_ps snd_soc_sdca 69632 1 soundwire_bus snd_soc_core 430080 4 snd_sof,snd_soc_sdca,snd_acp_pcm,soundwire_amd snd_compress 28672 1 snd_soc_core snd_hda_codec_conexant 36864 1 ac97_bus 12288 1 snd_soc_core snd_hda_codec_generic 114688 1 snd_hda_codec_conexant snd_pcm_dmaengine 20480 1 snd_soc_core snd_hda_codec_hdmi 94208 1 snd_rpl_pci_acp6x 16384 0 snd_hda_intel 69632 2 snd_acp_pci 12288 0 snd_intel_dspcfg 45056 2 snd_hda_intel,snd_sof snd_amd_acpi_mach 12288 1 snd_acp_pci snd_usb_audio 577536 2 snd_intel_sdw_acpi 16384 1 snd_intel_dspcfg snd_acp_legacy_common 20480 2 snd_acp70,snd_acp_pci snd_usbmidi_lib 49152 1 snd_usb_audio snd_pci_acp6x 20480 0 snd_hda_codec 217088 4 snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel snd_ump 40960 1 snd_usb_audio snd_pci_acp5x 20480 0 snd_hda_core 139264 5 snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec snd_rawmidi 53248 2 snd_usbmidi_lib,snd_ump snd_rn_pci_acp3x 24576 0 snd_seq_device 16384 3 snd_seq,snd_ump,snd_rawmidi snd_hwdep 24576 2 snd_usb_audio,snd_hda_codec snd_acp_config 20480 10 snd_rn_pci_acp3x,snd_sof_amd_acp70,snd_pci_acp6x,snd_pci_acp5x,snd_sof_amd_rembrandt,snd_sof_amd_vangogh,snd_sof_amd_acp63,snd_acp_pci,snd_pci_ps,snd_sof_amd_renoir mc 90112 5 videodev,snd_usb_audio,videobuf2_v4l2,uvcvideo,videobuf2_common snd_pcm 212992 16 snd_sof_amd_acp,snd_hda_codec_hdmi,snd_pci_acp6x,snd_acp_legacy_common,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_sof,snd_compress,snd_soc_core,snd_acp_pcm,snd_sof_utils,soundwire_amd,snd_hda_core,snd_pci_ps,snd_pcm_dmaengine snd_soc_acpi 16384 5 snd_sof_amd_acp,snd_acp_legacy_common,snd_acp_config,snd_amd_acpi_mach,snd_pci_ps snd_timer 57344 3 snd_seq,snd_hrtimer,snd_pcm snd_pci_acp3x 20480 0 snd 155648 27 snd_hda_codec_generic,snd_seq,snd_hda_codec_conexant,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_sof,snd_timer,snd_compress,snd_soc_core,snd_ump,snd_pcm,snd_rawmidi soundcore 16384 1 snd

Beelink CS-Rose

Please try to uninstall snd_sof_amd_acp70

mfornasa

Beelink CS-Rose I removed snd_sof_amd_acp70.

Deep mode still not available (BTW, this is probably expected).

cat /sys/power/mem_sleep
[s2idle]

Beelink CS-Rose

mfornasa

Please try:

Uninstall the main module and its dependency chain
sudo rmmod snd_acp70
sudo rmmod snd_acp_i2s
sudo rmmod snd_acp_pdm
sudo rmmod snd_acp_pcm

Deep Mode: If you have Performance Mode enabled, turn it off.

mfornasa

Beelink CS-Rose I tried that, no luck.
BTW, I don’t think that anything you can do after boot is going to change the mem_sleep options. It must be the BIOS.

Beelink CS-Ian Chan

Hi，there
Please check if you can enable it in these few ways:

1.Using the systemctl command
In modern Linux systems, you can control power management with the systemctl command. Here are two common suspend modes:
Suspend to RAM (Suspend-to-RAM):
This is a common way to enter deep suspend mode. The system shuts down most hardware, keeping only memory active to allow for quick recovery.
bash
sudo systemctl suspend
Suspend to Disk (Hibernate):
In this mode, the current system state is written to disk and the power is turned off. When resumed, the system loads the data from disk and restores to its previous state. This method usually requires a swap partition or swap file large enough to store the system state.
bash
sudo systemctl hibernate

2.
Configuring Deep Suspend Mode (Hibernate)
If hibernation is not enabled by default on your system, you may need to configure it manually. Ensure that your system has a sufficiently large swap partition or swap file to save the system state.
Check if your system supports hibernation:
bash
sudo cat /sys/power/state
If the output contains hibernate, the system supports hibernation.
Ensure that your swap partition is large enough (typically needs to be equal to or larger than your memory size) and configure it in /etc/fstab.
Enable hibernation:
Edit the /etc/systemd/logind.conf file and ensure the following setting:
ini
HandleLidSwitch=hibernate
Then reload the configuration:
bash
sudo systemctl restart systemd-logind

3.
Using pm-utils or uswsusp (Older Tools)

In some older Linux distributions, pm-utils or uswsusp are common tools used to manage power and suspend.

Suspend to RAM:

bash
sudo pm-suspend
Suspend to Disk:

sudo pm-hibernate

4.
Using TLP Tool for Power Management

TLP is a Linux power management tool that automatically configures many power optimization options. Once installed and configured, TLP will manage deep suspend and other features based on your hardware.

bash
sudo apt install tlp

5.Checking Power Management Services
If your system encounters issues while entering deep suspend, you can check the power management services to diagnose the problem. For example, check the systemd power management logs:
journalctl | grep suspend

mfornasa

Beelink CS-Ian Chan

Sorry, but this is not helpful. Providing generic ChatGPT-like responses does not address the issue.

Configuring Deep Suspend Mode (Hibernate)

First, “deep suspend” is not the same as hibernate. Hibernate is suspend-to-disk, while “deep suspend” is suspend-to-RAM (see: https://www.kernel.org/doc/Documentation/power/states.txt). Hibernate works correctly on my SER9.

If your system encounters issues while entering deep suspend, you can check the power management services to diagnose the problem. For example, check the systemd power management logs:

Again, this is not useful. A detailed analysis has already been done with a kernel developer assistance (see:https://gitlab.freedesktop.org/drm/amd/-/issues/4519).

At this point, the possibilities are clear:

It’s a BIOS issue (as suggested in the AMD report), or
It’s not.

The problem can be reproduced very easily: just install Linux on a SER9 HX370. If suspend works, then it’s not the BIOS.

Therefore, I will not continue “trying things” unless Beelink can provide clarity. Can you confirm that suspend works on your end? If so, please share the Linux distribution, version, and configuration details. If suspend does not work, please share your plan: either provide a timeline for a fix, or state explicitly that it cannot/won’t be fixed, if it’s not a priority. Either works for me. Not trying things randomly.

Thanks.

Beelink CS-Rose

mfornasa
Sorry for inconvenience to you.

Please contact after-sales service for repair or replacement of the device: support-pc@bee-link.com

mfornasa

Beelink CS-Rose Thanks for the option. I am keeping it, I like the machine!
Hope that future BIOS can fix this.

« Previous Page Next Page »