> Well, I don't know. There are several possible scenarios. Maybe a
> misdesigned RTC chip (generally integrated in the chipset), or poor
> design of the motherboard. The interrupt is absent, or not routed to the
> processor, or used for something else, or... the kernel misdetected the
> chip, and didn't do some required initialisation. Or something else...
> Really I don't know, and your 2 machines could even have 2 different
> problems hidden under the same timeout symptom.
I don't know either, but I think am not the only one with these
problems. Let's get your script working, that will be a fine solution.
> | Bugs: The /dev/rtc interrupt lacks on some not completely PC
> | compatible machines. The symptoms in hwclock are either a degraded
> | precision, or even the complete failure to read and write the clock.
> | Diagnose running hwclock in --debug mode and look for messages about
> | interrupts and timeouts. The usual solution is to always use the
> | hwclock --directisa option, and to setup HWCLOCKPARS="--directisa"
> | into the /etc/init.d/hwclock.sh startup script. But better don't use
> | --directisa on machines not requiring it: if it works, the /dev/rtc
> | interrupt works better.
Looks good.
> | #!/bin/sh
> |
> | # detect signs of lacking /dev/rtc interrupt
> | function interrupt_failure () {
> | LC_ALL=C /sbin/hwclock --show --debug 2>&1 | \
> | grep -q "does not have interrupt functions\|to wait for clock tick
> timed out"
> | }
> |
> | if interrupt_failure; then
> | echo "--directisa is recommended or required"
> | else
> | echo "/dev/rtc interrupt works OK"
> | fi
I tried that script on my 4 computers, it reports to use directisa on
3 of them, the fourth one is reported to work, however:
$ sudo /sbin/hwclock --show --debug
hwclock from util-linux-ng 2.13
hwclock: Open of /dev/rtc failed, errno=16: Device or resource busy.
Using direct I/O instructions to ISA clock.
Last drift adjustment done at 1190675845 seconds after 1969
Last calibration done at 1190675845 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: 2007/09/24 23:22:47
Hw clock time : 2007/09/24 23:22:47 = 1190676167 seconds since 1969
Tue 25 Sep 2007 01:22:47 AM CEST -0.990720 seconds
So even the fourth one is not working. So as you can see, I have 4
computers, and /dev/rtc works on neither of them. However, your
package works out of the box on 2 of them (the hwclock seems to use
directisa automatically), on the other two I need to specify directisa
manually.
Ondrej
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
