From owner-freebsd-ppc@FreeBSD.ORG Sun May 2 01:31:28 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3EC511065670 for ; Sun, 2 May 2010 01:31:28 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from mail.icecube.wisc.edu (trout.icecube.wisc.edu [128.104.255.119]) by mx1.freebsd.org (Postfix) with ESMTP id 167A08FC0C for ; Sun, 2 May 2010 01:31:27 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.icecube.wisc.edu (Postfix) with ESMTP id 23181582C0; Sat, 1 May 2010 20:31:27 -0500 (CDT) X-Virus-Scanned: amavisd-new at icecube.wisc.edu Received: from mail.icecube.wisc.edu ([127.0.0.1]) by localhost (trout.icecube.wisc.edu [127.0.0.1]) (amavisd-new, port 10030) with ESMTP id SXOKoLA-CHUZ; Sat, 1 May 2010 20:31:27 -0500 (CDT) Received: from wanderer.tachypleus.net (173-13-239-153-WashingtonDC.hfc.comcastbusiness.net [173.13.239.153]) by mail.icecube.wisc.edu (Postfix) with ESMTP id C22DA582BF; Sat, 1 May 2010 20:31:26 -0500 (CDT) Message-ID: <4BDCD5ED.3020606@freebsd.org> Date: Sat, 01 May 2010 21:31:25 -0400 From: Nathan Whitehorn User-Agent: Thunderbird 2.0.0.23 (X11/20100215) MIME-Version: 1.0 To: Super Biscuit References: <642407.28421.qm@web110101.mail.gq1.yahoo.com> In-Reply-To: <642407.28421.qm@web110101.mail.gq1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ppc@freebsd.org Subject: Re: Xorg and powerpc: tty switching causes unresponsive screen X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 May 2010 01:31:28 -0000 Super Biscuit wrote: > If this post to the mailing lists seems to be off topic, please do not allow it through. > > Has a fix or work around for the following been issued as of yet: > When switching vttyX after starting xsession causes unresponsive monitor- blank output. > Starting an xsession using a predefined path in .xinitrc or by adding a /usr/local/bin/path to /usr/local/bin/startx also results in unresponsive monitor. > This is an issue with the Rage 128 Open Firmware ROMs. If X exits, the FCode ROMs are seemingly not capable of fully restoring the state the way the Radeon and nVidia ones are. To fix this, you would need to spend a great deal of time understanding the quirks of the Rage 128 ROM, or to write a native framebuffer for it. In either case, you probably don't need to switch VTs that often. -Nathan