You are not logged in.
Since a few intel driver updates my HDMI monitor which is plugged in to my docking station for my thinkpad x250 is not recognised anymore. xrandr doesn't show the monitor as connected. This is the output of dmesg while inserting the notebook in the dockingstation.
[32817.865296] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[32818.567240] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[32819.267831] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[32819.968678] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[32819.969169] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to train DP, aborting
[32819.973320] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns
[32820.660183] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[32821.362693] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[32822.062872] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[32822.763883] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[32823.464664] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[32824.165652] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[32824.866331] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[32824.866822] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to train DP, aborting
[32824.870974] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns
When I plug in the monitor directly everything works. So ether my docking station is broken or the driver has some problems.
Does anyone have similar issues?
Last edited by XenGi (2020-07-18 00:25:27)
# got root?█
Offline
Hi,
I had the same problem on Latitude E7270, running Manjaro (linux 4.4.7) from microSD.
After a deep search, I found some Gentoo user comments reporting this issue came from within the kernel (patch or downgrade would solve it apparently)
I upgraded to Linux 4.7 and everything is working now.
Sorry for mentioning both Manjaro ang Gentoo on my first post down here.
I have read the README: Forum Rules, and even though I am a proud Arch Linux user, I sometimes like to get stupid and install Manjaro.
Offline
I upgraded to Linux 4.7 and everything is working now.
I haven't tried it after upgrading to 4.7.1 but I will do that tonight. Maybe the problem is fixed with my setup too. Would be nice to finally use my dock again.
Sorry for mentioning both Manjaro ang Gentoo on my first post down here.
I don't see why this would be a problem and if it is one then could someone maybe explain that to me? All (most) Linux distros have their place and purpose. I would always use Archlinux on a desktop but Debian on a server or Gentoo for highly specialized things. But that's just my favorite mix of Linux flavors. I always thought the Arch community isn't involved in any distro wars. That's why I like it so much.
# got root?█
Offline
What monitor are you trying to drive from the Thinkpad docking station?
are you aware that their is some known issues with earlier 27" monitors that support 1080p+ resolutions, ?
I had similar issues regarding voltage, turned out it was the monitor cable for example the HP ZR2740w which is 2560 x 1440 at 60Hz, it only does that resolution or 720p, it would only work with a mini displayport cable directly from the laptop
http://h20564.www2.hp.com/hpsc/doc/publ … -c03350168
http://www.ebay.com/itm/NEW-HP-Inc-7298 … SwcLxYHRhr
How many monitors do you run off your x250?
Offline
I have connected just one 1080p monitor to it via HDMI.
And it used to work so I don't think it's a problem with the monitor. Probably a new error Intel introduced in the graphics driver. They do this all the time.
Still couldn't find time to test if it working again. Now I'm running 4.8.17, so it probably works again.
# got root?█
Offline