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 compiled a new kernel (2.4.20) to get rid of the bloated stick 2.4.18 that came with the original installation (slack8.1). well, i'm sure it was just a stupid mistake on my part, but since i started running the new kernel, my console resolution is back to the default size (low) which isn't really a big deal, but i'd like it to be back at 1024x768x256 so i can keep up with IRC chat and lynx. everything else works fine, but does anyone know what i may have left out when i configured the new kernel?
just go into kde...then the control center, then lilo, then you can change back to the way you like it. I personally use fluxbox..but kde comes in handy when you need to do some things...im sure you could just reconfigur lilo also but that way is probably easier.
yeah, i forgot to mention that i'd already checked my lilo.conf file and it's in proper order. that was what led me to assume it's something i forgot to add into the kernel.
ok..i just looked in my lilo.conf and its pretty self explanatory on how to change it...never really looked in there so thats why i recommended the kde way. So jsut where it says vga=normal...change it to vga=791.
I also just moved up to the new kernel, but I haven't had any problems with the console. I don't remember doing any specific kernel option when I compiled.
I'm not sure if it helps, but I found this in the man page for lilo.conf:
----
vga=<mode>
This specifies the VGA text mode that should be
selected when booting. It may be specified as a
global option. The following values are recognized
(case is ignored):
normal: select normal 80x25 text mode.
extended (or ext): select 80x50 text mode.
ask: stop and ask for user input (at boot time).
<number>: use the corresponding text mode. A list
of available modes can be obtained by booting with
vga=ask and pressing [Enter].
If this variable is omitted, the VGA mode setting
contained in the kernel image is used. (And that is
set at compile time using the SVGA_MODE variable in
the kernel Makefile, and can later be changed with
the rdev(8) program.)
thanks for the replies. i've checked over my lilo.conf file and made sure the proper settings were entered as far as the vga=773 entry. i went back into the kernel config and under Console drivers, i see the box for Frame-buffer support, but can't access it. i have VGA text console selected and i've tried selecting Video mode selection support, but still can't access the Frame-buffer support tab. here's a screenshot to better show what i'm talking about:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.