Thanks guys; I finally got past this problem by ctrl-alt-f1 to console, which pulled the Viewsonic out of standby mode, entering "shutdown -r now" and when it came back up YAST2 picked up where it should be and proceeded correctly after that. For anyone who may be tracking this the monitor went to sleep right after XFINE adjustments to screen size and placement and clicking on "Save Configuration". "Steven T. hatton" wrote:
Al Tirevold wrote:
Steve,
Same problems here with SAX2. I never have been able to get it to work.
Using a ATI Rage 128 w/ 32MB and a ViewSonic P810, I have only been able to drive it to 1152x864 so far.
The XF86Config entry I keep 'golden' is:
Modeline "1152x864" 137.65 1152 1176 1304 1536 864 866 885 902 -hsync -vsync
The '-hsync -vsync' part is CRITICAL - if you leave them off it doesn't work for me.
Al ...
On Wed, 28 Feb 2001, you wrote:
On Wednesday 28 February 2001 18:02, Richard Witt wrote:
"Peter B. Van Campen" wrote:
Just rcvd 7.1 Prof. Started a fresh install with YAST2. Just after the point where YAST2 asks which brand and model of monitor (it found and identified my Elsa Office Winner 2000 8-Meg) (Viewsonic 17ps) it requested my choice of resolution and color depth I chose 1152 x 864 at 24 bits; YAST2 then put up a test screen which was ok,but off-center. I adjusted its position and size and entered a "OK". At that point the monitor went into standby mode. The system has remained active ( drive activity) but the monitor has not come back on;
How can I recover this YAST2 installation?
Hi Peter,
I had a somwhat similar problem during my upgrade to 7.1. I was able to get to a virual console by typing Ctrl-Alt-F1 and continue the installation from there.
Richard
Gents,
You are not alone. I too had/have problems with X and my monitor. I worked for half a day with a configuration that came from the 7.1 install. It didn't give me the higher resolutions 1600 X 1200 when I attempted the setup. This is a longstanding bug with SaX(2). I didn't reprot the problem till recently, which is something I feel kind of bad about.
What really surprised me was what happened when I fell asleep and woke up to find my monitor in 'standby'. It suddenly came back to life without intervention, but soon returned to standby. I can't explain why it worked for half a day and then stopped. Fortunately I had a backup of my /etc/XF86Config which I created by hand a long time ago. I swiped the modelines from that, and everyting works . . . kinda'. I still have a problem with my DRI. It doesn't like the 2.4.0 kernel, but works fine with the 2.4.2 that I built. I am however having other problems wtih that.
I suggest you post the specifics of your monitors and cards to the list and ask if other's have similar setups. Then compare notes. For me it ATI Rage Fury wtih 32 Meg and a 21' ViewSonic G810.
Steve
Hey Al,
I used to have a +hsync -vsync on this but I recently took them off and all is well. Put this in your tank as see how fast she runs! I think I could actually get a few more RPMs if I really pushed it.
Modeline "1600x1200" 189.00 1600 1664 1856 2160 1200 1201 1204 1250
Do know how the modelines in the /etc/X11/XF86Config relate to the "modes" we get from ctl + alt + KP_+? The only modeline I tweaked was the one above. I left all the others as SaX created them, and all seems well. I did put in the 1600x1200 manually in all the Screen subsections, e.g.:
Section "Screen" DefaultDepth 24 SubSection "Display" Depth 15 Modes "1600x1200" "1280x1024" "1152x870" "800x600" "640x480" EndSubSection"screen" . . . EndSection
Steve
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
--
===============================
Peter B.Van Campen
Peter_B@vancampen.org
===============================
--
<