[NTLUG:Discuss] Kernel module woes.

[jeremyb@univista.com]

 that's exactly what happened.
cd into your source directory and run  'make modules modules_Install'

-----Original Message-----
From: Justin M. Forbes
To: discuss at ntlug.org
Sent: 7/23/02 1:50 PM
Subject: Re: [NTLUG:Discuss] Kernel module woes.

I am not 100% sure about debian's .deb and kpkg stuff, but in making the
kernel, you have to 
1. create a .configure of some sort
2. make dep
3. make bzImage
4. make modules
5. make modules_install (copies all built modules to
/lib/modules/2.4.18-extraver
6. copy bzImage and System.map to /boot
7. create an initrd image if necessary (mkinitrd /boot/initrd-2.4.18.img
2.4.18
8. edit and run lilo
9. then reboot

Sounds to me like make modules_install, and possibly make modules didnt
happen. look in /lib/modules/ it might be the best place to begin.

Justin

On Tue, 2002-07-23 at 13:16, Scott Denlinger wrote:
> I recently set up a Debian Woody box using the 2.4 kernel boot flavor 
> specified in the setup disks. I have a QIC tape drive in this, so I 
> thought I would install Ftape, and compile and install it as a kernel 
> module. It appears that in order to do this, it was necessary for me
to 
> recompile my kernel, so I did that, and now there are a lot of modules

> that don't get loaded when I boot. Here is the process I went through.
> 
> 1. I installed the kernel sources via dselect, so the sources are in 
> /usr/src/kernel-source-2.4.18
> 
> 2. I used 'make xconfig' to create a .config file. In the process of 
> doing that, I realized I could just configure ftape support in the 
> kernel without messing with ftape as a standalone program, so that's 
> what I did.
> 
> 3. I then used Debian's kernel-package tool to create a .deb file. 
> Specifically, I used 'make-kpkg kernel_image', which resulted in a
.deb 
> file. I installed this using 'dpkg -i <file>.deb
> 
> 4. I let this go ahead and make modifications to lilo, and rebooted
> 
> Lilo successfully booted up the new kernel, but now there are a lot of

> messages about modprobe not being able to find any modules. The result

> of this is that I am not connected to the net on this box, since the 
> modules for my NIC cards aren't loaded.
> 
> What step did I miss in the above process? Doesn't the kernel_image 
> which the make-kpkg creates also create and install the modules?
> 
> Obviously I'm in over my head here, but I suspect there is a simple 
> solution to my problem. Thanks in advance for any tips.
> 
> Scott Denlinger
> 
> 
> 
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss



_______________________________________________
http://www.ntlug.org/mailman/listinfo/discuss