On Tue, 2002-04-30 at 12:15, Mike Meyer wrote: > In <[EMAIL PROTECTED]>, Andrew Reilly ><[EMAIL PROTECTED]> typed: > > On Sun, 2002-04-28 at 11:17, Bruce A. Mah wrote: > > > > > > If you actually do run into problems with the way the XFree86 4.2.0 got > > > integrated, give a holler. > > First biggie: the build doesn't seem to have the interactive business > > anymore. That would be well and good, if it worked properly. I don't > > know what happened, but portupgrade removed up my old XFree864.1 > > installation, including all of my config files in /etc/X11, and then the > > new version didn't install a new set. Aargh. I had to dig an old copy > > of /etc/X11 off a backup CD I'd made earlier. I still don't know what > > magic was really required to make the port install the config files. > > Everything but /etc/XF86Config moved to /usr/X11R6/lib/X11. Everything > "just worked" for me after the upgrade, without having to install > anything in /etc/X11.
Thanks for the pointer. Seems that the server is also happy to find XF68Config in /usr/X11R6/lib/X11 (there are some examples there too), so I have blown /etc/X11 away altogether. Not sure how good an idea that is: might make my backups more complicated... > > Second biggie: I have a Matrox MGA G200 video card that was well > > supported in earlier releases. The new release doesn't work at all if > > compiled without the WITH_MATROX_GXX_DRIVER=yes flag in make.conf. The > > server whinges that it can't find MGA_HAL_something.so.foo. So, > > re-compiling with the flag set builds a server that runs, but that (my > > guess) hangs the PCI bus. The screen goes black, a few seconds pass in > > which no input of any sort works, and then the system does a hard > > reboot. > > Sorry, but I can't help with that one. I tried the suggestion in another thread (Option "composite_sync" "Off"), but that did not seem to change anything. I still have it in, since it doesn't seem to be hurting Driver "vesa" performance.... -- Andrew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
