I have just changed from a CRT monitor to a new LG 15" TFT one. Before I changed, I was running the old monitor at the same settings as the new one requires - 1024x768 at 75Hz. The new monitor works correctly both in Windows98 and Libranet. I didn't have to change anything in Libranet, the new one just worked. However, it doesn't work in SuSE8.1. I can boot and everything looks correct. When it gets to the part of the boot process where KDM starts, the screen goes black and I get an error message: INPUT SIGNAL OUT OF RANGE. Then, nothing else happens. Booting into text mode, to try to run the text mode version of Sax2 (to see if I could find anything wrong) goes well until the prompt. Typing "Sax2" makes the screen go black again with the same error message and then nothing. So I can't run Sax2 to check anything. As I said, the new settings are the same as the old ones. So I can't understand why it won't work in SuSE. I can't find any answer to this problem either in the manuals or in the list archives. Please can anyone give me some advice? Many thanks Keith
Hi Keith On Tuesday 01 April 2003 5:30 pm, Keith Powell wrote:
However, it doesn't work in SuSE8.1. I can boot and everything looks correct. When it gets to the part of the boot process where KDM starts, the screen goes black and I get an error message: INPUT SIGNAL OUT OF RANGE. Then, nothing else happens.
Yes, 8.1 has a few little "foibles" that I found disqueiting in a product that is usually of such high quality - let's hope 8.2 is a bit better (eg provides an easy way to install LILO when GRUB won't work). What seems to be happening here is that Sax sets up the monitor to use the highest res that the graphics card is capable of, even if that is higher than the monitor can stand. I have a Hercules ProphetView 720 with the same issue. What you need to do is save your current /etc/X11/XF86Config file as something else (eg XF86Config.old), and then edit the original. Go to the "Modes" section, and remove from it all lines other than the 1024x768 one. In the "Screens" section, remove all references to resolutions higher than 1024x768.
Booting into text mode, to try to run the text mode version of Sax2 (to see if I could find anything wrong) goes well until the prompt. Typing "Sax2" makes the screen go black again with the same error message and then nothing. So I can't run Sax2 to check anything.
Unfortunately, because of this bug, you can't really use Sax to make screen changes from now on, because it will detect the highest res on the card, and set X to use that, which won't work .... Silly, really. HTH Kevin
On Tuesday 01 April 2003 5:30 pm, Keith Powell wrote:
However, it doesn't work in SuSE8.1. I can boot and everything looks correct. When it gets to the part of the boot process where KDM starts, the screen goes black and I get an error message: INPUT SIGNAL OUT OF RANGE. Then, nothing else happens.
Kevin Donnelly replied:
Yes, 8.1 has a few little "foibles" that I found disqueiting in a product that is usually of such high quality - let's hope 8.2 is a bit better (eg provides an easy way to install LILO when GRUB won't work). What seems to be happening here is that Sax sets up the monitor to use the highest res that the graphics card is capable of, even if that is higher than the monitor can stand. I have a Hercules ProphetView 720 with the same issue. What you need to do is save your current /etc/X11/XF86Config file as something else (eg XF86Config.old), and then edit the original. Go to the "Modes" section, and remove from it all lines other than the 1024x768 one. In the "Screens" section, remove all references to resolutions higher than 1024x768.
Booting into text mode, to try to run the text mode version of Sax2 (to see if I could find anything wrong) goes well until the prompt. Typing "Sax2" makes the screen go black again with the same error message and then nothing. So I can't run Sax2 to check anything.
Unfortunately, because of this bug, you can't really use Sax to make screen changes from now on, because it will detect the highest res on the card, and set X to use that, which won't work .... Silly, really.
Jason Hale replied:
I recently set up a Sharp LL-T1820 w/o problems using SAX2. I guess you should try to use XFree86Setup and try to generate the config file using that program. I used it a while back on Redhat 5.x, and it wasn't that difficult but required you to know *exactly* what video card chipset you have. Pop the lid and take a peek just to be sure. I got the same message if I tried to run my monitor at > 1280 X 1024, the native resolution on my flat panel. I entered my vertical and horizontal refresh rates myself instead of using any default settings. Be sure to have these with you when you start. If you drive your tft at the wrong rates, you can hose it for sure. Good luck.
Hello Jason and Kevin. Thank you both for your help with solving my monitor problem. To cut a long story short, I had no luck with the XFree86 configuration tools, including SaX2. Whatever I did, I still got the same error message. So, in the end, I "cheated!" I connected my old monitor back up. It wouldn't work in graphical mode, so my XFree file must have really got in a mess. It worked in textmode, so I ran the ncurses version of YaST2. I set the monitor up to only run at 1025x768 at 60KHz - 75Hz. I have checked the XF86Config and it does only contain the one resolution. When I plugged the new monitor back in, it worked. So all is now well. Many thanks again for your help. Cheers Keith
llOn Thu, 3 Apr 2003 05:22, Keith Powell wrote: ------------------Very big snip -----------------------------
To cut a long story short, I had no luck with the XFree86 configuration tools, including SaX2. Whatever I did, I still got the same error message.
So, in the end, I "cheated!" I connected my old monitor back up. It wouldn't work in graphical mode, so my XFree file must have really got in a mess. It worked in textmode, so I ran the ncurses version of YaST2. I set the monitor up to only run at 1025x768 at 60KHz - 75Hz. I have checked the XF86Config and it does only contain the one resolution.
When I plugged the new monitor back in, it worked. So all is now well.
Many thanks again for your help.
Cheers
Keith
Hi Keith, This may be useful in the future. I was mucking around with sax2 yesterday and brought up the man page. There is an option -l which may have solved your problem. -l Enable low resolution. Allow only the 640x480 reso lution for the graphics setup. This is usefull if the DDC probing of the monitor results in not dis playable resolution values. -- Regards, Graham Smith ---------------------------------------------------------
participants (3)
-
Graham Smith -
Keith Powell -
Kevin Donnelly