rfaulk69906 Posted November 10, 2003 Report Share Posted November 10, 2003 Hi, I had this same exact problem with 9.1. If I leave my computer for even a minute without doing anything the monitor goes black. There is nothing I can do to get it back. I end up having to turn the power strip off the computer is plugged into and then doing a reboot. In 9.1 this problem was fixed by installing the ACPI and ACPID packages and setting them to run when everything booted up. I also had to edit my lilo.conf file so that ACPI was turned on. I tried doing this in 9.2 and it does not work. I tried updating the kernel and that did not help either. Neither did installing all of the updates for 9.2. Quote Link to comment Share on other sites More sharing options...
Cannonfodder Posted November 10, 2003 Report Share Posted November 10, 2003 Do you have a screensaver or power saver running Try disabling these features.. You can also try turning off power saving in your bios.. Quote Link to comment Share on other sites More sharing options...
rfaulk69906 Posted November 10, 2003 Author Report Share Posted November 10, 2003 Hi, I went into the KDE control center and disabled the screen saver. I also went into power control and turned off enable display power management. Here are the options I have (and their current settings) under Power in my Bios. Enable ACPI is set to yes. Auto Suspend Timeout is off. Resume on modem ring is off. Remote power on LAN is disabled. Power button function is set to sleep/wake. I have tried turning ACPI off. When I did this I also changed my lilo.conf file accordingly. When this did not work I went back into the Bios and turned ACPI back on. I then adjusted the lilo.conf file again. Neither of these worked. I also changed the Power button function in the Bios to on/off, but that had no effect either. I am going out of town with my job for several days. So it will be Wednesday or Thursday before I can try anything else. I will still be able to check and see if anyone has any other suggestions. Thanks in advance. I'm also going to post my lilo.conf file to see if that helps. boot=/dev/hda map=/boot/map default="linux" keytable=/boot/us.klt prompt nowarn timeout=100 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz label="linux" root=/dev/hda5 initrd=/boot/initrd.img append="devfs=mount hdc=ide-scsi acpi=on resume=/dev/hda6" read-only image=/boot/vmlinuz label="failsafe" root=/dev/hda5 initrd=/boot/initrd.img append="devfs=nomount hdc=ide-scsi acpi=on resume=/dev/hda6 failsafe" read-only other=/dev/hda1 label="windows" table=/dev/hda other=/dev/fd0 label="floppy" unsafe image=/boot/vmlinuz-2.4.22-21mdk label=2422-21 root=/dev/hda5 read-only optional append=" devfs=mount hdc=ide-scsi acpi=on resume=/dev/hda6" initrd=/boot/initrd-2.4.22-21mdk.img Thanks, Ron Quote Link to comment Share on other sites More sharing options...
roland Posted November 10, 2003 Report Share Posted November 10, 2003 Just a little question just in case, does not hurt .. I hope :) didn't you forget to run lilo after having modified lilo.conf ? roland Quote Link to comment Share on other sites More sharing options...
rfaulk69906 Posted November 11, 2003 Author Report Share Posted November 11, 2003 Hi, I saved the lilo.conf file after I edited it. I then opened a termial entered su and put in my root password. I then entered lilo -v. I did this everytime I edited the file. What I posted earlier is what the file is right now. Thanks for the suggestion. Any other ideas? Quote Link to comment Share on other sites More sharing options...
bvc Posted November 11, 2003 Report Share Posted November 11, 2003 try man xset this xset s off s noblank dpms 0 0 0 will turn everything off, so that all stays on. Quote Link to comment Share on other sites More sharing options...
rfaulk69906 Posted November 12, 2003 Author Report Share Posted November 12, 2003 Thanks for the reply bvc. I'm out of town right now and will not have access to my Linux box until either Wednesday or Thursday night. I'll give that a shot and post back with the results. Sounds like that should work. Thanks again. Ron Quote Link to comment Share on other sites More sharing options...
bvc Posted November 12, 2003 Report Share Posted November 12, 2003 you mentioned kde above, so, if it works, then make a file called (whatever.sh) apm.sh and put xset s off s noblank dpms 0 0 0 or whatever you come up with in it. Then put it in ~/.kde/Autostart so the full path to it is ~/.kde/Autostart/apm.sh Now, when you login to kde it'll be set. Quote Link to comment Share on other sites More sharing options...
Cannonfodder Posted November 12, 2003 Report Share Posted November 12, 2003 You can also try editing your XF86Config-4 file and comment out the line related to VIDEO4LINUX (something like that). Used to be an 8.1 bug where the screen would go black. Backup the file first before changing. This is a far shot though.. Quote Link to comment Share on other sites More sharing options...
spiedra Posted November 13, 2003 Report Share Posted November 13, 2003 When I had this issue, I found it was standby that was causing the problem and not and not the other modes. I would try disabling standby first before editing. It's good to start easy then go upwards. Quote Link to comment Share on other sites More sharing options...
Daveleh Posted November 13, 2003 Report Share Posted November 13, 2003 If I leave my computer for even a minute without doing anything the monitor goes black. Mine has a tendency to go freeze during the initial boot, whilst all the services get started and the (OK)'s get printed down the right hand side. The only thing I can do when this happens is remove power from the PC. Not been able to pinpoint exactly when it does it yet. I'll post more when I do :sad: Quote Link to comment Share on other sites More sharing options...
rfaulk69906 Posted November 14, 2003 Author Report Share Posted November 14, 2003 I had previously gone into the KDE Control Center and unchecked the box for enable display power management. I went back and checked the box. I then changed all of the options to disabled and that fixed the problem. Thanks for all the help and I'll post back if the problem reoccurs. Ron Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.