Eberhard Moenkeberg wrote: > The general policy with LCD displays HAS TO be: "lowest frequencies" at > recognized resolutions.
> I.e. [EMAIL PROTECTED] or [EMAIL PROTECTED] for example. No higher > frequencies during > the installation phase please, or give the user a choice. > Currently the only chance for a user in that situation is to use a lower > resolution (I have learned to always use 800x600 to survive), but this affects > readability in a bad manner. Totally unnecessary. I do agree 100% regarding this long time, stupid "Monitor out of range" problem. I also filed this a bug or RFE during the previous 10.x beta, but got replied that this wouldn't be fixed (hardcoded info or something!?). And this problem has existed as long as I've used SuSE based distros, i.e I did encounter this on Sun Java Desktop system based on SLES8.1, on SuSE 9.x Pro and latest 10.x. My Viewsonic VP191b LCD manages [EMAIL PROTECTED] Checking with the F key on the first SUSE installation screen shows that the correct 1280x1024 resolution is set. But if I continue with this, soon after the monitor runs "Out of Range" and one have to start from scratch again. The reason I've found out is that the frequences is set too high, 85 Hz which my monitor cannot manage! The only workaround (for us that know it) to come further with the installation is to manually change to the lower 1024x768 resolution. I verified this earlier during the later, listed hardware configuration, where the monitor was set to [EMAIL PROTECTED], and had change it to (LCD) [EMAIL PROTECTED] (SaX2) before finishing the configuration. And now this does not only affect SUSE distros. The new GUI installation of the latest Ubuntu 6.0.6 (which for me looks to mostly have copied SUSE's first installation screen), does cause the same Monitor out of range problem! On the other hand, when I previous installed SkoleLinux based on Debian's text menu's on the same hardware, no monitor problem arised. Login to KDE after this installation showed that the correct [EMAIL PROTECTED] had been set. So obvisiously it looks to be possible to grab the right values. Rgds, Terje J. Hanssen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
