SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I recently added a nice looking boot bitmap for my slack system based off of shilo's how-to. Upon doing this, the system no longer shuts off my monitor after a period of time. Without the boot menu, it will do this, but once I implement this boot bitmap, the screen goes blank but does not put my monitor into standby mode. The only thing I changed for this is my lilo.conf file. I will post this as soon as I get access to my box.
Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
#message = /boot/boot_message.txt
prompt
timeout = 100
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
vga=769
map = /boot/map-bmp
install=/boot/boot-bmp.b
bitmap = /boot/lilo2.bmp
bmp-colors = 15,0,0;0,15,15
bmp-table = 478p,219p,1,15
bmp-timer= 575p,445p,0,15,15
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda8
label = Linux
read-only
# Linux bootable partition config ends
You can find driver infos in /var/log with the X logs and in /etc/X11 with the X config.
I suspect that memory of your video card is not cleaned when it pass boot step and free the graphic loaded by lilo, so it can cause problem with monitor as it is connected to it...
It is just an idea that comes in my mind at this time though
And for my part I'd disable the graphic in lilo as it seems fix the problem...
Ok. when I change the setting in my lilo.conf file to "vga=normal", it works. But strangely enough it doesn't with any other VESA settings. I'm running only in console and was playing with different options for setterm last night but didn't come up with anything that worked until I set it back to vga=normal. Thanks for the help Cedrik.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.