2.4.6 Kernel Compile

[Ashcrow]

I can compile it, BUT (there is always a but! :-P) none of the modules seem to install. This is what I am doing to set up the kernel:

make mrproper
make xconfig
....(configure)....
make dep
make modules
make modules_install
make bzImage
....(configure lilo)....

When I try to add the ide-scsi module with insmod it says it can't be found. Same thing with many other of the modules that I compiled with the kernel. Any sugestions?

[Dru Lee Parsec]

I'd have to check the Kernel How-To to be sure but I think you do make bzimage BEFORE you do the make modules and make modules_install.

I may be wrong.

BTW, I just d-loaded the kernel code yesterday and I couldn't use make xconfig. Were you able to use it?

[godot]

doesn't matter when you make bzImage, but how about you type this

ls -R /lib/modules/2.4.6

and show us what it spits out

[bdg1983]

Don't know if it will help and this is what I've read in some of the kernel compiling docs. Should there be one more step after make modules_install?

depmod -a

[GonzoJohn]

My experience has been that sometimes modules are compiled, but they don't always end up in /lib/modules/2.4.x/ where they should be. Look in the subdirectories where you compiled the kernel. Sometimes they're compiled here but not copied or moved. All the modules that end in ".o" are compiled.

[antitrustworthy]

Here is my process for kernel updating. It is a compilation of every kernel compiling document I have ever read. I hope it can help.
-download kernel to /usr/src
-rename 'linux' to 'linuxold'
-untar the kernel
-create symlink for new kernel source = linux
-cd linux
-make mrproper
-make xconfig
-edit top level makefile & uncomment out line 'export INSTALL_PATH= /boot'
-make dep
-make clean
-make bzImage
-make modules
-cd /lib/modules and rename 2.4.x to 2.4.x.old
-cd /usr/src/linux
-make modules_install
-depmod -a
-cd /boot
-rename System.map and vmlinuz to old
-copy bzImage from /usr/src/linux/arch/i386/boot to /boot
-copy System.map from /usr/src/linux/arch/i386/boot to /boot
-edit lilo.conf
-symlink your System.map and bzImage you just copied to make them System.map and vmlinuz respectively (System.map may have been System.map-2.4.x or something)
-run /sbin/mkinitrd /boot/initrd-2.4.x.img 2.4.x
-run /sbin/lilo
copy modules from /usr/src/linux to /lib/modules if they didnt get put there automatically...be sure to check that

And that should do you.... note the "should". Hope it works for ya!!

[godot]

here's what i do

make menuconfig
make-kpkg kernel_image

then install the .deb in /usr/src on the computer i want :)

Go Debian!

[Ashcrow]

Allright, it works up to bzImage now :-P. This is the output ...

make[1]: Entering directory `/usr/src/linux/arch/i386/boot'
ld -m elf_i386 -Ttext 0x0 -s -oformat binary bbootsect.o -o bbootsect
ld: cannot open binary: No such file or directory
make[1]: *** [bbootsect] Error 1
make[1]: Leaving directory `/usr/src/linux/arch/i386/boot'
make: *** [bzImage] Error 2


Anyone know how to fix this?

[bdl]

What version of what distro are you running? Some distros, like Debian *stable* cannot innately run the 2.4 series kernels because they have outdated modutils and other factors; you have to update the rest of your system before you can run these kernels properly.

[Ashcrow]

I am using Slackware 8.0 ... it was just released about a week ago.

[Gaccm]

i had the exact same problem you had, i went from a clean 2.2.19pre17 Debian install to 2.4.6. No matter what i did (first i tried depmod/modprobe/insmod commands, then i re-tried make modules, make modules_install, that s all i can remember) i couldn't get modules to be read. The stats for this box are: p200 64meg. I did the exact same thing on a 1.33TBird, 256 meg ddr and it worked fine.
Eventually i gave up and just stayed with 2.2 :(

[bdl]

Originally posted by Ashcrow:
<STRONG>I am using Slackware 8.0 ... it was just released about a week ago.</STRONG>

Hmm, I'm running Slack 8 also, with 2.4.6. About the only thing different I did was to install with 2.4.5 and also install on reiserfs, choosing the packages with 'expert' mode. I wouldnt think it would have a bearing on whether or no the modules would install and work properly.

[Ashcrow]

I went ahead and installed the problematic modules into the kernel in the monolithic fasion so it's working now. The only problem now is that the ide-scsi modules doesn't seem to set my burner up as it could with 2.2.x. lol. This WILL work! :-P