THIS POST IS INTENDED MAINLY FOR NOOBS AND MODERATE USERS FOR THE EXPERIENCED LINUX GURU ONE CAN SKIP TO THE CLI FIX IN UBUNTU SECTION
However, even though it might seem that the CLI fix is the most elegant, it may not, actually, solve the problem if it is a combination of things and not just "the monitor"
WOODSMOKE DETESTS THE TERM NOOB AND ANY DERIVATIVE THEREOF.
However, even though it might seem that the CLI fix is the most elegant, it may not, actually, solve the problem if it is a combination of things and not just "the monitor"
WOODSMOKE DETESTS THE TERM NOOB AND ANY DERIVATIVE THEREOF.
This situation appeared when I built my Blue on Blue computer which is very state of the art hardware.
What is observed upon startup more completely stated.
HP w2007 1680 x 1050 DVI monitor.
a) turn the computer on.
b) one see a black monitor
c) one sees "no video input" with, in this user's case the "rgb" color box
d) one sees "monitor going to sleep".
Turning the monitor on or off produces no result
A push of the button to restart gives NOTHING.
A shut down and start DOES... produce...
a) the monitor becomes active
b) the keyboard wakes up
c) the mouse wakes up.
d) A BLUE SCREEN appears with, in this user's case a KDE wallet requestor for a password ( for this user).
e) the normal wallpaper appears.
The first thing to do, of course, is to check Kubuntu forums, "better than toast with premium jam" !!
No joy so move on to the great world wide web AND if there is not an obvious discussion about "Linux" maybe there are some hints in Windblows fora.
BELOW are given:
I) the "hint"found in Windblows fora...
II) the possible Ubuntu fix not tried by the old woodsmoker
III) the Kubuntu fix.
I) THE HINT FROM WINDBLOWS FORA:
This is a problem for HP monitors and Windblows going back for several years.
BEWARE THE HP paid trolls!!
Just as with the problems with their printers, there are a LOT OF paid HP trolls who spend a lot of forum posts muddying the water by posting that...
a) there is a power supply problem!!
b) there is a power cord problem!!
If I had cared to copy and paste the replies to people that their problem with their HP printer is not HP's problem but instead it is that:
the USER has a power cord that is...TOO LONG... or "not plugged in securely..."...
OK...the COLOR CARTRIDGE is not producing the correct color and it is a problem of the power cord being too long...
OK...the monitor is not waking up and it is a problem in the MOBO power supply!
And what do the USERS reply? ...dozens of replies that they power cord is not loose, or too long or not powerful enough...
So just what IS the problem?
Apparently, the problem is the interaction with the video card DRIVERS and the interaction between the monitor and the video part of settings either in the BIOS or in Windblows settings.
The first knee jerk solution is that the USER has to go to HP and NVIDIA and WHOEVER to "update drivers"...
USING ANOTHER MONITOR...lol...
PLEASE NOTE THAT...the USER needs TWO MONITORS...to fix the problem...
b) there is a power cord problem!!
If I had cared to copy and paste the replies to people that their problem with their HP printer is not HP's problem but instead it is that:
the USER has a power cord that is...TOO LONG... or "not plugged in securely..."...
OK...the COLOR CARTRIDGE is not producing the correct color and it is a problem of the power cord being too long...
OK...the monitor is not waking up and it is a problem in the MOBO power supply!
And what do the USERS reply? ...dozens of replies that they power cord is not loose, or too long or not powerful enough...
So just what IS the problem?
Apparently, the problem is the interaction with the video card DRIVERS and the interaction between the monitor and the video part of settings either in the BIOS or in Windblows settings.
The first knee jerk solution is that the USER has to go to HP and NVIDIA and WHOEVER to "update drivers"...
USING ANOTHER MONITOR...lol...
PLEASE NOTE THAT...the USER needs TWO MONITORS...to fix the problem...
BUT...the real situation SEEMS TO BE... when the COMBINATION of Windblows/HPdrivers/Nvidiadrivers have set the monitor to...go to sleep.
Changing the sleep setting in Windblows, and / or maybe the monitor itself to "not go to sleep" APPARENTLY fixes the problem.
Another possible real fix for Windblows might be in the BIOS itself but pressing DEL or F8 and seeing all that STUFF that is in the GUTS of it...might...just...maybe...strike fear in the heart of the normal Windblows user...but the sleep setting for the hardware itself can be changed there.
II) THE POSSIBLE UBUNTU FIX ( also Kubuntu if one wants to do cli)
Apparently there is a setting for "brightness and lock" in pure Ubuntu which when changed to "monitor to not go to sleep" or something, MIGHT fix the problem.
There are also various scripts, which I have NOT tried, that will permanently fix the situation about the monitor "going to sleep" such as adding this to the "startup".
sh -c "sleep 30; xset -display :0 s off -dpms"
III ) The Kubuntu fix
I have tried various combinations and permutations for this but basically this is the fix for my particular system.
a) in Energy Saving change "screen energy saving" in Switch Off After "some large number", the old woodsmoker set it to 30 minutes. (to fix the monitor going to sleep too fast)
b) change the display manager to "xrender" ( to fix the blue screen)
Please compare the "30" minutes to the script specifying 30 minutes
Noooowww... whether it is "one" OR the "other' the old woodsmoker does not yet know.
THE OTHER SITUATION... MIGHT BE... THAT IT REALLY IS A HARDWARE PROBLEM IN THE BIOS.
SINCE THE SITUATION IS ON NEW COMPUTER METAL IS THAT THE BIOS COULD BE CHANGED TO FIX THE PROBLEM. THAT HAS NO BEEN ATTEMPTED AT THIS STAGE FOR THE SIMPLE REASON THAT "NEW" PEOPLE MIGHT BE HESITANT ABOUT CHANGING THE BIOS...
ALSO IT WILL TAKE MANY MORE STARTINGS AND STOPPINGS OF THE COMPUTER TO DETERMINE JUST PARTICULARLY WHAT IS GOING ON.
IF IT APPEARS THAT IT IS A BIOS SITUATION THE WOODSMOKER WILL SO POST IN THE FUTURE.
AND...
IT COULD ALSO BE THE VIDEO CARD WHICH WOULD REQUIRE TRYING OUT THE DIFFERENT DRIVERS FOR IT... AND AGAIN, GETS INTO THE CHANGE TO XRENDER AS OPPOSED TO THE OPEN gl DRIVERS..
It will take a lot of shutdowns NOT RESTARTS and startups to "maybe" determine if it is a combination of the two or if one or the other will fix the problem.
It is the old woodsmoker's initial thought that it is the 30 minutes to sleep is the situation with the monitor not waking up.
It is ALSO the old woodsmoker's initial thought that the 'blue screen' is involved with using the Open GPL drivers as opposed to xrender. it is possible that with this particular hardware configuration the "new drivers" do not interact well AT STARTUP ... the blue screen and then after interaction with something like Kwallet the background appears.
ANOTHER POSSIBLE CONCERN FOR SOME USERS... IF ONE DOES NOT HAVE SOMETHING SET TO START UP WITH WHICH ONE HAS TO INTERACT... it might be that one is stuck "at a blue screen"...the old woodsmoker DOES NOT KNOW...
The old woodsmoker DOES NOT KNOW...only time will tell.
+ + + + +
LAST NOTE:
It could be that it is a problem with the bios, the video card AND the monitor!
The fix using the sleep setting in Settings AND the change of xrender WOULD SEEM...AT FIRST BLUSH... to possibly fix either "the one problem( not determined at this stage) OR... the COMBINATION of problems... again...yet to be determined.
The permutations of this are: a) cpu bios b) video card c) monitor firmware d) video drivers e) sleep setting thusly a LOT of turning the computer on and off and changing settings...# combinations = half a jillion!
so...if anyone has had this problem, or a similar problem and a possible fix, please so post.
woodsmoke