You are not logged in.
I have just gotten myself a 2560x1600 external TFT, which I connect to my laptop via DisplayPort. The laptopt itself (Thinkpad X201), sits in a Docking Station, which in turn provides the DisplayPort. The X201 has an Intel GMA 5700MHD internal graphics.
I used to happen issues, where the monitor entered standby/sleep mode, and wouldn't wake up after moving the mouse. The same thing happens if I send the laptop itself to suspend and wake it up - the monitor simply does not get a signal. I fixed the first issue by switching from UXA to the SNA stack in the Intel Xorg driver.
Now, what usually happens:
I start the laptop, and the external Monitor DP1 gets the same signal as the laptop's LVDS1 screen (1280x800). Running xrandr, everything is detected nicely.
However, now running the below commands usually does not work at the first try (turning LVDS1 off in one step actually never works):
$ xrandr --output DP1 --auto --output LVDS1 --auto
# Or alternatively
$ xrandr --output DP1 --auto --output LVDS1 --offThe TFT simply says it's not getting any signal.
After some iterations of turning the signal off and on, it finally works (like in the session I have started to write this post):
$ xrandr --output DP1 --auto
$ xrandr --output DP1 --off
$ xrandr --output DP1 --auto
# Aha, it worked! Time to turn off the laptop screen!
$ xrandr --output LVDS1 --offWhen finally DP1 gets a signal, I can safely turn off LVDS1.
Any ideas what's up with that? I figure something is messed up with the Intel driver. I found the solution to the sleep problem with the SNA stack somewhere here in the forums.
Offline
Hi,
sorry for digging out this old thread, but it's unanswered so far and I have the exact same problem. Did you find a solution yet?
Is it just a coincidence, that I have almost the same configuration? My machine is an X201s, sitting in the docking station and hooked up to an external screen via DisplayPort (the screen is an Eizo). In this configuration, want to do the same thing: Disable LVDS1 and use only the DP1-output as my primary screen.
I used to happen issues, where the monitor entered standby/sleep mode, and wouldn't wake up after moving the mouse.
This is the most annoying thing! It happens almost always. Every once in a while, it will however wake up. How did you get rid of this? I have created /etc/X11/xorg.conf.d/20-intel.conf:
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "sna"
EndSectionand /var/log/Xorg.0.log says
intel(0): SNA initialized with Ironlake backendBut the issue persists...
The same thing happens if I send the laptop itself to suspend and wake it up - the monitor simply does not get a signal.
Same here. As with the issue above, it breaks almost always, however, I've seen it work occasionally.
As a workaround, I use the following script:
#!/bin/bash
echo "Setting screen configuration..."
SCREEN_DP=`xrandr | grep -o "DP1 connected"`
SCREEN_VGA=`xrandr | grep -o "VGA1 connected"`
if [ -n "$SCREEN_DP" ]; then
# assume EIZO setup
xrandr --output VGA1 --off
xrandr --output DP1 --off
xrandr --output DP1 --auto
xrandr --output DP1 --mode 1920x1200
xrandr --output DP1 --primary
xrandr --output LVDS1 --off
elif [ -n "$SCREEN_VGA" ]; then
# assume work setup
xrandr --output DP1 --off
xrandr --output VGA1 --mode 1280x1024 --above LVDS1
xrandr --output LVDS1 --mode 1440x900
else
# otherwise, enable laptop screen
xrandr --output LVDS1 --mode 1440x900
xrandr --output LVDS1 --primary
xrandr --output VGA1 --off
xrandr --output DP1 --off
fi
echo "Screen configuration set."I configured a keyboard shortcut, so that I can run it even when the screen is stuck in standby. But usually, I have to run it several times, before the screen comes back on.
Maybe it is connected to the type of machine (IronLake + Docking station)? First I suspected, it might be a power management issue, but removing 'tlp' didn't do anything.
Also, there are log messages like this, after booting up, or using standby, or the monitor going to sleep:
[ 19.572607] ------------[ cut here ]------------
[ 19.572649] WARNING: at drivers/gpu/drm/i915/intel_display.c:1028 intel_wait_for_pipe_off+0xd2/0x190 [i915]()
[ 19.572652] Hardware name: 5397FBG
[ 19.572653] pipe_off wait timed out
[ 19.572655] Modules linked in: snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_device rfcomm btusb joydev bnep bluetooth snd_hda_codec_hdmi snd_hda_codec_conexant arc4 iwldvm mac80211 coretemp kvm_intel kvm iTCO_wdt iTCO_vendor_support crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 xts lrw gf128mul ablk_helper cryptd psmouse microcode serio_raw iwlwifi intel_ips i2c_i801 cfg80211 thermal wmi snd_hda_intel thinkpad_acpi snd_hda_codec acpi_cpufreq mperf snd_hwdep nvram ac snd_pcm snd_page_alloc rfkill snd_timer battery snd e1000e soundcore mei lpc_ich evdev processor tp_smapi(O) thinkpad_ec(O) nfs lockd sunrpc fscache ext4 crc16 jbd2 mbcache hid_generic usbhid hid sr_mod cdrom sd_mod ahci libahci libata ehci_pci ehci_hcd scsi_mod usbcore usb_common i915 video button i2c_algo_bit intel_agp
[ 19.572717] intel_gtt drm_kms_helper drm i2c_core
[ 19.572725] Pid: 265, comm: X Tainted: G O 3.8.8-2-ARCH #1
[ 19.572727] Call Trace:
[ 19.572735] [<ffffffff81057190>] warn_slowpath_common+0x70/0xa0
[ 19.572739] [<ffffffff8105720c>] warn_slowpath_fmt+0x4c/0x50
[ 19.572755] [<ffffffffa00a4552>] intel_wait_for_pipe_off+0xd2/0x190 [i915]
[ 19.572770] [<ffffffffa00a4715>] intel_disable_pipe+0x105/0x180 [i915]
[ 19.572783] [<ffffffffa00a4ea6>] ironlake_crtc_disable+0xc6/0x870 [i915]
[ 19.572797] [<ffffffffa00b780b>] ? intel_dp_mode_fixup+0x24b/0x280 [i915]
[ 19.572811] [<ffffffffa00aca36>] intel_set_mode+0x306/0x940 [i915]
[ 19.572826] [<ffffffffa00ad84e>] intel_crtc_set_config+0x6de/0x900 [i915]
[ 19.572839] [<ffffffffa0020a69>] drm_mode_setcrtc+0x549/0x5b0 [drm]
[ 19.572848] [<ffffffffa00111e1>] drm_ioctl+0x4c1/0x570 [drm]
[ 19.572860] [<ffffffffa0020520>] ? drm_mode_setplane+0x380/0x380 [drm]
[ 19.572867] [<ffffffff81199715>] do_vfs_ioctl+0x2e5/0x4d0
[ 19.572871] [<ffffffff81199981>] sys_ioctl+0x81/0xa0
[ 19.572878] [<ffffffff814c731d>] system_call_fastpath+0x1a/0x1f
[ 19.572881] ---[ end trace 02a6580ca2d4b736 ]---
...
[25707.631288] ------------[ cut here ]------------
[25707.631336] WARNING: at drivers/gpu/drm/i915/intel_dp.c:1997 intel_dp_link_down+0x1ab/0x1b0 [i915]()
[25707.631339] Hardware name: 5397FBG
[25707.631340] Modules linked in: hidp md4 sha256_generic md5 hmac nls_utf8 cifs fuse snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_device rfcomm btusb joydev bnep bluetooth snd_hda_codec_hdmi snd_hda_codec_conexant arc4 iwldvm mac80211 coretemp kvm_intel kvm iTCO_wdt iTCO_vendor_support crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 xts lrw gf128mul ablk_helper cryptd psmouse microcode serio_raw iwlwifi intel_ips i2c_i801 cfg80211 thermal wmi snd_hda_intel thinkpad_acpi snd_hda_codec acpi_cpufreq mperf snd_hwdep nvram ac snd_pcm snd_page_alloc rfkill snd_timer battery snd e1000e soundcore mei lpc_ich evdev processor tp_smapi(O) thinkpad_ec(O) nfs lockd sunrpc fscache ext4 crc16 jbd2 mbcache hid_generic usbhid hid sr_mod cdrom sd_mod ahci libahci libata ehci_pci ehci_hcd scsi_mod usbcore
[25707.631403] usb_common i915 video button i2c_algo_bit intel_agp intel_gtt drm_kms_helper drm i2c_core
[25707.631415] Pid: 32495, comm: kworker/u:28 Tainted: G W O 3.8.8-2-ARCH #1
[25707.631417] Call Trace:
[25707.631426] [<ffffffff81057190>] warn_slowpath_common+0x70/0xa0
[25707.631430] [<ffffffff8105727a>] warn_slowpath_null+0x1a/0x20
[25707.631445] [<ffffffffa00b6f5b>] intel_dp_link_down+0x1ab/0x1b0 [i915]
[25707.631459] [<ffffffffa00b90d8>] intel_dp_check_link_status+0xb8/0x170 [i915]
[25707.631473] [<ffffffffa00b91a5>] intel_dp_hot_plug+0x15/0x20 [i915]
[25707.631484] [<ffffffffa008368e>] i915_hotplug_work_func+0x6e/0xa0 [i915]
[25707.631490] [<ffffffff81074dd5>] process_one_work+0x1b5/0x4d0
[25707.631494] [<ffffffff8107596f>] worker_thread+0x17f/0x470
[25707.631499] [<ffffffff810757f0>] ? manage_workers+0x310/0x310
[25707.631504] [<ffffffff8107a6f0>] kthread+0xc0/0xd0
[25707.631508] [<ffffffff8107a630>] ? kthread_stop+0x170/0x170
[25707.631515] [<ffffffff814c726c>] ret_from_fork+0x7c/0xb0
[25707.631519] [<ffffffff8107a630>] ? kthread_stop+0x170/0x170
[25707.631522] ---[ end trace 02a6580ca2d4b741 ]---
[25707.731197] ------------[ cut here ]------------
...
[28342.833741] [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal timeout (has irq: 1)!
[28342.833744] [drm:intel_dp_aux_ch] *ERROR* dp_aux_ch not done status 0xa015003f
[28342.850409] [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal timeout (has irq: 1)!I also have the feeling, that the issue is getting worse. In earlier kernel versions, I could switch to vt1 and back to X to get the screen working again. Today (3.9.4), if I dare to switch to vt1 and back to X, my screen loses the signal when returning to X.
Does anyone have any clues, what's going on?
Maybe this issue should be brought to the attention of the intel developers? If so, how would one go about this?
Offline
Some time ago I asked on #intel-gfx on freenode how to go about that problem back on kernel 3.7 I believe: they were aware of issues with DP priming and were working on it (if you dig around their bugtracker you might actually find some bug reports regarding this problem).
To be honest, I just gave up on getting this to work with every single kernel version. Sometimes it does, sometimes it doesn't. I mostly try to update the kernel + any intel-related packages (like intel-drm or xf86-video-intel) and check if xrandr works. Usually if xrandr fails to send an image to the monitor that's a pretty good sign that waking up from suspend or the like won't work either. :-) I simply downgrade to the kernel I know was working previously (3.9.3 at the moment).
Offline
I have the same problem with a Dell L502X Notebook and a Dell U2713HM.
This only happens on the Display Port without adapters.
When using DVI-D port witha mini DisplayPort connector the problem does not happens (but there is a need to lower the frequence to 40hz).
This also happens on Ubuntu 13.10 (for fuure reference).
-rsd
Offline
Oh, surprising to see that it is not a Lenovo specific problem, although most bug reports mention these machines.
I considered using an adapter, but never actually tried, as I don't have one around. But it's good to know that such a workaround exists.
Offline