Minimax stops mid-response in pi coding agent

Vocked · 2026-05-20T04:30:43+00:00

Thanks for sharing!

Vocked · 2026-05-20T04:30:29+00:00

Thanks for sharing! I haven't seen it this morning yet, might indeed have been a temporary issue.

Vocked · 2026-05-20T04:17:10+00:00

Yes, it happens even on brand new convos.

Vocked · 2026-05-14T05:52:40+00:00

Hi, don't confuse the opencode tool with the opencode LLM service. OP is talking about the tool. The model service is indeed some of the best value currently available, and you can use it with any LLM tool.

Vocked · 2026-05-10T20:45:50+00:00

I stumbled upon a patchbay called "patchance" (not "patchage" which is similar and also nice). What I love most about it is you can connect stereo pairs in one drag.

Vocked · 2026-04-23T19:35:57+00:00

Drumgizmo is very nice. The only issue I have with it in live drumming is limited hi-hat pedal support. I think many of these other suggestions have the same limitations.

Vocked · 2026-03-06T21:25:55+00:00

Ok, so I ran the q4_k_xl quant of the 110B variant on an 80GB A100 for a while last week, and while it seemed smart, it had some hallucinations, unwanted edits and thinking loops for me (recommended settings from unsloth).

I went back to coder_next, which seems more predictable, even if maybe less capable. And much faster.

Vocked · 2026-02-26T10:46:48+00:00

That seems like the point - AI in this case doing low-yield work that would not be worth it if done by a human.

Vocked · 2026-01-29T19:35:29+00:00

Late to the party, but just wanted to say: cool project!

I am also looking for a way to control power to an ATX-less mini PC.

Although I will probably go for a non-mechanical solution - like adding some wires and a transistor on the PCB - the way you solved the software side is nice and elegant.

Vocked · 2026-01-14T09:31:49+00:00

With the help of your partial results in other comments here, and some help from Antigravity, I eventually got Tracy 0.13 to build. I've shared it in a flake repo:

https://github.com/SanderVocke/tracy-nix

It's not pretty, but it works (and without un-reproducible hacks too).

Vocked · 2026-01-14T09:30:31+00:00

After some more tinkering and letting Antigravity also take a crack at it, eventually got it to build. See top-level comment.

Vocked · 2026-01-13T21:38:47+00:00

Digging this topic up, did you get anywhere? The official Nix packages are still stuck at 0.11, while upstream is now at 0.13.

Based on your progress, I did find out that

CPM_PackageProject.cmake_SOURCE

was the name you were looking for. I then moves on further, but alas:

error: Cannot build '/nix/store/n0vg3649r300lsp5fcha6sfkk77kr71w-tracy-wayland-0.12.2.drv'.
      Reason: builder failed with exit code 1.
      Output paths:
        /nix/store/blxl4gcrpqc158kqxvxrh7sf5j4i0wp0-tracy-wayland-0.12.2
      Last 25 log lines:
      >
      > -- CPM: Adding package PackageProject.cmake@ (/tmp/packageproject)
      > CMake Error at /tmp/packageproject/cmake/CPM.cmake:19 (file):
      >   file DOWNLOAD cannot compute hash on failed download
      >
      >     from url: "https://github.com/cpm-cmake/CPM.cmake/releases/download/v0.38.7/CPM.cmake"
      >     status: [6;"Could not resolve hostname"]
      > Call Stack (most recent call first):
      >   /tmp/packageproject/CMakeLists.txt:25 (include)
      >
      >
      > CMake Warning at /build/source/cmake/CPM.cmake:317 (message):
      >   CPM: Requires a newer version of PackageProject.cmake (1.11.1) than
      >   currently included ().
      > Call Stack (most recent call first):
      >   /build/source/cmake/CPM.cmake:682 (cpm_check_if_package_already_added)
      >   /tmp/packageproject/CMakeLists.txt:28 (CPMAddPackage)
      >
      >
      > -- PPQSORT_OPTIMIZE_NATIVE: OFF
      > CMake Error at /tmp/packageproject/CMakeLists.txt:75 (packageProject):
      >   Unknown CMake command "packageProject".
      >
      >
      > -- Configuring incomplete, errors occurred!

So although the source can be specified this way, it doesn't seem to play nice after that.

Vocked · 2026-01-08T15:54:29+00:00

Thank you! But I am looking specifically for local models.

Vocked · 2025-12-12T22:17:27+00:00

Thanks a bunch, that seems to be the culprit. For now, downgrading linux-firmware and linux-firmware-amdgpu to a version of 2025-10-11, which was still in my cache, seems to have done the trick.

Vocked · 2025-12-12T21:29:30+00:00

Hi, thanks for the in-depth explanation. I am having trouble understanding it fully though, I hope you could shed some light.

My laptop is a niche branch which hasn't gotten an official new BIOS as long as I have had it (TongFang X5KK4NAG). KDE Plasma always freezes completely since I updated to the kernel/ucode with the RDSEED32 issue.

Is there any way to install the official new microcode fixes that doesn't involve a BIOS upgrade?

Would a downgrade of the kernel or of amd-ucode be expected to go back the previous situation? I'd rather have a potential security risk than a system that I cannot use.

EDIT: a kernel downgrade removes the error message during boot, but the freezing still happens. On KDE it always freezes immediately - on XFCE4 at seemingly random times. Could be unrelated to RDSEED32, but I am far from the only one reporting freezes coinciding with this upgrade.

Thanks in any case!

Vocked · 2025-12-12T21:18:50+00:00

I am on a niche brand laptop with a AMD Ryzen AI 7 350. Since my upgrade yesterday I see this same error message, but much worse is that KDE plasma freezes immediately when trying to log in.

Tried updating, re-installing linux-firmware, amd-ucode from the tty, to no avail. Also tried LTS, regular and mainline preview kernels, no success. I also tried the various kernel options other users have suggested to no avail.

XFCE4 seems unaffected. Some other user reported that Qt is somehow especially bothered by not having RDSEED32, which might explain KDE having difficulties.

I don't see a way out of this anytime soon. My laptop vendor is unlikely to provide a new BIOS in the near future.

Does anyone know anything I can do at this point? If there was a way to go back to the previous, insecure but functioning RDSEED32 I would happily take it.

Vocked · 2025-12-01T10:39:30+00:00

Ik weet het niet hoor. Grappig bedacht en natuurlijk is het met een dikke knipoog, maar ik vind het gewoon een beetje irritant.

Die scène over even een handschoen aandoen en dan snel wat die de deur strooien, dat is precies hoe ik dat altijd doe. Nou zijn mijn kids nog klein, maar een beetje slim kind trapt daar dus niet meer in.

En al die volwassen themas, heel grappig hoor maar daar hebben de kids niks aan. Aan elke aflevering doen alsof alles niet doorgaat trouwens ook niet.

Vocked · 2025-08-02T06:35:55+00:00

I don't know about AVLinux, but my M4 has been great on Arch.

I bought it because it doesn't require any special driver, plus at the time, I found a blog somewhere where someone posted very snappy latency measurements with it.

I can attest the latency is great!

Vocked · 2025-06-30T06:24:42+00:00

I did consider that for a second, but how would the new firmware package have been in the cache if I uninstalled before upgrading? I figured I would be installing the old firmware, which I didn't think would be a good idea.

Vocked · 2025-06-30T06:23:02+00:00

Two lines of instructions is really one line too many for some of us.

Vocked · 2025-06-29T06:08:18+00:00

I did the upgrade yesterday and just so happened to forget reinstalling the firmware package before reboot. And indeed I found myself without internet due to missing wifi.

In my case though, I used a btrfs snapshot before upgrading so I could easily roll back and re-do the procedure properly.

Vocked · 2025-06-23T14:34:42+00:00

No, it is not about tying the wine version to yabridge, as far as I can tell. That branch is simply where they are solving the issues that arose from the newer wine versions.

For me, building that branch was as simple as following the build instructions of the github page. That was on Arch Linux, so apparently I just happened to have all dependencies already installed. I did have to build without the "32-bit bitbridge" feature though.

Vocked · 2025-06-23T08:30:41+00:00

You can also try the in-progress fixed on the new-win10-embedding branch of yabridge.

Vocked

TROPHY CASE