xrandr / amdgpu issue with new graphics card

nexx1 · 2017-11-27 16:01:31

Hi!

I initially set up my Arch with an AMD HD7770 installed using amdgpu. However, 6 weeks ago i changed the graphics card to a R9 380 without any change to arch.

The driver itself works just fine (gaming is fine, some glitches in Blender GUI and wine + sketchup.)

My issue now is, that my dual monitor set up does not work correctly after boot. During boot, the displays are mirrored (as suspected) but the moment the driver takes over, one of the display is being shut-off (is it really?).

I am using openbox with this xrandr command in the autostart.sh:

xrandr --output HDMI-A-0 --primary --mode 1920x1200 --pos 0x0 --rotate normal --output DVI-I-1 --mode 1920x1200 --rotate normal --right-of HDMI-A-0

Which seems not be executed. It did work as it should before i swapped the graphic card.

I now use lxrandr to manually turn off the display, turn it on again and apply the above mentioned xrandr command again - which then works.

Does anybody have a clue what could go wrong here? Where can i start debugging?

xx@yy ~ $ pacman -Qs amdgpu
local/xf86-video-amdgpu 1.4.0-1 (xorg-drivers)
    X.org amdgpu video driver

xx@yy ~ $ uname -ar
Linux chrisarch 4.13.12-1-ARCH #1 SMP PREEMPT Wed Nov 8 11:54:06 CET 2017 x86_64 GNU/Linux

xx@yy ~ $ pacman -Qs mesa
local/glu 9.0.0-4
    Mesa OpenGL Utility library
local/lib32-glu 9.0.0-3
    Mesa OpenGL utility library (32 bits)
local/lib32-libtxc_dxtn 1.0.1-5
    S3 Texture Compression (S3TC) library for Mesa (32-bit)
local/lib32-mesa 17.2.5-1
    an open-source implementation of the OpenGL specification (32-bit)
local/libtxc_dxtn 1.0.1-6
    S3 Texture Compression (S3TC) library for Mesa
local/mesa 17.2.5-1
    an open-source implementation of the OpenGL specification
local/mesa-demos 8.3.0-4
    Mesa demos and tools incl. glxinfo + glxgears
local/mesa-vdpau 17.2.5-1
    Mesa VDPAU drivers

xx@yy ~ $ pacman -Qs openbox
local/lxappearance-obconf 0.2.3-1 (lxde)
    Plugin for LXAppearance to configure Openbox
local/obconf 2.0.4-4
    A GTK2 based configuration tool for the Openbox windowmanager
local/openbox 3.6.1-3 (lxde lxde-gtk3 lxqt)
    Highly configurable and lightweight X11 window manager

Last edited by nexx1 (2017-11-27 16:02:47)

lo1 · 2017-11-27 16:13:09

Really dumb question: have you checked if the naming of your output devices is the same? HDMI-A-0 seems unusual to me.
Also, what have you found in Xorg log?

nexx1 · 2017-11-27 16:26:52

lo1 wrote:

Really dumb question: have you checked if the naming of your output devices is the same? HDMI-A-0 seems unusual to me.
Also, what have you found in Xorg log?

You are right, i did indeed have to change the device name in the command But the name is correct, at least xrandr does output HDMI-A-0:

xx@yy ~ $ xrandr
Screen 0: minimum 320 x 200, current 3840 x 1200, maximum 16384 x 16384
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
HDMI-A-0 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 519mm x 324mm
   1920x1200     59.95*+
   1920x1080     60.00    59.94  
   1920x1080i    60.00    59.94  
   1600x1200     60.00  
   1680x1050     59.88  
   1280x1024     76.00    75.02    72.05    60.02  
   1440x900      74.98    59.90  
   1152x864      75.00  
   1280x720      60.00    59.94  
   1024x768      75.03    70.07    60.00  
   1440x480i     59.94  
   832x624       74.55  
   800x600       72.19    75.00    60.32  
   720x480       60.00    59.94  
   720x480i      60.00    59.94  
   640x480       75.00    72.81    66.67    60.00    59.94  
   720x400       70.08  
DVI-D-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 connected 1920x1200+1920+0 (normal left inverted right x axis y axis) 518mm x 324mm
   1920x1200     59.95*+
   1920x1080     60.00    50.00  
   1680x1050     59.88  
   1600x900      60.00  
   1280x1024     60.02  
   1440x900      59.90  
   1280x800      59.91  
   1280x720      60.00    50.00    59.94  
   1024x768      60.00  
   800x600       60.32    56.25  
   720x576       50.00  
   720x480       60.00    59.94  
   640x480       60.00    59.94

The Xorg.0.log is rather big and withouth timestamps, so its hard to read, but one line i found (marked with arrows) is telling me:

[     5.967] (II) AMDGPU(0): Output DisplayPort-0 disconnected
[     5.967] (II) AMDGPU(0): Output HDMI-A-0 connected
[     5.967] (II) AMDGPU(0): Output DVI-D-0 disconnected
[     5.967] (II) AMDGPU(0): Output DVI-I-1 connected
[     5.967] (II) AMDGPU(0): Using spanning desktop for initial modes
[     5.967] (II) AMDGPU(0): Output HDMI-A-0 using initial mode 1920x1200 +0+0
[     5.967] (II) AMDGPU(0): Output DVI-I-1 using initial mode 1920x1200 +1920+0
[     5.967] (II) AMDGPU(0): mem size init: gart size :ffe3d000 vram size: s:febd3000 visible:ebd3000
[     5.967] (==) AMDGPU(0): DPI set to (96, 96)
[     5.967] (==) AMDGPU(0): Using gamma correction (1.0, 1.0, 1.0)
[     5.967] (II) Loading sub module "ramdac"
[     5.967] (II) LoadModule: "ramdac"
[     5.967] (II) Module "ramdac" already built-in
[     5.967] (II) UnloadModule: "modesetting"
[     5.967] (II) Unloading modesetting
[     5.967] (--) Depth 24 pixmap format is 32 bpp
[     5.968] (II) AMDGPU(0): [DRI2] Setup complete
[     5.968] (II) AMDGPU(0): [DRI2]   DRI driver: radeonsi
[     5.968] (II) AMDGPU(0): [DRI2]   VDPAU driver: radeonsi
[     5.968] (II) AMDGPU(0): Front buffer pitch: 15360 bytes
[     5.969] (II) AMDGPU(0): SYNC extension fences enabled
[     5.969] (II) AMDGPU(0): Present extension enabled
[     5.969] (==) AMDGPU(0): DRI3 enabled
[     5.969] (==) AMDGPU(0): Backing store enabled
[     5.969] (II) AMDGPU(0): Direct rendering enabled
[     5.979] (II) AMDGPU(0): Use GLAMOR acceleration.
[     5.979] (II) AMDGPU(0): Acceleration enabled
[     5.979] (==) AMDGPU(0): DPMS enabled
[     5.979] (==) AMDGPU(0): Silken mouse enabled
[     5.979] (II) AMDGPU(0): Set up textured video (glamor)
[     5.979] (II) AMDGPU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[     6.075] (--) RandR disabled <-<-<-<-<-<-<-<-<-<-<-<-<-<-<-
[     6.079] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[     6.079] (II) AIGLX: enabled GLX_ARB_create_context
[     6.079] (II) AIGLX: enabled GLX_ARB_create_context_profile
[     6.079] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[     6.079] (II) AIGLX: enabled GLX_INTEL_swap_event

I can provide the complete Xorg logfile via pastebin if needed.

Last edited by nexx1 (2017-11-27 16:27:30)

seth · 2017-11-27 17:06:48

Did you also see the line above? ;-)
What's the output of xrandr when the output (which?) is supposingly off?

nexx1 · 2017-11-27 18:27:13

seth wrote:

Did you also see the line above? ;-)
What's the output of xrandr when the output (which?) is supposingly off?

Ooops, i appearently didnt '-_-

Didnt mention it in the startpost: the Display "DVI-I-1 is causing the problem, HDMI-A-0 is fine.

The xrandr after booting and before doing the manual lxrandr/xrandr:

xx@yy ~ $ xrandr
Screen 0: minimum 320 x 200, current 3840 x 1200, maximum 16384 x 16384
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
HDMI-A-0 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 519mm x 324mm
   1920x1200     59.95*+
   1920x1080     60.00    59.94  
   1920x1080i    60.00    59.94  
   1600x1200     60.00  
   1680x1050     59.88  
   1280x1024     76.00    75.02    72.05    60.02  
   1440x900      74.98    59.90  
   1152x864      75.00  
   1280x720      60.00    59.94  
   1024x768      75.03    70.07    60.00  
   1440x480i     59.94  
   832x624       74.55  
   800x600       72.19    75.00    60.32  
   720x480       60.00    59.94  
   720x480i      60.00    59.94  
   640x480       75.00    72.81    66.67    60.00    59.94  
   720x400       70.08  
DVI-D-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 connected 1920x1200+1920+0 (normal left inverted right x axis y axis) 518mm x 324mm
   1920x1200     59.95*+
   1920x1080     60.00    50.00  
   1680x1050     59.88  
   1600x900      60.00  
   1280x1024     60.02  
   1440x900      59.90  
   1280x800      59.91  
   1280x720      60.00    50.00    59.94  
   1024x768      60.00  
   800x600       60.32    56.25  
   720x576       50.00  
   720x480       60.00    59.94  
   640x480       60.00    59.94

lo1 · 2017-11-27 20:03:36

DVI-I-1 connected 1920x1200+1920+0 (normal left inverted right x axis y axis) 518mm x 324mm
   1920x1200     59.95*+

So the resolution is preferred and applied, this means xrandr sends the request (but perhaps the VGA isn't ready to process the request?)
Have you tried enabling early KMS? https://wiki.archlinux.org/index.php/AM … _early_KMS

seth · 2017-11-27 20:43:47

Rule #1 with xrandr issues: try to split the calls

xrandr --output HDMI-A-0 --primary --mode 1920x1200 --pos 0x0 --rotate normal
xrandr  --output DVI-I-1 --mode 1920x1200 --rotate normal --right-of HDMI-A-0

nexx1 · 2017-11-27 20:46:18

lo1 wrote:

So the resolution is preferred and applied, this means xrandr sends the request (but perhaps the VGA isn't ready to process the request?)
Have you tried enabling early KMS? https://wiki.archlinux.org/index.php/AM … _early_KMS

Small minor glitch in the wiki:

MODULES="... amdgpu ..."

should be

MODULES=(... amdgpu ....)

But it didnt change a thing, same behaviour as before.

Just wanted to add something i found in dmesg:

[    3.270527] amdgpu 0000:0b:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff

Is this error any bad? Its marked red.

[    3.659269] amdgpu: [powerplay] amdgpu: powerplay sw initialized
[    3.659434] [drm] AMDGPU Display Connectors
[    3.659435] [drm] Connector 0:
[    3.659435] [drm]   DP-1
[    3.659436] [drm]   HPD4
[    3.659437] [drm]   DDC: 0x4868 0x4868 0x4869 0x4869 0x486a 0x486a 0x486b 0x486b
[    3.659437] [drm]   Encoders:
[    3.659437] [drm]     DFP1: INTERNAL_UNIPHY1
[    3.659438] [drm] Connector 1:
[    3.659438] [drm]   HDMI-A-1
[    3.659438] [drm]   HPD5
[    3.659439] [drm]   DDC: 0x4870 0x4870 0x4871 0x4871 0x4872 0x4872 0x4873 0x4873
[    3.659439] [drm]   Encoders:
[    3.659439] [drm]     DFP2: INTERNAL_UNIPHY1
[    3.659440] [drm] Connector 2:
[    3.659440] [drm]   DVI-D-1
[    3.659440] [drm]   HPD1
[    3.659441] [drm]   DDC: 0x4878 0x4878 0x4879 0x4879 0x487a 0x487a 0x487b 0x487b
[    3.659441] [drm]   Encoders:
[    3.659441] [drm]     DFP3: INTERNAL_UNIPHY
[    3.659442] [drm] Connector 3:
[    3.659442] [drm]   DVI-I-1
[    3.659442] [drm]   HPD6
[    3.659443] [drm]   DDC: 0x487c 0x487c 0x487d 0x487d 0x487e 0x487e 0x487f 0x487f
[    3.659443] [drm]   Encoders:
[    3.659443] [drm]     DFP4: INTERNAL_UNIPHY2
[    3.659444] [drm]     CRT1: INTERNAL_KLDSCP_DAC1

So this tells me, that amdgpu initializes all connectors correctly.

Last edited by nexx1 (2017-11-27 20:53:50)

seth · 2017-11-27 20:54:25

https://bbs.archlinux.org/viewtopic.php?id=211734

nexx1 · 2017-11-27 20:59:39

seth wrote:

https://bbs.archlinux.org/viewtopic.php?id=211734

Thanks, so nothing to complain about here.

seth wrote:

Rule #1 with xrandr issues: try to split the calls

Applied, but the behaviour does not change.

Lone_Wolf · 2017-11-28 14:56:36

Are you using a display manager ?

If not, have you tried putting those commands in xinitrc ?

nexx1 · 2017-11-28 16:40:55

Lone_Wolf wrote:

Are you using a display manager ?
If not, have you tried putting those commands in xinitrc ?

Yes, i am using openbox with lxde.

Just tried it with the .xinitrc, with no success:

xx@yy ~ $ cat .xinitrc 
xrandr --output HDMI-A-0 --primary --mode 1920x1200 --pos 0x0 --rotate normal
xrandr  --output DVI-I-1 --mode 1920x1200 --rotate normal --right-of HDMI-A-0
exec startlxde

seth · 2017-11-28 16:50:41

Tried ~/.config/lxsession/LXDE/autostart instead, resp. only "openbox-session", w/o lxde?

nexx1 · 2017-11-29 16:04:05

seth wrote:

Tried ~/.config/lxsession/LXDE/autostart instead, resp. only "openbox-session", w/o lxde?

The xrandr commands in the LXDE/autostart have no effect, just tried it.

Now I just need to find out how to use openbox without lxde to try your suggestion

seth · 2017-11-29 16:09:53

exec openbox-session

nexx1 · 2017-11-29 16:25:40

Well, at least putting it into .xinitrc does nothing.

Maybe there just is no other way than using the dualhead method via 10-monitor.conf as suggested in https://wiki.archlinux.org/index.php/Multihead#RandR

seth · 2017-11-29 19:28:34

What do you mean by "putting it into .xinitrc does nothing"?
What does your xinitrc look like then and what's the output of "which openbox-session"

nexx1 · 2017-11-30 16:06:32

My default .xinitrc is this:

exec startlxde

Replacing it with openbox-session:

exec openbox-session

...with no effect.

xx@yy ~ $ which openbox-session
/usr/bin/openbox-session

seth · 2017-11-30 16:08:54

Sorry it's still not clear what you mean by "no effect" - does openbox not start at all or do you still end up in lxde or does the randr adjustment still fail?

nexx1 · 2017-11-30 16:45:49

seth wrote:

Sorry it's still not clear what you mean by "no effect" - does openbox not start at all or do you still end up in lxde or does the randr adjustment still fail?

Ah sorry, now i know what you mean

I do have several options when logging in (graphical, default LXDE) - when i choose "openbox" the openbox-session starts up. Choosing "Standard" or "LXDE" does start the lxde-session.

Choosing "openbox" at login does start the openbox-session regardless of the content of my .xinitrc

I hope this clears things up

Last edited by nexx1 (2017-11-30 16:46:13)

seth · 2017-11-30 18:01:16

That sounds as if you're using some DM what makes it highly unlikely that the xinitrc is invoked at all.
Get the DM (which?) out of the equation.

nexx1 · 2017-11-30 18:10:33

I am using lxdm, nothing fancy here

seth · 2017-11-30 21:11:38

As https://wiki.archlinux.org/index.php/LX … figuration points out, xinitrc isn't invoked. So it doesn't matter what you put there.
Also when using a DM (ok: "but xdm") you're NOT supposed to execute any session by hand (in any config file), you're selecting it and the DM runs the session from that selection.

In case this doesn't get you anywhere, try to configure randr from /etc/lxdm/LoginReady (but iirc that doesn't work) and ultimately to get lxdm out of the way (https://wiki.archlinux.org/index.php/Xinit explains to correctly setup an xinitrc to be used by startx or xinit)

Lone_Wolf · 2017-12-02 14:01:58

you could also try to put the xrandr commands in ~/.xprofile .
That file should be executed by majority of display managers when user logs in just before the session is started.

lo1 · 2017-12-02 14:13:52

https://bbs.archlinux.org/viewtopic.php?id=229182 found it

What I'd suggest is try to use xf86-video-radeon instead, as it seems to me that Xorg is doing the best that it can, replace the module in your mkinitcpio.conf, and see if that was a driver issue from the start.

Arch Linux

#1 2017-11-27 16:01:31

xrandr / amdgpu issue with new graphics card

#2 2017-11-27 16:13:09

Re: xrandr / amdgpu issue with new graphics card

#3 2017-11-27 16:26:52

Re: xrandr / amdgpu issue with new graphics card

#4 2017-11-27 17:06:48

Re: xrandr / amdgpu issue with new graphics card

#5 2017-11-27 18:27:13

Re: xrandr / amdgpu issue with new graphics card

#6 2017-11-27 20:03:36

Re: xrandr / amdgpu issue with new graphics card

#7 2017-11-27 20:43:47

Re: xrandr / amdgpu issue with new graphics card

#8 2017-11-27 20:46:18

Re: xrandr / amdgpu issue with new graphics card

#9 2017-11-27 20:54:25

Re: xrandr / amdgpu issue with new graphics card

#10 2017-11-27 20:59:39

Re: xrandr / amdgpu issue with new graphics card

#11 2017-11-28 14:56:36

Re: xrandr / amdgpu issue with new graphics card

#12 2017-11-28 16:40:55

Re: xrandr / amdgpu issue with new graphics card

#13 2017-11-28 16:50:41

Re: xrandr / amdgpu issue with new graphics card

#14 2017-11-29 16:04:05

Re: xrandr / amdgpu issue with new graphics card

#15 2017-11-29 16:09:53

Re: xrandr / amdgpu issue with new graphics card

#16 2017-11-29 16:25:40

Re: xrandr / amdgpu issue with new graphics card

#17 2017-11-29 19:28:34

Re: xrandr / amdgpu issue with new graphics card

#18 2017-11-30 16:06:32

Re: xrandr / amdgpu issue with new graphics card

#19 2017-11-30 16:08:54

Re: xrandr / amdgpu issue with new graphics card

#20 2017-11-30 16:45:49

Re: xrandr / amdgpu issue with new graphics card

#21 2017-11-30 18:01:16

Re: xrandr / amdgpu issue with new graphics card

#22 2017-11-30 18:10:33

Re: xrandr / amdgpu issue with new graphics card

#23 2017-11-30 21:11:38

Re: xrandr / amdgpu issue with new graphics card

#24 2017-12-02 14:01:58

Re: xrandr / amdgpu issue with new graphics card

#25 2017-12-02 14:13:52

Re: xrandr / amdgpu issue with new graphics card

Board footer