> SUSE does not like my iiyama ProLite E1908WSV monitor. Native 1680 x
> 1050 returns this error:
>> ATTENTION SIGNAL FREQUENCY IS OUT OF RANGE
>> H: 66.8KHz V:61.3Hz
>> PLEASE CHANGE SIGNAL TIMING
> All other resolutions look cack & boot/shut down screen default to
> error state. I could get round this on live CD by booting into the
> safe kernel option.
> I have to report bug against a SUSE system component.
did you follow the link provided by Per Jensen?
if you did, as i just did, i don’t see where any question requires an
input on any “component”…
you should begin by searching to see if you bug has already been
then, the next step begins by clicking on “Enter a bug” where i see
“Classification (Product Line):” and a list of products, do you know
the name of the product you are having trouble with–i ask because you
do not name it in either of your posts…
are you running openSUSE or SUSE Enerprise Linux or or or??
maybe you are working in a different language than English…or the
page they show me is different from yours…but, i see no “component”
finally, i got far enough into the process to see the component question…
heh! i see on this page http://tinyurl.com/2vm9xcq
the developers want YOU to tell them a level of detail about the
problem that neither you nor i might know as a user!!
BUT, i also see a link you could click on, immediately following the
window where you are to make a “component” choice is a line of HELP:
“The area where the problem occurs. To pick the right component, you
could use the same one as similar bugs you found in your search, or
read the full list of component descriptions (opens in new window) if
you need more help.”
so, when you searched the list of existing bugs what component turned
up? (i would have searched using the terms you used in your first
post: signal frequency out of range, change signal timing…which now
turns up your bug
I’m WAY to slow to think of that! Erm, total newb but no excuse, after all Windows needs drivers depending on setup. Whoops. Before you cast me off in disgust, how do I do that or is it a case of RTFM?
> init 3
> entered into CLI as per guide is not working, am I doing it wrong?
when you say “not working” what does that mean? nothing happened? it
threw up an error message? (what error message)
WAIT! the guide you found assumes you know more than you apparently do
(it assumes you know that to issue an “init 3” at a command line and
have that cause closing of X will require you to be the super user)…
so why not try using THIS guide which is a little less demanding of
highly polished Administrator knowledge: