Description of problem: AMDGPU driver does not load Version-Release number of selected component (if applicable): 4.20.0-0.rc6.git0.1.fc30.x86_64.img How reproducible: Every boot Steps to Reproduce: 1. 2. 3. Actual results: Getting incorrect connector index Expected results: Additional info: from DMESG [ 2.104886] [drm] amdgpu kernel modesetting enabled. [ 2.141784] amdgpu 0000:00:01.0: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used) [ 2.141786] amdgpu 0000:00:01.0: GTT: 1024M 0x0000000000000000 - 0x000000003FFFFFFF [ 2.141937] [drm] amdgpu: 512M of VRAM memory ready [ 2.141938] [drm] amdgpu: 3072M of GTT memory ready. [ 2.149943] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3 [ 2.393255] fbcon: amdgpudrmfb (fb0) is primary device [ 2.420728] amdgpu 0000:00:01.0: fb0: amdgpudrmfb frame buffer device [ 2.426027] [drm] Initialized amdgpu 3.26.0 20150101 for 0000:00:01.0 on minor 0
[ 2.149943] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3 That error message is also reported here (in Attachment 1514618 [details]): Bug 1659711 - amdgpu (carrizo) Kernel 4.19.10-300.fc29.x86_64 Causes xfce desktop environment to become unresponsive Could you post the output from this command? $ journalctl -b | egrep 'smpboot.*AMD|modesetting' (That should show the AMD CPU and GPU for comparison with those in Bug 1659711, Comment 36.) Also, do you see any graphics anomalies like those in the screenshots attached to Bug 1659711?
You filed this bug against xorg-x11-drv-amdgpu, but from Bug 1658844 you seem to be running Gnome3, which uses Wayland instead of Xorg. Could you run this command to determine which it is? $ pgrep -ia 'xorg|wayland'
[EB30750@BRSINC-01Fed ~]$ journalctl -b | egrep 'smpboot.*AMD|modesetting' Dec 24 09:56:29 BRSINC-01Fed kernel: smpboot: CPU0: AMD A10-9600P RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1) Dec 24 09:56:29 BRSINC-01Fed kernel: [drm] amdgpu kernel modesetting enabled. Dec 24 09:56:29 BRSINC-01Fed kernel: [drm] initializing kernel modesetting (CARRIZO 0x1002:0x9874 0x103C:0x8221 0xCA). Dec 24 09:58:21 BRSINC-01Fed /usr/libexec/gdm-x-session[4206]: (==) Matched modesetting as autoconfigured driver 1 Dec 24 09:58:21 BRSINC-01Fed /usr/libexec/gdm-x-session[4206]: (II) LoadModule: "modesetting" Dec 24 09:58:21 BRSINC-01Fed /usr/libexec/gdm-x-session[4206]: (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so Dec 24 09:58:21 BRSINC-01Fed /usr/libexec/gdm-x-session[4206]: (II) Module modesetting: vendor="X.Org Foundation" Dec 24 09:58:21 BRSINC-01Fed /usr/libexec/gdm-x-session[4206]: (II) modesetting: Driver for Modesetting Kernel Drivers: kms [EB30750@BRSINC-01Fed ~]$ pgrep -ia 'xorg|wayland' 4208 /usr/libexec/Xorg vt2 -displayfd 3 -auth /run/user/1001/gdm/Xauthority -background none -noreset -keeptty -verbose 3 I experience NONE of the screen distortion images reported in bug 1659711. I am using GNome desktop. GNome config [EB30750@BRSINC-01Fed ~]$ cat /usr/share/gnome/gnome-version.xml <?xml version="1.0"?> <gnome-version> <platform>3</platform> <minor>30</minor> <micro>2</micro> <distributor>GNOME.Org</distributor> <date>2018-11-15</date> </gnome-version>
Thanks, Paul. That confirms that you have an AMD Carrizo GPU. However, I'm not sure why Wayland isn't running. There is a "gear button" on the login screen to the left of the "Sign In" button that lets you choose "GNOME on Xorg". Did you choose that? If so, could you try the first menu item, which is "GNOME"? See the screenshot here: How to debug Wayland problems https://fedoraproject.org/wiki/How_to_debug_Wayland_problems And for completeness, could you attach the output from: $ journalctl -b --no-hostname > journalctl-1.log
Created attachment 1516587 [details] requested logfile After clicking on user logon name the settings icon appeared. The 3 choices are GNOME, GNOME Classic, and GNOME Xorg. The default setting was GNOME Classic. I changed the default to GNOME but was unable to logon. Tried backup user too and different passwords. No combination allowed successful logon to the desktop. Changed back to the default setiting, GNOME Classic, and successfully logged on.
Thanks for attaching the log file and for your test report. The log file shows non-Fedora code is running. Could you temporarily remove all non-Fedora packages, so we are only debugging Fedora software? $ grep -m 1 taint journalctl-1.log Dec 24 09:56:31 kernel: wl: loading out-of-tree module taints kernel. $ grep -m 1 vmware journalctl-1.log Dec 24 09:56:44 vmware[3339]: Starting VMware services: Anyway, some of it is crashing: $ grep 'vmware-player.*fatal' journalctl-1.log Dec 24 13:44:51 vmware-player.desktop[4494]: XINFO IO fatal error.
Do you have xorg-x11-drv-amdgpu installed? $ rpm -q xorg-x11-drv-amdgpu Log snippet: Dec 24 09:58:21 /usr/libexec/gdm-x-session[4206]: (II) LoadModule: "amdgpu" Dec 24 09:58:21 /usr/libexec/gdm-x-session[4206]: (WW) Warning, couldn't open module amdgpu Dec 24 09:58:21 /usr/libexec/gdm-x-session[4206]: (EE) Failed to load module "amdgpu" (module does not exist, 0)
Created attachment 1516605 [details] sequel copy of requested document Installed this xorg-x11-drv-amdgpu package (Prior to FC27 this was not necessary. Maybe device was just disfunctional) Still getting a connector error [EB30750@BRSINC-01Fed ~]$ rpm -q xorg-x11-drv-amdgpu xorg-x11-drv-amdgpu-18.0.1-4.fc29.x86_64 [EB30750@BRSINC-01Fed ~]$ dmesg | grep gpu [ 2.760794] [drm] amdgpu kernel modesetting enabled. [ 2.777959] amdgpu 0000:00:01.0: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used) [ 2.777961] amdgpu 0000:00:01.0: GART: 1024M 0x000000FF00000000 - 0x000000FF3FFFFFFF [ 2.778126] [drm] amdgpu: 512M of VRAM memory ready [ 2.778128] [drm] amdgpu: 3072M of GTT memory ready. [ 2.778159] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 2.787799] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3 [ 3.028033] fbcon: amdgpudrmfb (fb0) is primary device [ 3.067398] amdgpu 0000:00:01.0: fb0: amdgpudrmfb frame buffer device [ 3.073538] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:00:01.0 on minor 0
(In reply to Paul Lambert from comment #8) > Created attachment 1516605 [details] > sequel copy of requested document > > Installed this xorg-x11-drv-amdgpu package (Prior to FC27 this was not > necessary. Maybe device was just disfunctional) Still getting a connector > error > > [EB30750@BRSINC-01Fed ~]$ rpm -q xorg-x11-drv-amdgpu > xorg-x11-drv-amdgpu-18.0.1-4.fc29.x86_64 ... Thanks for checking that. The attached log (journalctl-2.log) is missing a lot of info, including the "Invalid Connector" message. I'm not sure what could have happened, but could you try generating it again? Normally, the fourth line from the beginning has the kernel command-line: $ journalctl -b | less -N Also, can you log in now using the "GNOME" option on the login screen? If so, is Wayland running?
(In reply to Paul Lambert from comment #8) ... > [EB30750@BRSINC-01Fed ~]$ rpm -q xorg-x11-drv-amdgpu > xorg-x11-drv-amdgpu-18.0.1-4.fc29.x86_64 ... From F29 in a VM, "dnf repoquery" shows a newer version of xorg-x11-drv-amdgpu: # dnf -q repoquery xorg-x11-drv-amdgpu xorg-x11-drv-amdgpu-0:18.1.0-1.fc29.x86_64 # dnf --repo=rawhide -q repoquery xorg-x11-drv-amdgpu xorg-x11-drv-amdgpu-0:18.0.1-4.fc29.x86_64
Here's a link to the newer version: # dnf -q repoquery --location xorg-x11-drv-amdgpu https://fedora.mirror.constant.com/fedora/linux/releases/29/Everything/x86_64/os/Packages/x/xorg-x11-drv-amdgpu-18.1.0-1.fc29.x86_64.rpm # dnf update https://fedora.mirror.constant.com/fedora/linux/releases/29/Everything/x86_64/os/Packages/x/xorg-x11-drv-amdgpu-18.1.0-1.fc29.x86_64.rpm
After installing rawhide in a VM, I found that this will update to the newer version: # dnf update --enablerepo=fedora --releasever=29 xorg-x11-drv-amdgpu
Bug 1662033 - xorg-x11-drv-amdgpu not updated in rawhide
Created attachment 1516691 [details] sequel 2 of requested logfile Reply to previous comments The reduced logfile was due to running as a non admin account I can logon using a non admin account using GNOME. My other other accounts are admin and I have set the default desktop to GNOME-Classic using the Tweaks tool. GNOME defaults to the user setting. I do not see where the desktop setting will affect the video driver. The system has already loaded (or not) the driver during boot sequence. Logging out then logging in of user the user account that uses GNOME desktop did not change anything. Installed latest drv-amdgpu [root@BRSINC-01Fed EB30750]# dnf list | grep amdgpu xorg-x11-drv-amdgpu.x86_64 18.1.0-1.fc29 @fedora Error persists [root@BRSINC-01Fed EB30750]# dmesg | grep gpu [ 2.756945] [drm] amdgpu kernel modesetting enabled. [ 2.774551] amdgpu 0000:00:01.0: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used) [ 2.774553] amdgpu 0000:00:01.0: GART: 1024M 0x000000FF00000000 - 0x000000FF3FFFFFFF [ 2.774716] [drm] amdgpu: 512M of VRAM memory ready [ 2.774718] [drm] amdgpu: 3072M of GTT memory ready. [ 2.774754] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 2.784747] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3 [ 3.024894] fbcon: amdgpudrmfb (fb0) is primary device [ 3.063560] amdgpu 0000:00:01.0: fb0: amdgpudrmfb frame buffer device [ 3.069407] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:00:01.0 on minor 0
(In reply to Paul Lambert from comment #14) > Created attachment 1516691 [details] > sequel 2 of requested logfile Thanks for updating the log file. > Reply to previous comments > > The reduced logfile was due to running as a non admin account OK. I only login as an admin user (wheel), so I didn't know that could happen. Thanks for the explanation! $ groups joeuser joeuser : joeuser wheel > I can logon using a non admin account using GNOME. My other other accounts > are admin and I have set the default desktop to GNOME-Classic using the > Tweaks tool. GNOME defaults to the user setting. > I do not see where the desktop setting will affect the video driver. The > system has already loaded (or not) the driver during boot sequence. Logging > out then logging in of user the user account that uses GNOME desktop did not > change anything. Thanks for doing all those tests. My concern was that Xorg or Wayland could trigger Bug 1659711. > Installed latest drv-amdgpu > [root@BRSINC-01Fed EB30750]# dnf list | grep amdgpu > xorg-x11-drv-amdgpu.x86_64 18.1.0-1.fc29 @fedora > > Error persists ... OK. BTW, kernel 4.20.0-1.fc30 is in the pipeline: https://apps.fedoraproject.org/packages/kernel
xorg-x11-drv-amdgpu is reporting that "0x9874" is an unknown chipset: $ egrep 'CARRIZO|Chipset' journalctl-3.log Dec 25 11:59:35 kernel: [drm] initializing kernel modesetting (CARRIZO 0x1002:0x9874 0x103C:0x8221 0xCA). Dec 25 12:00:03 /usr/libexec/gdm-x-session[4164]: (--) AMDGPU(0): Chipset: "Unknown AMD Radeon GPU" (ChipID = 0x9874) Dec 25 12:00:04 /usr/libexec/gdm-x-session[4164]: (II) AMDGPU(0): glamor X acceleration enabled on AMD CARRIZO (DRM 3.27.0, 4.20.0-0.rc6.git1.1.fc30.x86_64, LLVM 7.0.1) And there is this error: $ grep fb0 journalctl-3.log Dec 25 11:59:36 kernel: fbcon: amdgpudrmfb (fb0) is primary device Dec 25 11:59:36 kernel: amdgpu 0000:00:01.0: fb0: amdgpudrmfb frame buffer device Dec 25 12:00:03 /usr/libexec/gdm-x-session[4164]: (EE) open /dev/fb0: Permission denied
It appears that the unknown chipset error is the problem. Here is report from 4.20.0-1.fc30.x86_64 #1 SMP Tue Dec 25 02:07:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux [root@BRSINC-01Fed wl]# dmesg | grep gpu [ 2.763383] [drm] amdgpu kernel modesetting enabled. [ 2.780926] amdgpu 0000:00:01.0: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used) [ 2.780928] amdgpu 0000:00:01.0: GART: 1024M 0x000000FF00000000 - 0x000000FF3FFFFFFF [ 2.781088] [drm] amdgpu: 512M of VRAM memory ready [ 2.781090] [drm] amdgpu: 3072M of GTT memory ready. [ 2.781118] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 2.790793] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3 [ 3.033920] fbcon: amdgpudrmfb (fb0) is primary device [ 3.079764] amdgpu 0000:00:01.0: fb0: amdgpudrmfb frame buffer device [ 3.086077] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:00:01.0 on minor 0 Don't know if chipset is not supported due to special drive code or, due to just never being added to kernel device code. If the former then probably should close this bug report as wont fix.
(In reply to Paul Lambert from comment #17) > It appears that the unknown chipset error is the problem. > > Here is report from 4.20.0-1.fc30.x86_64 #1 SMP Tue Dec 25 02:07:16 UTC 2018 > x86_64 x86_64 x86_64 GNU/Linux Thanks for testing 4.20.0. ... > [ 2.790793] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector > ObjectID from Adapter Service for connector index:2! type 0 expected 3 ... > Don't know if chipset is not supported due to special drive code or, due to > just never being added to kernel device code. If the former then probably > should close this bug report as wont fix. That error message is from this kernel file: $ grep -A2 'Invalid Connector ObjectID' linux-4.20/drivers/gpu/drm/amd/display/dc/core/dc_link.c dm_error("%s: Invalid Connector ObjectID from Adapter Service for connector index:%d! type %d expected %d\n", __func__, init_params->connector_index, link->link_id.type, OBJECT_TYPE_CONNECTOR); And this merge commit includes changes* to dc_link.c: Merge tag 'drm-next-2018-12-14' of git://anongit.freedesktop.org/drm/drm https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4971f090aa7f6ce5daa094ce4334f6618f93a7eb AFAICT, that commit is destined for kernel 4.21. You can track the progress of Fedora kernel builds here: https://koji.fedoraproject.org/koji/packageinfo?packageID=8 * Disclaimer: I make no claims to know what those changes actually do. :-)
I confirm the bug also affect Raven Ridge Mobile: journalctl -b --no-hostname | egrep 'smpboot.*AMD|modesetting' Dec 31 20:33:26 kernel: smpboot: CPU0: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx (family: 0x17, model: 0x11, stepping: 0x0) Dec 31 20:33:26 kernel: [drm] amdgpu kernel modesetting enabled. Dec 31 20:33:26 kernel: [drm] initializing kernel modesetting (RAVEN 0x1002:0x15DD 0x103C:0x8497 0xC4). amdgpu is installed as listed: rpm -q xorg-x11-drv-amdgpu xorg-x11-drv-amdgpu-18.1.0-1.fc29.x86_64 [ 2.453646] [drm] amdgpu kernel modesetting enabled. [ 2.474151] fb: switching to amdgpudrmfb from EFI VGA [ 2.474332] amdgpu 0000:03:00.0: enabling device (0006 -> 0007) [ 2.476323] amdgpu 0000:03:00.0: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used) [ 2.476324] amdgpu 0000:03:00.0: GART: 1024M 0x000000F500000000 - 0x000000F53FFFFFFF [ 2.476474] [drm] amdgpu: 2048M of VRAM memory ready [ 2.476475] [drm] amdgpu: 3072M of GTT memory ready. [ 2.476483] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 2.629235] amdgpu: [powerplay] dpm has been enabled [ 2.630600] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3 [ 2.672510] fbcon: amdgpudrmfb (fb0) is primary device
(In reply to Luya Tshimbalanga from comment #19) > I confirm the bug also affect Raven Ridge Mobile: ... Thanks for your report. Could you post your kernel version: $ uname -r
(In reply to Steve from comment #20) > > Thanks for your report. Could you post your kernel version: > > $ uname -r 4.19.12-301.fc29.x86_64
Dmesg output for amdgpu in version 5.0.0-0.rc3.git0.1.fc30.x86_64 Fixed? if so then proceed to close. [ 3.025644] [drm] vram apper at 0x2FF000000 [ 3.025645] [drm] size 5787648 [ 3.025646] [drm] fb depth is 24 [ 3.025647] [drm] pitch is 6400 [ 3.025757] fbcon: amdgpudrmfb (fb0) is primary device [ 3.038272] Console: switching to colour frame buffer device 200x56 [ 3.054180] amdgpu 0000:00:01.0: fb0: amdgpudrmfb frame buffer device [ 3.072714] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:00:01.0 on minor 0
Hi Hp Pavillion Amd Notebook Amd A10 9600p Apu Cpu R5 + R7 Gpu Kernel: 4.20.5 All kernels acpi and drm errors dmesg | grep gpu [ 15.345790] [drm] amdgpu kernel modesetting enabled. [ 15.348692] fb0: switching to amdgpudrmfb from EFI VGA [ 15.409158] amdgpu 0000:00:01.0: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used) [ 15.409161] amdgpu 0000:00:01.0: GART: 1024M 0x000000FF00000000 - 0x000000FF3FFFFFFF [ 15.409410] [drm] amdgpu: 512M of VRAM memory ready [ 15.409412] [drm] amdgpu: 3072M of GTT memory ready. [ 15.409443] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 16.648393] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3 ************************************************************************************************************************************************************ [ 16.899285] fbcon: amdgpudrmfb (fb0) is primary device [ 16.923101] amdgpu 0000:00:01.0: fb0: amdgpudrmfb frame buffer device [ 16.933965] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:00:01.0 on minor 0 [ 16.934159] amdgpu 0000:04:00.0: enabling device (0000 -> 0003) [ 16.989434] amdgpu 0000:04:00.0: kfd not supported on this ASIC [ 17.188122] amdgpu 0000:04:00.0: VRAM: 4096M 0x000000F400000000 - 0x000000F4FFFFFFFF (4096M used) [ 17.188130] amdgpu 0000:04:00.0: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF [ 17.188557] [drm] amdgpu: 4096M of VRAM memory ready [ 17.188563] [drm] amdgpu: 4096M of GTT memory ready. [ 17.188630] [drm] GART: num cpu pages 65536, num gpu pages 65536 [ 17.547136] amdgpu: [powerplay] can't get the mac of 5 [ 17.557499] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:04:00.0 on minor 1 [ 17.782215] audit: type=1130 audit(1548710791.467:20): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-backlight@backlight:amdgpu_bl0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 33.879776] amdgpu: [powerplay] VI should always have 2 performance levels [ 33.968474] amdgpu 0000:04:00.0: GPU pci config reset [ 61.691966] amdgpu: [powerplay] can't get the mac of 5 [ 66.915617] amdgpu: [powerplay] VI should always have 2 performance levels [ 66.991119] amdgpu 0000:04:00.0: GPU pci config reset [ 1873.233216] amdgpu: [powerplay] can't get the mac of 5 [ 1879.072325] amdgpu: [powerplay] VI should always have 2 performance levels [ 1879.146674] amdgpu 0000:04:00.0: GPU pci config reset [ 1887.841427] amdgpu: [powerplay] can't get the mac of 5 [ 1893.148842] amdgpu: [powerplay] VI should always have 2 performance levels [ 1893.222992] amdgpu 0000:04:00.0: GPU pci config reset [ 2540.049322] amdgpu: [powerplay] can't get the mac of 5 [ 2545.086917] amdgpu: [powerplay] VI should always have 2 performance levels [ 2545.162049] amdgpu 0000:04:00.0: GPU pci config reset
With kernel 5.0.0-0.rc6.git1.2.fc30.x86_64 a new error is being reported in dmesg [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3
FYI This is logged routinely on Ryzen 2400G desktop as well currently on F29 but desktop has been largely usable with no apparent impact. [ 3.140639] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3 pgrep -ia 'xorg|wayland' 1910 /usr/libexec/gdm-wayland-session /usr/bin/gnome-session 2088 /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6
Hp Pavillion Amd Notebook Amd A10 9600p Apu Cpu R5 + R7 Gpu [serdar@fedora Masaüstü]$ uname -a Linux fedora 5.0.0-300.fc30.x86_64 #1 SMP Mon Mar 4 22:46:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux [serdar@fedora Masaüstü]$ dmesg | grep gpu [ 4.125106] [drm] amdgpu kernel modesetting enabled. [ 4.126454] fb0: switching to amdgpudrmfb from EFI VGA [ 4.179447] amdgpu 0000:00:01.0: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used) [ 4.179449] amdgpu 0000:00:01.0: GART: 1024M 0x000000FF00000000 - 0x000000FF3FFFFFFF [ 4.179635] [drm] amdgpu: 512M of VRAM memory ready [ 4.179636] [drm] amdgpu: 3072M of GTT memory ready. [ 4.179659] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 4.189578] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3 [ 4.437232] fbcon: amdgpudrmfb (fb0) is primary device [ 4.437237] amdgpu 0000:00:01.0: fb0: amdgpudrmfb frame buffer device [ 4.452074] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:00:01.0 on minor 0 [ 4.452197] amdgpu 0000:04:00.0: enabling device (0000 -> 0003) [ 4.505374] amdgpu 0000:04:00.0: kfd not supported on this ASIC [ 4.544935] amdgpu 0000:04:00.0: VRAM: 4096M 0x000000F400000000 - 0x000000F4FFFFFFFF (4096M used) [ 4.544937] amdgpu 0000:04:00.0: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF [ 4.545293] [drm] amdgpu: 4096M of VRAM memory ready [ 4.545295] [drm] amdgpu: 4096M of GTT memory ready. [ 4.545333] [drm] GART: num cpu pages 65536, num gpu pages 65536 [ 4.578872] amdgpu: [powerplay] can't get the mac of 5 [ 4.589887] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:04:00.0 on minor 1 [ 19.008929] amdgpu: [powerplay] VI should always have 2 performance levels [ 19.090225] amdgpu 0000:04:00.0: GPU pci config reset
Likewise I get this error, definitely I am using wayland. [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.20.16-200.fc29.x86_64 root=/dev/mapper/fedora-root ro resume=/dev/mapper/fedora-swap rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet LANG=en_US.UTF-8 idle=nomwait iommu=pt processor.max_cstate=1 $ dmesg | grep amdgpu [ 2.466629] [drm] amdgpu kernel modesetting enabled. [ 2.467034] fb0: switching to amdgpudrmfb from EFI VGA [ 2.467137] amdgpu 0000:04:00.0: enabling device (0006 -> 0007) [ 2.469780] amdgpu 0000:04:00.0: VRAM: 256M 0x000000F400000000 - 0x000000F40FFFFFFF (256M used) [ 2.469781] amdgpu 0000:04:00.0: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF [ 2.469783] amdgpu 0000:04:00.0: AGP: 267419648M 0x000000F800000000 - 0x0000FFFFFFFFFFFF [ 2.470080] [drm] amdgpu: 256M of VRAM memory ready [ 2.470081] [drm] amdgpu: 3072M of GTT memory ready. [ 3.370445] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3 [ 3.451645] fbcon: amdgpudrmfb (fb0) is primary device [ 3.451652] amdgpu 0000:04:00.0: fb0: amdgpudrmfb frame buffer device [ 3.472443] amdgpu 0000:04:00.0: ring 0(gfx) uses VM inv eng 4 on hub 0 [ 3.472447] amdgpu 0000:04:00.0: ring 1(comp_1.0.0) uses VM inv eng 5 on hub 0 [ 3.472450] amdgpu 0000:04:00.0: ring 2(comp_1.1.0) uses VM inv eng 6 on hub 0 [ 3.472452] amdgpu 0000:04:00.0: ring 3(comp_1.2.0) uses VM inv eng 7 on hub 0 [ 3.472455] amdgpu 0000:04:00.0: ring 4(comp_1.3.0) uses VM inv eng 8 on hub 0 [ 3.472458] amdgpu 0000:04:00.0: ring 5(comp_1.0.1) uses VM inv eng 9 on hub 0 [ 3.472460] amdgpu 0000:04:00.0: ring 6(comp_1.1.1) uses VM inv eng 10 on hub 0 [ 3.472463] amdgpu 0000:04:00.0: ring 7(comp_1.2.1) uses VM inv eng 11 on hub 0 [ 3.472465] amdgpu 0000:04:00.0: ring 8(comp_1.3.1) uses VM inv eng 12 on hub 0 [ 3.472480] amdgpu 0000:04:00.0: ring 9(kiq_2.1.0) uses VM inv eng 13 on hub 0 [ 3.472482] amdgpu 0000:04:00.0: ring 10(sdma0) uses VM inv eng 4 on hub 1 [ 3.472485] amdgpu 0000:04:00.0: ring 11(vcn_dec) uses VM inv eng 5 on hub 1 [ 3.472499] amdgpu 0000:04:00.0: ring 12(vcn_enc0) uses VM inv eng 6 on hub 1 [ 3.472502] amdgpu 0000:04:00.0: ring 13(vcn_enc1) uses VM inv eng 7 on hub 1 [ 3.472504] amdgpu 0000:04:00.0: ring 14(vcn_jpeg) uses VM inv eng 8 on hub 1 [ 3.480250] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:04:00.0 on minor 0 To get the 4.20 kernels to boot I have raven_dmcu.bin removed from /lib/firmware/amdgpu/ See https://bugs.freedesktop.org/show_bug.cgi?id=109206
Still present in Kernel 5.0.5-200.fc29.x86_64 with xorg-x11-drv-amdgpu-19.0.0-1.fc29.x86_64
lspci -nn | grep -E 'VGA|Display' 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) uname -r 5.0.0-23-generic dmesg | grep amdgpu [ 5.678069] [drm] amdgpu kernel modesetting enabled. [ 5.679824] fb0: switching to amdgpudrmfb from EFI VGA [ 5.685129] amdgpu 0000:00:01.0: kfd not supported on this ASIC [ 5.685459] amdgpu 0000:00:01.0: VRAM: 80M 0x000000F400000000 - 0x000000F404FFFFFF (80M used) [ 5.685461] amdgpu 0000:00:01.0: GART: 1024M 0x000000FF00000000 - 0x000000FF3FFFFFFF [ 5.685607] [drm] amdgpu: 80M of VRAM memory ready [ 5.685609] [drm] amdgpu: 2913M of GTT memory ready. [ 5.926349] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3 [ 6.167656] fbcon: amdgpudrmfb (fb0) is primary device [ 6.167835] amdgpu 0000:00:01.0: fb0: amdgpudrmfb frame buffer device [ 6.320508] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:00:01.0 on minor 0
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
Anyone here seeing this one: Bug 1738650 - Kernel 5.2.5 graphics unstable https://bugzilla.redhat.com/show_bug.cgi?id=1738650 Everytning working great as long as I stay on kernel-5.1.20-300.fc30.x86_64
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.