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 .

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?

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.

support1

brk Could you please send us a picture of SN on the bottom of the PC ?

brk

support1
Image description

Support-pc@bee-link.com says that this is the latest BIOS version, but in this forum versions from 12 and 23 December are also referenced. So I don’t know if it is the latest or not.

support1

brk Hi there,

Your SN starts with B, also use the same BIOS file the same as Y.

https://dr.bee-link.cn/index.php?dir=uploads%2FSER%2FSER9--AI-9-HX-370%2FBIOS%2FSER9-Version1-SN-starts-with-Y-or-B-V103-Note-Original-version
Image description

kbcat1

benkrieger

What are you using to get that version data exactly? When I look at the bios version using powershell or with msinfo32, the full text is this:

STX.3xx.SER9.V103.P8C0M0C15.65.Link.GID.90.MBT, 11/18/2024

This is what Beelink Support told me to use, a direct link in email. My serial number starts with Y. It’s starting to look like I was told to install the previous available version, as it is clearly different from the one you quoted just now (“15_68” vs “15_65”). Based on being told to use this file, I assumed V103 was a version designation. But maybe it refers to the hardware, and 15.xx is the version.

Can you confirm the one in the root folder here is correct:
https://dr.bee-link.cn/?dir=uploads%2FSER%2FSER9--AI-9-HX-370%2FBIOS
There is a file named “ SER9-V103_15_68_Y-for-solving-the-blue-screen-problem-when-inserting-the-graphics-card-into-the-expansion-dock.zip”

I assume it is correct but I complained about the clutter of this folder and apparently I had good reason to, so I am just being cautious. This is not a great system to disseminate bios updates. There should never be a way to get the wrong firmware on accident.

support1

kbcat1 ! Hi there, your SN starts with Y, so please download the file as the picture. Image description
https://dr.bee-link.cn/index.php?dir=uploads%2FSER%2FSER9--AI-9-HX-370%2FBIOS%2FSER9-Version1-SN-starts-with-Y-or-B-V103-Note-Original-version

brk

support1 Thank you, after updating the BIOS it is now booting correctly.

Oligon

Ser9 user with a Y model here. Took a bit of extra time to confirm my personal outcome - but I have updated successfully to this supposed “linux solution” version 68 BIOS.
Now my system which worked with the workaround old Firmware from August does not work with ether.
Both old firmware and newest, if booted result in a black screen and freeze under Mint.
Downloaded the latest Mint ISO and booted from the stick fresh with the new BIOS does result for me in a freeze at the Mint Logo.
My only workaround now is back to the compatibility mode with zero gpu acceleration.
So in summery, for me things got worse…..

gukin

Oligon

The last time I checked, Mint does not have the 6.10 or later kernel, thus it won’t initialize the 890m correctly. If you try ubuntu 24.10, Fedora 41, Manjaro or any of the recent rolling Linux distributions, you should have better luck.

darkstorm331

I am getting an intermittent issue on the new firmware where my second monitor goes black but is still detected by Linux. Afterwards I see the below crash reported in the logs.

Image description

kbcat1

Hi ok using the 15_68 version, now all of my linux kernels are booting without nomodeset. Thanks. I’ll report if I notice any other issues.

support6

gukin
Hello,

Okay, we will update the download page with a note.

Best regards!
Wendy
Customer Support

tenninjas

I checked my SN and it starts with C … my current BIOS version is V103 15_65; so could someone confirm that flashing the ‘Start with Y V103’ version is correct?

Oligon

gukin That was the issue indeed. Thanks so much!

Did not want to go the full way and reinstall with Ubuntu just yet, so I installed the Mainline Kernels package and pushed my Mint to 6.12.3-061203-generic.
And it came right up in a straight and extremely fast boot.
Unsure if it has any other side effects, I am almost sure of it.
But for now at least I am no longer running in compatibility mode :)

Wishing You all a good ride into the next year.
See Ya in 2025

(EDIT: For the first time -> Ser9 now is able to come back from power settings, both black screen and suspend work as they should.)

brk

What speeds do you achieve with SSDs in Linux?
The drive is identified as: CT1000P3PSSD8
Which corresponds to: Crucial P3 Plus 1TB PCIe M.2 2280 SSD
Sequential read speed should be 5 GB/s, but I am only getting 1.7 GB/s.

$ sudo dd if=/dev/disk/by-path/pci-0000:61:00.0-nvme-1 of=/dev/null bs=8192 count=1048576
1048576+0 records in
1048576+0 records out
8589934592 bytes (8.6 GB, 8.0 GiB) copied, 5.02471 s, 1.7 GB/s

Ford

Any update on when a new BIOS version will be released for the “version 2” boards?

I’d also be interested to know of the differences between board versions, as if this version is not going to be receiving the same level of support then I’d be tempted to return my device.

support1

Ford Hi Ford,

We are still working on it for the Version 2. If any news, we will update in this forum.

Ford

support1 Any updates?

DrMindControl

I experienced the black screen issue when tried to install Linux, first Kubuntu, then KDE Neon, here is what I did to fix it and it works.

First step is to update the BIOS as explained here

> [](https://dr.bee-link.cn/?dir=uploads%2FSER%2FSER9--AI-9-HX-370%2FBIOS)

> [](https://dr.bee-link.cn/uploads/SER/SER9--AI-9-HX-370/BIOS/Use-USB-to-flash-BIOS-SER9-V103_15_68_Y.pdf)

Download the SER9-V103_15_68_Y-for-solving-the-blue-screen-problem-when-inserting-the-graphics-card-into-the-expansion-dock.zip file and flash it as explain in the PDF above.

Above are the links for the SER9 with serial numbers starting with Y, mine was like this, bottom of the computer you can read it, there is a label.

Then just plug-in the USB and when you boot the flashing process will start automatically, at least this was the case with me, wait to finish and reboot.

Second step is when you boot the linux installation iso to select the nomodeset safe graphics mode when asked, thus you will be able to boot without experiencing the issue, after step 3 you can switch to normal mode graphics.

Third step is to INSTALL the specific linux kernel dynamic AMD drivers, boot as pointed out in step two.

Make sure you have the linux-headers package installed, dkms and build-essential packages installed!

On my system KDE neon I had them all installed by default, example is the linux headers package below, just in case check for your specific case.

~# dpkg -l | grep linux
ii  binutils-x86-64-linux-gnu                     2.42-4ubuntu2.3                                        amd64        GNU binary utilities, for x86-64-linux-gnu target
ii  console-setup-linux                           1.226ubuntu1                                           all          Linux specific part of console-setup
ii  cpp-13-x86-64-linux-gnu                       13.3.0-6ubuntu2~24.04                                  amd64        GNU C preprocessor for x86_64-linux-gnu
ii  cpp-x86-64-linux-gnu                          4:13.2.0-7ubuntu1                                      amd64        GNU C preprocessor (cpp) for the amd64 architecture
ii  g++-13-x86-64-linux-gnu                       13.3.0-6ubuntu2~24.04                                  amd64        GNU C++ compiler for x86_64-linux-gnu architecture
ii  g++-x86-64-linux-gnu                          4:13.2.0-7ubuntu1                                      amd64        GNU C++ compiler for the amd64 architecture
ii  gcc-13-x86-64-linux-gnu                       13.3.0-6ubuntu2~24.04                                  amd64        GNU C compiler for the x86_64-linux-gnu architecture
ii  gcc-x86-64-linux-gnu                          4:13.2.0-7ubuntu1                                      amd64        GNU C compiler for the amd64 architecture
ii  libselinux1:amd64                             3.5-2ubuntu2                                           amd64        SELinux runtime shared libraries
ii  libv4l-0t64:amd64                             1.26.1-4build3                                         amd64        Collection of video4linux support libraries
ii  libv4lconvert0t64:amd64                       1.26.1-4build3                                         amd64        Video4linux frame format conversion library
ii  linux-base                                    4.5ubuntu9                                             all          Linux image base package
ii  linux-firmware                                20240318.git3b128b60-0ubuntu2.6                        amd64        Firmware for Linux kernel drivers
ii  linux-generic                                 6.8.0-51.52                                            amd64        Complete Generic Linux kernel and headers
ii  linux-generic-hwe-24.04                       6.8.0-51.52                                            amd64        Complete Generic Linux kernel and headers
ii  linux-headers-6.8.0-51                        6.8.0-51.52                                            all          Header files related to Linux kernel version 6.8.0
ii  linux-headers-6.8.0-51-generic                6.8.0-51.52                                            amd64        Linux kernel headers for version 6.8.0 on 64 bit x86 SMP
ii  linux-headers-generic                         6.8.0-51.52                                            amd64        Generic Linux kernel headers
ii  linux-headers-generic-hwe-24.04               6.8.0-51.52                                            amd64        Generic Linux kernel headers
ii  linux-image-6.8.0-51-generic                  6.8.0-51.52                                            amd64        Signed kernel image generic
ii  linux-image-generic                           6.8.0-51.52                                            amd64        Generic Linux kernel image
ii  linux-image-generic-hwe-24.04                 6.8.0-51.52                                            amd64        Generic Linux kernel image
ii  linux-libc-dev:amd64                          6.8.0-51.52                                            amd64        Linux Kernel Headers for development
ii  linux-modules-6.8.0-51-generic                6.8.0-51.52                                            amd64        Linux kernel extra modules for version 6.8.0 on 64 bit x86 SMP
ii  linux-modules-extra-6.8.0-51-generic          6.8.0-51.52                                            amd64        Linux kernel extra modules for version 6.8.0 on 64 bit x86 SMP
ii  linux-sound-base                              1.0.25+dfsg-0ubuntu7                                   all          base package for ALSA and OSS sound systems
ii  linux-tools-6.8.0-51                          6.8.0-51.52                                            amd64        Linux kernel version specific tools for version 6.8.0-51
ii  linux-tools-6.8.0-51-generic                  6.8.0-51.52                                            amd64        Linux kernel version specific tools for version 6.8.0-51
ii  linux-tools-common                            6.8.0-51.52                                            all          Linux kernel version specific tools for version 6.8.0
ii  pptp-linux                                    1.10.0-1build4                                         amd64        Point-to-Point Tunneling Protocol (PPTP) Client
ii  util-linux                                    2.39.3-9ubuntu6.1                                      amd64        miscellaneous system utilities
ii  util-linux-extra                              2.39.3-9ubuntu6.1                                      amd64        interactive login tools

Next just install amdgpu-dkms package as shown below, this will install and the amdgpu-dkms-firmware package, make sure the repo is edited correctly in the echo command, mine was noble, because KDE neon is actually ubuntu noble.

Checking what version of linux you have

# lsb_release -a
No LSB modules are available.
Distributor ID: Neon
Description:    KDE neon 6.2
Release:        24.04
Codename:       noble

Installing amdgpu-dkms

echo "deb [arch=amd64 signed-by=/etc/apt/keyrings/rocm.gpg] https://repo.radeon.com/amdgpu/latest/ubuntu noble main"     | sudo tee /etc/apt/sources.list.d/amdgpu.list
apt update
apt install amdgpu-dkms

Command above will compile the AMD driver inside the kernel and when you reboot the issue is gone. Upon installing a new kernel, dkms will rebuild the driver with the new kernel automatically.

You can confirm things running the command below.

~# dkms status
amdgpu/6.10.5-2095006.24.04, 6.8.0-51-generic, amd64: installed

That’s it! You will have a working linux installation.

michael

Just letting the forun know that once I updated the BIOS of my new SER9, the latest version of Manjaro Cinnamon loaded and booted up correctly. I have been using it all day every day since with no issues at all - rock solid and stable… 👍

ximejo

Testing with endeavourOS:

dmidecode 3.6

Getting SMBIOS data from sysfs.
SMBIOS 3.7.0 present.
Table at 0×78254000.

Handle 0×0000, DMI type 0, 26 bytes
BIOS Information
Vendor: American Megatrends International, LLC.
Version: STX.3xx.SER9.V103.P8C0M0C15.68.Link.GID.Linux_kimi_v1
Release Date: 12/13/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

Everything works fine for now with no crashes.

support6

ximejo
Hello,

I am glad to hear that.

Best regards!
Wendy
Customer Support

ximejo

Hello,

Thank you for your advice.
We will feedback to the relevant personnel.

Best regards!
Wendy
Customer Support

[unknown]
Hello,

Thank you for your advice.
We will feedback to the relevant personnel.

Best regards!
Wendy
Customer Support

« Previous Page Next Page »