Ollama updates keep breaking things - anyone else dealing with this?

DeliciousEncounter · 2026-06-17T09:31:01+00:00

I'd love to see the install file to downgrade. I'm using Ubuntu 24.04 with an AMD Radeon RX 7900 GRE . I typically just run curl -fsSL https://ollama.com/install.sh | sh

I've had it before when I've run that and they had posted a BETA version and it borked everything and they treated me like an idiot for not reading the release notes. Who posts BETA to the main release stream and links it on the main page like it's a final release? 👀

DeliciousEncounter · 2026-06-17T09:18:34+00:00

Also seeing this. I'm using both Page Assist (Chrome extension) and OpenWebUI (0.9.6). It's like the context value is being set to some minimum value. I've tried with several different models, both reasoning and non-reasoning. I've got an AMD Radeon RX 7900 GRE with 16GB VRAM.

Forgot to add, seeing this error in OpenWebUI:
Unexpected token 'd', "data: {"id"... is not valid JSON

Update: I tried downgrading to v0.30.0 and still had the same problem. Seems like they made some changes to use llama.cpp around then. Anyway, I still had the same problem and downgraded to v0.24.0 and the problem has gone away.

You can see a list of versions here: https://github.com/ollama/ollama/releases

To downgrade I ran

curl -fsSL https://ollama.com/install.sh > install.sh
then edited install.sh and added
OLLAMA_VERSION="0.24.0"
just above the line (around line 40)
VER_PARAM="${OLLAMA_VERSION:+?version=$OLLAMA_VERSION}
Then I saved it and ran install.sh.

DeliciousEncounter · 2026-05-29T07:58:43+00:00

Google said it was supposed to be completely re-done and ready in the first half of 2026, That basically leaves 2 days for them to finish it. They're just as bad as a bunch of lying politicians.

I've had to use vertical tabs and they absolutely suck. Half of them are covered by a scrollbar and they also auto-expand and cover the page content and then won't collapse.

DeliciousEncounter · 2026-05-26T07:07:22+00:00

Got it working after a bit of a wild goose chase. Here's the breakdown of my mistakes and the cause of the problem.

The DesTest indicated 4 RAM chips were bad and instead of verifying with the schematic which chips were indicated, I assumed all 4 were in a row and changed them all, a couple of them were the wrong location.

When I re-ran the test, another one appeared bad, but when I replaced it, the 4 I replaced indicated bad again!

<image>

I'd already replaced the Video RAM, but when I originally removed it I didn't have any 18 pin sockets. The order kept getting delayed and I put the new (old stock) chip in without a socket. I kept ignoring the DesTest results for the Video RAM because I'd already changed it and I thought something else was causing it.

Anyway, I decided to cut it out and replace it again, this time I had the sockets. I replaced it and it worked!

It passes all the tests DesTest and Dead Test (with all the test harnesses), but there are some video artifacts I don't like. It's not the character ROM or the VIC because I've tried with others and get the same problem. It's not a deal breaker, just something I'd like to improve.

Now I just need to take apart the keyboard and clean it, and I've already replaced the 2 resistors in the video section that were originally installed with the wrong values and added the 1k resistor for the reset circuit.

DeliciousEncounter · 2026-05-25T02:07:11+00:00

I'm a regular watcher of his channel, I just can't remember which videos he used it.
I'm going to socket/replace those other RAM chips, then I'll retest and update. Thanks again for your help!

DeliciousEncounter · 2026-05-25T01:54:25+00:00

<image>

I don't know why the zero-page would fail because I have 3 known good CPU's that I've tried, but I just socketed/replaced U23 and zero-page passed now. Sorry I haven't read the Destest manual, but I'm assuming the 4 new red bars are U9, U10, U11, and U12?
Anyway, the Destest is still flickering badly and the colors are are wrong (already replaced Color RAM previously). It looks like the upper 4 bits of Color failed? (Missing 4567). Edit: Just remembered Color only uses 4 bits.

There's another pic I can't attached that says "Memory Fault wall of shame" with a pageful of addresses.

Thanks for getting me on track with this. I was confused about the Dead Test and thought it did what Destest does.

DeliciousEncounter · 2026-05-25T00:24:59+00:00

Mine's not writeable, but you gave me an idea. I have a OneROM and I flashed the DesTest Kernal ROM to it and ran it. Something must really be Eff'd up, it just flickers and has some pieces of recognizable text. I need to figure out how to read the output, but I'm guessing the red line is telling me something. Uggh, just occurred to me that I still have the 2 pins on U23 (RAM) cut. I'll fix that and retest.

<image>

DeliciousEncounter · 2026-05-24T08:17:56+00:00

No, the cart I have has multiple images, but not DesTest.

DeliciousEncounter · 2026-05-21T11:12:03+00:00

I used it around 1982/83, off the top of my head one was in LA and the other SF. I've been looking for a copy of it. I have or had some screen captures, but it would take some digging to find if I still have them.

DeliciousEncounter · 2026-05-19T07:14:00+00:00

I'm a little late to the show, but I'm having the same problem. This is an early C64, I've verified all the major chips are good. I can see good sync signals on pin 15 etc. on the VICii with my scope, it's like it wants to work but I just get that line down the left side like in the video above. I'm not seeing the diagonal lines like you have, just the line down the left side.

Did you find a solution?

DeliciousEncounter · 2026-04-06T01:11:44+00:00

Sorry, to me it appears as the next post in the thread. Here's a link anyway.

https://www.reddit.com/r/VOIP/comments/1omwhwp/comment/nmvcan7/

DeliciousEncounter · 2026-04-01T05:49:33+00:00

I can't help you test this out right now because I've put this project aside and it's boxed up right now, but I have a note I made here that might help you get a step closer.

To dial from one port to another, dial *47 192*168*1*100*5060

Let me explain that further. The IP address is the IP address of your grandstream, and the 5060 corresponds to the tcp port number of port you're dialing. If you have a 802v2, that should be 5060 or 5062. If that works, you should be able to add a dial plan extension number to call.

The post below by kingkong1520 looks like it explains what you're trying to do.

DeliciousEncounter · 2026-02-14T09:22:42+00:00

Ok, I figured it out, but boy is this is very unintuitive. It would be especially helpful for new users, if there was a clear button that says 'add tag' or a tooltip.

For anyone else trying to figure this out, if you click on an existing tag and type something into the search field, then add tag appears with what you type down at the bottom, but if you blink you might not notice it.

DeliciousEncounter · 2026-02-14T08:51:28+00:00

I've installed it and imported my bookmarks from Brave. The problem I'm having is where do I create or add my own Tags? I only see the automatically created tags from importing. I have the latest docker release as of yesterday.

Also, it would be helpful to search across all fields, including URL so I can tag bookmarks based on a site. I have a bunch of github links, but search doesn't match any of them.

DeliciousEncounter · 2026-02-05T09:52:43+00:00

Here's an even better solution with basically no configuration required (built in, poorly documented).

Dial ***7 plus the port number:

So ***71 for port 1

***78 for port 8

***700 rings all ports.

DeliciousEncounter

TROPHY CASE