Bug 138599 - Grub install fails on E-Machines M6811 Laptop
Grub install fails on E-Machines M6811 Laptop
Status: CLOSED CANTFIX
Product: Fedora
Classification: Fedora
Component: grub (Show other bugs)
3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Peter Jones
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-11-09 23:54 EST by Ugo Enyioha
Modified: 2007-11-30 17:10 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-11-18 16:30:25 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)

  None (edit)
Description Ugo Enyioha 2004-11-09 23:54:04 EST
Description of problem:
A typical installation of FC3 on eMachines M6811 Laptop results in a
non bootable system. Computer continously reboots.

Version-Release number of selected component (if applicable):
CNU Grub Version 0.95

How reproducible:
Reinstalled FC3 twice and noticed similar results.

Steps to Reproduce:
1. Buy an M6811 Laptop
2. Install FC3
3. Watch the reboot frenzy!
  
Actual results:
Laptop continously reboots

Expected results:
Linux boots without issue.

Additional info:
I reverted to lilo without issues.
Comment 1 Jeremy Katz 2004-11-11 13:33:12 EST
The eMachines laptops have notoriously bad bioses.  Can you see if
there's an updated BIOS available and try again.
Comment 2 Matthew Miller 2007-04-06 11:13:40 EDT
Fedora Core 3 and Fedora Core 4 are no longer supported. If you could retest
this issue on a current release or on the latest development / test version, we
would appreciate that. Otherwise, this bug will be marked as CANTFIX one month
from now. Thanks for your help and for your patience.
Comment 3 Peter van Egdom 2007-11-18 16:30:25 EST
The information we've requested above is required in order to review this
problem report further and diagnose/fix the issue if it is still present. Since
there haven't been any updates to the report in quite a long time now after
we've requested additional information, we're assuming the problem is either no
longer present in our current OS release, or that there is no longer any
interest in tracking the problem.

Setting status to "CANTFIX", however if you still experience this problem after
updating to our latest Fedora release and are still interested in Red Hat
tracking the issue, and assisting in troubleshooting the problem, please feel
free to provide the information requested above, and reopen the report.

Thank you in advance.

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