From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LTP6P-0000CR-O7 for garchives@archives.gentoo.org; Sat, 31 Jan 2009 23:18:18 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7122BE0367; Sat, 31 Jan 2009 23:18:16 +0000 (UTC) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.169]) by pigeon.gentoo.org (Postfix) with ESMTP id 3549EE0367 for ; Sat, 31 Jan 2009 23:18:16 +0000 (UTC) Received: by wf-out-1314.google.com with SMTP id 29so990798wff.10 for ; Sat, 31 Jan 2009 15:18:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=2D8ijvNeKshE9drJEP8q6hhEh+zLeZ/8l9nDaXzw0MQ=; b=LeTrPElpqRlGyW42nuAc2V6v0sMM37AfUm0D3eV3k1WVWsmO3AxByx9pHKJXWAe0QY oJQn34EMkK1+ARolRpQjVMJRujJJj+ZiOimEORsZujirxJVsRfhk2Rhts94HnHuZ6dSl oslHpukUlDsJ1l2Pl4wG4QP0j+ddoNqyY6m5U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=TwzyF21f9uZNXDndsfJ6JR6qPiIbzay8YwY3y9sqri0AOpwkGlMoypIebh332c+LZP O39LUCQvKBXsT6WxEOnawbLvDdQmdUps3BGWSx3xbD9im8ms88a1GiwmZOYG4aMkqIzg Bten5jLNGaxVElHEauVuuR+xH70gT/O0Xduig= Received: by 10.143.1.12 with SMTP id d12mr1132531wfi.203.1233443895778; Sat, 31 Jan 2009 15:18:15 -0800 (PST) Received: from ?4.231.2.26? (dialup-4.231.2.26.Dial1.Houston1.Level3.net [4.231.2.26]) by mx.google.com with ESMTPS id 30sm3703685wfa.41.2009.01.31.15.17.54 (version=SSLv3 cipher=RC4-MD5); Sat, 31 Jan 2009 15:18:15 -0800 (PST) Message-ID: <4984DC00.5020707@gmail.com> Date: Sat, 31 Jan 2009 17:17:20 -0600 From: Dale User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.19) Gecko/20081227 SeaMonkey/1.1.14 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] /dev/rtc => rtc0 References: <5bdc1c8b0901311426t39d7d4bew31ec96c258c2a952@mail.gmail.com> <4984D42E.5090306@gmail.com> <5bdc1c8b0901311456o20343755kbf514641f12a8ed8@mail.gmail.com> In-Reply-To: <5bdc1c8b0901311456o20343755kbf514641f12a8ed8@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 4a2fb361-1ec8-4920-9a0c-3a054fa10fdd X-Archives-Hash: fbed1fdbe84f1904533b8f16b5908f2b Mark Knecht wrote: > On Sat, Jan 31, 2009 at 2:43 PM, Dale wrote: > >> Mark Knecht wrote: >> >>> Hi, >>> I know nothing of this part of the Linux boot process. If it's >>> *fairly* simple can someone point me at the right stuff to understand >>> how Gentoo creates a link from /dev/rtc to rtc0? When in the boot >>> process does this link become valid? >>> >>> Is it something that's held in a file and recreated from that file >>> on each boot? Is it created automagically by Gentoo Angels that look >>> after my well being but seldom reveal themselves? Is it created by the >>> kernel itself when something is specifically configured to do so? >>> Something else? >>> >>> Thanks, >>> Mark >>> >>> lightning src # uname -a >>> Linux lightning 2.6.27-gentoo-r8 #6 Fri Jan 30 18:55:56 PST 2009 >>> x86_64 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux >>> lightning src # ls -al /dev/rtc* >>> lrwxrwxrwx 1 root root 4 2009-01-30 10:58 /dev/rtc -> rtc0 >>> crw-r--r-- 1 root root 254, 0 2009-01-30 10:58 /dev/rtc0 >>> lightning src # >>> >>> >>> >>> >> From my understanding udev creates all the "stuff" in /dev. You can >> change the rules that it uses to make them tho. I think there is >> documentation on gentoo.org to help with that. So far, mine has worked >> well enough. Lucky I guess. >> >> That help? >> >> Dale >> > > Hi Dale, > While poking around in a bunch of different kernel config files - > some gentoo-sources - some not - I found there is an option in > > Device Drivers -> RTC > > that ONLY shows up when you tell the kernel to build the support in. > (I.e. - not off or modular) The option says > > <*> Set system time from RTC on startup or resume > (rtc0) RTC used to set the system time > > So, it appears it's a kernel oriented thing which allows it to get set > very early in the boot process. My problem on a kernel I built > yesterday was "File has a date in the future" sort of messages. I had > this set as modular so it couldn't load that early. The other problem > was that since it was a module and apparently I didn't load that > module the command hwclock -r failed. > > I've reconfigured the kernel and will build it and test after I get > finished with an emerge -e world later today. > > Thanks for the response. Hope this info helps someone else in the > future. (and me after the reboot!) ;-) > > Cheers, > Mark > > > My CMOS time chip sucks on this mobo. Everything else rocks but that stupid clock and yes I have checked the battery. Anyway, I get that error all the time. If I just reboot it does all right but if I do a shutdown, that error pops up. Sometimes it may only be a few seconds off, sometimes several hours to a day. I have never had it hurt anything here tho. It just warns you I guess. Dale :-) :-)