There is also a discussion in the linux-firmware git. The developers confirmed there that the issue can’t be reproduced on their device which is a Zenbook S16 which is also based on Strix Point like the SER9. So it looks more and more like a problem specific to the SER9. This is now further confirmed with the Minisforum Device from the Video.

See the discussion here:
https://gitlab.freedesktop.org/drm/amd/-/issues/3744

gukin Hi there,

Where do you get the linux-firmware-20241110 and dcn_3_5_dmcub.bin ?
Please send us a link for download .
We will test it.

      All the links are in the thread and might be distro dependent.
      The dcn_3_5_dmcub.bin file is part of every linux-firmware release and is located in the /usr/lib/firmware/amdgpu/ folder.
      Only the file from the 20240811 release is working with SER9.
      You can always start your testing with the latest ubuntu 24.10 iso.

      support1

      You get the firmware from here:

      https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
      or just do a wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20241110.tar.gz

      From there you do a tar fxva linux-firmware-20241110.tar.gz linux-firmware-20241110/amdgpu/dcn_3_5_dmcub.bin
      Then you just sudo cp linux-firmware-20241110/amdgpu/dcn_3_5_dmcub.bin /usr/lib/firmware/amdgpu/dcn_3_5_dmcub.bin

      Presuming you are running linux 6.10+ and have mesa 24.2+ you should be rewarded with a black screen and a non-booting SER9

          Follow similar instructions on the linux-firmware-20240811 to get the working dcn_3_5_dmcub.bin.

          The thread above on gitlab.freedesktop.org seems to indicate that it’s a BIOS bug; at least we have a workaround.

          Just was offered a new Firmware via the Update Manager in Linux Mint.
          Updated to Kernel 6.8.0-49.49 and Firmware 20240318.git3b128b60-0ubuntu2.5

          And it works without the need to downgrade “dcn_3_5_dmcub.bin” again to the older and so far only working solution.

            Oligon

            I doubt you have hardware acceleration, the 890m requires the 6.10 or later kernel and mesa 24.2 or later.

            Can you run “vkcube”? It won’t run on my system without hardware acceleration complaining about DRI3 missing.

            If you run "glxinfo | grep renderer, do you get something like this:
            OpenGL renderer string: AMD Radeon Graphics (radeonsi, gfx1150, LLVM 19.1.3, DRM 3.59, 6.12.0)
            or do you get something like this:
            OpenGL renderer string: llvmpipe (LLVM 15.0.6, 256 bits)

            The former is hardware acceleration but the latter is only software acceleration which is a disappointment considering the formidable power of the 890m video adapter.

              Oligon ha, no prob. I’m in one of my “try linux again” cycles. going really well this time on this ser9. But here I am, back searching for answers to a new graphics problem. Fun to come across this thread and your credit. Happy I could help!

                  I just realized that a new SER9 BIOS is available. But there are two different files which should we use? Also any Infos on what changed?

                  locuester
                  Since you’re not overly attached to any one Linux distribution, like I am (Mageia), you should give one of the fancy rolling distributions a shot: Endeavior, Fedora, Bazzite, Manjaro which should all have new enough packages to make use of your SER9.

                  Speaking of things, I noticed that Beelink released a BIOS update on 11/20/2024 which I’m going to give a try, perhaps it could fix the firmware problem and this thread could just float away in the river of time.

                  [unknown]

                  SER9_BIOS_Update_55_2024-09-27_8-27-04.zip <- This is the old BIOS file with the windows rubbish as well as the USB stuff.
                  SER9T103_D_2024-11-20_8-21-08.zip <- This is the new BIOS with only the USB installation goodies dated 2024-11-20.

                  I asked support if it was okay to patch my SER9 with this BIOS since they suggested we do so; thus I haven’t applied this BIOS yet but I’m hopeful it’ll fix the firmware problem.

                  [unknown]

                  SER9_BIOS_Update_55_2024-09-27_8-27-04.zip <- This is the old BIOS file with the windows rubbish as well as the USB stuff.
                  SER9T103_D_2024-11-20_8-21-08.zip <- This is the new BIOS with only the USB installation goodies dated 2024-11-20.

                  I asked support if it was okay to patch my SER9 with this BIOS since they suggested we do so; thus I haven’t applied this BIOS yet but I’m hopeful it’ll fix the firmware problem.

                  [unknown]

                  SER9_BIOS_Update_55_2024-09-27_8-27-04.zip <- This is the old BIOS file with the windows rubbish as well as the USB stuff.
                  SER9T103_D_2024-11-20_8-21-08.zip <- This is the new BIOS with only the USB installation goodies dated 2024-11-20.

                  I asked support if it was okay to patch my SER9 with this BIOS since they suggested we do so; thus I haven’t applied this BIOS yet but I’m hopeful it’ll fix the firmware problem.

                    Downloaded “SER9T103_D_2024-11-20_8-21-08.zip” put it on a 32GB USB stick formated FAT32 and named it “WINPE” as instructed.
                    It did boot nicely.
                    But after reading the bios it prompted me with the following:
                    The ROM file information does not match the system BIOS!
                    If forcedly update BIOS, it may destroy the System BIOS!
                    We strongly do not suggest to flash the BIOS!

                    As this naturally scared me s**tless :D I followed the advice and did not flash^^

                      Oligon It seems there are 2 potential files. There’s that one and then there’s “SER9_V103_P8C0M0C15_65_15_65_Y_2024-11-20_7-28-53”

                        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盘启动自动进行烧录；

                        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.

                        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.

                        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.