xrandr / amdgpu issue with new graphics card

nexx1 · 2017-12-05 17:46:54

Lone_Wolf wrote:

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.

Well, sadly it doesnt change a thing. Same behaviour as before

lo1 wrote:

https://bbs.archlinux.org/viewtopic.php?id=229182 found it wink
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.

I cant completely follow you, but amdgpu is the correct driver (see https://wiki.archlinux.org/index.php/Xorg#AMD)
Regarding the provided thread, i cant exchange the cables because the monitors have either VGA/DVI or VGA/HDMI.

The very strange this is, that this issue did not occur before swappig the graphics card.

And @seth: Sorry, but you lost me

EDIT:
Well, i think i just solved. Long story short: I created a /etc/X11/xorg.conf.d/10-monitor.conf as stated in https://wiki.archlinux.org/index.php/Multihead#RandR and changed the identifiers and resolutions to my needs, rebooted and voila - duplicated login screen and afterwards the correct layout.

EDIT2:
One strange thing remains - I did set the resolution 3840x2160 (2x 1920x1080) in the 10-monitor.conf but xrandr -q says that my current resolution is 2x 1920x1200. It seems that the 10-monitor.conf somehow provokes a somewhat-working-state, from what my custom xrandr commands in the openbox' autostart.sh are being executed correctly. Weird.

Last edited by nexx1 (2017-12-05 18:00:27)

loqs · 2017-12-05 17:55:26

I believe seth was suggesting you test using startx instead of lxdm after fixing your .xinitrc
Xinit#xinitrc

Note: At the very least, ensure that the last if block in /etc/X11/xinit/xinitrc is present in your .xinitrc file to ensure that the scripts in /etc/X11/xinit/xinitrc.d are sourced.

lo1 · 2017-12-05 20:11:14

nexx1 wrote:

I cant completely follow you, but amdgpu is the correct driver (see https://wiki.archlinux.org/index.php/Xorg#AMD)
Regarding the provided thread, i cant exchange the cables because the monitors have either VGA/DVI or VGA/HDMI.

That was dumb of me, I forgot to check if your video card was supported by radeon.
I posted that topic because the OP there was experiencing the same issue as you with an AMD R9 series and xf86-video-amdgpu, so I was suspecting an issue with the driver.
Good to know you solved it.
Post that 10-monitor.conf, I'm sure it's easily fixable.

nexx1 · 2017-12-06 15:33:38

lo1 wrote:

Post that 10-monitor.conf, I'm sure it's easily fixable.

Here it is:

xx@yy ~ $ cat /etc/X11/xorg.conf.d/10-monitor.conf 
Section "Monitor"
  Identifier "HDMI-A-0"
  Modeline "1920x1080_60.00"  146.25  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync
  Option "PreferredMode" "1920x1080_60.00"
  Option "LeftOf" "DVI-I-0"
  Option "DPMS" "true"
EndSection

Section "Monitor"
  Identifier "DVI-I-0"
  Modeline "1920x1080_60.00"  173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync
  Option "PreferredMode" "1920x1080_60.00"
  Option "RightOf" "HDMI-A-0"
  Option "DPMS" "true"
EndSection

Section "Screen"
  Identifier "Screen0"
  Device "Radeon" # e.g. Radeon, Intel, nvidia
  Monitor "HDMI-A-0"
  DefaultDepth 24
  SubSection "Display"
    Depth 24
    Virtual 3840 2160 
  EndSubSection
EndSection

seth · 2017-12-06 15:46:32

The first modeline ("HDMI-A-0") describes a 1680x1050 resolution.
-> "man cvt"

Also "Virtual 3840 2160": do you understand what this means and do you actually want it? Why is there a screen section itfp?

nexx1 · 2017-12-06 16:03:21

Well, the screen section exists because the example in the wiki uses it. Additionaly, wiki xorg.conf tells me, that there is at least on screen section needed.

I technically do not care if i use one large 3840x2160 resolution or 2x 1920x1080.

Which is the correct section for setting the resolution?

seth · 2017-12-06 16:20:50

Whatever wiki section you're referring to is wrong - Monitor sections with matching identifiers are sufficient, also the screen section describes a single monitor setup ("HDMI-A-0") with a virtual resolution of 3840x2160 px, ie. if it would apply you'd get a 1680x1050 output panning a 3840x2160 root window (but the description starts with a server, defining a screen identifier to use)

nexx1 · 2017-12-06 16:34:02

I am referring to https://wiki.archlinux.org/index.php/Multihead#RandR --> Section "Example: dualhead configuration using relative coordinates with custom resolutions"

But you are right with the screen section, thats rubbish. I deleted that part, works as before, nice.

Last edited by nexx1 (2017-12-06 16:36:24)

seth · 2017-12-06 16:35:24

You'll still have to fix the modeline.

nexx1 · 2017-12-06 16:45:25

I tried, but failed:

xx@yy ~ $ cvt -v 1920 1200 60.0
# 1920x1200 59.88 Hz (CVT 2.30MA) hsync: 74.56 kHz; pclk: 193.25 MHz
Modeline "1920x1200_60.00"  193.25  1920 2056 2256 2592  1200 1203 1209 1245 -hsync +vsync

Pasted into the 10-monitor.conf does result in a black 2nd screen. (yes, i deleted the old/wrong but working one)

nexx1 · 2017-12-06 17:20:16

I tried something, which is why i am writing from my windows right now...

Searching the xorg log for modeline entries i found one for my desired 1920x1200. I used it, and now the boot process is stuck at the amdgpu initialisation

sp5100_tco: I/O address 0x0cd6 already in use
kvm: disabled by bios
amdgpu 0000:0b:00.0: Invalid PCI ROM header signature: expecting
0xaa55, got 0xffff

The modeline was slightly different than the other ones, beginning with "1920x1200"x60.0. The x60.0 is the problematic part.

Now i just gotta get a live usb stick to run and reset the modeline...

seth · 2017-12-06 17:47:34

The modelines identifier is arbitrary, you can call it "modey_mc_modeline".
Try one with reduced blanking, if the output turns off for the regular one, some element in the chain (output/cable/input) doesn't support WUXGA

nexx1 · 2017-12-06 19:05:24

Finally, back to my arch system.

@seth: To be clear, i do not know how to fix the modeline. I cant even see the error because its just working fine as it is.

seth · 2017-12-06 20:28:26

cvt -r 1920 1080
# 1920x1080 59.93 Hz (CVT 2.07M9-R) hsync: 66.59 kHz; pclk: 138.50 MHz
Modeline "1920x1080R"  138.50  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync

I'm not sure what you mean by "fine" or how you would achieve that, but that modeline will get you a 1680x1050 resolution on HDMI-A-0
Any higher resolution is not the result of that modeline.

Lone_Wolf · 2017-12-08 13:02:14

post xrandr -q please, so we can see what X does set.

nexx1 · 2017-12-12 17:00:58

Lone_Wolf wrote:

post xrandr -q please, so we can see what X does set.

Here it is:

xx@yy ~ $ xrandr -q
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

Current state: No changes to the initial starting point, so no X config files.
I recently tested the behaviour of the LXDE-profile selected at the login screen. This does set the correct resolution to all screens. Using lxrandr inside the LXDE-session saves the changes to ~./config/autostart/lxrandr-autostart.desktop.

Using the savebutton of lxrandr inside the openbox-session though does write the correct config to the mentioned file but without the effect of working at the next reboot.

Lone_Wolf · 2017-12-12 17:41:47

That folder is one of the places for such files, what is the value of $XDG_CONFIG_HOME in lxde profile & openbox-sesssion ?

seth · 2017-12-12 21:11:29

That's the expectable output and if one of the screens is off, there's some "confusion" in the driver stack (possibly induced by a rapid sequence of ranr calls?)

The desktop service can limit its visibility to certain session types (you'd need to inspect it, it's plain text)

As for the original problem, let's draw the broad sword and rule out possible offenders: rename xrandr, lxrandr (and pot. arandr) to eg. not.xrandr, not.lxrandr and not.arandr and see whether a reboot/restart of the session sees any change.

nexx1 · 2017-12-13 16:08:42

Lone_Wolf wrote:

That folder is one of the places for such files, what is the value of $XDG_CONFIG_HOME in lxde profile & openbox-sesssion ?

Well, uhm, its empty:

xx@yy ~ $ echo $XDG_CONFIG_HOME

xx@yy ~ $

seth wrote:

As for the original problem, let's draw the broad sword and rule out possible offenders: rename xrandr, lxrandr (and pot. arandr) to eg. not.xrandr, not.lxrandr and not.arandr and see whether a reboot/restart of the session sees any change.

Do you mean /usr/bin/*randr?

Last edited by nexx1 (2017-12-13 16:11:20)

seth · 2017-12-13 16:42:54

Exactly those, I want to see whether one of them is used to alter your layout at startup and what happens if that doesn't take place.

There're assumed default paths for the xdg variables (if unset)

nexx1 · 2017-12-16 13:44:41

Sorry for the repeating delay, i am not spending much time at home at the moment.

Before testing the renaming, i just want to add an oddity i encountered today:
Booting with the usual problems, doing other stuff away from the pc --> screens are getting turned off (screensaver). Ending this with some input, the screens suddenly show the right resolution and layout.

Now proceeding with renaming the *randr files.

Edit1: Renamed /usr/bin/xrandr --> same behaviour of the problem, so no change (exept for the nonworking lxrandr what is expected)

Edit2: Renamed /usr/bin/lxrandr --> well... there is no change to be seen as well.

Last edited by nexx1 (2017-12-16 13:51:08)

nexx1 · 2018-02-06 18:33:56

This issues seems to be solved. I just updated to kernel 4.15.1 and the problems are gone thanks to the new drivers regarding radeon/vega.

Arch Linux

#26 2017-12-05 17:46:54

Re: xrandr / amdgpu issue with new graphics card

#27 2017-12-05 17:55:26

Re: xrandr / amdgpu issue with new graphics card

#28 2017-12-05 20:11:14

Re: xrandr / amdgpu issue with new graphics card

#29 2017-12-06 15:33:38

Re: xrandr / amdgpu issue with new graphics card

#30 2017-12-06 15:46:32

Re: xrandr / amdgpu issue with new graphics card

#31 2017-12-06 16:03:21

Re: xrandr / amdgpu issue with new graphics card

#32 2017-12-06 16:20:50

Re: xrandr / amdgpu issue with new graphics card

#33 2017-12-06 16:34:02

Re: xrandr / amdgpu issue with new graphics card

#34 2017-12-06 16:35:24

Re: xrandr / amdgpu issue with new graphics card

#35 2017-12-06 16:45:25

Re: xrandr / amdgpu issue with new graphics card

#36 2017-12-06 17:20:16

Re: xrandr / amdgpu issue with new graphics card

#37 2017-12-06 17:47:34

Re: xrandr / amdgpu issue with new graphics card

#38 2017-12-06 19:05:24

Re: xrandr / amdgpu issue with new graphics card

#39 2017-12-06 20:28:26

Re: xrandr / amdgpu issue with new graphics card

#40 2017-12-08 13:02:14

Re: xrandr / amdgpu issue with new graphics card

#41 2017-12-12 17:00:58

Re: xrandr / amdgpu issue with new graphics card

#42 2017-12-12 17:41:47

Re: xrandr / amdgpu issue with new graphics card

#43 2017-12-12 21:11:29

Re: xrandr / amdgpu issue with new graphics card

#44 2017-12-13 16:08:42

Re: xrandr / amdgpu issue with new graphics card

#45 2017-12-13 16:42:54

Re: xrandr / amdgpu issue with new graphics card

#46 2017-12-16 13:44:41

Re: xrandr / amdgpu issue with new graphics card

#47 2018-02-06 18:33:56

Re: xrandr / amdgpu issue with new graphics card

Board footer