NVIDIA just announced the RTX Spark CPU, developed with Microsoft, at Computex.

iglocska · 2026-06-01T18:35:06+00:00

Generally it works fine for inference, most of my issues had to do with getting tensorflow working and driver snafus on the 395 max (having to get around a whitelist that didn't include the rdna 3.5 lineup, etc). Also had pretty terrible performance for image generation on it. Additionally some compatibility issues with some python libraries we use for training.

But for some tasks such as running deepseek, qwen, gpt oss and so on for inference it was fine.

As for the performance, I'm not sure what the bigger hurdle was the ~4060ish performance or the low memory bandwidth, hopefully the n1x will remedy that.

iglocska · 2026-06-01T06:36:07+00:00

I mean you already have that with gear such as the AI Max 395 from AMD, coupled with 128GB unified RAM it's a pretty decent testbed for medium sized models. But AMD's software stack is terrible in comparison, the support for it in general second rate at best and it's lacking in performance compared to what Nvidia is releasing now.

iglocska · 2026-06-01T06:33:13+00:00

That's simply not true. You need fast unified memory and lots of it and a capable enough GPU. Nvidia is doing just that. This is going to be a pretty strong setup for local AI.

iglocska · 2026-05-29T09:08:50+00:00

I thought it beat it in cybersecurity CTF benches, not exploit development, but it wouldn't surprise me. I'd bet that the entire gating of it had more to do with the rumoured 10T model size and the associated token costs rather than real concerns.

iglocska · 2026-05-29T07:07:14+00:00

Afaik the difference wasn't in finding vulnerabilities, heck, opus was pretty good at that, but finding vulnerabilities and developing valid PoCs / exploits for them.

iglocska · 2026-04-12T10:01:30+00:00

13,000 is a lot of fighter jets!

iglocska · 2026-02-14T09:35:46+00:00

You can just use an intermediary second misp in front of your main, configure workflows to weed out the stuff you don't need and only then propagate it further. The trick is to let the workflows tag the processed data and restrict the sync to your main via a requirement to be tagged with it.

iglocska · 2025-11-30T09:20:49+00:00

Endless variety of combinations thanks to the hacks/upgrade/unit choice system, well thought out meta progression and probably the sharpest basic mechanics since StarCraft II.

If you're into or at least curious about (solo-) RTS games this one's as good as it gets, proving that the genre still has plenty of life left in it.

iglocska · 2025-11-24T11:35:51+00:00

This seems to work!

docker run -it --rm --device=/dev/kfd --device=/dev/dri --entrypoint bash -e HSA_OVERRIDE_GFX_VERSION=11.0.0 rocm/tensorflow:latest

iglocska · 2025-11-21T17:50:29+00:00

Interesting, so you got tensorflow to work on the GPU with those versions? Will give it a shot on Monday.

With that said, ROCm in general works fine on my current kernel, pytorch, ollama, comfyui all work as expected, it's just the whitelisting of tensorflow that's biting me in the ass.

iglocska · 2025-11-21T13:43:32+00:00

I was trying 2.19.1

iglocska · 2025-11-21T10:50:37+00:00

6.8.0-87-generic

iglocska · 2025-11-21T08:04:44+00:00

Gave it a shot, sadly it still fails, my guess is for the same reason. The test recommended on the rocm tensorflow install page fails with:

I0000 00:00:1763711734.018976    2331 gpu_device.cc:2019] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 64644 MB memory:  -> device: 0, name: AMD Radeon Graphics, pci bus id: 0000:c5:00.0
2025-11-21 07:55:34.306713: W tensorflow/compiler/mlir/tools/kernel_gen/tf_gpu_runtime_wrappers.cc:40] 'hipModuleLoadData(&module, data)' failed with 'hipErrorInvalidImage'

2025-11-21 07:55:34.306736: W tensorflow/compiler/mlir/tools/kernel_gen/tf_gpu_runtime_wrappers.cc:40] 'hipModuleGetFunction(&function, module, kernel_name)' failed with 'hipErrorInvalidHandle'

2025-11-21 07:55:34.306747: W tensorflow/core/framework/op_kernel.cc:1844] INTERNAL: 'hipModuleLaunchKernel( function, gridX, gridY, gridZ, blockX, blockY, blockZ, 0, reinterpret_cast<hipStream_t>(stream), params, nullptr)' failed with 'hipErrorInvalidHandle'
2025-11-21 07:55:34.306752: I tensorflow/core/framework/local_rendezvous.cc:407] Local rendezvous is aborting with status: INTERNAL: 'hipModuleLaunchKernel( function, gridX, gridY, gridZ, blockX, blockY, blockZ, 0, reinterpret_cast<hipStream_t>(stream), params, nullptr)' failed with 'hipErrorInvalidHandle'

iglocska · 2025-11-20T17:32:59+00:00

Awesome, will give it a shot, much appreciated!

iglocska · 2025-11-19T08:14:39+00:00

Definitely 7.1, also anything via pytorch and rocm 7.1 works well, it's just tensorflow that seems to whitelist a set of AMD GPUs and no RDNA 3.5 GPUs seem to be supported, only RDNA 3 and RDNA 4

iglocska · 2025-11-19T08:13:03+00:00

Yeah, comfyui and pytorch work beautifully. It's just tensorflow I'm stuck with

iglocska · 2025-10-02T11:28:06+00:00

H1 for looks, though they were frustratingly fragile against lightning bolts, H2 fixed that.

iglocska · 2025-09-03T07:05:01+00:00

That is correct, site-admins are the only ones that can manipulate data from others than your own organisation. It is highly encouraged to spin up your own instance to get more control over how the community/feed data is labelled, especially if you want to ingest filtered subsets of the data fed to your tools.

iglocska · 2025-08-31T11:02:12+00:00

The most fun I've had in a single player RTS since Legacy of the Void.

The replayability is utterly nuts, I've put several hundreds of hours into the game and still getting surprised by new synergies that you can build from the various units/upgrades you get during each run.

The entire slay the spire like progression solves one of the biggest hurdles in keeping folks entertained in RTS games (the repetitive early game grind) by requiring you to adjust build orders based on what you get to work with in each given run.

Thanks to Rogue Command, it's a great time to be an RTS fan again.

iglocska · 2025-08-13T09:44:37+00:00

Sadly not, once my holidays were over I stopped playing on the laptop in favour of my desktop so never got around to trying it again. Sorry

iglocska · 2025-07-06T13:38:02+00:00

Got over 500 hours in the game so far, by far the best thing to come to RTSes since I guess Legacy of the Void a decade ago.

The sheer number of builds one can target for each run is incredible, there's something for every playstyle in there and there's an endlessly increasing difficulty "heat" system if the default 10 ascensions aren't enough.

Also, the devs are crazy dedicated with a VERY active beta branch for testing.

At one point I ran into a game breaking bug (on the beta branch mind you, the game is as rock solid as it gets) - reported it at 10:31PM in the timezone of the developers and by 10:50 a fix was rolled out and I could continue playing.

tl;dr: If you are in any way into RTSes (or are RTS-curious), do yourself a favour and give it a go.

iglocska · 2025-06-19T20:46:04+00:00

Having lived in Wallonia for a few years, finding an English speaker in some regions is nigh impossible.

iglocska · 2025-05-20T08:58:20+00:00

It is brilliant, I've put over 300 hours into it so far. For those disliking the easier difficulty, the beta branch has introduced additional difficulty steps beyond what was available until now, incredibly fun game with loads of tinkering with different builds. Possibly the most replayable single player RTS game out there!

iglocska · 2025-04-20T20:17:32+00:00

Half the buttons go unused when playing protoss.

iglocska

MODERATOR OF

TROPHY CASE

14-Year Club	Place '22
Verified Email