From owner-freebsd-current Mon Jan 22 2:26: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from wop21.wop.wtb.tue.nl (wop21.wop.wtb.tue.nl [131.155.56.216]) by hub.freebsd.org (Postfix) with ESMTP id F23FD37B400 for ; Mon, 22 Jan 2001 02:25:43 -0800 (PST) Received: (from karelj@localhost) by wop21.wop.wtb.tue.nl (8.11.1/8.11.1) id f0MAP4577825; Mon, 22 Jan 2001 11:25:04 +0100 (CET) (envelope-from karelj) Date: Mon, 22 Jan 2001 11:22:45 +0100 From: "Karel J. Bosschaart" To: Chris Cc: David Syphers , current@FreeBSD.ORG Subject: Re: XFree86 4.0.2 Message-ID: <20010122112245.A77620@wop21.wop.wtb.tue.nl> Reply-To: K.J.Bosschaart@wtb.tue.nl References: <4.3.2.7.2.20010121013438.00ba9100@nsit-popmail.uchicago.edu> <20010121023208.A63679@citusc17.usc.edu> <3A6B3D84.58831A5@137.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3A6B3D84.58831A5@137.org>; from cc@137.org on Sun, Jan 21, 2001 at 01:50:28PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 21, 2001 at 01:50:28PM -0600, Chris wrote: > > If you are currently running 4.0.1, I would seriously recommend skipping > this > minor revision. I have run into a multitude of problems with it, and am now > back right where I started. > > One, is the lack of DRM support for the matrox cards anymore. The kernel > module has a version number in it, which is less than that required by the > DRM system. > At the moment I'm using XFree86-4.0.2_5 with Matrox G400 and DRM, on 4.2-STABLE. I could get the correct DRM module version compiled thanks to a bunch of patches that someone has sent me. Occasionally things lock up and I need to restart remotely (killing -9 the offending process does not help). This happens only when using drm. > It won't insert the module until you update this--so it appears > that no one is actually using it. FYI, http://wop21.wop.wtb.tue.nl/freebsd/hwaccel.html describes how to install drm/G400 with XFree86-4.0.1. I'm getting a few hits a day, so I suppose there is some interest, although the patches are getting only 20 % of the number of hits on the guidelines, which might be more indicative for the people actually trying. > Another, is that there seem to be delays in the event stream, making > interactive performance terrible. One example: When I go to move a window, > I > start dragging it, moving the outline as I go. Then I unclick, yet the > frame > is still visible. I actually have to move the mouse more to get the window > move to take effect. There are other cases, where it appears to lose events > all together--like clicking on windows to raise them, or with menus. > Hmm, I don't have such troubles. Only minor problem I have, besides above mentioned drm related things, is that VMware doesn't correctly use Full Screen mode. Karel. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message