The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: linux (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
I didn't mean to insult you. But unless we can reproduce or have someone to
test latest kernel it is useless to let this entry open.
So, it is WORKSFORME until we find a tester for it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
(In reply to Rodrigo Vivi from comment #34)
> Since the error reported cannot be reproduced anymore by reporter of reopen
> let's close this as invalid.
> Anyone able to reproduce again it feel free to re-reopen. But remind to test
> on latest drm-intel-nightly.
Well, it's still an issue. I just n
** Changed in: xorg-server
Status: Confirmed => Invalid
--
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/1021924
Title:
8086:0162 [Intel DQ77MK] Multiple Displays not working
Statu
Since the error reported cannot be reproduced anymore by reporter of reopen
let's close this as invalid.
Anyone able to reproduce again it feel free to re-reopen. But remind to test on
latest drm-intel-nightly.
--
You received this bug notification because you are a member of Kernel
Packages, w
This is still an issue as of 2014-06-20 on 3.13.0-29-generic in Ubuntu
14.04, however I have now upgraded to a single 4K monitor and a Haswell
CPU, so I won't be able to test any further possible fixes for this
issue.
One thing of note though, is that when X came up on 3.13.0-29, the
second monito
Yes, the bug is still present in 14.04 on kernel 3.13.0-29-generic.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1021
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is s
** Changed in: xorg-server
Status: Incomplete => Confirmed
--
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/1021924
Title:
8086:0162 [Intel DQ77MK] Multiple Displays not working
St
Created attachment 93418
dmesg|grep drm output for drm.debug=0xe on 2014-02-04
Here is a drm.debug log with the 3.13.0-6-generic kernel in Ubuntu
Trusty. It includes all the drm output from the boot command up to the
second display failure when lightdm comes up, another failure for the
display to
** Changed in: xorg-server
Status: Confirmed => Incomplete
--
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/1021924
Title:
8086:0162 [Intel DQ77MK] Multiple Displays not working
St
Can you please attach a new dmesg when trying to set up the output
configuration on 3.13? Please boot with drm.debug=0xe.
Also please do the manual xrandr dance which makes things work and again
grab the complete dmesg. You might need to increase the dmesg buffer
with log_buf_len if messages start
After getting the second monitor working properly with xrandr faffing,
the settings do not stick after a reboot, unfortunately.
How can I get it to work correctly by default, every time?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
Playing with xrandr some more, I have gotten "xrandr --output HDMI1
--crtc 0 --output HDMI3 --crtc 2 --right-of HDMI1" to work. I can use
both screens at full resolution, with this command. I don't know if it
will stick after a reboot, but I will comment here as soon as I do
reboot.
--
You receiv
Now running 3.13.0-1 on Ubuntu, and second display still not working,
and no link train errors in dmesg.
Second screen remains black. I can use both screens only when I set them
to an extremely low resolution of 1280x800 each. Any higher resolution,
and the second screen remains black.
If I run "
** Tags added: trusty
--
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/1021924
Title:
8086:0162 [Intel DQ77MK] Multiple Displays not working
Status in X.Org X server:
Confirmed
Status i
(In reply to comment #24)
> Now we find ourselves without uptodate information on what your bug is, so
> please do attach the full dmesg from the failure case.
Rodney, please post the full dmesg from the failure case. Since plenty
of time has passed, please use a later kernel. Thanks.
--
You rec
(In reply to comment #26)
> Rodney, please post the full dmesg from the failure case. Since plenty of
> time has passed, please use a later kernel. Thanks.
I've just upgraded the machine to Ubuntu Trusty development series,
which has kernel 3.12.0-7.15. The second display is still blank, but
there
Christopher, no, making the assumption that something may be "fixed" by
a BIOS update, which contains no documentation relevant to the issue, is
exactly that; an assumption. There is no evidence that suggests a BIOS
update would fix something that is not documented in the release notes
for the upda
Rodney Dawes, as you may know, and previously documented to you, not
everything that is addressed in a BIOS update has a comment to it. As
well, the notes don't make comments to the results of testing in linux.
Hence, one wouldn't know if this would have an impact or not, as one
hasn't updated it y
Christopher, while I appreciate your passion for triaging bugs, and
wishing to strictly adhere to process or protocol, a BIOS update that
will not fix anything is unnecessary, and a waste of time. One can
easily see by looking at the release notes of the BIOS update that it
will not affect this iss
Rodney Dawes, this BIOS update would still need to occur. For more on
this, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of
Christopher, must I really waste our time by updating the BIOS every
time a fix for the Q77 chip set comes out? It's a pain to do the BIOS
update, and it's a pain to test this bug specifically, because it
requires several reboots and shifting cables behind a rack.
If you read the Release Notes for
Rodney Dawes, as per
https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Desktop+Boards&ProductLine=Intel%C2%AE+7+Series+Chipset+Boards&ProductProduct=Intel%C2%AE+Desktop+Board+DQ77MK
an update is available for your BIOS (0064). If you update to this
following https://help.ubu
I've removed the i386 tag as well as the tag for requesting test on an
older kernel than is currently available. I was running 12.04 32-bit
when originally filing this bug, but have long since upgraded to a
64-bit only system, after installing a new hard drive.
** Tags removed: i386 kernel-reques
This is still an issue, even on the 13.10 RC kernel:
$: dmesg|grep link_train && uname -r
[9.766419] [drm:ivb_manual_fdi_link_train] *ERROR* FDI train 1 fail!
[9.768562] [drm:ivb_manual_fdi_link_train] *ERROR* FDI train 2 fail!
[ 118.902507] [drm:ivb_manual_fdi_link_train] *ERROR* FDI tra
Given the number of bugs that the Kernel Team receives during any
development cycle it is impossible for us to review them all. Therefore,
we occasionally resort to using automated bots to request further
testing. This is such a request.
We are approaching release and would like to confirm if this
The BIOS update rev 0061 lists no changes in its release notes file,
that would be potentially related to this issue.
--
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/1021924
Title:
8086:0
** Tags removed: latest-bios-0060
** Tags added: bios-outdated-0061
** Tags removed: kernel-unable-to-test-upstream
--
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/1021924
Title:
8086:01
I have upgraded to a new version of Ubuntu now, which is using 3.10.0-6,
as well as the latest version of the BIOS for this board, from Intel.
The second screen is completely red, and link train errors are
occurring:
: dmesg|grep drm
[7.281683] [drm] Initialized drm 1.1.0 20060810
[7.33615
Considering that the only failure in the previous dmesg was the FDI link
failure, and that implies the displays would be blank, that it was fixed
it was natural for to presume the bug was fixed.
Now we find ourselves without uptodate information on what your bug is,
so please do attach the full dm
** Tags added: needs-upstream-testing quantal raring rls-q-notfixing
--
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/1021924
Title:
8086:0162 [Intel DQ77MK] Multiple Displays not working
I've also removed the Quantal and Raring tasks, as they are non-LTS
releases, and I don't see the chance of this being fixed in them because
of that.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
Is there a specific version I should test? I see 3.11-rc5 mentioned, but
3.11.0-1-generic was installed as an update when I did a dist-upgrade
earlier today, and the bug is still present there. Given that, I would
also expect the bug to be present in upstream 3.11-rc5.
Also, this is not trivial to
Rodney Dawes, could you please test the latest upstream kernel available
following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow
additional upstream developers to examine the issue. Please do not test the
daily folder, but the one all the way at the bottom. Once you've tested the
The BIOS update did not help. Here is the new information:
MKQ7710H.86A.0060.2013.0618.1012
06/18/2013
I am now also running on Ubuntu Saucy 13.10, with kernel
3.10.0-6-generic.
The second display is entirely red, and the fdi link train failures are
still occurring:
[ 57.936050] [drm:ivb_manu
Rodney Dawes, as per
https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Desktop+Boards&ProductLine=Intel%C2%AE+7+Series+Chipset+Boards&ProductProduct=Intel%C2%AE+Desktop+Board+DQ77MK
an update is available for your BIOS (0060). If you update to this, does
it change anything?
37 matches
Mail list logo
