Bug 138948

Summary: xserver won't boot using i810 driver
Product: [Fedora] Fedora Reporter: Manfred Georg <mg2>
Component: xorg-x11Assignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: high Docs Contact:
Priority: medium    
Version: rawhide   
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:06:57 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:
Attachments:
Description Flags
X server output none

Description Manfred Georg 2004-11-12 01:42:51 UTC 
X.org server does not start up after install of Fedora core 3.
The same machine worked well under Fedora Core 2 (even with
kernel 2.6.9).
Computer: Sony Vaio laptop (PCG-SRX87)
Video card lines from lspci:

00:00.0 Host bridge: Intel Corp. 82815 815 Chipset Host Bridge and
Memory Controller Hub (rev 11)
00:02.0 VGA compatible controller: Intel Corp. 82815 CGC [Chipset
Graphics Controller] (rev 11)

Xserver output is attached (if I can figure out how to do that).

This is probably the same problem as bug 138055 however it is not
restricted to the install process.  Sorry if I'm breaking procedure
creating a new bug.

Manfred
Comment 1 Manfred Georg 2004-11-12 01:44:24 UTC 
Created attachment 106549 [details]
X server output
Comment 2 Mike A. Harris 2004-11-12 17:32:54 UTC 

*** This bug has been marked as a duplicate of 132267 ***
Comment 3 Mike A. Harris 2004-11-12 17:37:41 UTC 
*** This bug has been marked as a duplicate of 132267 ***

*** This bug has been marked as a duplicate of 132267 ***
Comment 4 Mike A. Harris 2004-11-12 17:40:19 UTC 
Hmm, the new bugzilla seems to be a bit buggy...  We had a mid-air
collision and it marked this as a dupe 3 times for some reason.
Thought I'd mention this in case it caused any confusion.
Comment 5 Red Hat Bugzilla 2006-02-21 19:06:57 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.