Radeon R9 290 problem
I have an AMD Radeon R9 290 video card, and since commit https://github.com/torvalds/linux/commit/96212fe8c27b I cannot boot into the system any more with CONFIG_DRM_RADEON turned on ([m]). These are the symptoms: the screen either reports NO SIGNAL (sometimes all the LEDs, scroll lock, caps lock and num lock start to blink synchronously) - I had a lot of this while bisecting v3.12.0 to v3.13.0, or, in newer kernels, including v3.18, the image just freezes somewhere around "Waiting for uevents to be processed" and nothing more happens on the screen. In both cases I have to use the reboot button.
Here's the output of lspci | grep ATI:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aac8
Here's my kernel config:
https://bpaste.net/show/8c353c80e37e
It works in 3.12 series up to 3.12.34 (it is the last version I checked) and doesn't work in 3.13 to v3.18 (b2776bf).
Quoted 4 lines · Alex Kuznetsoff
I have an AMD Radeon R9 290 video card, and since commit https://github.com/torvalds/linux/commit/96212fe8c27b I cannot boot into the system any more with
CONFIG_DRM_RADEONturned on ([m]). These are the symptoms: the screen either reports NO SIGNAL (sometimes all the LEDs, scroll lock, caps lock and num lock start to blink synchronously) - I had a lot of this while bisecting v3.12.0 to v3.13.0, or, in newer kernels, including v3.18, the image just freezes somewhere around "Waiting for uevents to be processed" and nothing more happens on the screen. In both cases I have to use the reboot button.Here's the output of lspci | grep ATI:
Quoted 8 lines
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aac8
Here's my kernel config:
https://bpaste.net/show/8c353c80e37e
It works in 3.12 series up to 3.12.34 (it is the last version I checked) and doesn't work in 3.13 to v3.18 (b2776bf).
That commit is the first commit to enable hawaii support in the driver so prior to that, the driver was not loaded on your hardware. X was probably using vesa or some firmware fbdev interface. Please file a bug (https://bugs.freedesktop.org) and attach your xorg log and dmesg output.
Alex
Quoted 4 lines
_______________________________________________
dri-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/dri-devel