Bug 869054 - R300g F17 GA & latest do full Gnome 3. F18 broken. F19 uses llvmpipe - meh (Radeon Mobile X600)
Summary: R300g F17 GA & latest do full Gnome 3. F18 broken. F19 uses llvmpipe - meh ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-22 21:35 UTC by Al Dunsmuir
Modified: 2015-02-17 14:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 14:31:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Al Dunsmuir 2012-10-22 21:35:58 UTC
Description of problem:
Fedora 16 on my Dell D810 laptop (with Radeon Mobile X600 video) used fallback mode (R300 driver). 

Starting with Fedora 17 betas (including test day) and GA, full Gnome Shell was available.   I noticed about a month ago that with latest Fedora 17 updates applied, F17 once again does not start Gnome Shell and uses fallback mode.

I waited until today to report in case was a transient change.  Nope - still broken with latest F17 updates.   Also downloaded F18 TC6 beta Live (written to DVD), and with that I still get fallback mode.  Unfortunately I was out-of-town the week of F18 Radeon test day, or would have participated then (like I did in F17).

Something has broken since F17 GA, and I would be pleased to do what I can to assist with debugging this issue - just tell me what logs are required for initial diagnosis.   Likely easiest to get F17 logs (real install).



Version-Release number of selected component (if applicable):
kernel.i686          3.6.2-5.fc17
xorg-x11-drv-ati     6.14.4-6.2-12-6-2got930760942.fc17
xorg-x11-server-Xorg 1.12.3           
gnome-shell          3.4.1

How reproducible:
100%

Steps to Reproduce:
1. Boot up to gdm
2. Log into gnome 3
3. Wait... fallback mode starts
  
Actual results:


Expected results:


Additional info:

Comment 1 Al Dunsmuir 2013-06-03 22:14:22 UTC
F17: Fully functional again with latest updates.
F18: GA was like F18 TC6 - unable to run Gnome 3 (on Gnome 3 Live Desktop).
F19: Alpha and Beta Live Desktops are fully functional.

I could try to upgrade to F18 and do all updates, but suspect I am better taking that time upgrading my servers and other desktops to F19.

I will likely bypass F18, and update F17 directly to F19 when GA comes out, provided F19 GA Live Desktop remains functional.

Comment 2 Fedora End Of Life 2013-07-04 04:35:14 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Al Dunsmuir 2013-07-05 00:24:57 UTC
Unfortunately, I did not notice that F19 Live Desktop DVD was using llvmpipe.

That became painfully obvious after replacing the finally-fully-functional-again F17 system with F19 GA. GDM (and Gnome utility used to create first user) never complete.

I am interested in assisting in getting the F19 setup working with R300g driver.  I will update the title, and release in the hope of attracting some attention from a developer willing to work with me to make this happen.

Comment 4 Fedora End Of Life 2015-01-09 17:26:20 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2015-02-17 14:31:51 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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