On Jan 24, 2008 2:10 PM, David C. Rankin <[EMAIL PROTECTED]> wrote: > Mates, > > This is one of the things that is driving my crazy. I have 2 boxes > that > have identical Acer 2216W displays. Both had previously run SuSE 10.0 > and the Yast Monitor database had the exact display "Acer 2216W" that > yast would automatically choose and properly setup under sax2. > > First machine updated December time frame, yast had and properly > selected the "Acer 2216W" for the 10.3 install. This Monday I had to > update the other machine and Yast now selected the Vesa --> 1280x1024 > monitor. I thought, "no problem, I'll just select the right one." > WRONGO! The "Acer 2216W" monitor is nowhere to be found in this install. > WTF? These two installs are all from the same .iso? How could that be? > > Is there or was there some monitor database update that should have > been utilized in this install that wasn't? If so, where do I get it? Has > anyone else seen such random nonsense on the installs they are doing? > > It is a pain to have to calculate modelines and manually set monitor > width heights and H and W freq. ranges when they were just there in the > last install and they were there on this very same box for the 10.0 install. > > Grumbling, but concerned. Can you help! > > -- > David C. Rankin, J.D., P.E.
Out of curiosity, did you try copying the /etc/X11/xorg.conf file from the working machine to the non-working one and use that to start your display? Of course, as all good computing practices go, backup the original xorg.conf file before doing the copy. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
