Pine A64 Plus Fails to Boot

[Luke]

pfeerick

I've now heard more than 4 reports of this in the IRC. It seems like if you first boot with HDMI connected then after consequent reboots headless doesn't work. Based on the feedback from other users who had this issue, the "solution" is too boot headless on first boot...

---

Figured out how to roll back:

pine64_update_kernel.sh 3.10.104-2-pine64-longsleep-113

And after that... still crashes.  Plug monitor back in, try again with 3.10.104-1-pine64-longsleep-103...

And it works!  So it's something that changed in 3.10.104-2-pine64-longsleep-113

Thanks for letting us know! Just a heads up: in 3.10.104-1 you will still likely experience problems with GbE ethernet.

See longsleep's potential explenation for the issue at: 12:04:16 and 12:09:06

11:32:59 <lukasz> longsleep: looks like people encounter issues booting headless if they boot WITH HDMI on first boot. 
11:33:14 <lukasz> Seems to only affect 3.10.105 ? 
11:34:16 <longsleep> lukasz: mhm - well some touch screen related modules were enabled in .105, but i still think that it might be a power issue. Has anyone reproduced this when powering through euler? 
11:35:09 <lukasz> not to my knowledge 
11:36:28 <longsleep> lukasz: what exactly is the problem? Can you describe it? 
11:38:44 <lukasz> Unfortunately no, as I myself havent experienced the problem 
11:38:58 <lukasz> but from what I understand some users boot with mouse/keyboard and monitor first 
11:39:34 <lukasz> then disconnect the mouse/keyboard and monitor and attempt to ssh on subsequent boots 
11:39:36 <lukasz> and cannot do so 
11:40:01 <lukasz> longsleep: ah, take a look here: https://forum.pine64.org/showthread.php?tid=4417 
11:41:41 <lukasz> see TinkerBear's last commnet (#8) 
11:41:47 <lukasz> comment* 
11:42:17 <lukasz> he rolled back and wrote "And it works! So it's something that changed in 3.10.104-2-pine64-longsleep-113" 
11:43:53 <maya> new distros to look like old windows  
11:44:29 <longsleep> lukasz: rolled back where? 
11:44:48 <lukasz> to an older kernel 
11:44:54 <longsleep> lukasz: yes to which one? 
11:45:27 <lukasz> 3.10.104-1 
11:46:12 <longsleep> lukasz: mhm thats without GbE fix, does he use ethernet? 
11:46:30 <lukasz> dont know - will let him know 
11:53:24 <longsleep> lukasz: please tell people with that problem to add their details to https://github.com/longsleep/build-pine6.../issues/51 - as it seems to be related 
11:56:27 <lukasz> pfeerick already added that 
11:56:37 <lukasz> *linked that 
12:02:50 <longsleep> lukasz: so just for me to understand this correctly,people have issues when booting for the first time when HDMI is connected, right? 
12:03:00 <lukasz> right 
12:03:04 <lukasz> thats how I understand it too 
12:04:16 <longsleep> lukasz: mhm, HDMI draws power - maybe in some cases it draws to much and the extra current cannot be provided through HDMI 
12:05:09 <lukasz> longsleep: Well the issue is that hte board doesnt boot AFTER no HDMI is connected on subsequent boots 
12:05:14 <lukasz> thats how I understand it 
12:06:12 <longsleep> lukasz: i do not get that part - does not boot after no HDMI .. ? 
12:07:19 <Pepe> Hello guys 
12:07:23 <longsleep> lukasz: also the log https://forum.pine64.org/attachment.php?aid=775 is from debian, no idea what so ever was modified there 
12:07:50 <longsleep> lukasz: that log pretty much starts crashing once wifi gets enabled, most likely power issue 
12:08:28 <longsleep> lukasz: also the wifi driver is crap and can cause all kind of crashes 
12:08:31 <lukasz> First time the user boots in a desktop configuration - mouse, keyboard, screen all connected. Then, they disconnect all peripherals and decide to run headless. As I understand it, this is where problems arise - the board wont boot without a screen attached. 
12:08:34 <longsleep> lukasz: i suggest to not use it 
12:09:06 <longsleep> lukasz: yes, they most likely remove stuff which feed extra power - now lacking that power things stop working 
12:09:22 <lukasz> ah, understand ... 
12:10:02 <lukasz> but, would this explain why rolling back to an older kernel (3.10.104-1) would solve the issue ? 
12:11:24 <longsleep> lukasz: just a coincidence, and it might draw less power as it does not load various modules and in case you have one of those boards with GbE timing issues also does use almost no power 
12:11:46 <lukasz> alright