(04-01-2016, 03:24 AM)seaniefs Wrote:(04-01-2016, 03:10 AM)Andrew2 Wrote:(03-31-2016, 03:57 PM)seaniefs Wrote: Yes, the 2GiB model boots OK for me with the Arch Linux Xfce4 image (arch-pine64-bspkernel-20160304-1-xfce4.img as found on http://wiki.pine64.org/index.php/Pine_A6...re_Release) with Gigabit Ethernet plugged in.
Could you please post the output of
Code:grep MemTotal /proc/meminfo
when running this image and in case it shows just 1 GB RAM if possible also the output from longsleep's minimal Arch image?
Sure, I'll try and do this at some point today.
However, I can tell you that htop on the Xfce4 image shows slightly less than 1GiB free, so therefore it seems to think it's a 1GiB model (some allocated for display); but will give you the exact output later...
Hmm... I believe no further testing is needed and I would believe the root cause is somewhere else (wrong .dtb loaded). Longsleep added support for the 512MB model a few weeks ago (needs another .dts file for different Ethernet settings) and implemented automatic switching based on detected DRAM size in u-boot so that on models with 512MB or less (!) the .dtb for Pine64 (Fast Ethernet) will be loaded and otherwise the one for Pine64+ (GbE).
And I suspect that this detection goes wrong for whatever reasons (0 GB detected at this stage?) so the wrong .dtb will be loaded which then leads to a crash (and endless reboot loop on Android since there a watchdog restarts the board)
EDIT: Nope: http://forum.pine64.org/showthread.php?t...53#pid4553
So if there's something to test then please update the Xfce4 image with latest u-boot and report back:
Code:
bash <(curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_update_uboot.sh)
bash <(curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_update_kernel.sh)