Skip to content

armgit / PS5LM

Public Imported from GitHub
0

llama.cpp on a jailbroken PS5: run any GGUF model natively on the console, starting with Qwen 3.8

2.6 KB
Raw Blame

Models

Models worth running on a PS5, from what is popular on Ollama in October 2026, with the GGUF sizes on Hugging Face. Every architecture below loads in the pinned llama.cpp (b11827).

The console has 16 GB shared by everything. How much one PS5LM process can hold is what probes/memprobe measures. Until then: ProsperoAI already keeps a 6.37 GiB model resident on this console, so up to about 6 GiB is safe, and anything above 8 GiB waits for the probe.

Fits for sure (up to 6 GiB)

Model Ollama name Quant Size Architecture Notes
Granite 4.2 3B granite4.2:3b Q4_K_M 2.09 GiB granite the smoke test model: small and fast
Nemotron 3 Nano 4B Q4_K_M 2.64 GiB nemotron_h hybrid Mamba, 1M context
Gemma 4 E4B Q4_0 4.28 GiB gemma4
Granite 4.2 8B granite4.2:8b Q4_K_M 4.98 GiB granite
Qwen3.5 9B Q4_K_M 5.29 GiB qwen35 the model ProsperoAI runs: a direct comparison
Ornith 1.5 9B ornith-1.5:9b Q4_K_M 5.38 GiB qwen35 among Ollama's most pulled
Gemma 4 12B Q3_K_M / IQ4_XS 5.30 / 5.94 GiB gemma4

Fits if the probe allows (6 to 11 GiB)

Model Ollama name Quant Size Architecture Notes
Qwen 3.8 27B qwen3.8 UD-IQ2_XXS / UD-Q2_K_XL 6.77 / 9.15 GiB qwen35 the headline target
Muse Glimmer 30B muse-glimmer IQ2_XXS 8.31 GiB muse-glimmer
Qwen 3.6 27B qwen3.6:27b UD-IQ2_XXS 8.74 GiB qwen35 Ollama's most pulled model
Bonsai 2 27B Q2_0 7.10 GiB qwen35 Qwen 3.8 27B in ternary weights (PrismML); 64k with a q8_0 cache in 10.3 GiB. PrismML's PQ2_0 converts losslessly with scripts/bonsai-pq2-to-q2.py; PTQ1_0 does not load
Qwen 3.6 35B-A3B qwen3.6:35b UD-IQ2_XXS 10.02 GiB qwen35moe MoE, 3B active
gpt-oss 20B gpt-oss:20b MXFP4 10.7 GiB gpt-oss MoE, 3.6B active; every quant is about this size

Does not fit

  • Nemotron 3.5 Lightning 30B-A3B: the smallest GGUF is 18 GiB.
  • Ornith 1.5 35B-A3B: only a 20 GiB Q4_K_M is published.
  • Qwen 3.8 Flash-Next (180B), and the cloud-only models (MiniMax M3, GLM 5.x, DeepSeek V4).

Speed

Decoding reads the active weights once per token, so tokens per second ≈ memory bandwidth / active bytes per token. A dense 27B at 2 to 3 bits reads 7 to 9 GiB per token; a MoE with 3B active reads around 1 GiB. On the CPU the MoE models (Qwen 3.6 35B-A3B, gpt-oss 20B) should be several times faster than the dense 27Bs, at a similar quality. Real numbers come with llama-bench on the console.