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'm running Slackware64 13.1 and I's like to make some changes in my kernel (2.6.33.4) configuration. Specially I'd like to :
Change MTRR setting from "continuous" to "discrete"
disable nVidia Framebuffer Support
disable nVidia Riva support
So, I'm juts wondering to do that keeping the original configuration.
I mean with two kernel version it's alright.
Also, I wish to know how to proceed. Do I have to go through all the building kernel processing?
make mrproper
make xconfig
make prepare
make
make modules_install
And then, what about boot directory and Lilo?
I mean, it's same kernel version ....
And I want to make sure that I keepp the original config intact so that I can boot on it any time ...
I've just found that one can edit the file Makefile and change the line "EXTRAVERSION =" to create a unique suffix at the end of the default name of the kernel.
Well, is it really what people do when they build a new kernel version?
Now lets suppose EXTRAVERSION is set to -new, I guess my new kernel will have the name bzImage-2.6.33.4-new.
So, will I get a new directory /usr/modules/2.6.33.4-new in addition to /usr/modules/2.6.33.4?
I've just found that one can edit the file Makefile and change the line "EXTRAVERSION =" to create a unique suffix at the end of the default name of the kernel.
Well, is it really what people do when they build a new kernel version?
Now lets suppose EXTRAVERSION is set to -new, I guess my new kernel will have the name bzImage-2.6.33.4-new.
So, will I get a new directory /usr/modules/2.6.33.4-new in addition to /usr/modules/2.6.33.4?
You should try it, and find out for yourself. That's the best way to learn. It sounds like you are on the right track so far.
You don't edit the Makefile - except in unusual circumstances.
Nor do you directly edit the config file, but yes adding the EXTRAVERSION will do what you hope. Show us a link to your reference - Alien Bob (IIRC) had a good one for Slack.
Rather than using EXTRAVERSION, set the LOCALVERSION string within the config file via its entry in xconfg/menuconfig. That's what I (and I think most others) do.
I believe EXTRAVERSION is intended to reflect differences in the source tree where as LOCALVERSION is there to reflect differences in the config. (but I could be wrong)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.