Bug 6747 – LILO 0.21 reports kernel too big where 0.20 does not.

Bug 6747 - LILO 0.21 reports kernel too big where 0.20 does not.

Summary:	LILO 0.21 reports kernel too big where 0.20 does not.

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	lilo (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Michael K. Johnson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-11-05 05:14 EST by John Eckerdal
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-02-05 01:37:47 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description John Eckerdal 1999-11-05 05:14:12 EST

LILO as shipped with RH 6.1 (and possibly 6.0) reports that
a newly built kernel is too big. This does however not
happen if you use the version of lilo that came with RH 5.2.

I sort of found this out while building a monolithic kernel
on an updated RH6.1 box with LILO 0.21. The kernel was
about 480 kB. After a bit of thinking I downgraded to LILO
0.20 and then it worked again.

Comment 1 Bill Nottingham 1999-11-05 10:49:59 EST

Use 'make bzImage' instead of 'make zImage'. That should
solve the problem.

Comment 2 John Eckerdal 1999-11-05 11:16:59 EST

Yes, make bzImage might work (although if I recall the events
correctly it did not allways work). The thing that bothers me is that
LILO 0.20 works where 0.21 does not.

Comment 3 Cristian Gafton 2000-01-04 17:25:59 EST

Assigned to dledford

Comment 4 Bill Nottingham 2000-02-05 01:37:59 EST

This is because lilo-0.21 loads the kernel slightly differently, because
it works around some problems with some newer/strange BIOSes ; hence
it has a little less memory for zImage use.

Note You need to log in before you can comment on or make changes to this bug.