Re: Freshly compiled kernel too big?

On Fri, Dec 08, 2000 at 02:56:59PM -0600, Brian Boonstra wrote: > Hi > > > bzImage? > > > Thanks for the suggestion. I thought that was the default, but I'll > check when I get home tonight. It is according to the manpages. However, remember the kernel must be uncompressed eventually.

Re: Freshly compiled kernel too big?

Hi > bzImage? Thanks for the suggestion. I thought that was the default, but I'll check when I get home tonight. - Brian

Re: Freshly compiled kernel too big?

on Fri, Dec 08, 2000 at 11:06:06AM -0600, Brian Boonstra ([EMAIL PROTECTED]) wrote: > Hi > > I just compiled a 2.2.17 kernel. I've got plenty of RAM and disk > space, so I generally chose to compile everything in rather than add modules. > > However, when I did "make-kpkg kernel-imag

Freshly compiled kernel too big?

Hi I just compiled a 2.2.17 kernel. I've got plenty of RAM and disk space, so I generally chose to compile everything in rather than add modules. However, when I did "make-kpkg kernel-image" it complained about the image being too big. Sure it's big, but not over 5MB. What's goin

Re: Kernel too big.

John Foster wrote: > > Kent West wrote: > > I've recompiled my kernel (using bzImage) to provide sound support, and > > now I'm getting a "vmlinuz is too big" message when I try to run lilo. John Foster answered: > sounds like your trying to use the vmlinuz file from > /usr/src/linuxXXX/vmlinuz,

Re: Kernel too big.

Kent West wrote: > > I checked the archives, but didn't find much on this. > > I've recompiled my kernel (using bzImage) to provide sound support, and > now I'm getting a "vmlinuz is too big" message when I try to run lilo. > My old kernel was 715260, and my new one is 749612. I've gone through >

Kernel too big.

I checked the archives, but didn't find much on this. I've recompiled my kernel (using bzImage) to provide sound support, and now I'm getting a "vmlinuz is too big" message when I try to run lilo. My old kernel was 715260, and my new one is 749612. I've gone through "make config" and recompiled at

Re: Kernel Panic (RE: kernel too big)

"Camilo Alejandro Arboleda" wrote: >Thanks to every one for the help with my first problem. > >Finaly I could compile the new kernel, but I could not start the system >with the new kernel. > >I get this message: >'kernel panic: no init found. Try passing init = option to kernel' >

Kernel Panic (RE: kernel too big)

Thanks to every one for the help with my first problem. Finaly I could compile the new kernel, but I could not start the system with the new kernel. I get this message: 'kernel panic: no init found. Try passing init = option to kernel' What is the value of 'option'? How I pass this value to th

Re: Kernel too big

all the features of 2.1 should be in 2.2, only more stable. >When I compile the kernel with the command 'make bzImage' the image >generated has a size of about 800.000 bytes, and when I try to install the >image using 'liloconfig' I get the error 'kernel too bi

Re: Kernel too big

>No idea, and I doubt it. Isn't it a LILO problem? No, it is because the BIOS has to load the kernel, and because the kenrel starts in real mode, not protected mode. There is a thorough description in the archives sometime this earlier this year. Carl

Re: Kernel too big

On Fri, Jun 04, 1999 at 09:31:06AM -0500, Camilo Alejandro Arboleda wrote: > > When I compile the kernel with the command 'make bzImage' the image > generated has a size of about 800.000 bytes, and when I try to install the > image using 'liloconfig' I get the erro

Re: Kernel too big

Camilo Alejandro Arboleda wrote: > When I compile the kernel with the command 'make bzImage' the image > generated has a size of about 800.000 bytes, and when I try to install the > image using 'liloconfig' I get the error 'kernel too big', but I canno

Kernel too big

Hello: My name is Camilo. I am trying to compile the Linux kernel 2.1. When I compile the kernel with the command 'make bzImage' the image generated has a size of about 800.000 bytes, and when I try to install the image using 'liloconfig' I get the error 'kernel too

Re: size of kernel too big?

Hello everybody, hi I recently compiled kernel 2.2.1 (my 1st attempt), and everything seems to be going smoothly (except for playing .wav files, but that's another story...) Anyway, did not put anything into "modules" (is that bad?)... Now, when I look at my /var/log/messages, I s

Re: size of kernel too big?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 25 Feb 1999 17:43:14 -0600, rich wrote: >monkeyhouse kernel: Memory: 30616k/32768k available (1000k kernel code, >416k reserved, 629k data, 44k init)Feb25 Memory: 63416k/65536k available (824k kernel code, 412k reserved, 856k data, 28k init)

size of kernel too big?

Hello everybody, I recently compiled kernel 2.2.1 (my 1st attempt), and everything seems to be going smoothly (except for playing .wav files, but that's another story...) Anyway, did not put anything into "modules" (is that bad?)... Now, when I look at my /var/log/messages, I see this... monkeyho

Re: Kernel compilation error / Kernel too big.

Andrew Ivanov wrote: > > I have binutils 2.9.1-0.2 installed, which is what I think , at least > this is a requirement for kernel source, as it's said on www.debian.org > And compilation ran with binutils installed, and I got that error. > Andrew > The as86 program is in the 'bin86' pac

Re: Kernel compilation error / Kernel too big.

I have binutils 2.9.1-0.2 installed, which is what I think , at least this is a requirement for kernel source, as it's said on www.debian.org And compilation ran with binutils installed, and I got that error. Andrew Never includ

Re: Kernel compilation error / Kernel too big.

On Sat, Nov 21, 1998 at 02:30:12AM -0600, Andrew Ivanov wrote: > I just finished compiling my own kernel( 2.0.34), and it comes out of size > 788K, which is too big for Lilo to handle. > Are there any ways around it? > > I tried make bzImage, like HOWTO suggested, but at the end of compilation > I

Re: Kernel compilation error / Kernel too big.

Andrew Ivanov wrote: > > I just finished compiling my own kernel( 2.0.34), and it comes out of size > 788K, which is too big for Lilo to handle. > Are there any ways around it? > > I tried make bzImage, like HOWTO suggested, but at the end of compilation > I get: > as86 -0 -a -o bbootsect.o bboot

Kernel compilation error / Kernel too big.

I just finished compiling my own kernel( 2.0.34), and it comes out of size 788K, which is too big for Lilo to handle. Are there any ways around it? I tried make bzImage, like HOWTO suggested, but at the end of compilation I get: as86 -0 -a -o bbootsect.o bbootsect.a make[1]: as86: Command not foun

Kernel Too Big Error?

I am trying to compile 2.1.127. I have tried make zImage and I get an error that System is too big. Using bzImage the kernel compiles but is 1.5 M and when I run lilo to remap I get the error that the system is too big. What can I do to correct this? I am compiling sound and various other modules