Your Surface RT Can Become Useful Again, With Raspberry Pi OS

Over the years there have been so many times when Microsoft came up with a product that so nearly got it right, but which tanked in the market because the folks at Redmond had more of an eye to what fitted their strategy than what the customer wanted. The Surface RT was one of these: while the hardware was at least as good if not better than Apple’s iPad, its ARM CPU and an ill-advised signed-apps-only policy meant the tablet couldn’t access the huge existing library of Windows software.

Consumers didn’t want a tablet with next-to-no apps, so it failed miserably. Never mind though, because [Michael MJD] has a video showing how an RT can be given a new life from an unlikely source, with the installation of Raspberry Pi OS.

The video pretty closely follows this guide, and involves creating a Raspberry Pi OS install medium modified with RT-specific kernel modules and device tree. It’s possible because the 32-bit ARM architecture is one of those which Raspberry Pi OS targets, and while a few things such as graphics acceleration don’t work, it’s still successful (if a little slow).

Oddly this is a technique not unlike one from the earliest days of the Raspberry Pi, when we remember people in Raspberry Pi Jams showing off the ancestor of the modern OS running on cheap ARM-based netbooks. In those cases the hack relied on transplanting the Pi userland over the device’s existing kernel, we’d be interested in an explanation of how the RT can use the Pi kernel without the famous Broadcom BLOB intended for the Pi.

We have a soft spot for the RT, as we said a good product held back by a very bad software decision. Seeing it take a new life years later is thus pleasing to us.

Continue reading “Your Surface RT Can Become Useful Again, With Raspberry Pi OS”

Raspberry Pi OS In-Place Upgrades, Not For The Faint Hearted

The Raspberry Pi series of boards are noted for their good software support, with a continuous flow of operating system upgrades such that an original Pi from 2012 will still boot the latest Pi OS. But these upgrades are best done by writing a fresh SD card, so oddly, the Pi remains surprisingly difficult in many cases to upgrade in place. [Iustin Pop] has taken a look at the problem, and finds that though it’s not always easy it remains possible with a bit or work.

An upgrade in place of a Raspberry Pi OS install that’s running on a headless device is probably the simplest of the lot, with a relatively small set of issues. Do it on a machine using the GUI though, and the switch from x.org to Wayland makes for a whole world of pain.

Perhaps most interesting for the insight it gives us into the way Raspberry Pi OS is derived from Debian, is the crossgrade process from the ARMhf build for earlier machines to the ARM64 one for the more recent ones. Here aside from a headache of differing paths and versions, he encounters the Pi-specific compilation tweaks put in place by the developers of Raspberry Pi OS, leading to the ARMhf version being a different branch from the original Debian than the ARM64 one.

Having read his examination of in-place upgrades we have to say that simply writing a new SD card remains the most attractive option. But sometimes along comes a remote system where that’s simply not possible, and this guide might just be very useful sometime.

Debian Bookworm Comes To The Raspberry Pi, And Wayland Is Now Default

It must have been a busy week for the PR department at Raspberry Pi, with the launch of their latest single-board computer, the Pi 5. Alongside the new board comes something else, an updated Raspberry Pi OS version.

This is built from Debian 12 “Bookworm”, and supplants the previous “Bullseye” version. As well as the new OS base it comes with a pile of Pi-specific upgrades including an optimsied version of Mozilla Firefox. Probably most important is that henceforth (at least on 64-bit boards) its desktop will use the Wayland compositor rather than X11 to draw and manipulate windows. This is a development that has been in the works for a very long time — it must be almost a decade since the first Raspberry Pi blog entry about Wayland — so it’s welcome at last to see it.

The new tweaks as well as Wayland are supposed to deliver a much faster Pi experience, so we thought we’d break out the stopwatch and do some rough real-world tests. The bench 8GB Pi 4 here has a vanilla 64-bit Bullseye installed, so off we went to measure boot time, Chromium browser opening time, and Hackaday load time. It was time to download the new 64-bit Bookworm image and do the same. Have we just downloaded a power-up?

Both tests were done with an everyday boot, after the first-time OS set-up, and with all browser caches emptied. First up was a significant boost, with Bookworm booting in 37.14 seconds to Bullseye’s 53.5, but the Chromium opening was a little more disappointing. On Bullseye it took 7.15s, while Bookworm’s Chromium managed a more pedestrian 9.13s. The new Firefox takes only 7.95s to open. Both Chromium browsers load Hackaday in about 1.8s, while the new Firefox did the same job in a shade over 3s.

So allowing for our stopwatch reaction time and the ad-hoc nature of the test, this is a faster-booting OS, but the underlying hardware is still the limiting factor. We’re disappointed to see that there’s no update for the x86 version of the Raspberry Pi Desktop, and we hope they’ll be able to rectify this in the future.

A 64-Bit Raspberry Pi OS At Last

Long-term Raspberry Pi watchers will have seen a lot of OS upgrades in their time, from the first Debian Squeeze previews through the Raspbian years to the current Raspberry Pi OS. Their latest OS version is something different though, and could be one of the most important releases in the platform’s history so far, as finally there’s an official release of a 64-bit Raspberry Pi OS.

Would-be 64-bit Pi users have of course had the chance to run 64-bit GNU/Linux operating system builds from other distributions for nearly as long as there have been Pi models with 64-bit processors, but until now the official distribution has only been available as a 32-bit build. In their blog post they outline their reasons for this move in terms of compatibility and performance, and indeed we look forward to giving it a try.

Aside from being a more appropriate OS for a 64-bit Pi, this marks an interesting moment for the folks from Cambridge in that it is the first distribution that won’t run on all Pi models. Instead it requires a Pi 3 or better, which is to say the Pi 3, Zero 2 W, Pi 4, Pi 400, and the more powerful Compute Modules. All models with earlier processors including the original Pi, Pi Zero, and we think the dual-core Pi 2 require a 32-bit version, and while the Pi Zero, B+ and A+ featuring the original CPU are still in production this marks an inevitable move to 64-bit in a similar fashion to that experienced by the PC industry a decade or more ago.

As far as we know the Zero is still flying off the shelves, but this move towards an OS that will leave it behind is the expected signal that eventually there will be a Pi line-up without the original chip being present. We’re sure the 32-bit Pi will be supported for years to come, but it should be clear that the Pi’s future lies firmly in the 64-bit arena. They’ve retained their position as the board to watch oddly not by always making the most impressive hardware but by having the most well-supported operating system, and this will help them retain that advantage by ensuring that OS stays relevant.

On the subject of the future course of the Pi ship, our analysis that the Compute Module 4 is their most exciting piece of hardware still stands.

Raspberry Pi 4 Gets Its 8 Gigs

What began as a rumor becomes reality. This morning [Eben Upton] announced that the newest flavor of the Raspberry Pi 4 comes with 8 gigabytes of RAM and a sticker price of $75, roughly twice that of the base model which is now pegged at 2 GB of ram.

Originally released on June 23rd of last year, the Pi 4 came with three different options for 1, 2, or 4 GB of memory. But just a few days later, Hackaday reported on an Easter egg in the user guide that referenced an 8 GB option.

So why didn’t this version get released in 2019? That’s the crazy thing about this story. In the announcement [Eben] mentions that the Pi’s design is capable of addressing up to 16 GB of LPDDR4 SDRAM (we say bring it, but that’s a discussion for a different day). It took a year to get here because there wasn’t a source available for this 8 gig version until Micron began manufacturing the chip earlier this year.

Also addressed in this announcement is a looming changeover that was bound to happen eventually: the move from 32-bit to 64-bit operating systems on the Pi. While a 32-bit image can access all of this larger memory across multiple process, it can’t devote more than 3 GB to a single Linux process because of address space limitations. Simply put, you need more bits to access the higher addresses. Moving to a 64-bit system accomplishes that, something you can do by running unofficial builds on the Pi, but the official build didn’t support it until today’s announcement of a 64-bit beta image.

This is inevitable, not purely because of this memory limitation, but because we’ve seen examples where the juggernaut of Linux development has its own eye on a 64-bit future. Official images for Raspberry Pi have always been 32-bits, and remain so for now, but the wind is beginning to blow for this and future hardware offerings that are bumping up against limitations. Along with the news of this impending architecture switch over, the official operating system has also gotten a name change: Raspbian will henceforth be known as Raspberry Pi OS.

When [Jenny List] first reported on the 8 GB rumors last June, she speculated that today’s announcement would happen on February 29th of this year. Why the leap day? It happened to be the 8th birthday of Raspberry Pi and synced up nicely with an 8 GB surprise. Today’s announcement drops the morsel of trivia that the foundation was indeed planning on that date, but missed it by three months due to supply chain disruption associated with the coronavirus pandemic that prevented them from sourcing all the parts necessary for the new power supply design included in this revision.

We’d love to hear your thoughts on this move. Do you need 8 GB on your Pi, and does the 3 GB limitation of a 32-bit kernel matter to you? Let us know in the comments below.