Dear All, When I compile a new kernel, my modules disappear.
Before, I have a fairly normal selection of modules: Module Size Used by Not tainted ac97_codec 9568 0 [cs46xx] agpgart 29824 1 aty128fb 16224 0 (unused) cs46xx 55080 0 (unused) ds 6624 2 i82365 22416 2 ide-scsi 7488 0 input 3072 0 [mousedev keybdev usbkbd] isa-pnp 27432 0 (unused) keybdev 1664 0 (unused) lp 6912 0 (autoclean) mousedev 3776 1 nls_cp437 4384 2 (autoclean) nls_iso8859-1 2880 1 (autoclean) parport 21728 1 (autoclean) [parport_pc lp] parport_pc 25704 1 (autoclean) pcmcia_core 41408 0 [ds i82365] r128 88696 0 (unused) sound 52876 0 (unused) soundcore 3236 5 [sound cs46xx] usb-uhci 20708 0 (unused) usbcore 48032 0 [usbkbd usb-uhci] usbkbd 2848 0 (unused) After, nothing: Module Size Used by Not tainted To compile the kernel, I follow instructions (e.g. from /usr/share/doc/kernel-source-2.4.18/debian.README), like this: # mv /lib/modules/2.4.18 /lib/modules/2.4.18-save # cd /usr/src/kernel-source-2.4.18/ # make menuconfig # make dep # make-kpkg clean # make-kpkg --revision=custom.1.0 kernel_image # dpkg -i ../kernel-image-2.4.18_custom.1.0_i386.deb // dpkg then asks me various questions about my boot manager (LILO). /etc/lilo.conf and the relevant files in /boot are all updated. # shutdown -r now The boot messages include a lot of "Can't locate module XXX" messages. What is going wrong? There must (?) be something simple amiss which means the modules aren't where the machine excpects to find them: non-standard file locations? Should I add command line options or environment variables? This is standing between me and alsa, pcmcia and probably a few other things. Best wishes Ivan
