u/uncanny_instinct

Buy now or wait on a local LLM box during the memory crunch? How I'd read it after running a Strix Halo daily for 6 months

Buy now or wait on a local LLM box during the memory crunch? How I'd read it after running a Strix Halo daily for 6 months

I get asked some version of "should I buy a local AI box now or wait for the next one" a lot, and my answer changed this year, so I wrote up how I currently think about it. The short version here, full writeup linked at the bottom.

As I'm sure you can all relate, the usual instinct is to wait, because hardware normally gets cheaper and better. Right now that's kind of backwards for this class of machine, for two reasons.

One, the memory is soldered (at least for the non-DIY boxes, I am not talking about multi-gpu self-built setups here) and it's getting more expensive, not cheaper. LPDDR5X jumped 89% in a single quarter and the analysts I've read don't expect real relief before late 2027. So for these, the capacity you pick is permanent, and you're picking it in a bad market. Concretely: the same box I paid under $2,200 for is about $2,800 now.

Two, for token generation these boxes are all bandwidth-bound, and the announced successors mostly add memory at the same bandwidth. A 192GB or 768GB successor lets you load a bigger model but runs it at more or less the same speed. So waiting for "the bigger one" only helps if you're actually running out of capacity, not if you want more speed.

One caveat so I'm not oversimplifying: prompt processing (time to first token) is a separate, compute-bound story, and there the picture flips. The Spark is much faster at it, Apple and Strix Halo are weaker. The M5 Mac is interesting because it is reported to target exactly that, and it's the one case where I'd actually think about waiting, with the honest caveat that Apple just raised prices and the release date is still an expectation, not a certainty.

I'm running a Strix Halo box myself, so I'm not neutral, but I tried to be fair to the Spark and the Mac in the full post. So I'm curious what you'd do: if someone came to you today and asked whether to buy now or wait, what would you tell them? Especially keen to hear from people actually running a Spark or a Mac Studio, and how prompt processing feels with daily use.

https://thefrontierlab.ai/buy-or-wait-local-llm-hardware/

u/uncanny_instinct — 4 days ago
▲ 37 r/LocalLLM+1 crossposts

PSA: Bosgame's newest BIOS (1.09) does not fix the Strix Halo ROCm allocation bug — and the cross-flash probably won't either

Quick field note for anyone running a Bosgame M5 / Sixunited AXB35-02 (Ryzen AI MAX+ 395, gfx1151) and hitting the ROCm wall.

#6182 - the HSA "Memory critical error … Reason: Memory in use" crash on model load under ROCm - is board-specific, not chip-specific. Same silicon runs ROCm fine on a Minisforum MS-S1 Max. So I tested whether a firmware update fixes it.

Bosgame shipped BIOS 1.09 (May 2026), newer than the 1.07 the bug was filed against. Flashed it, re-ran the smoke test (Qwen2.5-1.5B, -ngl 99, ROCm 7.2.4 via the kyuz0 toolbox): same fault. The newest BIOS doesn't fix it.

Two things worth knowing if you're tempted to cross-flash GMK's BIOS onto a Bosgame to chase this:

  1. No recovery mechanism. No flashback button, no dual-BIOS. If you brick it, the only way back is reflashing the ROM with an external programmer - and the BIOS ROM (Winbond W25R256JWEQ) runs at 1.8V, not 3.3V. A CH341A ships at 3.3V and can kill the chip without the right adapter. Chip's on the back of the board, so it's a full teardown.
  2. It probably won't help anyway. An EVO-X2 user (same AXB35 board, already on GMK BIOS 1.12) just reported a ROCm failure too - a different symptom (~30GB allocatable ceiling rather than the scratch-setup crash), but still Vulkan-only. The rebadge isn't clean either.

Reported the 1.09 negative upstream on #6182. Still Vulkan-only (RADV) in production here - and honestly it's been fine.

Full writeup: https://thefrontierlab.ai/bios-update-wont-fix-6182

u/uncanny_instinct — 24 days ago