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.
Just so you know, I had a really good day to day, managed to find a really good thread on how to compile my kernel (finally), posted here and here's a link to it!
And right under that you'll find instructions for setting up CPU Frequency Scaling.
So I ran slack 11 for a year, using the precompiled 2.6 "huge" kernel that came with it. No problems. I like 2.6 and I like udev and I was used to it from a previous non-slack distro. I've now switched to slack 12 and I am using the prebuilt 2.6 "huge" kernel. Again, no problems.
I would like to compile the kernel, using all of the settings that Patrick used, as they are working well for me. From my pre-slack days, when I used to compile the kernel often: recall that I would do something like this:
Code:
cd /usr/src/linux
make menuconfig
make
Then I could copy the three files over to /boot/and make changes to the bootloader.
Will this method work nowadays in slack 12?
Do I need to install another package from the DVD prior to compiling?
If you want to use Patrick's settings you should use one of his config files. I think you will find them in the boot directory.
There seems to me to be little point in simply recompiling the huge kernel. Perhaps you should be trying out the smaller pre-compiled kernels. If they do not work for you, you can look at their configuration and change whatever has to be changed. Of course you will have to create an initrd file if you do that.
I run a kernel that I have compiled based on Patrick's 2.6 smp config but optimised for an Athlon processor and with ext3 support built in to the kernel to spare the need for initrd.
Hi,
While I have been using Slackware for some time I have always been happy with the kernels as provided.
However 12 has given me the encouragement to try to compile my own.
The first problem I encounter is at the make oldconfig stage when I get a lot of error messages all concerned with scripts/basic/fixdep.c. Typical but not limited to :-
Looking at copies of fixdep.c on websites I can not see anything wrong with my copy and there is no mention of header files not being found. The computer was wiped clean before installing 12 and 12 is the only operating system on the computer so whatever headers it finds come with 12.
Please do not answer my above post. I have now found the problem myself. There was something wrong with my glibc installation and reinstalling it has got me further along.
hi guys i tried compiling new kernel 2.6.23 from kernel.org to upgrade my default huge-smp kernel in slackware 12. the compilation went succesfully and i copied bzImage from the /boot folder of new kernel to /boot/vmlinuz and System.map to /boot folder and run /sbin/lilo. lilo setup went smoothly and i re-started my system to test the new kernel. system booted smoothly and every thing works fine but when i run uname -r it shows kernel is 2.6.21.5-smp instead of new kernel 2.6.23. got bit confused wheather new kernel is installed or not.
Did you edit your '/etc/lilo.conf' to boot the new kernel ? Maybe you should, and then run 'lilo'. I would keep the old kernel there in case the new kernel was not compiled properly and panics on boot.
yes i edited lilo.conf to boot the new kernel. all works fine and the system starts up but shows it's booting kernel 2.6.21.5-smp. uname also shows kernel version is 2.6.21.5-smp. got confused where i had missed.
again i ran into problem when i re-compiled the kernel for audio support. so i had re-installed adn tried to compile the kernel 2.6.23 from kernel.org. now this time make oldconfig prompts for lots of options and made make menuconfig and installed the kernel but the kernel hanged with kernel panic unable to mount root file system and system froze. i used rescue disk and changed lilo to old kernel and booted into slack 12 and tried to compile again but again it asks for the same options while making make oldconfig. it seems to me that there is problem in the old .config file so how to compile the kernel correctly. i tried with menuconfig and chose the options related to my hardware but no sucess again the kernel freezes with same error. tell me how to make config from the running kernel, or will it be right to re-compile the default huge-smp kernel and install it again and use the .config file to compile new kernel.
last night i was tinkering,just wasting time, compile kernel 2.6.23.9,following most of the config from stock 2.6.21.5.
1st question:
It seems booted ok,but when I want to shutdown, the system just halted and freeze instead of halted and shut down completely.
Do you know what went missed with my config?
2nd questions:
my step after the new kernel is built (beside editing lilo and copy files to /boot) is I
Code:
#cp ~/rc.modules-2.6.21.5 ~/rc.modules-2.6.23.9
and edit the rc.modules-2.6.23.9 if necessary.
And I never use depmod.Don't know how to use it.
Is this correct?
What is the correct way related to configuring new modules for the new kernel?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.