Re: XFree86 4.0.2

2001-01-22 Thread Karel J. Bosschaart

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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: XFree86 4.0.2

2001-01-21 Thread Kris Kennaway

On Sun, Jan 21, 2001 at 01:51:05AM -0600, David Syphers wrote:

 the binaries from a directory labeled "FreeBSD 5.x".  So I tried the ports, 
 and it built fine for a long time, and then after about 35300 lines of 
 output to the screen, ran into
 
 make: don't know how to make ../../../fonts/encodings/encodings.dir. Stop
 *** Error code 2
 
 Stop in /usr/ports/x11/XFree86-4/work/xc/fonts/bdf.

The port should be working, but since it's not for you, just add the package.

pkg_add -r XFree86

Kris

--
NOTE: To fetch an updated copy of my GPG key which has not expired,
finger [EMAIL PROTECTED]

 PGP signature


Re: XFree86 4.0.2

2001-01-21 Thread Chris

Kris Kennaway wrote:
 
 On Sun, Jan 21, 2001 at 01:51:05AM -0600, David Syphers wrote:
 
  the binaries from a directory labeled "FreeBSD 5.x".  So I tried the ports,
  and it built fine for a long time, and then after about 35300 lines of
  output to the screen, ran into
 
  make: don't know how to make ../../../fonts/encodings/encodings.dir. Stop
  *** Error code 2
 
  Stop in /usr/ports/x11/XFree86-4/work/xc/fonts/bdf.
 
 The port should be working, but since it's not for you, just add the package.
 
 pkg_add -r XFree86

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.  It won't insert the module until you update this--so it appears
that no one is actually using it.

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.

There were also a handful of other things, that I don't recall offhand now.
These problems were observed on a 4.2-STABLE box, not too long ago.  I have
compiled the source from scratch (with and without matrox DRM stuff), as
well
as using the stock 4.0.2_5 package, both of which behave the same.

Chris


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message