Raspberry Pi 5 vs. Orange Pi 5 Plus vs. Rock 5 Model B
picockpit.com
picockpit.com
These ~1L sized computers idle in the 7-13W range. Even with EU electricity prices, it would take you a very, very long time to make up the difference from a 5W SBC.
You also get standard x86 support, normal expand-ability, M.2 slots, PCIe ports, etc. You lose GPIO support.
For $100-$120 on eBay, a search for 'dell optiplex 3070' typically results in getting either a i3-9100 or i5-9500, 8-16GB memory, and 120-256GB NVMe. I bought one a couple months ago for Blue Iris and it uses 8W at idle. Here's an example of a USFF (ultra small form factor) for $110 - https://www.ebay.com/itm/325826958401
Lenovo variant (M720q tiny) for $121 w/ i5-8400T, 16GB, and 256GB SSD (probably NVMe) - https://www.ebay.com/itm/266450621632
I had some Acer chromeboxes that would do 4.5w easy without any tuning or setup, and they used pretty low end dyal-core i3's from just barely before the i5-9500t. Generally I don't think servethehome finds many tiny mini-pcs below 7w.
When it has to roar however, the draw is substantial compared to my ODroid, but since it idles the majority of the time, I'll take it.
An orange pi 5 uses 7.5W under full load, 3.3W idle in comparison.
Average consumption matters, not peak. And you can pin CPU to not go on higher frequencies if you don't want to go into inefficient max frequency/max voltage region.
You will also be recycling already produced device.
Recycling is good, but only to a point. At some point the cost of operation (and resource pressure from its use) will exceed the cost of a more efficient device - at least until we get abundant green power...
Hard to say without real workloads, but if there are any plans of routinely pegging the CPU, most power efficient strategy is to buy a modern chip.
I do agree that modern CPUs are required for high-load situations.
What you probably want to compare for most home uses is power at some low idle vs performance at that CPU throttle level. The difference is probably a Watt or two max, which never would justify a brand new SBC over repurposing something headed to ewaste for environmental reasons.
A complete computer is at least somewhat hardened against ESD and what not, has onboard storage of some description, and isn't severely throttled from a power standpoint.
I like RPis and similar for rapid prototyping if I know I need GPIO control, but if you don't, there are better machines out there, at similar price points.
[0] https://pine64.com/product/pineseed-bl602-wifi-ble5-soc/
I have a couple of the Pine64 boards that run Linux. Unless something changed, it doesn't have WiFi or BLE support, and likely never will.
> The bl602 doesn't seem to have rust support yet, but I'm looking forward to more options.
I think it does: https://github.com/bouffalolab/bl-pac/tree/main/bl808
Sorry I was thinking of the 0x64, although it's entirely possible to get some form of Linux running.
It tends to be like this with Chinese chips, and often times western ones too, unfortunately.
I wish someone made a rack to hold them vertically. I'd own 10 if I could mount them in a rack like this: https://images.prismic.io/macstadium/949d85ad-18be-4059-acf6...
Gets me integrated: battery, screen, keyboard, mouse
I can buy an old laptop for $100 and would cost me $150 for similar RPI hardware.
Hm...
> No adapter is included. Needs 65W or above (most dell/hp laptops around the year it came out are compatible)
The 65W power adapter on Dell retails for $46.99 on sale, bringing the grand total to $156.99.
And that's just after skimming your link for 2 minutes.
The great thing about these Optiplexes is that they use a standard 20v 4.5x3mm DC jack for power. I run mine off a UPS with a usb-c to barrel jack cable.
Furthermore, I have several of these systems and tried sourcing 3rd party power adapters online. For this aspect, not one of them worked correctly.
I did a write up here: https://old.reddit.com/r/homelab/comments/11o0x5o/dell_3050_...
https://hclxing.wordpress.com/2014/02/09/hacking-a-dell-powe...
046 is the output current 4.6A instead of his partitioned as 46(there are power supplies output more than 10 amps).
The 22 bytes is the Dell PPID, which should be also present on the charger's label or the box: CN: Manufactured in China, some of them are TH which means made in Thailand. 09T215: Dell Part Number. 71615: Manufacturing factory code. 438: 2004 or 2014, March, 8th (Dell use YMD 3 bytes thus it is a lossy conversion always). 35EAL: This should be the serial number.
The last part 03 is a CRC16 (x16 + x15 + x2 + 1) checksum.
Edit:
I ran the `cpufreq-info` command in your write-up and it gave me the correct:
> hardware limits: 800 MHz - 3.00 GHz
Maybe it's because the usb-c to barrel jack cable I picked up was marketed for dell laptops?
Last I checked, a Pi also does not come with a charger, case, or storage.
Ebay Australia has a Lenovo M700 i5 with 8GB RAM, 256 GB SSD for AU$135.00 (US$86) including power supply and cords.
And for GPIO (if really needed) you can always add something like an USB Arduino micro (clone) for a couple of bucks.
Every time I look at the wall wart plug pack it comes with I laugh to myself. 8W. In terms of price, speed and compatibility the Raspberry Pi looks laughable.
If I want GPIO I just use ESP32s with wifi. I am then unconstrained in terms of other stuff hanging off them. Using the new nano ESP32 boards I can just hot glue them to whatever I want to talk to.
Just for kicks, some reference:
Assuming the Gflops numbers are roughly comparable, ~50 Gflops would have you competing for the #1 spot in the first TOP500 list, June 1993:
https://www.top500.org/lists/top500/1993/06
Which came equipped with 1,024 SuperSPARCs @ 32 MHz:
https://www.top500.org/system/166997
Even ~2000, that might still have squeezed you into the bottom of the list? Note that power consumption of above system will have been in the 10s if not 100s of kW. To say nothing of size or purchase price.
That's only 1 human generation ago. What on Earth are you doing with these things? Running physics simulations of nuclear explosions, or what?
Can anyone recommend one?
I love the silence, and run proxmox with enough memory and storage.
Let's acknowledge that there are good reasons for avoiding x86 for those who care. The security problems for one, and the long shadow of Microsoft over the ecosystem. Perhaps an additional concern about the supply chain. The closer we can get to an open-source system without blobs, the better.
But the above concerns apart, it seems clear that R.Pi 4 and 400 were peak R.Pi. The performance and low-cost of Intel's recent x86 NUC mainboards is impressive. AMD is also offering strong value in the SFF market.
As I long-time R.Pi/Odroid user, I continue to enjoy these devices. But their lunch has been eaten by competitors.
I have an HP SFF machine with a 10th gen i3 as my Emby/Plex box and it can transcode 4k streams without breaking a sweat.
The more modern cpu models are a little rare still, but they show up from time to time.
If you want to run a server-task, listen to the common chorus and buy an 3-7 year old SFF business PC. Slap Proxmox on it, and you can virtualize a bunch of small 'servers' as LXCs with plenty of CPU and memory. Easy to add storage, dependable, and well-supported. Power draw is highly overstated for typical ancillary-server tasks, and if you were planning on 2+ Pis, you're now in the same ballpark.
If you want to hack together something with sensors/electronics, use a $5 ESP32, which likely has way more power than you need. If you need more processing power, move that from the edge device to something like the cheap SFF above. Plenty of sample ESP32/8266 Arduino libraries to expose/control the GPIO via a simple API, MQTT, or UDP/TCP payloads. Then, you can write your processing logic in whatever language you want, on a powerful server, and the edge device doesn't need Linux distro updates to blink some LED strips or whatever.
https://www.ebay.co.uk/itm/256245170577
This listing is UK £75, but I got one for a similar price from the EU.
To say it was trouble would be an understatement. Even after I successfully completed the setup (which took forever, as the documentation was contradicting, confusing, and felt like it was worse than machine-translated to english). Stability wasn’t there either at all. Occasionally it would just lock up and freeze, requiring a hard reboot. It would heat up pretty bad sometimes, despite an extra heat dissipator/cooler (that i triply made sure was installed properly). Webcam would randomly just refuse working (and I had to manually edit linux configs to get it to work in the first place). Sometimes SSH connection would just die and I become unable to connect to it again without either a reboot or restarting networking services on it (which would require me physically being next to it, thus defeating the point of Octoprint being remote). And mind you, I didn’t run it as some heavy production-tier 3d printing controller, I would print something a couple times a week tops, and nothing too complex or too high res (in terms of the model being printed).
All while Raspberry Pi has great documentation, and Octoprint setup on it is pretty much plug and play with just a few clicks of installing dependencies (or even simpler than that, if you install a dedicated Octoprint distro made specifically for Raspberry Pi).
Just upgrading and dealing with downloading/upgrading the Raspberry Pi is a dream compared to the Rock Pis. The Khadas is a little better, but still I have a hard time upgrading it and sometimes certain images just won't even work from the company. Sometimes when trying to upgrade Rock Pis with eMMC you will find 2 or three different ways to install the freaking image on their own wikis.
There's also the "security" aspect for me, I really don't trust some of these distros (maybe I shouldn't worry??). A random image someone put on their website with broken instructions and messed up repos/kernels doesn't exactly instill confidence to me.
I will say the one GREAT thing from Rock Pi is their rock pi x. But it has an x86 processor and I can just install any distro. I wish they were easier to purchase and had more memory!!!
Pine64's QuartzPro64 board uses the same RK3588 in the Orange Pi 5 Plus and Rock 5B, and they're working on upstreaming support for that: https://wiki.pine64.org/wiki/QuartzPro64_Development#Upstrea...
Upstreaming for Pine64 devices is done by the community: https://lore.kernel.org/all/?q=pine64+rk3399+add
QuartzPro64 was recently mainlined by megous. I don't think he's employed or compensated by Pine64, but I'm not sure.
The SoCs are added by Rockchip, Collabora, and others.
If just for playing around paying extra for pi just to have something that works makes a lot of sense.
I've not been able to find any other SBC that is able to do that.
- http://www.orangepi.org (note: https does not work)
Then again, we might not even be seeing the same site, since it forces http:// and could be modified in transit by anyone on the path of either of our ISPs and the web host.
Their software I would not touch, but I never had to. Most Allwinner and Rockchip boards are well supported upstream. I just upstreamed support for Orange Pi 5 Plus a week ago or so.
All you ever need with these random boards is to build your own Linux kernel and bootloader for them, which is a few fairly standard steps, and then you can use any normal aarch64 distro on them, even if the board is not "supported" by the distro.
I just have a script to cross-build the recent kernel for the boards I own, and update it remotely. Not a huge issue.
The OPis themselves were quite decent devices, Raspbian worked very well on them.
Then when you get the device it won't do anything new after a while because the vendor never maintains their distro and the GPU or device tree are is proprietary so nobody else can either. If you're lucky maybe there's an Armbian build which marries new userspace with the older kernel and its unmaintained drivers.
This is why Raspberry Pi still dominates this market.
Ultimately, time is money. If I manufacture something en-masse, obviously a few dollars difference is important. But for my one-off hobby project? I'll stick with what works.
If you want a dependable computer, stay away from pseudo-embedded hardware.
For example: I use a few zero 2 w's with shairport-sync to make Airplay stereos. I use the header pins to control a relay to turn on and off an audio amp. Pi 4+ would actually work a lot better for this especially when playing audio on multiple of these setups at once. A Lenovo mini pc wouldn't be as easy to hide.
Schrodinger's power consumption.
The power considerations are pretty negligible from a cost per year perspective.
I really only use mine for pseudo IOT applications where space is a factor, like for OctPi and a Shairplay receiver.
5V/5A (USB-C) 5V/4A (USB-C) 5V/5A (USB-C)
My biggest frustration with hobbyist boards is how little power the can source to e.g. the USB ports. Its super frustrating to need a powered USB hub to add e.g. a USB indicator light. The fact that you can power the RPi from the powered USB hub seems hacky, but maybe that was always the intent.
After trying three I gave up.
Yet note that a good power source doesn't mean that these SBCs will suddenly draw 15W sustained.
Average draw will be much lower than any of these NUC-like devices.
e.g. my VisionFive 2 is below 4w.
Note that the M600 does not have any active cooling. The entire unit is a big heatsink. The thing will run as a headless network computer with just the power supply (a proper Lenovo SMPS brick) and an ethernet port connected.
power usage spikes with CPU activity (among many other things) and if your power supply can't deliver the current that is required, voltage will drop, and things start failing, but only for 1ms or maybe even less. maybe even a single clock cycle in some cases.
if you can't keep the board powered fully for every clock cycle, then you are going to have problems, and that's true for any computer, not just the Pi.
Since these SBCs keep getting pricier and need active cooling while software is still far from ideal, it's not that big of a jump.
Any non-real-time operating system will eventually get a little bit buggy around timing intensive operations like I2C or (especially) SPI. Better to have your GPIO operations performed by a dedicated micro that only handles your serial traffic and whatever pin-twiddling operations you need to do. Ideally, your serial traffic is in a binary protocol like MODBUS-RTU, so your traffic parser is as fast as possible.
Bitbanging I2C or SPI is tedious but generally pretty achievable in a bare-metal application. But unless you're hacking your kernel to force that kind of timing fidelity, bit banging on an RPi running Debian is just impossible.
You'll have the same issue on any SBC running Linux. You'd need to carefully use realtime process scheduling, if you want more predictable timing on a general purpose OS for such stringent timing requirements.
What I see a lot of is people trying to cram all sorts of shit into a Pi and expecting everything to work properly. I actually wrote a fairly small event-driven kernel for AVR parts a few years ago called XOC "exec-or-communicate" which could do small real-time tasks easily (combinational logic, state machines, interrupt handling) and delegated complicated ones to a host machine over virtual serial port. It was used for a metering system I developed. The AVR side could withstand a complete host failure and reboot.
Found this:
"Ryanteck RTk.GPIO (PC GPIO Interface)" https://uk.pi-supply.com/products/ryanteck-rtk-gpio-pc-gpio-...
gpiozero > Remote GPIO: https://gpiozero.readthedocs.io/en/stable/remote_gpio.html :
> GPIO Zero supports a number of different pin implementations (low-level pin libraries which deal with the GPIO pins directly). By default, the RPi.GPIO library is used (assuming it is installed on your system), but you can optionally specify one to use. For more information, see the API - Pins documentation page.
> One of the pin libraries supported, pigpio, provides the ability to control GPIO pins remotely over the network, which means you can use GPIO Zero to control devices connected to a Raspberry Pi on the network. You can do this from another Raspberry Pi, or even from a PC.
Presumably, e.g. TLS to secure that control channel is your responsibility.
Parallel ports > Pinouts: https://en.wikipedia.org/wiki/Parallel_port#Pinouts
"The parallel port" (2023) https://news.ycombinator.com/item?id=34585216
Serial port: https://en.wikipedia.org/wiki/Serial_port
UART: Universal asynchronous receiver-transmitter:
Serial TTL: https://en.wikipedia.org/wiki/Transistor%E2%80%93transistor_... :
> TTL serial refers to single-ended serial communication using raw transistor voltage levels: "low" for 0 and "high" for 1. [31] UART over TTL serial is a common debug interface for embedded devices.
"Possible to use a 9 Pin Serial port as "GPIO" using ioctl()?" https://stackoverflow.com/questions/27789099/possible-to-use...
D-subminiature > Typical applications > Communications ports: https://en.wikipedia.org/wiki/D-subminiature#Communications_...
Crosstalk: https://en.wikipedia.org/wiki/Crosstalk
"Can you hotwire this computer to transmit a tone through the radio?" https://www.getyarn.io/yarn-clip/aac07d77-c6d6-4da7-bdd3-b93... https://en.wikipedia.org/wiki/Air-gap_malware
Proper real time on the metal. Interrupts. Native i2c, i2s, spi, serial with a cross-plane so you can re-route most pins around, depending on the board and a few minor caveats.
the official power supplies (and others with the same ratings) are only sufficient if you don't plug anything into the USB port, don't have any hardware drawing power from the GPIO, and don't utilize Bluetooth and wifi 100% of the time at full throughput or anything.
boot to a fast thumb drive, power the board via a 30W or more power supply, and get an onboard battery so in the rare event that the onboard power regulation can't keep up, a battery powered supply can deliver power through the GPIO pins.
Raspberry Pis are built down to a price point, not up to a quality level. they are extremely good per unit of money spent on them, but they are not perfect.
calling them "shit" shows a general lack of understanding, to me.
And you basically outlined it: they are bad quality and we have all these power problems and here's the insane list of workarounds.
Incidentally I ran mine of an Agilent E3614A which was worth 30x the price of the Pi.
The Raspberry Pi is not an embedded platform in the ways that you are using for comparison. The Raspberry Pi is an educational platform.
It's just a (respectable( power supply. I'm assuming OP just wanted to say that power quality was not the issue.
prior Pis didn't log when they had power issues, and current ones do, if they are able to.
on a Pi 2 A (I think) I had to hook up an oscilloscope to catch all the tiny power problems I was having, and only then realized what was happening. I was 100% sure I was delivering enough power. I was not. those symptoms were only visible without the scope as weird errors in the OS and running applications, and corrupted SD cards.
1: https://www.raspberrypi.com/documentation/computers/configur...
For example, the mini PC doesn't run on PoE. It won't fit in enclosure and can't put it on pole outside. But that is what I'm planning to do with Pi for ADS-B receiver.
The mini PC doesn't have PPS support or ability to install GPS receiver. That is what I need for Stratum 1 time server.
A lot of things I want to do just need USB. The question is if one PC or multiple Pis is better. I like idea of Pi per task since are independent units.
Still, does the new one do better beyond having an off-button? Like does it wake via USB properly? Does it have some way to safely recover the filesystem after power-loss?
Because that has always been the gigantic asterisk on the otherwise-cool RPI. "It's a ticking time-bomb until its memory gets corrupted, and if it crashes you have to roll the dice by power-cycling it" was never a good story. That and its unbearable prima-donna pickyness about voltage.
Whether we should feel bound to go to such lengths is another topic…
I don't regret owning some since they basically taught me to do Linux adminning, but the shopping experience is a bit like buying an airline ticket.
> Does it have some way to safely recover the filesystem after power-loss?
that is not a hardware feature
Raspberry Pi can't redirect blame for filesystem problems if the user is using an OS that's called "Raspberry Pi Operating System".
"Good chance"? We used to do kernel module development directly on Pi3/4s at this one client of mine, and I would OOPS the kernel from time-to-time (couple of times a day on average in the beginning stages) and never had a loss that ext4 couldn't recover from (and as the Pis lacked a "reset" button, resets were done via power-cycling).
We used standard PNY/Samsung Micro-SDs, too (i.e., not industrial-grade varieties), but we did pick the faster-IO variants when possible.
Corrupt filesystems are definitely a lot rarer these days but they still do happen.
I've also had decent sdcards (genuine SanDisk from brick-and-mortar chain store) just completely die on power cycle or reflash.
>Obviously, the Raspberry Pi ecosystem and community is much stronger than the Orange Pi or Rock communities. However, I can basically promise you that the Orange Pi community and Rock community will both grow in coming years.
This seems way more important than the differences in computing power, and even the (massive) differences in price. Until I can seamlessly use raspberry pi OS and all the RPi software, those other boards are just non-starters for me.
It looks like I might be a step closer with the RPI5's pcie expansion options.
I should try testing under some load however.
it's the same with sriracha, you can pretty easily find it for msrp now, but lots of people still think it is hard to find because the last thing they heard on the topic was a news article about bottles selling on the gray market for $40-$80 back in may.
Otoh, Odroid H3 is a quite capable x86 machine and these days parts are so cheap, I bought a quad core Odroid with 32GB mem and 1TB nvme for around $300 and figured I'd retire my cloud server that costs $50+/mo (pitiful 4GB memory) for a much better spec.