[Kernel-packages] [Bug 1520751] Re: Kernel 4.2 does not detect external monitor

2015-12-17 Thread David Abergel
Okay, I tested the daily build of xenial (ubuntu version) this morning. It is using kernel 4.3.0-2, and I can confirm that this detects the monitor without problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://b

[Kernel-packages] [Bug 1520751] Re: Kernel 4.2 does not detect external monitor

2015-12-16 Thread David Abergel
You mean upgrade to the whole distribution or just the kernel? This issue is happening on my main work laptop so I need reasonable stability so I'm not sure I want to use a pre-alpha distro. I think for now I am fine using the mainline 4.3 kernel which works fine, or the 4.2.0-rc8 one which I comp

[Kernel-packages] [Bug 1520751] Re: Kernel 4.2 does not detect external monitor

2015-12-15 Thread David Abergel
Christopher, I have finished the bisection (man, that took a long time!) and I have attached the output. The summary is that commit 4efa83c8c786ab7ec7982e3dd348cb7e7ecbeb04 is the one that fixes things. This makes sense because I am attaching my external monitor via a DP->VGA dongle, mentioned in

[Kernel-packages] [Bug 1520751] Re: Kernel 4.2 does not detect external monitor

2015-12-08 Thread David Abergel
Dear Christopher, I updated the BIOS today. Ouput from the command you requested is: $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date [password] A07 11/11/2015 The problem persists, so I have marked this as Confirmed, per your request. As I stated in the initial post, the

[Kernel-packages] [Bug 1520751] Re: Kernel 4.2 does not detect external monitor

2015-12-02 Thread David Abergel
Dear Christopher, Thank you for the suggestion. Unfortunately, I won't be able to do this for at least a week because Real Lifeā„¢ is too busy. (Also, I've not updated a BIOS before so I am cautious about the idea.) But if I can do it some time in the next week or two I shall update the bug. Cheer

[Kernel-packages] [Bug 1518976] Re: miniDisplay VGA adapter doesn't work after switching to 4.2 kernel

2015-11-28 Thread David Abergel
Done, see here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520751 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1518976 Title: miniDisplay VGA adapter doesn't work after swi

[Kernel-packages] [Bug 1517465] Re: Resolution too low on external monitor through Intel graphics, reversion in 4.x kernel

2015-11-28 Thread David Abergel
Done, please see here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520751 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1517465 Title: Resolution too low on external monitor

[Kernel-packages] [Bug 1520751] [NEW] Kernel 4.2 does not detect external monitor

2015-11-28 Thread David Abergel
Public bug reported: On xubuntu 15.10. Kernel version 4.2.0-18-generic x86_64 does not detect an external monitor when it is connected via the minidisplay port. Using xrandr, I can force output to the monitor, but the maximum resolution is 1024x768 (I think). Hardware is a Dell XPS 13. Upgrading

[Kernel-packages] [Bug 1518976] Re: miniDisplay VGA adapter doesn't work after switching to 4.2 kernel

2015-11-26 Thread David Abergel
I was having a problem rather similar to this (although on different hardware). I found that installing a 4.3.xx version kernel from the mainline builds described above fixed the problem. (Miraculously, I don't think it broke anything else either!) -- You received this bug notification because y

[Kernel-packages] [Bug 1517465] Re: Resolution too low on external monitor through Intel graphics, reversion in 4.x kernel

2015-11-26 Thread David Abergel
I was having a problem rather similar to this (although on different hardware). I found that installing a 4.3.xx version kernel from the mainline builds described above fixed the problem. (Miraculously, I don't think it broke anything else either!) -- You received this bug notification because y