Bug 206876 – grub will not boot on intel 965 platform

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 206876 - grub will not boot on intel 965 platform

Summary:	grub will not boot on intel 965 platform

Status:	CLOSED DUPLICATE of bug 116311

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	grub (Show other bugs)
Sub Component:
Version:	6
Hardware:	x86_64 Linux

Priority	medium Severity urgent
Target Milestone:	---
Target Release:	---
Assigned To:	Peter Jones
QA Contact:	Mike McLean
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2006-09-17 12:24 EDT by Avi Kivity
Modified:	2007-11-30 17:11 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-09-27 18:00:32 EDT
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 Avi Kivity 2006-09-17 12:24:22 EDT

Description of problem:

I installed rawhide (equivalent to FC6T3 at this time) on a Core 2 Duo machine 
based on the 965 chipset.  The machine has 4GB of RAM.

Grub will not boot the newly installed system, saying:

Error 28: Selected item cannot fit into memory

Removing the initrd prevents the error, but of course the kernel will not 
boot. The expanded initrd is about 4MB (which should fit in 4GB).

Eventually I installed lilo as a workaround.

Version-Release number of selected component (if applicable):
0.97-11

How reproducible:
Always

Steps to Reproduce:
1. Install rawhide
2. Boot
  
Actual results:
Won't boot

Expected results:
Boot

Comment 1 Peter Jones 2006-09-27 18:00:32 EDT


*** This bug has been marked as a duplicate of 116311 ***

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