| View previous topic :: View next topic |
| Author |
Message |
IvanHoe
l33t
Joined: 05 Oct 2002
Posts: 658
|
 Posted: Tue Jun 15, 2004 7:57 am Post subject: Unable to set system clock... |
 |
|
| I get the error "unable to set system clock to hardware clock" on boot and the opposite ("unable to set hardware clock to system clock") on shutdown. Anyone know what's causing this and how to correct it? |
|
| Back to top |
|
 |
RAPUL
l33t
Joined: 29 Dec 2002
Posts: 664
Location: Valencia (SPAIN)
|
|
| Back to top |
|
|
rburcham
Apprentice
Joined: 20 Mar 2003
Posts: 243
|
| Posted: Mon Jun 21, 2004 12:51 am Post subject: I have the same trouble.... |
|
|
The real problem here is that every boot is going to fsck your root partition because the machine is going to think that last time it was fsck'd was the epoch. And that's just wrong.
I just moved to 2.6.7 kernel too. I did the following to troubleshoot this:
| Code: | # hwclock --show --debug
hwclock from util-linux-2.12
hwclock: Open of /dev/rtc failed, errno=2: No such file or directory.
No usable clock interface found.
Cannot access the Hardware Clock via any known method.
|
Aha. No /dev/rtc (real time clock). Let's check the kernel config:
| Code: | # grep -i rtc .config
CONFIG_GEN_RTC=m
CONFIG_GEN_RTC_X=y |
Ah. It's compiled as a module. This means I either need an initrd at boot, or I need to recompile it into the kernel. I'll try the latter and let you know what happens. |
|
| Back to top |
|
|
IvanHoe
l33t
Joined: 05 Oct 2002
Posts: 658
|
| Posted: Mon Jun 21, 2004 1:16 am Post subject: |
|
|
| Thanks for the info. I'll take a look at my config a little later. |
|
| Back to top |
|
|
rburcham
Apprentice
Joined: 20 Mar 2003
Posts: 243
|
| Posted: Mon Jun 21, 2004 1:21 am Post subject: no "error" now.... |
|
|
no error, and the /dev/rtc is there. However it does hang when it tries to access it. I have to do a series of ^C and returns to get control back from the hwclock process.
It may be that I am on a PPC and I am running a stock 2.6.7 kernel. Don't know.
This isn't solved for me yet. |
|
| Back to top |
|
|
rburcham
Apprentice
Joined: 20 Mar 2003
Posts: 243
|
| Posted: Mon Jun 21, 2004 3:59 am Post subject: SOLVED |
|
|
*My* problem was that I had both CONFIG_GEN_RTC and CONFIG_GEN_RTC_X set in my kernel. What threw me off was that 2.4.x used CONFIG_PPC_RTC instead. This appears not to have been carried forward in 2.6.x.
For PPCs, just set CONFIG_GEN_RTC, leave CONFIG_GEN_RTC_X disabled, and you are golden.
This may also be the case for your AMD64 IvanHoe, but can't be sure. |
|
| Back to top |
|
|
IvanHoe
l33t
Joined: 05 Oct 2002
Posts: 658
|
| Posted: Mon Jun 21, 2004 6:45 am Post subject: |
|
|
I figured it out. I just needed to select "Enhanced Real Time Clock Support" under "Device Drivers / Character devices" and it works fine now.  |
|
| Back to top |
|
|
zawart
n00b
Joined: 03 Sep 2006
Posts: 3
|
| Posted: Sun Sep 03, 2006 4:45 pm Post subject: Cannot access the Hardware Clock via any known method AMD64 |
|
|
hi,
I have gentoo 2006.1.
I do everything what was in handbook,
and I get some error when i try to boot gento
| Code: | Setting system clock using the hardware clock [Local Time] ...
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
Failed to set system clock to hardware clock |
Of course when i delete /etc/init.d/clock and the registry 'clock' in the /sbin/rc and the symbolic link in /etc/runlevels for clock. System boot. but without syslog-ng, which is not working witout clock. Any ideas what to do to start /etc/init.d/clock without errors ?? |
|
| Back to top |
|
|
nixnut
Bodhisattva
Joined: 09 Apr 2004
Posts: 10974
Location: the dutch mountains
|
| Posted: Sun Sep 03, 2006 4:48 pm Post subject: |
|
|
Did you enable the driver for the RTC device in your kernel? Or did you use genkernel to build a kernel?
What machine does this happen on?
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered
talk is cheap. supply exceeds demand |
|
| Back to top |
|
|
zawart
n00b
Joined: 03 Sep 2006
Posts: 3
|
| Posted: Sun Sep 03, 2006 4:50 pm Post subject: |
|
|
I checked the "Real Time Clock" in Device Driver in Kernel. I don't used genkernel.
It's on Processor AMD64 3500+ s.939 , Motherboard Gigabyte GA-K8N51GMF-9
Now, it's works. I missed the driver for RTC in Character Device. 
Last edited by zawart on Sun Sep 03, 2006 5:40 pm; edited 1 time in total |
|
| Back to top |
|
|
nixnut
Bodhisattva
Joined: 09 Apr 2004
Posts: 10974
Location: the dutch mountains
|
| Posted: Sun Sep 03, 2006 5:01 pm Post subject: |
|
|
Merged above three posts here.
Let's continue here.
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered
talk is cheap. supply exceeds demand |
|
| Back to top |
|
|
SHINODATT
n00b
Joined: 07 Jan 2006
Posts: 70
Location: Ontario, Canada
|
| Posted: Mon Sep 18, 2006 10:41 pm Post subject: |
|
|
I had the same problem and just found out I didn't have Generic RTC support enabled in my Kernel.
DOH!!! |
|
| Back to top |
|
|
|
Gentoo on AMD64
