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

    Please check your private message.

    support1
    And what BIOS version should I use when my SER9 SN starts at BHX374BF….? You only list Y and D, but I have B. I tried emailing, but I see you’re ragging more here. Thank you.

        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

            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?

            ps, thank you to everyone who is working to make this product better. @brk they are responding to emails too, and quite responsively

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

            • brk replied to this.

                support1
                Image description
                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.

                    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.

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

                          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

                          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.

                          gukin
                          Hello,

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

                          Best regards!
                          Wendy
                          Customer Support 

                            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

                            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.

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

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

                                    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