Bug 692567 - FC15 Alpha
Summary: FC15 Alpha
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-31 15:24 UTC by mikemc-redhat
Modified: 2011-04-04 00:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-04 00:13:54 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description mikemc-redhat 2011-03-31 15:24:20 UTC 
Description of problem:

The display driver in the .38 kernel for AMD zacate chips (http://en.wikipedia.org/wiki/AMD_Fusion#.22Zacate.22_.2840nm.29) in FC15 Alpha is unusable.  The screen flickers white lines.  

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

http://mirrors.kernel.org/fedora/releases/test/15-Alpha/Fedora/x86_64/os/Packages/kernel-2.6.38-0.rc5.git1.1.fc15.x86_64.rpm


How reproducible:

Every time

Steps to Reproduce:
1. Boot FC15 alpha live cd
2. 
3.
  
Actual results:

Flickering unusable screen

Expected results:

Working screen

Additional info:

Loading the basic video driver option works.  Looks like upstream may have a fix for this: http://phoronix.com/forums/showthread.php?36649-Open-Source-AMD-Fusion-E-350-Support-Takes-A-Dive/page2  May be easy to incorporate for FC15.
Comment 1 Dave Airlie 2011-03-31 23:34:10 UTC 
can you retry with a later fc15 kernel?
Comment 2 mikemc-redhat 2011-04-01 00:11:10 UTC 
That would require installing fc15 i think.  Is there a way to load another kernel off a live cd?  Are there nightly live cd builds somewhere?
Comment 3 Chuck Ebbert 2011-04-03 18:57:39 UTC 
> Are there nightly live cd builds somewhere?

http://alt.fedoraproject.org/pub/alt/nightly-composes/current.html
Comment 4 Chuck Ebbert 2011-04-04 00:13:54 UTC 
That patch was merged before 2.6.38 release.
Note You need to log in before you can comment on or make changes to this bug.