On Tuesday 02 October 2001 06:57 am,Mike Andrew wrote: > On Monday 01 October 2001 14:58, Tony Alfrey wrote: > > make modules_install: OK until the very end where I think it runs > > depmod -a. The list of modules with "unresolved symbols" looks > > like > > [snip] > > Almost for sure (being a caldera derived kernel) the offender is > /etc/modules.conf. > remove all path statements from the top of that file. eg path[usb]
David Bandel recommended to retain only path[usb]=/lib/modules/'uname -r' Shoule I kill that too?? > > you can, safely, neuter that file altogether to get a kernel made and > add back the relevant bits later. I'm a little unclear here. Do you mean wipe out /etc/modules.conf during make bzImage and then put it back before make modules? > Not a recommended procedure but, > hell, nothing wrong in reducing noise levels first time out. > <snip> > > So, if modules are your only problem you will be 'ok' to reboot on a > now (functionally compiled) kernel. At this point, I get Installing kernel . . . . . . . . . . . Uncompressing Linux . . . . . . . . . Invalid compressed format (err=1) > It is quite likely in any case, > that because this is your first go, you've probably 'missed' > selecting / compiling a module or two and depmod / modprobe will > scream regardless. I went back and did a very vanilla xconfig with as little stuff as I thought I would need. The list of complaints is now shorter. depmod -a seems (but I'm not yet absolutely sure) to complain about unresoved symbols on each module that I selected as a loadable module. > > The bottom line safety net is to leave an intact kernel 2.4.0 kernel > image in /boot, ensure lilo does indeed point to it in some way, and, > secondly retain /lib/modules/2.4.0 Everything else is playtime, and > you'll be reasonably bomb proof. So far, I have been able to boot the 2.4.0 kernel with no problem after the new kernel boot crashes. This is my script. It is a synthesis of the various scripts and suggestions in the various SxSs. My new kernel source is in /root/testlinux/linux-2.4.4 #!/bin/bash # bk - script to build a kernel mv /lib/modules/2.4.0 /lib/modules/old-2.4.0 echo Building a new kernel . . . cd /root/testlinux/linux-2.4.4 make mrproper if [ $? -gt 0 ] ; then echo make mrproper failed exit 1 fi make xconfig es=$? if [ $es -gt 0 ] ; then echo make xconfig failed exit es fi make dep if [ $? -gt 0 ] ; then echo make dep failed exit 1 fi make clean if [ $? -gt 0 ] ; then echo make clean failed exit 1 fi make bzImage if [ $? -gt 0 ] ; then echo make bzImage failed exit 1 fi make modules if [ $? -gt 0 ] ; then echo make modules failed exit 1 fi make modules_install if [ $? -gt 0 ] ; then echo make modules_install failed exit 1 fi cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.4-modular cp System.map /boot/System.map-2.4.4 # Put this back anyway if the script crashes mv /lib/modules/old-2.4.0 /lib/modules/2.4.0 depmod -a 2.4.4 lilo Thanks for your help! -- Tony Alfrey [EMAIL PROTECTED] "I'd rather be sailing" _______________________________________________ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
