Instructions to use FastFlowLM/Deepseek-R1-Distill-Llama-8B-NPU2 with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Transformers
How to use FastFlowLM/Deepseek-R1-Distill-Llama-8B-NPU2 with Transformers:
# Use a pipeline as a high-level helper from transformers import pipeline pipe = pipeline("text-generation", model="FastFlowLM/Deepseek-R1-Distill-Llama-8B-NPU2") messages = [ {"role": "user", "content": "Who are you?"}, ] pipe(messages)# pip install -U transformers accelerate # Load model directly from transformers import AutoTokenizer, AutoModelForCausalLM tokenizer = AutoTokenizer.from_pretrained("FastFlowLM/Deepseek-R1-Distill-Llama-8B-NPU2") model = AutoModelForCausalLM.from_pretrained("FastFlowLM/Deepseek-R1-Distill-Llama-8B-NPU2", device_map="auto") messages = [ {"role": "user", "content": "Who are you?"}, ] inputs = tokenizer.apply_chat_template( messages, add_generation_prompt=True, tokenize=True, return_dict=True, return_tensors="pt", ).to(model.device) outputs = model.generate(**inputs, max_new_tokens=256) print(tokenizer.decode(outputs[0][inputs["input_ids"].shape[-1]:])) - Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- vLLM
How to use FastFlowLM/Deepseek-R1-Distill-Llama-8B-NPU2 with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "FastFlowLM/Deepseek-R1-Distill-Llama-8B-NPU2" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "FastFlowLM/Deepseek-R1-Distill-Llama-8B-NPU2", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/FastFlowLM/Deepseek-R1-Distill-Llama-8B-NPU2
- SGLang
How to use FastFlowLM/Deepseek-R1-Distill-Llama-8B-NPU2 with SGLang:
Install from pip and serve model
# Install SGLang from pip: pip install sglang # Start the SGLang server: python3 -m sglang.launch_server \ --model-path "FastFlowLM/Deepseek-R1-Distill-Llama-8B-NPU2" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "FastFlowLM/Deepseek-R1-Distill-Llama-8B-NPU2", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker images
docker run --gpus all \ --shm-size 32g \ -p 30000:30000 \ -v ~/.cache/huggingface:/root/.cache/huggingface \ --env "HF_TOKEN=<secret>" \ --ipc=host \ lmsysorg/sglang:latest \ python3 -m sglang.launch_server \ --model-path "FastFlowLM/Deepseek-R1-Distill-Llama-8B-NPU2" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "FastFlowLM/Deepseek-R1-Distill-Llama-8B-NPU2", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }' - Docker Model Runner
How to use FastFlowLM/Deepseek-R1-Distill-Llama-8B-NPU2 with Docker Model Runner:
docker model run hf.co/FastFlowLM/Deepseek-R1-Distill-Llama-8B-NPU2
Commit History
-
Fix chat_template crash when assistant message omits the `content` key
Verified signature## Fix `chat_template` to handle assistant messages without a `content` key **⚠️ This template will start crashing for every tool-calling user as soon as the next `transformers` release ships.** The upstream PR https://github.com/huggingface/transformers/pull/45422 normalizes message inputs by stripping `content=None` before rendering (`None` and absent are semantically identical, and `content=None` is exactly what the OpenAI API returns for tool-call-only messages). That normalization is correct, but it exposes a latent bug in this template: the `tool_calls` branch reads `message['content']` directly, which raises when the key is absent. Concretely, this code path is hit by **any tool-calling pipeline** (OpenAI-compatible servers, agent frameworks, function-calling demos) that produces assistant messages with `tool_calls` and no textual content. Today most of them happen to pass `content=None` explicitly and get away with it. After the transformers release, all of them break. ### …b808369
-
Update README.md
Verified signaturedeca786 -
Update README.md
Verified signature91dc357
-
Create README.md
Verified signature8deccd0
-
Update config.json
Verified signature1902964
-
update_mm
ngdxzy59fffc3
-
update_glu
ngdxzyd77ceb2
-
Upload tokenizer_config.json
Verified signature16ac420
-
updateMM
ngdxzyfb69208 -
support_prefill
ngdxzy94e495f
-
add_bin
ngdxzycea47d5
-
addatt
ngdxzy5770a06 -
init
ngdxzy4ff9fbd