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.
I track ports pretty regularly, which is sometimes good, sometimes bad... Since I'd had no problems with XFree864.0 and 4.1, when 4.2 rolled around in the ports, I built'em as usual (with portupgrade, of course). Not a good idea, in my case. 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. 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. So I'm running 4.2 with the vesa driver instead of the mga driver. It works, but it's slow. Weeks have gone by and I haven't seen any other cries for help, so I guess I've done something dumb. X is big, though, and I don't have sufficient spare time to try randomly tweaking config knobs and re-building. I'll re-build and try again the next time there's a port version bump, of course. Portupgrade will see to that. Anyone have a clue about this? -- Andrew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
