On Sun, Mar 27, 2005 at 08:50:08PM -0800, Jim Osborn wrote: >On Sun, Mar 27, 2005 at 12:37:19PM -0500, David Dawes wrote: >> I don't know what the state of the mga HAL module is. We should >> change the default to not load it if it no longer works. > >The latest HALlib on the Matrox site seems to be for X-4.3.0. I >assume the mismatch between 4.3.0 and 4.5.0 is what causes the >unresolved symbol error; I couldn't tell from the docs I read if >there was an easy way to resolve the problem, compile a new mga_drv.o >somehow, without building the X-4.5.0 installation from source, or >somesuch. Or even if that would work, if using the HALlib means you're >stuck at 4.3.0 until Matrox builds a new module. So I'll just hope >I don't need it; I'd rather use X-4.5.0. :) I tracked down the relevant change, and apparently it was to adjust for a change in the 17 July 2003 version of the HAL interface in mgadrivers-3.0-src.tgz from Matrox, where the function HALSetDisplayStart had a name change, to MGASetDisplayStart. The mga driver could be modified to handle both cases at runtime. >> The recognition of an EDID preferred mode is new for 4.5.0, and the >> options related to it are documented in the XF86Config(5) man page. > >Indeed they are, once I purged the old 4.1 XF86Config(5) manpage >from the cache! A real cautionary tale there... :) > > >> The way that it is used needs some refinement. Can you run XFree86 >> with the '-logverbose 4' option and send me the log file? > >Attached. I ran it without the "UsePreferredMode" "no" option, on >the theory that's what would be most useful to you; if you'd like >another go, let me know. That's fine -- thanks. >> >What do I need to do to get 1280x1024 with X-4.x? >> >> If you add the following line to your Monitor section, the preferred mode >> should be ignored, and you should be able to get 1280x1024 to work again: >> >> Option "UsePreferredMode" "no" > >And I'm up and running at 1280x1024! Thanks very much for the info. You're welcome. Thanks for the feedback. >Now if I can figure out how to get some fonts back in my KDE 2.2.1 >Konsole (xterm)... I've peeked at the .../X11/fonts dirs, and run >fc-cache, per the README.fonts, and run the KDE font-installer, but >still can't get a visible font to work with. > >For some reason, I *can* get a usable xterm in my wife's screen, so >I'm typing away there now, having su'd to my account from there. At >least that lets me continue running 4.5.0 while I proceed with debugging. >I can't see an obvious difference between her KDE config and mine, >so I suspect it's dumb luck that hers works at all. Maybe after I've >made it through all the font-related man pages I'll have more questions. A regular 'xterm' should work, at least. I haven't seen this type of problem in my 4.5.0 test installs, but I did run into a different problem a little while back (very slow application startup) that was resolved by runing 'fc-cache' as root. David _______________________________________________ XFree86 mailing list XFree86@xxxxxxxxxxx http://XFree86.Org/mailman/listinfo/xfree86
