Created attachment 136748 [details] Xrandr verbose output Running Ubuntu 17.10, my machine has two external displays which are shown as DP-1 and eDP-1 in xrandr (verbose output attached). Both monitors display correctly for the BIOS and initial purple screen before the Ubuntu splash. Additionally, the same is true various using liveUSB sticks, the monitor displays correctly until the OS boot splash. Once the Ubuntu loading screen begins, the display becomes corrupted. This is true using both Xserver and Wayland on Ubuntu 17.10.
Created attachment 136749 [details] Dmesg output Dmesg output
Created attachment 136750 [details] Xorg output
Created attachment 136751 [details] DP-1 displaying correctly
Created attachment 136752 [details] eDP-1 corrupted display under Wayland (monitor still partially functional)
Created attachment 136753 [details] eDP-1 corrupted display under Xserver (monitor not functional)
Hardware is Haswell 4010U with Intel Graphics 4400. Dual display functions correctly on Win10, but not on any of several Linux distros attempted.
Hello Rory, could you please attach dmesg with debug information, drm.debug=0xe parameter on grub. Thanks.
Created attachment 136776 [details] Dmesg with drm.debug=0xe grub parameter Hi Elizabeth, Thank you for looking at this. Attached should be dmesg with drm.debug=0xe flag set by editing /etc/default/grub. If this is not the correct way to set the flag let me know and I will correct. Rory
Created attachment 136778 [details] dmesg with drm debug output Apologies, update-grub command not run for previous dmesg output. Updated output attached.
Comment on attachment 136776 [details] Dmesg with drm.debug=0xe grub parameter Please disregard this output
If you have the opportunity could you reproduce with this branch https://cgit.freedesktop.org/drm-tip and attach dmesg with debug information with it. Thanks again.
Also when attaching new logs, you can mark as obsoletes the old logs.
Created attachment 136781 [details] Kernel 4.15.0-rc8 dmesg Hi, the attached should be the debug output built using the drm-tip branch.
(In reply to Rory O'Siochain from comment #0) > Running Ubuntu 17.10, my machine has two external displays which are shown > as DP-1 and eDP-1 in xrandr (verbose output attached). What machine is this? eDP is supposed to be the local flat panel of a laptop, not an external display.
Created attachment 136849 [details] attachment-24966-0.html This machine is an all in one device for use as a point of sale. It has both front and rear facing monitors. The monitors connect directly to the motherboard and not externally - apologies if my description was incorrect/confusing. Both monitors function correctly running Windows and upon initial boot, so it doesn't seem to be an invalid configuration. > On 19 Jan 2018, at 15:14, bugzilla-daemon@freedesktop.org wrote: > > > Comment # 14 <https://bugs.freedesktop.org/show_bug.cgi?id=104653#c14> on bug 104653 <https://bugs.freedesktop.org/show_bug.cgi?id=104653> from Jani Nikula <mailto:jani.nikula@intel.com> > (In reply to Rory O'Siochain from comment #0 <x-msg://4/show_bug.cgi?id=104653#c0>) > > Running Ubuntu 17.10, my machine has two external displays which are shown > > as DP-1 and eDP-1 in xrandr (verbose output attached). > > What machine is this? eDP is supposed to be the local flat panel of a laptop, > not an external display. > > You are receiving this mail because: > You reported the bug. > You are on the CC list for the bug.
Hi, would anyone be able to point me in the right direction in terms of getting this resolved? I'm not familiar with the kernel but if someone could point me in the right direction, I can look to put a patch together myself? Many thanks, Rory
So there's nothing out of the ordinary in the dmesg. I can't make heads or tails about the pictures of the corrupted output. Some ideas, try them separately: Please attach /sys/kernel/debug/dri/0/i915_vbt. Please disable DP-1 and see if that makes a difference on eDP-1. Please try booting with i915.fastboot=1. Does it work until the first modeset? Does it fail after the first modeset? Do you have i915 built into the kernel? Can you try it as a module?
First of all. Sorry about spam. This is mass update for our bugs. Sorry if you feel this annoying but with this trying to understand if bug still valid or not. If bug investigation still in progress, please ignore this and I apologize! If you think this is not anymore valid, please comment to the bug that can be closed. If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Closing, please re-open if still occurs.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.