LCD can't support input signal
SuSE 9.2 Pro Just got a nice birthday present, an Acer 1913b LCD display. I connected it, and it was not able to start using the existing signal. No problem. I reconnected the old CRT, started YaST and Hardware config, video card and monitor, put the mouse pointer over the "Re-probe" button, then disconnected the CRT, reconnected the LCD and clicked. The system found the new display and immediately began ... well.... displaying, at 1280 x 1024, as advertised. Kewl! So I saved and exited, and went happily about my business in KDE. Then my wife wanted to open a session. No problem, just [Ctrl][Alt][F1], log in, and type "startx -- :1" to start a new X session on F8, right? Well, not quite. As soon as the [F1] session becomes live, the Acer goes blank and reports "Input signal not supported". There's something about that enhanced-text session (with the blue suse bar, top and bottom), that it doesn't like. Probably some obscure horizontal and vertical or dot-clock numbers. Well, I can log in blind and type the startx command blind, and get my second session (which does display nicely at [F8]. But I really want to have my [F1] text-based terminal session back. Similarly, the Acer does not support the input during the Linux startup. You know, that splash-screen that says press [F2] for details? Doesn't work. Can't see the silly splash screen, and can't see the boot messages. It's three solid minutes of blankness until the kdm login screen appears. Currently, I'm set to start in run level 5. Is there a way to modify the parameters of that splash-screen and graphic/text boot-message display? I like it because it gives the green and red visual clues for "done, done, done" versus "failed" when a service or device doesn't load. Has anybody else met this? Kevin (really wanting to keep his new flat panel, but not wanting to keep an old 19-inch CRT on standby) -- The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message, and then delete it from your computer without copying or disclosing it. The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer without copying or disclosing it.
I'm not sure what video card your using, didn't see a reference to it in your post. I had just got done combing through the nvidia readme for their 6229 driver. They had mentioned allot of stuff about getting flat panels to recognize correctly. Seems like it has something to do with some new kernel/video card features. If you are using Nvidia, see (app-k) APPENDIX K: CONFIGURING A LAPTOP I know it's not a laptop, but lots of stuff on LCD's there. I suppose this could even help if your NOT using nvidia. lemme know if you need me to send you the README. Hope this helps, I know I DID have trouble on my new laptop and those EDID's. B-) On Friday 18 March 2005 02:18 pm, mlist@safenet-inc.com wrote:
SuSE 9.2 Pro
Just got a nice birthday present, an Acer 1913b LCD display. I connected it, and it was not able to start using the existing signal. No problem. I reconnected the old CRT, started YaST and Hardware config, video card and monitor, put the mouse pointer over the "Re-probe" button, then disconnected the CRT, reconnected the LCD and clicked. The system found the new display and immediately began ... well.... displaying, at 1280 x 1024, as advertised.
Kewl!
So I saved and exited, and went happily about my business in KDE.
Then my wife wanted to open a session. No problem, just [Ctrl][Alt][F1], log in, and type "startx -- :1" to start a new X session on F8, right? Well, not quite.
As soon as the [F1] session becomes live, the Acer goes blank and reports "Input signal not supported". There's something about that enhanced-text session (with the blue suse bar, top and bottom), that it doesn't like. Probably some obscure horizontal and vertical or dot-clock numbers.
Well, I can log in blind and type the startx command blind, and get my second session (which does display nicely at [F8]. But I really want to have my [F1] text-based terminal session back.
Similarly, the Acer does not support the input during the Linux startup. You know, that splash-screen that says press [F2] for details? Doesn't work. Can't see the silly splash screen, and can't see the boot messages. It's three solid minutes of blankness until the kdm login screen appears.
Currently, I'm set to start in run level 5. Is there a way to modify the parameters of that splash-screen and graphic/text boot-message display? I like it because it gives the green and red visual clues for "done, done, done" versus "failed" when a service or device doesn't load.
Has anybody else met this?
Kevin (really wanting to keep his new flat panel, but not wanting to keep an old 19-inch CRT on standby)
--
The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message, and then delete it from your computer without copying or disclosing it.
The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer without copying or disclosing it.
mlist@safenet-inc.com wrote:
SuSE 9.2 Pro
No problem, just [Ctrl][Alt][F1], log in, and type "startx -- :1" to start a new X session on F8, right? Well, not quite.
As soon as the [F1] session becomes live, the Acer goes blank and reports "Input signal not supported". You should choose a setting for the framebuffer (i.e. vga line in GRUB) your monitor supports. Similarly, the Acer does not support the input during the Linux startup. Do you mean the BIOS POST or GRUB stage 1 (grub screen)? You know, that splash-screen that says press [F2] for details? That is a different setting. Check it with the Yast, System, Boot Configuration. Doesn't work. Can't see the silly splash screen, and can't see the boot messages. This one is controlled by the vga= line in GRUB. Is there a way to modify the parameters of that splash-screen and graphic/text boot-message display? Maybe in an xterm, try hwinfo --framebuffer and choose a setting that will work. Has anybody else met this?
It isn't that uncommon as LCD flat panels are more freq sensitive.
Kevin (really wanting to keep his new flat panel, but not wanting to keep an old 19-inch CRT on standby)
You will get this working. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
On Fri, 2005-03-18 at 16:01 -0600, Joe Morris (NTM) wrote:
mlist@safenet-inc.com wrote:
SuSE 9.2 Pro Can't see the silly splash screen, and can't see the boot messages. This one is controlled by the vga= line in GRUB. Is there a way to modify the parameters of that splash-screen and graphic/text boot-message display? Maybe in an xterm, try hwinfo --framebuffer and choose a setting that will work.
And after this run mk_initrd to set it for the boot splash screen. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Friday 18 March 2005 23:56, Brad Bourn wrote:
Isn't the only thing you have to do to change framebuffer is set vga=xxxx on the boot line in grub?
Indeed.
B-)
On Friday 18 March 2005 03:47 pm, Ken Schneider wrote:
And after this run mk_initrd to set it for the boot splash screen.
This reason for using mk_initrd strikes me too. Cheers, Leen
Brad Bourn wrote:
Isn't the only thing you have to do to change framebuffer is set vga=xxxx on the boot line in grub?
On Friday 18 March 2005 03:47 pm, Ken Schneider wrote:
And after this run mk_initrd to set it for the boot splash screen.
You are right, I missed that Ken, and Brad, Ken is correct. Running mkinitrd puts the splash image in the initrd, so if you change the size it would need to be reinstalled. This should, though, be done by the Yast boot loader, if that was used. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
participants (5)
-
Brad Bourn -
Joe Morris (NTM) -
Ken Schneider -
Leendert Meyer -
mlist＠safenet-inc.com