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.

support4 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.

support6

mfornasa
Regarding your question we had it tested by the relevant staff.
We do reproduce the problem. It should be the system incompatibility issue. We suggest you change it to Ubuntu.

mfornasa

support6 can you confirm that you tested it on Ubuntu and the suspend works there? If so, can you provide the exact Ubuntu version?

support10

mfornasa

Hello there,

Yes, our technicians have tested that it works properly on the Ubuntu system.

We suggest that you install Ubuntu23.04 or 24.04 versions.

Have a nice day!

mfornasa

support10 I tried to boot a Ubuntu 24.04 from the a USB stick.
Network works correctly at startup. I hit “suspend” -> suspensions last 5 seconds, network stops working. Same behaviour that I was observing on another Linux distribution (Arch).

support6

mfornasa
The SER9’s AMD Ryzen AI HX370 platform uses Modern Standby (S0ix), a low-power state where the system remains partially active to enable fast wakeups. Unlike traditional S3 sleep (which powers down most hardware), S0ix requires strict driver and firmware compatibility for reliable operation. This explains why:
Network interfaces fail: Wi-Fi/Ethernet adapters may not properly enter/exit low-power states.
Random wakeups occur: Misconfigured wake sources (e.g., USB devices, RTC timers) can trigger premature resumptions.
Hard resets are needed: Some hardware components (like Wi-Fi radios) may require full power cycling to recover from S0ix inconsistencies.
You can try: Add mem_sleep_default=deep to grub and rebuild the initramfs:
bash
sudo update-grub && sudo mkinitcpio -P

Metro

Hi, been reading this chat as I would be interested in installing Linux on a Beelink SER9 Pro AMD Ryzen AI 9 HX 370. I’m looking to get one. Haven’t bought it yet.

My question is are all these bios updates and solutions only for the 64GB model to get Linux to boot properly? Is there a solution for the 32GB model? I was looking at the 32GB model just from the cost perspective.

And also, someone mentioned the 2TB storage is actually two 1TB. Anyway to install windows on just one stick ?

Thank you.

support6

Metro
BIOS updates and troubleshooting are related to the BIOS version. They are not related to 32GB or 64GB.
One SSD is the system drive, and the other is the storage drive. The system drive comes pre-installed with Windows 11 PRO.

mfornasa

support6
It appears that the hardware is not advertising the deep mode. It there a way a way to activate it, perhaps a boot option?

$ cat /sys/power/mem_sleep
[s2idle]

support7

mfornasa
Are you talking about booting from ssd?

Please press delete key as soon as you restart the PC, so that you can go to BIOS. Then go to boot page, set SSD as the first option.

mfornasa

support7 No. I am saying that it appears that the “deep” mode suggested by @support6 is not made available by the machine

support4

mfornasa
Hi ,there
See if you can go into Deep mode by disconnecting internal speaker or uninstall speaker driver.

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

support4

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

support4
I already gave SN right?
sn:BHX375IG60046

Image description

support6

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

« Previous Page