• Content Count

  • Joined

  • Last visited

  1. Hah, I am in an apartment complex so it's a bit crowded but I try to take the bands where only 2 or 3 people are using them rather than a dozen. Still, WiFi shouldn't be the problem when I can transfer at 20MB/s over a windows share but only do 3MB/s over the Rock64. Something is fishy there but I'm not sure if I need to reflash my board with a different bootloader or really what steps to take right now. Thanks for the info about bumping!
  2. 3 MB/s was fine for what I was expecting over my 802.11n network, but now I've upgraded to 802.11ac and it hasn't increased speeds. I've seen a few users on here get 40+ MBps over wifi, so I know that higher performance is indeed possible. I think you're right with the local loopback though, seeing as it's only a gigabit connection on the Rock64
  3. Rock64 is the server, and my apologies - I edited that post right as you were replying. Pinging in a loop from the Rock64 back to the Rock64 across different ports got a result - I haven't been able to get it to work from that IP to my desktop on the same network though. Not sure if it matters but I'm running off of an SD card and not eMMC or anything. No additional software that I would be able to name either than Plex and Samba. From what I remember the speeds were that slow prior to setting up Plex. Armbianmonitor link is
  4. It's one of the 2GB models, I bought it last summer so it's about 9 months old. Looks like it might be - if I'm doing this right (I'm a bit of a linux novice), I set iperf to be the server, and iperf -c to the IP of my Rock64. It's still hanging, whereas my Windows laptop was showing 1.73 Gbps doing the same style test. I'm definitely confused now since I can SSH into it without a problem, and have it connected with a brand-new CAT6 cable. Maybe an issue with the kernel? Edit: Novice is right, I had it configured wrong. Here's the output from iperf to the Rock64's assigned IP [ 3] local 192.168.1.-- port ----- connected with 192.168.1.-- port ---- [ ID] Interval Transfer Bandwidth [ 3] 0.0- 2.0 sec 960 MBytes 4.03 Gbits/sec [ 3] 2.0- 4.0 sec 958 MBytes 4.02 Gbits/sec [ 3] 4.0- 6.0 sec 962 MBytes 4.03 Gbits/sec [ 3] 6.0- 8.0 sec 954 MBytes 4.00 Gbits/sec
  5. Hey all! Finally got my Rock64 booted up and running. I set up a Samba server and a Plex share so I can access an attached USB3 RAID array as a media server. Initially I was getting speeds of ~3 MB/s write and attributed it to transferring over wifi with an ancient Airport Express Draft-N router. Upgraded to a Netgear R7000P and the issue still persists so I figured it would be worth it to post here. I would've attributed it to the USB3 to eSata converter going to the RAID array but doing some disk speed tests on the Rock64 shows it getting about 130 MB/s read/write speed over the connection so I doubt it's that. Samba setup is stock and my share described below. " read only = no create mask = 0777 directory mask = 0777 follow symlinks = yes wide links = yes browsable = yes " My Rock64 boots up saying it's running 5.65 stable Ubuntu 18.04.1 LTS 4.4.162-rockchip64
  6. New user of a Rock64 board, I've tinkered with a RaspberryPi and BeagleBone before but wanted something to set up as a home media server. I flashed the SD card with an "Armbian_5.42_Rock64_Ubuntu_xenial_default_4.4.124" image and it worked perfectly fine at home, connecting to my network, etc. However, I took it to a new location and it straight up refuses to boot. I've tried it on several displays and with several HDMI cables. It hangs for a solid 30-45 seconds after initiating boot with a black HDMI screen, and then turns off and back on dumping a log citing either spinup shutdown errors or a temperature shutdown on Core 0. I've flashed a separate SD card with the same image as well as the stretch image off the main Armbian page and both of them work for a short while but then proceed to crash seemingly without change ~24 hours later. Is there a large chance my board is simply intermittently dead or is the Rock64 known for being extremely picky with HDMI cables/monitors at boot? Edit: Got it home to my original setup and I have no dice there. I'm at a loss - everything seems to work perfectly with the board after flashing but only for a day or so, then it gets stuck on boot. At this point I'm keen to put it down as a defective board, I'm not sure what else it would be after trying different images, SD cards, HDMI cables, and monitors.