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.

      thank you for your sharing.

      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 2100 single core performance which is 700 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.

      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.

      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

      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.

        5 days later

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

          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.

          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.

            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.