Bug 1052749 - Booting with radeon module broken
Summary: Booting with radeon module broken
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 20
Hardware: x86_64
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: 2014-01-14 01:01 UTC by Honza Brázdil
Modified: 2015-06-29 14:26 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 14:26:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
/var/log/messages (174.11 KB, text/plain)
2014-01-21 21:34 UTC, Honza Brázdil
no flags Details
/var/log/Xorg.0.log (50.87 KB, text/plain)
2014-01-21 21:35 UTC, Honza Brázdil
no flags Details

Description Honza Brázdil 2014-01-14 01:01:39 UTC
Description of problem:
I had Fedora 19 with fglrx. I unistalled fglrx and upgraded to Fedora 20 using fedup. Everything OK.
I then found out that i forgoted to remove from /etc/modprobe.d/blacklist.conf: 
blacklist radeon
blacklist radeonhd

When I removed them and rebooted, I had only black/(8-bit?)colour blinking stripes on my screen.

I thought that I broke something with the fglrx so I inserted Fedora 20 DVD and wanted to do clean install. But when the DVD booted there were the stripes again.

I have ATI Radeon HD7870

Version-Release number of selected component (if applicable):
3.12.7-300.fc20.x86_64
3.12.6-300.fc20.x86_64

How reproducible:
Every time i remove radeon and radeonhd from blacklist and reboot.


Steps to Reproduce:
1. Remove radeon and radeonhd from blacklist
2. Reboot


Actual results:
There is several seconds of black screen and then black/color blinking stripes on the screen.


Expected results:
It should start Gnome and run smoothly.

Comment 1 Honza Brázdil 2014-01-15 18:38:58 UTC
$ rpm -qa xorg-x11-drv-ati
xorg-x11-drv-ati-7.2.0-3.20131101git3b38701.fc20.x86_64

Comment 2 Honza Brázdil 2014-01-19 19:40:33 UTC
Is there anything I can do to help resolve this bug?

Comment 3 Honza Brázdil 2014-01-21 21:34:15 UTC
Created attachment 853463 [details]
/var/log/messages

Comment 4 Honza Brázdil 2014-01-21 21:35:32 UTC
Created attachment 853464 [details]
/var/log/Xorg.0.log

Comment 5 Honza Brázdil 2014-01-24 14:37:31 UTC
This is how it looks when I have the module enabled. https://plus.google.com/112721714533612030540/posts/CgdVaCv7ghz

Can I do anything to speed it up? Report a bug somewhere else?

Comment 6 Fedora End Of Life 2015-05-29 10:29:34 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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 7 Fedora End Of Life 2015-06-29 14:26:23 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.