Re: [SuSE Linux] Suse 5.3 Kernel build errors
On Sun, 15 Nov 1998 14:34:24 -0800, Martin Hess wrote:
I tried to rebuild the kernel with the 5.3 distribution with smp turned on.
I got a compile error in ide-tape.c. Didn't need it, so I removed it from the configuration.
Built again, and this time I got the error "System is too big".
I have 2GB free on disk so i'm not running out of space.
I got this too. It means the kernel is too big. I'm not sure what constitutes too big, however, since the kernal I compiled was smaller than the ones that come with SuSE. Try removing some items in the kernal and recompile. Casey Bralla Chief Nerd in Residence NerdWorld.net (A Vorlon Information Technologies Company) - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
I have you checked the number of inodes you allocated for your system. If you run out of those, you might get such messages. Regards, Sandra Carney Casey Bralla wrote:
On Sun, 15 Nov 1998 14:34:24 -0800, Martin Hess wrote:
I tried to rebuild the kernel with the 5.3 distribution with smp turned on.
I got a compile error in ide-tape.c. Didn't need it, so I removed it from the configuration.
Built again, and this time I got the error "System is too big".
I have 2GB free on disk so i'm not running out of space.
I got this too. It means the kernel is too big. I'm not sure what constitutes too big, however, since the kernal I compiled was smaller than the ones that come with SuSE. Try removing some items in the kernal and recompile.
Casey Bralla
Chief Nerd in Residence NerdWorld.net (A Vorlon Information Technologies Company)
- 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
Hi, On Sun, Nov 15, Sandy Carney wrote:
I have you checked the number of inodes you allocated for your system. If you run out of those, you might get such messages.
No. In this case you will get a "no space left on device" message. "System is too big" just means that the kernel is too big (loading of the kernel happens in real mode, so the old 640KB limit applies). Creating a bzImage solves the problem, as the new loader is able to use the "high" memory for loading and decompressing the kernel. Or use modules.
Regards, Sandra Carney
Casey Bralla wrote:
On Sun, 15 Nov 1998 14:34:24 -0800, Martin Hess wrote:
I tried to rebuild the kernel with the 5.3 distribution with smp turned on.
I got a compile error in ide-tape.c. Didn't need it, so I removed it from the configuration.
Built again, and this time I got the error "System is too big".
I have 2GB free on disk so i'm not running out of space.
I got this too. It means the kernel is too big. I'm not sure what constitutes too big, however, since the kernal I compiled was smaller than the ones that come with SuSE. Try removing some items in the kernal and recompile.
Casey Bralla
Chief Nerd in Residence NerdWorld.net (A Vorlon Information Technologies Company)
- 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
-- -o) Hubert Mantel Goodbye, dots... /\\ _\_v - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Sydney, 24 November 1998 - 10:15 AM It is a very good question "...what constitutes too big" !!! I too compiled smaller kernels than the ones that come with SuSE, and I was getting the "... too big message". Interesting. inemes@transylvania.com.au PS: I AM STILL WAITING FOR THE REPLACEMENT CDs AND FOR WABI !!! THANK YOU S.u.S.E. Casey Bralla wrote:
On Sun, 15 Nov 1998 14:34:24 -0800, Martin Hess wrote:
I tried to rebuild the kernel with the 5.3 distribution with smp turned on.
I got a compile error in ide-tape.c. Didn't need it, so I removed it from the configuration.
Built again, and this time I got the error "System is too big".
I have 2GB free on disk so i'm not running out of space.
I got this too. It means the kernel is too big. I'm not sure what constitutes too big, however, since the kernal I compiled was smaller than the ones that come with SuSE. Try removing some items in the kernal and recompile.
Casey Bralla
Chief Nerd in Residence NerdWorld.net (A Vorlon Information Technologies Company)
- 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
inemes wrote:
Sydney, 24 November 1998 - 10:15 AM
It is a very good question "...what constitutes too big" !!! I too compiled smaller kernels than the ones that come with SuSE, and I was getting the "... too big message". Interesting.
Hubert Mantel recently said that the vmlinuz image had to fit under the old dos 640k limit, I guess due to bios limitations? I am completely baffled by all the posts I see about the "too big error". Is everyone including alot of uneeded functionality into their kernels? I have a nice scsi kernel, with ppp built in, and it is only around 460k, and that is just using zImage. It is a little over 1 meg uncompressed. If people need to use bzImage, the kernels must be up around 2 megs when uncompressed. People must be adding useless stuff to the kernel not knowing what it's for. Or else they are trying to copy the uncompressed vmlinux kernel to root, then trying to run lilo on it. What's going on? I feel like I'm missing something with all this talk of make bzImage. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Mon, 23 Nov 1998, zentara wrote:
I am completely baffled by all the posts I see about the "too big error". Is everyone including alot of uneeded functionality into their kernels? I have a nice scsi kernel, with ppp built in, and it is only around 460k, and that is just using zImage. It is a little over 1 meg uncompressed.
If people need to use bzImage, the kernels must be up around 2 megs when uncompressed. People must be adding useless stuff to the kernel not knowing what it's for.
Or else they are trying to copy the uncompressed vmlinux kernel to root, then trying to run lilo on it.
What's going on? I feel like I'm missing something with all this talk of make bzImage.
You probably have nothing on your system except scsi and modem ;-) For example: I have 2 different ethernet cards, modems, scsi, ide, printer, sound, smb, ip masquerading. The 2.0.35 kernel size is 484562. (I heard some people here have 350k kernels using everything as modules). If you take the same configuration and compile 2.1.12X you will get 680k kernel. Maybe this is why everybody gets huge kernels? - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Mon, 23 Nov 1998, alexm wrote:
The 2.0.35 kernel size is 484562. (I heard some people here have 350k kernels using everything as modules).
I had a look at my kernels: they are 2.0.35 size 321516 2.0.34 size 324721 (on different machines) and I didn't "use everything as modules", only the things I know I don't always need Eugenia - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
I think it's a combination of unnecessary things included into the kernel and people aren't using modules. I know that with SCSI, PPP, firewall, etc are compiled into my kernel and it's a bit on the huge side. Luckily I only load the modules as needed. :) Loadable module support, ANOTHER reason linux beats windows!
I am completely baffled by all the posts I see about the "too big error". Is everyone including alot of uneeded functionality into their kernels? I have a nice scsi kernel, with ppp built in, and it is only around 460k, and that is just using zImage. It is a little over 1 meg uncompressed.
If people need to use bzImage, the kernels must be up around 2 megs when uncompressed. People must be adding useless stuff to the kernel not knowing what it's for.
Or else they are trying to copy the uncompressed vmlinux kernel to root, then trying to run lilo on it.
What's going on? I feel like I'm missing something with all this talk of make bzImage. - 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
participants (8)
-
alexm＠htr-60.tx.symbio.net -
carneys＠earthlink.net -
eugenia＠stud.pg.infn.it -
inemes＠transylvania.com.au -
mantel＠suse.de -
Vorlon＠pdn.net -
wizard01＠impop.bellatlantic.net -
zentara＠mindspring.com