From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id B904213851E for ; Thu, 17 Jan 2013 20:45:27 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 928CD21C0DE; Thu, 17 Jan 2013 20:45:18 +0000 (UTC) Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id CF43121C029 for ; Thu, 17 Jan 2013 20:45:16 +0000 (UTC) Received: from localhost (66-208-231-133.ubr01a.rte20201.pa.hfc.comcastbusiness.net [66.208.231.133]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0LmrI4-1THPRm1iGK-00hU2Y; Thu, 17 Jan 2013 15:45:15 -0500 Date: Thu, 17 Jan 2013 14:45:13 -0600 From: Bruce Hill To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: System won't boot if CMOS clock is slow Message-ID: <20130117204513.GN2656@server> References: <20130116175249.GE2656@server> <20130116225248.34e1e06a@khamul.example.com> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Provags-ID: V02:K0:WDHkIE78r6MOA3FdLTQb8HinnbZOBirobMUbWQrEKXD xf8uGhgcwkh2YQurLakV479eJJxX7t33Dsji3NuqOiw02MWJxT LZD0pOSfyMWBAxs5CFA87ZEYux3ICE1QAuHGCQjrynB51H81y8 69/r5o29FR7HKHdsqxuZxVIilXdKRgZ+kRQv0ogNUEgyMA5Ggn q3ONkSep4i0Kbnzj+HSLA/4xeRHCa/A0xlyVgQI4+T0mglrrTv vWqRzwxOQz9hcWl3pykFBb0TIYJccHqrFe1XfnQCL+ktWwwMz4 d0D2BOcrdSVIqzBRMGTj2T2PW5E5X3llJ0RLfg86s5whTu9xay +/ojuP+ZCiAxpz9r74ko= X-Archives-Salt: 1c337686-6775-4ff1-a326-8f9b65616d09 X-Archives-Hash: fe4289ae260a93b5dac44c7570c5beb8 On Thu, Jan 17, 2013 at 02:35:50PM -0600, Paul Hartman wrote: > > I already had that set. :) I'm not talking about clearing the screen > at the login prompt; it clears mid-OpenRC during/after the udev step > (as Grant also described), though in my case it does not halt but > continues printing the rest of the OpenRC messages and eventually gets > to the login prompt. I'm thinking it may be fbcondecor responsible for > the blanking there. I'll need to experiment more with it. When KMS kicks in? -- Happy Penguin Computers >') 126 Fenco Drive ( \ Tupelo, MS 38801 ^^ support@happypenguincomputers.com 662-269-2706 662-205-6424 http://happypenguincomputers.com/ Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting