Startx doesn't start
My 17" monitor keeps coming up with Out of Range warning. Suse detected the Komondo monitor during installation. Whereis XFree86.conf located I need to change the Hoz and Vert settings.
* jim
My 17" monitor keeps coming up with Out of Range warning. Suse detected the Komondo monitor during installation. Whereis XFree86.conf located I need to change the Hoz and Vert settings.
/etc/X11/XF86Config -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
Hi all ! Patrick Shanahan schrieb:
* jim
[10-15-05 17:40]: My 17" monitor keeps coming up with Out of Range warning. Suse detected the Komondo monitor during installation. Whereis XFree86.conf located I need to change the Hoz and Vert settings.
/etc/X11/XF86Config
Since SuSE changed to Xorg the file is called /etc/X11/xorg.conf (/etc/X11/XF86Config now is a symlink to xorg.conf) I guess it is a better idea to use a tool like "sax2" to do that task ... Therefore I recommend to change to runlevel 3 (by command "init 3" as user root) and then calling "sax2" (as well as user root). On the first page displayed by "sax2" you will find an entry for the resolution. Probably it is set to 1280x1024. For 17" monitors a resolution of 1152x864 or 1024x768 might be the better choice. If your monitor supplier is not within the list of possible selections I suggest to use the "-->> VESA" section. Probably you should start with 1024x768 and then trying 1152x768. Never give up ! Best regards, Reinhard.
Reinhard Gimbel wrote:
Hi all !
Patrick Shanahan schrieb:
* jim
[10-15-05 17:40]: My 17" monitor keeps coming up with Out of Range warning. Suse detected the Komondo monitor during installation. Whereis XFree86.conf located I need to change the Hoz and Vert settings.
/etc/X11/XF86Config
Since SuSE changed to Xorg the file is called
/etc/X11/xorg.conf (/etc/X11/XF86Config now is a symlink to xorg.conf)
I guess it is a better idea to use a tool like "sax2" to do that task ...
Therefore I recommend to change to runlevel 3 (by command "init 3" as user root) and then calling "sax2" (as well as user root).
On the first page displayed by "sax2" you will find an entry for the resolution. Probably it is set to 1280x1024. For 17" monitors a resolution of 1152x864 or 1024x768 might be the better choice. If your monitor supplier is not within the list of possible selections I suggest to use the "-->> VESA" section.
Probably you should start with 1024x768 and then trying 1152x768.
Never give up !
Best regards, Reinhard.
--------------------------------------------------------------------- To unsubscribe, e-mail:use in Sndscomma opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Thanks very much for your help. I'am typically a Fedora user and I want to give Suse a checkout , I think Novell is going to put a Lot of effort into making Suse the Desktop for Linux, as a hardcore Linux user I prefer Fedora4 because it gives me more of the bash commands to use than does Suse, Yes I know I could install those commands in Suse. But Fedora and Suse gives me the best of both words , commandline and desktop. That is if I can get X to work on this boxwith Suse like Fedora does. I had no problems in Suse9.3. I do agree with you on the settings of 1024x768. Suse Install setup is very easy for anyone to use. thanks again Jim
jim wrote:
Reinhard Gimbel wrote:
Hi all !
Patrick Shanahan schrieb:
* jim
[10-15-05 17:40]: My 17" monitor keeps coming up with Out of Range warning. Suse detected the Komondo monitor during installation. Whereis XFree86.conf located I need to change the Hoz and Vert settings.
/etc/X11/XF86Config
Since SuSE changed to Xorg the file is called
/etc/X11/xorg.conf (/etc/X11/XF86Config now is a symlink to xorg.conf)
I guess it is a better idea to use a tool like "sax2" to do that task ...
Therefore I recommend to change to runlevel 3 (by command "init 3" as user root) and then calling "sax2" (as well as user root).
On the first page displayed by "sax2" you will find an entry for the resolution. Probably it is set to 1280x1024. For 17" monitors a resolution of 1152x864 or 1024x768 might be the better choice. If your monitor supplier is not within the list of possible selections I suggest to use the "-->> VESA" section.
Probably you should start with 1024x768 and then trying 1152x768.
Never give up !
Best regards, Reinhard.
--------------------------------------------------------------------- To unsubscribe, e-mail:use in Sndscomma opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Thanks very much for your help. I'am typically a Fedora user and I want to give Suse a checkout , I think Novell is going to put a Lot of effort into making Suse the Desktop for Linux, as a hardcore Linux user I prefer Fedora4 because it gives me more of the bash commands to use than does Suse, Yes I know I could install those commands in Suse. But Fedora and Suse gives me the best of both words , commandline and desktop. That is if I can get X to work on this boxwith Suse like Fedora does. I had no problems in Suse9.3. I do agree with you on the settings of 1024x768. Suse Install setup is very easy for anyone to use.
thanks again
Jim
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
I tryed running sax2 in runlevel3 (suse, failsafe) and sax2 starts, the screen goes dark and monitor goes into offline mode, no running of sax2. Not a very dependable application this sax2. Jim
On Sun, Oct 16, 2005 at 08:02:35AM -0500, jim wrote:
I tryed running sax2 in runlevel3 (suse, failsafe) and sax2 starts, the screen goes dark and monitor goes into offline mode, no running of sax2. Not a very dependable application this sax2.
Type `sax2 --help` to see some possible things to start with. e.g. `sax2 -l` or `sax2 -V 0:1024x768@85` houghi -- Quote correct (NL) http://www.briachons.org/art/quote/ Zitiere richtig (DE) http://www.afaik.de/usenet/faq/zitieren Quote correctly (EN) http://www.netmeister.org/news/learn2quote.html
Hi all ! houghi schrieb:
On Sun, Oct 16, 2005 at 08:02:35AM -0500, jim wrote:
I tryed running sax2 in runlevel3 (suse, failsafe) and sax2 starts, the screen goes dark and monitor goes into offline mode, no running of sax2. Not a very dependable application this sax2.
Type `sax2 --help` to see some possible things to start with. e.g. `sax2 -l` or `sax2 -V 0:1024x768@85`
Oops, with an non-working configuration it is of course not possible to get a useful output with "sax2". Thanks, houghi ! Never give up ! Best regards, Reinhard.
On Sunday 16 October 2005 10:14, Reinhard Gimbel wrote:
Oops, with an non-working configuration it is of course not possible to get a useful output with "sax2".
Hi Reinhard, If you boot to run level 3, log in as root and run "sax2 -l" (lower case "L"), SaX2 will run in standard VESA compliant low resolution (VGA) mode, which is supported natively in hardware, (no special external drivers needed) in every PC graphics subsystem marketed in at least the past ten years. If you're getting a text console and can log into run level 3, *and* if your hardware is not broken in some way or misidentified during installation, "sax2 -l" will work. If it *doesn't* work, that is a clear sign that there is something fundamentally wrong at the hardware level... either: - the hardware is not supported - the hardware is not recognized properly (meaning the installer is getting confused and misidentifying it, thereby creating inappropriate config files) - there is actually something wrong with the hardware: - wrong BIOS settings - a mix of unsupported+supported parts producing confused probe results - damaged or improperly installed components IMHO, it isn't fair or reasonable to dump on SaX2 until you've ruled out these possibilities. regards, - Carl
Carl Hartung schrieb:
If you boot to run level 3, log in as root and run "sax2 -l" (lower case "L"), SaX2 will run in standard VESA compliant low resolution (VGA) mode, which is supported natively in hardware, (no special external drivers needed) in every PC graphics subsystem marketed in at least the past ten years.
If you're getting a text console and can log into run level 3, *and* if your hardware is not broken in some way or misidentified during installation, "sax2 -l" will work. If it *doesn't* work, that is a clear sign that there is something fundamentally wrong at the hardware level... either:
- the hardware is not supported - the hardware is not recognized properly (meaning the installer is getting confused and misidentifying it, thereby creating inappropriate config files) - there is actually something wrong with the hardware: - wrong BIOS settings - a mix of unsupported+supported parts producing confused probe results - damaged or improperly installed components
IMHO, it isn't fair or reasonable to dump on SaX2 until you've ruled out these possibilities.
O.k., that's true ! One also can try to get a more common video timing by calling YaST from a text conole device, navigate to the graphics card settings and select a 1024x768@60Hz screen. Using the "sax2 -l" or "sax2 -il" should work every time but is crude somehow. In this case I would prefer to use "sax2 -V 0:1024x768@60" as posted by houghi. Never give up ! Best regards, Reinhard.
On Sunday 16 October 2005 12:16, Reinhard Gimbel wrote:
O.k., that's true !
Thank you!
One also can try to get a more common video timing by calling YaST from a text conole device, navigate to the graphics card settings and select a 1024x768@60Hz screen.
Why add a layer of abstraction? Doesn't this just run SaX2 in the background?
Using the "sax2 -l" or "sax2 -il" should work every time but is crude somehow.
Please elaborate on this. In my view, directly calling the essential utility from the CLI is more elegant. No worries that the GUI is masking important output or symptoms/clues.
In this case I would prefer to use "sax2 -V 0:1024x768@60" as posted by houghi.
Oh... *him* again! OK, I see how it is. Hmmph! ;-)
Never give up !
Here, that's "Never, ever give up!" Take care! - Carl
Am Sonntag, 16. Oktober 2005 15:02 schrieb jim:
jim wrote:
Reinhard Gimbel wrote:
Hi all !
Patrick Shanahan schrieb:
* jim
[10-15-05 17:40]: My 17" monitor keeps coming up with Out of Range warning. Suse detected the Komondo monitor during installation. Whereis XFree86.conf located I need to change the Hoz and Vert settings.
/etc/X11/XF86Config
Since SuSE changed to Xorg the file is called
/etc/X11/xorg.conf (/etc/X11/XF86Config now is a symlink to xorg.conf)
I guess it is a better idea to use a tool like "sax2" to do that task ...
Therefore I recommend to change to runlevel 3 (by command "init 3" as user root) and then calling "sax2" (as well as user root).
On the first page displayed by "sax2" you will find an entry for the resolution. Probably it is set to 1280x1024. For 17" monitors a resolution of 1152x864 or 1024x768 might be the better choice. If your monitor supplier is not within the list of possible selections I suggest to use the "-->> VESA" section.
Probably you should start with 1024x768 and then trying 1152x768.
Never give up !
Best regards, Reinhard.
Thanks very much for your help. I'am typically a Fedora user and I want to give Suse a checkout , I think Novell is going to put a Lot of effort into making Suse the Desktop for Linux, as a hardcore Linux user I prefer Fedora4 because it gives me more of the bash commands to use than does Suse, Yes I know I could install those commands in Suse. But Fedora and Suse gives me the best of both words , commandline and desktop. That is if I can get X to work on this boxwith Suse like Fedora does. I had no problems in Suse9.3. I do agree with you on the settings of 1024x768. Suse Install setup is very easy for anyone to use.
thanks again
Jim
I tryed running sax2 in runlevel3 (suse, failsafe) and sax2 starts, the screen goes dark and monitor goes into offline mode, no running of sax2. Not a very dependable application this sax2.
Jim
Have you tried running sax2 -il ? This helped one of the times that sax did not work for me ... Ciao, Alex
Alexander Grujic wrote:
Am Sonntag, 16. Oktober 2005 15:02 schrieb jim:
jim wrote:
Reinhard Gimbel wrote:
Hi all !
Patrick Shanahan schrieb:
* jim
[10-15-05 17:40]: My 17" monitor keeps coming up with Out of Range warning. Suse detected the Komondo monitor during installation. Whereis XFree86.conf located I need to change the Hoz and Vert settings.
/etc/X11/XF86Config
Since SuSE changed to Xorg the file is called
/etc/X11/xorg.conf (/etc/X11/XF86Config now is a symlink to xorg.conf)
I guess it is a better idea to use a tool like "sax2" to do that task ...
Therefore I recommend to change to runlevel 3 (by command "init 3" as user root) and then calling "sax2" (as well as user root).
On the first page displayed by "sax2" you will find an entry for the resolution. Probably it is set to 1280x1024. For 17" monitors a resolution of 1152x864 or 1024x768 might be the better choice. If your monitor supplier is not within the list of possible selections I suggest to use the "-->> VESA" section.
Probably you should start with 1024x768 and then trying 1152x768.
Never give up !
Best regards, Reinhard.
Thanks very much for your help. I'am typically a Fedora user and I want to give Suse a checkout , I think Novell is going to put a Lot of effort into making Suse the Desktop for Linux, as a hardcore Linux user I prefer Fedora4 because it gives me more of the bash commands to use than does Suse, Yes I know I could install those commands in Suse. But Fedora and Suse gives me the best of both words , commandline and desktop. That is if I can get X to work on this boxwith Suse like Fedora does. I had no problems in Suse9.3. I do agree with you on the settings of 1024x768. Suse Install setup is very easy for anyone to use.
thanks again
Jim
00 I
Have you tried running sax2 -il ? This helped one of the times that sax did not work for me ...
Ciao, Alex
Thanks Alex,and thanks everybody sax2 -il did it. I can see it now, Suse for all my friends and family Desktops, Lookout $Microsoft, and for me , hardcore Linux user , Fedora on my main box and possibly Suse for my Laptop. has Suse got the problem solved for the Intel ipw2100 wireless card and Nvidia vedio drivers, that is, what is unique to my Dell Inspiron8600 Laptop. Thanks everyone Jim
participants (6)
-
Alexander Grujic
-
Carl Hartung
-
houghi
-
jim
-
Patrick Shanahan
-
Reinhard Gimbel