<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<blockquote cite="mid:495D2A55.3090200@soulkiln.org" type="cite">Which
brings up another question, perhaps worthy of a separate thread: Is it
just me, or is X.org really badly broken lately? I'm reading what seems
like a rapid rise in complaints about stuff directly related to X.org
on lots of forums. Debian's devs say it's not working properly, and
they simply cannot script the X server setup as they had in the past.
When I run X configure utility directly, it's leaving out a *lot* of
stuff it used to write automatically. There are other complaints about
breaking configs carried over from the previous version. I noticed the
nv driver will no longer support what my chipset and monitor can do,
without significant artifacts.
<br>
</blockquote>
I don't know. I'm running the latest Linux Mint, and it found my
nVidia card which requires the older proprietary driver set perfectly,
installed the drivers (Ubuntu failed to do this last time), and
worked. Then I rebooted, and the X server had defaulted to a refresh
rate invalid for my Planar LCD. I rebooted again, into fallback, and
it came up correctly. Rebooted again normally, and all is now well. I
didn't touch a single configuration item. The sound system has been a
significantly larger miracle; I have sound on motherboard, on SB2 PCI
card, and USB speakers, and they're all working, again without editing
a single text file or a single command-line operation.<br>
<br>
As result of the above, I suspect that the Mint people understand the
newer X.org behavior more than most. I have heard that X.org is moving
deliberately into auto-configuration territory, and away from
traditional Unix don't-you-dare-do-anything-automatic religion, so
maybe what we are seeing is most distros just not ready to play ball.<br>
<br>
J.E.B.<br>
<br>
<br>
</body>
</html>