From owner-freebsd-alpha Sat Apr 7 16:30:45 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 2015837B423; Sat, 7 Apr 2001 16:30:42 -0700 (PDT) (envelope-from naddy@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 14m2A8-0004hN-00; Sun, 8 Apr 2001 01:30:36 +0200 Received: (from naddy@localhost) by kemoauc.mips.inka.de (8.11.3/8.11.1) id f37NKMd61139; Sun, 8 Apr 2001 01:20:22 +0200 (CEST) (envelope-from naddy) Date: Sun, 8 Apr 2001 01:20:22 +0200 From: Christian Weisgerber To: freebsd-alpha@freebsd.org Cc: jmz@FreeBSD.org Subject: XFree86-4 on alpha Message-ID: <20010408012022.A60088@kemoauc.mips.inka.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (Cc to the maintainer of our XFree86-4 port.) After an aborted attempt in the days of 4.0.1, I finally decided to switch to XFree86 4.0.3 on my box (PC164, Matrox Mystique, 5.0-CURRENT). Short summary of my results: - The x11/XFree86-4 ports builds fine. - xdm still dumps core when queried by an X display. This means you cannot use an alpha to manage X terminals, i.e. you cannot log into an alpha from an X display. (Depending on individual work habits that ranges from "huh?" to very bad.) - The mga driver occasionally produces garbage on the display and, what's much worse, hangs completely. You can SIGKILL it, but that leaves the console in an unusable state. My current stopgap solution is to run the solid XF86_SVGA server from 3.3.6 along with the rest of XFree86 4.0.3. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message