You are not logged in.

#1 2009-12-24 16:23:47

iamsmrt
Member
Registered: 2009-08-12
Posts: 138

Hardware clock issues

For some reason, all of a sudden, I started getting this error on startup:

select() to /dev/rtc to wait for clock tick timed out

I looked up a fix and found that adding the "--directisa" parameter for hwclock worked. First I tried by editing my rc.conf file, setting "USEDIRECTISA="yes"". This didn't do anything so I went into rc.shutdown and rc.sysinit to manually add these parameters. Why doesn't editing the rc.conf file work?

Secondly, why the hell does my computer suddenly need to use directisa? I haven't had my battery plugged into my laptop for a while and I read somewhere that may cause an issue with the BIOS, is that it?

Also, how do I get the clock to be accurate again? I set the hardware clock manually and it's roughly close, but I'd like it to be accurate.

Offline

#2 2009-12-24 18:03:20

Cyrusm
Member
From: Bozeman, MT
Registered: 2007-11-15
Posts: 1,053

Re: Hardware clock issues

I'm not really sure about the first part of your problem, but if you want accurate time I would suggest Network Time Protocol.
here's the wiki page: http://wiki.archlinux.org/index.php/Net … e_Protocol
basically, it's a daemon that sets your clock off of various network servers.  it's wicked easy to set up.
just install, and then include it in your /etc/rc.conf daemons array.


Hofstadter's Law:
           It always takes longer than you expect, even when you take into account Hofstadter's Law.

Offline

#3 2009-12-24 19:21:58

iamsmrt
Member
Registered: 2009-08-12
Posts: 138

Re: Hardware clock issues

Looks like USEDIRECTISA functionality has been removed from rc.conf:

http://www.mail-archive.com/arch-dev-pu … 09387.html

Offline

Board footer

Powered by FluxBB