Earlier quoted context omitted.
Nearly all SD cards that I've used in Pis and other SBCs have died unpredictably in the past, so I've pretty much given up on using them
This seemed to be such a frequent problem that I have up on ARM SBCs (despite how cool they are). Bought a cheap NUC with a disk and a BIOS and it is working like a champ - boots every time. I probably paid a little more but it's enough for my needs - a simple login and (occasional) DLNA server.
BeagleV – An affordable RISC-V computer designed to run Linux
281–290 of 311 posts
Re: BeagleV – An affordable RISC-V computer designed to run Linux
#282Earlier quoted context omitted.
On the systems I can control, I do all work "disk-less". I strongly prefer it. I like to keep programs and data segregated. The basic setup on NetBSD is as follows, with endless variations possible therefrom. The kernel(s) and userland(s), along with bootloader(s), are on external media, like an SD card or USB stick, marked read-only. There's a RAM-disk in the kernel with a multi-call binary-based userland (custom-ma…
This is interesting setup. Do you know a good guide for such setup?
Chromebooks are claimed to be 100% safe from certain types of attacks. The developers came up with this silly "whitewash" gimmick. Their motivation for a disk-less-like system is to force users to store personal data in the cloud. Ugh. Well, the disk-less systems I have been creating for recreational use long before Chromebooks existed are just as safe. Probably safer because I do not use a graphics layer or a web browser with Javascript interpeter.
Re: BeagleV – An affordable RISC-V computer designed to run Linux
#283Re: BeagleV – An affordable RISC-V computer designed to run Linux
#284Earlier quoted context omitted.
Why would you want use these as build machines? It seems more efficient to just cross-compile on your fastest build machines. You get much faster CI feedback that way. Obviously you want to validate RISC-V code on native devices but using them as builders seems wasteful. I'm genuinely curious why that's desirable. Maybe I just misunderstand your comment and you want the RISC-V boards for validation i.e. make sure you…
I'm sure the Fedora builds aren't designed for cross compilation (which is far from trivial for most packages not designed for it). Also, man-power is the most precious resource so it would be a waste to spend time trying to cross-compile what could be built natively.
Re: BeagleV – An affordable RISC-V computer designed to run Linux
#285Earlier quoted context omitted.
This seemed to be such a frequent problem that I have up on ARM SBCs (despite how cool they are). Bought a cheap NUC with a disk and a BIOS and it is working like a champ - boots every time. I probably paid a little more but it's enough for my needs - a simple login and (occasional) DLNA server.
NUCs costs much more than Pi, even used.
Also, when comparing costs you should take into account things like enclosure, power supply, as card(s) etc.
I'd say I probably paid around $250 or so for the NUC and a SODIMM and I had a SATA boot disk already. I had previously owned ODROID, libre computer (le potato), and Pi(s). These were probably in the ballpark of $80-$120 each, when including all the necessary equipment.
Re: BeagleV – An affordable RISC-V computer designed to run Linux
#286Re: BeagleV – An affordable RISC-V computer designed to run Linux
#287Earlier quoted context omitted.
Honestly I just wish there was a faster standard than SD. 100MB/s for solid state is just incredibly slow now-a-days. There's no reason you couldn't kick SD transfer speeds up towards SSD speeds other than the protocol doesn't allow for it.
I wish folks would stop conflating boot media and root media. There's no reason your SD card has to consist of anything more than u-boot. SD is fantastically simple, so that the boot rom can get at a bootloader without much effort (generally the bootrom just looks at a memory offset on the mmc device). Once you start speaking newer faster protocols, this simplicity is lost. You're not likely going to find a bootrom t…
Oh, that's a nice idea! It would be nice if you linked to a guide or wiki page so that more people can replicate your setup.
Re: BeagleV – An affordable RISC-V computer designed to run Linux
#288Earlier quoted context omitted.
A PI4 compute unit with 8GB of RAM instead of 1GB (faster, DDR4 instead of DDR3 too) and 32GB eMMC and a quad-core 64-bit CPU with much higher IPC while only costing $90 which is around $50 cheaper than a BeagleBoard AI (the same comparison exists for the Black too). You also get direct PCIe access to do what you want. Beagle just doesn't offer anywhere near the same value.
The Black compared with the older RPi3. And everybody was always "The RPi3 is cheaper". The conversations always went like this: "Cheaper? So, did you count the SD card you need for the RPi?" "But it's cheaper." "And the special power supply because the RPi power systems suck?" "But it's cheaper." "And the keyboard and monitor because it doesn't run headless over USB?" "But it's cheaper." "... Okay, boss, it's cheape…
Re: BeagleV – An affordable RISC-V computer designed to run Linux
#289Earlier quoted context omitted.
Existing and shipping at all is the first step. Low price comes later, with volume.
That makes sense and sounds logical, but (and I'm certainly no historian) didn't the Raspberry Pi debut at a low price?
Re: BeagleV – An affordable RISC-V computer designed to run Linux
#290Earlier quoted context omitted.
How about _reliable_ storage needs?
SD in itself isn't technically unreliable. Lots of smartphones do just fine with eMMC, which is same thing as microSD card except in nonstandard IC chip form thus can't carry SD branding.
1. most SD card devices are battery powered
2. SD card failure is acceptable because they are replaceable
3. SD cards are not used as main storage for a computer
That leads to low quality SD cards.