<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Sm120 on Bits-Entangled</title><link>https://stondo.github.io/tags/sm120/</link><description>Recent content in Sm120 on Bits-Entangled</description><generator>Hugo -- 0.162.1</generator><language>en-us</language><lastBuildDate>Sat, 12 Sep 2026 10:30:00 +0000</lastBuildDate><atom:link href="https://stondo.github.io/tags/sm120/index.xml" rel="self" type="application/rss+xml"/><item><title>552B Parameters and the 203 GB You Keep on Disk: DeepSeek-V4.1-Flash on Two RTX PRO 6000</title><link>https://stondo.github.io/posts/deepseek-v41-flash-552b-exl3-two-rtx-pro-6000/</link><pubDate>Sat, 12 Sep 2026 10:30:00 +0000</pubDate><guid>https://stondo.github.io/posts/deepseek-v41-flash-552b-exl3-two-rtx-pro-6000/</guid><description>DeepSeek dropped V4.1-Flash on a Thursday: 552B backbone parameters plus a 196B Engram memory, activating 8-16B per token. Two days later it runs on my two RTX PRO 6000s at EXL3 2bpw — because a quant existed for exactly this hardware. This is the fit analysis, the deployment, and the honest gap between my 123 GB of host RAM and the 113 tok/s headline.</description></item><item><title>An Uncensored 305B With Eyes: DeepSeek-V4-Flash-Vision on 2× RTX PRO 6000, and the Two-Engine Week That Tamed It</title><link>https://stondo.github.io/posts/deepseek-v4-flash-vision-uncensored-two-rtx-pro-6000/</link><pubDate>Fri, 04 Sep 2026 16:45:00 +0000</pubDate><guid>https://stondo.github.io/posts/deepseek-v4-flash-vision-uncensored-two-rtx-pro-6000/</guid><description>Replacing DeepSeek-V4-Flash-0731 with the abliterated Vision-Exp build on two RTX PRO 6000s: the SM120 kernel that rejected vision prefill, the DSML tool-call bugs that only fired in real sessions, and why I swapped sglang for a community-qualified vLLM image mid-flight — plus a router fix this adventure forced into existence.</description></item></channel></rss>