Quote:
|
InK says: I can run X, but y can't set the resolution to 1024x768... and of course I have that res configured in XF86config-4
|
Well, if you're feeling lucky, you can try
# dexconf, one of the many evil children of
debconf. And if you ever find intelligible documentation on any of this Debconf Axis of Evil, drop a link around here someplace. If you accidentally on purpose told Debconf that you wanted it to manage your X config, anything you put in XF86config-4 is as likely as not to get stomped by Debconf's hobnail boots.
If dexconf (which I thought for a long time was a typo of debconf ) doesn't work, and your XF86config is managed by debconf (which is ultimately a Good Thing, or is the Debian Way, at least ), you'll have to go find the (fairly dreadful) docs, buried deep in /usr/share/doc/xfree86-common, untar the FAQ.gz, find the question: How do I add custom sections to a dexconf-generated XF86Config-4 file? Search waaaaay down to the answer, which is: Add it
before the ###BEGIN DEBCONF-CONTROLLED... something-or-other line.
THEN! Make custom Monitor and Screen sections up there, probably by cutting and pasting and giving these "real" configs some new names. Also, snoop around the web (Google is our friend) for the XF86Config of someone with a similar video card and monitor who claims to have it working and plagiarize that.
The trick is that the first Monitor and Screen are the default, so the bogus dexconf ones just consume some memory.
And, if that doesn't work, look at X's log file and see if it complains about something. If you don't understand the error message (they are every bit as clear as the docs
), put quotes around it and stick it in Google (or come back here and ask, but Google works pretty well).
And remember - tell us how it turns out, won't you?
Is that clear as mud? Or what?
Well, HTH,
Ab.
p.s. - Hey, Mods! How about a <CODE> button?
