Unresolved AMDGPU issue with a new install on an HP255G7 laptop

tannington · August 31, 2019, 8:25pm

I have one unresolved issue with a new install of leap 15.1 on an HP255G7 laptop.

At boot I get the following error message:

Aug 28 13:55:09 HP255G7 kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3
Aug 28 13:55:09 HP255G7 kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3

This, as far as I’m able to tell, is just an annoyance rather than a problem, there appears nothing wrong with the graphics.

Googling for that error returns quite a few hits, but they are invariably from people reporting “serious” problems with the graphics.

A little hardware info:

paul@HP255G7:~> sudo journalctl -b | egrep 'smpboot.*AMD|modesetting'
[sudo] password for root: 
Aug 28 13:55:08 HP255G7 kernel: smpboot: CPU0: AMD Ryzen 3 2200U with Radeon Vega Mobile Gfx (family: 0x17, model: 0x11, stepping: 0x0)
Aug 28 13:55:08 HP255G7 kernel: [drm] amdgpu kernel modesetting enabled.
Aug 28 13:55:08 HP255G7 kernel: [drm] initializing kernel modesetting (RAVEN 0x1002:0x15DD 0x103C:0x84AE 0xC5).
paul@HP255G7:~>

paul@HP255G7:~> inxi -GGx
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Radeon Vega 8 Mobile bus-ID: 04:00.0
           Display Server: x11 (X.Org 1.20.3 ) drivers: ati,amdgpu (unloaded: modesetting,fbdev,vesa)
           Resolution: 1920x1080@60.01hz
           OpenGL: renderer: AMD RAVEN (DRM 3.27.0, 4.12.14-lp151.28.13-default, LLVM 7.0.1)
           version: 4.5 Mesa 18.3.2 Direct Render: Yes
paul@HP255G7:~>

malcolmlewis · August 31, 2019, 10:26pm

Hi
FWIW, I see the same here HP Pavillion 15 (On Tumbleweed), no issues though…


dmesg |grep drm:construct

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

journalctl -b | egrep 'smpboot.*AMD|modesetting'

Aug 31 15:21:53 bert kernel: smpboot: CPU0: AMD A10-9600P RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1)
Aug 31 15:21:56 bert kernel: [drm] amdgpu kernel modesetting enabled.
Aug 31 15:21:56 bert kernel: [drm] initializing kernel modesetting (CARRIZO 0x1002:0x9874 0x103C:0x81FE 0xCA).
Aug 31 15:21:57 bert kernel: [drm] initializing kernel modesetting (TOPAZ 0x1002:0x6900 0x103C:0x81FE 0x83).

inxi -Gxx

Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] vendor: Hewlett-Packard driver: amdgpu 
           v: kernel bus ID: 00:01.0 chip ID: 1002:9874 
           Device-2: AMD Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] vendor: Hewlett-Packard driver: amdgpu 
           v: kernel bus ID: 04:00.0 chip ID: 1002:6900 
           Display: tty server: X.org 1.20.5 driver: amdgpu compositor: gnome-shell tty: 191x27 
           Message: Advanced graphics data unavailable in console for root.

tannington · September 1, 2019, 12:21pm

OK… Thanks. I’ll continue to ignore it

All appears fine otherwise, I’m quite impressed with it’s performance, better than I anticipated.

I’ve “entangle” ( https://software.opensuse.org/package/entangle ) up and running, which is what I primarily envisaged using it for, so quite pleased with that.

I may even have became a laptop convert

dcurtisfra · September 2, 2019, 1:08pm

@tannington:

Have you added “modprobe.blacklist=radeon” to the Kernel command line?

I suspect that, the Radeon driver can interfere with the AMD GPU driver as much as the reverse case …

tannington · September 2, 2019, 1:42pm

No… I’ll give that a try later today, although to be quite honest I’m not too bothered about the error message, as it’s not to my knowledge causing any issues. I do acknowledge though it would be nice to see the message gone.

malcolmlewis · September 2, 2019, 2:56pm

Hi
The later cards only use amdgpu, no radeon involved;

Newer card… no radeon in kernel modules output;


/sbin/lspci -nnk | egrep -A3 "VGA|Display|3D"
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev ca)
    Subsystem: Hewlett-Packard Company Device [103c:81fe]
    Kernel driver in use: amdgpu
    Kernel modules: amdgpu
--
04:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] [1002:6900] (rev 83)
    DeviceName: AMD Radeon (TM) R7 440M
    Subsystem: Hewlett-Packard Company Device [103c:81fe]
    Kernel driver in use: amdgpu

Older card, can use either;


 /sbin/lspci -nnk | egrep -A3 "VGA|Display|3D"
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R3 Graphics] [1002:9850] (rev 40)
    Subsystem: Hewlett-Packard Company Device [103c:8305]
    Kernel driver in use: amdgpu
    Kernel modules: radeon, amdgpu

tannington · September 2, 2019, 3:49pm

@dcurtisfra

Tried blacklisting “radeon”, no difference:

paul@HP255G7:~> journalctl -b | grep -i "drm:construct"
Sep 02 14:42:04 HP255G7 kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3
Sep 02 14:42:04 HP255G7 kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3
paul@HP255G7:~>

but that was before I’d read the post by @malcolmlewis

looks like I have a “new” card:

paul@HP255G7:~> /sbin/lspci -nnk | egrep -A3 "VGA|Display|3D"
04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Radeon Vega 8 Mobile [1002:15dd] (rev c5)
        Subsystem: Hewlett-Packard Company Device [103c:84ae]
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu
paul@HP255G7:~>

mrmazda · September 3, 2019, 5:29am

FWIW, this is not reproducible with my older GCN1 card:

# inxi -GxxSaz
System:    Host: big31 Kernel: 4.12.14-lp151.28.13-default x86_64 bits: 64 compiler: gcc v: 7.4.0
           parameters: root=/dev/sda30 ipv6.disable=1 net.ifnames=0 noresume mitigations=auto consoleblank=0
           radeon.si_support=0 amdgpu.si_support=1 vga=791 video=1280x720@60 video=1024x768@60 video=1440x900@60 5
           Desktop: Trinity R14.0.6 tk: Qt 3.5.0 wm: Twin dm: TDM Distro: openSUSE Leap 15.1
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] vendor: Dell driver: amdgpu
           v: kernel bus ID: 01:00.0 chip ID: 1002:6611
           Display: server: X.Org 1.20.3 driver: amdgpu unloaded: fbdev,modesetting,vesa alternate: ati
           resolution: 2560x1440~60Hz, 1920x1200~60Hz
           OpenGL: renderer: AMD Radeon HD 8500 Series (OLAND DRM 3.27.0 4.12.14-lp151.28.13-default LLVM 7.0.1)
           v: 4.5 Mesa 18.3.2 direct render: Yes
big31:~ # xrandr | egrep 'onnect|creen|\*' | grep -v disconn | sort -r
Screen 0: minimum 320 x 200, current 2560 x 2640, maximum 16384 x 16384
DisplayPort-0 connected primary 2560x1440+0+1200 (normal left inverted right x axis y axis) 598mm x 336mm
DVI-I-0 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 519mm x 324mm
   2560x1440     59.95*+  74.92
   1920x1200     59.95*+
# journalctl -b | grep -i "drm:construct"
#

tannington · September 3, 2019, 4:23pm

Yes, I’m guessing perhaps the software doesn’t yet fully support newer cards correctly.

A bug report may be in order I suppose… but I’m unsure what against “xf86-video-amdgpu”, or maybe “libdrm_amdgpu1”, or maybe ??? - I’m not at all familiar with AMD video cards / drivers.

Either way, as I’ve no obvious problems, I’d be rather reluctant to file the report myself; and no, I’m not hinting that you should.

malcolmlewis · September 3, 2019, 5:41pm

Hi
Just add your info to this one…
https://bugs.freedesktop.org/show_bug.cgi?id=104206

tannington · September 3, 2019, 6:37pm

Good find, thanks…