Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
You may now start configuring from scratch, however as I already explained I believe that it is better to load Patrick's configuration file and build on it. In the configuration window, choose the option 'Load an alternate file', an type /usr/src/config-2.6.10 in the box, then click 'ok'. You have now loaded a proper startup configuration file.
I try loading the config file and I receive the following error, then it stops.
Code:
' invalid for LOG_BUF_SHIFTsymbol value '14
make[1]: *** [menuconfig] Error 1
make: *** [menuconfig] Error 2
I recall following these steps before and it worked just fine. Anyone have a clue what I'm doing wrong?
Last edited by JustinCoyan; 06-22-2005 at 02:20 PM.
I don't know where you got those instructions, but I would throw them away quickly.
What are you trying to do?
Upgrade your kernel?
Which kernel are you running now? (uname -r)
Do you have the kernel sources for the new kernel?
Where did you unpack them?
Which guide are you following to install your kernel?
Do you know your hardware intimately?
If you want to use Pat's kernel config as a starting point, you're wasting your time compiling
with it. Just install his kernel and be done with it. If you use the 2.6.10 kernel, even just the
config file, you should read his README.initrd file that comes with it, or the kernel probably
won't reboot when you're finished.
It's a whole lot easier to just learn how to compile a kernel with a good guide and do it
yourself. If you save your old kernel, you can boot back into it until you get a new good
kernel.
There is a README file that comes with the kernel sources written by Linus Torvalds. He is
probably The Expert (TM) on the Linux kernel, so you should read that. And here is a good guide written by Jesper Juhl which will work just fine. I would recommend that you do not
make the System.map symlink he suggests at the bottom of that guide, but everything
else is fine.
Originally posted by Chinaman
If you want to use Pat's kernel config as a starting point, you're wasting your time compiling
with it. Just install his kernel and be done with it.
When I compiled a kernel 2.6.11.12, I also built on Pat's config file for 2.6.10, and it worked perfectly. As long as you use an existing kernel config file from the same series (i.e. 2.6, don't mix 2.4 and 2.6) and from a lesser version (2.6.10 < 2.6.11.12), I can't see why that wouldn't work.
Originally posted by uselpa When I compiled a kernel 2.6.11.12, I also built on Pat's config file for 2.6.10, and it worked perfectly. As long as you use an existing kernel config file from the same series (i.e. 2.6, don't mix 2.4 and 2.6) and from a lesser version (2.6.10 < 2.6.11.12), I can't see why that wouldn't work.
Then I'll explain to you why it might not work.
Pat's config file for 2.6.10 has support for ext2 built in, but all others as modules. Who is running a non-journalized filesystem on a Slackware-10.1 box these days? Especially on the / partition. That's just not a good choice.
Most people choose ext3 or reiserfs, especially since ReiserFS is the default when you install Slackware. (Patrick himself even uses reiserfs for his / filesystem.) So if this guy (or anyone else) doesn't know enough to compile his own kernel, he's more than likely not going to know to look through those file systems and change (at least) his / partition's file system from a module to built in, nor to read and learn how to make an initrd. And if he doesn't, and there's no reason to say that he will, and he doesn't make and install an initrd.img, the kernel isn't going to boot unless he has ext2 as his / filesystem. (At least the .config generated by the sources from Kernel.org has reiserfs bulit in.) You can browse LQ and see how many kernel panic threads were created as the result of not having support for the / filesystem built into the kernel.
Another reason not to use that config of Pat's is that it is loaded with modules for hardware that your box doesn't have. If you don't know your own hardware enough to compile your own kernel, starting with that config isn't going to help you learn anymore than starting with a pristine set of sources from Kernel.org. You still have to make the choice on everything, which means you need to read the help on it all. So if you're going to use Pat's module laden kernel config, you might as well just install his packages for it, including making the initrd.img according to his instructions.
Just my opinion, feel free to disagree. And that guide he used has some incorrect instructions. There are many better ones on the internet ... the one I recommended earlier is for someone who understands how to build and configure a kernel, but is new to the proper way to compile and install a 2.6 kernel. Kwan Lowe has a very good Kernel Rebuild Guide that I usually recommend to newbies. I haven't seen a better one yet.
I believe it's a good starting point to use Pat's config file because it fits well into Slackware. Of course you'll have to do some research, like using the rc.modules-2.6.10 he provides and reading the README about initrd. Or build reiserfs and mouse support directly into the kernel. It'll still be "module laden" as you put it, but not more so that Pat's kernel, and it will work. And it's obviously a better choice than starting with an non-existent .config file, _especially_ for a newbie.
Furthermore, when Slackware will provide the next 2.6 kernel it is likely to be based on Pat's previous config files for 2.6, making the transition easy.
This way, you get a quick start at compiling kernels and you can improve your configuration from there if you want to. I think this approach is more newbie-friendly that to say "don't do it unless you _exactly_ know what you are doing and you are able to do it perfectly".
It's a whole lot easier to just learn how to compile a kernel with a good guide and do it yourself. If you save your old kernel, you can boot back into it until you get a new good kernel.
That's how you learn. Using someone else's config doesn't teach you about your hardware.
1- doing a necessary change to your kernel to activate support for some hardware or tweak a specific option
2- building an ideal kernel, 100% optimized for your machine and without any unneeded parts.
It's easier to start with 1 and to gradually move up to 2. You cannot expect somebody who wants to make a minor change to his kernel to learn and understand all the kernel options before doing anything that is required.
So, JustinCoyan, to help with your original question: If you're going to use someone else's config file, it's best to put it with your sources and issue "make oldconfig". If you want to change anything in it, then you would issue "make xconfig" (or gconfig or menuconfig) and make your changes, then continue with compiling and installing the kernel.
Last edited by Bruce Hill; 07-08-2005 at 04:39 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.