You are not logged in.
Pages: 1
I am using a dell laptop. I connect to a dock that has two monitors connected via DVI. Yesterday (and for years hence), I have been able to use the two docked monitors with minimal problems. Yesterday I ran pacman -Syu; and today, after restarting, I get:
Script started on 2018-05-23 09:50:52-04:00
~/.screenlayout$ lspci | \grep -i vga
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus XTX [Radeon HD 8890M / R9 M275X/M375X] (rev 83)
~/.screenlayout$ pacman -Q | \grep mesa
lib32-mesa 18.0.4-1
mesa 18.0.4-1
~/.screenlayout$ xrandr --output eDP-1 --off \
> --output eDP-1-2 --off \
> --output HDMI-3 --off \
> --output HDMI-2 --off \
> --output HDMI-1 --mode 1920x1080 --pos 0x0 --rotate normal \
> --output DP-1-6 --off \
> --output DP-1-5 --off \
> --output DP-1-4 --mode 1920x1080 --pos 1920x0 --rotate normal \
> --output DP-3 --off \
> --output DP-2 --off \
> --output DP-1 --off \
> --output VGA-1-1 --off
xrandr: Configure crtc 3 failed
~/.screenlayout$ xrandr --verbose | \grep DP-1-4 -A 42
DP-1-4 connected (normal left inverted right x axis y axis)
Identifier: 0x46
Timestamp: 1898669
Subpixel: horizontal rgb
Clones:
CRTCs: 3 4 5 6 7 8
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
filter:
EDID:
00ffffffffffff004c2d4d064e51315a
1315010380351e782a6041a6564a9c25
125054bfef80714f8100814081809500
950fa940b300023a801871382d40582c
4500132b2100001e000000fd00384b1e
5111000a202020202020000000fc0053
4d4232343330480a20202020000000ff
0048434b423530313439330a20200001
PRIME Synchronization: 1
supported: 0, 1
output_csc: bypass
supported: bypass, tvrgb, ycbcr601, ycbcr709
audio: auto
supported: off, on, auto
scaling mode: None
supported: None, Full, Center, Full aspect
dither: off
supported: off, on
underscan vborder: 0
range: (0, 128)
underscan hborder: 0
range: (0, 128)
underscan: off
supported: off, on, auto
coherent: 1
range: (0, 1)
link-status: Good
supported: Good, Bad
CONNECTOR_ID: 52
supported: 52
non-desktop: 0
supported: 0, 1
~/.screenlayout$ exit
exit
Script done on 2018-05-23 09:52:12-04:00
I have also tried using --crtc 4 through 8, and the problem was the same with the error message corresponding to the number I provided.
I have seen this problem before in the following scenario: use the computer docked successfully, undock, reconfigure to use only the built-in laptop monitor, dock again. After that sequence of events, I have often experienced "Configure crtc 3 failed", and couldn't figure out how to address it short of restarting the machine. Today is the first time that restarting the machine doesn't help.
Offline
xrandr -q docked and undocked please, also xorg log from an undocked and docked start.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Thanks for the reply. Here's the information requested in your first comment; let me know if anything else would be helpful.
Docked xrandr: https://ptpb.pw/ZOUJ
Undocked xrandr: https://ptpb.pw/l38p
Docked Xorg: https://ptpb.pw/PQ17
Undocked Xorg: https://ptpb.pw/BTeA
Offline
lspci -nnk output to be sure what card you have.
Check pacman.log, did the update include xorg-server 1.20 ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
lspci -nnk; is https://ptpb.pw/fC82
pacman.log says
[2018-05-22 09:35] [ALPM] upgraded xorg-server (1.19.6+13+gd0d1a694f-2 -> 1.20.0-2)
Offline
Has the update to xorg-server 1.20.0-5 brought an improvement ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Hi, just to mention that I have a similar problem.
Used to work without problem, and since an update around end of may : I need to reboot to have dual display work again. (I mean : once it worls, if I unplug, I won't be able to have monitors work again after I plug them back).
Dell laptop with intel i915
'dock' is made through usb-c adaptor
xrandr --verbose is not helpful in my case :
xrandr --verbose --output eDP-1 --mode 1920x1080 --pos 0x0 --output DP-1 --pos 0x-1080 --mode 1920x1080
screen 0: 1920x2160 508x572 mm 95.92dpi
crtc 0: 1920x1080 59.93 +0+1080 "eDP-1"
crtc 1: 1920x1080 60.00 +0+0 "DP-1"
xrandr: Configure crtc 1 failed
crtc 0: disable
crtc 1: disable
crtc 2: disable
screen 0: revert
crtc 0: revert
crtc 1: revert
crtc 2: revert
One interesting thing is : using gnome-3 "display" utility (in configuration center), I can switch from one monitor to the other, but no dual display.
I cannot perform the same thing with xrandr.
No idea what other logs I could look at.
Offline
Also, note that I did just revert my kernel to 4.16.8-1, which dates back to mid-May
(since i915 drivers are inside kernel, ... at least I guess)
I'll keep this thread updated in case it makes things better.
A first attempt at plug / unplug / replug / unplug / replug / uplug-> sleep -> wake -> plug : ... apparently it works. I'll have to test my Office dock and back to home dock before reaching any conclusion though.
https://archive.archlinux.org/repos/201 … os/x86_64/
Last edited by squalou (2018-06-04 20:26:25)
Offline
So far ... so good, sadly enough.
If it's kernel related it will prbably be hard to bugfix.
Potential culprits could maybe in this revision :
https://cdn.kernel.org/pub/linux/kernel … Log-4.16.9
commit b554e152bd1b8c65e49c61906a845340703d065b
Author: Rodrigo Vivi <rodrigo.vivi@intel.com>
Date: Wed May 2 10:52:55 2018 -0700drm/i915: Adjust eDP's logical vco in a reliable place.
commit b7b575c4f6f135cd71351b4f7986b0e68a09aeb7
Author: Florent Flament <contact@florentflament.com>
Date: Thu Apr 19 19:07:00 2018 +0300drm/i915: Fix drm:intel_enable_lvds ERROR message in kernel log
Offline
Damn it !
failing again after changing from an ub-c connector to another
Offline
Ok, ... sorry for all this noise ... ot kernel related after all. Even the 4.14 lts has the same symptoms.
Offline
Trying wayland as a workaround
Offline
in my case, wayland works best. My case is : USB-C kind of adapters / dock stations. Works much better than xorg. No need to tweak with xrandr anymore.
There are other limitations due to wayland itlsef but nothing blocking in my personnal case.
Offline
And finally ... I couldn't cope with wayland appearing 'sluggish'
So I ended up downgrading xorg-server to 1.19 and ... the world is perfect again
Here's what I did :
sudo pacman -U https://archive.archlinux.org/packages/x/xorg-server/xorg-server-1.19.6%2B13%2Bgd0d1a694f-2-x86_64.pkg.tar.xz
warning: downgrading package xorg-server (1.20.0-7 => 1.19.6+13+gd0d1a694f-2)
resolving dependencies...
looking for conflicting packages...
:: xorg-server and xf86-video-fbdev are in conflict. Remove xf86-video-fbdev? [y/N] y
:: xorg-server and xf86-video-intel are in conflict. Remove xf86-video-intel? [y/N] y
:: xorg-server and xf86-video-vesa are in conflict. Remove xf86-video-vesa? [y/N] y
sudo pacman -U https://archive.archlinux.org/packages/x/xf86-video-vesa/xf86-video-vesa-2.3.4-4-x86_64.pkg.tar.xz
sudo pacman -U https://archive.archlinux.org/packages/x/xf86-video-intel/xf86-video-intel-1%3A2.99.917%2B818%2Bgaf36a4ab-1-x86_64.pkg.tar.xz
sudo pacman -U https://archive.archlinux.org/packages/x/xf86-video-fbdev/xf86-video-fbdev-0.4.4-7-x86_64.pkg.tar.xz
in /etc/pacman.conf add to IgnorePkg = xorg-server xf86-video-vesa xf86-video-intel xf86-video-fbdev
Now I feel bit trapped between two worlds :
- waitng for wayland to become better so that I can drop X
- or waiting for X to solve the issue
Last edited by squalou (2018-06-18 09:32:00)
Offline
That's a head-scratcher. Why does changing X affect a sluggish wayland?
Offline
Looking back at this thread made me realise we didn't investigate other possible causes then xorg 1.20 .
lmat & squalou :
Are you using a display manager or startx/xinit ?
What WM/DE are you using ?
Please try to start X differently and run another wm/de to verify if this influences the problem.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Thanks for the idea! I use startx, and I use xfce4. I tried wayland/gnome and it works fine, but that's not terribly applicable just now :-)
I downgraded Xorg and everything works fine. I don't know how else to start X.
Offline
Could you try with a very simple WM like twm ?
Putting the lines below in ~/.xinitrc and commenting exec startxfce4 should be enough .
(you may need to install twm, xorg-xclock and xterm)
twm &
xclock -geometry 50x50-1+1 &
xterm -geometry 80x50+494+51 &
xterm -geometry 80x20+494-0 &
exec xterm -geometry 80x66+0+0 -name login
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I'm having what I think is the same issue, with a new dock I just bought. Dropping back to the LTS kernel seems to have completely eliminated the issue.
Edit:
* Dell XPS 9550
* Dell TB16 dock
Same issue of having the two attached displays working when I first dock, but if I undock and then redock, can only enable one display. Don't have this issue using the LTS kernel.
Last edited by Winsaucerer (2018-07-16 02:30:01)
Offline
Pages: 1