From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1N7Qu5-00087B-HH for garchives@archives.gentoo.org; Mon, 09 Nov 2009 09:51:18 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 84E6BE0A5F; Mon, 9 Nov 2009 09:51:16 +0000 (UTC) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by pigeon.gentoo.org (Postfix) with ESMTP id 4B312E0A5F for ; Mon, 9 Nov 2009 09:51:16 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id 19so760036fgg.10 for ; Mon, 09 Nov 2009 01:51:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=aWE1F0zG023PRylKcaQr+p+VmkEH4kS8dwUZTfhKNEc=; b=kE2fKPPotYgKFKJ9dgVycsJLNmO3fe+PZHiNt/9bNjnrgCyO12aJBOplR9/0Omvq3l 02vewP/KNeeDiqqUtB3VZINWIKOksP2NoFC7tVadWCVhBNTt0FNWaz+DdXUjFmB/1qww AkUA1c5OYDQts1J6BwNB/J/eC64REQoPlsPCM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id; b=U/ao07LpIamQxWuD+RsHvjbRUXYXvRMPO70HW2fIHJVS+GDEfYCiNJQjZsam8OZShE vlhrPuD4GYf6AOU55l2L5P34srtjWVPkgjn5o7JihJVGz/3dzGEFXTVk06UrVLrp08FK xJ8IKTb9SXsxNZizl7tcfdr2lu66awYeW55pE= Received: by 10.86.198.12 with SMTP id v12mr5991963fgf.17.1257760275733; Mon, 09 Nov 2009 01:51:15 -0800 (PST) Received: from nazgul.localnet (dustpuppy.is.co.za [196.14.169.11]) by mx.google.com with ESMTPS id e3sm6541496fga.8.2009.11.09.01.51.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 09 Nov 2009 01:51:15 -0800 (PST) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] strange dmesg output - RESOLVED Date: Mon, 9 Nov 2009 11:50:15 +0200 User-Agent: KMail/1.12.90 (Linux/2.6.31-zen6; KDE/4.3.73; x86_64; ; ) References: <200910280655.42546.michaelkintzios@gmail.com> <4AF7DBC3.3000100@oversi.com> In-Reply-To: <4AF7DBC3.3000100@oversi.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="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200911091150.15525.alan.mckinnon@gmail.com> X-Archives-Salt: bc504125-af6d-4c72-8c23-e97a675963f9 X-Archives-Hash: 35b96452994bf65ba57bfdc95ebee444 On Monday 09 November 2009 11:07:15 Amit Dor-Shifer wrote: > On Wednesday 28 October 2009 20:10:52 Maxim Wexler wrote: > > > Not sure this is related with the OP's problem, I have noticed that > > on my > > > > system I can scroll up in a console if it displays the output of a > > > command, e.g. ls, but I cannot scroll up on the boot messages. Also, I > > > cannot scroll up on the log messages on VT12. Is there something that > > > I need to set up in the kernel? In the old days (perhaps different > > > machine?) I used to be able to > > > scroll up in both. > > > > Also note, if you migrate away from the boot console and then come > > back, it may not scrollback at all. If I want to see what boot is > > doing I scroll back immediately before running startx or moving to > > another console. > > Maxim (or anyone else): > do you know what causes scrollback to be disabled once you move to a > different terminal? > Amit > The scrollback buffer is global, not per-VT So when you change VT, the buffer must go away other wise you have wrong text on the wrong terminal. -- alan dot mckinnon at gmail dot com