Jump to content

James Kingdon

  • Posts

  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Does anyone have the pin mappings for the gpio header on the One Plus? At the moment I'm a bit stumped both on what might be connected to each pin, and how to control them. I guess the sensible thing is to just wait for the dust to settle...
  2. ... and here are the openssl/7z tests: https://pastebin.com/huSB5LhC @tkaiser updated results with the performance governor: https://pastebin.com/pUR5D7AA You were right, it makes a big difference to the openssl results at the smaller block sizes. The board has passive heatsinks only at the moment, fan is still to be added. I saw some temperatures in the high 60s during these runs, so it's possible/likely that some throttling still occurred.
  3. @tkaiser Memory test you requested on OPi one+ board: https://pastebin.com/ubszDSUH Temperature peaked at 53C during the test, so should have stayed well clear of any throttling. I added heatsinks this morning
  4. My OPi one+ arrived. I burned the ubuntu image with etcher and it worked fine. I had to manually resize the fs but you expect a few rough edges with a new board. The bare board runs on the hot side, idling at a reported (but unconfirmed) 48C. Benchmarks quickly push it into throttling at 70C, but even so it is faster (just) than any of my other 4 core boards. I'll add a heatsink and fan and see if I can get the temps under control. If so, and if the board remains reliable it seems like excellent value for money. The H6 looks very promising.
  5. My recommendation would be to stay clear of raid configurations. With modern disk sizes the rebuild times are so long that the probability of a second disk failing during the rebuild becomes significant, and when that happens you're looking at a world of hurt. Sure, use raid 0 if you need the performance and can tolerate the doubled failure rate, but I'd recommend using a straightforward rsync cron job to do backups to a completely different drive (as in different manufacturer/size or at the very least batch) rather than rely on any form of raid for reliability. Same applies to overly complicated LVM setups - in principle you can keep everything organized with LVM stripes and replicas, but in practice it's way too easy to loose track of things and have multiple dependencies that you weren't aware of. Having just suffered a 2 disk failure on a complex LVM setup, I don't intend to go there again. Label all your disks with their install date and replace them at intervals that match your risk tolerance.
  6. Ah, I thought that noise was a bit worrying, but not having used these particular disks in any other system I pushed it to the back of my mind. Thanks for raising awareness.
  7. Just a note of warning for anyone finding this thread later; 5.7V is very high for the supply voltage, be cautious about going that high. I run all my boards at between 5.20 to 5.25V, including an M3. Usually when people report needing higher voltages for stable running it's because they are using long power cables of small guage which drop significant voltage across their length, but I see that's not the case here. Friendly Arm released a replacement for the M3 called the Fire3. It's smaller and uses a micro hdmi connector, but otherwise is very similar to the previous board (1G ram, no emmc). There's also a new version of the T3 which uses the same excellent SOC but has 2G ram and 16G emmc, but costs twice as much.
  8. I see Orange have released a H6 board. Android only for the moment, but might be interesting once Linux is available. https://www.aliexpress.com/store/product/Orange-Pi-One-Plus-H6-1GB-Quad-core-64bit-development-board-Support-android7-0-mini-PC/1553371_32848891030.html Not a board to cause huge amounts of excitement (limited IO, only 1G ram) but it's a low cost way of testing out the H6. Edit: Ah, thanks tkaiser. I obviously haven't been keeping up recently.
  9. It's slightly frustrating the extent to which they cut features from the XU4 when they created the HC-1 board. I would have preferred a slightly larger board which retained the hdmi/emmc/gpio and of course the fan output. If that added $10 to the price I'd be ok with that, and I doubt if it would have been any more than that.
  10. I applied the firmware upgrade. I haven't had time to test the spin down properly, but I noticed that -C still wakes the drive up from sleep.
  11. Sure is taking a long time for this board to appear. Hope they haven't dropped it.
  12. Ok, so that's bad news and good news. Bad news about the aggressive spin down, and good news that JMicron is at least listening to you and working on it. It's a shame I didn't read your message before ordering two HC1s today, but then it sounds like my other choice (rock64 plus it's sata adapter) has the same problem. Let's hope that JMicron come through with that fix!
  13. Thanks for the pointers @tkaiser Do you happen to know if the same problem affects the Odroid HC1 when connecting via its sata port (I assume that uses a USB3 converter on the pcb)?
  14. After a major failure of my file server I bought a pair of seagate desktop USB3 drives to use for temporary storage while I sort out the mess. I plugged them into an XU4 and started transferring several 100GBs of data only to have it lock up solid. dmesg indicates a number of uas restarts, the last of which doesn't complete. I had the same thing on another SBC (one of the orange PIs I think, although I can't remember which model) and I also found references to the same problem on x86 boxes, so I think the problem is fairly generic. Apparently it can be worked around by adding a conf file to to /etc/modprobe.d, but I haven't got that to work yet (time has been in short supply). Hanging the drives off SBCs running an older kernel or connecting to the USB2 port on the xu4 gets things running smoothly (if slowly).
  15. Kudos to @tkaiser for providing so much quality info here.
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines