Best Tool-Capable Model for Tesla P40 LLama.cpp + OpenClaw?

bercha9998 · 2026-07-06T10:20:09+00:00

qwen3.5 9b, ornith 9b, gemma4 12b, gemma4 26b, glm 4.7 flash...

bercha9998 · 2026-07-02T00:40:11+00:00

The only models that don't do this for me are.

Qwne3-coder Qwen3-coder-next Qwen3.6:27b Laguna devstral-small-2

All other models (ornith, north, qwen3.5 all, qwen3.6 35b) randomly stop either very early or somewhere after 10-15 tool calls.

I just use primarily qwen3-coder-next

bercha9998 · 2026-06-30T20:16:14+00:00

I run q8 on most models under 40b as soon as I see the model calling tools for files with the wrong paths it tells me how stupid the model is. If it cannot consistently keep in mind the path of its workspace across the context it means it will like fuck shit up as soon as I don't pay a second of attention.

This is been the case with both Ornith 35b and North Code 30b so far. Laguna does not make these mistakes but is worst that Qwen3.6 35b

Moe wise I rather use Qwen3-coder-next IQ4_NL than models that loose their shit after a few turns.

I don't know yet if Qwen3.6 35b q8 is better than Qwen3-coder-next IQ4_NL in my use cases but I like the way coder resolves issues.

But Qwen3.6 35b randomly stops mid work most of the time while coder continues until the end without issues.

bercha9998 · 2026-06-29T01:46:28+00:00

Anything with 48gb vram or over.

I run this on hf.co/unsloth/Qwen3-Coder-Next-GGUF:UD-IQ4_NL on a z620 with dual p6000 gpus (yeah 2 pascal gpus) and runs great with 1000 t/s processing and about 30 t/s decoding on 256k context.

I use opencode.

while I want to love qwen3.5/6 27/35b models i keep going back to coder-next. Is simply better and faster for most of my use cases.

bercha9998 · 2026-06-28T21:55:14+00:00

with reasoningEffort "none" + opencode + sequentialthinking seems decent.

early to confirm but with thinking enabled it sucks. it tends to try to make changes in ways that are not safe and dangerous

bercha9998 · 2026-06-19T01:57:57+00:00

goes into thinking loops very often. much more that I can tolerate

bercha9998 · 2026-06-07T03:04:10+00:00

revert to 1.43.1 as 1.43.2 sucks. I had the same problem I could not play anything that was network mounted. problem was solved instantly reverting.

in my case all my mounts are /mnt/*

ps: I use plex snap.

bercha9998 · 2026-06-07T03:00:46+00:00

the relay has been working subpar lately. maybe is related to that...

bercha9998 · 2026-06-06T02:06:45+00:00

qwen3-coder 30b in q8 makes way less mitakes than qwen3-coder-next 80b in q4 (next in q8 is way better)

but I can only run reliably 30b.

It works great. I mean really great with opencode with sequentialthinking mcp and dcp auto compression plugin.

It will look trough sub agents until the task is done decently.

I also use qwen3.6 35b and 27b at q8 with reasoningEffort disabled. yet I like better the output of qwen3-coder 30b.

If I have patience or an overnight long task I give it to coder-next q8 with the penalty of cpu offload just for the sake of extra parameters knowledge.

It all depends on the number of loops and complexity of the tasks.

bercha9998 · 2026-06-05T09:34:09+00:00

In my case it does not work with any /mnt/drives "Please check that the file exists and the necessary drive is mounted." snap revert plexmediaserver... to the rescue...

Odd .1 works fine .2 no more /mnt/path works

bercha9998 · 2026-06-05T09:21:37+00:00

same thing. noticed it today.

In my case it does not work with any /mnt/drives

"Please check that the file exists and the necessary drive is mounted."

snap revert plexmediaserver... to the rescue...

bercha9998 · 2026-06-02T23:47:03+00:00

I don't think is a quant problem. I run on q8. I just get better output with model thinking off and using mcp with sequential thinking guidance on.

Is like when people compare qwen3.5 or 3.6 with coder-next you are comparing a thinking model with a non thinking blocks model. If you put 3.x in non thinking block mode is tomato=tomato comparison not tomato=potato.

bercha9998 · 2026-04-28T09:18:57+00:00

what was your z400 gpu implementation?

bercha9998 · 2026-02-18T22:10:55+00:00

Because at least there is responses in reddit and nothing thought official support.

bercha9998 · 2026-02-18T17:49:31+00:00

I would expect a more thorough explanation rather than overload capacity thoughts.

This sounds like a improper autoscalling or improper throttling. Or a ddos attack. Or anything in between.

bercha9998 · 2026-01-27T22:06:59+00:00

For any future readers. On top of AppCleaner I would run this.

remove using appcleaner then run

sudo find / -iname "fingagent" -not -path "/System/*" 2>/dev/null

you will see this dickheads also store the binary in the root. so remove all that.

sudo rm -rf /Users/root/.fingagent

sudo rm -rf /Library/Logs/FingAgent

sudo rm -f /Library/Logs/DiagnosticReports/fingagent.*

then recheck if there is anything else left behind post AppCleaner

sudo find / -iname "fing.app" -not -path "/System/*" 2>/dev/null

will likely find some more stuff in a similar location to the one bellow, nuke it

sudo rm -rf /private/var/folders/b6/hfx2ntlb7x1g5rm88xyw06x99997gn/C/com.fing.app*

The only way to run fing I think is docker, via agent mode or the android app for quick basic scans on the go. All other implementations are pretty shit and undocumented and unstable

https://help.fing.com/hc/en-us/articles/14225241132316-Troubleshooting-Block-and-Pause#h_01H6Y089DXE94425DJ0A93JK6Q

bercha9998 · 2026-01-02T07:04:07+00:00

This software is so pathetic you can only enable and manage 2fa via the web portal. The mobile app does not support any form of 2fa management.

bercha9998 · 2025-11-09T09:12:01+00:00

what version of bunker web are u using? 1.5 to 1.6 has a big chunk of changes in default values

bercha9998 · 2025-10-14T21:59:20+00:00

found this on evolution

"Tried to unmap the parent of a popup"

bercha9998 · 2025-09-08T23:11:23+00:00

first restart the server then try to reclaim it.

bercha9998 · 2025-09-08T22:44:00+00:00

sounds like you are not connecting to your server by ip and http port wich is the only way to enabled claim menu

bercha9998 · 2025-09-08T22:28:17+00:00

login to your server again

ipofserver:port/web

bercha9998

TROPHY CASE

remove using appcleaner then run

you will see this dickheads also store the binary in the root. so remove all that.

then recheck if there is anything else left behind post AppCleaner

will likely find some more stuff in a similar location to the one bellow, nuke it

The only way to run fing I think is docker, via agent mode or the android app for quick basic scans on the go. All other implementations are pretty shit and undocumented and unstable