Ryzen AI 300 Batch 1

Mine was scheduled to deliver on Monday but now says out for delivery today.

Got mine today (AI 9 HX 370, northern NJ), expected to be in Mon/Tue, but came earlier. Installation was smooth, but first disappointment is that Intel BE200 WiFi doesn’t work - black screen and no boot till I removed the module. I know that BE200 compatibility with non-Intel boards is unpredictable, but looks like HX370 is out of luck. Will looks for some WiFi 7 compatible card now - I assume choice is Mediatek vs. Qualcomm.
Need to re-setup the keys for Secure Boot now, fix my rEFInd boot-loader and update the firmware/drivers for both Win11 and Arch, but this are all known territory :slight_smile:

P.S. WiFi 6E working just fine with AX210 - no need to rush with WiFi 7 card. Secure boot and Arch are back in place - EFI interface on new MB is way too fancy to my liking :slight_smile:

2 Likes

I’m in the Netherlands. Mine (DIY Ryzen 5 340) was scheduled to be delivered on Monday but also arrived earlier, this Friday. A very pleasant surprise that was :grin:
As I mentioned in my introduction post, I installed windows on it for now, but am aiming to move to Linux Mint eventually. As for setting it up and the experience using it, so far so good! It’s been a smooth experience and I haven’t had any issues. Hope that holds for the rest of you too!

1 Like

My HX370 mainboard arrived yesterday, beating the delivery prediction by two days. (One day, kind of, because FedEx doesn’t deliver on Sunday; the question was whether they would get it on a local truck on Saturday or not.)

It went into a system that started out as an 1135G7, was upgraded for a while to a 7840U, and then reverted to the Intel processor when I spilled liquid on the system :frowning: I sent it off to Louis Rossman, who has repaired some Framework motherboards; it was sent back as unrepairable because they couldn’t get the parts to fix it. Rather than buy a replacement 7840U mainboard, I chose to wait for the AI 300 series.

Installing it went uneventfully. But I had already been through the same process with the 7840U install, including the thing about installing the driver pack twice (the first install actually turned out to be unnecessary as it only installs the wireless network driver, and I have an AX210 in my system; I bought the RZ616 with the 7840U mainboard and found it didn’t work as well for me as the AX210 so I put the Intel card back in), and then it came right up. (I chose to stay with my existing Windows installation rather than start anew.) This system had already been upgraded with the CNC top cover, the 2.8K display, the second generation webcam, the new hinges, and a large Gen 4 SSD, so it was already reasonably up to date. My 32 GB of Framework RAM from the 7840U board went onto the new one.

I had a brief scare when I first tried it out; it was going in and out of sleep. The problem turned out to be that my Framework screwdriver was too close to the system and was triggering the ā€œcase closedā€ sensor! With that out of the way, everything worked.

An unexpected glitch; using the Framework power supply and maximum performance mode, the system goes right up to 60W pulled from the power supply, runs very hot, and drains the battery even while plugged in. (That presumably means that the system is drawing MORE than 60W.) After a while it throttles down to 30W for thermal reasons and STILL drains the battery; the charge current is limited because of the temperature of the system. (Numbers from an in-line USB-PD monitor.)

Balanced mode works better for gaming sessions; after a very brief spike the power consumption levels out at 45W and stays there, with the system being noticeably cooler than in the maximum performance setting. GPU temperatures are in the 70s as reported by AMD’s Adrenalin software, which is a bit on the warm side but within specs. GPU performance doesn’t hit 100%, but it’s probably held back by the power limit. (The AI 300 series doesn’t have separate U and H processors, just a choice of different power limits; if we eventually see an FW16 with this CPU it will get more performance out of it.) Gaming performance remains very good. It’s faster than the 7840U, though not as dramatically as I had hoped.

The HX370 is the beast that it promised to be, offering both outstanding CPU performance and good graphics for an iGPU. The value proposition is iffy (many buyers will be better off buying a 7840U system while they last, or an AI 350 once those are gone), but if you want the best currently available performance available for the Framework 13 this is what you want.

Bonus: between all the parts that had been replaced over the years and some components from a mystery box, I had enough parts to put together a second laptop. That one’s got the 1135G7 and its RAM, an SSD salvaged from a non-Framework system, the original display, another AX210, the old top cover, and an input cover and base from the box. That will go to a more basic use case that needs a laptop new enough to run Windows 11 (for support reasons) but is not particularly demanding.

3 Likes

I’m also using an AX210. The RZ616 from the earlier Ryzen FW13 will also work, and the AI 300 driver pack installs the driver for it as well as for the RZ717. AX201 and AX211 from other FW13 systems will not work, nor will the BE200.

1 Like

I ordered QCNCM865. RZ717 will be second choice if Qualcomm’s will not be doing the job. I didn’t do deep into WiFi7 research yet since intel was doing its job on the old board, but I didn’t hear much positive things about Mediatek so far (i.e. New Ryzen AI Framework 13 RZ717 wifi doesn't work great with 6ghz). AX210 is very decent fallback option if other won’t work and there is a hope for another WiFi7 card from Intel without vendor lock.

Keep in mind my post that you referenced was specifically for Linux (fedora to be exact). I had no problems with the RZ717 under windows 11.

Fedora has since released a fix for the issue i noted and it did indeed work fine.

I ended up getting a QCNCM865 because I was wanted 320mhz support and MLO support which the RZ717 don’t have.

Under Linux things just worked with the qualcomm, but under Windows, finding an appropriate driver was a little more work (not too hard. Went directly to the Windows update catalog Microsoft Update Catalog to fetch the cab files and extracted).

320Mhz would be great to have for sure - I invested into the good WiFi 7 AP and would be a shame not to use it to full capabilities.
Regarding drivers, I am not worried - for Windows all the approaches are pretty same since Windows 2000 (which was the first version I dig quite deeply) and for Linux, as long as it works in any distribution, I can make it work in Arch for sure :slight_smile: Thanks for the info thought - good to know what to expect!

I’ve gotten my 370 set up with arch. But I’m having 2 issues. The AX210 is having crazy dropouts. That seems to be reported elsewhere in other threads. But I’m also having intermittent black screens for just a few seconds but then the screen freezes. Sometimes it recovers, sometimes not. Are you not having these issues? Journalctl is showing amdgpu problems with microcode. I’m using 6.15rc4 kernel and the latest microcode dated 4/10 even though it’s being early loaded from the bios.

May be because you are on too new kernel :slight_smile:

Mine is mostly stable, but I did see some black screens past few days and dmesg is full of exceptions of many kinds - looks like the hardware is still half-backed in the kernel and we will need to wait a bit to get it stabilized.

I am using ucode and kernel from testing:

Ī» paru -Qi linux amd-ucode | grep -e Name -e Version
Name            : linux
Version         : 6.14.4.arch1-1
Name            : amd-ucode
Version         : 20250408.c1a774f3-1

P.S. Regarding Wi-Fi, my AX210 is rock solid so far. However I am getting Qualcomm WiFi 7 card very soon and plan to do a swap:

Ī» lspci | grep Wi-Fi
c0:00.0 Network controller: Intel Corporation Wi-Fi 6E(802.11ax) AX210/AX1675* 2x2 [Typhoon Peak] (rev 1a)
1 Like

Same ucode, same wifi card but still keep getting drops.

Using an AX210 on arch, not having any dropout issues. Thought I noticed the screen flash/flicker really briefly yesterday but it was quick and I haven’t seen it do that again. I’m figuring it’s probably just the display cable in my case, if anything.

I am currently using the NCM865 in my FW13 7840U. Wi-Fi 7 works well in Windows 11, but the Wi-Fi is slower than the RZ616 in Ubuntu 24.10, and doesn’t work in earlier Ubuntu versions.

My Bluetooth earbuds haven’t worked with the NCM865 in Windows, where they do with the RZ616. But I just installed the latest Bluetooth drivers from last month and after removing and re-adding my earbuds, audio now works!

I was anxiously waiting for the RZ717 to become available. It’s a shame I couldn’t get it before my HX 370 board arrived today. But if performance for the RZ717 isn’t any better than the NCM865 in Linux and is limited to 160 MHz, where the NCM865 supports 320 MHz, maybe I’ll stick with the NCM865, now that Bluetooth audio is working with the latest drivers.

I was anxiously waiting for the RZ717

Any reason why RZ717 is more preferable?

I got my NCM865 today and it is pretty good so far. Not the rock solid yet, but pretty good.

Looks like the problem that was there for the AMD 7040 series still reproducible on new AI300 series when connecting the PD charger…

[  182.552674] ucsi_acpi USBC000:00: con4: failed to register partner alt modes (-5)
[  182.770530] ucsi_acpi USBC000:00: unknown error 0
[  182.770543] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5)
[  182.852731] ucsi_acpi USBC000:00: unknown error 0
[  182.852746] ucsi_acpi USBC000:00: con4: failed to register partner alt modes (-5)
[  183.108806] ucsi_acpi USBC000:00: unknown error 0
[  183.108821] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5)
[  183.201065] ucsi_acpi USBC000:00: unknown error 0
[  183.201080] ucsi_acpi USBC000:00: con4: failed to register partner alt modes (-5)

It was solved by firmware update for FW16, but stock firmware for 300 series doesn’t have the fix :frowning:

1 Like

it’s probably just the display cable in my case, if anything

I am pretty sure this is the GPU reset issue caused by immature support of new GPU in kernel…

[ 1327.503485] amdgpu 0000:c1:00.0: amdgpu: Dumping IP State
[ 1327.505951] amdgpu 0000:c1:00.0: amdgpu: Dumping IP State Completed
[ 1327.506010] amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 timeout, signaled seq=308802, emitted seq=308804
[ 1327.506012] amdgpu 0000:c1:00.0: amdgpu: Process information: process RDD Process pid 23549 thread firefox:cs0 pid 28723
[ 1327.506015] amdgpu 0000:c1:00.0: amdgpu: GPU reset begin!
[ 1327.568685] amdgpu 0000:c1:00.0: amdgpu: MODE2 reset
[ 1327.590193] amdgpu 0000:c1:00.0: amdgpu: GPU reset succeeded, trying to resume

Mostly just that it’s the stock Wi-Fi 7 card recommended by Framework and AMD, and that I’ve been having issues with Bluetooth audio with the NCM865. But now that that’s working with the latest drivers, there’s less of a reason.

I expected the RZ717 would have better Linux support too, but apparently that’s not necessarily the case. I haven’t tested the NCM865 with the 6.14 kernel with Ubuntu 25.04 yet. I was waiting for official upgrade support. Hopefully performance is improved from 6.11. I’ll need to upgrade before installing my HX 370 mainboard.

I ordered a NCM865 card and it’s marginally faster than the RZ717 on linux (i assume this is due to the 320mhz channel as much as anything else). However with Fedora 42 and kernel 6.14.4 the ath12k driver hangs the wifi stack if i try to swap APs. There was a problem with 6ghz initiall with the Rz717 but a wireless-regdb package update fixed it and now the RZ717 is more stable overall than the qualcomm and slightly slower, but stability matters more. I may try the qualcomm again if i see more firmware/kernel driver updates but right now it’s sitting in a desk drawer :slight_smile:

So I just thought I’d note something funny about my Batch 1 order. Here’s the fedex tracking:

Here’s the arrival time of the ā€œYour order has shipped emailā€:

1 Like

resolved by : Making sure you're not a bot!