It could be a bug in the kernel modules 'acpi' and/or 'apm' or the daemons that work with them, acpid and/or apmd. You can find out by temporarily disabling them.
Reboot the machine, and when the grub menu appears, press "e" to edit the boot configuration. On Ubuntu-based distros you may have to hold down the SHIFT key after the computer's POST messages to get to the grub menu, keep SHIFT held down until you see the menu. Don't worry, what you change here will only apply until the next reboot. Once in the edit screen, find the line that starts with "linux" and has things like "ro splash quiet" and other stuff in it. Move the cursor over to somewhere after "ro" and type in:
acpi=off
or if on a laptop:
noapm
Then press F10 to continue booting. If your screen blanking stops, you've found what's triggering it. Note though that these modules control other power features too, so you may need to keep an eye on your system behavior to see if anything else goes a bit wonky before adding it permanently to /boot/grub/grub.cfg. It also wouldn't hurt to open a terminal and run "dmesg | less" to look at the system log to see if anything is having problems because of these modules being turned off.
You can find info on these modules in your '/usr/share/doc/' folder that may be of some help.
Reboot the machine, and when the grub menu appears, press "e" to edit the boot configuration. On Ubuntu-based distros you may have to hold down the SHIFT key after the computer's POST messages to get to the grub menu, keep SHIFT held down until you see the menu. Don't worry, what you change here will only apply until the next reboot. Once in the edit screen, find the line that starts with "linux" and has things like "ro splash quiet" and other stuff in it. Move the cursor over to somewhere after "ro" and type in:
acpi=off
or if on a laptop:
noapm
Then press F10 to continue booting. If your screen blanking stops, you've found what's triggering it. Note though that these modules control other power features too, so you may need to keep an eye on your system behavior to see if anything else goes a bit wonky before adding it permanently to /boot/grub/grub.cfg. It also wouldn't hurt to open a terminal and run "dmesg | less" to look at the system log to see if anything is having problems because of these modules being turned off.
You can find info on these modules in your '/usr/share/doc/' folder that may be of some help.
Comment