github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 16:11:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #10886] Quantization Q6 silently removed? #53667

New Issue
Closed
opened 2026-04-29 04:26:29 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-29 04:26:29 -05:00
Owner
Copy Link

Originally created by @chhu on GitHub (May 28, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/10886

What is the issue?

Hi, I was a big fan of Q6 because of the sweet-spot between poor Q4 performance and required memory. Since the zoo of quants are not available for download anymore (understandable), I loved to see the --quantize option to do it myself. Now I realize that ollama can still run Q6 models but I cannot quant them anymore. Is there a particular reason?

Thanks!

Relevant log output

OS

Linux

GPU

No response

CPU

No response

Ollama version

0.7.1

Originally created by @chhu on GitHub (May 28, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/10886 ### What is the issue? Hi, I was a big fan of Q6 because of the sweet-spot between poor Q4 performance and required memory. Since the zoo of quants are not available for download anymore (understandable), I loved to see the --quantize option to do it myself. Now I realize that ollama can still run Q6 models but I cannot quant them anymore. Is there a particular reason? Thanks! ### Relevant log output ```shell ``` ### OS Linux ### GPU _No response_ ### CPU _No response_ ### Ollama version 0.7.1
GiteaMirror added the bug label 2026-04-29 04:26:29 -05:00
GiteaMirror commented 2026-04-29 04:26:33 -05:00
Author
Owner
Copy Link

@chhu commented on GitHub (May 28, 2025):

PS: Error: unsupported quantization type Q6_K - supported types are F32, F16, Q4_K_S, Q4_K_M, Q8_0

<!-- gh-comment-id:2915735281 --> @chhu commented on GitHub (May 28, 2025): PS: `Error: unsupported quantization type Q6_K - supported types are F32, F16, Q4_K_S, Q4_K_M, Q8_0`
GiteaMirror commented 2026-04-29 04:26:35 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (May 28, 2025):

https://github.com/ollama/ollama/pull/10647#pullrequestreview-2834756193

<!-- gh-comment-id:2915935309 --> @rick-github commented on GitHub (May 28, 2025): https://github.com/ollama/ollama/pull/10647#pullrequestreview-2834756193
GiteaMirror commented 2026-04-29 04:26:36 -05:00
Author
Owner
Copy Link

@chhu commented on GitHub (May 28, 2025):

Very weird. I searched for relevant keywords and that didn't came up. Closing this one in favor of #10647

<!-- gh-comment-id:2916023532 --> @chhu commented on GitHub (May 28, 2025): Very weird. I searched for relevant keywords and that didn't came up. Closing this one in favor of #10647
GiteaMirror commented 2026-04-29 04:26:39 -05:00
Author
Owner
Copy Link

@stutteringp0et commented on GitHub (May 28, 2025):

#10647 was closed a couple of days ago

<!-- gh-comment-id:2916368773 --> @stutteringp0et commented on GitHub (May 28, 2025): #10647 was closed a couple of days ago
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#53667
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?