** Changed in: linux (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/929635
Title:
[snb-m-gt2] Blank screen
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
Hey Mark,
The v3.3 kernel is now release. Can you test the 3.3 kernel before we
try to bisect the issue in 3.2? The kernel can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-precise/
** Tags added: regression-update
--
You received this bug notification because you
I don't get either error when I plug in a 1920 x 1200 display. Just
with 2048 x 1152.
I still can't use both if the external is plugged in at startup, but the
external does work each time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Joe,
Sorry for the slowness. I tested several times booting off an Oneiric
live USB and dual monitors works fine. No evidence of the
[drm:pch_irq_handler] or [drm:intel_cpt_verify_modeset] errors.
When I installed precise on January 27, dual monitor was working. I
would say the regression
Hi Mark,
That might indicate this bug exists upstream as well. Do you think you
could test some earlier kernels, such as Oneiric[0] or Lucid[1]? That
way we can see if this is a regression.
[0] https://launchpad.net/~canonical-kernel-team/+archive/ppa/+build/3126697
[1]
Hi Mark,
Do you think you could test the latest mainline kernel? If so, you can get it
from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc5-precise/
There is some information on the topic of testing the mainline kernel at:
https://wiki.ubuntu.com/KernelMainlineBuilds
** Tags added:
I've done three boots so far with this kernel. All three times the
second display came on. It still always shows the PCH poison
interrupt error, but not the pipe 0 stuck error you get when the
external display goes black. You still can't enable the laptop display
after attaching the external.
I take it back. I've seen failures now. Same two errors. I also tried
with the display connected from boot, which looked good all the way
through lightdm, but it went black when x loaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Package changed: xserver-xorg-video-intel (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Bryce,
Just got back home to my external display. Here are my results so far using
the kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-fixes/current/ (uname
-r = 3.3.0-994-generic).
Steps: boot all the way to Unity desktop, plug in external display,
observe.
Try 1:
** Tags added: dual-head
** Tags added: black-screen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/929635
Title:
[snb-m-gt2] Blank screen after login with dual monitor
To manage notifications
Hi Mark,
There have been several sandybridge fixes upstream. Could you test the
latest drm-intel-fixes kernel? You can install it from the kernel
team's PPA: kernel.ubuntu.com/~kernel-ppa/mainline/ Unfortunately that
PPA is offline at the moment but should be back online by the end of the
13 matches
Mail list logo
