amdgpu needed blacklisting of radeon module

Bug #1696231 reported by Török Edwin
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I have installed a new Radeon card alongside the old one:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] (rev cf)
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730 PRO [Radeon HD 4650]

Booted Ubuntu, and the console just froze when switching to graphics mode. I was not able to switch consoles with ctrl+alt+f1/ctrl+alt+f2, despite having NAutoVTs=6 in /etc/systemd/logind.conf.
I could login via SSH, but all I could see is that X wasn't able to find any screens, but without any clues why:
[ 11.142] (EE) No devices detected.

Finally when running X -configure as root I got the following helpful log message before crashing:
amdgpu_device_initialize: DRM version is 2.49.0 but this driver is only compatible with 3.x.x.

After some searching I found that I should blacklist the radeon module to get the amdgpu module working, and indeed adding this file fixed it:

/etc/modprobe.d/blacklist-radeon.conf
# cannot load both amdgpu and radeon
blacklist radeon

Then: sudo update-initramfs -u -k all

Another workaround is to remove the old graphics card, that made booting work again.

I think there is a bug here though: X shouldn't crash: it should be able to use at least one of the two graphics card drivers, and the text console should still be operational even if it failed to initialize graphical mode, so that the user can log in, investigate and fix things from a local console, instead of relying on fixing things over SSH.

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: xserver-xorg-core 2:1.19.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CrashCounter: 1
Date: Mon Jun 5 20:44:06 2017
ExecutablePath: /usr/lib/xorg/Xorg
ExecutableTimestamp: 1490632988
InstallationDate: Installed on 2017-03-25 (71 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcCwd: /
ProcEnviron: PATH=(custom, no user)
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 OsAbort ()
 ?? ()
 FatalError ()
 ?? ()
 __libc_start_main (main=0x556cb5e47590, argc=11, argv=0x7ffca36148c8, init=<optimised out>, fini=<optimised out>, rtld_fini=<optimised out>, stack_end=0x7ffca36148b8) at ../csu/libc-start.c:291
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Török Edwin (edwintorok) wrote :
Revision history for this message
Török Edwin (edwintorok) wrote :
Revision history for this message
Török Edwin (edwintorok) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1543192, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-amd64-retrace
Revision history for this message
Török Edwin (edwintorok) wrote :

The crash stacktrace might be the same as in the dup report, due to no screens found, but I think it is a separate bug: the dup bugreport has no indication of 2 graphics cards being used, and the need to blacklist one module.

Revision history for this message
MasterCATZ (mastercatz) wrote :

how can I get radeon and amdgpu to play nice with each other ?
or better yet not use amdgpu and still be able to use opencl

I have a A10-5800K APU and R9 290

Ubuntu 16.04 / amdgpu-pro-17.40-492261

lspci -nnk | grep -i vga -A3 | grep 'in use'
 Kernel driver in use: radeon
 Kernel driver in use: amdgpu

amdgpu_device_initialize: DRM version is 2.50.0 but this driver is only compatible with 3.x.x.

Revision history for this message
Demon (demonrx) wrote :

Firstly, AMD has released amdgpu-pro 18.10 (for rhel and supports Ubuntu 16.04.4):

https://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-for-Linux-Release-Notes.aspx

Download Links are on the site.

Secondly, I'm still having the DRM version issue, and I have come across a post on reddit about this:

https://www.reddit.com/r/vulkan/comments/4idouk/problem_with_vulkan_on_amd_linux/

More specifically the comment here: https://www.reddit.com/r/vulkan/comments/4idouk/problem_with_vulkan_on_amd_linux/d2xc4ta/

where the issue seems to have to do with the driver that's in use by linux (radeon) rather than amdgpu:

amdgpu has version 3.1.0:
https://github.com/torvalds/linux/blob/32cf95db22d49cf4a3b421ba9fd156bb5f920ebb/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c#L49-L56

and radeon has version 2.43:
https://github.com/torvalds/linux/blob/32cf95db22d49cf4a3b421ba9fd156bb5f920ebb/drivers/gpu/drm/radeon/radeon_drv.c#L95-L99

In Addition, the reddit user talks about having `CONFIG_DRM_AMDGPU_CIK=y` set to 'y' to enable support for the GPU in amdgpu driver (this requires manually compiling the linux kernel, as the default has this setting off). You can check if your currently running kernel has this option:

   grep CONFIG_DRM_AMDGPU_CIK /boot/config*

And checking what driver is actually in use by linux:

   lspci -nnk | grep -i vga -A3 | grep 'in use'

So the question is how to get the amdgpu driver to load in place of radeon ?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg-server (Ubuntu):
status: New → Confirmed
Norbert (nrbrtx)
tags: removed: zesty
Changed in xorg-server (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]

Changed in xorg-server (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.