I did not yet rebase all patches. May do that at some point.
I have just been playing with the Artful minimal image and Lubuntu-QT-Desktop which works real nice.
17.10 has the 4.13 Kernel but was looking at the dates and hoping maybe the 4.14 LTS will be released before the 5th Kernel Freeze — October 5th.
The inclusion of 17.10 I guess is statement of intent and both LTS of 18.04 & 4.14 are a wished destination.
he complete release schedule of Ubuntu 17.10 as follows:
Alpha 1 — June 29th
Alpha 2 — July 27th
Feature Freeze — August 24th
Beta 1 — August 31st
Final Beta — September 28th
Kernel Freeze — October 5th
Release Candidate — October 12th
Ubuntu 17.10 final release — October 19th
4.14 is already RC2 so maybe and its brilliant to have a product and being among developers who are talented enough to be so bleeding edge.
Its looking really good for the Rock64 as a LTS product that will have a long life and the pains for some of early adoption are prob going to pay dividends.
I have seen some entries for other Arm SoCs but Rockchip & Pine have got much adoption in the kernel.
My alternative to the Rock64 is the Odroid XU4 and maybe I have missed things but its looks like hardkernel have missed the 4.14 boat.
Raspberry dont have a Pi4 till 2019 and looking like the Rock64 has a market space of 2 years.
There will be a beer for backporting 4.14 for Ayufan and think without asking that is going to happen if 17.10 misses 4.14 but it could end up in 17.10 and Ayufan & Ubuntu seem to have working images with 17.10 & the 130 release.
Unlike all the other images the pre-release 130 works whilst 118 release doesn't with 17.10.
If your playing with linux I suggest having a look at 17.10 armHF Lubuntu-QT-Desktop as its under heavy development for the 17.10 release so actually its quite stable.
Also maybe its the MALI driver of 4.12 or a fix but the colours seem to look more vibrant.
Recently I have been experimenting with the stock 4.14.x kernel code from kernel.org on my ROCK64 (with no patches at all). 4.14 boots up ok although HDMI doesn't work. Serial console and ethernet both work.
The 4.14 kernel does need the dtb that is generated from the 4.14 build. You must update both the kernel and dtb to the 4.14 versions created in the 4.14 build for it to work. If you try to boot the 4.14 kernel without updating the dtb also, it doesn't work.
I took a shot at porting the mali code to 4.14. WIth some changes to the mali code I got it incorporated into my kernel but I still don't get any HDMI output. I don't know much about graphics but there may be more pieces needed before HDMI works.
Just placed an order for my rock64 but didn't read this thread.
Chose rock64 board for good throughput from NIC and USB 3 but now reading these posts makes me worry the Xenial builds will be unstable.
Tell me it isn't so..
I got fed up with my Banana Pi2 Ultra having poor support and crashing once in a while.
Just need a 24/7 Single NAS drive...
Hi,
I installed Fedora rawhide (up coming 28) on my rock64 by replacing the rootfs of one of the debian images. It works well - no problems there. The next step I tried was to replace the Ayufan 4.4 kernel with mainline. I resized the boot partition (and added swap partition while at it) and things still worked OK. I had to do this so that I could fit the necessary files on the boot partition.I tried to replace Image, dtb and initrd.img with the corresponding files from Fedora as follows (built the source rpm):
Image <- arch/arm64/boot/Image (also tried vmlinuz from the binary kernel rpm)
dtb <- /usr/lib/modules/4.15.0-0.rc3.git1.1.fc28.aarch64/dtb/rockchip/rk3328-rock64.dtb
and finally to prepare the initrd.img I did: dracut -f /boot/initrd.img 4.15.0-0.rc3.git1.1.fc28.aarch64 (also tried using the initramfs produced by installing the binary kernel rpm)
Well, no cigar. It does not seem to boot. I also tried modifying /boot/extlinux the same way as it would be on standard fedora (and use the standard files that appear under /boot on installing the kernel rpm), but no go.
Any thoughts how this should be done? Also, has anyone gotten 4.15.0-rc3 to boot (I did not try 4.14)? I have the system setup so that it will go online on boot and start sshd. So, I should be able to tell if it came up over the network even if the console did not come up. I can get the system to boot again if I copy the original Image, dtb and initrd.img to /boot.
Thanks,
Jussi