screenblanker vs login

[Gene Heskett]

How do I shut the screenblanker off on an arm64.

If the screen gets blanked, the login is busted, no username and password 
is valid and the only way out is a hard reset, which is a huge time 
killer, starting with 9.9 seconds in, a 90 second wait while the journal 
is being played back, then a return key or a 5 minute wait before it 
does a startx.

I am capable of turning the monitor off when I am done for the night, but 
everytime the blanker kicks in, 5 minutes I think, its a reboot to get 
back into this thing. And the reboot takes at least 5 minutes.


I have looked around in the xfce menu's looking for blanker timing and 
such, but they aren't there. xset gets reset to its defaults , which is 
way too fast, on a reboot.

So how do I completely disable this so I can actually get something done?
450 seconds is not enough to get logged in even.

And nothing related to ssh works until xfce is up and running.

Thanks for any hints that will restore this thing to usable.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Mirabox kernel help needed

[Leigh Brown]

On 2018-02-05 01:30, amon wrote:

Got it and printed a copy for annotation when I get to the
lab tomorrow. Thanks much.


I noticed I made a little mistake in step 4.  I've corrected it on the
website.

The step to apply the small kernel patch should be as follows:

wget -O- https://www.solinno.co.uk/public/mirabox/mirabox-sdio.patch | 
patch -p1


I also added instructions on how to download the SD8787 firmware in step 
9.


Regards,

Leigh.

Re: Utilite Pro

[Gert Wollny]

Am Sonntag, den 04.02.2018, 12:54 -0500 schrieb Scott Tablett:
> On 2/4/2018 5:46 AM, Gert Wollny wrote:
> > There is another boot partition available in
> >images/kernel-update.tar.bz2
> > 
> > and this I got to boot. It doesn't have a ramdisk. Currently, I use
> > a Ubuntu 16.04 userspace with a patched glibc to accept the old
> > kernel 3.0* that was there before though, so for some reason NFS is
> > not working and NAT seems to be disabled in the kernel (have to
> > investigate).
It turned out that iptables-nat is disabled in the kernel and some
module nfsd is missing.

unfortunately, I did an upgrade on my userspace and now it seems that
systemd has troubles with the kernel and stops booting after the
Ubuntu-blabla message, so i can not tell you much more right now.

> Thanks Gert,
> 
> You give a good idea having root on sdcard versus ramdisk.  I am not 
> seeing kernel-update.tar.bz2 in debian installer images folder.
> Maybe  you are referring to Ubuntu.
> 
> ftp://ftp.ca.debian.org/debian/dists/testing/main/installer-
> armhf/current/images/

I was referring to 

http://www.compulab.com/products/computer-on-modules/cm-fx6/#devres

This package includes the closed source driver for the graphics card,
but one should be able to use the config as a base for creating a new
4.14.16 based kernel that has etnavi support. In fact, I build such a
kernel that also booted and mounted the root partition, but then
systemd hangs same like with the kernel provided by compulab. 



> 
> Thanks for pointing out update.  I updated on-board SPI flash
> following the link you provided.
> Debian installer boot.scr results in same message.
> The Debian boot.scr checks for ${boot_targets} .  This is not set in 
> Compulab u-boot update.

When I look at this boot.scr then you have to set many parameters to
run this, but I don't know much about uboot

best, 
Gert