pi 5

With the Raspberry Pi 5's exposed PCI Express connector comes many new possibilities—which I test and document in my Pi PCIe Database. Today's board is the Geekwork X1011, which puts four NVMe SSDs under a Raspberry Pi.

Unlike the Penta SATA HAT I tested last month, this carrier uses thinner and faster NVMe storage, making it a highly-compact storage expansion option, which has the added benefit of freeing up the top of the Pi 5 for other HAT expansion options.

Radxa's latest iteration of its Penta SATA HAT has been retooled to work with the Raspberry Pi 5.

The Pi 5 includes a PCIe connector, which allows the SATA hat to interface directly via a JMB585 SATA to PCIe bridge, rather than relying on the older Dual/Quad SATA HAT's SATA-to-USB-to-PCIe setup.

Does the direct PCIe connection help? Yes.

Is the Pi 5 noticeably faster than the Pi 4 for NAS applications? Yes.

Is the Pi 5 + Penta SATA HAT the ultimate low-power NAS solution? Maybe.

...and it's not just for Pi Day.

After posting my deep-dive into the Pi 5's new BCM2712 and RP1 silicon this morning, someone linked me to this GitHub issue: Raspberry Pi 5 cannot overclock beyond 3.0GHz due to firmware limit(?).

For the past few weeks, a few blog readers (most notably, tkaiser—thanks!) commented on PLLs, OPP tables, and DVFS and how something seemed a little off with the 3.0 GHz CPU limit—which was apparently recommended by Broadcom, according to that GitHub issue.

But today, @popcornmix generated a test firmware revision without the 3.0 GHz limit, and zealous overclockers can get to pushing the clocks higher.

Silicon lottery.

Now that the Raspberry Pi 5s been readily available (at least in most regions) for a few months, more people started messing with clocks, trying to get the most speed possible out of their Pi 5s.

Unlike the Pi 4, the Pi 5 is typically comfortable at 2.6 or even 2.8 GHz, and some Pi 5s can hit 3.0 GHz (but no higher—more on why tomorrow well... this limit may be able to be lifted).

After some testing, I found the default 2.4 GHz clock on the Pi 5 is pretty much the efficiency sweet spot, and after a lot more testing recently, I can confirm that's still the case, testing a number of Pi 5 samples.

Power over Ethernet lets you run both power and networking to certain devices through one Ethernet cable. It's extremely convenient, especially if you have a managed PoE switch, because you get the following benefits:

• A single cable for power + Ethernet (no need for separate power adapters)
• No need to have electrical service near every device
• Simple remote power on/off capability (assuming you have a managed switch)
• Centralized power management (e.g. one UPS in a rack room covering all powered devices)

I have used the Raspberry Pi PoE and PoE+ HATs for years now, allowing me to have 4 or 5 Raspberry Pi per 1U of rack space, with all wiring on the front side. I also use PoE for cameras around my house, though there are dozens of use cases where PoE makes sense.

The Raspberry Pi, since it only requires 3-10W of power, is an ideal candidate for PoE, assuming you can find a HAT for it.

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:

Following up on my X-ray scans of the Raspberry Pi Zero 2 W two years ago, I had the opportunity to scan the Raspberry Pi 5, working with an electronics inspection lab:

I posted a video detailing everything I imaged on the board, but in this blog post, I'll hit on the highlights—the new chips at the heart of the Pi 5: the BCM2712 SoC and the RP1 'southbridge'.

My journey testing various graphics cards on the Raspberry Pi began soon after the Compute Module 4 was launched in 2020. Since then I've tested almost 20 graphics cards—with a little success.

But there were two roadblocks to getting drivers for even older AMD radeon drivers working well:

Sorry to clickbait with that title... but it's actually true. I can help you improve power use by 140x—for power off power consumption, at least.

By default, the Raspberry Pi 5 (like the Pi 4 before it) leaves the SoC powered up (just in a shutdown state) when you shut down the Pi.

Because of this, a Pi 5 will still sit there consuming 1.2-1.6W when completely shut down, even without anything plugged in except power.

That's a lot—even compared to a modern desktop PC!

Why is this?

Apparently some HATs have trouble if the 3v3 power rail is off, but 5v is still active—which would be the case if you completely power off the SoC, but still have your 5V power supply plugged in.

Because of that, the Pi ships by default with the setting POWER_OFF_ON_HALT=0, and the Pi eats up precious watts all the time.

In my video about the brand new Raspberry Pi 5, I mentioned the new external PCIe port makes it possible to boot the standard Pi 5 model B directly off NVMe storage—an option which is much faster and more reliable than standard microSD storage (even with industrial-rated cards!).

Enabling NVMe boot is pretty easy, you add a line to /boot/firmware/config.txt, modify the BOOT_ORDER in the bootloader configuration, and reboot!