Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

862 profile views
  1. The strangest thing happened today. I switched of my rok64 rev.2 and connected to my PC to move the files of my USB HDD. My plan was to change the disk format from NTFS to EXT4. Then when i plugged it back in the rock64 wouldn't boot properly. Turns out my USB 3 port isn't working anymore with the USB HDD or any other USB drive. The light comes on for my SSD but fdisk -l doesn't see it. Could one of the firmware updates broken it? UPDATE... I downloaded the latest Ayufun arm64 bionic build and booted from this. My USB 3 HDD was picked up fine. I've gone back to the new Armbian Bionic build and it doesn't work. Only on USB 2 ports. Something must have changed with the latest build (u-boot / firmware) that's caused this issue. If you need some logs, please let me know... Will need a hand with the commands to run.
  2. It's been over a week and so far the rock64 NIC has been stable. I'll update further if anything changes. Many thanks for all the help.
  3. Thanks, I've just made the update to my rock64 and will see how it goes over the next couple of weeks. The NIC is only stable for a maximum of a week.
  4. Thanks jpegxguy , I will try that. What is mkscr? and where does the boot.cmd live? Don't know why my rock64 gets this but i don't see other people discussing this. It's about once a week and the only recovery is to restart it.
  5. Hi, Another NIC failure today that I managed to grab before I restarted it. As you can see 750 TX errors.... I've attached so other logs... Hope this helps. Seems I'm the only one getting this which makes me think, is it my router? eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet netmask broadcast inet6 fe80::8023:c6f6:b8cd:f435 prefixlen 64 scopeid 0x20<link> ether 8a:aa:04:a1:19:ec txqueuelen 1000 (Ethernet) RX packets 1424321 bytes 234852215 (234.8 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2583586 bytes 3741269708 (3.7 GB) TX errors 750 dropped 0 overruns 3 carrier 0 collisions 0 device interrupt 40 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet netmask inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1 (Local Loopback) RX packets 44263 bytes 49204370 (49.2 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 44263 bytes 49204370 (49.2 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Maybe this patch will fix it for mainline kernel https://patchwork.kernel.org/patch/10846013/ Is it difficult to change my kernel from 4.4 to 5? dmesg.txt armbian-hardware-monitor.log kern.log
  6. How's the Rev 3 of the ROCK64 going? How did you manage to get it as the website doesn't seem to show whether its rev2 or 3 that you get.... Realise there are more powerful boards out there but don't need some power hungry board for my needs, though the Odroid N2 looks tempting and low power too.
  7. So if I understand correctly, the next kernel release for rock64 will be 5.0xxx! That's great. I see that Ayufan on github is still working on 4.4 . Personally I'd be happy with just a stable build.... Thanks for all the hard work. Would like to think that there is still plenty interest in the the 3328....
  8. I've added the setting to the header but I don't get the Kernel or DTB information. Not sure why. I put your additional settings at the end of the file.
  9. I like the armbian-system-packages armbian header information. Will modify my rock64 to output the additional information. Thanks for the tip!
  10. Just saw these recent changes to the mainline Kernel on Ayufun's git repository. Maybe this will help... Will these come across to the Armbian build? https://github.com/ayufan-rock64/linux-mainline-kernel https://github.com/ayufan-rock64/linux-mainline-kernel/commit/41eeb7cd789ea7cac0cbf4b35b53055f354da757 https://github.com/ayufan-rock64/linux-mainline-kernel/commit/41eeb7cd789ea7cac0cbf4b35b53055f354da757
  11. Hi TonyMac32, hope this info helps uname -a Linux rock64 4.4.174-rockchip64 #6 SMP Sun Feb 10 10:43:16 CET 2019 aarch64 aarch64 aarch64 GNU/Linux dmesg ip link show dev eth0 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000 link/ether 8a:aa:04:a1:19:ec brd ff:ff:ff:ff:ff:ff ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet netmask broadcast inet6 fe80::8023:c6f6:b8cd:f435 prefixlen 64 scopeid 0x20<link> ether 8a:aa:04:a1:19:ec txqueuelen 1000 (Ethernet) RX packets 25652717 bytes 25286449632 (25.2 GB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 21508044 bytes 10823532692 (10.8 GB) TX errors 135 dropped 0 overruns 135 carrier 0 collisions 0 device interrupt 40
  12. Thanks. I'll capture the information on the next failure (which shouldn't be more than a week).
  13. Hi, my rock64 (rev2) with the latest build of Armbian randomly looses its network connection. I couldn't use the armbianmonitor -u as it had no network connection, but when i use ifconfig, I can see it's still got it's settings and is the NIC lights are on. ifconfig showed 6 TX errors. My NIC is set to DHCP with static reserved IP address to an ASUS router. I leave it on 24/7 and check it once a while as it pretty much is used as a NAS with a single USB 3 drive. This morning I connected up via HDMI and a USB keyboard and logged in successfully. I don't have much Linux experience so wasn't sure how to capture the logs to SD card so i could copy them up here later. The NIC dropouts occur about once a week at random days and times. I have tried use ifup and ifdown to try and re-enable the NIC, but when I did this I got a stack dump and I couldn't enter any further commands into Ubuntu. Next time the NIC fails, what command(s) should I use? I've had this issue before on the later ayufun arm64 ubuntu builds too. I see the kernel has been updated to v5 over at ayufun's github, maybe there are some code changes that might help. I did read that dropping the MTU down from 1500 to 1492 might help, but don't really want to make random changes. Any suggestions much appreciated.
  14. I'd like to think that pine64 would send you the current and popular selling rev 2 which I've had for 9 months as well as rev 3 when it comes out as you as well as every other dev on Armbian is helping make the rock64 more reliable and useful
  15. Thanks for your hard work. Just started using Armbian on my Rock64 rev 2. Pleased with performance and resource usage. I did notice that it updated from 5.73 to 5.75 during an upgrade but when I login, it still shows 5.73.... I read that Rock64 rev 3 with POE will be released in the coming months.
  • Create New...