I have spent most of the day doing kernel compiles trying to get the 2.6.10 kernel to work on Slackware 10.1. I've narrowed the problem down to massive module issues. My kernels have failed becuase:
Kernel panic when root file system was not recognized, fixed by changing the ReiserFS support from [M] in kernel config to[*]
Next was a kernel panic when partition with /home was unrecognized. This time ext3 support in kernel needed to be enabled.
Now I could finally boot into log in prompt. Start X and no mouse. Had to change from [M] on ps/2 support to[*]

There were a couple other various lock-ups that I just chaulked up to newbie screw-ups but finally I got a semi-working kernel. This time there was no sound or network connection, both issue missing /lib/mod errors. Now I am starting to take the hint. For some reason my modules are really not working at all. I can't figure out why, but I'm thinking that I'm not actually installing them right. So, here is what I've been doing to complile the kernel, please let me know what I'm doing wrong.

Extract the Kernel from the .tar.bz2 file and move it to /usr/src

mv to /usr/src/linux-2.6.10

make mrproper

make menuconfig

make clean

make bzImage

make modules

cd /boot

mv /vmlinuz /vmlinuz.old

cd /usr/src/.../i386/boot

cat bzImage > /boot/vmlinuz

mv /boot/System.map /boot/System.map.old

cp System.map /boot/System.map

Edit /etc/lilo.conf and run /sbin/lilo

Is there some spot where I should be installing the modules? Most other methods of compiling a kernel do some kind of make_install, but the Slackware book says nothing about this. Is the book just outdated and intended for compiling a 2.4 kernel?

I'd say change this line to make modules && modules_install

I tried the make modules && modules_install and got an error after the modules compiles saying that modules_install is not a valid command. Could something be going wrong because I'm doing this from X or because i'm using su rather than just doing it from root?

you've gotto use "#make modules_install "
( ...or did you...)

egag

I just tried it again, slightly different method this time. After the make menuconfig I did:

make

su -c "make modules_install"

make install

This worked better, I guess, since it recognized my mouse, filesystems, and network. However it killed Dropline for some reason (it just hangs at the splash screen) and It's still not recognizing my onboard audio (though there is a soundcard in the mail). So I guess I'll try to get Dropline working and call it a success.

yeah you need a make modules_install there somewhere. generally for 2.6.10 i use

make mrproper
make bzImage
make modules
su make modules_install


and that takes care of it. of course you still have to copy the bzImage, System.map and .config files, but you already knew that.

I just finished compiling a custom 2.6.10 kernel for Slack 10 install. I had no problems on the compile and install.

Ran the following:
make mrproper
make menuconfig
make bzImage
make modules && make modules_install

I deleted soft links System.map, config from /boot. Then copied over bzImage and System.map from the new kernel tree. Created new soft links in /boot for the new System.map and config. I've made a soft link in /usr/src called linux which points to my linux-2.6.10 folder in the same directory.

My new kernel boots just fine. X windows starts just fine

My problems are the following:

1) when I do an lsmod, I show nothing except the headers Module, Size, Used by. It shows no modules loaded. However I do get the startup sound from KDE when I start X. My USB intellimouse runs just fine, but I built that into the kernel. When I run rc.modules I get this:

Module dependencies up to date (no new kernel modules found).
FATAL: Module agpgart not found.
FATAL: Module ide_scsi not found.

what am I missing?

2) my system is running extra slow with the new kernel! any ideas?

Please let me know what other readouts you need to see to troubleshoot.

Thank you for your help.
Shaun

agpgart and ide_scsi are not compiled in as a module, most likely they are compiled into the kernel.

You are getting the FATAL error message because you boot scripts still try to do a modprobe. To get rid of them

Go to /etc/rc.d/rc.modules

and remove or comment out the lines
and
From the file and save it. Next time on boot, you shouldn't get the FATAL error message.

Can anyone hazzard a guess as to why an lsmod would show nothing? I would think that there would be at least one module loaded.

Also, if you install a module before configuring, compiling, and booting a new kernel, shouldn't it still exist in the same form with the new kernel?

With a 2.4.29 kernel I installed IVTV. Everything worked fine. (I upgraded because the TV card I had was a newer PVR350 which waranted the upgraded v4l)

Now with the 2.6.10 kernel, I have no sign of IVTV??? I can't modprobe IVTV.

my modules.conf file has something like the following in it...

alias char-major-81 videodev
alias char-major-81-0 ivtv
options tuner type=2
options msp3400 once=1 simple=1
add below ivtv msp3400 saa7115 tuner

With udev I keep loosing my /dev/video0 sym link. I also loose my /dev/cdrw and /dev/dvdrw sym links. I can't even mount my cd and dvd drives anymore because the sym links mentioned above go away. This udev thing confuses me! Any words of wisdom???

shaun

well...look in /lib/modules .
do you see a dir called 2.6.10 ? and are there modules in it ?

if not ( or maybe anyway ), goto /usr/src/linux-2.6.10
do a "make modules". ( watch for errors )
in case of no errors do " make modules_install"

i guess the're not installed.

egag

well, I checked for a 2.6.10 folder under /lib/modules.....it exists and has folders in it including ivtv

do you have to recreate devices in /dev after moving from a 2.4.* to a 2.6.* kernel? I already made /dev/cdrw and /dev/dvdrw before upgrading. Now they are gone and cdrom and dvd are back

I run IVTV and LIRCD as modules. They are linux drivers for my TV tuner card and the remote sensor. Everytime I reboot, I have to probe for them. How do I get this to happen automatically at reboot?

btw...I figured out my previous problem. I used a modified version of this post from our own Shilo.

http://www.linuxquestions.org/questi...ght=udev+cdrom

udev is a cool new way of working your devices!

Thanks!
shaun