Simple Question, has anyone successfully booted a 2Gb Pine?

[rahlquist]

So has anyone had any success with getting a 2Gb pine to boot and/or work with the onboard Ethernet either used or not? If so which of the OS's?

[arpanj2]

Yes. Mine works fine with Android version.

[pine.tree]

I haven't, but this guy did: http://forum.pine64.org/showthread.php?t...g.#pid4059

EDIT: I haven't received my board yet. That's why i haven't done it.

[rahlquist]

Yes. Mine works fine with Android version.

Would that be Android Image Release 20160216 or Remix OS Image Release 20160227 Beta?


Thanks!

[seaniefs]

So has anyone had any success with getting a 2Gb pine to boot and/or work with the onboard Ethernet either used or not? If so which of the OS's?

Hi there,

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.

The minimal Ubuntu and Arch Linux images I've tried don't seem to work.

(The Ubuntu image locks-up for me before any login prompt.

The minimal Arch Linux image gets to a login prompt, but then shortly after generates pages and pages of output which look like exceptions of some sort)...  If I don't plug in Ethernet then I don't get those messages and I can login, but since there's no network...

Many thanks,

Sean.

[arpanj2]

Yes. Mine works fine with Android version.

Would that be Android Image Release 20160216 or Remix OS Image Release 20160227 Beta?


Thanks!

It is Android Image Release 20160216 

[Andrew2]

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?

[seaniefs]

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...

---

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...

Ok, Xfce4 ArchLinux output confirms 1 GiB accessible only:

Code:

MemTotal:        1002164 kB

Will try to do the minimal ArchLinux image later as need to reflash the sd card...

[Andrew2]

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)

[seaniefs]

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)

Thanks.

Ok, just tried and it seems worse. Now it locks up completely after getting to the graphical login screen...