[S.u.S.E. Linux] SuSe 5.2 says new kernel is too big?
I used xconfig to make a new kernel, and at the end of 'make zImage' I
got 2 errors, basically saying that the kernel (system?) was too big (it
is slightly over 1 meg).
I can't understand this, since I cut nearly everything to the quick. My
stand-alone system has no networking, etc..
How did my kernel get this large?
I tried installing it anyway, and 'lilo' kicked out saying that the
kernel (system) is too big, so back to the old kernel, which was the
default kernel from my install (which is about 1/2 meg).
-----------------------------------------------
Man's mind is his basic tool of survival!
Lawrence Sayre
SuSE kernel's are fat, there isn't much need for most people to run a 500k kernel. They do this to provide support for many common devices, sort of a lowest commom denominator de facto kernel. My kernels are 350k and I'm not sacrificing any functionality. If you are getting 1mb kernels you have to be choosing support for a lot of devices you probably don't need. Also try using functions that you need but rarely use as modules instead of compiled directly into the kernel (parallel printer, floppy support, iso9660 fs support, dos fs support if you dual boot, sound). Lawrence Sayre wrote:
I used xconfig to make a new kernel, and at the end of 'make zImage' I got 2 errors, basically saying that the kernel (system?) was too big (it is slightly over 1 meg).
I can't understand this, since I cut nearly everything to the quick. My stand-alone system has no networking, etc..
How did my kernel get this large?
I tried installing it anyway, and 'lilo' kicked out saying that the kernel (system) is too big, so back to the old kernel, which was the default kernel from my install (which is about 1/2 meg).
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Are you using the kernel created in /usr/src/linux/arch/i386/boot? I've never seen one over 500M or so. Hope that helps. Robb
Lawrence Sayre wrote:
I used xconfig to make a new kernel, and at the end of 'make zImage' I got 2 errors, basically saying that the kernel (system?) was too big (it is slightly over 1 meg).
I can't understand this, since I cut nearly everything to the quick. My stand-alone system has no networking, etc..
How did my kernel get this large?
I tried installing it anyway, and 'lilo' kicked out saying that the kernel (system) is too big, so back to the old kernel, which was the default kernel from my install (which is about 1/2 meg).
-- Robb Romans www.swt.edu/~rr44607 His High Judgemental Supremacy, Judicial Pag, L.I.V.R. (the Learned, Impartial and Very Relaxed... -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
He isn't getting that far. His kernel is larger than zImage will tolerate. I know people that use bzImage because they have strenuous driver needs, but there is no reason for Joe Linux User on a single user box running a 2.0.x kernel to be as large as he is getting. Robb wrote:
Are you using the kernel created in /usr/src/linux/arch/i386/boot? I've never seen one over 500M or so.
Hope that helps. Robb
Lawrence Sayre wrote:
I used xconfig to make a new kernel, and at the end of 'make zImage' I got 2 errors, basically saying that the kernel (system?) was too big (it is slightly over 1 meg).
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Michael Lankton wrote:
He isn't getting that far. His kernel is larger than zImage will tolerate. I know people that use bzImage because they have strenuous driver needs, but there is no reason for Joe Linux User on a single user box running a 2.0.x kernel to be as large as he is getting.
Robb wrote:
Are you using the kernel created in /usr/src/linux/arch/i386/boot? I've never seen one over 500M or so.
Hope that helps. Robb
Lawrence Sayre wrote:
I used xconfig to make a new kernel, and at the end of 'make zImage' I got 2 errors, basically saying that the kernel (system?) was too big (it is slightly over 1 meg).
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
I made another kernel and cut even more out. This got it down to about
480K with no error messages.
Then I made the mistake of using the kernel source file instead of the
zImage as others suggested for the problem, so the advice of the others
helped in the end.
I'm happy to say that my new kernel with sound support added is
working. Now, if I could only figure out how to get my Soundblaster
AWE32 PnP to work (without resorting to the OSS driver, which doesn't
work with RealAudio) I'd be even happier.
Thanks to everyone who pitched in on this!
-----------------------------------------------
Man's mind is his basic tool of survival!
Lawrence Sayre
Lawrence Sayre wrote:
I used xconfig to make a new kernel, and at the end of 'make zImage' I got 2 errors, basically saying that the kernel (system?) was too big (it is slightly over 1 meg).
I can't understand this, since I cut nearly everything to the quick. My stand-alone system has no networking, etc..
How did my kernel get this large?
I tried installing it anyway, and 'lilo' kicked out saying that the kernel (system) is too big, so back to the old kernel, which was the default kernel from my install (which is about 1/2 meg).
----------------------------------------------- Man's mind is his basic tool of survival!
Lawrence Sayre
----------------------------------------------- -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Something that I did on my first few attempts to manually compile my own kernels was trying to install the uncompressed kernel. When I would compile the kernel, I would copy the kernel to /vmlinuz and run lilo. /usr/src/linux/vmlinuz about 870k, kernel too big /usr/src/linux/arch/i386/boot/zImage about 360k, works great!! :-) It sounds like this may be the problem. If not, maybe this will save someone else headaches. mc -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Thanks for explaining why the kernel comes from where it does. I have been trying to figure that one out. When does it get compressed and called zImage? Thanks again.. Michael Clark wrote:
Lawrence Sayre wrote:
thing that I did on my first few attempts to manually compile my own kernels was trying to install the uncompressed kernel. When I would compile the kernel, I would copy the kernel to /vmlinuz and run lilo.
/usr/src/linux/vmlinuz about 870k, kernel too big
/usr/src/linux/arch/i386/boot/zImage about 360k, works great!! :-)
It sounds like this may be the problem. If not, maybe this will save someone else headaches.
mc
-- - - -- IMHO BEST Beginners book so far. Sams' Teach Yourself Linux in 24 hours. redhat press. - Celis Gran Cru and Linux; Nowhere but South Austin Texas. - - - TEX <A HREF="http://www.ccms.net/~mhtexcollins/78704.htm"><A HREF="http://www.ccms.net/~mhtexcollins/78704.htm</A">http://www.ccms.net/~mhtexcollins/78704.htm __ / / __ _ _ _ _ __ __ / /__ / / / \// //_// \ \/ / /____/ /_/ /_/\/ /___/ /_/\_\ ...for IQs GREATER than 95/98?... --- -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
TEX wrote:
Thanks for explaining why the kernel comes from where it does. I have been trying to figure that one out. When does it get compressed and called zImage?
Thanks again..
'make zImage' deposits the compressed kernel in that directory. Neato, eh? Have Fun! Robb. -- Robb Romans www.swt.edu/~rr44607 His High Judgemental Supremacy, Judicial Pag, L.I.V.R. (the Learned, Impartial and Very Relaxed... -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
I believe that when you use: make zImage -- it makes that file if you type: make zlilo -- instead, the kernel will be compressed and installed automatically hope that helps mc TEX wrote:
Thanks for explaining why the kernel comes from where it does. I have been trying to figure that one out. When does it get compressed and called zImage?
Thanks again..
Michael Clark wrote:
Lawrence Sayre wrote:
thing that I did on my first few attempts to manually compile my own kernels was trying to install the uncompressed kernel. When I would compile the kernel, I would copy the kernel to /vmlinuz and run lilo.
/usr/src/linux/vmlinuz about 870k, kernel too big
/usr/src/linux/arch/i386/boot/zImage about 360k, works great!! :-)
It sounds like this may be the problem. If not, maybe this will save someone else headaches.
mc
-- - - -- IMHO BEST Beginners book so far. Sams' Teach Yourself Linux in 24 hours. redhat press.
- Celis Gran Cru and Linux; Nowhere but South Austin Texas. - - - TEX <A HREF="http://www.ccms.net/~mhtexcollins/78704.htm"><A HREF="http://www.ccms.net/~mhtexcollins/78704.htm</A">http://www.ccms.net/~mhtexcollins/78704.htm
__ / / __ _ _ _ _ __ __ / /__ / / / \// //_// \ \/ / /____/ /_/ /_/\/ /___/ /_/\_\ ...for IQs GREATER than 95/98?... ---
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Michael Clark wrote:
Lawrence Sayre wrote:
I used xconfig to make a new kernel, and at the end of 'make zImage' I got 2 errors, basically saying that the kernel (system?) was too big (it is slightly over 1 meg).
I can't understand this, since I cut nearly everything to the quick. My stand-alone system has no networking, etc..
How did my kernel get this large?
I tried installing it anyway, and 'lilo' kicked out saying that the kernel (system) is too big, so back to the old kernel, which was the default kernel from my install (which is about 1/2 meg).
----------------------------------------------- Man's mind is his basic tool of survival!
Lawrence Sayre
----------------------------------------------- -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Something that I did on my first few attempts to manually compile my own kernels was trying to install the uncompressed kernel. When I would compile the kernel, I would copy the kernel to /vmlinuz and run lilo.
/usr/src/linux/vmlinuz about 870k, kernel too big
/usr/src/linux/arch/i386/boot/zImage about 360k, works great!! :-)
It sounds like this may be the problem. If not, maybe this will save someone else headaches.
mc
That was it. I found zImage right where you said I would.
Thanks! The new kernel is working just fine!!!!
-----------------------------------------------
Man's mind is his basic tool of survival!
Lawrence Sayre
participants (5)
-
lsayre@integrityonline13.com
-
mclark@datsrvr.datsit.com
-
mhtexcollins@ccms.net
-
rr44607@swt.edu
-
satan@nfinity.com