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

[GH-ISSUE #12689] plamo-2-translate-gguf #54930

New Issue
Open
opened 2026-04-29 08:01:20 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-29 08:01:20 -05:00
Owner
Copy Link

Originally created by @shilik on GitHub (Oct 18, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/12689

Have installed all available plamo-2-translate-gguf on Huggingface, but keep getting error

GGML_ASSERT(inp != nullptr && "missing result_norm/result_embd tensor")

Are there any ways to get this problem solved?

Originally created by @shilik on GitHub (Oct 18, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/12689 Have installed all available plamo-2-translate-gguf on Huggingface, but keep getting error > GGML_ASSERT(inp != nullptr && "missing result_norm/result_embd tensor") Are there any ways to get this problem solved?
GiteaMirror added the model label 2026-04-29 08:01:20 -05:00
GiteaMirror commented 2026-04-29 08:01:22 -05:00
Author
Owner
Copy Link

@mitmul commented on GitHub (Oct 24, 2025):

@shilik I also managed to reproduce the same issue, while the fix seems likely to require only a single line change (luckily). Since I've requested the modifications needed to fix the problem by #12761, it would be greatly appreciated if you could apply the changes and verify whether the issue resolves.

<!-- gh-comment-id:3442561640 --> @mitmul commented on GitHub (Oct 24, 2025): @shilik I also managed to reproduce the same issue, while the fix seems likely to require only a single line change (luckily). Since I've requested the modifications needed to fix the problem by #12761, it would be greatly appreciated if you could apply the changes and verify whether the issue resolves.
GiteaMirror commented 2026-04-29 08:01:23 -05:00
Author
Owner
Copy Link

@shilik commented on GitHub (Oct 24, 2025):

@mitmul, sounds great! I have been waiting and trying so long to make it work for my project.
I will give a try as long as your patch is applied.

<!-- gh-comment-id:3442783357 --> @shilik commented on GitHub (Oct 24, 2025): @mitmul, sounds great! I have been waiting and trying so long to make it work for my project. I will give a try as long as your patch is applied.
GiteaMirror commented 2026-04-29 08:01:24 -05:00
Author
Owner
Copy Link

@shilik commented on GitHub (Oct 24, 2025):

Weill, still got the same error even forked ollama project and made a patch
like yours.

Error: llama runner process has terminated: GGML_ASSERT(inp != nullptr &&
"missing result_norm/result_embd tensor") failed

On Fri, Oct 24, 2025 at 7:10 PM Shunta Saito @.***>
wrote:

mitmul left a comment (ollama/ollama#12689)
https://github.com/ollama/ollama/issues/12689#issuecomment-3442561640

@shilik https://github.com/shilik I also managed to reproduce the same
issue, while the fix seems likely to require only a single line change
(luckily). Since I've requested the modifications needed to fix the problem
by #12761 https://github.com/ollama/ollama/pull/12761, it would be
greatly appreciated if you could apply the changes and verify whether the
issue resolves.

—
Reply to this email directly, view it on GitHub
https://github.com/ollama/ollama/issues/12689#issuecomment-3442561640,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKW7RHFOQI2BGVURSG57VL3ZICKZAVCNFSM6AAAAACJRXHMO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINBSGU3DCNRUGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

<!-- gh-comment-id:3443134149 --> @shilik commented on GitHub (Oct 24, 2025): Weill, still got the same error even forked ollama project and made a patch like yours. Error: llama runner process has terminated: GGML_ASSERT(inp != nullptr && "missing result_norm/result_embd tensor") failed On Fri, Oct 24, 2025 at 7:10 PM Shunta Saito ***@***.***> wrote: > *mitmul* left a comment (ollama/ollama#12689) > <https://github.com/ollama/ollama/issues/12689#issuecomment-3442561640> > > @shilik <https://github.com/shilik> I also managed to reproduce the same > issue, while the fix seems likely to require only a single line change > (luckily). Since I've requested the modifications needed to fix the problem > by #12761 <https://github.com/ollama/ollama/pull/12761>, it would be > greatly appreciated if you could apply the changes and verify whether the > issue resolves. > > — > Reply to this email directly, view it on GitHub > <https://github.com/ollama/ollama/issues/12689#issuecomment-3442561640>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAKW7RHFOQI2BGVURSG57VL3ZICKZAVCNFSM6AAAAACJRXHMO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINBSGU3DCNRUGA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
GiteaMirror commented 2026-04-29 08:01:24 -05:00
Author
Owner
Copy Link

@mitmul commented on GitHub (Oct 24, 2025):

Thank you for trying it out. By the way, when you ran go run . serve at the top directory of the patched Ollama code base, was there any other instance of the old-version Ollama server already running?

<!-- gh-comment-id:3443249209 --> @mitmul commented on GitHub (Oct 24, 2025): Thank you for trying it out. By the way, when you ran `go run . serve` at the top directory of the patched Ollama code base, was there any other instance of the old-version Ollama server already running?
GiteaMirror commented 2026-04-29 08:01:25 -05:00
Author
Owner
Copy Link

@shilik commented on GitHub (Oct 24, 2025):

I didn't try it, just installed the forked and patched project, then run
"ollama run hf.co/mmnga/plamo-2-translate-gguf:Q8_0"
The error is what I got when pulling the gguf file.

On Fri, Oct 24, 2025 at 9:46 PM Shunta Saito @.***>
wrote:

mitmul left a comment (ollama/ollama#12689)
https://github.com/ollama/ollama/issues/12689#issuecomment-3443249209

Thank you for trying it out. By the way, when you ran go run . serve at
the top directory of the patched Ollama code base, was there any other
instance of the old-version Ollama server already running?

—
Reply to this email directly, view it on GitHub
https://github.com/ollama/ollama/issues/12689#issuecomment-3443249209,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKW7RDGUYOZ6CYT577VTDD3ZIUVDAVCNFSM6AAAAACJRXHMO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINBTGI2DSMRQHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

<!-- gh-comment-id:3443449620 --> @shilik commented on GitHub (Oct 24, 2025): I didn't try it, just installed the forked and patched project, then run "ollama run hf.co/mmnga/plamo-2-translate-gguf:Q8_0" The error is what I got when pulling the gguf file. On Fri, Oct 24, 2025 at 9:46 PM Shunta Saito ***@***.***> wrote: > *mitmul* left a comment (ollama/ollama#12689) > <https://github.com/ollama/ollama/issues/12689#issuecomment-3443249209> > > Thank you for trying it out. By the way, when you ran go run . serve at > the top directory of the patched Ollama code base, was there any other > instance of the old-version Ollama server already running? > > — > Reply to this email directly, view it on GitHub > <https://github.com/ollama/ollama/issues/12689#issuecomment-3443249209>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAKW7RDGUYOZ6CYT577VTDD3ZIUVDAVCNFSM6AAAAACJRXHMO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINBTGI2DSMRQHE> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
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 model
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#54930
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?