(ARCHIVED) Ubuntu Xenial Image (BSP Kernel)

[rahlquist]

I think I may have some further insight. I tried arch and remix os today and same thing happens with the ethernet cable connected. It looks like other people with 2GB boards are having the same problem (e.g. look here: http://forum.pine64.org/showthread.php?tid=488).

[edit] plugging in the ethernet after booting up remix os causes an instant crash followed by endless bootloop
[edit 2] just tried arch - the exact thing happens as with Ubuntu

Yeah, I tried arch last night as well - the same issue happens. My model is the 2gb model. Haven't tried Remix though. I haven't experienced a boot loop in Ubuntu or Arch though - the kernel just oops and sits there (I cant type in the terminal) -> which i think is the kernel panicking.

Starting to wonder... They had supply issues with the Ethernet IC I think they said after the quake in Taiwan. I wonder if they got ahold of a bunch of counterfeit or B grade chips while trying to fill their supply lines once again. I'd sure like to know if they boot tested these boards with anything.

[Andrew2]

I wonder if they got ahold of a bunch of counterfeit or B grade chips

The RTL8211 chips used on Pine64 are used in dumb mode (PHY only) since the MAC who does the real work sits in A64 processor. So no worries... even grade D chips would work flawlessly if they would exist and the whole problem seems to be related to DRAM capacity for yet unknown reasons.

[Luke]

I think I may have some further insight. I tried arch and remix os today and same thing happens with the ethernet cable connected. It looks like other people with 2GB boards are having the same problem (e.g. look here: http://forum.pine64.org/showthread.php?tid=488).

[edit] plugging in the ethernet after booting up remix os causes an instant crash followed by endless bootloop
[edit 2] just tried arch - the exact thing happens as with Ubuntu

Yeah, I tried arch last night as well - the same issue happens. My model is the 2gb model. Haven't tried Remix though. I haven't experienced a boot loop in Ubuntu or Arch though - the kernel just oops and sits there (I cant type in the terminal) -> which i think is the kernel panicking.

Starting to wonder... They had supply issues with the Ethernet IC I think they said after the quake in Taiwan. I wonder if they got ahold of a bunch of counterfeit or B grade chips while trying to fill their supply lines once again. I'd sure like to know if they boot tested these boards with anything.

Dont think its a problem with the IC (although my knowledge on this subject matter is limited). What I do know for sure, however, is that they have not boot tested the 2gb boards because with the ethernet cable connected nothing works. Kind of hard to overlook such an issue wouldn't you say   I hope this gets solved soon ...

[Andrew2]

Is anyone of you 2GB users equipped with a serial console and can tell us how the output of 'Pine64 model: ' looks like when u-boot is starting?

Background: See the comment to this commit.

[Jagmn]

Is anyone of you 2GB users equipped with a serial console and can tell us how the output of 'Pine64 model: ' looks like when u-boot is starting?

Background: See the comment to this commit.

I attached one to my post; and have done the same again for this one. Thanks for looking into this.

The log shows:
Pine64 model: pine64-plus

[Andrew2]

The log shows:
Pine64 model: pine64-plus

Thx, then DRAM detection works and the correct .dtb is chosen:

Code:

DRAM:  2 GiB
...
get Pine64 model from DRAM size
DRAM >512M
Pine64 model: pine64-plus

Unfortunately no more ideas... just one: which is the exact model number of the PHY used on the 2GB model? RTL8211...?

[DaveKram]

The log shows:
Pine64 model: pine64-plus

Thx, then DRAM detection works and the correct .dtb is chosen:

Code:

DRAM:  2 GiB
...
get Pine64 model from DRAM size
DRAM >512M
Pine64 model: pine64-plus

Unfortunately no more ideas... just one: which is the exact model number of the PHY used on the 2GB model? RTL8211...?

Looking more at that log file, I see this:

Code:

** Unable to read "uboot.env" from mmc0:1 **
Using default environment

--------fastboot partitions--------
mbr not exist
base bootcmd=run mmcbootcmd
bootcmd set setargs_mmc
key 0
recovery key high 12, low 10
fastboot key high 6, low 4
no misc partition is found
to be run cmd=run mmcbootcmd
update dtb dram start
update dtb dram  end
serial is: 041051900804281c034b
get Pine64 model from DRAM size
DRAM >512M
Pine64 model: pine64-plus

It can't load uboot.env and then the default settings are used and  DRAM is 512M? Am I reading that right? Or is that saying DRAM is greater than 512 and the plus model is chosen?

Clearly says greater than 512 and the model is pine64-plus.

[Andrew2]

It would be interesting how a complete boot log looks like when using the pretty outdated Arch/XFCE image since then Linux only detects 1 GB of DRAM and the Ethernet problem doesn't occur.

The aforementioned Arch image misses all fixes/improvements longsleep made the last 4 weeks so maybe it's possible to find the culprit by comparing. At least a boot log might help...

[longsleep]

I got a 2GB model in the mail today. So i guess i can look into this now

[Luke]

I got a 2GB model in the mail today. So i guess i can look into this now

May the computer gods bless you longsleep !