From owner-freebsd-x11@FreeBSD.ORG Thu Mar 29 01:03:31 2007 Return-Path: X-Original-To: x11@freebsd.org Delivered-To: freebsd-x11@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8521B16A400 for ; Thu, 29 Mar 2007 01:03:31 +0000 (UTC) (envelope-from Kristen.Glynn@virginblue.com.au) Received: from mail62.messagelabs.com (mail62.messagelabs.com [203.166.119.147]) by mx1.freebsd.org (Postfix) with SMTP id EAF7913C44C for ; Thu, 29 Mar 2007 01:03:30 +0000 (UTC) (envelope-from Kristen.Glynn@virginblue.com.au) X-VirusChecked: Checked X-Env-Sender: Kristen.Glynn@virginblue.com.au X-Msg-Ref: server-12.tower-62.messagelabs.com!1175130209!18627108!1 X-StarScan-Version: 5.5.10.7.1; banners=-,-,- X-Originating-IP: [203.202.21.160] Received: (qmail 30224 invoked from network); 29 Mar 2007 01:03:29 -0000 Received: from mail.virginblue.com.au (HELO mail.virginblue.com.au) (203.202.21.160) by server-12.tower-62.messagelabs.com with SMTP; 29 Mar 2007 01:03:29 -0000 Received: from ISKCMX01.virginblue.internal ([192.168.60.71]) by VIRBQHOCMX1.virginblue.internal with Microsoft SMTPSVC(6.0.3790.1830); Thu, 29 Mar 2007 11:04:29 +1000 X-MessageTextProcessor: DisclaimIt (2.50.252) [Virgin Blue Airlines Pty Limited, AU] Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Thu, 29 Mar 2007 11:04:29 +1000 Message-ID: <7C3101310BBC894E8A0D5FB2C36B958934574C@ISKCMX01.virginblue.internal> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Is Vodoo3 supposed to work and have DRI? thread-index: Acdxmtuxm3LOSHTpTtGCkT7NFsy2HwAAv/yg From: "Kris Glynn" Importance: normal Priority: normal To: "Mikhail Teterin" , "Erik Trulsson" X-OriginalArrivalTime: 29 Mar 2007 01:04:29.0360 (UTC) FILETIME=[33F1BB00:01C7719E] Cc: Vince , x11@freebsd.org Subject: RE: Is Vodoo3 supposed to work and have DRI? X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Mar 2007 01:03:31 -0000 This is true.. Finally got beryl working last night by removing my = Geforce 256 (as the nvidia-driver-7184 port does not build on 7.0 = current.) and installing an old Geforce4 MX440 64mb. I was quite surprised how well the old Geforce4 functioned with Beryl = and all the desktop effects. Very cool. Kris=20 -----Original Message----- From: Mikhail Teterin [mailto:mi+kde@aldan.algebra.com]=20 Sent: Thursday, 29 March 2007 10:39 AM To: Erik Trulsson Cc: Vince; Kris Glynn; x11@freebsd.org Subject: Re: Is Vodoo3 supposed to work and have DRI? On Tuesday 20 March 2007 16:58, Erik Trulsson wrote: =3D I.e. 'device tdfx' seems to be for Voodoo II cards. =3D For Voodoo 3/4/5 you would want =3D device drm =3D device tdfxdrm Yes, indeed. This worked! The X-servers comes up, and even glxgears seem = to spin at decent speed. However, at random points after much work, such as moving a window "too = much"=20 or scrolling through "too much" textual output in an xterm, the X-server = hangs. In top(1) it looks like: PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU = COMMAND 720 mi 1 130 0 80016K 6792K RUN 22.2H 97.56% Xorg Killing it works (but only with -9) leaving the screen black. Trying to = start a new session after this (logging in remotely) hangs the whole = machine... The box is a single Pentium3 @450MHz... Any ideas? -mi P.S. I must admit, with sadness, that the only case of properly and = quickly working OpenGL, that I ever saw on FreeBSD, was with NVidia's = own driver... OAG Best Low Cost Airline Of The Year=20 The content of this e-mail, including any attachments, is a confidential = communication between Virgin Blue, Pacific Blue or a related entity (or = the sender if this email is a private communication) and the intended = addressee and is for the sole use of that intended addressee. If you are = not the intended addressee, any use, interference with, disclosure or = copying of this material is unauthorized and prohibited. If you have = received this e-mail in error please contact the sender immediately and = then delete the message and any attachment(s). There is no warranty that = this email is error, virus or defect free. This email is also subject to = copyright. No part of it should be reproduced, adapted or communicated = without the written consent of the copyright owner. If this is a private = communication it does not represent the views of Virgin Blue, Pacific = Blue or their related entities. Please be aware that the contents of any = emails sent to or from Virgin Blue, Pacific Blue or their related = entities may be periodically monitored and reviewed. Virgin Blue, = Pacific Blue and their related entities respect your privacy. Our = privacy policy can be accessed from our website: www.virginblue.com.au