Search the Community

Hey everybody, First, thanks for Armbian. The Asus Tinkerboard and the ROCK64 both have the same processor. I'm interested why the Asus Tinkerboard gets the mainline kernel, but the ROCK64 only gets the legacy kernel. Why is this?

I'm looking for current and upcoming PXE bootable SBCs. I guess if it has uboot on a SPI chip (like ROCK64, PINE64, espressobin, opi r1 ...) this is already a good indicator that it will support PXE boot. But I'm not 100% sure if PXE will really work, it seems to be rarely used for such boards. The only board I know which does not have uboot but can boot via PXE is the rpi 3. Maybe there are other ones. Some other boards like the nanopi duo could boot via a SPI chip attached to the respective GPIO pins. Maybe someone here knows other boards with PXE boot support or has tested it already?

Hello guys, does anyone activated CVBS output on Rock64 board? After a short look into datasheet Rock64 should support 480i and 576i. Many thanks.

Pine H64 claims to follow the same price with Rock64 with the same DRAM capacity. (Note: the 4GiB version of Pine H64 can only address 3GiB DRAM due to restriction of Allwinner chips).

I have some questions about the Linux images that Ayufan built for the Rock64 board. Not really technical issues so I did not think they should go on the Github page. If this is not the appropriate place for these, let me now and I'll remove this post. Also, if this is not the place, where should I be asking these types of questions? I just downloaded the new PRE-RELEASE version of Debian Stretch from the Github page (Yes, I know it's bleeding edge, but just experimenting for now). Specifically the stretch-minimal-rock64-0.6.5-152-arm64 image. I just burned it to my eMMC board. Will boot and see how it all works tomorrow. There are a number of other .deb packages that are on the download list. Do I need any of them? I am specifically talking about these: linux-rock64-package-0.6.5_all.deb linux-rock64-0.6.5_arm64.deb linux-image-4.4.103-rockchip-ayufan-152_0.6.5_arm64.deb or linux-image-4.15.0-rockchip-ayufan-152-ga69162eb_arm63.deb linux-headers-4.4.103-rockchip-ayufan-152_0.6.5_arm64.deb or linux-headers-4.15.0-rockchip-ayufan-152-ga69162eb_arm63.deb linux-firmware-image-4.4.103-rockchip-ayufan-152_0.6.5_arm64.deb Thank you.

Hi there, Trying to build full OS image (or only kernel) to Rock64 in order to add support to AR9271 Atheros chipset. I only managed once to make the board recognize the wlan adapter only after reconnecting it (doesn't survive reboot). any help will be much appreciated.

it's not really an answer to your problem but i'll mention that for headless server oriented devices with good performance for the price, i have moved to rockchip and specifically rk3328 devices (same as rock64 board) which (should) have good Gbe and usb3. The rk3328 is not more powerful than a s905 (i don't care about hw decoder and 3D stuff) but it has a crypto extension module that works fine and will almost saturate a Gbe openvpn link, i bought a 2g/16g + bt/802ac (not working in linux yet) for around 35e, it's the alfawise z28 pro, here's a thread about it https://forum.armbian.com/topic/4708-z28-rk3328-18/ Read the thread carefully it has some serious caveats (can't boot from sdcard which it could, but no on that particular board) so it may not be a device for everyone and we are currently waiting for other box reviews to see if another one has less "linux install" problems.. i've been using a linux mainline kernel (17.04 server) on it for a month and i don't think i'll need a device more fully featured that this one for quite some time..

Hi Guys, I bought a new Rock64 and try to connect a CC1101 FM Transmitter (CC1101 wiring with the Raspberry Pi) which communicates over spi with the Rock64. How can I activate spidev on the Rock64? I tried to add spidev to the armbianEnv.txt: verbosity=1 console=both ethaddr=02:38:a0:82:2d:c0 eth1addr=02:38:a0:82:2e:c1 overlay_prefix=sun8i-h3 rootdev=UUID=52ddb7ff-487f-4f7c-8606-4e27c00ab708 rootfstype=ext4 overlays=spi-spidev user_overlays=spi-spidev param_spidev_spi_bus=0 param_spidev_max_freq=100000000 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u But spidev is not appearing in /dev/ . I only used Raspberry PI's before, that's why I'm new to use Linux Overlays and stuff like that. I hope anyone can help me.

Ok, that sounds reasonable. Just waiting on my eMMC card for the Rock64. Once that arrives, I'll give Armbian a try. How should I go about my results?

Same HC1 used, same SSD (EVO840), JMS578 on the board vs. JMS578 connected to USB 2.0 port (ROCK64 SATA cable), same firmware version on both JMS578 (JMS578_Hardkernel_v173.01.00.01.bin), same benchmark test: 'iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2': JMS578 via USB 3.0 random random kB reclen write rewrite read reread read write 102400 4 13592 14530 18712 18744 14664 14514 102400 16 46857 49586 59322 59665 50182 49651 102400 512 204547 217732 200402 205359 201479 217830 102400 1024 233728 239458 237045 247595 241844 245813 102400 16384 224437 276093 308294 317705 317230 274902 JMS578 via USB 2.0 random random kB reclen write rewrite read reread read write 102400 4 7960 7967 7995 7999 7993 7977 102400 16 15040 15643 15984 15998 15984 15930 102400 512 21761 21874 22360 22411 22416 21884 102400 1024 22332 22866 22509 22585 22582 22421 102400 16384 22476 22912 22801 22864 22765 22879 Above tests were made with performance governor... and obviously performance sucks (I've seen much better numbers already). I flashed the external JMS578 with v0.4.0.5 firmware again and tested: JMS578 with v0.4.0.5 firmware via USB 2.0 random random kB reclen write rewrite read reread read write 102400 4 7318 7967 7994 7999 7988 7976 102400 16 15584 15904 15982 15998 15984 15938 102400 512 22059 22787 22400 22442 22436 22170 102400 1024 22508 22875 22524 22586 22583 22558 102400 16384 22554 23002 22810 22853 22760 22956 So most probably this is a kernel issue and something slowing down USB has been commited to Hardkernel's 4.9LTS kernel in the meantime. Please direct all your questions at Hardkernel over in ODROID forum, I'm simply too tired to deal any more with this constant mess...

Both of these behaviours are to be expected. I've not been following pine64/rock64 development for the last 2/3 months, but I looked at the changelog the other day, and I see in the release notes for ayufan's rock64 builds "0.6.0: Highly experimental", so it's probably a known thing that it will break. You'd have to go onto the forum or IRC to find out more. The thing to realise is that it is still marked a pre-release build, and unless their development structure has changed in the last few months, 'pre-release' (in GitHub parlance) is considered testing' 'latest' (in GitHub parlance) is considered beta, and the images available from the pine64 website are the more tested 'stable' versions. The update scripts included with those builds will always default to the 'latest', but you can specify the version you want to update to if you want to force the issue. To see which one it will update to automatically, just go to the latest release tag on GitHub -> https://github.com/ayufan-rock64/linux-build/releases/latest

This works on a voluntary basis, by and large. The core team is extremely small, and so far the only board on the books with the RK3328 is the Rock64 (discussion should begin soon on Libre Computer's Renegade, but I don't know where that is), meaning it takes a lot of effort and is the only board to presently benefit from the attention. If the dev's don't have the hardware, or the hardware broke or was changed since introduction, then things come to a halt. Especially around a version bump where the currently supported boards need to take precedent. The typical reply is donations and hardware, donations and hardware. Also testing testing testing. An image can not be thought of as "stable" until it's been tested by more than just the dev team. Try the image and let us know what the results are, however I'd caution you that this board is very early in development in general, it won't be stable for some time.

I am hoping that the community can enlighten me on how the Armbian development process works. I just purchased a Rock 64 board to use for a NextCloud box at home. I am seeing that Armbian seems to be the "best" OS solution for this. I also see that the Armbian release for Rock64 is still in "testing" phase. I would really prefer to run a "stable" release for this application. So my question is how does Armbian for Rock64 move from testing to stable. What is the process, what still needs to be done? I am not a developer or linux expert by any means. I am wondering how the process works so the I can see if I might be able to assist in any way. Thanks!

Finally received my SCISHION V88 Piano box. I was able to burn the DietPi image for Rock64 to a micro SD card, place it in the micro SD slot, apply power and it booted up to a login. The ethernet showed up as eth0 but I couldn't connect to anything. Wireless also wasn't working. I'm not sure what else is broken.

I got the same Problem with my rock64 4gb. As of today the available Image are all not finished... ayufan image v. 0.5.15 only works only with my Samsung TV but not with my benq Full HD Monitor via hdmi o only get 800x600 resolution. The 0.6x image wont boot. and the exsisitng 0.5x image won't upgrade to this new build. I hope they push new builds soon.

Up to 4 GB RAM, nice. I don't believe the RK3328 (Quad core Cortex A53) is capable of pulling the kind of power the RK3288 can, so that shouldn't be as terrifying a prospect on microUSB (and to be fair, I've been running my Tinker Board on microUSB for over a week just to see what would happen, even plugged my cell phone into it). The campaign says this was done in conjunction with the Firefly board designers, explaining the name I saw floating around for a while. It's using a Rockchip PMIC, from the look of it. Probably RK805 like the Rock64. [edit] <--- The populated part is seemingly ADC, put the unpopulated part appears to have "P"s... could it be the elusive power header? no, but system control buttons I think. While that would be amazing, I'm not going to hold out too much hope. Would be interested in looking at these.

Guys I'm with you! Unfortunately I do not have enough knowledge of linux to help you ( I have Z28 PRO RLT8211e + RTL8822bs no sd boot I try https://github.com/ayufan-rock64/linux-build/releases/ rock64 image and found out that from version 0.5 eth does not work. looks like ayufan remove external phy support. Do not forget that rockchip has https://github.com/rockchip-linux/rkdeveloptool this util can write\read partition\loader\gpt table via maskrom

How can I write an image on SD card with Linux? For my current Armbian on Orange Pi Plus I have always used dd, or dc3dd if I want to see the progress. For rock64, other tools are suggested, like Etcher and PINE64 Installer (based on Etcher). I tried dd, Etcher and PINE64 Installer, without success. By the way, Etcher and PINE64 Installer have an options for verifying. Can you suggest me another way to burn the rock64 armbian image on SD Card? If needed, I have also Windows system. Thanks Matteo

I've had zero problems with my Rock64/4GB on the 171121 nightly build rock64:~# cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=rock64 BOARD_NAME="ROCK64" VERSION=5.34.171121 LINUXFAMILY=rk3328 BRANCH=default ARCH=arm64 IMAGE_TYPE=nightly BOARD_TYPE=wip INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image

@matteobp which build are you using? The image built on 21/11 boots correctly on my Rock64 board. Maybe you can extract some info from serial console, as explained here: https://forum.pine64.org/showthread.php?tid=5029

Hi. I'm currently using the armbian image (Debian Jessie) on an Orange Pi Plus board as NAS, and I bought the Rock64 one because it should have better performance in copying to and from NAS (the current average for the Orange Pi Plus is about 28-30MB/s), although so far the performance are lower than Orange Pi Plus, but it is another story. I want to use the Armbian also on Rock64, and the only available image is the server one (https://dl.armbian.com/rock64/Ubuntu_xenial_default_nightly.7z), but I was not able to use it I have already created this post Can you help me? Sorry for duplication post. Thanks in advance. Matteo

Just check project Github if there was any progress on this. In case of major progress, we mention that in a release log. It can take months, sometimes a year(s) before board is labeled stable. I only have RK3328 based TV box and have to get Rock64 first I'll check what can be done but in any case, this will still be a testing build.

Hi, do you have any progress on Rock64?

thx @Igor for testing armbian's image. I see that it's using ayufan's kernel source, from what i know his rock64 images have working ethernet on z28 pro, something different in the kernel config or dts ? Also if i wanted to build armbian rock64 against my z28 pro dts, full disassembled dts not dtsi includes (available in this thread), how would i go about that ? I also have spotted that box, haven't found any tests so far. If i'm correct you should be able to use SDMMC0 (boot sd card slot) along with the GMAC interface, Alfawise decided for some reason not to use it, that's why you can't boot from sdcard on their box..

Thanks for your feedback. I wasn't looking for a "backup" solution rather interested to find out how many disks can I operate permanently using that one USB3 port of the ROCK64. I only figured I I had to solder in order to use the board to just address two disks instead of using RAID, when I had in my hands already. I was expecting some kind of switch or jumper.. Well I should have read the manual. Since RAID1 is the default, and I didnt find anything about this board here, I shared. The board already made it into the trash. I am waiting for these cheap usb3-sata pcb boards.. https://www.amazon.com/gp/product/B01N5J63RT that is going to be my next test. Btw, somewhere here I read about the rock64 power cable assemblies, I am running my boards with these: https://www.arrow.com/en/products/10-01072/tensility-international connected to that https://www.arrow.com/en/products/lrs-150f-5/mean-well-enterprises Back to several disks per usb3, I am not considering SSDs (trying to keep the cost low), I am going to try http://www.oricostore.com/index.php?route=product/product&path=399_405&product_id=6655 I am interested to see if I can get 200mb/s out of two disks and utilizing the second 1GE over usb3.