Bug 139329 - Intel i815 X server freezes on first boot after install
Intel i815 X server freezes on first boot after install
Status: CLOSED DUPLICATE of bug 132267
Product: Fedora
Classification: Fedora
Component: xorg-x11 (Show other bugs)
i686 Linux
medium Severity high
: ---
: ---
Assigned To: X/OpenGL Maintenance List
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2004-11-15 04:01 EST by Barry Kelly
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:07:01 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Barry Kelly 2004-11-15 04:01:36 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5)
Gecko/20041107 Firefox/1.0

Description of problem:
When the X server which supports the Intel i815 integrated graphics
chip is running on a machine with said chip in 24-bit 1024x768 with
acceleration enabled (i.e. Option NoAccel On is not specified),
scrolling (or any bit-block transfer of video memory) appears to cause
the graphics card driver to crash.

I ssh'd in from another machine and edited /etc/X11/xorg.conf to
enable the NoAccel option for the X server, and rebooted, and things
worked (albiet slowly).

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

How reproducible:

Steps to Reproduce:
1. Install FC3 on machine with Intel i815 integrated graphics
2. Choose to install "everything".
3. Freezes after first reboot, usually after doing a scroll of some
part of the screen, typically on the license accept page.

Actual Results:  The X server crashed.

Expected Results:  I expected to be able to read the license.

Additional info:
Comment 1 Mike A. Harris 2004-11-17 22:37:46 EST

*** This bug has been marked as a duplicate of 132267 ***
Comment 2 Red Hat Bugzilla 2006-02-21 14:07:01 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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