Re: bzImage question - now make modules
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. > > > 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
Re: bzImage question - now make modules
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] you can, safely, neuter that file altogether to get a kernel made and add back the relevant bits later. Not a recommended procedure but, hell, nothing wrong in reducing noise levels first time out. there is *still* an unresolved issue with depmod -a that requires it to be used AFTER you reboot the new kernel. This 'problem' is so endemic that all distros i am aware of automatically fire that command out at boot time without your help. The ways they do that are sometimes wondrous to behold. So, if modules are your only problem you will be 'ok' to reboot on a now (functionally compiled) kernel. 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. 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. -- http://linux.nf -- [EMAIL PROTECTED] _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: bzImage question - now make modules
On Sunday 30 September 2001 08:51 pm, Bruce Marshall spoke thus unto Caesar's assembled legions: > On Sunday 30 September 2001 23:28 pm, Tony Alfrey wrote: > > OK, I removed zoran and buz from the video adapters loadable > > modules. I re-ran xconfig: OK > > make dep: OK > > make clean: OK > > make bzImage: OK > > make modules: OK > > make modules_install: OK until the very end where I think it runs > > depmod -a. The list of modules with "unresolved symbols" looks > > like virtually every module. depmod -a 2.4.4 produces the same > > list again. Before I started anything, I did > > mv /lib/modules/2.4.0 /lib/modules/old-2.4.0 > > depmod -a on the running kernel 2.4.0 gives no problems. > > > > Getting closer but still no cigar. > > Any ideas? > > Thanks! > > I haven't been following this thread too closely but I do remember > that the first time I did a compile of a 2.4.x kernel, I had all > kinds of unresolved symbols. I kept at it by changing the config > until I got it right. I think that was the 2.4.6 kernel. If you > pick certain options without picking other related options, I think > you can get into this mess. Hmmm. Maybe I will try a vanilla default kernel to get it to boot, then add stuff on. Thanks! -- 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
Re: bzImage question - now make modules
On Sunday 30 September 2001 23:28 pm, Tony Alfrey wrote: > OK, I removed zoran and buz from the video adapters loadable modules. > I re-ran xconfig: OK > make dep: OK > make clean: OK > make bzImage: OK > make modules: OK > make modules_install: OK until the very end where I think it runs > depmod -a. The list of modules with "unresolved symbols" looks like > virtually every module. depmod -a 2.4.4 produces the same list again. > Before I started anything, I did > mv /lib/modules/2.4.0 /lib/modules/old-2.4.0 > depmod -a on the running kernel 2.4.0 gives no problems. > > Getting closer but still no cigar. > Any ideas? > Thanks! I haven't been following this thread too closely but I do remember that the first time I did a compile of a 2.4.x kernel, I had all kinds of unresolved symbols. I kept at it by changing the config until I got it right. I think that was the 2.4.6 kernel. If you pick certain options without picking other related options, I think you can get into this mess. -- ++ + Bruce S. Marshall [EMAIL PROTECTED] Bellaire, MI 09/30/01 23:49 + ++ "Can you repeat the part after, "Listen very carefully?" ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
Re: bzImage question - now make modules
On Sunday 30 September 2001 06:46 pm,Collins Richey wrote: > On Sun, 30 Sep 2001 18:01:29 -0700 Tony Alfrey > > > > zoran is a loadable kernel module for a video adapter that is > > selected > > as "m" in xconfig as is buz. So what do you experts think? > > Should I > > just trash these in xconfig? Or any other ideas? > > Unless your hardware configuration requires this to run, by all means > don't select this one in your kernel configuration. It's quite > common for some of the more esoteric selections not to have been > thoroughly checked out. OK, I removed zoran and buz from the video adapters loadable modules. I re-ran xconfig: OK make dep: OK make clean: OK make bzImage: OK make modules: OK make modules_install: OK until the very end where I think it runs depmod -a. The list of modules with "unresolved symbols" looks like virtually every module. depmod -a 2.4.4 produces the same list again. Before I started anything, I did mv /lib/modules/2.4.0 /lib/modules/old-2.4.0 depmod -a on the running kernel 2.4.0 gives no problems. Getting closer but still no cigar. Any ideas? Thanks! -- 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
Re: bzImage question - now make modules
On Sunday 30 September 2001 06:46 pm,Collins Richey wrote: > > > > zoran is a loadable kernel module for a video adapter that is > > selected > > as "m" in xconfig as is buz. So what do you experts think? > > Should I > > just trash these in xconfig? Or any other ideas? > > Unless your hardware configuration requires this to run, by all means > don't select this one in your kernel configuration. It's quite > common for some of the more esoteric selections not to have been > thoroughly checked out. OK. It was selected as a loadable kernel module on the 2.4.0 kernel, but I'll blow it away and see if it works. -- 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
Re: bzImage question - now make modules
On Sun, 30 Sep 2001 18:01:29 -0700 Tony Alfrey <[EMAIL PROTECTED]> wrote: > Hi list! > > Earlier I complained about my 2.4.4 kernel compile crashing at make > bzImage. But it appears that the problem was in running xconfig in > run > level 3 and not within X. So now things get as far as make modules > before going bonk. I get this: > > buz.c:322: `KMALLOC_MAXSIZE' undeclared (first use in this function) > buz.c:316: warning: `alloc_contig' might be used uninitialized in > this > function > buz.c: In function `zoran_ioctl': > buz.c:2837: `KMALLOC_MAXSIZE' undeclared (first use in this > function) > make[3]: *** [buz.o] Error 1 > make[3]: Leaving directory > `/root/testlinux/linux-2.4.4/drivers/media/video' > make[2]: *** [_modsubdir_video] Error 2 > make[2]: Leaving directory > `/root/testlinux/linux-2.4.4/drivers/media' > make[1]: *** [_modsubdir_media] Error 2 > make[1]: Leaving directory `/root/testlinux/linux-2.4.4/drivers' > make: *** [_mod_drivers] Error 2 > > zoran is a loadable kernel module for a video adapter that is > selected > as "m" in xconfig as is buz. So what do you experts think? Should > I > just trash these in xconfig? Or any other ideas? Unless your hardware configuration requires this to run, by all means don't select this one in your kernel configuration. It's quite common for some of the more esoteric selections not to have been thoroughly checked out. -- Collins Richey Denver Area gentoo_rc6 xfce+sylpheed ___ http://linux.nf -- [EMAIL PROTECTED] Archives, Subscribe, Unsubscribe, Digest, Etc ->http://linux.nf/mailman/listinfo/linux-users
bzImage question - now make modules
Hi list! Earlier I complained about my 2.4.4 kernel compile crashing at make bzImage. But it appears that the problem was in running xconfig in run level 3 and not within X. So now things get as far as make modules before going bonk. I get this: buz.c:322: `KMALLOC_MAXSIZE' undeclared (first use in this function) buz.c:316: warning: `alloc_contig' might be used uninitialized in this function buz.c: In function `zoran_ioctl': buz.c:2837: `KMALLOC_MAXSIZE' undeclared (first use in this function) make[3]: *** [buz.o] Error 1 make[3]: Leaving directory `/root/testlinux/linux-2.4.4/drivers/media/video' make[2]: *** [_modsubdir_video] Error 2 make[2]: Leaving directory `/root/testlinux/linux-2.4.4/drivers/media' make[1]: *** [_modsubdir_media] Error 2 make[1]: Leaving directory `/root/testlinux/linux-2.4.4/drivers' make: *** [_mod_drivers] Error 2 zoran is a loadable kernel module for a video adapter that is selected as "m" in xconfig as is buz. So what do you experts think? Should I just trash these in xconfig? Or any other ideas? Thanks! -- 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
