On Wed, Jun 10, 1998 at 09:17:20PM -0600, Jason Gunthorpe wrote: > When you boot the kernel it copies the Image from the disk to 0x1000 > (about 64k). If the Image is beyond 600k then you have a problem because > it suddenly will not all fit in low memory. > > A bzImage is more sinister. After it loads a few block in it makes some > bios calls to copy the blocks up to 1 meg where the 3rd stage boot loader > will run. After that it uncompresses the kernel to some location then > copies it to it's proper placement at 1M. a zImage simply uncompresses the > kernel to 1M. > > In theory, on a notebook the int calls are glitchy and crash the system. > > If your kernel is > 600k you MUST use a bzImage and you MUST load it into
So is there any other advantage? 600k is pretty big for a default kernel, especially since we are making heavy use of modules. My custom 2.0.34 is 300k odd, although obviously the Debian one needs a bunch of SCSI drivers. If we are < 600k, why use it when it is problematic? I've no idea why my desktop hates it. Everything else about the machine is perfect, and it's a custom-built clone rather than some IBM or Compaq box, the sought with weird BIOSen. Hamish -- Hamish Moffatt, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5 CCs of replies from mailing lists are welcome. http://hamish.home.ml.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
