Linux on SER9.

gukin

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/

support4

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 !

ximejo

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.

gukin

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.

ximejo

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.

support4

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 .

gukin

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

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?

gukin

I don’t know about uploading a picture but here’s the output from “dmidecode”:

SMBIOS 3.7.0 present.
Table at 0×78256000.

Handle 0×0000, DMI type 0, 26 bytes
BIOS Information
Vendor: American Megatrends International, LLC.
Version: STX.3xx.SER9.V103.P8C0M0C15.54.Link.GID
Release Date: 09/10/2024
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 32 MB
Characteristics:

It would be nice to be able to use a more up to date amdgpu firmware.

ximejo

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

gukin

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.

Oligon

Good day - absolut Linux noob here who got the Ser9 to learn and move away from Windows 11

Now I ran into the same issue and I am glad to finally found this thread.
I am currently running Linux Mint and can only boot the system on the Ser9 in Recovery mode, or I have the same black screen and freeze.
Now I got You that a downgrade to linux-firmware 20240811 would at least temporarly fix the issue.
But I was unable to figure out how to perform the downgrade. I found and downloaded “linux-firmware20240811.tar.gz” from git repository but now what?
Can someone explain the process, or point me towards a tutorial ?

Thanks in advance

Oligon

Got it resolved! By shoutout to EDIT1:locuester on reddit! You mad genuis.
Guy on reddit said he resolved it by removing all packages that contain “amdgpu*” via package manager - then reinstall the latest AMD driver.
So I did and it works ! (Without any Liniux-Firmware downgrade)

EDIT2: new problem no sound in any proton or Wine emulated game in Steam or Heroic Game launcher 😃
Linux is such an adventure! 🙂

support4

Oligon
HI thanks for your efforts

Please try this :
Step 1: Check Audio Settings
System Settings: Go to your Linux Mint audio settings and make sure the correct output device is selected.
Steam Settings: In Steam, go to Settings > Audio and ensure the right device is set there too.
Step 2: Verify Wine and Proton Settings
Wine Configuration: You can open winecfg from the terminal to check audio settings. Make sure the audio driver (like ALSA or PulseAudio) is correctly set up.

bash
winecfg
Proton Settings: In Steam, right-click on your game, go to Properties, and under Compatibility, try enabling the Steam Play for all other titles.

Step 3: Install Additional Packages
Sometimes, certain audio packages might be missing. You can install the following packages:

bash
sudo apt install pavucontrol pulseaudio
After installing, run pavucontrol (PulseAudio Volume Control) and check if the game is outputting sound to the correct device.

Step 4: Update Proton and Wine
Ensure you’re using the latest versions of Proton and Wine. You can do this from the Steam settings or by checking for updates in your package manager.

Step 5: Test with Different Games
Sometimes specific games might have their own issues. Try testing with different games to see if the problem persists across the board.

ximejo

Oligon
What is your current linux-firmaware?

locuester

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!

Oligon

I suppose it’s this?

via:
dpkg-query –list linux-firmware

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-===============================-============-=================================
ii linux-firmware 20240318.git3b128b60-0ubuntu2.4 amd64 Firmware for Linux kernel drivers

@support4 thanks for the tips 🙂 got sound from Wine GE yesterday. Did a short test with Skyrim.
Still tinkering with Proton. I am careful with the PulseAudio stuff, as I understand that the latest Linux Mint “Wilma” has switched to “Pipewire” so I don´t know how much these are still relevant.

I sadly can also confirm a bug that this solution has, when the system is idle for a while and even after turning standby to “never”. The OS does not come back from the black screen requiring a hard reboot.
i am sure future updates will improve the situation.

This should give a good overview on how my system is setup currently:

via:
inxi -Fxxrzc0

System:
Kernel: 6.8.0-47-generic arch: x86_64 bits: 64 compiler: gcc v: 13.2.0
Desktop: Cinnamon v: 6.2.9 tk: GTK v: 3.24.41 wm: Muffin dm: LightDM
Distro: Linux Mint 22 Wilma base: Ubuntu 24.04 noble
Machine:
Type: Mini-pc System: AZW product: SER9 v: N/A serial: <superuser required>
Chassis: type: 35 serial: <superuser required>
Mobo: AZW model: SER9 v: V10 serial: <superuser required> part-nu: 75
UEFI: American Megatrends LLC. v: STX.3xx.SER9.V103.P8C0M0C15.54.Link.GID
date: 09/10/2024
Battery:
Device-1: hidpp_battery_1 model: Logitech MX Master 3S serial: <filter>
charge: 90% status: discharging
CPU:
Info: 12-core model: AMD Ryzen AI 9 HX 370 w/ Radeon 890M bits: 64
type: MT MCP arch: N/A rev: 0 cache: L1: 960 KiB L2: 12 MiB L3: 24 MiB
Speed (MHz): avg: 769 high: 2459 min/max: 599/5156:5314:5472:3289 cores:
1: 599 2: 599 3: 2008 4: 2459 5: 599 6: 599 7: 1419 8: 599 9: 599 10: 599
11: 599 12: 599 13: 599 14: 599 15: 599 16: 599 17: 599 18: 599 19: 599
20: 599 21: 599 22: 599 23: 599 24: 599 bogomips: 95815
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD driver: amdgpu v: kernel pcie: speed: 16 GT/s lanes: 16 ports:
active: DP-1 empty: DP-2, DP-3, DP-4, DP-5, DP-6, HDMI-A-1, Writeback-1
bus-ID: 64:00.0 chip-ID: 1002:150e temp: 32.0 C
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu
display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560×1440 s-dpi: 96
Monitor-1: DP-1 mapped: DisplayPort-0 model: LG (GoldStar) ULTRAGEAR
res: 2560×1440 dpi: 93 diag: 690mm (27.2″)
API: EGL v: 1.5 platforms: device: 0 drv: radeonsi device: 1 drv: swrast
surfaceless: drv: radeonsi x11: drv: radeonsi inactive: gbm,wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.9-0ubuntu0.2
glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi
gfx1150 LLVM 17.0.6 DRM 3.57 6.8.0-47-generic) device-ID: 1002:150e
Audio:
Device-1: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel
v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 64:00.1 chip-ID: 1002:1640
Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: snd_acp_pci
v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 64:00.5 chip-ID: 1022:15e2
Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel v: kernel
pcie: speed: 16 GT/s lanes: 16 bus-ID: 64:00.6 chip-ID: 1022:15e3
Device-4: Linux Foundation POROSVOC
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 bus-ID: 1-1:2 chip-ID: 1d6b:a4a7
Device-5: Lautsprecher Teufel GmbH CINEBAR ONE
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 bus-ID: 3-4:3 chip-ID: 2cc2:0027
API: ALSA v: k6.8.0-47-generic status: kernel-api
Server-1: PipeWire v: 1.0.5 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: speed: 5 GT/s
lanes: 1 bus-ID: 62:00.0 chip-ID: 8086:2723
IF: wlp98s0 state: down mac: <filter>
Device-2: Realtek RTL8125 2.5GbE driver: r8169 v: kernel pcie:
speed: 5 GT/s lanes: 1 port: f000 bus-ID: 63:00.0 chip-ID: 10ec:8125
IF: eno1 state: up speed: 2500 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 bus-ID: 3-5:4 chip-ID: 8087:0029
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
lmp-v: 11 sub-v: 2184
Drives:
Local Storage: total: 931.51 GiB used: 95.59 GiB (10.3%)
ID-1: /dev/nvme0n1 vendor: Crucial model: CT1000P3PSSD8 size: 931.51 GiB
speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 24.9 C
Partition:
ID-1: / size: 915.32 GiB used: 95.59 GiB (10.4%) fs: ext4
dev: /dev/nvme0n1p2
ID-2: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat
dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2
file: /swapfile
Sensors:
System Temperatures: cpu: 37.8 C mobo: N/A gpu: amdgpu temp: 33.0 C
Fan Speeds (rpm): N/A
Repos:
Packages: 2206 pm: dpkg pkgs: 2186 pm: flatpak pkgs: 20
No active apt repos in: /etc/apt/sources.list
No active apt repos in: /etc/apt/sources.list.d/amdgpu-proprietary.list
Active apt repos in: /etc/apt/sources.list.d/amdgpu.list
1: deb https://repo.radeon.com/amdgpu/6.2.3/ubuntu noble main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb https://ftp-stud.hs-esslingen.de/pub/Mirrors/packages.linuxmint.com wilma main upstream import backport
2: deb http://ftp.uni-mainz.de/ubuntu noble main restricted universe multiverse
3: deb http://ftp.uni-mainz.de/ubuntu noble-updates main restricted universe multiverse
4: deb http://ftp.uni-mainz.de/ubuntu noble-backports main restricted universe multiverse
5: deb http://security.ubuntu.com/ubuntu/ noble-security main restricted universe multiverse
Active apt repos in: /etc/apt/sources.list.d/rocm.list
1: deb [arch=amd64] https://repo.radeon.com/rocm/apt/6.2.3 noble main
Info:
Memory: total: 28 GiB note: est. available: 27.01 GiB used: 3.87 GiB (14.3%)
Processes: 488 Power: uptime: 52m wakeups: 0 Init: systemd v: 255
target: graphical (5) default: graphical
Compilers: gcc: 13.2.0 Shell: Bash v: 5.2.21 running-in: gnome-terminal
inxi: 3.3.34

gukin

I’ve tracked this problem down to a single file: /usr/lib/firmware/amdgpu/dcn_3_5_dmcub.bin.

If it’s 479008 bytes it’s good, if it’s 479648 it’s bad. The 479008 is in the 20240811 firmware. This is the only file that changed after 20240811. A system with modern firmware will boot and work correctly with this file replaced.

support6

thank you for your sharing

gukin

Successful install of Manjaro 24.1.1:
Here’s how you do it:
After booting from the USB but before getting into the installer, press “e” and add “nomodeset” to the line with “linux” to prevent the installer from doing a “modprobe amdgpu”. You’ll wind up with a very low but usable resolution, complete the install.
On the first boot, once again add “nomodeset” to the command line and boot into Manjaro.
Replace the file /usr/lib/firmware/amdgpu/dcn_3_5_dmcub.bin which is 479648 bytes long with the file from the 20240811 firmware found here: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ The correct file should be 479008 bytes long.

Lastly and very importantly, regenerate initramfs by issuing the command “sudo mkinitcpio -P”
Reboot and your manjaro should come up in full resolution with hardware acceleration working.

gukin

To the gentle support entities, perhaps you could host the dcn_3_5_dmcub.bin from the linux-firmware-20240811 because anything older won’t allow hardware acceleration and anything newer will prevent Linux from booting.

This file is paramount to Linux running on the SER9, please don’t let your customers down.