Modules after kernel upgrade.

[Hans van den Boogert]

I use Debian 2.1 with kernel 2.0.36.

I baked a new kernel for use with my AWE64 Soundblaster. In the process it
was adviced to rename /lib/modules/2.0.36 to /lib/modules/2.0.36-old before
installing the new kernel package. After intstalling there was a new
/lib/modules/2.0.36 directory, but essential files like ps2aux.o were
missing, making me have to live without a mouse now. 

Do I have to bake a new kernel now for these modules to be included and
automatically activated, or can I still remedy the situation afterwards.
Understand the kernel needs to trigger these modules, but how is that
exactly done? With a initiating file maybe? I hope anybody can give some
background apart from a workable solution.

Have a nice weekend.

Hans

Re: Modules after kernel upgrade.

[Manoj Srivastava]

Hi,

When you configre a new kernel, (in the source directory, use
 make config/menuconfig/xconfig),  you need to install as modules (on
 compile into the kernel) everything that you need (like the psaux
 driver for your mouse). I generally copy the /boot/config-X.X.XX
 files into /usr/local/src/kernel-source/X.X.XY/.config and make
 incremental changes.

The modules are laoded in the order specified in /etc/modules
 file (the auto keyword allows kerneld to trigger these modules on
 demand). The modules must exist in the /lib/modules/X.X.XX/* subdirs,
 of course, for this to work.

manoj
-- 
 Finagle's First Law: To study a subject best, understand it
 thoroughly before you start.  Finagle's Second Law: Always keep a
 record of data -- it indicates you've been working.  Finagle's Fourth
 Law: Once a job is fouled up, anything done to improve it only makes
 it worse.  Finagle's Fifth Law: Always draw your curves, then plot
 your readings.  Finagle's Sixth Law: Don't believe in miracles --
 rely on them.
Manoj Srivastava   [EMAIL PROTECTED]  http://www.debian.org/%7Esrivasta/
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E