I think I found out why the keyboard was screwey. The settings were fine.
The clock is on amphetamines though, spinning about twice its proper speed, which is why I'm up at this ungodly hour: The alarm went off at "9:10" at 5:20 am. Now, I understand drift, etc. so I figure the system thought my hw clock may have been set to GMT or some other foolishness. Nope. Damned thing is chugging away at insane speeds, whether NTP is running or not. # /usr/sbin/ntpdate pool.ntp.org && /usr/sbin/ntpdate pool.ntp.org && /usr/sbin/ntpdate pool.ntp.org && /usr/sbin/ntpdate pool.ntp.org Looking for host pool.ntp.org and service ntp host found : hopfen.linux-kernel.at 12 Mar 06:05:50 ntpdate[17401]: step time server 213.129.242.93 offset -7.903172 sec Looking for host pool.ntp.org and service ntp host found : hopfen.linux-kernel.at 12 Mar 06:05:51 ntpdate[17402]: step time server 213.129.242.93 offset -1.268802 sec Looking for host pool.ntp.org and service ntp host found : hopfen.linux-kernel.at 12 Mar 06:05:52 ntpdate[17403]: step time server 213.129.242.93 offset -0.505580 sec Looking for host pool.ntp.org and service ntp host found : hopfen.linux-kernel.at 12 Mar 06:05:53 ntpdate[17404]: step time server 213.129.242.93 offset -0.761701 sec # That's insane. In the time it took to run ntpdate, the system was off by over half a second! Anyone have ANY clue why it might do this and how I could fix it? Thanks. Brian _______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
