Alain Guibert wrote:
> Hello Michael,
>
> On Wednesday, April 9, 2008 at 10:58:23 +0200, Michael Grosser wrote:
>
>> On a chip set "NVIDIA nForce 630a" the commans "hwclock --show"
>> produces the output "select() to /dev/rtc to wait for clock tick
>> timed out".
>
> It can be a hardware bug, a kernel bug, or something else. What is the
> output of:
>
> | # hwclock --rtc=/dev/rtc0 --debug
hwclock: unrecognized option `--rtc=/dev/rtc0'
--> It seems that the Etch version of hwclock does not have implemented
this option. I destroyed my Lenny and Sid versions. As soon as I
set up a new Lenny in a few days or weeks, I will post you the
the output of that command.
Here is another output if someone finds it useful:
# hwclock --debug
hwclock from util-linux-2.12r
Using /dev/rtc interface to clock.
Last drift adjustment done at 1207932493 seconds after 1969
Last calibration done at 1207932493 seconds after 1969
Hardware clock is on local time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
select() to /dev/rtc to wait for clock tick timed out
...got clock tick
In the meantime, I solved my problem by performing a workaround:
I edited the file "/etc/init.d/hwclock.sh" and replaced the entry
HWCLOCKPARS=
by this entry:
HWCLOCKPARS="--directisa"
I found that solution here:
http://lists.debian.org/debian-user/2008/02/msg01259.html
So, from now on, my system clocks show me the correct time and
not anymore a time that is wrongly 2 hours ahead (I always use
local time instead of UTC, because normally I use multiple
different operating systems on my computers).
>
>
>> I think, this bit of information is very useful
>
> Indeed: Much thanks for reporting it. One more to the list of chipsets
> triggering the problem.
>
>
> Alain.
>
I am not sure and I did not further investigate, but: Can a possible
reason for this problem be that newer chip sets now have a
High Precision Event Timer (HPET) instead of a PIT and RTC as
suggested within the English Wikipedia?
http://en.wikipedia.org/wiki/HPET
I suppose that newer chip sets do not necessarily have a bug
but that they are technically enhanced and that Debian does
not cope yet with these technical enhancements.
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
