From owner-freebsd-questions Fri Mar 6 23:47:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07768 for freebsd-questions-outgoing; Fri, 6 Mar 1998 23:47:05 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07763 for ; Fri, 6 Mar 1998 23:47:01 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id BAA25450; Sat, 7 Mar 1998 01:46:34 -0600 (CST) From: Kevin Day Message-Id: <199803070746.BAA25450@home.dragondata.com> Subject: Re: Cyrix MediaGX support under X? In-Reply-To: <199803070737.CAA00489@dyson.iquest.net> from "John S. Dyson" at "Mar 7, 98 02:37:04 am" To: toor@dyson.iquest.net (John S. Dyson) Date: Sat, 7 Mar 1998 01:46:33 -0600 (CST) Cc: questions@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Kevin Day said: > > > > Has anyone been sucessful with getting a cyrix mediagx system to run X > > windows? I can switch modes, and X appears to be running fine, but the > > vertical sync is off by at least a factor of two.... > > > Be careful also about system memory allocation. I have had serious > problems with the region between 512K and 640K, and so you might > want to tell the system to avoid it. This gave me fits for about > 2wks. (This is indeed on a MediaGX system.) > I'll take a look at that... I'm about 2 hours into a buildworld, and haven't had any problems so far. The only other side effect I'm seeing is that the screensaver won't activate. I can't really understand it. :) Same hard drive, moved to an intel system, the screen saver runs fine. :) (tried both daemon and blank) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message