SUSE linux desktop video signal out of range.
Hi, I'm trying out SUSE linux desktop and when I install it the NEC LCD 1850E monitor say video signal out of range, now I have this before with setting up X but this ok's even at the console level any ideas about what I can do about this. thanks, Dave. -- Dr. David Holden. (Systems Developer) Crystallography Journals Online: http://journals.iucr.org Thanks in advance:- Please avoid sending me Word or PowerPoint attachments. See: http://www.fsf.org/philosophy/no-word-attachments.html UK Privacy (R.I.P) : http://www.stand.org.uk/commentary.php3 Public GPG key available on request. -------------------------------------------------------------
On Tuesday 02 December 2003 10:38 am, David Holden wrote:
Hi,
I'm trying out SUSE linux desktop and when I install it the NEC LCD 1850E monitor say video signal out of range, now I have this before with setting up X but this ok's even at the console level any ideas about what I can do about this.
thanks,
Dave.
-- Dr. David Holden. (Systems Developer) Crystallography Journals Online: http://journals.iucr.org
Thanks in advance:- Please avoid sending me Word or PowerPoint attachments. See: http://www.fsf.org/philosophy/no-word-attachments.html
UK Privacy (R.I.P) : http://www.stand.org.uk/commentary.php3 Public GPG key available on request. -------------------------------------------------------------
I've had two situation under which something similars occurs. 1. Initially setting up my Linux system. In which case I had to make sure that the system was set to initially boot with resolution 1024x768 (even though my monitor was capable of better). And also make sure that the xserver was also set correctly or the same thing would happen when the xserver started up. 2. A seemly spontaneous "Out of timing" error message (on thin clients connected to a Windows Server). This was "solved" spontaneously by powering off the monitor for a few minutes.
On Tuesday 02 December 2003 04:38 am, David Holden wrote:
I'm trying out SUSE linux desktop and when I install it the NEC LCD 1850E monitor say video signal out of range, now I have this before with setting up X but this ok's even at the console level any ideas about what I can do about this. thanks,
More than likely you have the resolution set up to high. For example if your monitor is only capable of 1200x.700 and you have sax set at 1200x1200 you would get the error message. If that is the case, then go into sax or yast and set up your video card resolution to something your monitor can handle. If that's not it then some guru will have to step in. Richard
On Tuesday 02 Dec 2003 12:51 pm, eddie wrote:
On Tuesday 02 December 2003 10:38 am, David Holden wrote:
Hi,
I'm trying out SUSE linux desktop and when I install it the NEC LCD 1850E monitor say video signal out of range, now I have this before with setting up X but this ok's even at the console level any ideas about what I can do about this.
thanks,
Dave.
-------------------------------------------------------------
I've had two situation under which something similars occurs.
1. Initially setting up my Linux system. In which case I had to make sure that the system was set to initially boot with resolution 1024x768 (even though my monitor was capable of better). And also make sure that the xserver was also set correctly or the same thing would happen when the xserver started up.
2. A seemly spontaneous "Out of timing" error message (on thin clients connected to a Windows Server). This was "solved" spontaneously by powering off the monitor for a few minutes.
Hi eddie, How do you set it so that the initial boot is at a specific resolution, our LCD display do 1280x1024, is this an argument I can give to the boot prompt. Also will this setting carry forward to the console screens, e.g. tty1, tty2 etc thanks, Dave. -- Dr. David Holden. (Systems Developer) Crystallography Journals Online: http://journals.iucr.org Thanks in advance:- Please avoid sending me Word or PowerPoint attachments. See: http://www.fsf.org/philosophy/no-word-attachments.html UK Privacy (R.I.P) : http://www.stand.org.uk/commentary.php3 Public GPG key available on request. -------------------------------------------------------------
<snip>
If that is the case, then go into sax or yast and set up your video card resolution to something your monitor can handle.
You can tell SaX2 to start in low resolution mode so you can configure your monitor. Start SaX2 on the command line with the -l flag like so sax2 -l and this should get you started. HTH -- Marshall "Nothing is impossible, we just do not have all the answers to make the impossible, possible."
On Tuesday 02 December 2003 15:59, David Holden wrote:
How do you set it so that the initial boot is at a specific resolution, our LCD display do 1280x1024, is this an argument I can give to the boot prompt.
When booting from the install CD, there's a tab at the bottom that shows the resolution that grub (I assume) detected. It always detects my 15" as 1280x1024, even though the screen is 1024x768 - I'ts been like that in 8.0, 8,1 and 8,2. Set that one lower. If you need a lower res for booting an already installed system, highlight your choice in the grub bootmenu, press e, highlight the kernel line and press e again. There should be a line that says something like vga=791 - change this to vga=normal. You'll loose splash, but your console will work. You can try moving it up notch by notch (vga=1, vga=2, ect) and see what your monitor can handle.
Also will this setting carry forward to the console screens, e.g. tty1, tty2 etc Yes
Hans
On 12/02/2003 10:20 PM, H du Plooy wrote:
There should be a line that says something like vga=791 - change this to vga=normal. You'll loose splash, but your console will work. You can try moving it up notch by notch (vga=1, vga=2, ect) and see what your monitor can handle.
Or better yet, as root run hwinfo --framebuffer, which will printout the different modes your card will handle, and replace the vga= line in greb's menu.lst with a more compatible for your setup. Then, you can keep splash. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Marshall Heartley wrote:
You can tell SaX2 to start in low resolution mode so you can configure your monitor. Start SaX2 on the command line with the -l flag like so sax2 -l and this should get you started.
Doesn't work for me. Same thing happened as in most XFree versions over many different distros for as long as I've been installing Linux. Excerpts from SaX.log: (WW) TSENG(0): Mode pool is empty (EE) TSENG(0): No valid modes found (EE) TSENG(0): Screen(s) found, but none have a usable configuration. The problem, as in the past, is that XF86Config actually contains: Section "Device" BoardName "ET6000" BusID "0:9:0" Driver "tseng" Identifier "Device[0]" VendorName "Tseng" EndSection instead of what it needs to contain to work: Section "Device" BoardName "ET6000" BusID "0:9:0" Driver "tseng" Identifier "Device[0]" VendorName "Tseng" VideoRam 4096 Option "noaccel" EndSection Because it never gets started that way, it never creates usable modelines. I can edit the file to get some working modes, but never the maximum resolution supported by the hardware in windoze. -- "You will know the truth, and the truth will set you free." John 8:32 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
Joe Morris (NTM) wrote:
Or better yet, as root run hwinfo --framebuffer, which will printout the different modes your card will handle
Doesn't work for me (8.2). It prints some information on the screen, but all on the same line - no scrolling - happens too fast to read any of it, and leaves the screen as found when done. I tried redirecting to a file, but that comes to 0 bytes. -- "You will know the truth, and the truth will set you free." John 8:32 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
On Wednesday 03 December 2003 3:19 am, Felix Miata wrote:
Joe Morris (NTM) wrote:
Or better yet, as root run hwinfo --framebuffer, which will printout the different modes your card will handle
Doesn't work for me (8.2). It prints some information on the screen, but all on the same line - no scrolling - happens too fast to read any of it, and leaves the screen as found when done. I tried redirecting to a file, but that comes to 0 bytes.
Have you tried piping it through less? hwinfo --framebuffer | less That works for me. But maybe something else is going on since you have no scrolling. Eddie
-- "You will know the truth, and the truth will set you free." John 8:32 NIV
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://members.ij.net/mrmazda/
On 12/03/2003 11:19 AM, Felix Miata wrote:
Joe Morris (NTM) wrote:
Or better yet, as root run hwinfo --framebuffer, which will printout the different modes your card will handle
Doesn't work for me (8.2). It prints some information on the screen, but all on the same line - no scrolling - happens too fast to read any of it, and leaves the screen as found when done. I tried redirecting to a file, but that comes to 0 bytes.
I am also on 8.2. Does splash work on your machine? Your video card can run X but not support framebuffers. Again, it will show what your card will handle. I suspect your card does not support framebuffer. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Joe Morris (NTM) wrote:
On 12/03/2003 11:19 AM, Felix Miata wrote:
Joe Morris (NTM) wrote:
Or better yet, as root run hwinfo --framebuffer, which will printout the different modes your card will handle
Doesn't work for me (8.2). It prints some information on the screen, but all on the same line - no scrolling - happens too fast to read any of it, and leaves the screen as found when done. I tried redirecting to a file, but that comes to 0 bytes.
I am also on 8.2. Does splash work on your machine? Your video card can run X but not support framebuffers. Again, it will show what your card will handle. I suspect your card does not support framebuffer.
I disabled splash entirely on my 8.2 box, but don't remember what method I used. It works on my 8.1 box. I use the same graphics adapter in all my PCI machines. On my 8.1 box, I just tried piping hwinfo --framebuffer through both less and grep successfully: Hardware Class: framebuffer Without the piping, it starts to do the same thing that happened on my 8.2 box, writing the first group of output lines on the same line, but then printing each supported mode on a separate line. I tried again with both grep and less on the 8.2 box, and both those fail as well. -- "You will know the truth, and the truth will set you free." John 8:32 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
On 12/04/2003 12:06 AM, Felix Miata wrote:
Without the piping, it starts to do the same thing that happened on my 8.2 box, writing the first group of output lines on the same line, but then printing each supported mode on a separate line.
I think what you are seeing is the scanning of the cards capabilities, which produces some writing all on the same line (same for all hwinfo scans). After the scans, it will print out the results on separate lines
I tried again with both grep and less on the 8.2 box, and both those fail as well.
Since you are using the same card in 8.1 which is working (which means the card does support framebuffers), I would suspect an acpi problem with your system in 8.2 that keeps the framebuffer from working in 8.2, thus the failure to print out any capabilities. If it is a pci video card, maybe a boot line such as pci=noacpi would allow it to work, or acpi=off, but if splash is all that is not working properly, it may not be worth fixing. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Joe Morris (NTM) wrote:
On 12/04/2003 12:06 AM, Felix Miata wrote:
Without the piping, it starts to do the same thing that happened on my 8.2 box, writing the first group of output lines on the same line, but then printing each supported mode on a separate line.
I think what you are seeing is the scanning of the cards capabilities, which produces some writing all on the same line (same for all hwinfo scans). After the scans, it will print out the results on separate lines
All those entries that scroll on the same line produce separate lines piped through grep or less.
I tried again with both grep and less on the 8.2 box, and both those fail as well.
Since you are using the same card in 8.1 which is working (which means the card does support framebuffers), I would suspect an acpi problem with your system in 8.2 that keeps the framebuffer from working in 8.2, thus the failure to print out any capabilities. If it is a pci video card, maybe a boot line such as pci=noacpi would allow it to work, or
The video cards were designed in 1996, the motherboards in 1997. The BIOS dates are 1999. I've never needed any boot parameters for apic or acpi on any of my systems in any distro before. I doubt this hardware knows anything about them.
acpi=off, but if splash is all that is not working properly, it may not
I don't care whether splash would work or not. I intentionally disabled it.
be worth fixing.
Maybe I wasn't making myself clear. The ONLY things that totally fail are YaST/YaST2 and 'hwinfo --framebuffer'. The former produce an XF86Config file missing two parameters ABSOLUTELY REQUIRED for my video cards to work in XFree86: VideoRam 4096 Option "noaccel" Once I modifiy YaST's defectively produced config file, X works just fine, all the way up to 16 bit 1600x1200. In contrast to this broken 8.2 behavior, 8.1 got it right the first try during initial installation, IIRC the only distro with an XFree86 v4.x version ever to do so. -- "You will know the truth, and the truth will set you free." John 8:32 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
participants (7)
-
David Holden -
eddie -
Felix Miata -
H du Plooy -
Joe Morris (NTM) -
Marshall Heartley -
Richard