[SOLVED] cannot access hardware clock!!

[makaveli87]

I've a G4 cube (it's the one with problems with alsa, X ,....).

When I boot I have this error:
Failed to set the System Clock to Hardaware clock
Failed to start /etc/init.d/clock

If I try hwclock -w :

cannot access the Hardware Clock via any known method
_________________
GoogleTalk: romanovic@gmail.com

[makaveli87]

I forgot to enable the kernel support :

Device Drivers -> Character devices -> <*> Generic /dev/rtc emulation
<*> Extended ETC operation



Now the clock works .

Thanks
_________________
GoogleTalk: romanovic@gmail.com

[Frostwarrior]

constructive revive (?)

I had the same problem, until I realized the real time clock support needs to be integrated in the kernel to work properly.

cheers

[mimosinnet]

Good to find this thread. I have been able to revive the hardware clock by enabling in the kernel:

Devide Drivers -> Real Time Clock -> PC-style 'CMOS'

CONFIG_RTC_DRV_CMOS=m

Thanks for the thread!

Cheers!

[gohmdoree]

hasn't work for me as of yet on my ppc64

[mimosinnet]

[gohmdoree]

I will have to fire up my machine and check. It was something similar to the above. The suggestions for the fix did not work for me. Still searching around.

[fbcyborg]

The suggestion for the fix doesn't work for mee too. Actually the CONFIG_RTC_DRV_CMOS module, was already set to "y".
_________________
[HOWTO] Come criptare la /home usando cryptsetup e luks
[HOWTO] Abilitare il supporto al dom0 XEN su kernel 3.X
Help answer the unanswered

[depontius]

Just an odd note on this...

I never paid much attention to the RTC. I normally build my kernels by tweaking a previous config, and for years now most things have "just worked" (TM) with occasional hiccups as kernel features changed. One of those changes, and I'm not sure what it was, came with the 3.0 kernel series. Suddenly I was having hardware clock problems at boot and shutdown. Once I was fully aware of it and had a little time to chase it down, it was easy to fix, as in this thread. But something changed with the 3.0 config, either the name or the way the option was split out, because that's when it broke.
_________________
.sigs waste space and bandwidth

[fbcyborg]

As a matter of fact I am now using gentoo-sources-3.0.4 both for the dom0 and the domU, since I'm having this problem on a Xen guest gentoo system.
Maybe it's because of that.
_________________
[HOWTO] Come criptare la /home usando cryptsetup e luks
[HOWTO] Abilitare il supporto al dom0 XEN su kernel 3.X
Help answer the unanswered

[fbcyborg]

The problem has gone, after deleting the following line in /etc/conf.d/hwclock:

[DirtyHairy]

I remember having a similar issue of "unable to access the hardware clock" which was actually completely unrelated to the hardware clock but instead the result of a screwed up /etc/adjtime. While I don't remember what exactly I did to resolve it (which was slightly more complex), removing the file should resolve the problem.

[Bashrc]

For some reason I was unable to make this work until I set rtc_cmos as a module (CONFIG_RTC_DRV_CMOS=m) instead of in-kernel (CONFIG_RTC_DRV_CMOS=y).

[Ottre]