09-09-2016, 12:05 AM
(This post was last modified: 09-09-2016, 12:06 AM by UnixOutlaw.)
OK - now my Pine64+ (2 GB) won't stay "on" when I've got it connected to my lapdock. Longsleep latest Debian XFCE build...
It was working before I did :
https://www.pine64.pro/getting-started-linux/ :
(didn't need to resize - I already did that from GParted on my Linux workstation)
When I power it up, either from the power button, or plugging into mains (i.e. USB otg) - it stays up...
Once it's up - and - staying up - if I plug it into my Lapdock - I get nothing output...
If I try to power it up connected to the Lapdock - either drawing power from the Lapdock or direct from mains (i.e. USB otg) the PWR LED will come on for about 5-10 seconds then it shuts off again.
If I can get it "rescued" from this state (e.g. SSH over ethernet [I don't know what IP address it's getting over work's WiFi]) I'm going to rename the host to pezzo-di-merda...
It was working before I did :
https://www.pine64.pro/getting-started-linux/ :
Code:
sudo -i
/usr/local/sbin/pine64_update_uboot.sh
/usr/local/sbin/pine64_update_kernel.sh
resize_rootfs.sh
reboot(didn't need to resize - I already did that from GParted on my Linux workstation)
When I power it up, either from the power button, or plugging into mains (i.e. USB otg) - it stays up...
Once it's up - and - staying up - if I plug it into my Lapdock - I get nothing output...
If I try to power it up connected to the Lapdock - either drawing power from the Lapdock or direct from mains (i.e. USB otg) the PWR LED will come on for about 5-10 seconds then it shuts off again.
If I can get it "rescued" from this state (e.g. SSH over ethernet [I don't know what IP address it's getting over work's WiFi]) I'm going to rename the host to pezzo-di-merda...