I think I'm done with raspberry pi

I’ve had a raspberry pi 4 for a few years, doing backup for the machines on my lan. It started out as Debian 10, and I was able to do an in-place upgrade to Debian 11.

Last year I tried to boot up Debian 12, and it failed. Back to Buster. I’ve been seeing impending signs of the end for Buster, and today I tried to boot up Debian 13, and again the pi 4 acted like a doorstop.

It’s been reliable, as far as it goes, but it’s always been uncooperative about running anything else.

So I ordered a $100 mini PC with intel hardware to take it’s place. Life is too short to spend fighting with hardware to try and make it do what you need.

BTW I’ve got a box full of Raspberry Pi machines if anyone is interested.

5 Likes

Agreed. Pure and simple. One of these days, if I have the time, maybe I play around with one. I probably need memory prices to come down a tad first.

2 Likes

I’ve had a raspberry pi from each generation. They helped me learn and hone the skills that I have today and I’ve loved having them on the network. I currently run two Raspberry Pi 5 8GB models as active participants on my network (PiHole/Icinga2/Nagios/other monitoring services and my bastion/jumpbox) and they run great.

I did have a Pi 4 acting as my PiHole/Icinga2/Nagios box for at least a year, maybe more. The only reason I’m not running it now is b/c I got the 2nd Pi 5 as a gift, so figured why not take the boost to hardware specs. The only Pi 4 I have running currently is used for a camera setup to keep an eye on my older cat when we take vacations and it’s currently running Raspbian Lite as well, which I believe is on Debian 12 right now (though I did install this one, it did not get an upgrade in place).

I can’t say I’ve had any update/upgrade problems with any Pi, but I do primarily run the Raspbian Lite OS. I’ve not tried to run any other OSes on them, so I can’t speak to them in that regard. I’m always open to new projects on them, if you really don’t have a use for them, I can find a home for them pretty easily here!

3 Likes

How far do you live from me? I need to check out shipping rates.

2 Likes

The main issue I’ve had with RPi boards isn’t with the boards themselves as @J_J_Sloan also indicated (OS issues). But in my case it’s repeatedly the SD and now microSD cards. :confounded_face:

I really wish they would abandon that route and launch with eMMC on board (like the Compute Module boards) with a short m.2 nvme slot replacing microSD.

RPi boards feel a bit stagnant and deaf to feedback these days. We can’t dismiss the massive impact they’ve had on education, hobbyists, and low-cost computing worldwide, but that doesn’t mean they should stop evolving where real-world reliability is concerned.

Also see this article, inspired by this topic: Raspberry Pi Reliability Has a Storage Problem
3 Likes

Mi impression for first version of RPi B and RPi 2 B+ was good.
Once I became familiar with the hardware and the philosophy of handling data trees and control through overlays, I detected two problems: the fragility of the SD card in the face of power failures, and the slow speed of this device type.

As a result, I focused the applications on running in memory, I arranged an alternative buffer power supply system with a signal for a controlled shutdown of all systems, and sufficient power autonomy time for it to be completed.
Simultaneously, I installed an adapter for each of the SDIO bus systems where the SD card and eMMC memory were connected. Initially, I started using a secondary, high-quality storage via SPI.

However, SPI was slow and power-intensive; the four signals—MISO (Master In Slave Out, sends data), MOSI (Master Out Slave In, receives data), SCK (Serial Clock receiver to tx sync), and CS (Chip Select from SPI Bus)—did not provide the necessary data transfer speed.

I had to deal not only with the adaptation to 3.3V, but also with the 1.8V adaptation, which allowed me, after modifying the kernel, the boot overlays, and other elements, to use the other four SDIO lines that allowed it to work faster and at a much higher speed, with UHS units instead of DS/HS, through said SDIO communication interface.

You can configure SDIO Clock(25Mhz-208Mhz) to media at GPIOs 22(CLK),23(CMD),24(DAT0),25(DAT1),26(DAT2),27(DAT3), on SD host/eMMC or pinout. Token commands are 48 bit on SPI mode, one bit(DS/HS,3.3V) or four bits(UHS, 1,8V) data lines.

The result was acceptable, for the stack of RPi units, their connections to physical and logical applications, but as @J_J_Sloan points out, it’s pretty, and going through that effort again when they switched to a superior architecture, with a different ABI, wasn’t convenient to continue, and I didn’t use the new RPi versions, except for the RPi Zero, which carries the BCM from my development version.

RPi’s went through those systems: RTOS, Alpine, Debian, BSD derivatives, and many others, even some university practice OSs (ZeOS) for computer science students.

Now they’re just a memory, stored away, that should still work. It was great learning so much, dedicating countless hours to that hobby. They sit next to the Stellaris Launchpad LM4F120, Beagle Bone Black, Beagle Bone, Arduino Uno, Arduino Mega, Atmel ATTYNY44A and 817-XMINI, Onion Omega, Onion Omega2, Nvidia Jetson TX2, Jetson Nano, and other development systems and devices I’m currently testing.

But everything has its time and place. I appreciate what it have given me, and I continue to move forward, because otherwise I would still be writing code in FORTRAN and COBOL on the DIGITAL PDP-11, or on the VAX8200, and then in BASIC with my Sinclair ZX81, and then Spectrum, or MSX, before the 8086 architecture with MS-DOS arrived at my country, Catalonia.

As they say, it was nice while it lasted, but that’s water under the bridge now. These were learning experiences for every situation. Time was passed XD

6 Likes

I’m over in Durham, North Carolina!

1 Like

Absolutely agree with you, the most repetitive problems I’ve had have always been with the SD cards, micro or not. I’ve had better luck with the recent Samsung SD cards I’ve bought, but it’s still a weak point and I’d love to see them move into something more stable.

3 Likes

The best reliability I’ve had is with these industrial microSD cards by Kingston.

But really, avoiding microSD and using USB storage is better. Or, get a mini PC for ~ $150:

4 Likes

I enjoy reading about the Raspberry Pi, but I have avoided them. The incompatibility with x86-64 is a dealbreaker for me. There is too much software I use that is either unavailable or would require manual compilation on Pi.

I am not served by a high priced kilowatt-hour utility, and I would rather have things more consistent.

2 Likes

This biggest fix for me is running

sudo fstrim / -v

Every update, I’ve been using the same sdcard for years

4 Likes

Thanks for that feedback. Welcome to the forums.

1 Like

What’s the big deal? Just use an NVME drive on the new official HAT that fits inside the case.

The Radxa Dragon Q6A also looks like a good alternative if you don’t need Raspberry Pi’s level of support.

2 Likes

I guess that HAT advice really only applies to the Pi 5. I appreciate the concern with all the other Pis.

2 Likes

They’re not cheap (on the face of it) and not always appropriate, but there are also the recently launched official Pi USB sticks (for Pi3, Pi4 and Pi5). I was amazed at how fast they are according to the comparisons made by leepspvideo.

It seems they use technology that keeps them secure from data loss too, including through power loss.

2 Likes