9.2 Live CD - Monitor Problem
The 9.2 Live CDROM cannot identify either of my Samsung monitors correctly and as soon as the graphical portion of the boot process begins, each monitor reports that the signal is out of range. I tried using the F2 key during the boot manager screen to select text mode, but that too fails in the exact same way. I also tried VESA, since both monitors are indeed quite VESA compliant, but got the same result. Works fine on another computer with a Hitachi monitor, BTW. Frustrating, because for each release of SuSE since 8.2 one of the two monitors has been misidentified (the second monitor was acquired last month), and I have with the release of each version dutifully filled out a bug report for SuSE. Any way I can get a command prompt to run sax and set the monitor settings correctly? Thanks, Mark -- ____________________________________________________ Another Message From... L. Mark Stone Reliable Networks of Maine, LLC 477 Congress Street Portland, ME 04101 Tel: (207) 772-5678
"L. Mark Stone"
The 9.2 Live CDROM cannot identify either of my Samsung monitors correctly and as soon as the graphical portion of the boot process begins, each monitor reports that the signal is out of range.
I had a similar problem with SUSE Linux 9.1 and the Samsung SyncMaster 193T LCD monitor. The monitor was incorrectly identified as Samsung 4S (or similar) and the frequencies were out of range. The workaround was to - switch to a text console via Ctrl-Alt-F2 - go to run level 3 via "init 3" - run "sax2 --vesa 0:1280x1024@60", configure keyboard, ... - go back to runlevel 5 via "init 5" -- A.M.
On Monday October 25, 2004 09:17 am, Alexandr Malusek wrote:
"L. Mark Stone"
writes: The 9.2 Live CDROM cannot identify either of my Samsung monitors correctly and as soon as the graphical portion of the boot process begins, each monitor reports that the signal is out of range.
I had a similar problem with SUSE Linux 9.1 and the Samsung SyncMaster 193T LCD monitor. The monitor was incorrectly identified as Samsung 4S (or similar) and the frequencies were out of range. The workaround was to
- switch to a text console via Ctrl-Alt-F2 - go to run level 3 via "init 3" - run "sax2 --vesa 0:1280x1024@60", configure keyboard, ... - go back to runlevel 5 via "init 5"
Hi Alexandr, The above worked, except for the last line. Instead of doing init 5 (which just put things back the way they were, out of sync), I ran "startx" and then I was presented with a Desktop I could actually see! Thanks! Mark -- __________________________________________________________ A Message From... L. Mark Stone Reliable Networks of Maine, LLC 477 Congress Street Portland, ME 04101 (207) 772-5678
On Sunday 24 October 2004 10:37 pm, L. Mark Stone wrote:
The 9.2 Live CDROM cannot identify either of my Samsung monitors correctly and as soon as the graphical portion of the boot process begins, each monitor reports that the signal is out of range.
I tried using the F2 key during the boot manager screen to select text mode, but that too fails in the exact same way. I also tried VESA, since both monitors are indeed quite VESA compliant, but got the same result.
Works fine on another computer with a Hitachi monitor, BTW.
Frustrating, because for each release of SuSE since 8.2 one of the two monitors has been misidentified (the second monitor was acquired last month), and I have with the release of each version dutifully filled out a bug report for SuSE.
Any way I can get a command prompt to run sax and set the monitor settings correctly?
Thanks, Mark
Mark, Just a single question for you. When you sent in the bug reports, did you include all your monitor specs, model, type, scan rates, so that SuSE could include it in their monitor database? Also, I'm thinking maybe the monitors are sending some type of odd info that they are not picked up correctly. Is it possible to instruct it to stop at init 3 when booting? Can you type "init 3" at the bootloader screen to do that? Lee -- --- KMail v1.7.1 --- SuSE Linux Pro v9.1 --- Registered Linux User #225206 Those Who Dance Are Considered Insane, by Those Who Cannot Hear the Music!
On Monday 25 October 2004 09:25, BandiPat wrote:
Just a single question for you. I count two or three questions... ;-)
When you sent in the bug reports, did you include all your monitor specs, model, type, scan rates, so that SuSE could include it in their monitor database? Of course!
Also, I'm thinking maybe the monitors are sending some type of odd info that they are not picked up correctly. Is it possible to instruct it to stop at init 3 when booting? Can you type "init 3" at the bootloader screen to do that? Will try and report back later today.
-- __________________________________________________________ A Message From... L. Mark Stone Reliable Networks of Maine, LLC 477 Congress Street Portland, ME 04101 (207) 772-5678
On Monday 25 October 2004 9:25 am, BandiPat wrote:
Also, I'm thinking maybe the monitors are sending some type of odd info that they are not picked up correctly. Is it possible to instruct it to stop at init 3 when booting? Can you type "init 3" at the bootloader screen to do that?
I don't have a monitor problem, but a mis-identification problem. I installed 9.1 on my Dell desktop. I noticed that I have a power icon, like a laptop, and I finally noticed ( I forget where i saw it) that my setup thinks I am on a Sony Vaio laptop ! should I be worried? can I change it somehow? -- Paul Cartwright Registered Linux user # 367800
participants (4)
-
Alexandr Malusek
-
BandiPat
-
L. Mark Stone
-
Paul Cartwright