Bug 220038

Summary: Good: XORG is unable to initialize graphics for i810...on Intel 82845GL graphics chipset
Product: [Fedora] Fedora Reporter: Manish Singh <manish.singh123>
Component: xorg-x11-drv-i810Assignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 6   
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-12-18 20:54: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 Manish Singh 2006-12-18 16:28:18 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; EmbeddedWB 14,52 from: http://www.bsalsa.com/ EmbeddedWB 14.52; .NET CLR 2.0.50727; InfoPath.2)

Description of problem:
After installing FC6 i couldnt get the GUI. Whenever FC6 starts it detects the graphic controller but fails to intialize the screen...what i get is a blank screen and after a few moments some garbage text is displayed and some characters are flickering in it. Sometimes it is completly blank. Anaconda runs fine and FC5 works perfectly. in FC6 i have to boot the system on runlevel 3 to get the console window on noraml(run level 5) system GUI is locked out. no display (GUI and CLI)

Version-Release number of selected component (if applicable):
kernel-2.6.18-1.2798.fc6xen

How reproducible:
Always


Steps to Reproduce:
1. Install FC6 on a Intel 82845GL graphics chipset using P4 2.4Ghz, 640 MB ram and ASRock motherboard
2. Start the system
3. Probelm is there

Actual Results:
No display of GUI or CLI in level 5

Expected Results:
Nice FC6 GUI

Additional info:
p4 2.4 Ghz
640 MB ram 8 MB shared
Intel 82845GL graphics chipset
ASRock Motherboard p4i45GL
Comment 1 Adam Jackson 2006-12-18 20:54:38 UTC 

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