You are not logged in.
Pages: 1
I have recently noticed the following message after resuming from a hibernate (suspend to disk):
select() to /dev/rtc to wait for clock tick timed out
But the clock time is restored correctly.
I'm using kernel26beyond. Any ideas what's causing this message?
FaunOS: Live USB/DVD Linux Distro: http://www.faunos.com
Offline
What does
/sbin/hwclock --show
print?
Offline
What does
/sbin/hwclock --show
print?
After about 10 seconds it times out and says:
select() to /dev/rtc to wait for clock tick timed out
FaunOS: Live USB/DVD Linux Distro: http://www.faunos.com
Offline
Please check
/sbin/hwclock --directisa --show
If this works, we have to and add a flag such as CLOCKFLAGS or CLOCKOPTS. Unfortuntaly I'm not accustomed enough to Arch's idiosyncrasies to tell where this must be done.
Offline
It does work and returns:
Tue 03 Apr 2007 10:54:59 AM MDT -0.427332 seconds
FaunOS: Live USB/DVD Linux Distro: http://www.faunos.com
Offline
Maybe you open a new thread asking where to put such an option, for I don't know
Offline
Maybe you open a new thread asking where to put such an option, for I don't know
I'm not sure what you mean. Could you please explain? Why couldn't the script try
"/sbin/hwclock --show" first and if that fails try "/sbin/hwclock --directisa --show" next?
Last edited by raymano (2007-04-05 04:02:34)
FaunOS: Live USB/DVD Linux Distro: http://www.faunos.com
Offline
What I meant is that you need the --direct-isa option to remove the error message, but entering it by hand everytime isn't a good solution. There must be a place somewhere in the configuration files of Arch to add the option permanently, but I don't know where or which configuration file this would be.
Under Debian you would add the option in /etc/conf.d, under RHEL/CentOS you would add the option in /etc/sysconfig/clock, but I don't know where to add this option in Arch.
Offline
Well, Arch has /etc/conf.d.
Also I checked the man page on hwclock and here's what it says about directisa:
--directisa
is meaningful only on an ISA machine or an Alpha (which imple-
ments enough of ISA to be, roughly speaking, an ISA machine for
hwclock's purposes). For other machines, it has no effect.
This option tells hwclock to use explicit I/O instructions to
access the Hardware Clock. Without this option, hwclock will
try to use the /dev/rtc device (which it assumes to be driven by
the rtc device driver). If it is unable to open the device (for
read), it will use the explicit I/O instructions anyway.The rtc device driver was new in Linux Release 2.
As you see it says --directisa has no effect on non ISA machines. Why not make it the default option?
Last edited by raymano (2007-04-06 05:08:07)
FaunOS: Live USB/DVD Linux Distro: http://www.faunos.com
Offline
Well, Arch has /etc/conf.d.
Yes, of course. My mistake. I meant a clock file in this directory.
Also I checked the man page on hwclock and here's what it says about directisa:
--directisa
is meaningful only on an ISA machine or an Alpha (which imple-
ments enough of ISA to be, roughly speaking, an ISA machine for
hwclock's purposes). For other machines, it has no effect.
This option tells hwclock to use explicit I/O instructions to
access the Hardware Clock. Without this option, hwclock will
try to use the /dev/rtc device (which it assumes to be driven by
the rtc device driver). If it is unable to open the device (for
read), it will use the explicit I/O instructions anyway.The rtc device driver was new in Linux Release 2.
As you see it says --directisa has no effect on non ISA machines. Why not make it the default option?
I don't know. All I know is that many PCs may not have ISA slots but use an internal ISA bus to communicate system data such as sensors readouts.
Offline
Pages: 1