On Fri, 2007-11-09 at 10:12 -0700, LaMont Jones wrote: > It appears that /dev/rtc does exist on your laptop, and hwclock is able > to open it for read. So the manpage is correct in its statement...
There was a combination of me not understanding the default hwclock
action and an unclear bug report by me, sorry about that.
Some clarifications:
1. By default, Debian on this latop cannot save the time between
reboots, unless I add HWCLOCKPARS=--directisa
to /etc/default/rcS, probable cause:
http://bugzilla.kernel.org/show_bug.cgi?id=7014
2. /dev/rtc exists, but is buggy (see #1)
3. Here are the logs for getting and setting the date:
[EMAIL PROTECTED]:~# hwclock --set --date="9/22/96 16:45:05"
select() to /dev/rtc to wait for clock tick timed out
^^ looks like the date couldn't be set
[EMAIL PROTECTED]:~# hwclock
select() to /dev/rtc to wait for clock tick timed out
^^ looks like the date couldn't be read
[EMAIL PROTECTED]:~# hwclock --directisa
Sat Nov 10 08:56:30 2007 -0.060346 seconds
^^ the date was read, but obviously the --set didn't work
[EMAIL PROTECTED]:~# hwclock --directisa --set --date="9/22/96 16:45:05"
^^ the set seems to have worked
[EMAIL PROTECTED]:~# hwclock --directisa
Sun Sep 22 16:45:09 1996 -0.921204 seconds
^^ Yep, using --directisa when setting the clock worked
[EMAIL PROTECTED]:~# ll /dev/rtc
crw-rw---- 1 root audio 10, 135 Nov 6 18:09 /dev/rtc
^^ root has read/write on the device
So, it would be nice if hwclock would switch to using --directisa when
either reading or writing to /dev/rtc fails or times out. Either that or
the manual page should be updated to reflect these problems.
Another Debian sid user in Sydney had the exact same problem with a
Toshiba laptop (mine is a Dell Inspiron 6400) and the HWCLOCKPARS change
fixed their problem too.
--
bye,
pabs
http://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
