Bug 167562 - Installer hangs when loading boot
Summary: Installer hangs when loading boot
Keywords:
Status: CLOSED DUPLICATE of bug 159026
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 4
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL: http://joshii.szm.sk/1.booting.JPG ;...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-09-05 16:57 UTC by Michal
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-09-05 17:05:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michal 2005-09-05 16:57:50 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)

Description of problem:
I download FC4 on DVD(late too-CDversion and late only FC4 boot disc).I booting normal, but when I press Enter for continue installation…Kernel panic. I made some photos. System goes down. That in the kernel is no support for my motherboard or processor, I m think. 
But FC3 work good(apart of up2date).

Photos:

http://joshii.szm.sk/1.booting.JPG   
http://joshii.szm.sk/2.jpg  
http://joshii.szm.sk/3.jpg 
http://joshii.szm.sk/4.system go down.jpg


Version-Release number of selected component (if applicable):
loader Fedora Core4 or kernel?

How reproducible:
Always

Steps to Reproduce:
1.Insert the DVD(or CD) in DVDrom.
2.Start Install FC4
3.System down...
  

Actual Results:  I can`t install FC4.

Expected Results:  I can install FC4

Additional info:

motherboard: 	 Intel 915GEV
processor:	 Intel Celeron D 330J (2.66Ghz, 128Kb L2 cache, 533Mhz)
HDD: 		 Maxtor SATA 80GB
RAM:		1x DDR2533,  512MB

Comment 1 Rahul Sundaram 2005-09-05 17:05:21 UTC
Thank you for the report. However this has already been filed and has a known
workaround. Check the original report for comments

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


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