Public SourceMage Discussion List

[Seth Woolley <seth AT tautology.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I guess we have an answer to the question of "why compress the kernel?"

Is it just me or is a limit on kernel size kind of dumb... anybody know
why lilo does that?

Good luck on finding the culprit.

On Fri, 12 Sep 2003, Duane Malcolm wrote:

> I made a vmlinux kernel but lilo says it too large ("Fatal: Kernel
> /boot/vmlinux is too big"). I am nw compiling the kernel using a 2.4.18
> kernel config file from a person who has a Evo n160. I'll see if I'm
> missing something in the kernel.
>
> I think it's hardware or how lilo talks to the hardware because the same
> image doesn't have a problem on other machines.
>
> If this doesn't work and nothing else comes to mind, I'll give up and
> hang out for a new laptop.
>
> Duane.
>
> Seth Woolley wrote:
> > from /usr/src/linux/README:
> >
> >  - Do a "make bzImage" to create a compressed kernel image.  If you want
> >    to make a boot disk (without root filesystem or LILO), insert a floppy
> >    in your A: drive, and do a "make bzdisk".  It is also possible to do
> >    "make install" if you have lilo installed to suit the kernel makefiles,
> >    but you may want to check your particular lilo setup first.
> >
> >    To do the actual install you have to be root, but none of the normal
> >    build should require that. Don't take the name of root in vain.
> >
> >  - In the unlikely event that your system cannot boot bzImage kernels you
> >    can still compile your kernel as zImage. However, since zImage support
> >    will be removed at some point in the future in favor of bzImage we
> >    encourage people having problems with booting bzImage kernels to report
> >    these, with detailed hardware configuration information, to the
> >    linux-kernel mailing list and to H. Peter Anvin <hpa+linux AT zytor.com>.
> >
> > make vmlinux for uncompressed
> > make  zImage for gzip
> > make bzImage for bzip2
> >
> > copy it into /boot from eiher . or ./arch/${ARCH}/boot/, setup lilo, away
> > you go.
> >
> > vmlinux should be in /usr/src/linux/vmlinux even with our own linux spell
> > that does bzipping by default for i386.
> >
> > Just cast it, and cp /usr/src/linux/vmlinux /boot and then point lilo to
> > it and run lilo.  See if that makes bootup a lot faster?
> >
> > Seth
> >
> > On Wed, 10 Sep 2003, Andrew wrote:
> >
> >
> >>basically if your bios is broken you may not be able to load a compressed
> >>kernel, or at least thats what i hear is the reason for leaving that
> >>stuff in the kernel build process.
> >>
> >>On Thu, Sep 11, 2003 at 01:21:40AM -0400, Jeremy A. Kolb wrote:
> >>
> >>>I've never known anyone to not compress their kernel.  What's the reason
> >>>for not compressing it? Other than a slightly slower bootup (a couple
> >>>seconds at the most) what are the advantages/disadvantages?
> >>>
> >>>Jeremy
> >>>
> >>>On Wed, 10 Sep 2003, Seth Woolley wrote:
> >>>
> >>>
> >>>>-----BEGIN PGP SIGNED MESSAGE-----
> >>>>Hash: SHA1
> >>>>
> >>>>Maybe our linux spell should allow you to select compression options.
> >>>>
> >>>>Seth
> >>>>
> >>>>On Wed, 10 Sep 2003, Dufflebunk wrote:
> >>>>
> >>>>
> >>>>>It's a long shot, but are you sure the PII image was compressed? Might
> >>>>>it have been an uncompressed image? That would make the boot much
> >>>>>faster...
> >>>>>
> >>>>>On Wed, 2003-09-10 at 17:37, Duane Malcolm wrote:
> >>>>>
> >>>>>>I installed Mandrake 8.2 using an XFS and ext3 partition and there was
> >>>>>>no difference. I do know that I put an image from my maching on a 
> >>>>>>200MHz
> >>>>>>PII and it uncompresses the kernel image in less than a second. This
> >>>>>>pissed me off. I might look into the bios. I don't understand how the
> >>>>>>acpi can kick in from the kernel if you haven't uncompressed the 
> >>>>>>kernel.
> >>>>>>
> >>>>>>Anyway, I'll keep going and tell you when I give up and accept my 
> >>>>>>fate.
> >>>>>>
> >>>>>>Duane.
> >>>>>>
> >>>>>>Duane Malcolm wrote:
> >>>>>> > Seth Woolley wrote:
> >>>>>> >
> >>>>>> >> Something tells me that's way too long... is this a laptop?  
> >>>>>> >> Could be
> >>>>>> >> some
> >>>>>> >> acpi buggery and on bootup it starts in a slow state until acpi
> >>>>>>kicks in.
> >>>>>> >> How are non-smgl partitions behaving, or is it just our kernels?
> >>>>>> >
> >>>>>> > It is a laptop. I was considering quickly putting mandrake on to 
> >>>>>> > test if
> >>>>>> > it's my smgl or not. I'll reply on this soon.
> >>>>>> >
> >>>>>> >>
> >>>>>> >> On Wed, 10 Sep 2003, Duane Malcolm wrote:
> >>>>>> >>
> >>>>>> >>
> >>>>>> >>> Hi,
> >>>>>> >>>
> >>>>>> >>> This is a bit different but it is starting to really annoy me.
> >>>>>> >>>
> >>>>>> >>> I have an Compaq Evo N160, PIII 1.2 Ghz, 30G HD and 750 MB RAM. 
> >>>>>> >>> When I
> >>>>>> >>> boot up, it gets into lilo fine and when I choose one of my 
> >>>>>> >>> sourcemage
> >>>>>> >>> partition it takes 15-20 seconds to uncompress the kernel image. 
> >>>>>> >>> The
> >>>>>> >>> rest of the boot up goes fine. I have searched the web and tried 
> >>>>>> >>> a
> >>>>>> >>> number of things but haven't been lucky. Does anyone have an 
> >>>>>> >>> idea?
> >>>>>> >>>
> >>>>>> >>> Cheers, Duane.
> >>>>>> >>
> >>>>>> >>
> >>>>>> >>
> >>>>>> >> --
> >>>>>> >> Seth Alan Woolley <seth at tautology.org>, SPAM/UCE is 
> >>>>>> >> unauthorized
> >>>>>> >> Key id 7BEACC7D = 2978 0BD1 BA48 B671 C1EB 93F7 EDF4 3CDF 7BEA 
> >>>>>> >> CC7D
> >>>>>> >> Full Key at seth.tautology.org and pgp.mit.edu. info: 
> >>>>>> >> www.gnupg.org
> >>>>>> >
> >>>>>> >
> >>>>>> > _______________________________________________
> >>>>>> > SM-Discuss mailing list
> >>>>>> > SM-Discuss AT lists.ibiblio.org
> >>>>>> > http://lists.ibiblio.org/mailman/listinfo/sm-discuss
> >>>>>> >
> >>>>>> >
> >>>>>> > _______________________________________________
> >>>>>> > SM-Discuss mailing list
> >>>>>> > SM-Discuss AT lists.ibiblio.org
> >>>>>> > http://lists.ibiblio.org/mailman/listinfo/sm-discuss
> >>>>>>
> >>>>>>
> >>>>>>_______________________________________________
> >>>>>>SM-Discuss mailing list
> >>>>>>SM-Discuss AT lists.ibiblio.org
> >>>>>>http://lists.ibiblio.org/mailman/listinfo/sm-discuss
> >>>>>
> >>>>>_______________________________________________
> >>>>>SM-Discuss mailing list
> >>>>>SM-Discuss AT lists.ibiblio.org
> >>>>>http://lists.ibiblio.org/mailman/listinfo/sm-discuss
> >>>>>
> >>>>
> >>>>- --
> >>>>Seth Alan Woolley <seth at tautology.org>, SPAM/UCE is unauthorized
> >>>>Key id 7BEACC7D = 2978 0BD1 BA48 B671 C1EB 93F7 EDF4 3CDF 7BEA CC7D
> >>>>Full Key at seth.tautology.org and pgp.mit.edu. info: www.gnupg.org
> >>>>
>
>
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss
>
>
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss
>

- --
Seth Alan Woolley <seth at tautology.org>, SPAM/UCE is unauthorized
Key id 7BEACC7D = 2978 0BD1 BA48 B671 C1EB 93F7 EDF4 3CDF 7BEA CC7D
Full Key at seth.tautology.org and pgp.mit.edu. info: www.gnupg.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)

iD8DBQE/YQPL7fQ833vqzH0RAqlbAKDCQ7C1KRxqyF7k0ErwacN0XEyj0QCeKMMo
plqCn7AyCWyJmv3AKJsXiIA=
=hq69
-----END PGP SIGNATURE-----