I have tried this screen and machine with 3.6 and so far it seems to be
working.
Martin
On Oct 22, 2012 1:30 AM, bugzilla-dae...@freedesktop.org wrote:
Chris Wilson ch...@chris-wilson.co.uk changed bug
45211https://bugs.freedesktop.org/show_bug.cgi?id=45211
What Removed Added Status
I haven't seen this problem with the standard precise kernels for several
months. ok to close.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/906086
Title:
[arrandale]
I haven't seen it recently.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/752157
Title:
[RS880] graphical corruption in launcher (Solid grey rectangles over
icon text and
On Ubuntu's current kernel (3.2.0-20-generic #32-Ubuntu SMP Thu Mar 22
02:22:46 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux), the behaviour is:
* after booting, the machine comes up ok to the lightdm screen, and after
logging in it restores the previous configuration correctly, ie external
monitor
Hi Bryce,
I have other external-monitor problems (bug 745112) but I haven't seen
an oops for a while.
status invalid
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is
That comment was on the upstream bug, Launchpad just forwarded it to you
;)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/745112
Title:
[arrandale] desktop is messed up
Using the current kernel from Precise, which is supposed to have the
latest patches, my external monitor works if audio is forced off using
xrandr, but fails if audio is left in auto mode. So, reopening.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Current status in Precise seems to be:
- works reliably with ` xrandr --output DP1 --mode 2560x1600 --set audio off`
- fairly reliably **does not** work if I set the external monitor direct to
2560x1600 from the monitors control panel, I'm guessing because that does auto
audio and gets it
** Attachment added: /
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/745112/+attachment/2777170/+files/20120224-kern.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
This is definitely improved but not fixed. Most of the time the
external monitor comes up ok, but sometimes when I switch a running
session on to the external monitor it stays irretrievably blank. Here's
a kernel log with debugging on of those transitions.
I have not yet worked out the pattern
Thanks, Leann.
I have just tried 3.2.0-16.25 and it's not completely working, the
external monitor is still black at high resolutions. I'll investigate
some more.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
One apparently regression in 3.2.0-16.25 (maybe unconnected to this
change?) is that fn-f7 does not seem to have any effect. It was working
on the previous kernel I tried, both the Ubuntu ones and my own builds.
Turning on the external screen with xrandr does work:
xrandr --output DP1 --mode
Just to be clear: forcing audio off every time the external display is
configured, by using xrandr ... --set audio off, does make it work
reliably every time so far.
What I tested previously, and what did not work to turn it off just once
and then use the system's normal configuration method (eg
the current tip of drm-intel-fixes does seem to have this fixed (but
drm-intel-next-fixes does not)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/745112
Title:
[arrandale]
so perhaps the fix for https://bugs.freedesktop.org/show_bug.cgi?id=44881
c898261c0dad617f0f1080bedc02d507a2fcfb92
will also fix this...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
Ogasawara's build http://people.canonical.com/~ogasawara/fdo44881/amd64/cmt3/
from bug 44881 is only partly working for me: the external monitor does come
up, but only at 1600x1200 and xrandr shows
mbp@joy% xrandr
xrandr: Failed to get
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/2012-01-05-precise/linux-image-3.2.0-997-generic_3.2.0-997.201201050433_amd64.deb
does seem to work correctly.
I'm going to try what I think is the right patch applied to the precise
kernel.
--
You received this bug notification
I built Ubuntu-3.2.0-15.24
from git://kernel.ubuntu.com/ubuntu/ubuntu-precise.git plus
https://git.kernel.org/?p=linux/kernel/git/keithp/linux.git;a=commitdiff;h=c898261c0dad617f0f1080bedc02d507a2fcfb92
and that does seem to fix the problem, hooray. Maybe that one fix can be
cherrypicked into
Here's an attempted backport of that patch to the oneiric kernel; not
tested yet.
** Patch added: 2012-02-09-intel-dp-oneiric.diff
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/745112/+attachment/2725463/+files/2012-02-09-intel-dp-oneiric.diff
--
You received this
on precise,
http://people.canonical.com/~ogasawara/fdo44881/amd64/cmt3/ does seem
to be working correctly
on oneiric's kernel, https://bugs.launchpad.net/ubuntu/+source/xserver-
xorg-video-intel/+bug/745112/+attachment/2725463/+files/2012-02-09
-intel-dp-oneiric.diff seems to fix it, and there is
The problem i describe in
https://bugs.freedesktop.org/show_bug.cgi?id=45211#c16, coming up with
only a restricted set of resolutions available, seems connected to
booting in 'recovery' mode and then proceeding to a normal desktop.
Leaving that aside, with the one patch from
Now that I know not to use recovery mode (which might be a separate less
important bug),
http://people.canonical.com/~ogasawara/fdo44881/amd64/cmt3/ does work
for me.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
And https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/745112/+attachment/2725463/+files/2012-02-09-intel-dp-
oneiric.diff looks like it works as a (not quite trivial) backport of
the fix to 3.0.17.
--
You received this bug notification because you are a member of Ubuntu-X,
I tried the current tip of drm-intel-next-fixes
(44306ab302687b519a31aa498b954c1e26f95a6b) and it has the same problem.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/745112
It seems like if I force audio off at the same time I add the external
screen, through xrandr, it does work reliably(?) so far. Using the
monitor control panel or fn-f7 apparently puts audio back to the 'auto'
setting, which does induce a problem
I tried running
for i in `seq 30` ;do; echo i
Running
xrandr --output DP1 --mode 2560x1600 --above LVDS1 --set audio on
when it's previously working does immediately make the monitor black
out, and using '--set audio off' does not bring it back, nor does soft
power cycling the monitor or unplugging/replugging it.
I can see some reports of
I've tried, as a bit of a shot in the dark, cutting out one bit of code
that seems to try to enable the audio pipe, and this does not seem to be
enough to make it reliable when the display is configured automatically.
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
I tried a couple of variations on that patch to try to force dp audio
off, with no success. If someone gives me a patch or an idea on where
to start I'm happy to try it.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel
xrandr --output DP1 --set audio off
looks good:
I plugged my laptop into the dock, and it came up at the medium
resolution it was running at earlier in the day. I ran that command,
and the screen blanked briefly, I guess while the dp link was
reestablished. I then used the displays panel to
Hitting Fn-F7 a few more times, I still have the blank screen problem,
and turning dp audio off again does not fix it.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/745112
it looks like bugs.freedesktop.org is down at the moment, so I'll attach
them in lp.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/745112
Title:
[arrandale] desktop is
lspci -vvnn output
** Attachment added: x201-lspci.txt
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/745112/+attachment/2700631/+files/x201-lspci.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
xrandr --verbose output
** Attachment added: x201-dell30-xrandr.txt
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/745112/+attachment/2700632/+files/x201-dell30-xrandr.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is
This kernel log shows it:
* initially coming up in mirrored mode, successfully
* trying to set it to 2560x1600 and having the external monitor blank
* then gradually stepping up the external monitor to 1920x1080 (where it
works) and then 1920x1200 (where it doesn't work)
** Attachment added:
Hi, here is the requested information:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/745112/+attachment/2700631/+files/x201-lspci.txt
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/745112/+attachment/2700632/+files/x201-dell30-xrandr.txt
On 25 January 2012 17:42, Daniel-ffwll 906...@bugs.launchpad.net wrote:
Just to check: the patch _does_ get rid of the oops?
I haven't seen it since running that patch for a few days, with
several disconnect/reconnect cycles. It was never 100% reproducible.
For the blank screen issue: Please
** Bug watch added: freedesktop.org Bugzilla #45211
https://bugs.freedesktop.org/show_bug.cgi?id=45211
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/906086
Title:
Sent upstream in https://bugs.freedesktop.org/show_bug.cgi?id=45211
(Please attach that to this bug if you can work out how...)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
Current Precise still has this bug. I also tried with the current drm-
intel-next kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline
/drm-intel-next/2012-01-05-precise/ and I had the same problem.
Bug 906086 is about a kernel oops when trying to use the external
display. I have not seen
Hi Daniel,
With this patch applied, and 'slub_debug' on the kernel command line, I
get the same problem I was previously: no oops, but the external screen
is blank or can't sync.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
OK, I'll try that.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/906086
Title:
[arrandale] kernel OOPS setting external monitor to a higher
resolution
To manage
/home/mbp/build/linux/ubuntu-precise/drivers/gpu/drm/i915/i915_gem.c: In
function ‘i915_gem_create’:
/home/mbp/build/linux/ubuntu-precise/drivers/gpu/drm/i915/i915_gem.c:210:19:
error: ‘dev_priv’ undeclared (first use in this function)
You are missing one declaration of dev_priv, around line 205. With that
fixed, it does build on the Ubuntu kernel. I'm going to test it with
slub_debug.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
On 18 January 2012 20:04, Bryce Harrington 906...@bugs.launchpad.net wrote:
Hi Martin, did RAOF resolve this for you at the rally? If not, I can
work on it a bit for you.
No, he helped with some other bugs but not this. It needs a high-res
external monitor to reproduce it and we didn't have
Public bug reported:
I have a thinkpad x201 with intel graphics. I experienced intermittent
but frequent multi-second lags in X input, both keys and mouse on
precise, using both the standard xorg and also the current one from the
x-staging ppa. With help from raof, I discovered that turning off
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/914216
Title:
arrandale xorg very laggy when Intel vt-d is enabled
To manage notifications about this bug go to:
Sadly it is still failing in Precise. It is fairly reliable at lower
resolutions but rarely works at full resolution. I will have the laptop
(but obviously not the 30in monitor!) at the rally if you want to have a
lok.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete =
Public bug reported:
Following on from bug 745112 but on precise - similar but different
symptoms so a separate bug.
With an external monitor connected through the doc displayport of a
thinkpad x201, running current precise:
* the internal screen looks ok
* if I use the display control panel
** Attachment added: IMG_20111215_201557.jpg
https://bugs.launchpad.net/bugs/906086/+attachment/2638773/+files/IMG_20111215_201557.jpg
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/906086
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/906086 for similar
but different problems on precise.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/745112
Title:
This was failing consistently, but it just worked now. Perhaps it is
fixed in the latest updates.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/906086
Title:
[arrandale] crashes setting
With today's updates I also had things just come up and work in the
correct resolution. I hope it lasts.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/745112
Title:
chipaca suggested I could packages of that kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/
with Linux joy 3.1.0-997-generic #20170422 from there, I get the
same behaviour I described in comment#110.
--
You received this bug notification because you are a member of
steve langasek says
BTW, your Arrandale DisplayPort issues are probably fixed in the
drm-intel-next tree, given that Keith has been working on these exact issues
recently. You might want to give this kernel a try:
git://people.freedesktop.org/~keithp/linux drm-intel-next
(AFAIK we don't
OK, so kernel 3.2.0-030200rc1 seems to consistently behave like this:
* boot up an x201 docked with dp connected to an external monitor
* grub appears on both screens
* plymouth appears on both screens
* lightdm appears on both screens in low-res mirrored mode
* unity session comes up with
I tested with 3.2.0-030200rc1, and external displayport seems roughly
equally broken there: if I boot up the laptop with it connected it
usually works; if I try to connect it afterwards it generally doesn't
work.
vga seems to work reasonably well through either the directly onboard
vga or through
As of today, it sometimes works, but it's hard to characterize when it
does and when it does not. Generally speaking docking the laptop while
it's powered on is problematic.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
As of current oneiric, external displays on this machine seem totally
broken, even if the machine is booted up with the display attached:
worse than a week ago.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
Current oneiric seems pretty consistent: if the external monitor is
connected when the machine is turned on or comes back from suspend, it
works. If the machine is inserted in to the dock while powered on, and
then the external display is activated, it doesn't set the right mode
and it does not
This bug, or one a lot like it, seems to have regressed on oneiric
(3.0.0-11). If I boot up my x201 with the external monitor connected,
it normally but not always works. When it comes back from the
screensaver, normally the external screen will be blank but switching to
vt1 and back does get
I also have not seen this for a month or more.
On Sep 14, 2011 1:36 AM, Jay Taoko 752...@bugs.launchpad.net wrote:
This was a driver bug. I can't reproduce it on Oneiric for at least 2
months now.
** Changed in: unity
Status: Confirmed = Invalid
--
You received this bug notification
One more thing, which also worked ok before: after coming back from
resume, there is out-of-sync noise on the external monitor. Switching
to vt1 and back fixes it, which suggests to me it's also mode-setting
related.
--
You received this bug notification because you are a member of Ubuntu-X,
One remaining problem with Timo's kernel is that Fn-F7 does not work,
which amongst other things means if the laptop ever gets confused with
the internal display off there is no escape other than hard-rebooting.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
One other issue (though it might be compiz rather than the kernel) is
that after ejecting and then re-docking I'm left with a screen that's
totally blank aside from a mouse cursor. The cursor moves with the
mouse and it actually changes shape from arrow to I-bar to finger as I
move around,
The black-screen issue has happened more than once, but I don't yet know
how to consistently reproduce it. It is different to (though maybe
related) to the other issue seen where some regions of the screen aren't
drawn correctly.
--
You received this bug notification because you are a member of
It worked perfectly in previous Ubuntu releases.
It's also worked in some of the kernel I've tried in the course of
trying to localize this bug.
** Summary changed:
- [arrandale] desktop is messed up (goes black) when laptop is docked with two
external 1920x1200 monitors (x86_64)
+
Using Timo's linux-image-2.6.38-10-generic_2.6.38-10.44sru1_amd64.deb,
with my regular external monitor mentioned above: so far so good.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
I tried this on my x201 against an Optoma projector and it seems to
basically work. (I'm not at home with my monitor at the moment.)
I do see the black areas but I agree that's likely a unity thing, or at
least not a modesetting bug.
Fn-F7 does not work.
--
You received this bug notification
That package does have the drawback that suspend/resume is broken: the
machine sits there with the screen (or both screens) off, and
unresponsive to keyboard input. This was working correctly in the
stock natty packages.
--
You received this bug notification because you are a member of
7f58aabc369014fda3a4a33604ba0a1b63b941ac shows some flickering on the
external monitor when first logging in to metacity/classic, but it does
work reliably in all modes.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
6ee3b5a12740eddc5a76e130b6cc7cc64468d1f7 also seems ok, and according to
git bisect that might be the patch that fixes it. From the description
it seems somewhat plausible. I am going to try one of the parent
revisions too and see if they reliably break.
On f0c8602 which is the immediate parent of this revision, when I boot
with an external screen attached, I don't see any display on the
internal panel, and it doesn't show up in the monitors control panel.
That's the same breakage I described affecting rc1 in comment 57. So
this is at least one
Ubuntu-2.6.38-9.43-8-g930a188 from that branch seems to work well for
me, thanks!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/745112
Title:
[arrandale] desktop is messed
I spoke a bit too soon.
Timo's branch is a bit better in that the external display works, but
not quite right. Some observations:
* booting with the external display connected shows the boot and login screens
on both, and then my session comes up only on the external display
* I can use the
If you want me to test anything else, or bisect between two particular
points, let me know.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/745112
Title:
[arrandale] desktop
I put an amd64 package of that branch into
http://sourcefrog.net/tmp/1y/745112/ in case other people want to try
it.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/745112
tjaalton and bryceh suggested bisecting using the packages built from
mainline rather than building from scratch.
Using http://kernel.ubuntu.com/~kernel-ppa/mainline/
v2.6.39-rc1-natty when the external monitor is plugged in will _only_
use the external monitor; the monitors control panel
and rc3 also seems ok.
I will try again on a bisect between rc1 and rc3.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/745112
Title:
[arrandale] desktop is messed up (goes
rc4 shows some visual corruption after resume from suspend, which can be
cleared off by going to vt1 and back.
git bisect start v2.6.39-rc1 v2.6.39-rc4 drivers/gpu/drm
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
The fix seems to be prior to upstream
9bb09fa1b5b07459279301ac6220d575f307597b
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/745112
Title:
[arrandale] desktop is messed up
I tested with Oneiric's kernel http://packages.ubuntu.com/oneiric/linux-
image-2.6.39-3-generic running natty userspace, and so far it seems to
be working ok in either internal, external, or mirrored mode. In side-
by-side mode I have trouble with regions of the screen appearing black
but I
From Bryce's #29, I tested acelan's kernel from
http://people.canonical.com/~acelan/bugs/lp753189/ linux-
image-2.6.38-8-generic
At first this looked promising because the machine did start up with
both displays working, and I could switch it to using only the external
display. However, after
Oneiric's 2.6.39-3-generic by contrast seems robust across multiple
mode switches. In 2d classic (metacity) mode, it does not have any
problems with black areas on the screen.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I will try the bisection.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/745112
Title:
[arrandale] desktop is messed up (goes black) when laptop is docked
with two
Is it worth updating the title to clarify this bug also apparently
covers cases where just a single monitor doesn't work (as some of the
bugs duped to this complain.)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
This kernel seem to have another regression that about one time in
three, when suspending, it will hang with the 'suspend' and capslock
lights flashing.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
OK, there are three problems related to external screens, with these
packages installed. Let me know if you want them to be filed
separately:
1- after connecting the external monitor (even if it's not turned on or
active) some windows are painted incorrectly, with bits of the desktop
background
actually 2 and 3 might have been due to the 'displays' control panel
being moved off screen when I switched monitors, and the fallback
timeout going off.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
2011-04-21 11:24:54 configure xserver-xorg-video-intel
2:2.14.0-4ubuntu8~lp747205~2 none
2011-04-21 11:24:54 status unpacked xserver-xorg-video-intel
2:2.14.0-4ubuntu8~lp747205~2
2011-04-21 11:24:54 status half-configured xserver-xorg-video-intel
2:2.14.0-4ubuntu8~lp747205~2
2011-04-21 11:24:54
I'm happy to say with that kernel installed this is fixed (at least in
my test). I can switch between internal, external, mirror and side-by-
side using fn-f7 both at the gdm prompt and in gnome classic. Thanks!
--
You received this bug notification because you are a member of Ubuntu-X,
which
I don't get this precise type of corruption using fglrx (it was
intermittent) but I do get a much worse case of bug 760405, and general
flickering on the screen.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
When I rebooted with today's updates, I did not see the crash mentioned
in comment #39 and #40. I get mirrored screens on the text console and
at the gdm greeter screen. After logging in to Ubuntu Classic I
initially get a black screen, but pressing Fn-F7 does flip between
modes. Strangely
It's a bit more complicated: when I reconnected and tried to use the
external monitor, it was back to the original behaviour of showing just
black on both panels. With the monitor connected by vga over either the
ultrabase or built in vga port, I get the flickering red/black display.
Unplugging
With today's natty updates, if the external monitor is connected, the
machine crashes while booting, with this oops recorded:
Apr 10 17:47:45 joy kernel: [5.913652] BUG: unable to handle kernel NULL
pointer dereference at 0230
Apr 10 17:47:45 joy kernel: [5.913701] IP:
screenshot of crash
** Attachment added: IMG_0947.JPG
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/749817/+attachment/2008997/+files/IMG_0947.JPG
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
bradm apparently saw problems with his external monitor go away when he
upgraded to kernel 2.6.38-8.40, so I wanted to confirm that has not
fixed this problem for me.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in
RAOF So something's setting strangeness.
I don't suppose a guest mode login works?
Also, could you set the drm.debug=0x04 kernel parameter (either from the
command line, or via /sys/modules/drm/parameters/debug) and reproduce, then
attach dmesg and Xorg.0.log to the bug?
Attached is me
** Attachment added: Xorg.0.log
https://bugs.edge.launchpad.net/ubuntu/+source/xorg/+bug/749817/+attachment/1980553/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/749817
** Attachment added: Xorg.0.log.old
https://bugs.edge.launchpad.net/ubuntu/+source/xorg/+bug/749817/+attachment/1980554/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
I don't know if it's connected to the drm debug setting, but my mouse
now seems really jerky and unresponsive. I have to click several times
to make it respond. I did install other updates before rebooting so it
may be caused by something else.
--
You received this bug notification because you
1 - 100 of 153 matches
Mail list logo
