Joined: 16 Dec 2014 Posts: 515 Location: Upper Columbia
Posted: Sat 02 Jan 2016, 04:38 Post subject:
Believe it or not, key fails when the hardware clock is out of sync. run psync in terminal or /root/Startup/DisabledItems/timesync. Then in terminal, type 'hwclock -wD'. This sets the hardware clock to system time. A nice gui is provided by pup clockset. Just click on the taskbar clock in openbox-session (the default wm). Restart X or reboot and gslapt should accept the keys. I've had this problem since I started with lighthouse. I thought my box just had a bum battery. The newer kernels seem to conflict with busybox in the initrd and, ironically, the measures taken in the init script to prevent data writes occuring in the future. I've commented them out in the latest distribution (also plays hell with compiling)
bash-4.2# hwclock -wD
hwclock from util-linux 2.21.2
Using /dev interface to clock.
Last drift adjustment done at 1451759374 seconds after 1969
Last calibration done at 1451759374 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2016/01/02 18:42:31
Hw clock time : 2016/01/02 18:42:31 = 1451760151 seconds since 1969
Time elapsed since reference time has been 0.000170 seconds.
Delaying further to reach the new time.
Setting Hardware Clock to 00:42:31 = 1451781751 seconds since 1969
ioctl(RTC_SET_TIME) was successful.
Not adjusting drift factor because it has been less than a day since the last calibration.
Slacko 6.3.0 FULL INSTALL
File Manager - Thunar
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum