Debian etch kernel compile problem
Dear all, i compiled kernel on debian etch (two times). But i have a same problem No raid arrays. No Lvm compiled 2.6.21 , 2.6.25 same problem Begin: Assembling all Md arrays mdadm : No array found in config file on automatically failure : failed to assemble all arrays Check root=bootarg cat /proc/cmdline or missing modules, devices cat /proc/modules ls /dev/ ALERT /dev/sda1 does not exist. Dropping to on shell! (initramfs): what is problem ? Thansk for your helps. Regards. Reply With Quote -- #!/bin/bash Murat Ugur EMINOGLU www.fedoraturkiye.com www.murat.ws liste[at]fedoraturkiye.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian etch kernel compile problem
also sprach Murat Ugur EMINOGLU [EMAIL PROTECTED] [2008.05.04.1144 +0100]: i compiled kernel on debian etch (two times). But i have a same problem No raid arrays. No Lvm You have not provided any details, such as the configuration and command line used, so we can't really help you. ALERT /dev/sda1 does not exist. Dropping to on shell! Seems like you forgot to include the SCSI/SATA drivers. -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems when zarathustra was alone... he said to his heart: 'could it be possible! this old saint in the forest hath not yet heard of it, that god is dead!' - friedrich nietzsche digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: kernel compile problem -- unresolved symbols
On Mon, Mar 11, 2002 at 04:53:52PM -0600, Christopher M. Jones wrote: I'm compiling for a K7/Athlon/Duron system. As far as I can tell, -all- modules come up with unresolved symbols. In other words, any module I try to load comes up with unresolved symbols, whether part of the kernel, or standalone. Clearly, I am doing something very wrong, though I haven't changed the methods for compiling, that have worked successfully for me since about 2.4.13. I have made sure (to the best of my knowledge) that I have sufficiently new versions of the important packages. This may be a daft question but when you load modules are you using inmod or modprobe ? Try running depmod -ae too to see if that makes any difference. Post the error messages here too, that might help.
Re: kernel compile problem -- unresolved symbols
On Tue, Mar 12, 2002 at 11:24:22AM +, Alan James wrote: This may be a daft question but when you load modules are you using inmod or Sorry I meant insmod there of course. Still modprobe is the one to use.
kernel compile problem -- unresolved symbols
I am having a problem compiling from source 2.4.17 packaged for Debian. Using make-kpkg kernel_image in the source dir, all my modules come up with unresolved symbols. What causes this? What am I doing wrong? What should I do to fix it? Using gcc 2.95.4
Re: kernel compile problem -- unresolved symbols
I'm compiling for a K7/Athlon/Duron system. As far as I can tell, -all- modules come up with unresolved symbols. In other words, any module I try to load comes up with unresolved symbols, whether part of the kernel, or standalone. Clearly, I am doing something very wrong, though I haven't changed the methods for compiling, that have worked successfully for me since about 2.4.13. I have made sure (to the best of my knowledge) that I have sufficiently new versions of the important packages. modutils 2.4.13-3 debhelper 3.4.11 kernel-package 7.93 Also sprach Faheem Mitha: On 11 Mar 2002, Christopher M. Jones wrote: I am having a problem compiling from source 2.4.17 packaged for Debian. Using make-kpkg kernel_image in the source dir, all my modules come up with unresolved symbols. What causes this? What am I doing wrong? What should I do to fix it? Using gcc 2.95.4 I've compiled 2.4.17 on a number of different machines with signicantly different hardware. I've never had a problem with unresolved symbols. However, I have not compiled many different stand-alone module packages. I think we need rather more information before we can help. Firstly, please tell us what modules are coming up with unresolved symbols, and then (optionally) show us what the unresolved symbols are. (These won't mean much to me but might to someone.) Are these modules part of a standalone package or part of the kernel? If the latter, unresolved symbols probably means you are doing something wrong. A word about your computer's hardware if relevant (like if the modules are drivers for hardware) might be helpful. Please remember there are no mindreaders on this list. Sincerely, Faheem Mitha.
Re: v2.4.14 kernel compile problem
There is a binutils problem, I download binutils, binutils-dev and modutils Potato version and it's compile :D There are my version's: ii binutils 2.9.5.0.37-1 The GNU assembler, linker and binary utiliti ii binutils-dev 2.9.5.0.37-1 The GNU binary utilities (BFD development fi ii modutils 2.3.11-13.1Linux module utilities. On Mon, Nov 05, 2001 at 10:54:43PM -0500, James D Freels wrote: I have just tried to compile a clean source (without any patches) of v2.4.14. I did a straight make oldconfig of a working v2.4.13 .config. I get the following error message at that last part of the make bzImage when it is creating the final kernel image: ld -m elf_i386 -T /usr/src/linux/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o \ --start-group \ arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \ drivers/char/char.o drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/char/agp/agp.o drivers/ide/idedriver.o drivers/scsi/scsidrv.o drivers/cdrom/driver.o drivers/pci/driver.o drivers/video/video.o \ net/network.o \ /usr/src/linux/arch/i386/lib/lib.a /usr/src/linux/lib/lib.a /usr/src/linux/arch/i386/lib/lib.a \ --end-group \ -o vmlinux drivers/block/block.o: In function `lo_send': drivers/block/block.o(.text+0x894f): undefined reference to `deactivate_page' drivers/block/block.o(.text+0x8999): undefined reference to `deactivate_page' make: *** [vmlinux] Error 1 I suspect others will have the same problem. Any idea of a fix? Please respond by email to either [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: v2.4.14 kernel compile problem
Another one of those release many and release quick again Uuughh... I remember someone once said regarding the impending release of 2.4.0 and why it was taking so long...that Linus just has much higher standards...oh oh...this is definitely not in the correct direction in support of the previous comment... On Tue, 2001-11-06 at 11:54, James D Freels wrote: I have just tried to compile a clean source (without any patches) of v2.4.14. I did a straight make oldconfig of a working v2.4.13 .config. I get the following error message at that last part of the make bzImage when it is creating the final kernel image: ld -m elf_i386 -T /usr/src/linux/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o \ --start-group \ arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \ drivers/char/char.o drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/char/agp/agp.o drivers/ide/idedriver.o drivers/scsi/scsidrv.o drivers/cdrom/driver.o drivers/pci/driver.o drivers/video/video.o \ net/network.o \ /usr/src/linux/arch/i386/lib/lib.a /usr/src/linux/lib/lib.a /usr/src/linux/arch/i386/lib/lib.a \ --end-group \ -o vmlinux drivers/block/block.o: In function `lo_send': drivers/block/block.o(.text+0x894f): undefined reference to `deactivate_page' drivers/block/block.o(.text+0x8999): undefined reference to `deactivate_page' make: *** [vmlinux] Error 1 I suspect others will have the same problem. Any idea of a fix? Please respond by email to either [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: v2.4.14 kernel compile problem
On Tue, Nov 06, 2001 at 02:11:52PM +0800, Patrick Cheong Shu Yang wrote: Another one of those release many and release quick again Uuughh... I remember someone once said regarding the impending release of 2.4.0 and why it was taking so long...that Linus just has much higher standards...oh oh...this is definitely not in the correct direction in support of the previous comment... /me keeps his fingers crossed that Linux will not become winblows. /me pgpF4I6KSy64H.pgp Description: PGP signature
Re: v2.4.14 kernel compile problem
On Tue, Nov 06, 2001 at 02:11:52PM +0800, Patrick Cheong Shu Yang wrote: Another one of those release many and release quick again Uuughh... I remember someone once said regarding the impending release of 2.4.0 and why it was taking so long...that Linus just has much higher standards...oh oh...this is definitely not in the correct direction in support of the previous comment... The thing is that they tried to accomplish ALOT in 2.4... everything that they did is good and will lead to the linux kernel being a genuinely excellent kernel that can rightly compete with commercial unices, but all of the changes has introduced some new bugs that need to be worked out. The thing is, do you want a super stable toy kernel that works well for hobbyists and low-end desktop machines (one that is simple but inefficient)? Or do you want a kernel that strives to be the best... one that runs efficiently and well even under high load? The 2.2 series is quite stable, but it cannot compete with most commercial unices or even freeBSD on high end machines, while the 2.4 kernel has gone a long way towards being able to do so. But high end power and efficiency comes at the cost of much greater complexity, which is that much harder to maintain flawlessly. Also keep in mind that 2.4 is being actively worked on (despite it's declaration of being stable), and so it cannot be counted on to run perfectly just yet. Give it some time... Linus' standards are both high and ambitious, and when the smoke clears the kernel should be really top notch. -- John Patton [EMAIL PROTECTED] Too bad all the people who know how to run this country are busy running taxicabs or cutting hair. -George Burns
Re: v2.4.14 kernel compile problem
On Tue, Nov 06, 2001 at 08:53:51AM -0600, John Patton wrote: On Tue, Nov 06, 2001 at 02:11:52PM +0800, Patrick Cheong Shu Yang wrote: Another one of those release many and release quick again Uuughh... I remember someone once said regarding the impending release of 2.4.0 and why it was taking so long...that Linus just has much higher standards...oh oh...this is definitely not in the correct direction in support of the previous comment... The thing is that they tried to accomplish ALOT in 2.4... everything that they did is good and will lead to the linux kernel being a genuinely excellent kernel that can rightly compete with commercial unices, but all of the changes has introduced some new bugs that need to be worked out. The thing is, do you want a super stable toy kernel that works well for hobbyists and low-end desktop machines (one that is simple but inefficient)? Or do you want a kernel that strives to be the best... one that runs efficiently and well even under high load? The 2.2 series is quite stable, but it cannot compete with most commercial unices or even freeBSD on high end machines, while the 2.4 kernel has gone a long way towards being able to do so. But high end power and efficiency comes at the cost of much greater complexity, which is that much harder to maintain flawlessly. Also keep in mind that 2.4 is being actively worked on (despite it's declaration of being stable), and so it cannot be counted on to run perfectly just yet. Give it some time... Linus' standards are both high and ambitious, and when the smoke clears the kernel should be really top notch. Although I appreciate the enormous work that has been done during the development of the 2.4 kernel to bring it nearer to enterprise level (it has already reached this level in many aspects) I'm not sure if this is the right way to accomplish this goal. I had problems with kernel versions 2.4.9 to 2.4.12 (once there were errors while compiling NTFS support, another time there were problems with the parallel port, and finally a lot of VMM errors in version 2.4.10). Therefore I've just made the change from 2.4.8 to a running kernel 2.4.13. But now it seems this story will continue with 2.4.14. I never had these problems when changing to a new kernel version of the 2.2 series. So with all these problems in differnet 2.4 releases and keeping in mind that it's been actively worked on kernel 2.4 (as you wrote before) I wouldn't call it stable. Maybe it would be better to do this work on an unstable tree 2.5. But I think the Debian mailing list is not the right place for such discussions. Finally I agree with your conclusion: In the end the kernel will be top notch and everybody - including me - will be happy :-) Bye Andreas Schmidt
Re: v2.4.14 kernel compile problem
On Tue, Nov 06, 2001 at 06:42:23AM -0500, Michael P. Soulier wrote: On Tue, Nov 06, 2001 at 02:11:52PM +0800, Patrick Cheong Shu Yang wrote: Another one of those release many and release quick again Uuughh... I remember someone once said regarding the impending release of 2.4.0 and why it was taking so long...that Linus just has much higher standards...oh oh...this is definitely not in the correct direction in support of the previous comment... /me keeps his fingers crossed that Linux will not become winblows. FUD. That won't happen until you can no longer the source code yourself, but instead are required to download a binary which you can only retrieve after agreeing to some weird license. -- Nathan Norman - Staff Engineer | A good plan today is better Micromuse Ltd. | than a perfect plan tomorrow. mailto:[EMAIL PROTECTED] | -- Patton pgpNw6mqFP4tT.pgp Description: PGP signature
v2.4.14 kernel compile problem
I have just tried to compile a clean source (without any patches) of v2.4.14. I did a straight make oldconfig of a working v2.4.13 .config. I get the following error message at that last part of the make bzImage when it is creating the final kernel image: ld -m elf_i386 -T /usr/src/linux/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o \ --start-group \ arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \ drivers/char/char.o drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/char/agp/agp.o drivers/ide/idedriver.o drivers/scsi/scsidrv.o drivers/cdrom/driver.o drivers/pci/driver.o drivers/video/video.o \ net/network.o \ /usr/src/linux/arch/i386/lib/lib.a /usr/src/linux/lib/lib.a /usr/src/linux/arch/i386/lib/lib.a \ --end-group \ -o vmlinux drivers/block/block.o: In function `lo_send': drivers/block/block.o(.text+0x894f): undefined reference to `deactivate_page' drivers/block/block.o(.text+0x8999): undefined reference to `deactivate_page' make: *** [vmlinux] Error 1 I suspect others will have the same problem. Any idea of a fix? Please respond by email to either [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: v2.4.14 kernel compile problem
This is a kernel problem, nothing to do with Debian. It has been posted to the linux-kernel list, but no fix has been posted yet. This may be another case where they fix it and make another release in a SHORT period of time. Commenting out the two references to the function and recompiling seems to work. Ben At 10:54 PM 11/5/01 -0500, you wrote: I have just tried to compile a clean source (without any patches) of v2.4.14. I did a straight make oldconfig of a working v2.4.13 .config. I get the following error message at that last part of the make bzImage when it is creating the final kernel image: ld -m elf_i386 -T /usr/src/linux/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o \ --start-group \ arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \ drivers/char/char.o drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/char/agp/agp.o drivers/ide/idedriver.o drivers/scsi/scsidrv.o drivers/cdrom/driver.o drivers/pci/driver.o drivers/video/video.o \ net/network.o \ /usr/src/linux/arch/i386/lib/lib.a /usr/src/linux/lib/lib.a /usr/src/linux/arch/i386/lib/lib.a \ --end-group \ -o vmlinux drivers/block/block.o: In function `lo_send': drivers/block/block.o(.text+0x894f): undefined reference to `deactivate_page' drivers/block/block.o(.text+0x8999): undefined reference to `deactivate_page' make: *** [vmlinux] Error 1 I suspect others will have the same problem. Any idea of a fix? Please respond by email to either [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: v2.4.14 kernel compile problem
On Mon, 5 Nov 2001, James D Freels wrote: make: *** [vmlinux] Error 1 I suspect others will have the same problem. Any idea of a fix? Quoting [EMAIL PROTECTED]: If you're using pgcc, try getting a real less-buggy compiler, like egcs1.1.2 or gcc-2.95. -- Baloo
kernel compile problem
hi! I tried to compile the kernel of my potato distro (kernel is quite old: 2.2.17) and I got the following error message: as86: command not found; or something like that. The main problem the as86 is seems to be missing from my machine. Does anyone some guess what the hell is this? Or which package should I install in order to get this as86? thanks in advance! gabi EGON - az ingyenes levelezorendszer http://egon.gyaloglo.hu
Re: kernel compile problem
hi! I tried to compile the kernel of my potato distro (kernel is quite old: 2.2.17) and I got the following error message: as86: command not found; or something like that. The main problem the as86 is seems to be missing from my machine. Does anyone some guess what the hell is this? Or which package should I install in order to get this as86? thanks in advance! gabi EGON - az ingyenes levelezorendszer http://egon.gyaloglo.hu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] I believe that you should do an apt-get install bin86 Because: Package: bin86 0.14.9-3 16-bit assembler and loader This is the as86 and ld86 distribution written by Bruce Evans. It's a complete 8086 assembler and loader which can make 32-bit code for the 386+ processors (under Linux it's used only to create the 16-bit bootsector and setup binaries). Klaus Ade GnuPG v1.0.6 http://www.astro.uio.no/~klaus
Re: kernel compile problem
On Mon, Sep 17, 2001 at 10:50:57AM +0200, pink panther wrote: hi! I tried to compile the kernel of my potato distro (kernel is quite old: 2.2.17) and I got the following error message: as86: command not found; or something like that. The main problem the as86 is seems to be missing from my machine. Does anyone some guess what the hell is this? Or which package should I install in order to get this as86? I'm pretty sure it's the package bin86. thanks in advance! gabi Duncan Findlay
Kernel Compile Problem
When compile 2.4.9 kernel with gcc 3.0.2 : #make-kpkg clean #make-kpkg --append-to-version -tao3 kernel_image #make-kpkg clean #make-kpkg --append-to-version -tao4 kernel_image #make-kpkg clean #make-kpkg --append-to-version -tao5 kernel_image (install the three kernels) #cd /boot #ls -l ... -rw-r--r--1 root root 706298 Sep 7 12:50 vmlinuz-2.4.9-tao3 -rw-r--r--1 root root 706300 Sep 7 13:36 vmlinuz-2.4.9-tao4 -rw-r--r--1 root root 706299 Sep 7 13:52 vmlinuz-2.4.9-tao5 the configuration of the three kernels are same, why the size of them are diffient? -- Regards Tao Liu _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: Kernel Compile Problem
High, On Fri, 7 Sep 2001, Tao Liu wrote: When compile 2.4.9 kernel with gcc 3.0.2 : #make-kpkg clean #make-kpkg --append-to-version -tao3 kernel_image #make-kpkg clean #make-kpkg --append-to-version -tao4 kernel_image #make-kpkg clean #make-kpkg --append-to-version -tao5 kernel_image (install the three kernels) #cd /boot #ls -l ... -rw-r--r--1 root root 706298 Sep 7 12:50 vmlinuz-2.4.9-tao3 -rw-r--r--1 root root 706300 Sep 7 13:36 vmlinuz-2.4.9-tao4 -rw-r--r--1 root root 706299 Sep 7 13:52 vmlinuz-2.4.9-tao5 the configuration of the three kernels are same, why the size of them are diffient? I do not think this is a big problem. The kernels are different too, though the only difference is a 3,4 and 5. The kernels are packed, so perhaps the number 3 is used a lot more in the kernel than the number 4, and therefore packed better. Another wild guess is that gzipping zips a bit different every time. I am not sure of this, but I have heard that some packagers (powerpacker, DMS) pack different every time. You should try something like this: #make-kpkg clean #make-kpkg --append-to-version -tao4 kernel_image install kernel note the size delete the kernel #make-kpkg clean #make-kpkg --append-to-version -tao4 kernel_image install kernel note the size delete the kernel and see if the sizes change. Greetz, Sebastiaan
Re: kernel compile problem
on Sat, Aug 04, 2001 at 04:51:06PM -0500, Jay Latham ([EMAIL PROTECTED]) wrote: I was going to re-compile my kernel today to get rid of some of the things I don't need but when I got to the network card driver modules, mine was greyed out (Realtec 8139). This is on the 2.2.19pre17 kernel. I then went to the 2.2.19 kernel which offered two drivers (rtl8139 and 8139too), but again both were greyed out. What do I need to activate in an earlier screen to make these drivers available to me. Networking support is activated as is module support. Both kernels came from debian. I haven't tried one from www.kernel.org yet. Also which one of these kernels is the latest version? I'm not at my debian workstation or I would look at the readme. Have you selected experimental features option? Many options are disabled unless this is set. -- Karsten M. Self kmself@ix.netcom.comhttp://kmself.home.netcom.com/ What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org Free Dmitry!! Boycott Adobe!! Repeal the DMCA!! http://www.freesklyarov.org Geek for Hire http://kmself.home.netcom.com/resume.html pgpDupLa8FQPX.pgp Description: PGP signature
kernel compile problem
I was going to re-compile my kernel today to get rid of some of the things I don't need but when I got to the network card driver modules, mine was greyed out (Realtec 8139). This is on the 2.2.19pre17 kernel. I then went to the 2.2.19 kernel which offered two drivers (rtl8139 and 8139too), but again both were greyed out. What do I need to activate in an earlier screen to make these drivers available to me. Networking support is activated as is module support. Both kernels came from debian. I haven't tried one from www.kernel.org yet. Also which one of these kernels is the latest version? I'm not at my debian workstation or I would look at the readme. Thanks -- Jay Latham Driving while talking on a cell phone is like multi-tasking in Windows...Sooner or later your going to crash!
Kernel Compile Problem
When I try to compile the kernel I get this error: gcc: Internal compiler error: program cc1 got fatal signal 11 The compile then exits. It does not seem to matter which kernel I try. I tried both gcc 2.95.2 and 2.7.2. It gets this error in different places. In the most recent (kernel 2.2.15) it exited here: gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce -mpreferred-stack-boundary=2 -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -c -o aic7xxx.o aic7xxx.c gcc: Internal compiler error: program cc1 got fatal signal 11 make[4]: *** [aic7xxx.o] Error 1 I tried both make-kpkg and doing it manually. I have the latest Debian libraries installed. The last time I compiled was kernel 2.2.12 which worked -- 6 months ago. But now even that will not compile. Since then I have upgraded all my libraries and gcc. Can anyone help? Thanks, Matt Simpson
Re: Kernel Compile Problem
http://www.bitwizard.nl/sig11/ Matthew Simpson wrote: When I try to compile the kernel I get this error: gcc: Internal compiler error: program cc1 got fatal signal 11
Kernel compile problem
I am having problems with recompiling my kernel. I had kernel 2.2.12 and recompiled it to thw same 2.2.12 but to include ip_masquerading. Now when I boot I see depmod: *** Unresolved symbols in /lib/modules/2.2.12/ipv4/ip_masq_quake.o depmod: *** Unresolved symbols in /lib/modules/2.2.12/ipv4/ip_masq_vdolive.o depmod: *** Unresolved symbols in /lib/modules/2.2.12/ipv4/ip_masq_cuseeme.o What do I need to do to fix this?
Re: Kernel compile problem
Jay Kelly wrote: I am having problems with recompiling my kernel. I had kernel 2.2.12 and recompiled it to thw same 2.2.12 but to include ip_masquerading. Now when I boot I see depmod: *** Unresolved symbols in /lib/modules/2.2.12/ipv4/ip_masq_quake.o depmod: *** Unresolved symbols in /lib/modules/2.2.12/ipv4/ip_masq_vdolive.o depmod: *** Unresolved symbols in /lib/modules/2.2.12/ipv4/ip_masq_cuseeme.o What do I need to do to fix this? this looks like you forgot to make modules?, make modules install? either that, or old modules left over from the previous build. ron
kernel compile problem
Here is the last lines of my make-kpkg --revision=custom.1.0 kernel_image ..snip.. install -p -d -o root -g root -m 755 debian/tmp-image/usr/share/doc/kernel-image-2.3.16 sed -e 's/=V/2.3.16/g'-e 's/=B//g' \ -e 's/=S//g' -e 's/=R//g' \ -e 's/=K/bzImage/g' -e 's/=L/lilo/g' \ -e 's,=D,/boot,g' \ /usr/share/kernel-package/image.postinst debian/tmp-image/DEBIAN/postinst chmod 755 debian/tmp-image/DEBIAN/postinst sed -e 's/=V/2.3.16/g'-e 's/=B//g' \ -e 's/=S//g' -e 's/=R//g' \ -e 's/=K/bzImage/g' -e 's/=L/lilo/g' \ -e 's,=D,/boot,g' \ /usr/share/kernel-package/image.postrm debian/tmp-image/DEBIAN/postrm chmod 755 debian/tmp-image/DEBIAN/postrm sed -e 's/=V/2.3.16/g'-e 's/=L/lilo/g' \ /usr/share/kernel-package/image.preinst debian/tmp-image/DEBIAN/preinst chmod 755 debian/tmp-image/DEBIAN/preinst sed -e 's/=V/2.3.16/g'-e 's/=L/lilo/g' \ /usr/share/kernel-package/image.prerm debian/tmp-image/DEBIAN/prerm chmod 755 debian/tmp-image/DEBIAN/prerm install -p-o root -g root -m 644 debian/changelog \ debian/tmp-image/usr/share/doc/kernel-image-2.3.16/changelog.Debian install: debian/changelog: No such file or directory make: *** [kernel-image-deb] Error 1 I recompiled the kernel just a few days ago and it worked just fine. I did an update/ugrade and also installed most of the debian alsa stuff after that. And now this is what I get. Tried bothe 2.3.16 and 2.3.18 but the both ends in the same way. Best regards Joakim
Re: kernel compile problem
See also bug #47054, which suggests a one-line additon to the kernel-package script that's probably a better fix to this problem (though I haven't tested it).
Re: kernel compile problem
-BEGIN PGP SIGNED MESSAGE- On 10 Oct 1999, David Coe wrote: See also bug #47054, which suggests a one-line additon to the kernel-package script that's probably a better fix to this problem (though I haven't tested it). I got it to work by changing line 759 to the following: stamp-image: debian configure build kernel-image-deb Looking at it now, i think adding both this and the patch in the bug report would be the best solution. A combined patch is below. - --- rules Sun Oct 10 14:18:02 1999 +++ rules Sun Oct 10 14:13:57 1999 @@ -756,7 +756,7 @@ touch stamp-doc kernel-image kernel_image: stamp-image - -stamp-image: configure build kernel-image-deb +stamp-image: debian configure build kernel-image-deb # % make config # % make-kpkg build # % sudo make -f debian/rules kernel-image-deb @@ -767,6 +767,7 @@ rm -f -r ./debian/tmp-image ./debian/tmp-image.deb test -f stamp-configure || $(deb_rule) configure test -f stamp-build || $(deb_rule) build + test -f stamp-debian || $(deb_rule) debian $(make_directory) debian/tmp-image/DEBIAN $(make_directory) debian/tmp-image/boot $(make_directory) debian/tmp-image/usr/share/doc/$(i_package) -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: noconv iQCVAwUBOADmxb7M/9WKZLW5AQEn8gP/Vd+oirQ/J18lXRdHpoIqF7vtS+WNCbzz AAD+pGbNErlwtaM07Jiu0JUUTwvm98wBLaWVLdQvQPKR1XFxY0EDEOrBT+7Trnin +BihKj5505//LRxfSQgRIYaQljmaRg3Y9DGnRh6iYlP5T33pUh7wteUKISePmzzO SI4pzFkxQwM= =8JrE -END PGP SIGNATURE-
Re: kernel compile problem
Brad [EMAIL PROTECTED] writes: On 10 Oct 1999, David Coe wrote: See also bug #47054, which suggests a one-line additon to the... I got it to work by changing line 759 to the following... Thanks!
Re: Kernel compile problem
Roger Franz [EMAIL PROTECTED] writes: I got a sound card (my wife insisted on having a sound card), and am now trying to recompile the kernel to include support for it. I've got the configuration set up, and everything appears to be correct. I run make-kpkg, and it runs until I get this: gcc: Internal compiler error: Program cc1 got fatal signal 11. This apparently occurs at random points during the run of the compile; this particular one occurred while compiling init.o. Previous errors have occurred at floppy.o, keyboard.o, pty.o. I get the same error trying to compile the kernel manually (make clean, make config, make dep, make zImage). I think you should read the sig11 FAQ at http://www.bitwizard.nl/sig11/. It could help you a bit. btw, I'm having same kind of problems, but sometimes my machine lockups completely. I haven't investigated what's the cause. I can still compile kernels, I just use 'make-kpkg kernel_image' again. It continues there it left before the lockup and the compiled kernel works fine. Sorry about my english, Kalle Valo
Re: Kernel compile problem
On Sun, Nov 29, 1998 at 07:06:29PM +, Roger Franz wrote: gcc: Internal compiler error: Program cc1 got fatal signal 11. Ohh, nasty. AFAIR this means you have some bad mem or cpu (more likely memory). I could be wrong. --- I once got some messages like the above. I re-loaded the kernel sources, re-configured and tried again -- and the problem went away. Maybe a 'make clean' would have helped, then again maybe my kernel sources really did get corrupted somehow. I think this did happen the first time I tried to compile sound. I did happen on after the 3rd or 4th compile of the kernel however. This was under debian 1.3.1 and I seem to remember that the sound configuration option was sortof broken under 1.3.1 (not all of the options could be selected. did not have the problem under slackware, or debian 2.0). _ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: Kernel compile problem
On Mon, Nov 30, 1998 at 05:05:24 -0800, Kenneth Scharf wrote: On Sun, Nov 29, 1998 at 07:06:29PM +, Roger Franz wrote: gcc: Internal compiler error: Program cc1 got fatal signal 11. Ohh, nasty. AFAIR this means you have some bad mem or cpu (more likely memory). Not necessarily, but quite possibly. Check out the FAQ at http://www.bitwizard.nl/sig11/ Ray -- PATRIOTISM A great British writer once said that if he had to choose between betraying his country and betraying a friend he hoped he would have the decency to betray his country. - The Hipcrime Vocab by Chad C. Mulligan
Kernel compile problem
I got a sound card (my wife insisted on having a sound card), and am now trying to recompile the kernel to include support for it. I've got the configuration set up, and everything appears to be correct. I run make-kpkg, and it runs until I get this: gcc: Internal compiler error: Program cc1 got fatal signal 11. This apparently occurs at random points during the run of the compile; this particular one occurred while compiling init.o. Previous errors have occurred at floppy.o, keyboard.o, pty.o. I get the same error trying to compile the kernel manually (make clean, make config, make dep, make zImage). Sometimes I get a message saying that cpp has experienced a broken output pipe. Sometimes I don't. What am I missing? I tried turning off the CPU cache, and it didn't change this behavior. I can run this inside of X and outside of X, and I get the same problem. The headers and the source are both present. If it matters, I'm running a Cyrix 6x86L P200+. Disk space available is 75MB or so; memory is 80MB. Help... Roger Franz
Re: Kernel compile problem
On Sun, Nov 29, 1998 at 07:06:29PM +, Roger Franz wrote: gcc: Internal compiler error: Program cc1 got fatal signal 11. Ohh, nasty. AFAIR this means you have some bad mem or cpu (more likely memory). I could be wrong. -- --- - - --- - - - --- Ben Collins [EMAIL PROTECTED] Debian GNU/Linux UnixGroup Admin - Jordan Systems Inc. [EMAIL PROTECTED] -- -- - - - --- --- -- The Choice of the GNU Generation
Re: Kernel compile problem
On Sun, 29 Nov 1998 19:06:29 +, you wrote: I run make-kpkg, and it runs until I get this: gcc: Internal compiler error: Program cc1 got fatal signal 11. This apparently occurs at random points during the run of the compile; this particular one occurred while compiling init.o. Previous errors have occurred at floppy.o, keyboard.o, pty.o. I get the same error trying to compile the kernel manually (make clean, make config, make dep, make zImage). This combined with the randomness of the failure suggests bad hardware. I'd suspect bad memory first, followed by a bad main board. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber |Questions are the | Mailadresse im Header Karlsruhe, Germany | Beginning of Wisdom | Fon: *49 721 966 32 15 Nordisch by Nature | Lt. Worf, TNG Rightful Heir | Fax: *49 721 966 31 29
Help! kernel compile problem
I thought I'd build a nice slim 'n trim kernel for one of my machines... so I went and did a make config, then did 'make zImage' and got: ld -m elf_i386 -Ttext 0x10 -e stext arch/i386/kernel/head.o init/main.o init/version.o \ arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o net/network.a \ fs/filesystems.a \ drivers/block/block.a drivers/char/char.a drivers/net/net.a drivers/pci/pci.a \ /usr/src/linux/arch/i386/lib/lib.a /usr/src/linux/lib/lib.a /usr/src/linux/arch/i386/lib/lib.a -o vmlinux init/main.o: In function `start_kernel': init/main.o(.text+0x8fb): undefined reference to `bigphysarea_init' init/main.o(.data+0xf0): undefined reference to `scsi_luns_setup' init/main.o(.data+0xf8): undefined reference to `st_setup' init/main.o(.data+0x100): undefined reference to `msmouse_setup' init/main.o(.data+0x108): undefined reference to `ppa_setup' init/main.o(.data+0x118): undefined reference to `bigphysarea_setup' arch/i386/kernel/kernel.o: In function `restore_i387': arch/i386/kernel/kernel.o(.text+0x9c2): undefined reference to `restore_i387_soft' arch/i386/kernel/kernel.o: In function `save_i387': arch/i386/kernel/kernel.o(.text+0xc32): undefined reference to `save_i387_soft' arch/i386/kernel/kernel.o: In function `do_signal': arch/i386/kernel/kernel.o(.text+0x13e9): undefined reference to `math_emulate' kernel/kernel.o(.data+0x104): undefined reference to `bigphysarea_alloc' kernel/kernel.o(.data+0x10c): undefined reference to `bigphysarea_free' kernel/kernel.o(.data+0x114): undefined reference to `bigphysarea' fs/fs.o: In function `sys_setup': fs/fs.o(.text+0xd9fe): undefined reference to `init_ext_fs' fs/fs.o(.text+0xda26): undefined reference to `init_smb_fs' fs/fs.o(.text+0xda2b): undefined reference to `init_iso9660_fs' fs/fs.o(.text+0xda30): undefined reference to `init_sysv_fs' fs/fs.o(.text+0xda35): undefined reference to `init_hpfs_fs' fs/fs.o(.text+0xda3a): undefined reference to `init_ufs_fs' drivers/block/block.a(ll_rw_blk.o): In function `blk_dev_init': ll_rw_blk.o(.text+0xedc): undefined reference to `loop_init' drivers/block/block.a(genhd.o): In function `device_setup': genhd.o(.text+0x7ed): undefined reference to `scsi_dev_init' drivers/char/char.a(misc.o): In function `misc_init': misc.o(.text+0x240): undefined reference to `psaux_init' misc.o(.text+0x245): undefined reference to `ms_bus_mouse_init' drivers/net/net.a(Space.o): In function `ethif_probe': Space.o(.text+0x22): undefined reference to `tc59x_probe' Space.o(.text+0x2f): undefined reference to `el3_probe' make: *** [vmlinux] Error 1 Which bugs me since most of the things it's bitching about aren't even in my .config! Help! --Zachary PS: my .config is: # # Automatically generated make config: don't edit # # # Code maturity level options # # CONFIG_EXPERIMENTAL is not set # # Loadable module support # CONFIG_MODULES=y # CONFIG_MODVERSIONS is not set # CONFIG_KERNELD is not set # # General setup # # CONFIG_MATH_EMULATION is not set CONFIG_NET=y # CONFIG_MAX_16M is not set CONFIG_PCI=y # CONFIG_MCA is not set CONFIG_SYSVIPC=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_KERNEL_ELF=y # CONFIG_M386 is not set CONFIG_M486=y # CONFIG_M586 is not set # CONFIG_M686 is not set # CONFIG_BIGPHYS_AREA is not set # # Floppy, IDE, and other block devices # CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_IDE=y # # Please see Documentation/ide.txt for help/info on IDE drives # # CONFIG_BLK_DEV_HD_IDE is not set # CONFIG_BLK_DEV_IDECD is not set # CONFIG_BLK_DEV_IDETAPE is not set # CONFIG_BLK_DEV_IDE_PCMCIA is not set CONFIG_BLK_DEV_CMD640=y # CONFIG_BLK_DEV_CMD640_ENHANCED is not set CONFIG_BLK_DEV_RZ1000=y CONFIG_BLK_DEV_TRITON=y CONFIG_IDE_CHIPSETS=y # # Note: most of these also require special kernel boot parameters # # CONFIG_BLK_DEV_ALI14XX is not set # CONFIG_BLK_DEV_DTC2278 is not set # CONFIG_BLK_DEV_HT6560B is not set # CONFIG_BLK_DEV_QD6580 is not set # CONFIG_BLK_DEV_UMC8672 is not set # # Additional Block Devices # # CONFIG_BLK_DEV_LOOP is not set # CONFIG_BLK_DEV_MD is not set # CONFIG_BLK_DEV_RAM is not set # CONFIG_BLK_DEV_XD is not set # CONFIG_BLK_DEV_HD is not set # # Networking options # # CONFIG_FIREWALL is not set CONFIG_NET_ALIAS=y CONFIG_INET=y # CONFIG_IP_FORWARD is not set # CONFIG_IP_MULTICAST is not set CONFIG_SYN_COOKIES=y # CONFIG_IP_ACCT is not set # CONFIG_IP_ROUTER is not set # CONFIG_NET_IPIP is not set CONFIG_IP_ALIAS=y # # (it is safe to leave these untouched) # # CONFIG_INET_PCTCP is not set # CONFIG_INET_RARP is not set # CONFIG_NO_PATH_MTU_DISCOVERY is not set CONFIG_IP_NOSR=y CONFIG_SKB_LARGE=y # # # # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_AX25 is not set # CONFIG_NETLINK is not set # # SCSI support # # CONFIG_SCSI is not set # # Network device support # CONFIG_NETDEVICES=y CONFIG_DUMMY=y # CONFIG_EQUALIZER is not set # CONFIG_PLIP is not set # CONFIG_PPP is not set # CONFIG_SLIP is not set #
Re: Help! kernel compile problem
On Mon, 30 Jun 1997 21:11:32 CDT Zachary DeAquila ([EMAIL PROTECTED] .org) wrote: I thought I'd build a nice slim 'n trim kernel for one of my machines... so I went and did a make config, then did 'make zImage' and got: [snip] And you probably forgot to make clean and make dep in the action... Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: kernel compile problem
-BEGIN PGP SIGNED MESSAGE- On Tue, 10 Sep 1996, Vadik V. Vygonets wrote: vadikCrazy -- yes, hacker -- not yet :) don't beleave him! vadikBorik you promised me RedHat fortune ;) fortune (RedHat) ___ Boris Beletsky [EMAIL PROTECTED] For pgp public key, e-mail me with subject get pgp-key. ___ In Linux veritas -BEGIN PGP SIGNATURE- Version: 2.6.3ia+ Charset: latin1 Comment: Boris Beletsky [EMAIL PROTECTED] iQCVAwUBMjXQbwz8DjY6pgpxAQELCQP/QkZ9F7XaAnMint+x4rZt7g8K7pWlxrI0 45PDYvqDll0kkcjTW4KmBIKMg1YyTrBAmF++ykCVh76xI35cqvf3YGdCgu8by03e WOCQKbwB33UgSR5zM6C12VfXxH6LRLs7gM8BoG7+ZbDHyPh8B0LILLwT0wppjt2X /z4se01KAnQ= =/7RF -END PGP SIGNATURE-
kernel compile problem
i everybody. I want to update my linux kernel to one which can run ELF format. I get the linux kernel 2.0.18 i think is the newest version??. when i try to compile i receive a message on the screen telling me gcc is to old. Then i get the new gcc version and when i try ro run it a see a new message Can't run binary file i think this is because the new gcc is on ELF format. now my question is which gcc (what version ?) or what i have to do for compile the new kernel.? thanks guillermo solis A TI2SAG
Re: kernel compile problem
-BEGIN PGP SIGNED MESSAGE- On Mon, 9 Sep 1996, Guillermo Solis wrote: gsolisI want to update my linux kernel to one which can run gsolisELF format. I get the linux kernel 2.0.18 i think is the newest gsolisversion??. yes, but that will change gsoliswhen i try to compile i receive a message on the screen gsolistelling me gcc is to old. Then i get the new gcc version gsolisand when i try ro run it a see a new message Can't run binary file gsolisi think this is because the new gcc is on ELF format. gsolisnow my question is which gcc (what version ?) or what i have to do gsolisfor compile the new kernel.? i whould say - reinstall the all system there lots of thigs that u need to upgrade - libs , etc.. so i think thats the best thing u could do. if u're realy want to do it manualy (NOOO!!!) then email [EMAIL PROTECTED] he is the only person i know that did it. (crazy hacker) Regards borik ___ Boris Beletsky [EMAIL PROTECTED] For pgp public key, e-mail me with subject get pgp-key. ___ In Linux veritas -BEGIN PGP SIGNATURE- Version: 2.6.3ia+ Charset: latin1 Comment: Boris Beletsky [EMAIL PROTECTED] iQCVAwUBMjS8Awz8DjY6pgpxAQGdwgP8C0ZLkw0hFpw56wp7aokqOnwmTUkqCrYA t/rrSArAIEnXq2qPNdWflF8hQXH7dGjVFlodnQt34tMD+RBBG/FUecqSbr2mWDra CIHA7esAiOlh9ryC6+In0E0jUxaIW4jZZuLX1f1U+2dLGRX7rUGA0vcs37O1FIte CAygTrnM4J4= =K1dy -END PGP SIGNATURE-
Re: kernel compile problem
On Mon, 9 Sep 1996, Guillermo Solis wrote: i everybody. I want to update my linux kernel to one which can run ELF format. I get the linux kernel 2.0.18 i think is the newest version??. when i try to compile i receive a message on the screen telling me gcc is to old. Then i get the new gcc version and when i try ro run it a see a new message Can't run binary file i think this is because the new gcc is on ELF format. now my question is which gcc (what version ?) or what i have to do for compile the new kernel.? You should start with your old kernel. Build it with the old gcc with ELF support added. That is, build the kernel as a.out but with ELF support. Now you can install the new gcc (seems to me you need some shared libraries like libc5 and others. Check out the docs in the upgrades directory). You should now be able to build a new kernel in ELF format. Hope this helps, Dwarf -- aka Dale Scheetz Phone: 1 (904) 877-0257 Flexible Software Fax: NONE Black Creek Critters e-mail: [EMAIL PROTECTED] If you don't see what you want, just ask --
Re: kernel compile problem
On Tue, 10 Sep 1996, Boris Beletsky wrote: gsolisnow my question is which gcc (what version ?) or what i have to do gsolisfor compile the new kernel.? i whould say - reinstall the all system there lots of thigs that u need to upgrade - libs , etc.. so i think thats the best thing u could do. if u're realy want to do it manualy (NOOO!!!) then email [EMAIL PROTECTED] he is the only person i know that did it. (crazy hacker) Crazy -- yes, hacker -- not yet :) I did it on my slackware (yes! in elder days of Linux) system, well, with HOWTOs in my hands (actually, with nutscrape between my fingers), but I won't tell you to RTFM, I'll gladly help. Well, but I think that upgrading debian packages will work (but I'm not sure). My current system (Debian 1.1, mostly) has a.out libs installed too. Regards borik Borik you promised me RedHat fortune ;) All the best, Vadik the Elf ([EMAIL PROTECTED]). ++_ Vadik V. (_`[EMAIL PROTECTED] http://www.arbornet.org/~vadik/ Vygonets (_.lf PGP public key (ID 9FC1DED9) available from surfnet.nl Linux hackers are funny people: They count the time in patchlevels.
