Bug 199879 - screen garbled
Summary: screen garbled
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-i810
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-07-23 21:21 UTC by David Juran
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: 2006-08-10 08:09:54 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Xorg log file (47.43 KB, text/plain)
2006-07-23 21:21 UTC, David Juran 		no flags Details
lspci -vvv (18.97 KB, text/plain)
2006-07-23 21:22 UTC, David Juran 		no flags Details
View All

Description David Juran 2006-07-23 21:21:15 UTC 
Description of problem:
On my Dell Latitude D820, using the i810 driver, all I get is screen all garbled
by thin vertical bars. Running the vesa driver works perfectly fine. Logfile and
output of 'lspci -vvv' attached.



Version-Release number of selected component (if applicable):
xorg-x11-drv-i810-1.6.0-11.20060713modeset

How reproducible:
Always

Steps to Reproduce:
1. Start X using the i810 driver
2.
3.
  
Actual results:
Screen all garbled, no meaningful picture

Expected results:


Additional info:
Comment 1 David Juran 2006-07-23 21:21:15 UTC 
Created attachment 132888 [details]
Xorg log file
Comment 2 David Juran 2006-07-23 21:22:39 UTC 
Created attachment 132889 [details]
lspci -vvv
Comment 3 Jens Knutson 2006-08-02 05:40:21 UTC 
I am getting this as well on my Dell E1505 notebook with the i945GM/gma950 gfx
chip.  

The problem started after installing the first
xorg-x11-drv-i810-1.6.0-2006xxyymodeset RPM and is still present as of today's
i386 development repo.

I can also provide any extra info requested.
Comment 4 David Juran 2006-08-10 08:09:54 UTC 
Works fine again after reverting to the stable i810 driver in
xorg-x11-drv-i810-1.6.4-3.fc6 (-:
Note You need to log in before you can comment on or make changes to this bug.