(02-17-2018, 06:04 AM)CallMeFoxie Wrote: fdisk the emmc to see what it actually is/reports and reseat all the partitions. The forementioned dd wouldn't have destroyed eMMC ... at least I'd think so

(08-15-2017, 01:01 PM)CallMeFoxie Wrote: Hi

As I've created a thread earlier last week, I've got a working image for Pine64+ with complete mainline support:


Features
Kernel 4.14 branch, few extra patches (ethernet DTB revert and few others)
U-Boot 2017.09 branch, no external patches
NO boot0! Uses U-Boot SPL
Updates via normal debian packages for kernel (metapackage linux-image-pine64 keeps up2date kernels), no u-boot automated updates yet
Docker 17.09 branch or newer (installable via Debian package docker-ce) with Overlay2 full support
Debian Stretch with Systemd
Boot log: https://github.com/CallMeFoxie/pine64-mainline-project/blob/master/bootlog.txt

Tested on 2GB Pine64+, should work on 1GB version as well, unsure about 512MB version. Definitely would need to swap DTBs around.

Docker and Kernel are hosted on my repo (https://repo.foxiehost.eu/debian stretch main) and its key is imported to the image.
Boots via U-Boot through extlinux.conf -> ext2 partition with vmlinuz-* + fdt file -> ext4 rootfs (default 4GB, can be resized).
Kernel updates trigger extlinux.conf generator, normal kernel rules apply (keep last 2 and mark the other for removal etc).


Downloads:
[b]Base build 2017-10-15
[/b]https://repo.foxiehost.eu/pine-image/pine64-plus-stretch-mainline-20171015.img.xz
Kernel 4.13.6/U-Boot 2017.09


Base build 2017-08-15
https://repo.foxiehost.eu/pine-image/pine64-plus-stretch-mainline_20170815.img.xz
Kernel 4.13.0-rc5/U-Boot 2017.09-rc2






Source configs and scripts to build the images:
https://github.com/CallMeFoxie/pine64-mainline-project
(uses Docker to compile kernel/uboot/atf)


Known issues for latest base image:
SSH keys are not re-generated! It is suggested to delete them and ssh-keygen -t them on the first bootup. (Fixed in github already)
Fixed clock (~900MHz), no cpufreq/voltage regulation - missing kernel modules in upstream (as of 4.13.0-rc5)
No HDMI output (missing drivers)


Default config:
IP: 10.0.0.199/24, gw 10.0.0.138
SSH enabled:
Login: user pine, password pine; use sudo to get root


To do:
Fix known issues
- please use github issues for that.

Updates:
19/12/2017 - Released kernel 4.14.7 into repository, update via Apt and reboot
22/11/2017 - Released kernel 4.14.1 into repository, update via Apt and reboot
28/10/2017 - Released kernel 4.13.10 into repository, update via Apt and reboot
15/10/2017 - Released Docker-ce 17.09, update via Apt
15/10/2017 - Released new base image (*not required* to update, just rollup of kernel+base pkgs)
15/10/2017 - Released kernel 4.13.6 into repository, update via Apt and reboot
27/08/2017 - Released kernel 4.13.0-rc6 into repository, update via Apt and reboot (nothing else required)
28/08/2017 - Released kernel 4.13.0-rc7 into repository, update via Apt and reboot (rc5 should be autoremove-able)
28/08/2017 - Released Docker-ce 17.07.0-ce-rc4, update via Apt
30/08/2017 - Released Docker-ce 17.07-ce (final), update via Apt

(03-11-2018, 11:04 AM)CallMeFoxie Wrote: DHCP client has been in since the beginning however the default state is to boot up with fixed IP (for when it is booted in standalone mode without any terminal connected).

MALI driver is not in yet, will see when 4.16 stable kernel comes along possibly.

(06-25-2018, 12:51 PM)Baldnerd Wrote: Is this something up with the distro? Or is it the board itself?

(06-25-2018, 06:08 PM)evilbunny Wrote: There is a bash script that you can get those details from it...

Code:

/usr/local/sbin/rock64_diagnostics.sh -m

(06-25-2018, 06:28 PM)Baldnerd Wrote:

(06-25-2018, 06:08 PM)evilbunny Wrote: There is a bash script that you can get those details from it...

Code:

/usr/local/sbin/rock64_diagnostics.sh -m

Thank you. Yes, I did some searching around before posting, and spotted this as one of the tips, but that script is missing from my filesystem. Did it come with the img? Or something I have to install?

I'll confirm once I can boot up the image (later tonight) -- it's always possible the instructions I'd followed had a typo in the file path.  

Thanks!