Short answer
No official Qwen source ties a Qwen 3.6 release to 9B, 122B, or 397B parameter tiers, and none of the Qwen team's channels — the Qwen blog, the QwenLM GitHub organization, or the Qwen Hugging Face org — reference AMD Instinct MI300X or MI355X accelerators as a training or deployment target for Qwen 3.6. A version of this claim that's been circulating also attributes the work to Tencent, which is a separate error: Qwen is Alibaba's model family. Tencent's competing line is Hunyuan, not Qwen.
What SpecPicks has actually verified about Qwen 3.6 — through prior coverage of specific inference runs — centers on consumer NVIDIA hardware, not an AMD datacenter roadmap. That mismatch, plus a couple of hardware-spec errors baked into the AMD version of the story, is enough to treat the 9B/122B/397B AMD framing as unconfirmed at best.
What's actually been verified about Qwen 3.6
SpecPicks has covered several real-world Qwen 3.6 inference reports, all on NVIDIA silicon:
| Coverage | Hardware | What was checked |
|---|---|---|
| Qwen3.6-27B at 80 TPS on RTX 5090 | RTX 5090, vLLM 0.19 | Throughput claim against public vLLM benchmarking practice |
| Qwen3.6-27B at 72 tok/s on RTX 3090 | RTX 3090, native Windows | Native-Windows vLLM inference numbers |
| $400 Qwen 3.6-27B setup | Dual RTX 3060 | Budget dual-GPU build cost claim |
| Qwen 3.6 35B GGUF: NTP vs MTP | Consumer GPUs, llama.cpp | Quantization-format tradeoffs |
| Qwen3.6-35B-A3B VRAM optimization | Consumer GPUs | VRAM footprint of larger quants |
| Multi-token prediction on llama.cpp + TurboQuant | Consumer GPUs | MTP support status in llama.cpp |
Every one of those pieces traces back to community inference runs — GitHub issues, forum threads, vLLM and llama.cpp release notes — not to an official Qwen roadmap announcement. That's an important distinction: Qwen 3.6 exists and people are running it (true, and well documented in the 27B and 35B-A3B range) is a different claim from Qwen has announced a further roadmap spanning 9B, 122B, and 397B tiers on specific AMD hardware (unconfirmed).
It's also worth noting that a large-total-parameter Qwen release isn't inherently implausible on its face — Qwen's confirmed flagship, Qwen3-235B-A22B, is a mixture-of-experts design with 235B total parameters and roughly 22B active per token, so Alibaba has already shipped models in that size class. What's missing isn't plausibility, it's confirmation: nothing on Qwen's own channels currently backs a 397B Qwen 3.6 checkpoint, an AMD-specific hardware tier, or the specific 9B/122B split described in the circulating claim.
Where the AMD/9B-122B-397B story falls apart
Three separate problems undercut the claim as it's circulating:
1. Wrong developer. The claim credits Tencent with training a 122B Qwen 3.6 model on MI300X. Qwen has been developed by Alibaba's Qwen team since its first release; Tencent ships its own separate frontier model line, Hunyuan. A story that gets the parent company wrong is a strong signal it wasn't sourced from anything official.
2. Hardware specs that don't match AMD's own published numbers. The claim states a 9B Qwen 3.6 variant requires at least 24GB VRAM (Radeon RX 6800 XT or better) — but the RX 6800 XT ships with 16GB of GDDR6, not 24GB, so it can't be the reference card for a 24GB requirement. The claim also describes 8x MI300X (512GB total VRAM); AMD's Instinct MI300X carries 192GB of HBM3 per card, so eight of them total roughly 1.5TB, not 512GB. Numbers that don't reconcile with AMD's own spec sheets are a red flag for a fabricated benchmarking claim, not a rounding error.
3. No primary-source corroboration. Official model announcements from the Qwen team — new checkpoints, parameter counts, recommended hardware — show up on the Qwen blog, the QwenLM GitHub org, and the Qwen Hugging Face org first. None of those channels currently list a 397B Qwen 3.6 model, a 122B AMD-specific variant, or a roadmap statement matching the claim's structure.
Hardware reality check
| Claimed tier | Claimed AMD requirement | Actual card spec | Verified community pattern |
|---|---|---|---|
| 9B | RX 6800 XT, 24GB VRAM | RX 6800 XT = 16GB GDDR6 | 27B-class Qwen 3.6 running on NVIDIA RTX 3060/3090/5090 per SpecPicks coverage above |
| 122B | 8x MI300X, 512GB total | MI300X = 192GB HBM3/card (~1.5TB for 8) | No verified consumer or prosumer 122B Qwen 3.6 run found |
| 397B | MI355X, 256GB per card | Not corroborated by any Qwen source | No verified run at this scale for Qwen 3.6 |
The pattern across every verified Qwen 3.6 report SpecPicks has checked is the same: NVIDIA cards, CUDA-based stacks (vLLM, llama.cpp with CUDA builds), and parameter counts in the 27B–35B range where consumer hardware is actually viable. An AMD Instinct-first roadmap for 9B/122B/397B tiers doesn't fit that pattern, and nothing on Qwen's official channels currently supports it independently.
Why this kind of claim spreads anyway
Threads on forums like r/LocalLLaMA move fast, and specific-sounding numbers — a VRAM figure, a percentage improvement, a named accelerator — read as more credible than vague claims, even when they don't hold up against the hardware vendor's own spec sheet. The AMD/Tencent version of the Qwen 3.6 story has the shape of a real announcement (parameter tiers, hardware tiers, performance deltas) without the substance of one: no dated announcement, no changelog entry, no primary source. That's the same pattern flagged in prior is the claim real coverage of viral Qwen 3.6 throughput numbers — see the RTX 5090 and RTX 3090 pieces linked above for how those specific claims held up against the public benchmarking record.
How to check for a real Qwen 3.6 update yourself
Because AI model releases move fast, the fastest way to confirm whether Qwen has said anything new is to check primary sources directly rather than relying on secondhand hardware-requirement claims:
- Qwen's official blog — where model releases and roadmap notes are posted first.
- QwenLM on GitHub — release tags and model cards land here alongside code.
- Qwen on Hugging Face — new checkpoints appear here with model cards listing actual parameter counts and recommended hardware.
If a claim about a new Qwen 3.6 tier doesn't show up in at least one of those three places, treat it as unconfirmed — regardless of how specific the VRAM numbers or performance percentages sound.
Related SpecPicks coverage
- Qwen-Image-3.0 on an RTX 3060 12GB — local image generation with a Qwen model on consumer hardware
- Apple Intelligence ships in China on Alibaba's Qwen — how Alibaba's Qwen family is being deployed outside the open-weights community
- Qwen 3.6 35B GGUF: NTP vs MTP quantization explained
- Qwen3.6-35B-A3B VRAM optimization
Frequently asked questions
Is Qwen 3.6 a real model family? Yes — multiple independent Qwen 3.6 inference reports at the 27B and 35B-A3B scale have been verified, all running on consumer NVIDIA GPUs.
Does Qwen 3.6 have official AMD Instinct support? Not according to any current Qwen blog, GitHub, or Hugging Face listing. Every verified Qwen 3.6 run traced so far uses NVIDIA hardware.
Who actually develops Qwen? Alibaba's Qwen team. Tencent has a separate, unrelated frontier model family called Hunyuan.
Has Qwen confirmed a 397B parameter model? No. There's no dated announcement, changelog entry, or model card on Qwen's official channels for a 397B tier as of this writing.
Where can I check for the latest official Qwen updates? The Qwen blog, QwenLM's GitHub org, and Qwen's Hugging Face org are the primary sources — check those before trusting a secondhand hardware-requirement claim.
What hardware actually runs Qwen 3.6 well today? Per verified SpecPicks coverage, consumer NVIDIA GPUs — RTX 3060, RTX 3090, and RTX 5090 — running vLLM or llama.cpp handle the 27B and 35B-A3B Qwen 3.6 tiers.
Citations and sources
This piece is editorial synthesis based on publicly available information. No independent first-party benchmarking is reported.