On Tue, Dec 25, 2012 at 03:31:01PM +0100, Karol Babioch wrote:
Hi,
it's been a while, however I've got other things to do the last couple
of weeks. Nevertheless this is still something bugging me.
Am 26.11.2012 00:03, schrieb Peter Hutterer:
please provide your Xorg.log. this should be a
On Tue, Jan 01, 2013 at 04:33:31PM +0100, Markus Ellinger wrote:
Hi everyone,
I am using Linux Mint Nadia which ships with X.Org 1.13.0 on a Sony
Vaio Z13. I experience two problems with the Synaptics driver which
do not occur on the Windows 7 Professional installation on the same
machine:
libXdamage is the Xlib based library for the X Damage extension.
This minor maintenance release cleans up the build configuration scripts,
including making them compatible with automake-1.13, which errors out on
the old AM_CONFIG_HEADER macro.
Alan Coopersmith (2):
Strip trailing
libXdamage is the Xlib based client library for the X Composite extension.
This minor maintenance release cleans up the build configuration scripts,
including making them compatible with automake-1.13, which errors out on
the old AM_CONFIG_HEADER macro.
Alan Coopersmith (2):
Strip trailing
Matt Dew marcoz@... writes:
It's actually been open since last Thursday but this is notice for
anyone wondering.
The nomination window is 3 weeks; until Jan 3.
I've updated the X.Org calendar.
I would like to request that
glx/dri2: initialise api to avoid indirect rendering failing
On 12/18/12 09:44 PM, Alan Coopersmith wrote:
Once Keith pulls it into master, this is a 1.13.2 candidate:
EnableDisableExtensionError: Use ARRAY_SIZE rather than sentinel
http://patchwork.freedesktop.org/patch/12682/
Fixes a crash if you run Xorg -extension crash (or any other
On 12/26/2012 11:49 PM, Pierre-Loup A. Griffais wrote:
Ping; anyone feel like merging this?
To ssh://git.freedesktop.org/git/xorg/app/xrandr
b26fd53..094b40e master - master
--
Aaron
Thanks,
- Pierre-Loup
On 12/19/2012 12:35 PM, Pierre-Loup A. Griffais wrote:
I could have sworn
Thanks!
On 01/02/2013 01:25 PM, Aaron Plattner wrote:
On 12/26/2012 11:49 PM, Pierre-Loup A. Griffais wrote:
Ping; anyone feel like merging this?
To ssh://git.freedesktop.org/git/xorg/app/xrandr
b26fd53..094b40e master - master
--
Aaron
Thanks,
- Pierre-Loup
On 12/19/2012 12:35
Some tests segfault if XT_DISPLAY is set and XT_DISPLAYHOST is not.
Signed-off-by: Peter Harris phar...@opentext.com
---
xts5/bin/xts-config.in |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/xts5/bin/xts-config.in b/xts5/bin/xts-config.in
index 9e30b5f..ce55618
https://bugs.freedesktop.org/show_bug.cgi?id=58894
--- Comment #4 from Alex Deucher ag...@yahoo.com ---
What are the pci ids for your chip?
--
You are receiving this mail because:
You are the assignee for the bug.
___
xorg-driver-ati mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=58928
--- Comment #3 from Alex Deucher ag...@yahoo.com ---
Are their any changes to the xf86-video-ati package between 8.2-RELEASE and
9.1-RELEASE? If so, I'd try to narrow down what change caused the problem. If
the xf86-video-ati driver versions
https://bugs.freedesktop.org/show_bug.cgi?id=58894
--- Comment #5 from Benny Ammitzbøll be...@ammitzboell-consult.dk ---
bla-hpenvy17 ~ # lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller
https://bugs.freedesktop.org/show_bug.cgi?id=58894
--- Comment #6 from Alex Deucher ag...@yahoo.com ---
You've got a hybrid laptop with two GPUs. You need to use vgaswitcheroo to
select which one is active. I suspect you have the Intel GPU selected and you
are ending up with the vesa driver
https://bugs.freedesktop.org/show_bug.cgi?id=58894
--- Comment #7 from Benny Ammitzbøll be...@ammitzboell-consult.dk ---
Ok, I have also discovered that I've got a muxless Intel/ATI hybrid graphics
card by reading e.g. http://forums.gentoo.org/viewtopic-t-909802-start-0.html.
I've tried
https://bugs.freedesktop.org/show_bug.cgi?id=58894
--- Comment #8 from Michel Dänzer mic...@daenzer.net ---
(In reply to comment #4)
What are the pci ids for your chip?
BTW, this can be seen in the log file:
[50.286] (--) PCI:*(0:0:2:0) 8086:0116:103c:168a rev 9, Mem @
0xc000/4194304,
https://bugs.freedesktop.org/show_bug.cgi?id=58894
--- Comment #9 from Benny Ammitzbøll be...@ammitzboell-consult.dk ---
(In reply to comment #8)
(In reply to comment #4)
What are the pci ids for your chip?
BTW, this can be seen in the log file:
[50.286] (--) PCI:*(0:0:2:0)
https://bugs.freedesktop.org/show_bug.cgi?id=58894
--- Comment #10 from Alex Deucher ag...@yahoo.com ---
Your system appears to be MUXed rather than MUX-less:
[drm] Radeon Display Connectors
[drm] Connector 0:
[drm] eDP-1
[drm] HPD2
[drm] DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448
https://bugs.freedesktop.org/show_bug.cgi?id=58894
--- Comment #11 from Alex Deucher ag...@yahoo.com ---
If it were MUX-less, there would be fewer or no display connectors listed in
the dmesg output.
--
You are receiving this mail because:
You are the assignee for the bug.
On Fri, Dec 21, 2012 at 3:22 PM, Albrecht Dreß albrecht.dr...@arcor.de wrote:
Hi Alex!
Am 21.12.12 19:44 schrieb(en) Alex Deucher:
Sounds like internal tmds may be broken in kms. Probably easiest to dump
the registers from a working setup (console fb, or old version of the
driver) and a
19 matches
Mail list logo
