Bug 23766 - No/poor hardware acceleration available for Radeon Vega 8 (AMD Ryzen 2200G) *ERROR* construct: Invalid Connector ObjectID from Adapter Service
Summary: No/poor hardware acceleration available for Radeon Vega 8 (AMD Ryzen 2200G) *...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL: https://forums.mageia.org/en/viewtopi...
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2018-10-26 21:40 CEST by Adam Dolata
Modified: 2020-08-03 17:49 CEST (History)
3 users (show)

See Also:
Source RPM: x11-driver-video-amdgpu-1.4.0-1.mga6
CVE:
Status comment:


Attachments
dmesg.log (65.08 KB, text/plain)
2018-10-26 21:42 CEST, Adam Dolata
Details
Xorg.0.log (38.64 KB, text/plain)
2018-10-26 21:43 CEST, Adam Dolata
Details
inxi -F (1.81 KB, text/plain)
2018-10-26 21:48 CEST, Adam Dolata
Details

Description Adam Dolata 2018-10-26 21:40:47 CEST
Description of problem:

1. There seems to be no 3d acceleration (2200fps ist glxgears, 130fps in fullscreen mode - i assume it should be approx. 10x more on this machine...). 

2. There are also several errors in dmesg.log and xorg.log (see below and attachments)

[    3.257534] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3

[   578.015] (EE) AMDGPU(0): glamor detected, failed to initialize EGL.


3.The system doesn't wake from sleep mode (blank screen - no signal).


Version-Release number of selected component (if applicable):
x11-driver-video-amdgpu-1.4.0-1.mga6
mesa-17.3.9-1.mga6


Steps to Reproduce:
1. Install Mageia 6.1 on a Ryzen 2200G machine with no dedicated graphic card
2. Update kernel from backports to kernel-desktop-4.18.12-1.mga6
3a. Run glxgears benchmark
3b. Get into sleep mode and try to wake the system.
Comment 1 Adam Dolata 2018-10-26 21:42:20 CEST
Created attachment 10429 [details]
dmesg.log
Comment 2 Adam Dolata 2018-10-26 21:43:06 CEST
Created attachment 10430 [details]
Xorg.0.log
Comment 3 Adam Dolata 2018-10-26 21:48:32 CEST
Created attachment 10431 [details]
inxi -F
Comment 4 Marja Van Waes 2018-10-27 21:10:06 CEST
Assigning to the kernel & drivers maintainers, CC'ing the registered maintainer.

CC: (none) => marja11, thierry.vignaud
Assignee: bugsquad => kernel

Comment 5 Adam Dolata 2018-12-11 11:06:16 CET
(In reply to Marja Van Waes from comment #4)
> Assigning to the kernel & drivers maintainers, CC'ing the registered
> maintainer.

Situation after updating kernel to 4.18.20-desktop-1.mga6:

1. Still no/poor 3d acceleration

2. Both errors still present

3. System wakes up after sleep mode normally, so the problem #3 seems to be solved.
Comment 6 Adam Dolata 2019-02-07 11:35:42 CET
Any news in this issue? System is using llvmpipe - although the graphics chip is recognized correctly.

bash-4.3$ glxgears -info         
GL_RENDERER   = llvmpipe (LLVM 3.9, 128 bits)
GL_VERSION    = 3.0 Mesa 17.3.9
GL_VENDOR     = VMware, Inc.
GL_EXTENSIONS = GL_ARB_multisample GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_minmax...
Comment 7 Adam Dolata 2019-04-26 16:53:21 CEST
Mageia 7 beta3 (5.1.0-desktop-0.rc6.2.mga7) seems to solve most of the problems. There is a significant speed-up in the way the system is working, and 3D acceleration. 

The "drm:construct error" still exist.


vblank_mode=0 glxgears -info
ATTENTION: default value of option vblank_mode overridden by environment.
GL_RENDERER   = AMD RAVEN (DRM 3.30.0, 5.1.0-desktop-0.rc6.2.mga7, LLVM 8.0.0)
GL_VERSION    = 4.5 (Compatibility Profile) Mesa 19.0.3
GL_VENDOR     = X.Org
GL_EXTENSIONS = GL_ARB_multisample...
57236 frames in 5.0 seconds = 11447.106 FPS

[    12.743] (II) Loading sub module "glamoregl"
[    12.743] (II) LoadModule: "glamoregl"
[    12.743] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
[    12.747] (II) Module glamoregl: vendor="X.Org Foundation"
[    12.747] 	compiled for 1.20.4, module version = 1.0.1
[    12.747] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    12.760] (II) AMDGPU(0): glamor X acceleration enabled on AMD RAVEN (DRM 3.30.0, 5.1.0-desktop-0.rc6.2.mga7, LLVM 8.0.0)
[    12.760] (II) AMDGPU(0): glamor detected, initialising EGL layer.


[    2.825402] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3
[    2.901896] fbcon: amdgpudrmfb (fb0) is primary device
Comment 8 Thierry Vignaud 2019-04-27 14:00:33 CEST
What's the output of "lspcidrake -v|grep Card"?

Keywords: (none) => NEEDINFO

Comment 9 Adam Dolata 2019-04-28 18:43:15 CEST
bash-4.3$ lspcidrake -v|grep Card

Card:ATI Volcanic Islands and later (amdgpu/fglrx): Advanced Micro Devices, Inc. [AMD/ATI]|Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [DISPLAY_VGA] (vendor:1002 device:15dd subv:1458 subd:d000) (rev: c8)
Comment 10 Aurelien Oudelet 2020-08-03 17:49:01 CEST
This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

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 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

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 Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

CC: (none) => ouaurelien
Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.