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.
First of all, let me explain my set up. I have Red Hat 8.0, Slack 9.1 and Win98 all running on the same PC. My bootloader is GRUB, which boots direcrly to Red Hat and Windoze, and boots to LILO to load Slack. For Christmas, I got an HP vs17e flat panel monitor. Installing it opened up issues in both Red Hat 8.0 and Slack 9.1. When I started Red Hat, the GNOME log-in window came up and the monitor informed me that I needed to readjust the horizontal freqyency settings. After displaying this message for a few seconds, the monitor entered sleep mode. I ran x86config and now all is well. Slackware is another story. It will not boot-up on its own from LILO. It starts to, then the screen goes blank and the monitor gives the error message telling me to reset my screen resolution and the system halts. I can boot using a CD-ROM without incident and have done so and reconfigured X. Now that I reflect on the problem, it seems to be a LILO issue. Could this be? What can I do about it? Any suggestions would be appreciated.
Distribution: BeOS, BSD, Caldera, CTOS, Debian, LFS, Mac, Mandrake, Red Hat, Slackware, Solaris, SuSE
Posts: 1,761
Rep:
Quote:
I ... and reconfigured X.
What did you reconfigure? After the changes, were you able to use 'startx' from the command line and use the GUI?
Quote:
It will not boot-up on its own from LILO. It starts to, then the screen goes blank and the monitor gives the error message telling me to reset my screen resolution and the system halts.
This sounds more like a VESA framebuffer issue than the X server. I suspect you have the VESA framebuffer set to something other than "vga = normal" in /etc/lilo.conf. I suggest you boot to a command line, edit your /etc/lilo.conf to reflect "vga = normal", run 'lilo' command so the changes are made, then reboot.
When I reconfigured X, I reconfigured everything... AGP card, mouse, monitor,etc. That is all a moot point now, because I followed your suggestion and reset vga uder VESA to "vga=normal." For some reason it was set to "vga=271"?!? Anyway after following through with your suggestion, Slack now boots properly. Thank you much. I love this site.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.