Bug 1068866 - radeon driver does not work after kernel update
Summary: radeon driver does not work after kernel update
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 20
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: 2014-02-22 17:18 UTC by Henderb Rodriguez
Modified: 2015-06-29 19:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 19:01:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Xorg logs when good and when bad (57.28 KB, text/plain)
2014-02-22 17:18 UTC, Henderb Rodriguez
no flags Details

Description Henderb Rodriguez 2014-02-22 17:18:42 UTC
Created attachment 866435 [details]
Xorg logs when good and when bad

Description of problem:
I have Fedora 20 running in a INTEL motherboard based PC with a Radeon HD 5450 XFX (PCIe) video card, and a working multiseat configuration, from more than six months (aprox.). I have done a lot of updates with "yum update", but my last one (yesterday) did crash the second seat (no video at all).

Trying to solve, did realize that loading the new kernel (kernel-3.13.3-201.fc20.x86_64) the seat fails, while with a previos one (kernel-3.11.10-301.fc20.x86_64) the seat works perfect.

The errors saw at /var/log/Xorg.1.log are:
"...
[    43.829] (--) RADEON(0): Chipset: "ATI Radeon HD 5450" (ChipID = 0x68f9)
[    43.934] (EE) RADEON(0): [drm] Failed to open DRM device for pci:0000:01:00.0: No such file or directory
[    43.934] (EE) RADEON(0): Kernel modesetting setup failed
[    43.934] (II) UnloadModule: "radeon"
[    43.934] (EE) Screen(s) found, but none have a usable configuration.
..."

Version-Release number of selected installed components:
kernel-3.13.3-201.fc20.x86_64
xorg-x11-drv-evdev-2.8.2-1.fc20.x86_64
xorg-x11-drv-vmware-13.0.1-2.fc20.x86_64
xorg-x11-drv-vesa-2.3.2-10.fc20.x86_64
xorg-x11-drv-modesetting-0.8.0-2.fc20.x86_64
xorg-x11-drv-openchrome-0.3.3-2.fc20.x86_64
xorg-x11-drv-nouveau-1.0.9-2.fc20.x86_64
xorg-x11-drv-fbdev-0.4.3-10.fc20.x86_64
xorg-x11-drv-vmmouse-13.0.0-6.fc20.x86_64
xorg-x11-drv-synaptics-1.7.1-6.fc20.x86_64
xorg-x11-drv-qxl-0.1.1-3.fc20.x86_64
xorg-x11-drv-intel-2.21.15-5.fc20.x86_64
xorg-x11-drv-ati-7.2.0-3.20131101git3b38701.fc20.x86_64
xorg-x11-drv-mga-1.6.2-8.fc20.x86_64
xorg-x11-drv-wacom-0.23.0-4.fc20.x86_6


How reproducible:
Always.

Steps to Reproduce:
1. Start Fedora with kernel 3.13.3-201
2. Wait to load X
3. Just one seat is working (the Internal graphics with "intel" driver)

Actual results:
Crash the second seat (the one with "radeon" driver)

Expected results:
Have the two seats working, with the radeon and intel drivers.

Additional info:

Video Cards:
[henderb@camila ~]$ lspci | egrep -i vga
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series]

Seat0 configuration file:
[henderb@camila ~]$ cat /etc/X11/xorg_seat0.conf 
Section "Device"
        Identifier  "Interna"
        Driver      "intel"
        BusID       "PCI:0:2:0"
EndSection

Section "InputClass"
    Identifier "ignore_other_seats"
    Option "Ignore" "yes"
EndSection

Section "InputClass"
    Identifier "input_default"
    MatchTag "input_default"
    Option "Ignore" "no"
EndSection
[henderb@camila ~]$ 

Seat1 configuration file:
[henderb@camila ~]$ cat /etc/X11/xorg_seat1.conf 
Section "Device"
        Identifier  "Externa"
        Driver      "radeon"
        BusID       "PCI:1:0:0"
EndSection

Section "InputClass"
    Identifier "ignore_other_seats"
    Option "Ignore" "yes"
EndSection

Section "InputClass"
    Identifier "input_seat1"
    MatchTag "input_seat1"
    Option "Ignore" "no"
EndSection
[henderb@camila ~]$ 

Inside attachment:
Xorg log when working: Xorg.1.log.good.3.11.10-301
Xorg log when fails: Xorg.1.log.bad.3.13.3-201

Comment 1 Henderb Rodriguez 2014-02-26 23:28:33 UTC
The problem still persists with the NEW kernel:

[henderb@camila ~]$ tail -20 /var/log/Xorg.1.log 
[    51.680] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
[    51.680] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[    51.680] (==) RADEON(0): Default visual is TrueColor
[    51.680] (==) RADEON(0): RGB weight 888
[    51.680] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
[    51.680] (--) RADEON(0): Chipset: "ATI Radeon HD 5450" (ChipID = 0x68f9)
[    51.784] (EE) RADEON(0): [drm] Failed to open DRM device for pci:0000:01:00.0: No such file or directory
[    51.784] (EE) RADEON(0): Kernel modesetting setup failed
[    51.784] (II) UnloadModule: "radeon"
[    51.784] (EE) Screen(s) found, but none have a usable configuration.
[    51.784] (EE) 
Fatal server error:
[    51.784] (EE) no screens found(EE) 
[    51.784] (EE) 
Please consult the Fedora Project support 
	 at http://wiki.x.org
 for help. 
[    51.784] (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information.
[    51.784] (EE) 
[    51.785] (EE) Server terminated with error (1). Closing log file.


[henderb@camila ~]$ uname -a
Linux camila.powerinside 3.13.4-200.fc20.x86_64 #1 SMP Thu Feb 20 23:00:47 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
[henderb@camila ~]$

Comment 2 Greg Edwards 2014-03-02 00:47:27 UTC
I have a similar setup, intel drives screen 0, radeon drives screens 1 and 2.  This setup has worked fine until 3.13 and above kernels.  My chipset is also:

[    27.277] (--) RADEON(1): Chipset: "ATI Radeon HD 5450" (ChipID = 0x68f9)

I was able to get it to work by booting with "radeon.runpm=0".

I think this bug should be retargeted at Component: kernel.  I saw same behavior on 3.14-rc4.

Comment 3 Garrett Mitchener 2014-03-17 15:17:07 UTC
I just saw this after upgrading to kernel-3.13.6-200.  I have a Pitcairn-based graphics card, with two monitors plugged in the display port sockets, and one plugged into the DVI socket.  The primary monitor is a different resolution from the other two.  If I turn off all but the primary monitor (display port) and boot this workstation, everything seems to be fine.  I get the above errors if I boot it with all three monitors turned on.

Comment 4 Fedora End Of Life 2015-05-29 11:01:10 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 5 Fedora End Of Life 2015-06-29 19:01:54 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.