OpenSUSE :: Monitor To Stay On For Long Periods Of Time?
Dec 1, 2009
I am useing a PC as a simple display and I need the monitor to stay on for long periods of time. I have set the power saving setting to "presentation" mode and it is not supposed to turning the monitor off. Is there somewhere else I need to adjust this??? I am running OpenSUSE 11.1.
It takes me a while to log in the splash screen just sits there for ages before i get to the desktop. Never used to be this slow and I'm not sure why. Firstly, I'm running Ubuntu 11.04, standard DE. I do have conky starting up in a script but it has the & at the end of the line so I didn't think this would cause it (or is there some special case for log in time on how & is treated?). However as a test I will comment out the line in the script and see if it is the cause.
However just for general knowledge and in case that isn't the problem, how does one go seeing what is happening during the time from when one log's in and the desktop is displayed? Is there some kind of log that shows the date/time that can be enabled or is there a debug mode that can be enabled somehow via special keys or maybe from grub?
This has happened in natty more than once. Once the screen gets locked after long periods of no keyboard/mouse activity (all ok for short periods of time), I don't even get back the familiar unlock screen with password.I get a blank screen and then Io a ctrl-alt-f7Is this a known issue in natty? Or is this a gnome bug
The CPU frequency scaling monitor won't stay at 800mhz after reboot or a certain period of time. My goal is to always have my dual core CPU locked at 800mhz to have it run cooler. I'm running Ubuntu 10.10 on my toshiba u300 laptop.
I am running Centos 5.3. I ran no updates, performed no installs, nor changed any configuration immediately prior to this issue. My problem is this: when I run the command startx (default runlevel 3), it is a long time (5-10 minutes) before Gnome startx, and once it does start applications will not run. Also, when I try to use sudo (from any environment, even ssh), it is a long time (5-10) before the command is executed.
I cannot say for sure, but it seems like this is an intermittent problem. Sometimes X takes a long time to start, but once it starts it will launch programs. Sometimes X takes a long time to launch, but once it starts it will only launch certain programs. Though presently X always takes a long time to start, and I cannot successfully launch any programs.
A while back a had a similar problem to this (x taking long time to start, sudo taking long time to execute) and it ended up being a DNS problem. Unfortunately, I cannot remember exactly what it was and I stupidly did not document it. Maybe this is also DNS related, I don't know.
I don't know what log files to look at for problems with X, Gnome, and sudo taking a long time to start.
When I turn on the computer, it connects to wireless automatically. That's good. But it doesn't stay connected very long. Especially if I turn on a p2p program or make a call through messenger. Then I get disconnected suddenly and if I want to connect again it doesn't work anymore. Network - You are now disconnected and that's it. Every time it happens I restart the system. I use an Acer Aspire 5738z laptop.
Sometimes I get this weird thing where typing a name into the kickoff menu hangs after a few letters. It hangs the entire computer! Once it happens, I try to close it but have to wait about 20 seconds before I can do anything on the computer. Then everything else works fine (after it's closed). But if I go back to kickoff and try again, it does the same thing! I can't seem to find anything in "top" to indicate what's happening.
openSUSE 11.2 KDE 4.3.4 Linux 2.6.31.8-0.1-default i686 AMD Sempron(tm) Processor 3100+ 1.8 GHZ nVIDIA G98 GForce 8400 GS with nvidia driver
Here's "top" during a recent issue where konqueror wasn't opening to show sysinfo and there was some hanging (although this was after it came back from kickoff hanging) code...
Shutting down my machine takes a very long time! Not convenient when one want to pack his laptop (I don't dare to when the fan is still blowing).
Upon shutdown, I press 'esc' and see what's happening. The last commands seem to hang. First, shutting down the network interfaces seem to last long than needed (eth0, pan0, wlan0). Sometimes, it stalls also on "networkmanager disconnecting from DBUS" (or something like this ) (which is the very last command executed). Hmm, I will write the exact command down.
My ISP offers the service of native IPv6. So my ADSL router provides me with a local and global IPv6 address. However after a reboot it takes minutes to finally see the global address when using "ifconfog eth0". During that time I can't do a ping6 to an external server, which seems logical. So I waited several minutes, but no global address. After that I started a KDE session, went back to the console(<Ctrl>+<Alt>+F1) and now the global address was there. Is this normal behavior or should I file bug report?
When booting Fedora 11, my system hangs for a very long time on starting udev. Sometimes I get an I/O error. However, my hardware is fine. I do eventually get in to the system.
I frequently turn my monitor off (e.g. during downloads). Usually,
Code:
works great for this purpose, but on my new Thinkpad W520 with Fedora 15 the monitor won't stay off but come back after a few seconds. This is rather annoying. Does anybody have an idea how I can make it stay turned off? Oh yeah: Pad is deactivated, only trackpoint is active.
For example, I have a script that writes the time to a pipe in /etc/pipe. It writes continuously in a while true loop. How long will the data in the pipe be available for reading? If I only decide to read the pipe a day later with cat /etc/pipe, will I get all the time values right from the time I started writing?
Conversely, what if my loop only wrote the time every 10 minutes. Will I be able to access everything a day later?
Finally, pretend my loop writes the time continuously (like my first example) and I read the pipe every 30 minutes. If my computer shuts down right before I read the pipe, will the pipe be empty when I reboot or will it hold all that data?
I have a Fedora 11 server that runs at init 3, the monitor goes out after awhile. I would like this to be on permanently. I've searched the net and I'm not able to find the answer.
VGA compatible controller: ATI Technologies Inc RV350 AR [Radeon 9600] (prog-if 00 [VGA controller])
I'm having this problem with a older ibm thinkcentre with some:00:02.0 VGA compatible controller: Intel Corporation 82915G/GV/910GL Integrated Graphics Controller (rev 04) video controller in it.
The problem is the monitor connected has to stay on all the time, but something keeps shutting down the video card then the machine has been idle for some time, and the monitor goes "No video signal" until someone touches the mouse or keyboard.
The system is the newst updated 9.10, and ive set "Put monitor to sleep = never" in the power management settings. Ive also disabled the screen saver.
Now, i dont think its Xorg that shut the video card down, i believe its the framebuffer (or kernel console or whatever its called). If i jump to the console with ctrl-alt + F1, log in and turn off Xorg with lets say sudo service gdm stop, the video card still turns off after like 15-20 minutes.
Other things ive tried: completely disabling framebuffer in the grub configuration (with vga=normal and nofb and even combining both, this however doesn't really disable the high resolution framebuffer at all. Its still on now matter how much i try to disable it..hmm (and the grub settings is used by grub as I'm able to set nosplash witch is effective))
and the last thing I've tried was setterm -powersave off, no luck there.
Before thinking it may be the console doing the video poweroff, I tried disabling DPMS in Xorg config, (and disabling it with xset) this dosent help, although i'm able to turn on the video signal again from a ssh session with xset -dpms -display :0.0 or xset dpms force on -display :0.0. However after some idletime the video signal shutsdown again.
I could easily go to ms system monitor display by clicking on background of desktop and finding it through there to change settings related to desktop. I want to be able to watch a movie without the desktop screen saver thing going off. where can extend it to longer than 2-3 minutes on linux mint?
I have installed "open-SUSE 11.4" on a "500GB Free Agent External Hard Drive". I didn't have any problem in booting since last week that I booted it from my laptop. Also I did it before several times from then when I try to boot it e.g. from an "Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz" PC the time between loading INITRD and starting boot sequence messages lasts nearly 30 minutes!(i didn't actually measure it but it take a long time in the same order). after starting boot sequence which is showed on monitor everything looks normal. e.g copy of files would be done by speeds between 2MB/s to 30 MB/s depending on the targets.I used to use the external hard derive to boot from different laptops and PC's from start but I didn't have such a problem anytime.
Running Ubuntu 10.10 on Hp Mini 1030nr My wireless card is a Broadcom BCM4312. I have the b43 driver installed. When I disable networking I can change to monitor mode but then it changes back to manage mode when I enable networking again. I tried using airmonNG but it;s not working.
Currently I have two 1920x1080 screens running in Twinview on my Geforce 275 graphics card. Want I want to do is a quick simple way of disabling my secondary monitor when playing video games or using xbmc to watch movies, etc. I've tried a few applets but they require the xandr function which I think Nvidia doesn't support.
Is there a way to disable this quickly other than loading up nvidia-settings and disabling the monitor everytime. I don't really want to use two seperate x sessions and xinerama due to the fact you can't use compositing.
The desktop stops working, the panel stops working.. but compositing, desktop cube etc all work fine.I can still launch a program with Alt-F2.When I try and kill it (to restart) using 'killall plasma' / 'kill -9 <pid> / 'kill -15 pid' from a terminal, nothing happens, the process keeps running. If I leave it for about 30 mins it suddenly dies, allowing me to run 'plasma' from a terminal - then everything is back to normal.
If I log out and try to log back in again, I get a black screen. Only way to fix it is either to kill it and wait for 30 mins or so, or totally reboot the computer.Tail of the xsessions error file:
I am trying to install rhythmbox-0.13.1.tar.gz in my fedora 10 for a long time but i am in vain I downloaded it and i put it in my desktop.Then i did this:
# cd ~/Desktop # tar -zxvf rhythmbox-0.13.1.tar.gz Doing this a new folder named tar -zxvf rhythmbox-0.13.1 is created in my desktop. then i did this: # cd rhythmbox-0.13.1
I am using Fedora 15 KDE 32-bit. I am facing a problem while shutdown. It takes unusually long to shut down. It reaches the blue screen with the fedora logo within a few seconds, but it stays on the blue logo screen for 2-3 minutes before shutting down. However, I am facing no problems during startup.
About suspending F15 KDE. It goes into suspend successfully but after switching on after suspend, it just shows an unresponsive black screen.
Is anyone else facing the same problem and has it been solved before? Because I haven't come across many posts regarding F15 KDE.
in ubuntu 10.04 After logging in t All I had was the wallpaper & my widgets for around a minute, and then the usual upper and lower panels appeared.. didnt had this problem in 9.10
After I installed a new hard drive, when I booted up into Ubuntu, it would give me this error: "failed command: WRITE DMA". So I tried the workarounds and I guess it just covered the log with the Boot Splash, now it's taking a long time just to boot up.
My machine is taking ages to get from the login screen after booting to actually showing the gnome desktop (as in, over a minute). The bootchart is at golg-lucid-20101111-1.png
I'm having trouble with Vim in any terminal emulator I use. I have a link (vi) to vim. Occasionally it will take very long to load, whether I use 'vi' or 'vi file'. Before, if I could I would restart X, and then it would load instantly again, but I waited this time and it did load, after a minute or so. Is this a problem with X or vim?
LDAP Server => CentOS 5.5 Configured according to this link [url]
LDAP Client => Fedora 14 Configured according to this link [url]
Now after I reboot the Fedora14 during startup, it takes very very long time to start up the mdmonitor service.
After that when I log on using a local account in the Fedora14 machine, it takes painfully long time to log on. And it does not identify the domain user.
I can able to log on to the ldap server through ssh from the Fedora machine.
I issued the command 'getent passwd' which does not fetch the domain users either. I am completely lost now.
i got intel inside. when grabbing windows and moving them around they "streaked "(right word ?) over the monitor. Desktop-experience was simply "sluggish". I searched for all kind of info on this board. e.g.: installed preload, intel-microcode, set Xwrapperconfig to -1; -5, -10. tried some changes with swappines and cache_pressure in sysctl.conf. without knowing what it might be good for i ran prelink -a. For about a week it simply rocks: all is "sharp" and clean, including the move of windows. How come? does preload take such a long time ( a few months) to give such an amazing result? Is it related to graphics at all? I upgraded to ext4 bout 4 weeks ago (which takes a while too, from what i have read). intel-microcode doing magic? With the money i got chances are high that the pc`s i buy are intel-inside ones. and with a build-in graphics-card