*** This bug is a duplicate of bug 828623 ***
https://bugs.launchpad.net/bugs/828623
Alright, after poking around a bit I believe this is the same thing as
bug #828623, which is reported upstream so I'll dupe to that.
** This bug has been marked a duplicate of bug 828623
[Regression] gnome
[ 1301.290842] [drm:i915_driver_irq_handler], pipe A underrun
[ 1301.307600] [drm:i915_driver_irq_handler], pipe A underrun
[ 1301.309934] [drm:drm_mode_getconnector], [CONNECTOR:5:?]
[ 1301.309944] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:5:LVDS-1]
[ 1301.309967] [drm:drm_helper_
[ 417.493074] [drm:i915_get_vblank_timestamp], crtc 0 is disabled
[ 417.504230] [drm:i915_driver_irq_handler], pipe A underrun
[ 417.509705] [drm:i915_get_vblank_timestamp], crtc 0 is disabled
[ 417.520990] [drm:i915_driver_irq_handler], pipe A underrun
--
You received this bug notification b
Steps to reproduce for me are slightly different from OP:
1. Connect external monitor to VGA output.
2. Launch gnome-display-properties and make sure LVDS1 is on, VGA1 is off.
3. Turn LVDS1 off, VGA1 on
4. LVDS1 turns off, and VGA1 shows linear corruption pattern (different than
the corruption in
This prints out whenever I do a screen configuration change:
[15844.649388] dell_wmi: Received unknown WMI event (0x11)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/737891
T
After using xrandr to disable lvds1:
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
LVDS1 connected (normal left inverted right x axis y axis)
Identifier: 0x41
Timestamp: 32659
Subpixel: horizontal rgb
Clones:
CRTCs: 1
Working state
bryce@clanfield:~$ xrandr --verbose
Screen 0: minimum 320 x 200, current 1920 x 1848, maximum 8192 x 8192
LVDS1 connected 1366x768+231+1080 (0x44) normal (normal left inverted right x
axis y axis) 293mm x 164mm
Identifier: 0x41
Timestamp: 15385367
Subpixel:
While in broken state:
bryce@clanfield:~$ xrandr --auto
xrandr: cannot find crtc for output LVDS1
bryce@clanfield:~$ xrandr --verbose
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
LVDS1 connected (normal left inverted right x axis y axis)
Identifier: 0x41
Ti
I take it all back. I now have an arrandale laptop on hand for testing
and am able to reproduce the bug exactly as originally reported. I'll
do some diagnostics and report back.
** Tags added: oneiric
** Tags added: rls-mgr-o-tracking
--
You received this bug notification because you are a m
** Also affects: gnome-desktop (Ubuntu P-series)
Importance: Undecided
Status: New
** Also affects: xserver-xorg-video-intel (Ubuntu P-series)
Importance: Undecided
Status: New
** Tags removed: rls-mgr-o-tracking
--
You received this bug notification because you are a member
Actually, rather than tasking oneiric on this bug report (which is a bit
stale at this point) I would recommend opening a new bug report, because
so much has changed in arrandale support in oneiric. For instance, mesa
now supports 8k textures on arrandale, so the issue I alluded to still
remaining
** Tags added: rls-mgr-o-tracking
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/737891
Title:
[Arrandale] gnome-display-properties unable to correctly enable
monitors conn
This bug is still affecting me in Oneiric. Adding an oneiric task.
Boy, I sure would like to see this solved for Oneiric...
** Also affects: gnome-desktop (Ubuntu Oneiric)
Importance: High
Status: Confirmed
** Also affects: xserver-xorg-video-intel (Ubuntu Oneiric)
Importance: Wish
** Changed in: gnome-desktop (Ubuntu)
Status: New => Confirmed
** Changed in: gnome-desktop (Ubuntu Natty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in Ubuntu.
https://bugs.la
Same annoying problem for me on HP ProBook 4520s with IntelHD graphics
card.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/737891
Title:
[Arrandale] gnome-display-properties
I guess I am affected by this bug too. I have a Dell D820 with Intel
Mobile GM965/GL960 Integrated Graphics Controller. I use a docking
station to which 2 identical monitors HP LA1951g are hooked, one DVI,
one VGA. The monitors "native resolution" is 1280 x 1024 at 60 Hz.
With Maverick I had to cr
Sorry, forgot to add: this is in 2D "classic" mode, NOT with compiz
enabled, so I'm not hitting the >4096px problem. Nor do my two screens
together add up to >4096px anyway, so this is not merely the Arrandale
hardware limit that I'm hitting.
--
You received this bug notification because you are
Not much to add besides "me too", but I can specifically confirm that
using xrandr(1) does NOT trigger the problem, whereas using the GNOME
Monitors applet does trigger the problem. Also, the GNOME Monitors
applet produces some very bizarre geometry at times (half-height LVDS
screen, typically), f
Similar problem with lenovoT410. when I wake up or reboot my laptop the
X session doesn't start completely.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/737891
Title:
[Arra
Right, and 761236 is looking like a dupe of a common Arrandale bug,
#745112. That in turn *might* be a sub-case of bug #761065 which
affects late-model cards and for which a kernel fix is being verified.
So, as to the disposition of this bug report: We've factored out the
single-monitor issue An
All,
Note that I've filed bug [1] with updated information. On such bug,
Bryce pointed out that a newer kernel should contain patches fixing this
issue. After installing the newer kernel in the Ubuntu's daily builds
the issue was fixed.
Unfortunately, I've been unable to bisect the patches to det
> I am actually unable to run *any* resolution on my external monitor,
if I disable my laptop LCD in gnome's monitor configuration utility.
This is what I am seeing as well, in bug 767319(which is marked as duplicate,
though slightly different than this bug's description).
https://bugs.launchpa
I installed Natty Beta2 this weekend on my HP laptop. I run it with an
Acer 22" external monitor. I prefer the big screen (to the left) as
primary and the laptop screen (to the right) for email and IM.
I only had to edit the ~/.config/monitors.xml to set the VGA screen to
primary to get the setup
Okay, one more interesting tidbit...
I am actually unable to run *any* resolution on my external monitor, if
I disable my laptop LCD in gnome's monitor configuration utility. Seems
that something is very broken there...
--
You received this bug notification because you are a member of Ubuntu
De
Okay, I'm *finally* back home and was able to test this...
I can confirm part of what Thierry suggested. I removed
~/.config/monitors.xml and that got rid of the Samsung flashing monitor
on reboot.
It comes up in cloned monitor mode, dropping down to the lowest common
resolution, which is 1280x8
** Changed in: gnome-desktop (Ubuntu Natty)
Status: Confirmed => Invalid
** Changed in: gnome-desktop (Ubuntu Natty)
Importance: High => Undecided
** Changed in: xserver-xorg-video-intel (Ubuntu Natty)
Milestone: None => natty-updates
--
You received this bug notification because
I managed to get it kinda working. The flashing issue with the Samsung
seemed to be in a stale monitors.xml file. Posting for reference:
Boot laptop separate, then remove ~/.config/monitors.xml and /etc/gnome-
settings-daemon/xrandr/monitors.xml
Shutdown. Place laptop on Ultrabase. Boot, system c
I have the same issue as Dustin. x201 on Ultrabase docking station,
connected to a Samsung 225BW monitor.
If I connect the laptop to my smallish 17" 1280x1024 Sony, I manage to
hook it up in dual display mode. But if I try to disable the laptop
screen it fails with a black screen /cursor. So I can
Bryce,
I have file bug #761236. To file the bug report I did the following:
1. Connected to my x201 through remote desktop.
2. Launched gnome-display-properties and enabled output through VGA1: WORKING
3. Disabled LVDS: ERROR showed as previously discussed (flickering)
4. While having the ex
Hi Bryce,
I booted from a Maverick livecd and the bug does *not* happen.
Everything works as expected, so yeah I guess that we can confirm that
this is not a gnome regression. I'll file the new bug now.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Andres, also would you be able to test booting Maverick via a livecd
with this monitor configuration, using gnome-display-properties to
configure things, and see if you get the same bug there? If it works
properly on maverick, that would tend to confirm seb's hypothesis that
it's not a gnome regre
Hi Andres, yes a new bug report for that configuration would be helpful.
Reference this bug report so we can associate it with this one.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in Ubuntu.
https://bugs.launchpad.ne
Bryce!
Sorry, I guess I really never posted the results (Thought I did) hence,
the testing was unsuccessful.
Would you like another bug report against xserver-xorg-video-intel only
connected to one monitor?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
@Andres, how has your testing gone so far?
@Dustin, the issue seems to have some relationship to the resolution(s)
selected, but I don't *think* it is strongly monitor-specific. It might
be interesting if you tested against a couple other monitors to see if
there is a pattern. But I think the bu
Bryce,
No luck here :-( Still very, very broken in my home setup.
A few pieces of information, though...
1) GDM seems to work correctly. ie, if I reboot my system with my external
24" Samsung 1920x1080 monitor hooked up, GDM comes up in mirror mode, full
resolution and grandeur. When I log
Hi Bryce,
Will sure do. Though right now I'm out of town, and in Texas for the
Texas Linux Fest. I'll test this Monday first thing in the morning.
Cheers,
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in Ubuntu.
https
Hi Andres,
I can't tell from the logs if it is a dupe, but I posted a fix to a
vaguely similar issue (bug #747205) to this PPA:
https://launchpad.net/~bryce/+archive/cherry
I've a hunch that fix might help with this one too, would you mind
installing that package and testing? Test it with the se
** Tags added: regression-release
** Also affects: gnome-desktop (Ubuntu Natty)
Importance: High
Status: Confirmed
** Also affects: xserver-xorg-video-intel (Ubuntu Natty)
Importance: High
Status: Triaged
--
You received this bug notification because you are a member of Ubun
Bryce,
Yes I can confirm that this happens when connecting the laptop directly
to the external monitor (not using the dualhead2go).
Now, what I did is (all from Classic Desktop no effects - and from
gnome-display-settings:
1. Connect external monitor to VGA
2. Enable mirror screens: WORKED
3. Di
Ok, well the case of compiz + >4096 width is essentially a dupe of bug
555641 (which is a wishlist X bug - basically X can't do anything about
this until Xrandr 1.4, and so config tools will have to check for the
invalid configuration).
However, that issue doesn't occur with compiz turned off.
An
Bryce,
Yes I confirm that this happens when using Classic Desktop (No effects).
Now, in terms of the monitors, the logs are when plugged to the
DualHead2Go, displaying in the two monitors at 3840x1080, 1920x1080
each.
However, the *same* happens when plugged it to a *single* monitor at
1920x1080
Andres, can you confirm that this happens when booted into Classic
Desktop (no effects)? It appears from your bug report that compiz (or
kwin compositing) is turned off, but I want to be doubly sure this is
true.
The reason is that upstream says that this bug is because there is a
4096x4096 maxim
** Changed in: xserver-xorg-video-intel
Status: Unknown => Confirmed
** Changed in: xserver-xorg-video-intel
Importance: Unknown => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in Ubuntu.
https://bugs.l
** Bug watch added: freedesktop.org Bugzilla #35682
http://bugs.freedesktop.org/show_bug.cgi?id=35682
** Also affects: gnome-control-center via
http://bugs.freedesktop.org/show_bug.cgi?id=35682
Importance: Unknown
Status: Unknown
** Changed in: gnome-control-center
Importance:
Chatting with kirkland and RoAkSoAx, they believe they have the same
issue, and are also on arrandale chips.
Nothing arrandale-specific has been added to the xrandr utility recently
(in fact the only changes to xrandr since maverick are man page fixes,
autoconf tweaks, and one minor fix that only
** Summary changed:
- gnome-display-properties unable to correctly enable monitors connected to VGA
+ [Arrandale] gnome-display-properties unable to correctly enable monitors
connected to VGA
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscri
46 matches
Mail list logo
