Messages in this thread Patch in this message |  | | Date | Fri, 27 Sep 1996 01:46:50 +0200 | From | Hans Lermen <> | Subject | Re: bzImage vs zImage |
| |
On Thu, 26 Sep 1996, George Bonser wrote:
> In article <3248FF85.3E1CD0E8@rad.net.id>, > Agus Budy Wuysang <fswmis@rad.net.id> writes: > > > > What is the difference between these 2 kernel images? > > On my system .... zImage works, bzImage does not. ^^^^^^^^^^^^^^^^
On Linux 2.0.x bzImage _works_, it just needs one of the newer loaders (LILO >18, LOADLIN-1.6, ...) On a few couple of (odd) mainboards there have been seen problems with INT15 (used to access above 1Meg), when the 2nd level cache is enabled. ( don't ask _me_ why, ask the board manufacturer ) This problem does _not_ exist, when loading bzImages via Loadlin.
On Linux 2.1.x (pre-patch-2.1.0-#4.gz) bzImage is broken, but the below patch (already sent to Linus) fixes this problem.
---------------------------------------------------------------------- --- linux-pre-2.1.0-2/arch/i386/Makefile Tue Sep 24 23:58:34 1996 +++ linux/arch/i386/Makefile Wed Sep 25 20:47:04 1996 @@ -19,8 +19,10 @@ # # ZIMAGE_OFFSET is the load offset of the compression loader +# BZIMAGE_OFFSET is the load offset of the high loaded compression loader # ZIMAGE_OFFSET=0x1000 +BZIMAGE_OFFSET=0x100000 # # IMAGE_OFFSET is the load offset of the _real_ kernel, soon @@ -40,7 +42,7 @@ ZLDFLAGS=-e startup_32 LDFLAGS=-e stext ZLINKFLAGS =-Ttext $(ZIMAGE_OFFSET) $(ZLDFLAGS) -BZLINKFLAGS =-Ttext $(IMAGE_OFFSET) $(ZLDFLAGS) +BZLINKFLAGS =-Ttext $(BZIMAGE_OFFSET) $(ZLDFLAGS) LINKFLAGS =-Ttext $(IMAGE_OFFSET) $(LDFLAGS) CFLAGS := $(CFLAGS) -pipe ----------------------------------------------------------------------
Hans <lermen@fgan.de>
|  |