Did you try a make mrproper first (before make menuconfig)?  Copy you
.config file somewhere, because it will erase it.  Then do:

make dep clean modules modules_install bzImage

Forrest

> -----Original Message-----
> From: John Leeuw [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 23, 2001 11:48 AM
> To: [EMAIL PROTECTED]
> Subject: Compiling kernel modules...
> 
> 
> Can someone tell me what I am doing wrong here?  I have never 
> been able to
> successfully recompile the kernel with modules.  I am using 
> seawolf and I
> have looked up numerous articles on how to do it but none of 
> the procedures
> I have read about have worked.  I can recompile the kernel as 
> long as all of
> the support I want is compiled in (no modules).  I can 
> include kernel module
> loader support and it seems to work fine on the newly 
> compiled kernel, 'cept
> I have no modules to insert because everytime I build the modules the
> process fails.  This is what I am doing:
> 
> # make menuconfig
>  - select the stuff i want, nothing fancy, exit saving changes.
> 
> # make dep clean modules
>  - make errors out during the modules part (usually Error 2) 
> referencing
> whatever things I have selected as modules (for example 
> parallel port, usb
> stuff, stuff like that, things that are already running as 
> modules in the
> default kernel)
> 
> # some books I have on the subject say to remove the existing 
> module support
> from /lib/modules/'version', then after making the modules run # make
> modules_install , thus installing them.  Then I edit /etc/modules.conf
> accordingly.  Update lilo.conf, run lilo, then reboot.  This 
> is what I know
> to do thus far.
> 
> Like I said I can recompile the kernel successfully as long 
> as I do not
> select to make any of the items I want as modules, they 
> compile fine if I
> just include them.  As a note, I don't need any module support during
> bootup, meaning all the support I need during boot I compile into the
> kernel, thus eliminating the need to build and ramdisk image.
> 
> I haven't included all of the error details because I suspect 
> that there is
> something simple that I am doing wrong that is causing this 
> problem and
> therefore what I have written here should be sufficient.  I 
> can include
> specifics if needed.
> 
> Cheers,
> 
> John Leeuw
> Network Administrator
> Dwight Asset Management
> 100 Bank Street
> Suite 800
> Burlington, VT 05401



_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list

Reply via email to