View previous topic :: View next topic |
Author |
Message |
jeastman n00b
Joined: 02 Mar 2005 Posts: 52
|
Posted: Sun Jan 21, 2007 7:28 pm Post subject: Problem with /etc/init.d/clock on restart after install |
|
|
After my install with raid1 and LVM2 support I have a problem at reboot time. When the boot gets to the part where it says 'Setting system clock using the hardware clock [UTC] ...' i get a yellow asterisk with the message 'select() to /dev/rtc to wait for clock tick timed outselect() to /dev/rtc to wait for clock tick timed out'. Then I get a series of lines with red asterics that say ->
<red asteric> Failed to set system clock to hardware clock
<red asteric> Failed to start /etc/init.d/clock
<red asterisk> One or more critical startup scripts failed to start!
<red asteric> Please correct this, and reboot
Give root password fo rmaintenance
(or type Control-D to continue):
I've checked /etc/conf.d/clock and I see that CLOCK="UTC" and I've made sure to 'cp /usr/share/zoneinfo/US/Central /etc/localtime'. I'm stuck. Any help is greatly appreciated. Thanks in advance.
Jeastman |
|
Back to top |
|
|
didymos Advocate
Joined: 10 Oct 2005 Posts: 4798 Location: California
|
Posted: Sun Jan 21, 2007 9:53 pm Post subject: |
|
|
What happens if you login as root and do "/etc/init.d/clock start"? Same thing? _________________ Thomas S. Howard |
|
Back to top |
|
|
jeastman n00b
Joined: 02 Mar 2005 Posts: 52
|
Posted: Sun Jan 21, 2007 11:01 pm Post subject: if I login as root and do /etc/init.d/clock start I get .... |
|
|
Thomas:
Thanks for the reply. If I login as root and do /etc/init.d/clock start I get ->
<red asterisk> ERROR: cannot run clock until sysinit completes
<red asterisk> clock will be started in the boot runlevel
I took a look inside /dev and I can see /dev/rtc is there and is a link to misc/rtc. Also I've run a 'dmeg + grep -i clock' and I see ->
Time: tsc clocksource has been installed
Real Time Clock Driver v1.12ac
Many thanks for the help.
Jeastman |
|
Back to top |
|
|
jeastman n00b
Joined: 02 Mar 2005 Posts: 52
|
Posted: Mon Jan 22, 2007 3:35 pm Post subject: i got a thought .... |
|
|
Thomas:
I just had a light bulb of an idea ..... how about i take the clock script out of the startup and use ntp instead. Would that do the trick?
Jeastman |
|
Back to top |
|
|
didymos Advocate
Joined: 10 Oct 2005 Posts: 4798 Location: California
|
Posted: Mon Jan 22, 2007 8:04 pm Post subject: |
|
|
No, you should leave that in. ntp is intended for a different purpose, namely syncing the clock to some reference source. What do you have set in /etc/conf.d/clock? Besides the CLOCK="UTC", I mean.
Also, there's a workaround I found out about which you can try. Change CLOCK_OPTS to this:
Code: |
CLOCK_OPTS="--directisa"
|
It looks like this is a very common problem, on a bunch of distros. I've seen it attributed to BIOS updates, dual-core processors, et cetera. What rtc-related settings are you using in the kernel? Mainly, I'm curious about the HPET stuff under "Character Devices" and the "Provide RTC interrupt" under "Processor type and features", but obviously, if you're using the RTC Class stuff, that's relevant too. _________________ Thomas S. Howard |
|
Back to top |
|
|
jeastman n00b
Joined: 02 Mar 2005 Posts: 52
|
Posted: Tue Jan 23, 2007 1:25 am Post subject: |
|
|
I've made the 'CLOCK_OPTS="--directisa"' change and am rebooting now.
The options under Character Devices are ->
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_VT_CONSOLE=y
As well, anything with RTC in its name are ->
CONFIG_RTC=m
CONFIG_GEN_RTC=m
CONFIG_GEN_RTC_X=y
CONFIG_RTC_LIB=m
CONFIG_RTC_CLASS=m
CONFIG_RTC_INTF_SYSFS=m
CONFIG_RTC_INTF_PROC=m
CONFIG_RTC_INTF_DEV=m
CONFIG_RTC_DRV_M48T86=m |
|
Back to top |
|
|
didymos Advocate
Joined: 10 Oct 2005 Posts: 4798 Location: California
|
Posted: Tue Jan 23, 2007 3:39 am Post subject: |
|
|
So, are you loading genrtc, or just rtc? Also, I assume you built rtc-m48t86 for a reason, so is that getting loaded during bootup?. Oh, and when I mentioned character devices, I meant what HPET options, found in the character devices section, do you have in your config? You probably don't need to bother with the RTC class stuff, unless you have some special needs. Usually, I just build the standard rtc into the kernel, instead of as a module, but again, maybe you have special requirements that make it easier to have it as module instead. _________________ Thomas S. Howard |
|
Back to top |
|
|
jeastman n00b
Joined: 02 Mar 2005 Posts: 52
|
Posted: Tue Jan 23, 2007 4:47 am Post subject: Eureka!!! |
|
|
The CLOCK_OPTS="--directisa" option worked. When I noticed that my 4 port 10/100 NIC was not being recognized I rebuilt the kernel with the tulip drivers built in and promptly screwed up my RAID and LVM2 settings. As you might expect this caused the reboot to NOT perform as hoped. This is not a bad thing though because I can recover from this one ..... I hope ...... Many thanks for your help. Have a nice evening.
Jeastman |
|
Back to top |
|
|
ecce Tux's lil' helper
Joined: 22 Oct 2005 Posts: 92
|
Posted: Sat Feb 10, 2007 12:02 am Post subject: Cannot access the hardware clock! |
|
|
I'm trying to install gentoo on my C2D machine. I use the "small gentoo" live-CD that supports the JMicron controller that I need. Installation is done, and when I reboot for the first time and the system starts up it stops with this error message:
Code: |
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details... yadayada
* Failed to set system clock to hardware clock
* Failed to start /etc/init.d/clock
* One or more critical startup scripts failed to start!
Give root password for maintenance
(or type Control-D to continue): |
Help please! |
|
Back to top |
|
|
dkostic Apprentice
Joined: 24 May 2006 Posts: 220 Location: Madison, NJ
|
Posted: Sat Feb 10, 2007 12:27 am Post subject: |
|
|
I confess I've never heard of this happening. Is rc-update starting the clock at boot time? Can you chroot into the environment off the LiveCD and show me what
outputs? _________________ Toshiba Satellite A105 laptop, 1.7 mHz Celeron M, 100 Gb hard disk, 512 Mb RAM, 2006.0, 2.6.16-r7 kernel
Homemade desktop, 3.2+ mHz AMD Athlon 64 processor, 120 Gb hard disk, 1 Gb RAM, 2005.0, 2.6.14-r2 kernel |
|
Back to top |
|
|
black.gavin n00b
Joined: 10 Feb 2007 Posts: 3 Location: Washington D.C.
|
Posted: Sat Feb 10, 2007 2:15 am Post subject: |
|
|
This happens with some boards(VIA K8t800 is one I know of) and is actually a problem with RTC. My guess is that the rtc module is probably loading after it should be. Going into the kernel and compiling in rtc instead of having it as a module might work. You could just goto /usr/src/linux/.config and make sure that you have CONFIG_RTC=y uncommented and then recompile the kernel. That's all I can think of right now that might be possible. |
|
Back to top |
|
|
mudrii l33t
Joined: 26 Jun 2003 Posts: 789 Location: Singapore
|
Posted: Sat Feb 10, 2007 2:28 am Post subject: |
|
|
to access hw clock use
hwclock
and compare with
date _________________ www.gentoo.ro |
|
Back to top |
|
|
whiskas n00b
Joined: 11 Sep 2003 Posts: 58 Location: Bucharest, Romania
|
Posted: Sat Feb 10, 2007 9:56 am Post subject: |
|
|
Try to run hwclock --directisa (as root). If that works, add --directisa in /etc/conf.d/clock to CLOCK_OPTS and voilà, problem solved! |
|
Back to top |
|
|
nixnut Bodhisattva
Joined: 09 Apr 2004 Posts: 10974 Location: the dutch mountains
|
Posted: Sat Feb 10, 2007 10:01 am Post subject: |
|
|
merged above five posts 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 |
|
|
ecce Tux's lil' helper
Joined: 22 Oct 2005 Posts: 92
|
Posted: Sat Feb 10, 2007 2:06 pm Post subject: |
|
|
black.gavin: That was exactly what was wrong. I use ASUS P5B motherboard with iP965 chip, but anyway, now its fixed. Thanks a lot! |
|
Back to top |
|
|
pjv Guru
Joined: 02 Jul 2003 Posts: 353 Location: Belgium
|
Posted: Tue Jul 24, 2007 10:35 am Post subject: |
|
|
My same problem was solved with --directisa. I have CONFIG_RTC=y, but I was wondering which HPET options I should select, just to get things right? I have these (on a dualcore):
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y |
|
Back to top |
|
|
nixnut Bodhisattva
Joined: 09 Apr 2004 Posts: 10974 Location: the dutch mountains
|
Posted: Tue Jul 24, 2007 5:18 pm Post subject: |
|
|
Moved from Installing Gentoo to Other Things Gentoo.
Postinstallation problem, so moved 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 |
|
|
|