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 79F47138522 for ; Thu, 17 Jan 2013 22:39:56 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 344A121C062; Thu, 17 Jan 2013 22:39:41 +0000 (UTC) Received: from mail-wg0-f42.google.com (mail-wg0-f42.google.com [74.125.82.42]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7D22421C03D for ; Thu, 17 Jan 2013 22:39:39 +0000 (UTC) Received: by mail-wg0-f42.google.com with SMTP id dr1so91786wgb.1 for ; Thu, 17 Jan 2013 14:39:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:subject:message-id:in-reply-to:references :organization:x-mailer:mime-version:content-type :content-transfer-encoding; bh=ZJX7sG8dtohCWvkFYoMQQ/3Q6EcwBex2x4VUZQOt3Ew=; b=OvjD3D+D2xrY1Ky6cwBiIP+QrmO3yCgUvirAAl/kza4uXkGWT7A2CyQL5QBMvhld00 XQQ7CfvQgKviA/X79rKPH0ig2TvjPMp4fpVL+1oPBt7kh9QWLYll9SeGr5Hjm1jgmr+f x2gvgADOxdBRWQvjg7RYRsU8aAoxMkIGAWr5IXcG5O7qI/pcf0dEukGTy4079Eotbht2 m8TOwbMkM39PuYuI7/HcAUXfbinRJS417fXbK295mKDdzFGNEbr6qLkddnptc8oVJ2WC /6uugIEXisCAtHqFpnFUKChSMbH1+jzuc7ejyDlD3TXW8968jXCZ4gJZt5EidutKnJsm lpNw== X-Received: by 10.180.85.103 with SMTP id g7mr500708wiz.29.1358462378184; Thu, 17 Jan 2013 14:39:38 -0800 (PST) Received: from khamul.example.com (196-209-242-12.dynamic.isadsl.co.za. [196.209.242.12]) by mx.google.com with ESMTPS id t17sm775937wiv.6.2013.01.17.14.39.35 (version=SSLv3 cipher=RC4-SHA bits=128/128); Thu, 17 Jan 2013 14:39:37 -0800 (PST) Date: Fri, 18 Jan 2013 00:39:15 +0200 From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: System won't boot if CMOS clock is slow Message-ID: <20130118003915.134f0639@khamul.example.com> In-Reply-To: <20130117204513.GN2656@server> References: <20130116175249.GE2656@server> <20130116225248.34e1e06a@khamul.example.com> <20130117204513.GN2656@server> Organization: Internet Solutions X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.14; x86_64-pc-linux-gnu) 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-Transfer-Encoding: 7bit X-Archives-Salt: b8d2287e-407c-42ee-951f-fed56bf91b00 X-Archives-Hash: c251a53299e9b21b91adbdace724692e On Thu, 17 Jan 2013 14:45:13 -0600 Bruce Hill wrote: > 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? I've never seen KMS clear the screen there for either nvidia or radeon cards so I doubt it's that. All it does at that point that is visible to the user is set the resolution and paint on the $GO_FAST stripes. Now fbcondecor, that's a likely area to look in. I personally no longer use fancy fb and boot splash type things (I like my Alt-F1 console to look like a console and not get in my way) so I doubt I can be of much help further on this. -- Alan McKinnon alan.mckinnon@gmail.com