Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
06-22-2005, 09:58 PM
|
#1
|
Member
Registered: May 2005
Distribution: Slackware 10.1
Posts: 49
Rep:
|
Kernel 2.6.12 upgrade and console text size
I could use some help here from you more experienced kernel compilers out there!
I have never done the kernel compile thing before, because I liked knowing that for the most part, the included kernel version was probaby somewhat more stable and secure then the latest. But this time, I was moved to upgrade to the new 2.6.12 kernel for a couple reasons. Namely the new cryptoloop support and the IPSec support.
The compile went great. Much better than expected. I am quite happy [and excited] with the new kernel, as I now have a few more projects to work on now.
But theres one thing I dont like [minor, but nevertheless...]
And that is the fact that unlike the included Slackware 10.1 kernel 2.4.29 which had the nice small text at the console, I now have the 'extra-large' text!
What do I need to do in the kernel to get back the nice small text I am used to? Does that have something to do with the framebuffer options?
Anyways, if someone could give me a hand with what to do under the kernel options to get that nice small text back, I would be very appreciative!
Thanks.
|
|
|
06-22-2005, 10:08 PM
|
#2
|
Member
Registered: Nov 2004
Location: Columbus, Ohio
Distribution: Slackware-Current / Debian
Posts: 795
Rep:
|
compile VESA VGA and Framebuffer support into your kernel.
|
|
|
06-22-2005, 11:48 PM
|
#3
|
Member
Registered: May 2005
Distribution: Slackware 10.1
Posts: 49
Original Poster
Rep:
|
Okay, I did this. And I still have the large console text.
|
|
|
06-22-2005, 11:52 PM
|
#4
|
Senior Member
Registered: Jun 2004
Location: Argentina (SR, LP)
Distribution: Slackware
Posts: 3,145
Rep:
|
What's the value of vga in /etc/lilo.conf?
|
|
|
06-22-2005, 11:58 PM
|
#5
|
LQ Newbie
Registered: May 2005
Posts: 15
Rep:
|
Are they compiled in, or as modules? I *think* they have to be compiled in (there's probably a more technical term for that, but I mean active, but not as a module, you know?) At least, that's how I got it to work in mine.
Last edited by beezlebozo; 06-23-2005 at 12:12 AM.
|
|
|
06-23-2005, 01:27 AM
|
#6
|
Member
Registered: May 2005
Distribution: Slackware 10.1
Posts: 49
Original Poster
Rep:
|
Well, I got it working, the problem was that for some reason, the new kernel wasn't loading after typing LILO. Yes, I compiled those options into the kernel. Problem now, is even though it is finally starting in the proper mode, now it's frezing after it starts! lol!
Well, Im on the right track now anyways. This looks like something Im just going to have to play with.
Kinda funny. Everything works great in the new kernel. But the one thing I am having trouble with is the trivial issuse of the font size. lol! Go figure.
anyways, I'll get this. Thanks for the help.
|
|
|
06-23-2005, 01:37 AM
|
#7
|
LQ Guru
Registered: Mar 2004
Distribution: Slackware
Posts: 6,552
|
If you have a nvidia card, do not enable CONFIG_FB_VGA16
but make sure CONFIG_FB_VESA is enabled (as built-in)
Also did you enable some fonts in config, like CONFIG_FONT_8x8 ?
|
|
|
06-23-2005, 02:47 AM
|
#8
|
Member
Registered: May 2005
Distribution: Slackware 10.1
Posts: 49
Original Poster
Rep:
|
Success. Again, thank you all for the help.
keefaz, Dont have nVidia. And yes I am pretty sure the fonts you mentioned were enabled. As far as I can tell, I did everythign correctly the first time. I went over it several times, but it just kept freezing no matter what I did. So I just started over with a fresh untarred kernel, and redid the same thing (to the best of my knowledge) and it works now.
|
|
|
06-23-2005, 02:52 AM
|
#9
|
LQ Veteran
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,236
|
Pick up the config from your old system, then Answer all the questions for the new options (there'll be a few), then as usual. I did this for 2.6.11 and it worked fine.
EDIT: - too late it seems
Last edited by syg00; 06-23-2005 at 02:53 AM.
|
|
|
All times are GMT -5. The time now is 07:40 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|