Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 225132 - Intel 915GV not working correctly with i810 driver
Summary: Intel 915GV not working correctly with i810 driver
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: xorg-x11
Version: 4.4
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2007-01-29 09:21 UTC by Jos Vos
Modified: 2007-11-17 01:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-01-31 17:26:08 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Jos Vos 2007-01-29 09:21:50 UTC
Description of problem:

A system with an 1024x768 LCD screen and an Intel 915GV chipset is not working
correctly in RHEL4 U4 with the "i810" driver (but it works correctly with RHEL5
beta2!).  The display is shifted about 1/2 inch downwards and the topmost 1/2
inch of the screen is filled with more or less random pixels.

The "vesa" driver works ok, but then DPMS is not working anymore (a must for
this system), so this is no option.

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

Any chance the i810 driver will be upgraded in an upcoming RHEL4 update?  Or is
there anything I can do to solve the problem via settings in xorg.conf?

Comment 1 Jos Vos 2007-01-29 10:18:16 UTC
I solved my own problem by setting the "NoAccel" option to "yes": now the screen
looks ok with the "i810" driver, including DPMS.

Should the bug be closed now or better leave it open as a trigger for better
915GV  support?

Comment 2 Matěj Cepl 2007-01-31 17:26:08 UTC
I think it should be closed, if you want to make drivers better, file a bug
upstream (

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