Bug 838823 - AMD 6310 - Screen corruption from boot to desktop
Summary: AMD 6310 - Screen corruption from boot to desktop
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 17
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-10 08:56 UTC by biodark
Modified: 2013-03-14 00:48 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-03-14 00:48:24 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
example of corruption (39.48 KB, image/jpeg)
2012-07-10 08:56 UTC, biodark 		no flags Details
messages log (114.09 KB, text/plain)
2012-07-11 01:35 UTC, biodark 		no flags Details
xorg.0 log (158.48 KB, text/plain)
2012-07-11 01:35 UTC, biodark 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Launchpad 930463 0 None None None 2012-07-10 08:56:49 UTC

Description biodark 2012-07-10 08:56:48 UTC 
Created attachment 597249 [details]
example of corruption

Description of problem:
Screen corruption occurs during Plymouth and after gnome shell loads.
There is one way to reproduce it reliably when the DE is loaded is to go to system settings > screens and it flickers every time you hit the button detect screens.

Version-Release number of selected component (if applicable):
Latest 3.4 kernel and all fedora updates to this date.

How reproducible:
Install fedora on a foxconn barebone nT-A3550

Steps to Reproduce:
Install fedora on a foxconn barebone nT-A3550
  
Actual results:
Flickering.

Expected results:
No flickering.

Additional info:
I filled the same bug on launchpad a while ago:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/930463
Comment 1 biodark 2012-07-11 01:35:06 UTC 
Created attachment 597439 [details]
messages log
Comment 2 biodark 2012-07-11 01:35:54 UTC 
Created attachment 597440 [details]
xorg.0 log
Note You need to log in before you can comment on or make changes to this bug.