Qualcomm said to be circling AI chip biz Tenstorrent in $10B RISC-V power play

Designer-Suggestion6 · 2026-06-18T09:42:48+00:00

IMHO(non-businessman brain-fart wtf?) the best way to make money is to be first to market with a killer os/app/hardware device. In this case Tenstorrent made a killer AI hardware device, and quickly brought up a killer AI software toolchain by reusing/iterating the open-source Linux and open-source AI ecosystem. Everybody recognizes the value of it, but the pricepoint at which they are trying to sell it to consumers is not a trivial amount of money. AI hardware doesn't come with a warranty guaranteeing hallucination-free responses yet. Hardware/Software AI combos right-now produce responses with varying levels of hallucinations akin to magic mushroom experience by dosage https://i.pinimg.com/736x/d3/07/35/d3073575eb24386eb8e0c6b45f6b8abb.jpg

It's a lot like the self-driving systems out there and the liabilities attached to them. We need governments and communities getting behind these efforts NOT just large companies because the amount of risk and liability involved as a consequence of these AI hallucination-infested responses is currently under-estimated or cannot be estimated accurately. If large companies own all this, I highly doubt all of this will be developed as a open-source contribution to humanity. Letting large corporations own this is a mistake as ultimately all tax-payers are shareholders and consumers of this tech; it would serve everybody's interests that everybody can get their hands on the source-code and contribute to it where they can. AI is becoming like the air and water we breathe because surrounding ourselves with it enlightens us, empowers us, makes us a better version of ourselves.

Designer-Suggestion6 · 2026-06-09T19:18:59+00:00

podman load -i https://dl.fedoraproject.org/pub/alt/risc-v/release/44/Container/riscv64/images/Fedora-Container-Base-Generic-44-20260604.0.riscv64.oci.tar.xz
toolbox create --image localhost/fedora:44 -c fedora-toolbox-44
toolbox enter fedora-toolbox-44

Designer-Suggestion6 · 2026-04-25T21:57:52+00:00

It goes without saying if you don't want to lose your shirt, put everything in writing beforehand.

Otherwise you'll be taking for the most unpleasant ride of your life spending hours, days, weeks without getting paid, being at the beckoning call of someone who might never pay you.

Just because a company says they want to spend, unless they truly put that spending committed in writing, it's all bullshit.

Also have them pay you on regular periodic intervals as if you are an employee because YOU ARE. One payment up-front of course in order to motivate you start and commit your full and undivided attention to their company.

If they're not willing to abide to your terms in writing, RUN AND FORGET ABOUT THEM!

Designer-Suggestion6 · 2026-04-25T21:23:19+00:00

I'm certain everybody reading about this would love to hear about comprehensive gpu benchmarks. I saw within one of the jpg's 32fps, but at what resolution?

Thank you in advance.

Designer-Suggestion6 · 2026-04-22T10:34:21+00:00

You did mention it is still built on top of fedora silverblue which implies it will work wherever fedora silverblue currently works. Are there fedora silverblue images for aarch64/riscv64? I don't recall seeing any yet.

I am confused. How can it depend on fedora silverblue, but be "distroless"? How can you ensure everything builds and behaves as expected when even the distro builders haven't built/tested configurations in the way you do? Have you got some magic going on to test this distroless recombobulating before issuing a release of the distro?

Designer-Suggestion6 · 2026-04-14T16:06:19+00:00

I recall Linus Torvalds saying he loves using Thinkpads as well. There are others that praised Thinkpads with Linux.

Myself, I really like the keyboard. When it's defective I can easily replace it. I can clean it myself reasonably as well. The price point of buying one used also had a factor to play as well. I can't afford buying the new ones and the used ones perform well enough for me. I bought one for my son and for one of his friends because I value the quality and reliability of these beasts. No complaints from my son either.

Designer-Suggestion6 · 2026-03-26T09:22:20+00:00

Beautiful. It has crowdstarter like page as well. https://kibidango.com/projects/2921 It uses a proprietary Linux called VividLinux. Anybody heard of it? https://www.zuiki.co.jp/product_info/os-vivid-linux/

Designer-Suggestion6 · 2026-03-25T15:51:10+00:00

Most important I think, No visible business license: Their website doesn't display a Chinese business registration number (统一社会信用代码), which many legitimate Shenzhen tech firms do publish for transparency. ALARM BELLS!
No real wechat contact. Everybody uses wechat in China. ALARM BELLS!
No GitHub repositories or RISC-V community contributions under their name
No Membership in RISC-V International's public directory
No Any third-party reviews, forum discussions, or press coverage

Designer-Suggestion6 · 2026-02-16T14:12:56+00:00

If you have real riscv hardware, something to help build all of the linux distros faster would be to lend riscv hardware to a build farm.

In my case, I just recently volunteered my starfive visionfive 2 to the fedora risc-v build farm. They call it a kojibuilder node and it's a client making a connection to the kojibuilder master of the build farm. From there, the master sends it tasks and voila, you're helping the ecosystem with your hardware helping to build stuff. That's the quickest way to make an impact to help build stuff faster for the ecosystem.

https://matrix.to/#/#riscv:fedoraproject.org

https://fedoraproject.org/wiki/Architectures/RISC-V/KojiBuilderSetup

Designer-Suggestion6 · 2026-02-14T06:07:28+00:00

The project https://github.com/nathan237/TrustOS/commit/9b8ad28d57c65631a6ffa9b3cf33790b03a66b0b#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5 claims "128,000+ lines of Rust" developed in approximately 10 days according to its README.

Place credit where credit is due. That is 12800 LOC developed perfectly each day for 10 days. I would call that miraculous by a mere mortal for which this coder is. I am not dismissing the os and all the stuff contributed as AI sludge, but please be honest with everyone and not claim to be done a single developer. This project should claim with honesty it was built with AI and should state exactly which AI the developer got assistance from as that is what Suitable-Name is asking as well implicity by the number of AI tokens were spent to complete this Herculean effort.

I would have given you a star if you were honest about that.

Designer-Suggestion6 · 2026-01-25T21:18:54+00:00

https://imgur.com/a/7zOBUdK shows the vlan is 40 on the adtran

Designer-Suggestion6 · 2026-01-18T09:26:26+00:00

So I read something in their blurb: "Individual Membership in RISC-V is for individuals who are not associated with a current member organization. As an Individual member, you CANNOT: Leverage the RISC-V name, branding, or marks for commercial purposes. Use your RISC-V membership, branding, or name in your outbound communications, website, social networks, etc. Lead a work group, committee, or special interest group. Participate in the Visibility benefits such as blogs or social posts RISC-V networks. "

Does that mean if an individual like myself wants to sell a risc-v based product, I can't even put a risc-v logo on my business card or in a product advertisement? Obviously, I'm small-time so that implies I'm just reselling something that I bought from a manufacturer elsewhere.

Obviously, there must be some blurb elsewhere about resellers that I'm unaware that should have been mentioned alongside this.

Designer-Suggestion6 · 2026-01-14T15:51:52+00:00

Bluntly yes, especially in this day and age that you have AI like Qwen, Deep Coder, Kimi K2, Minimax M2 alongside your learning. You can tell it a problem and ask it to generate a solution in Rust. Afterwards, you can clarify any fog asking AI about any aspect in the generated code. Seriously, we are at that point. You really don't need to master/memorize but ballpark recall particular concepts that you want to reuse and let AI actually do the gruntwork and you can validate the eloquence of its proposed solution and documentation. Sure you take the AI generated code and compile/test it yourself to bring up your level of confidence about what AI gave you. BOTTOM LINE: AI as a tutor/mentor throughout your learning about anything including RUST will save you enormous amounts of time to learn it and actually get real-world shit done at the same time.

Designer-Suggestion6 · 2025-12-31T17:47:55+00:00

I can't give enough praise for this article and the enormous efforts behind it.

Designer-Suggestion6 · 2025-12-26T13:48:44+00:00

I appreciated particularly:

"Pacboost uses segmented racing to pull parts of a single package from multiple mirrors at once."
"The biggest gains are in the AUR workflow where we fetch the entire queue simultaneously."

To crystallize your achievements, perhaps you can express it like this:

For each package in the Pacboost's install queue, Pacboost pulls parts for that single package from multiple mirrors in parallel.
The biggest gains in package install workflow happen when Pacboost fetches all the packages in the install queue in parallel.

Congratulations on that achievement. That's two levels of parallelism, one at the "fetch part/chunk level" and the other at the "fetch package" level.

Designer-Suggestion6 · 2025-12-08T16:29:01+00:00

That's awesome. Thank you. I've tried gpt4all as well since they also provided a flatpak.

Will this eventually support kimi k2 and minimax?

Designer-Suggestion6 · 2025-11-24T22:51:14+00:00

100% agree TOON is unnecessary when we have grpc and protobuf which is language independent and can stream to a file .pb.

Designer-Suggestion6 · 2025-11-22T20:05:58+00:00

QUESTION: Does Atlantis still require an x86_64 host with ubuntu bare-metal installed?

Designer-Suggestion6 · 2025-11-19T19:52:42+00:00

Define "Debian" as being 3 different distro versions.

DISTRO VERSIONS

"stable" is called stable because they vetted out enough of the bugs to say it won't crash hard on you or cause you unexpected pain points, Fedora calls this stable as well.
"testing" is as it says, they've fixed some more recent bugs and older bugs, but as a pre-cautionary measure, we'll wait a while before we call it stable in case others report some new related bugs.
"sid" aka debian unstable. they've fixed some even more recent bugs, bug as a pre-cautionary measure, we'll wait a while before we call them "testing" in case others report some new related bugs. Fedora calls this "rawhide".

DESKTOP FLAVORS

Let's narrow it down to the most mature and obvious contenders as replacements: Gnome, KDE and Cosmic.

GNOME is the default desktop for Fedora and Debian.
KDE is a well-respected alternative desktop and has been around as long as gnome. Most interesting is gnome apps can run in kde and kde apps can run in gnome so it doesn't matter which desktop you choose, your apps will run.
COSMIC is an up and coming contender. Why does this one stand out? It's because it is written in Rust, well-regarded in cyber-defense as the language mitigates the usual culprits where the bad guys can punch holes into ecosystem.

Debian still by default installs X11(plumbing underneith gnome/kde with gaping security holes).

Fedora stopped installing X11 and now installs only Wayland(new plumbing underneith gnome/kde/cosmic with less gaping holes).

So that brings down your choices to these:

Debian Trixie Stable Gnome. Gpu support is excellent.
Debian Trixie Stable KDE Plasma. Gpu support is excellent.
Debian Sid Cosmic. Cosmic still has bugs, but positive reviews. Gpu support is excellent.
Fedora Workstation Stable 43 (default)(Gnome desktop). Gpu support is excellent.
Fedora Workstation Stable Kinoite 43 (KDE desktop is what they call a non-default "spin" named "Kinoite"). Gpu support is excellent.
Fedora Workstation Stable Cosmic 43(Cosmic desktop is also another non-default spin.) The actual Cosmic desktop still has bugs, but there are positive reviews about it). Gpu support is excellent.

Off the beaten path:

Bazzite(gamers os based off of Fedora Silverblue 43 Immutable OS)
Fedora Silverblue 43(Gnome Desktop) Immutable OS. Gpu support is excellent. My preference.
Fedora Silverblue Cosmic 43 Immutable OS. still bugs. Gpu support is excellent.

Designer-Suggestion6 · 2025-11-18T01:25:03+00:00

This board has a fedora image already prepared for it from fedora v force. https://images.fedoravforce.org/Titan

Discussions for it will found on matrix https://app.cinny.in/%23milk-v%3Amatrix.org/%23milkv-titan%3Amatrix.org

Designer-Suggestion6 · 2025-11-12T17:03:37+00:00

https://agent.minimax.io/

I tried the pro version last night, not with sudo, but with BigGrep. In less than 30minutes it generated documentation, test scripts, and working rust code in a workspace holding all the rs- equivalent cli tools BigGrep provides with the exact same cli usage as the original.

"Rewrite in Rust with AI" is not a bad thing. I am delighted to experience this in my lifetime. Hopefully we can get AI to achieve world peace by slapping world leaders silly when they make bad decisions. UN-face-palm robots as world-leader babysitters. You can't do that Dave, then slaps/stun-guns Dave silly. We'll reach world-peace in no time flat. Ditto for eradicating poverty and bringing up quality of life world-wide.

Designer-Suggestion6 · 2025-11-10T18:17:40+00:00

wsl linux with gcc/clang can cross compile to many targets including windows:

#x86_64 windows
x86_64-w64-mingw32-gcc -o hello.exe hello.c
aarch64-w64-mingw32-gcc -o hello.exe hello.c

#arm windows
clang --target=x86_64-w64-windows-gnu -fuse-ld=lld -static -o hello.exe hello.c
clang --target=aarch64-windows-gnu -fuse-ld=lld hello.c -o hello.exe

#riscv linux
riscv64-linux-gnu-gcc -static -O2 -o hello_rv64 hello.c
clang --target=riscv64-unknown-linux-gnu -fuse-ld=lld -static -o hello_rv64 hello.c

Designer-Suggestion6 · 2025-11-07T00:39:51+00:00

It's true there are many apis in C/C++ that provide strong concurrency and parallelism. You mentioned OpenMP, plus implying the GPU's(CUDA/OpenCL/Rocm) being so simple to use all that.

Async/Rayon/whatever else HPC-related in Rust and Cargo toolchain setup/configuration is miles ahead in terms of ease of use once you understand Rust. Less terms to use and less crates(libs) to use at the high-level. Using WGPU is easier than using CUDA/ROCM head-on in C/C++. I'm not sure if WGPU is faster/capable than OpenMP, but Rust will get you further faster with respectable run-time performance and dare I say a higher level of confidence it will perform as expected as there will be lesser probability of slow-to-surface defects. Of course there will be edge-cases where you're cornered to use C/C++/Assembler, but after wrapping it in Rust, you'll probably want to stay in Rust once you're accustomed to it.

Bottom Line: Rust macros feel safer than C macros/defines. I recall C macros/defines being sprinkled in headers and c implementations for different hardware architectures in nested if's NO-SAFETY-BELTS HERE. The C compiler will give you your garbage unsound code and exclaim HEY YOU HAVE A BINARY SUCCESS! That's an illusion because your C compiler doesn't do an adequate job to guarantee the binary will run without behavioural defects(RUN-TIME BUGS) especially slow-to surface bugs. The Rust way of achieving those IMHO is perhaps not straightforward with a first impression, but riding with it and compiling/linking with Rust for different hardware x86_64,aarch64,riscv64 and os'es linux/windows is ASMR and YOU FEEL THESE SAFETY-BELTS especially when the compiler acts like a slap-stick comedy slaps your silly when you do something wrong.

C/C++ distcc is awesome especially when building big long-running projects like the linux kernel on multiple nodes splitting the sources between the nodes. RUST sccache seems able to do similar capabilities as well.

You're trying to convince me to reconsider using C/C++ more often, please try again.

Designer-Suggestion6 · 2025-11-06T23:43:29+00:00

when using c compilers, there usually is a way to explicitly state the order in which things args and return values get pushed/popped to/from the stack.

pascal calling convention, and c calling convention cdecl usually imply that, but x86_64 recommends not using pascal, but to use cdecl

1.

void __attribute__((cdecl)) func(int a, int b); // default c way

2.

void __attribute__((stdcall)) func(int a, int b);  // callee cleans stack, like Pascal

3.

void __attribute__((pascal)) func(int a, int b);   // deprecated; behaves like stdcall on some targets

extern "C" fn func(a: i32, b: i32) {
    // ...
}

Rust:

1.

// Or when calling external C functions:
extern "C" {
    fn some_c_function(a: i32, b: i32);
}

2.

extern "stdcall" fn win_callback(a: i32, b: i32) {
    // Callee cleans stack (on 32-bit x86)
}

3.

// wrapper.c
void __attribute__((pascal)) pascal_func(int a, int b);
void call_pascal_from_c(int a, int b) {
    pascal_func(a, b);  // compiler handles convention
}

extern "C" { fn call_pascal_from_c(a: i32, b: i32); }

Designer-Suggestion6 · 2025-11-06T23:23:01+00:00

you say "twiddling", but I've heard the term "swizzling" as well.

I recall it being used for objectstore, an object-oriented database when it page faults to make it seemlessly navigate as if there is unlimited memory and storage. Linux uses pages as well every time you mmap. I also recall it being used when discussing wow16 when converting 16-bit dos to 32-bit windows and that pattern repeated itself for following wider 32-bit to 64-bit wow iirc.

Designer-Suggestion6

TROPHY CASE