Bug 206462 - corrupt display on ATI ES1000 chipset
Summary: corrupt display on ATI ES1000 chipset
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: rawhide
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-09-14 14:51 UTC by Andy Burns
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version: f7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-07-23 23:05:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
/tmp/ramfs/X.log from anaconda (54.18 KB, text/plain)
2006-09-16 11:50 UTC, Andy Burns
no flags Details
/tmp/ramfs/anaconda.log (13.12 KB, text/plain)
2006-09-16 11:50 UTC, Andy Burns
no flags Details
xorg.0.log from a normal boot, not from during anaconda (55.25 KB, text/plain)
2006-09-27 09:55 UTC, Andy Burns
no flags Details

Description Andy Burns 2006-09-14 14:51:10 UTC
Description of problem:

Installing FC6T3 on an intel SR2500 chassis, anaconda starts probes which finds
an ATI ES1000 chipset, Xorg starts, and is "obviously" drawing correct stuff
into the framebuffer, however what is being displayed (on a 1024x768 CRT) is
badly garbled, best way to describe it is that like a a rapid version of the
wayne's world "dream sequence" wiggly video transition, it makes the mouse
pointer look like a rotating lissajous figure on an oscilloscope, the edges of
the screen are "frilly"

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

How reproducible:
100%

Steps to Reproduce:
1. boot from DVD, run anaconda in GUI mode

Comment 1 Adam Jackson 2006-09-15 20:39:18 UTC
rpm -q xorg-x11-drv-ati

Also please attach your Xorg.0.log.

Comment 2 Andy Burns 2006-09-16 11:49:32 UTC
As this occurs during initial anaconda setup while booted from DVD, xorg isn't
technically installed at this point, so nothing sensible from rpm -q, however
the RPM included on the FC6T3 DVD is xorg-x11-drv-ati-6.6.2-1.fc6.x86_64.rpm, so
presumably that is the same version included within the stage2.img?

Unfortunately anaconda also fails to install an initrd so the machine isn't
bootable post-install, therefore no Xorg.0.log available, so instead I've booted
from DVD, paused during GUI installation, mounted a memory stick, and copied
/tmp/ramfs/X.log and /tmp/ramfs/anaconda.log to memory stick, I will attach
these files ...


Comment 3 Andy Burns 2006-09-16 11:50:31 UTC
Created attachment 136421 [details]
/tmp/ramfs/X.log from anaconda

Comment 4 Andy Burns 2006-09-16 11:50:54 UTC
Created attachment 136422 [details]
/tmp/ramfs/anaconda.log

Comment 5 Andy Burns 2006-09-18 07:32:00 UTC
Despite all the problems of taking a still photo from a CRT to describe a moving
problem, I've had a go, see http://adslpipe.co.uk/pics/es1000corruption.jpg

The picture as a whole isn't rolling vertically, but imagine that the sawtooth
distortion is rapidly shifting vertically, but out of sync so that it is like a
scrambling, rather than a rolling motion, that's about what I see ...

Ignore the moiré fringing, that's just an artifact of the photo.

Comment 6 Andy Burns 2006-09-27 09:55:00 UTC
Created attachment 137205 [details]
xorg.0.log from a normal boot, not from during anaconda

Just a quick update, I worked around the issue that was leaving this machine
unbootable after install, when firstboot ran, it had a good Xorg display, then
when Xorg/gdm started for real it was back to the "frilly" display, I've set
the machine to use VESA driver for now as it will be accessed remotely in this
case.

Comment 7 Adam Jackson 2006-10-03 15:53:01 UTC
I think this is a repeat of a PLL math bug we've hit before:

(II) RADEON(0): PLL parameters: rf=2700 rd=60 min=12000 max=46909632818162;
xclk=16600

That max value seems unlikely.

Comment 9 Andy Burns 2007-03-18 20:15:35 UTC
Just to refresh this bug, it still occurs during install with the F7t2 DVD,
however the Xorg that actually gets installed starts up properly.



Comment 10 Andy Burns 2007-07-23 23:05:48 UTC
This now works in F7 release.


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