Whew, small panic moment. It quit booting, so I restored to a live CD and restored the old xorg.conf file. Seems OK now, but multi monitor still doing weird stuff, so advice is still well appreciated <img src="cid:330@goomoji.gmail" style="margin-top: 0px; margin-right: 0.2ex; margin-bottom: 0px; margin-left: 0.2ex; vertical-align: middle; " goomoji="330"><div>
<br></div><div>In the meantime, I think I'm going to run a backup - just in case.</div><div><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Mike Bean</b> <span dir="ltr"><<a href="mailto:beandaemon@gmail.com">beandaemon@gmail.com</a>></span><br>
Date: Thu, Sep 22, 2011 at 8:01 PM<br>Subject: need Xorg advice (unable to multi-monitor)<br>To: CLUE talk <<a href="mailto:clue-talk@cluedenver.org">clue-talk@cluedenver.org</a>><br><br><br>Hi guys,<br><br>I've been kinda breaking my brain on this one for a while, think maybe it's time I admit I'm in over my head and ask for help. My computer/laptop is running Mint11 "Katya".<br>
For the most part, it's fine. Tried to plug a multi-monitor, 2nd monitor in.<br>
<br>It detects the monitor, and runs with clone image/same image on both monitors, but when I try to separate the monitors, I get an error saying basically that the specified geometry is greater then the available space. I've been trying to figure this out on my own, here's the deal:<br>
<br>1) I burned a live CD, and booted to it, and I can run multi-monitor just fine (separate images on both monitors)<br>2) I go to one of the virtual terminals, stop gdm, and run X-configure, and I get an error that says "number of created screens does not match number of detected devices"<br>
<br>When I began this whole process my xorg.conf was surprisingly sparse, it just had one monitor in it, but everything seemed OK, so I didn't think too much about it.<br><br>1) I did some reading and found some people on the web with driver issues and the like, the vesa driver for example, and running aticonfigure --initial helped.<br>
They would remove the vesa driver completely, rerun aticonfigure, and restart X.<br><br>I'm kind of the careful type, so I haven't nuked the vesa driver completely, and I've been just renaming my old xorg files to xorg.old, but similar measures so far haven't helped. <br>
(I'm currently typing this while booted from a live CD)<br><br>So that's more or less where I'm at. Kind of stumped, wanted to ask around, any advice is welcome.<br><font color="#888888"><br>Bean<br><br><br>
</font></div><br></div>