on

Can the Intel Arc A580 run OpenReasoning Nemotron 14B?

46Fair quality (C) · 46 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 60/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs well (offloads to RAM)

Runs well (offloads to RAM). At Q2_K it needs about 8.5 GB of 8.0 GB usable, with an estimated speed of 37.4 tok/s.

Best quant
Q2_K
Generation speed
37.4 tok/s
Prompt processing
860 tok/s
First token (1K prompt)
1.2 s
Largest safe context
5K

Best app to run it on the Intel Arc A580

On Windows

llama.cpp

Command line + local API · runs on llama.cpp

  • Splits the model between GPU memory and system RAM, which this setup needs.
  • Gives you direct control of how many layers sit on the GPU, the best way to squeeze a model that doesn’t quite fit.
  • Supports Intel Arc through SYCL and Vulkan.
llama-server -hf bartowski/nvidia_OpenReasoning-Nemotron-14B-GGUF:Q2_K
  • LM Studio Splits the model between GPU memory and system RAM, which this setup needs.
  • Jan Splits the model between GPU memory and system RAM, which this setup needs.

On Linux

llama.cpp

Command line + local API · runs on llama.cpp

  • Splits the model between GPU memory and system RAM, which this setup needs.
  • Gives you direct control of how many layers sit on the GPU, the best way to squeeze a model that doesn’t quite fit.
  • Supports Intel Arc through SYCL and Vulkan.
llama-server -hf bartowski/nvidia_OpenReasoning-Nemotron-14B-GGUF:Q2_K
  • LM Studio Splits the model between GPU memory and system RAM, which this setup needs.
  • Jan Splits the model between GPU memory and system RAM, which this setup needs.

Want an agent? OpenReasoning Nemotron 14B supports tool use, so you can pair a llama.cpp or MLX LM server with one of these. Apps that run on this computer come first.

Coding agents

Personal assistants

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download OpenReasoning Nemotron 14B

Recommended for the Intel Arc A580: Q2_K. Every other quantization has its own download link in the table below.

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

Download the Q2_K file (opens in a new tab)

huggingface.co/bartowski/nvidia_OpenReasoning-Nemotron-14B-GGUF (opens in a new tab)

ollama run hf.co/bartowski/nvidia_OpenReasoning-Nemotron-14B-GGUF:Q2_K

Original weights · Hugging Face

Full-precision files from NVIDIA, for fine-tuning, vLLM, Transformers.

huggingface.co/nvidia/OpenReasoning-Nemotron-14B (opens in a new tab)

No sign-in needed.

Links checked 1 day ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 46Fair quality (C) · 46 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 60/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q2_K, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs welloffloads to RAM
How well it runs on the Intel Arc A580: speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.20.8 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.10.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.14.5 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.15.0 / 15
Match score60.3 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the Intel Arc A580

Quant Memory needed Available Speed Runs Quality Download
Q2_K 8.5 GB 8.0 GB 37.4 tok/s Runs welloffloads to RAM 46Fair quality (C) · 46 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 60/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q3_K_M 9.8 GB 8.0 GB 18.7 tok/s Runs welloffloads to RAM 55Good quality (B) · 55 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 60/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q4_K_M 11.6 GB 8.0 GB 11.0 tok/s Slowheavy RAM offload 62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 55/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 13.1 GB 8.0 GB 8.0 tok/s Slowheavy RAM offload 64Good quality (B) · 64 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 54/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q6_K 14.7 GB 8.0 GB 6.1 tok/s Slowheavy RAM offload 65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 54/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 18.3 GB 8.0 GB 3.9 tok/s Slowheavy RAM offload 66Good quality (B) · 66 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 53/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 32.2 GB 8.0 GB — Won't run 66Good quality (B) · 66 of 100: how capable the model is at F16, whatever it runs on. Match score 8/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab) Original weights (opens in a new tab)

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

Other hardware that runs it

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.

Was this page helpful?