Linux on SER9.
- #80
ximejo
https://dr.bee-link.cn/?dir=uploads%2FSER%2FSER9--AI-9-HX-370%2FBIOS
pls contact to bee-link support team to confirm latest bios match your device
- #81
Someone check my work, but I applied the December 23rd BIOS update from Beelink and the linux-firmware 20241210 seems to now be working. I’m on NixOS and I checked that the hash of dcn_3_5_dmcub matches the latest firmware and NOT August’s.
➤ sha256sum /nix/store/r788ivyw8dawqpq0x3ms3zp7dkvgx7wx-linux-firmware-20241210-zstd/lib/firmware/amdgpu/dcn_3_5_dmcub.bin.zst
117d4210b97cfb2aae72818b25d3f05a57be72e51522ab436cebe7ea3a9f1d2f /nix/store/r788ivyw8dawqpq0x3ms3zp7dkvgx7wx-linux-firmware-20241210-zstd/lib/firmware/amdgpu/dcn_3_5_dmcub.bin.zst
➤ sha256sum /nix/store/qsg866lkgibias5s5078bgsf3h7a97a7-linux-firmware-20240811-zstd/lib/firmware/amdgpu/dcn_3_5_dmcub.bin.zst
d6b1d0a45909d702146b993c69c66fdc368b32687fe3bdfd0b6c1eef73f2b247 /nix/store/qsg866lkgibias5s5078bgsf3h7a97a7-linux-firmware-20240811-zstd/lib/firmware/amdgpu/dcn_3_5_dmcub.bin.zst
➤ sha256sum /run/booted-system/firmware/amdgpu/dcn_3_5_dmcub.bin.zst
117d4210b97cfb2aae72818b25d3f05a57be72e51522ab436cebe7ea3a9f1d2f /run/booted-system/firmware/amdgpu/dcn_3_5_dmcub.bin.zst
And then
➤ sudo lsmod | grep ^video
video 81920 1 amdgpu
- #82
I noticed a BIOS update on the bee-link site for the SER9 dated December 23 2024 and blindly gave it a shot, what could possibly go wrong?
Paired with the 20241210 firmware, my SER9 came up and worked correctly with GravityMark (vk, gl and vk-rt) and I was able to launch Batman Arkham Knight without issue. So far things look VERY promising.
I did try Ubuntu 24.10 in live mode and the system booted off USB and came up correctly, I also ran GravityMark (vk, gl and vk-rt) successfully. The only area of concern was that the system hung when shutting down. When running the new BIOS and 20241210 firmware I did not have the hang during shutdown.
I’m heartened to see the progress being made on getting Linux and the SER9 to play nicely with one another.
- #83
Just updated to that new 23rd December BIOS and I was able to install Fedora 41 without a problem. So far so good
- #84
Can confirm.
No issues with the latest AMD firmware on Arch Linux after BIOS update.
- Edited
- #86
edwardo https://dr.bee-link.cn/?dir=uploads%2FSER%2FSER9--AI-9-HX-370%2FBIOS
But there are two versions of BIOS, you need download the correct one,otherwise it will brick your PC.
Please check your SN first.
①SER9-Version1-SN-starts-with-Y-V103-Note-Original-version
②SER9-Version2-SN-starts-with-D-T103-Note-Original-version
- #87
edwardo
This is the link I used: https://dr.bee-link.cn/?dir=uploads%2FSER%2FSER9--AI-9-HX-370%2FBIOS
From the above note from support, the BIOS update is only for the Y-series SER9s right now, however another person tried the D on his Y and the system reported that BIOS was incompatible, nevertheless, be sure what you’re doing before applying a BIOS.
Your SN is on a sticker on the bottom but if you’re like me, and I know you are, you can use “sudo dmidecode” to retrieve your SN. Again, be careful because on mine, which is a Y-series, the serial number under “System Information” comes back as YHX37…… while under Base Board Information it reads D9DS0……. I believe that the “System Information” serial number is what you’re after.
The new BIOS is working out extremely well, on heavy games like Robocop Rogue City, the graphics are faster, smoother and clearer. Also I would occasionally be greeted with a solid green screen when changing resolutions or coming out of sleep but with the new BIOS and firmware, that hasn’t happened.
Thank you for the update gentle support entity, please make a note on the BIOS download page that there are Y-series and D-series SER9s and never the two should mix BIOS updates.
- #88
Huh? I’m confused about this firmware update: my serial number is “YHX734AH90263”. I don’t understand the comments above from Beelink support:
"①SER9-Version1-SN-starts-with-Y-V103-Note-Original-version
②SER9-Version2-SN-starts-with-D-T103-Note-Original-version"
How does that match up with what I have? What is this “V103” and “T103” ?
- Edited
- #90
support1 I am unsure of which files to use.
In this folder:
https://dr.bee-link.cn/?dir=uploads%2FSER%2FSER9--AI-9-HX-370%2FBIOS%2F
There are a lot of files dated December 12 and December 23. Then there are two subfolders:
SER9-Version1-SN-starts-with-Y-V103-Note-Original-version
SER9-Version2-SN-starts-with-D-T103-Note-Original-version
Inside are files dated December 20. I do not see clear version numbers in the naming scheme.
Also, I cannot find a clear link to support files for the SER9 from the beelink main website. I only found this folder from previous comments here in this thread.
Considering one might brick their PC, I think these folders need to be cleaned up so that there is no possible way someone might choose the wrong file. I will await your reply before trying anything.
Best regards
[unknown]
Sorry, I found finally the link from the home page to the download server. It is still a bit cluttered though, so I wish to get some clear understanding. Maybe some of these files should be deleted..?
- #91
Please check your private message.
- #93
brk I also have a BHX-prefixed SER9 and used https://dr.bee-link.cn/uploads/SER/SER9--AI-9-HX-370/BIOS/SER9-V103_15_68_Y.zip. Unfortunately, that no longer seems to exist, but I think it points to the V103 BIOS downloads being appropriate.
I think the one I used was renamed to https://dr.bee-link.cn/uploads/SER/SER9--AI-9-HX-370/BIOS/SER9-V103_15_68_Y-for-solving-the-blue-screen-problem-when-inserting-the-graphics-card-into-the-expansion-dock.zip.
Specifically, SMBIOS shows this after my upgrade to the December 23rd update (not sure why BIOS shows December 13th… typo?):
BIOS Information
Vendor: American Megatrends International, LLC.
Version: STX.3xx.SER9.V103.P8C0M0C15.68.Link.GID.Linux_kimi_v1
Release Date: 12/13/2024
- Edited
- #94
Hello, my update:
I am using Proxmox VE 8.3.2 (which is the latest release).
Y-V103 new firmware (for Yxxxxxxxxxxx serial numbers) works for Linux kernel 6.8.12-4-pve, but not 6.8.12-5-pve (“pve” means it is customized for their virtual environment software). The latter is the default for this version of Proxmox, but it’s easy enough to default to 6.8.12-4-pve. Future versions of Proxmox VE 8 (8.4) are expected to continue to default to 6.8.12-5-pve, though there is an option currently to opt-in and test kernel 6.11. Proxmox VE 8.4 will be the last before PVE 9, most likely, which is expected later in 2025, and it should use kernel 6.11 if my research is correct.
I have tried just now kernel 6.11.0.2-pve and it also does not work unfortunately, same black screen - monitor is alive, but screen is black. Nomodeset allows boot. So for now I am forced to use 6.8.12-4-pve
You guys who mentioned Ubuntu 2024.10, it looks like it uses kernel 6.11, can you confirm the specific version that works for you?
- #97
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.
- Edited
- #98
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.