SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm almost there-on my fourth try with Slack 10 I was able to build and install my new kernel of 2.4.29. My old kernel was 2.4.26. The problem is that I now have no sound and alsaconf cannot find modules (I use ESS module).
Here's what I did after I untarred the new kernel:
cp /usr/src/linux-2.4.26/.config /usr/src/linux-2.4.29/.config
change some settings
make dep && make clean bzImage modules modules_install
mv /boot/vmlinuz /boot/vmlinuz.old
cat arch/i386/boot/bzImage > /boot/vmlinuz
mv /boot/System.map /boot/System.map.old
cp System.map /boot/System.map
There is a modules directory in /lib/modules/2.4.29.
Also /usr/src/linux is still a symbolic link to /usr/src/linux-2.4.26. Should I point this link towards my new kernel 2.4.29?
I have a similar problem with a 2.6.11 kernel. When i run make modules_install it doesn't seem to move many files and there are hardly any modules moved into the /lib/modules/2.6.11 folder whereas my 2.4.26 has loads. The 2.6 module files also seem to be .ko files which apparently are the wrong format.
Originally posted by APB_4 I have a similar problem with a 2.6.11 kernel. When i run make modules_install it doesn't seem to move many files and there are hardly any modules moved into the /lib/modules/2.6.11 folder whereas my 2.4.26 has loads.
If there were * by most of your selections then you didn't build them as modules, they compiled into the kernel. Or if you were using xconfig and it was a check mark instead of a "round black circle" (sorry I can't remember what those are called now), then they were compiled into the kernel and weren't compiled as modules. So you wouldn't have many modules. The stock kernel that comes with Slackware has "most" stuff built as modules.
Originally posted by APB_4 The 2.6 module files also seem to be .ko files which apparently are the wrong format.
Actually that's EXACTLY how it's supposed to be named. Starting with the 2.6 kernel modules started using the .ko extension rather than the .o extension. That said, the kernel modules that Pat builds somehow get "extended" with .t.gz or something similar. It's been so long since I looked a stock Slackware module that I've forgotten.
cp /usr/src/linux-2.4.26/.config /usr/src/linux-2.4.29/.config make oldconfig
change some settings make bzImage && make modules && make modules_install cp arch/i386/boot/bzImage /boot/bzImage-2.6.11 cp System.map /boot/System.map-2.6.11 nano /etc/lilo lilo reboot
You weren't making any modules with your original posted commands.
bzImage & vmlinuz are the same thing (confusing, but the same thing)
I had just woke up when I posted and made a typo-I didn't modprobe anything. That should have been make oldconfig. I started with make mrproper before I did anything and then finished by editing /etc/lilo.conf and executing lilo.
It does look like modules weren't made. uname -r shows 2.4.29. Can I copy the modules from 2.4.26 over to the modules directory for 2.4.29? If not, do I need to start over with mrproper or can I just pick up with:
Last edited by linuxhippy; 03-10-2005 at 09:28 AM.
That's one of the reasons I'm recompiling the kernel. My laptop is 6 yrs. old and pre-dates most of the hardware that the modules are for. I looked over the .config file that came with Slack 10 and saw that everything under the sun was compiled into it using modules. I want to take those out.....I'll do my 5th kernel compile tonight without all those modules. I just need a couple....I know I need the ESS ones for my ESS soundcard.
APM is another that currently has a module but doesn't power down my laptop. Should I select Y to compile that into the kernel...would my laptop then power down by itself??
good idea-lsmod. I did that and saw I don't have that many modules active. I'd like to use xconfig on my existing .config file for 2.4.29 that I know works, but trim down on the modules. Any idea how I can do that knowing which modules I typically use?