Bug 124096

Summary: Installer crashed on the first step
Product: [Fedora] Fedora Reporter: david <d.avenante>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 2   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:03:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description david 2004-05-24 02:25:07 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031114

Description of problem:
I 'use the last fedora core 2 CD1 for installation.
The CD is md5sum verified

The installer propose me some options :
F1 ... F2.... etc
I press enter for normal installation

i' ve two lines
vmlinuz ...........................
initrd......................

The screen pass blank and the system reboot

I' ve try to use the option
linux nofb ans linux texte it's the same scenario

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


How reproducible:
Always

Steps to Reproduce:
1.Insert Fedora core 2 CD1
2.Start th Computer
3.The System boot on the CD
4.I select on installation option (linux, linux nofb or linux text)
6.I've two lines on screen
7.the system crash with a blank screen and reboot    

Actual Results:  The system rboot

Additional info:

Ok i use a PC with :
Intel P4 3 GHrz:
Ram 1 Go (2x512)
MotherBoard : Intel P4P800 Deluxe
Video card : ATI radeon 8600Pro 128 Mo

The system is ok if i install Fedora core 1
Is it a problem with the new X11 ?

Thanks for your help

Comment 1 Arjan van de Ven 2004-05-24 06:51:48 UTC

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

Comment 2 Red Hat Bugzilla 2006-02-21 19:03:38 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.