open source

Popular Rockchip SBC distro in limbo after maintainer burns out

Recently Joshua Riek posted he's dropping off from GitHub. If you haven't heard of him, he's one of the few reasons working with Linux on Rockchip SBCs is so much easier today than it was just a few years ago.

His Ubuntu Rockchip distribution is built for Ubuntu 22 and 24, and they've been maybe the most popular and stable way to run Ubuntu on Rockchip devices.

So popular, in fact, that manufacturers who use Rockchip, like Turing Pi, build their own official images on top of Joshua's.

XKCD Dependencies

Now, if you're reminded of XKCD #2347, yeah, I am too.

Use an External GPU on Raspberry Pi 5 for 4K Gaming

After I saw Pineboards 4K Pi 5 external GPU gaming demo at Maker Faire Hanover, I decided it was time to set up my GPU test rig and see how the Pi OS amdgpu Linux kernel patch is going.

GLmark2 running on Pi 5 with AMD RX 460 external GPU

I tested it out on a livestream over the weekend, but I thought I'd document the current state of the patch, how to apply it, and what else is left to do to get full external GPU support on the Raspberry Pi.

I also have a full video up with more demonstrations of the GPU in use, you can watch it below:

Sipeed NanoKVM: A RISC-V stick-on

Sipeed NanoKVM

This is the Sipeed NanoKVM. You stick it on your computer, plug in HDMI, USB, and the power button, and you get full remote control over the network—even if your computer locks up.

How did Sipeed make it so small, and so cheap? The 'full' kit above is about $50, while the cheapest competitors running PiKVM are closer to $200 and up!

This blog post is a lightly-edited transcript of the following video on my YouTube channel:

Saying a lot while saying nothing at all about Ansible AWX

A few days ago, the post Upcoming Changes to the AWX Project came across my feed. An innocuous title, but sometimes community-impacting changes are buried in posts like this. So, as an interested Ansible user, I read through the post.

In 1,610 words, almost nothing of substance was written.

A lot about how it's not 2014 anymore, so 2014-era architecture doesn't suit AWX. Then a big bold disclaimer at the bottom:

Before we conclude, we should be clear about what will not happen.

  • We are not changing the Ansible project
  • We are not adjusting our OSS license structure

Ultimately, we need to make some changes to the way our systems work and our projects are structured. Not a rewrite but a refactoring and restructuring of how some of the core components connect and communicate with each other.

Corporate Open Source is Dead

IBM is buying HashiCorp for $6.4 billion.

That's four months after HashiCorp rugpulled their entire development community and ditched open source for the 'Business Source License.'

As someone on Hacker News pointed out so eloquently:

IBM is like a juicer that takes all the delicious flavor out of a fruit

skywhopper replied:

HashiCorp has done a good job of pre-draining any flavor it once had.

Some people wonder if HashiCorp's decision to drop open source was because they wanted to juice the books for a higher price. I mean, six billion dollars? And they're not even a pointless AI company!

Highly-condensed time-lapse footage with Frigate

Frigate's 0.13.0 release included a feature near and dear to my heart: easy exporting of timelapses, straight from the Frigate UI.

I'm a little bit nutty about timelapses, and have made them with dashcams, GoPros, full DSLRs, webcams, and even Raspberry Pi.

But one thing I haven't done (until now) is make easy timelapses from IP cameras like the Annke 4K PoE cameras I use for security around my house.

Eventually I'm planning on automating things further, but for now, here's my process for building up a timelapse that's relatively small in file size, preserving only frames where there's motion from frame to frame.

For something like clouds/sky, or natural environments, it's better to do a straight timelapse export and maybe recompress it if you want, but for indoor or outdoor security footage, it's nice to condense it down.

Raspberry Pi IPO: Selling out?

Raspberry Pi 5 blended into 100 dollar bill USD

Raspberry Pi is looking into an IPO (Initial Public Offering).

But wait, Raspberry Pi's a non-profit! They can't do that? And who would want stock in Raspberry Pi anyway? Their core market hates them—they abandoned hobbyists and makers years ago!

And there are like tons of clones and competitors, nobody even needs Raspberry Pi? Plus, aren't they crazy-expensive? It's like a hundred bucks now, and that's if you can even find one to buy!

Well, hold on a second... there are a lotta misconceptions out there. In this post, I'll walk through what's actually happening, and also through things I see online.

This blog post is a lightly-edited transcript of a video on my YouTube channel, which you can watch below:

MNT Reform - a hackable laptop, not for everyone

MNT Reform bottom with purple battery cells

The MNT Reform's design, the components, everything—is open source. If iFixIt did a teardown, they'd probably give it an 11 out of 10.

You can replace individual battery cells! Some people with these laptops hacked in their own speakers, added more internal Ethernet, or even swapped out the CPU itself.

Does that mean I think you should buy it? No, probably not. It's expensive (starting at €1199), and it's built for a certain type of person. It's not gonna replace a MacBook or a cheap Chromebook.

But why does this exist, and why am I excited about it?

Disclaimer: The reform used in this review was sent to me for testing; it's already been shipped back to MNT Research. They haven't paid me anything, and they have no input into the content of this blog post.

How to customize the dtb (device tree binary) on the Raspberry Pi

Every so often, when you're debugging weird hardware issues on SBCs like the Raspberry Pi, it's useful to get way down into the guts of how the Pi represents its hardware to Linux.

And the Linux kernel uses a method called Device Tree overlays to do it. On the Pi 5 (and other Pis), these overlays are stored as .dtb files inside the /boot/firmware directory, and there's an overlay for every major Raspberry Pi hardware model.

I've had to modify the dtb files in the past to increase the PCIe BAR space for early GPU testing on the Compute Module 4. And recently I've had to mess with how the PCIe address space is set up for testing certain devices on the Raspberry Pi 5.