Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
zbitx Memory
I run wsjtx all the time, flawlessly. Run top to see memory and cpu consumption. On Fri, Apr 4, 2025, 7:50 AM Ken N2VIP via <ken=[email protected]> wrote:
|
Building applications is always going to be slow on the Zero 2 W. If you have another more capable Raspberry Pi, including the Raspberry Pi 4 in the sBitx, you'll be better off building them there and moving the applications over. On Thu, Apr 3, 2025 at 10:25?PM Leo Aniol, AI5II via <leomaniolone=[email protected]> wrote:
|
My development system is a zbitx with Raspberry Pi zero 2. It takes a couple of seconds to build zbitx? - f On Fri, Apr 4, 2025 at 8:43?AM Ryan Wesolowski via <cosmo1stgen=[email protected]> wrote:
|
On Apr 4, 2025, at 04:53, Ken N2VIP <ken@...> wrote: Swapping to microSD seems like a bad idea (even though rpios does it by default): those can be both slow and unreliable, depending which one you buy. So now we know there are at least two reasons the zbitx might be doing significant writing when you pull the power plug: it could be swapping, or it could be writing FT8 decodes or your QSO log to sqlite. At least it’s not critical when writing swap is incomplete: unless you are using swap for hibernation (not something that most Linux users are doing), the contents don’t matter the next time you boot, they will be overwritten with whatever needs to be swapped out next time. On ordinary computers, I try to have enough memory so that I don’t need swap at all, ever since I started using SSDs. It means that I sometimes get out-of-memory failures, if there just isn’t enough RAM to hold everything. Using swap could cause the SSD to wear out sooner. Yeah I know, most people don’t worry about it, and rpios has swap set up by default, like most distros do. Most people replace computers before the SSD wears out. Pulling the power would be safer if it was running from RAM, and the root FS was mounted read-only. OpenWRT works this way, for example: your router needs to be reliable, and it’s quite normal to reboot it by pulling power rather than having to ssh to it and ask it to reboot. So it only reads files from flash, and does not write anything at all in everyday use. If you install extra packages, they get written to a separate overlay filesystem on the same flash, to avoid writing anything to the root FS. But working this way precludes writing periodic log files to the same storage! OpenWRT does not persist any logs, and does not need to. But usually there is a USB port, in case you want to add more storage and use that for something. For sbitx/zbitx, one could at least use a separate partition for sqlite and other saved files: that would not reduce the wear on the SD card, but at least if it gets corrupted, the radio would still boot. Or, go further and use a separate drive for that (USB stick probably). Or, redesign the sbitx to use the CM4, and install at least 2 forms of storage: probably eMMC for the root FS and an SD card for auxiliary storage. But this would complicate the board design quite a bit, and add cost. All the software that you want to run would have to be small enough to fit in RAM, if you want to avoid swapping. The sbitx process is pretty light, but unfortunately some of the other programs are more bloated. |
to navigate to use esc to dismiss