devman

Members
  • Content Count

    53
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Calendar

Everything posted by devman

  1. Numbers look not far from where I am now. R2S says 64c, Cheap IR thermometer on the underside of the PCB gives me 48-50c, thumb says "ouch", and I can't get a reliable reading off the heatsink. Temp here is 30c ambient
  2. Looks it's reacting correctly compared to the settings it's being fed. james@r2s:~$ cat /etc/default/cpufrequtils ENABLE=true MIN_SPEED=600000 MAX_SPEED=1390000 GOVERNOR=ondemand james@r2s:~$ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor ondemand ondemand ondemand ondemand
  3. Idle temps drop by ~10c without the enclosure. No issues with connections between the heatsink and the cpu. No enclosure, thermal pad: _ _ _ ____ ____ ____ | \ | | __ _ _ __ ___ _ __ (_) | _ \|___ \/ ___| | \| |/ _` | '_ \ / _ \| '_ \| | | |_) | __) \___ \ | |\ | (_| | | | | (_) | |_) | | | _ < / __/ ___) | |_| \_|\__,_|_| |_|\___/| .__/|_| |_| \_\_____|____/ |_| Welcome to Armbian Bionic with Linux 5.4.45-rockchip64 System load: 0.00 0.00 0.00 Up time: 33 min Memory usage: 17 % of 472MB IP: 169.254.9.92 192.168.86.36 CPU temp: 61°C Usage of /: 4% of 29G [ General system configuration (beta): armbian-config ] Last login: Sat Jun 13 02:52:34 2020 from 192.168.86.28 james@r2s:~$ sudo -s [sudo] password for james: root@r2s:~# armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 03:13:31: 600MHz 0.00 0% 0% 0% 0% 0% 0% 59.5°C 0/6 03:13:36: 600MHz 0.00 0% 0% 0% 0% 0% 0% 58.6°C 0/6 03:13:41: 600MHz 0.00 0% 0% 0% 0% 0% 0% 58.6°C 0/6 03:13:46: 600MHz 0.00 0% 0% 0% 0% 0% 0% 58.2°C 0/6 03:13:52: 600MHz 0.00 0% 0% 0% 0% 0% 0% 57.7°C 0/6 03:13:57: 600MHz 0.00 0% 0% 0% 0% 0% 0% 58.2°C 0/6 03:14:02: 600MHz 0.00 0% 0% 0% 0% 0% 0% 57.7°C 0/6 No enclosure, copper shim: _ _ _ ____ ____ ____ | \ | | __ _ _ __ ___ _ __ (_) | _ \|___ \/ ___| | \| |/ _` | '_ \ / _ \| '_ \| | | |_) | __) \___ \ | |\ | (_| | | | | (_) | |_) | | | _ < / __/ ___) | |_| \_|\__,_|_| |_|\___/| .__/|_| |_| \_\_____|____/ |_| Welcome to Armbian Bionic with Linux 5.4.45-rockchip64 System load: 0.00 0.00 0.00 Up time: 30 min Memory usage: 17 % of 472MB IP: 169.254.11.84 192.168.86.36 CPU temp: 59°C Usage of /: 4% of 29G [ General system configuration (beta): armbian-config ] Last login: Sat Jun 13 03:13:22 2020 from 192.168.86.28 james@r2s:~$ sudo -s [sudo] password for james: root@r2s:~# armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 03:47:30: 600MHz 0.07 0% 0% 0% 0% 0% 0% 55.5°C 0/6 03:47:35: 600MHz 0.07 0% 0% 0% 0% 0% 0% 54.6°C 0/6 03:47:40: 600MHz 0.06 0% 0% 0% 0% 0% 0% 56.8°C 0/6 03:47:46: 600MHz 0.06 0% 0% 0% 0% 0% 0% 56.4°C 0/6 03:47:51: 600MHz 0.05 0% 0% 0% 0% 0% 0% 56.4°C 0/6 03:47:56: 600MHz 0.05 0% 0% 0% 0% 0% 0% 56.4°C 0/6 03:48:01: 600MHz 0.04 0% 0% 0% 0% 0% 0% 57.3°C 0/6
  4. I'm seeing similar results on my unit, although mine throttled a bit further (816 MHz @15 minutes) if you leave it running. In that little case with token ventilation holes, there's just nowhere for the heat to go. I'll retest tonight without the case.
  5. My mistake. I saw messages about an updated driver but thought it hadn't made it into the releases yet.
  6. Last I checked, wifi on the Zero was disabled by default due to quality issues (I did see some recent patches for it on github, but I don't _think_ armbian has them up) I've had decent luck with the FriendlyArm stuff. If you only need wifi, then take a look at the NanoPi duo 2
  7. I had a similar problem on one of my boxes. Turns out that Speedtest was at fault. From Ookla: You can get a modern version for your platform from https://www.speedtest.net/apps/cli
  8. Thanks, I'll just wait then
  9. Thanks, I made a fresh SD card and no problems for 2 weeks now. Is Stretch / OMV4 still the recommended software, should I be using Buster / OMV5?
  10. Sorry, haven't had a chance to get back to this. My system is running a 3-disk btrfs / raid 5
  11. Oh, definitely reboot. The way I first noticed it was the sound of the fans all spinning up to 100% It's one of the first batch units, so ~2 years now. Current uptime is a few hours since the last failure. http://ix.io/2g1j ● watchdog.service - watchdog daemon Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-04-01 02:17:21 HKT; 10h ago Process: 2232 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ "${watchdog_module}" = "none" ] || /sbin/modp Process: 2234 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec /usr/sbin/watchdog $watchdog_options (code=exited, Main PID: 2236 (watchdog) Tasks: 1 (limit: 4776) Memory: 708.0K CGroup: /system.slice/watchdog.service └─2236 /usr/sbin/watchdog Apr 01 02:17:21 helios4 watchdog[2236]: interface: no interface to check Apr 01 02:17:21 helios4 watchdog[2236]: temperature: no sensors to check Apr 01 02:17:21 helios4 watchdog[2236]: no test binary files Apr 01 02:17:21 helios4 watchdog[2236]: no repair binary files Apr 01 02:17:21 helios4 watchdog[2236]: error retry time-out = 60 seconds Apr 01 02:17:21 helios4 watchdog[2236]: repair attempts = 1 Apr 01 02:17:21 helios4 watchdog[2236]: alive=/dev/watchdog heartbeat=[none] to=root no_act=no force=no Apr 01 02:17:21 helios4 watchdog[2236]: watchdog now set to 60 seconds Apr 01 02:17:21 helios4 watchdog[2236]: hardware watchdog identity: Orion Watchdog Apr 01 02:17:21 helios4 systemd[1]: Started watchdog daemon.
  12. When I write large files (intermittently) the system will spontaneously reboot. I don't know if it's related, but I've also noticed that often, when copying from windows over to the NAS, the throughput will drop fairly quickly to 0, stay there for a minute or so, and then shoot back up I checked the power supply and it's giving me ~12.5v
  13. Probably, depending on your content type and target device. I did some rudimentary testing with transcoding on the NanoPi M3, and it technically worked. I had stability issues though, so I switched to a small/cheap x86 box that supported hardware transcoding.
  14. Mine arrived a few days ago. Still need to scrounge up an appropriate power supply, fan and hub. Thanks for the heads up, @gounthar!
  15. Yep. Sorry if I came out snarky, guidol's right, it's an easy mistake to make. Still impressed you managed swap the ram chip.
  16. Actually, nothing is wrong. You got exactly what you should expect. The K4B4G1646E-BYMA is a 4 gigabit ram module. BTW: impressive that you can resolder a BGA at home. Congrats.
  17. I'd recommend keeping Kobol's option of the little clear window w/mounting holes on the front panel for the OLED status display.
  18. It's a nice idea if you have all the hardware already and have cheap (school/makerspace/etc) access to a laser cutter. I'd be concerned that you're pushing data for 4 HD's through a usb hub to one of the Pi3's ports, which is also an (internal) usb2 hub... which is shared with the ethernet. The Pi3B+ ethernet can do ~300 mbps if you're not using the USB for anything else. Half that bandwidth will be used pulling data from the disks, so you'll be lucky to get ~150mbps. If you're dead set on a pi, I'd recommend considering the Pi4, as the ethernet is no longer shared on a single USB root port.
  19. And I need to find a way to migrate my current install. I turned 3x 8TB into a 16TB raid-5 BTRFS array, and am somewhere around 8.5-9TB in use. I thought I had a lot of headroom, but if the tools won't work...
  20. Oh <edit: expletive actually deleted>. umm, do you have a source for that?
  21. I wonder if it's more a matter of where are the sensors mounted relative to the fans. The sensors only tell the story at a very specific point in space, after all. The helios board itself is placed in the back half of the enclosure. With reversed (intake) fans, you're blowing external cool air directly on the board. With standard (exhaust) fans, you're pulling internal air that's been preheated by the HD's, across the board.
  22. OrangePi 3 uses the Allwinner H6 chip... and the issue is, basically, AllWinner (deliberately?) messed up the hardware implementation. From the wiki: http://linux-sunxi.org/Linux_mainlining_effort#Status_Matrix
  23. Yeah, no tracking number here either. My order just appeared via local courier on Monday. They said they'd have an OS image up by (last) Wednesday, but nothing yet.
  24. FYI, the Kickstarter rewards are starting to arrive.
  25. 5.1 RC4 just landed. The release notes have all been pretty calm, so I'm going to guess it'll only go to RC7 Figure 3 more weeks for 5.1, a 2 week merge window, and potentially 8 weeks for 5.2... so ~3 months puts us end of June / beginning of July