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?

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.

Oligon

Image description
Here is the “screenshot”.
The other file has a readme that in Chinese only and I somehow did not feel addressed with that one…

It says:
!! U盘格式FAT32
文件拷贝到根目录下后U盘启动自动进行烧录；

darkstorm331

I was able to update the BIOS with the “SER9_V103_P8C0M0C15_65_15_65_Y_2024-11-20_7-28-53.zip” files and then I tried to boot into Fedora Workstation 41 usb but get the same black screen issue.

gukin

I too updated my BIOS with SER9_V103_P8C0M0C15_65_15_65_Y_2024-11-20_7-28-53.zip, installed linux-firmware-20241110, rebooted and . . . my system hung on initializing amdgpu. Here’s the first few lines from “dmidecode”:

BIOS Information
Vendor: American Megatrends International, LLC.
Version: STX.3xx.SER9.V103.P8C0M0C15.65.Link.GID.90.MBT
Release Date: 11/18/2024
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 32 MB

At least Beelink is trying, and their BIOS worked and we still have 20240811 to fall back on.

Oligon

Confirming the “SER9_V103_P8C0M0C15_65_15_65_Y_2024-11-20_7-28-53.zip” BIOS update worked for me as well.
Process was simular, but no message/warning - the process once booted from stick just performs with no interaction needed.

support6

thank you for your sharing.

theflakes

I have Linux Mint 22 running on it with the latest BIOS (not sure it matters though). Booted install in compat mode. Then rebooted after install and edited kernel startup params to “nomodeset” replacing “quite splash” by hold ingshift key down on boot. Then used mainline to install the latest kernel and ran all updates. Then rebooted and no black screen.

Latest kernel isn’t scheduling processes on the hybrid architecture efficiently. Geekbench6 shows ₂₁₀₀ single core performance which is ₇₀₀ lower than Win 11. I also changed the pstate driver to “amd_pstate=active”, but didn’t make any performance difference.

I did have a boot problem on the first reboot after install and I had to boot back to the live ISO and do a disk repair using boot-repair.

bungle

I also upgraded BIOS. That went fine, but the issue is still there. Doesn’t bother me too much as I am using this as a headless server.

lukexi

Hi support staff! Just wanted to check in on this — have you been able to get in touch with AMD’s engineers regarding this issue? Mario Limonciello, technical staff at AMD believes this is a BIOS issue with the SER9 and can advise on specific details. You can contact him at mario.limonciello@amd.com or via the thread investigating the issue at https://gitlab.freedesktop.org/drm/amd/-/issues/3744#note_2666260

gukin

I checked with Mario and he said that the problem is squarely on Beelink:

FWIW we did manage to track down one of these and dig into the exact details of what is wrong. Their BIOS isn’t configuring muxes properly, and it causes a hang in DCN.
The DMCUB firmware that is loaded to DCN hardware isn’t unique to Linux, it’s the exact same binary used by Windows as well and thus a Windows driver with the same DMCUB firmware binary will also be affected.
The proper solution is for them to fix the BIOS.

So the SER9 is broken as it comes and their primary customers, windows users, are vulnerable as well; an update could leave lots and lots of SER9 users even more broken than we Linux users are finding ourselves.

Keep an eye out for BIOS updates in the chance that Beelink makes a fix for the SER9.

Bienenhalm

gukin

Windows users are definitely the primary target, but I wanted to mention that there is at least one YouTube video that claims that Linux (Bazzite, so probably Fedora 41?) runs flawlessly on the SER9:

I assume he lucked out and hit just the right firmware version when doing the video. Anyway, I wouldn’t be surprised if more people will buy this as a Linux computer over time.

Ordered one for work (=Linux) before finding this thread, I hope it’s not a major engineering effort to adjust the firmware.

support1

Hi there ,

Our R&D are still testing linux on SER9, if any news ,we will let you know.

VasqueZ

Hello, I also have a Beelink SER9, how can I update the BIOS on it, please tell me.

gukin

VasqueZ

On the BIOS download page for the SER9 is a document called “ Use-USB-to-flash-BIOS-SER9T103_2024-11-20_8-38-22.docx”, it lays out the steps you will need to take to flash the BIOS. It worked for me although it didn’t do anything for the firmware problem under Linux.

support1

Update： We have talked with AMD. AMD is also working on it, they are trying to debug .Currently , AMD is updating the codebase verification. We will see if have more news this week.

@VasqueZ
Before you flash the BIOS, please contact our support.

gukin

support1
That’s great news, I’ve found some instabilities in Xorg as well with x0vncserver (from tigervnc) which seems to cause the whole system to reboot BUT if the firmware problem gets worked out, then strix-point and strix-halo (AI Ryzen 390 AI HZ AI AI AI AI) are much more likely to be successes on minis as well as hand helds. Thank you support folks for sticking with this.

support6

you will be updated if there has any news.

gukin

Has there been any progress on getting the SER9 BIOS fixed so that the firmware workaround isn’t necessary any more?

support1

Hi there,

I just check with our R&D, no news yet.
We will keep you updated once any news.

gukin

It looks like the minisforum elitemini AI370 has the same problem as the SER9, at least according to a recent entry in the thread on freedesktop.org (https://gitlab.freedesktop.org/drm/amd/-/issues/3744#note_2666260):

The exact same issue happens on a minisforum elitemini AI370, they might share the same BIOS software.

Mario L. from AMD suspects that the muxes were incorrectly programmed on the elitemini as well.

I do hope there is a solution to this problem, not everyone wants a laptop or a handheld.

support10

Hello there，

Our R&d personnel are still testing, at present can not determine whether it is a BIOS problem.

Please wait patiently.

Have a nice day!

« Previous Page Next Page »