I've Debian Sid, Slackware and Windows on the same hd.
When I start Debian, the time is 2 hours afterwards, and only
after a few time ntp syncronize it correctly. But something
is wrong, because, if I launch Slackware after Debian,
it finds that the last mount of the partitions "in the future"
and has to fix this error. I configured my area with tzconfig,
Europe - Rome. I'm not in UTC, for I've Windows too...
I add some information:
===============================
samiel@debian:~$ date -u
gio ago 2 16:59:06 UTC 2007
===============================
But obviously it's 14:59:06
In /etc/default/rcS referring to time
i've only this line:
===========
UTC=no
===========
Morevoer:
======================================================
debian:~# hwclock
select() to /dev/rtc to wait for clock tick timed out
======================================================
(but I don't understand what this means...)
On the contrary:
================================
debian:~# cat /proc/driver/rtc
rtc_time : 19:28:36
rtc_date : 2007-08-02
rtc_epoch : 1900
alarm : 00:00:00
DST_enable : no
BCD : yes
24hr : yes
square_wave : no
alarm_IRQ : no
update_IRQ : no
periodic_IRQ : no
periodic_freq : 1024
batt_status : okay
================================
Is there a solution to have the right hour
at the boot, and not only after the syncronization with ntp?
Thanx!
M.
Bookmark/Search this post with:
The right hour...
That SHOULD work, so the only possible problem I can think of is something mentioned in the hwclock docs:
If you specify neither --utc nor --localtime , the default is whichever was specified the last time hwclock was used to set the clock (i.e. hwclock was successfully run with the --set, --systohc, or --adjust options), as recorded in the adjtime file.
So look at /etc/adjtime and see whether that indicates UTC (still frequently incorrectly called 'GMT') or LOCAL. If it's not LOCAL, use 'ntpdate' to immediately set the date/time and then use hwclock --localtime --systohc and that should rewrite the adjtime file as well.
The right hour...
/etc/adjtime is set to LOCAL.
debian:~# hwclock --localtime --systohc
select() to /dev/rtc to wait for clock tick timed out
I'm not able to understand what mean the output
of command. I tried, but it dies't work...
Thanx!
M.
The right hour...
The message you are getting means that hwclock was using the select() system call to test if the RTC has just updated the seconds. Did hwclock update the RTC even though it gave you that message?
If you can find out which support chip actually has the RTC, you might be able to use Google to search for known issues with that chip and hwclock.
The right hour...
Try from the command line:
hwclock --systohc --directisa
if that works with no errors, edit /etc/init.d/hwclock.sh
and change the line:
HWCLOCKPARS=
to read:
HWCLOCKPARS="--directisa"
--
Jai yen
The right hour...
========================================================
debian:~# date
dom ago 5 03:41:33 CEST 2007
debian:~# hwclock --localtime --systohc
select() to /dev/rtc to wait for clock tick timed out
debian:~# date
dom ago 5 03:41:45 CEST 2007
debian:~# hwclock --systohc --directisa
debian:~# date
dom ago 5 03:41:56 CEST 2007
========================================================
Nothing changes: it's 01:etc..., not 03:etc....
M.
The right hour...
http://www.mail-archive.com/debian-devel@lists.debian.org/msg236472.html
Penso que il calculatore non capisce Italiano.
The right hour...
hwclock --systohc --directisa
Sorry, I made some confusion and changed the hw clock too.
Now, with the above string it seems works fine!!
Thanx!!
M.
The right hour...
Cheers!
--
Jai yen