Mailinglist Archive: opensuse (4749 mails)

["L. Mark Stone" <LMStone@xxxxxxxxxxx>]

Chuck and Zentara,

Thanks for your posts. I'm top posting to save you from scrolling...

Basically, the problem is that my monitor is not in the SuSE monitor
database, but sax2 thinks the monitor string identifies itself as a Samsung
4S. Consequently, none of the solutions involving sax2 worked for me (at
first).

What I did was boot into a command line as root, and then I ran
"Xf86Config4", which works a lot like the old Xf86config app. I used this
tool to create a new monitor definition, and I defined the monitor as a
VESA-compliant monitor (which the Samsung is).

Then I could boot normally.

To tidy up, I then ran sax2 from KDE and changed the bad old SuSE-created
Samsung 4S monitor definition (I haven't figured out how to delete monitor
definitions using sax2 yet) into the same VESA-compliant definition I used
for the new monitor definition I created with Xf86Config4. In this way, the
two monitors defined on my system are identical.

I am now running at 1280x1024 at a 16-bit color depth just fine.

The video card, BTW, is a Matrox G450 dual-head. This was configured by SuSE
correctly (I don't use the Matrox beta Linux driver; I find it has
problems). I don't believe there was ever any issue with the video card in
my case.

Thanks again for all of your help!

_____________________________________________
A Message From...  L. Mark Stone

Reliable Networks of Maine, LLC
477 Congress Street, 5th Floor
Portland, ME 04107
Tel: (207) 772-5678
Cell: (917) 597-2057
Email: LMStone@xxxxxxxxx
Private: LMStone@xxxxxxxxxxx
Web: http://www.rnome.com



-----Original Message-----
From: zentara [mailto:zentara@xxxxxxxxxxx]
Sent: Saturday, May 17, 2003 7:13 AM
To: suse-linux-e@xxxxxxxx
Subject: Re: [SLE] X Config Problem on 8.2


On Fri, 16 May 2003 19:28:46 -0400
"L. Mark Stone" <LMStone@xxxxxxxxxxx> wrote:

>> I get the same result when I try to run sax2 directly. Once sax2
launches,
>> the screen goes blank with the out of sync message.
>>
>> Since I can get to a command line, and I (think I) can use vim, what is
>the
>> X config file I need to edit manually?

It's /etc/X11/XF86Config.

You might be able to delete(or rename it to .bak) and
try sax2 again.
If that dosn't work, maybe try using the command line setup
utilities, xf86cfg and xf86config.
I know it's one of the weaknesses with SuSE's X setup
with sax2, if it gets setup wrong during install, you just
run into this "blank screen roadblock".

Maybe you have an old XF86Config from an earlier install?
I always keep my old XF86Config files, because of situations
like yours.



--
use Perl;  #powerful programmable prestidigitation

--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx