I was stung by this using the Mesa driver.
I concur that it should be a dependency of libgl1-mesa-dri instead of
recommended, unless there is some downside to it that I can't see. I'm not a 3d
drivers expert.
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You
@Kai-Heng I'm running that now it seems to be working well:
$ uname -a
Linux giacomo-awin-latitude 4.4.0-100-generic #123-Ubuntu SMP Thu Nov 2
10:16:13 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
I see many changes in the changelog, what's the patch that fixed it?
--
You received this bug
@Kai-Heng thanks a lot, using the modesetting driver helped!
I just read that using the Intel driver is not recommended anymore on newer
systems, I didn't know that.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in
@Kai-Heng: the problem is fixed here using your 4.4.0-99 version on my Dell
Latitude E7470 with Skylake.
Well it's buggy like on 4.4.0-72, after loggin both screens go black, but I
have my workaround works again. If I switch to text mode (Ctrl+Alt+F1) and back
(Alt+F7) both screens work
--
Sorry for the delay, I tried:
linux-image-4.4.0-83-generic doesn't work
linux-image-4.8.0-040800-generic doesn't work
linux-image-4.10.0-041000-generic works
linux-image-4.11.0-041100-generic works
By the way, I didn't mention is that even the kernel versions that work are far
from perfect.
@Kai-Heng I use a Dell E-Port Plus.
This is my ouput of lsmod | grep i915:
i915_bpo 1302528 5
intel_ips 20480 1 i915_bpo
i2c_algo_bit 16384 1 i915_bpo
drm_kms_helper155648 1 i915_bpo
drm 364544 6 i915_bpo,drm_kms_helper
video
Version 4.4.0-72-generic seems to be the last version that works for
everyone here, on different systems. I renamed this bug to mention
Intel, but Shay Perlstein above had the same problem on NVidia.
@Kai-Heng could it be the same bug even if on different graphic drivers? Do you
know if there is
The problem is only reproducible with some Kernel versions, how can it not be
related to the Kernel?
I actually have a Sky Lake, not a Haswell like the reporter.
So maybe one of those commits for Baytrail caused a regression on other Intel
Graphics processors?
Another culprit seems to be Dell
@kaihengfeng this is my output of that command:
~ $ dpkg -l | grep linux-image
hi linux-image-4.4.0-72-generic 4.4.0-72.93
amd64Linux kernel image for version 4.4.0 on 64
bit x86 SMP
ii linux-image-4.4.0-78-generic
** Summary changed:
- External monitor connecting problem
+ External monitor connecting problem on Intel graphics card
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1686189
I have this problem since linux-image-4.4.0-75
linux-image-4.4.0-77 is also affected.
linux-image-4.4.0-72 works
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
@naveenkumarmula do you mind trying to boot with the previous kernel
version and see if that fixes it for you too? You should be able to
choose the Kernel to start at boot.
Btw I'm also on Intel graphics
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Sorry for spamming everyone, as this started happening after a kernel
upgrade is it a Kernel bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1686189
Title:
External
I have the same problem on 16.04.2 Xenial since upgrading the Kernel to
4.4.0-75 yesterday.
Booting the the older kernel version 4.4.0-72-generic seems to be a workaround.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg
14 matches
Mail list logo
