2005/10/10, Alain Black :

Jukka wrote:

...

Hi!

I have had a strange malfunction with my monitor since I started to try OpenSuse Beta's. My monitor looses it's signal every time during boot: it goes blank, starts blinking a message informing current horizontal/vertical sync-rates and if "pc-settings are correct"? Only way to get it back to normal is to start pushing buttons in monitor "adjusting-panel" and keybord. This blanking happens also during normal use (after the boot process) if there has not been any activity (keyboard presses, mouse clicks etc) for a while. I have checked monitors refresh rates via Sax2 but despite they are correct, this goes on. This doesn't happen in Windows (I dualboot with Win98SE), nor with Suse 9.3 (or older releases) or other linux distributions. Any idea what may be a problem? My monitor is Hitachi CM715.

-Jukka

It sounds like either the refresh rate or the resolution is too high. Try changing it to 1024x768 or 800x600 in sax2 and see if that helps.

Hi! Thanks for your tip! I try it next time I am at home (writing this from work), but refresh rate is correct (according to monitor manual) and my past experiences with Suse (I have used it since version 7.1), with other linux distributions and with Win98 has had no problems? Even it would work, I think it is not a solution because monitor is capable for 1600x1200 resolution?? -Jukka

2005/10/10, houghi :

On Mon, Oct 10, 2005 at 09:40:44AM +0300, Jukka wrote:

...

Thanks for your tip! I try it next time I am at home (writing this from work), but refresh rate is correct (according to monitor manual) and my past experiences with Suse (I have used it since version 7.1), with other linux distributions and with Win98 has had no problems? Even it would work, I think it is not a solution because monitor is capable for 1600x1200 resolution??

Look at the refresh rate. f it is set at 85, perhaps 75 will work. I used to have a CRT monitr that could do 1600x1200, but I had to go to a lower refreshrate then if it were at 1024x768 even though the manual did not mention this.

Just start with the lowest possibilaties and work your way up.

houghi

Problem solved! Monitor/model was not recognized automatically until OpenSuse (so I thought everything should be right after the installation) but when I checked values again, I realized that only *model* was right, but manufacturer was not (it should have been "Hitachi", but it was "HTC" - I suppose that means something else than Hitachi??). I entered windows INF-disk ("Hitachi Monitor INF Disk for Windows) and everything seems to work now. Should I report this to someone? -Jukka

Hello, Am Montag, 10. Oktober 2005 11:06 schrieb Jukka:

2005/10/10, houghi :

...

On Mon, Oct 10, 2005 at 09:40:44AM +0300, Jukka wrote: [...] Problem solved! Monitor/model was not recognized automatically until OpenSuse (so I thought everything should be right after the installation) but when I checked values again, I realized that only *model* was right, but manufacturer was not (it should have been "Hitachi", but it was "HTC" - I suppose that means something else

I'm not sure about that. It could also be a short name and a wrong monitor information in SUSEs database.

than Hitachi??). I entered windows INF-disk ("Hitachi Monitor INF Disk for Windows) and everything seems to work now. Should I report this to someone?

Yes, please add it to bugzilla. The category depends on how you [tried to] setup your monitor - it could be "Installation", "YaST" or "sax2" ;-) If you didn't use sax2 to do the (not working) configuration, please also try sax2 -r and check if it has the same bug. It may be a good idea to backup your working xorg.conf before doing that ;-) Oh, and please append the working INF file from your monitor's disk to the bugreport. Regards, Christian Boltz -- [16x *PATSCH*]

Gerade du solltest wissen, dass man keine Domains missbraucht! [...] Sorry David, ich gelobe Besserung, aber bitte keine Schläge mehr ;-) [> Manfred Tremmel und David Haller in suse-linux]