Regardless of how I set the power settings, the monitor is dimmed at ~ 5 minutes if the system is idle. How do I make it stay on indefinitely? Disabling the option or setting it to “never” has no effect.
On 2011-04-25 03:06, seekermeister wrote:
>
> Regardless of how I set the power settings, the monitor is dimmed at ~ 5
> minutes if the system is idle. How do I make it stay on indefinitely?
> Disabling the option or setting it to “never” has no effect.
As this is the 64 bit hardware subforum, I fail to see how your problem
relates to it, because you don’t mention what type of hardware you have.
Anyway, you don’t say what openSUSE version you have, and what desktop you
are using. That’s important to try to help.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
As well as the missing DE information, when you say dimmed do you mean dimmer or black/blank screen? If the latter, check that you haven’t got a blank-screen saver set to activate after 4-5 mins.
robin_listas ,
It is an x64 system, running Suse 11.4 x64 on KDE. If you feel that this question doesn’t relate to the x64 forum, then tell me where it does, because as far as I could see, none of the other forums relate to this kind of question, whether x64 or x32.
At the moment, I’m not in Suse, so will have to reboot to check. I have never set a screen saver, and don’t know where to look for it, but I will nose around. Would the installation have set a screen saver by default?
Yes a screen saver will be set
Disable it
FYI: It’s tricky getting kde power settings to work the way you want (especially the screen powersaving)
It now appears that this question is moot, because when I rebooted, I got a “disk read error”, this is the second time that this has occurred in ~ a week. Last time I was able to fix it by doing an upgrade installation, but that didn’t work this time.
It may well have been something that I did wrong, because it said that there were dependency problem that I would have to fix myself, and when I clicked on the software configuration, it displayed a window offering only two solutions. The first was to uninstall what appeared to be the entire x64 installation of Suse, along with ~ 70 other packages, with a mixture of actions. The second was to not install the x64 distro. Neither of these made any sense to me, but I selected the second one. Right or wrong, it continued to display the disk read error.
I was very hopeful about this distro, because I have had far less problems setting up the basic system, than I have had in the past, but I’m far too ignorant about Linux to try to deal with this kind of major problem on a regular basis, so I guess that I will wait for a future version to be released before I try it again.
On 04/25/2011 08:06 AM, seekermeister wrote:
>
> I’m far too ignorant about Linux to try to deal with this kind of major
> problem on a regular basis, so I guess that I will wait for a future
> version to be released before I try it again.
and, if you are serious about using Linux, do some reading of how-tos,
manuals, and documentation so when you try next you have given yourself
a fair shot at being successful…
if you want a list of recommended reading, just ask…until then, nose
around here: doc.opensuse.org
–
CAVEAT: http://is.gd/bpoMD
[openSUSE 11.3 + KDE4.5.5 + Thunderbird3.1.8 via NNTP]
Q: What do you get if you divide the circumference of a jack-o-lantern
by its diameter?
A: Pumpkin Pi!
I appreciate your advise and offer, but while my interest in Linux doesn’t seem to die, regardless of my many problems with it, I’m getting too old to go back to college, or spend endless hours groping my way through manuals just to get a distro to do what it should do straight out of the box.
I would imagine that I could read your entire list of study material, and I still would not know how to deal with that disk read error. I did Google on it some, and from what I could tell, no one knows exactly what causes it, and I found no concensus about how to deal with it.
If you believe otherwise, then instead of a reading list, you should have either stated the solution, or have provided a relevant quote. The lack of either of these leads me to believe that you don’t have the answer, but I do imagine that you would find one, if you needed it yourself.
It now appears that this question is moot, because when I rebooted, I got a “disk read error”, this is the second time that this has occurred in ~ a week. Last time I was able to fix it by doing an upgrade installation, but that didn’t work this time.
This could be the start of a disk failure, which has not yet become catastrophic, or it could be some kind of kernel bug. In any case, I would back up any important data before proceeding with finding any likely caise.
If you believe otherwise, then instead of a reading list, you should have either stated the solution, or have provided a relevant quote. The lack of either of these leads me to believe that you don’t have the answer, but I do imagine that you would find one, if you needed it yourself.
Vague references to problems are not always enough to determine the exact cause of a problem, or its solution. So DenverD, myself,and others can only speculate as to the problem anyway. On that note, maybe you were referring to a grub ‘disk read error’ perhaps?
On 2011-04-25 04:06, consused wrote:
>
> As well as the missing DE information, when you say dimmed do you mean
> dimmer or black/blank screen?
If the system install thought the machine is a laptop, there are utilities
that dimm the backlight after some time iddle when on power, and always or
earlier when on battery.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
On 2011-04-25 08:06, seekermeister wrote:
>
> It now appears that this question is moot, because when I rebooted, I
> got a “disk read error”, this is the second time that this has occurred
> in ~ a week. Last time I was able to fix it by doing an upgrade
> installation, but that didn’t work this time.
Disk errors are not to be solved by an upgrade.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
On 04/25/2011 01:06 PM, seekermeister wrote:
> If you believe otherwise, then instead of a reading list, you should
> have either stated the solution, or have provided a relevant quote.
thank you for your observation of how i should try to help here…
> The
> lack of either of these leads me to believe that you don’t have the
> answer, but I do imagine that you would find one, if you needed it
> yourself.
Sir, you didn’t ask for help with the new problem, instead you said “I
guess that I will wait for a future version to be released before I try
it again” which is just about like: “Goodbye”…
so, why should i think even a minute about the two problems you had
already given up on ?
do i know what the problem is, from here?
No sir…
but i have a hunch…while i have zero idea how right it might be,
because i have NO clue on what kind of hardware you are dealing with there…
but, if that disk is one day past its warranty period i’d advise you to
make your next action to do a tidy backup of all data you want to keep,
to a different disk…
let me start that over: even if your disk is one week old, your next
action should be to ensure continued access to all data on that disk by
moving a copy to another disk.
–
CAVEAT: http://is.gd/bpoMD
[openSUSE 11.3 + KDE4.5.5 + Thunderbird3.1.8 via NNTP]
Q: What do you get if you divide the circumference of a jack-o-lantern
by its diameter?
A: Pumpkin Pi!
I know what backlight dimming is, as I have a notebook with that facility 
The OP hadn’t provided hardware details, PM settings hadn’t worked, and symptom(s) needed clarifying. Best remove confusion by disabling any screen-saver blanking first.