Okay, In short my screen goes blank with no input after ~10 minutes. So, I am in the process of going through all the log files, syslog, Xorg et cetera. In the midst of my contemplations, I wonder if anyone has fixed this problem already?
Now, I know everyone might get upset about how I accomplished my current installation of Ubuntu. My situation was bleak, no card reader to load and dd flash nand from within after copying to the sd card... I even tried to dd image the sdcard using netcat then ssh. Then stretch the partition using gparted. No dice.
It was then that in order to maintain a useable system state that I used the boot option to copy the ubuntu installation to sd card. Then I downloaded the upgrade tool using apt-get. Then I did:
This brought me up to the current state:
root@ubuntu:/home/ubuntu# uname -a Linux ubuntu 3.4.79+ #2 SMP PREEMPT Fri Dec 5 17:23:11 CST 2014 armv7l armv7l armv7l GNU/Linux
root@ubuntu:/home/ubuntu# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.3 LTS Release: 14.04 Codename: trusty root@ubuntu:/home/ubuntu#
So naturally to find the issues regarding the screen going blank while unattended and (xscreensaver is disabled).
I started combing the /var/logs to find the answer.
syslog lists console-kit-daemon as having issues when it occured so naturally I am researching that.
Xorg.0.log says Mali is not loading properly:
[ 21.808] (II) LoadModule: "mali" [ 21.809] (II) Loading /usr/lib/xorg/modules/drivers/mali_drv.so [ 21.846] (EE) Failed to load /usr/lib/xorg/modules/drivers/mali_drv.so: libUMP.so: cannot open shared object file: No such file or directory [ 21.846] (II) UnloadModule: "mali" [ 21.846] (II) Unloading mali [ 21.846] (EE) Failed to load module "mali" (loader failed, 7)
Here is Xrandr --query
root@ubuntu:/home/ubuntu# xrandr --query xrandr: Failed to get size of gamma for output default Screen 0: minimum 1366 x 768, current 1366 x 768, maximum 1366 x 768 default connected 1366x768+0+0 0mm x 0mm 1366x768 60.0*
naturally, I ssh[ed] into the pcduino3 nano after it happened... then did xrandr --query
It said no display present.
Naturally I tried, powering off/on the display, and used xset to force the default display on.
Soooo... I am guessing this might be related to Mali/console-kit-daemon/Xorg/Xrandr issue. If anyone knows anything about the specific configurations present and modules of the latest kernel build for these programs I would be very interested. Also any knowledge or references on Mali and the object librarys would be a second noteworthy thing.
Since I am typing this message from the pcduino3 nano, there are not a lot of problems I have.
I use a chargeable battery running at 100% 5v@500mamp to 2.1amps max, it is constantly charged through a firstname.lastname@example.org charger, with a high speed cooling fan. No heat issues. Most of this is end-user (myself) designed. I have had no reboot issues at all.
From what I know, certain Xorg/Xrandr/console-kit-daemon settings have been known to cause all kinds of display issues. However, since it is just a simple "power off display after no input for ~10 minutes" issue... My educated guess is that this is a specific setting. SSH[ing] in shows that the system is up and running and useable after the monitor goes dark. However the only current remedy I have is hitting the reset button.