https://bugs.freedesktop.org/show_bug.cgi?id=31984
Rafał Miłecki zaj...@gmail.com changed:
What|Removed |Added
Summary|[radeon] Commit 3455a3 |[radeon] Commit 3455a3
https://bugs.freedesktop.org/show_bug.cgi?id=31984
Felix Blanke felixbla...@gmail.com changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=31724
Felix Blanke felixbla...@gmail.com changed:
What|Removed |Added
CC||m...@mattcox.ca
---
Hi Felix,
I moved my modelines from xorg.conf into 50-monitor.conf as per your advice,
and it actually works. I've been using XF86Config/xorg.conf for so many years
in ignorance that I barely noticed the arrival of xorg.conf.d. I'd say that
the issue is definitely related to KMS being
https://bugs.freedesktop.org/show_bug.cgi?id=31724
--- Comment #8 from Alex Deucher ag...@yahoo.com 2010-11-30 07:28:48 PST ---
Are either you running a compositing manager like compiz? If so which one?
Unfortunately, I can't reproduce this with either 2 or 3 monitors with or
without compiz.
https://bugs.freedesktop.org/show_bug.cgi?id=28821
--- Comment #7 from Pablo Rodríguez freedesk...@pragmata.tk 2010-11-30
08:20:58 PST ---
(In reply to comment #6)
(In reply to comment #5)
Thanks for your help, but what is this patch for? I mean, does it enable
radeon.modeset=0 or does it
https://bugs.freedesktop.org/show_bug.cgi?id=31724
--- Comment #10 from Matthew Cox m...@mattcox.ca 2010-11-30 08:46:26 PST ---
I can reproduce it two ways. The first is with a static xorg.conf, in which
case the problem manifests at GDM startup and compiz is not running.
Alternatively, if I
https://bugs.freedesktop.org/show_bug.cgi?id=31724
--- Comment #11 from Alex Deucher ag...@yahoo.com 2010-11-30 09:18:38 PST ---
(In reply to comment #10)
I can reproduce it two ways. The first is with a static xorg.conf, in which
case the problem manifests at GDM startup and compiz is not
https://bugs.freedesktop.org/show_bug.cgi?id=31958
--- Comment #4 from re...@damongeot.fr 2010-11-30 09:23:06 PST ---
Hello,
I've compiled a 2.6.37-rc3 kernel which has this patch and I still got an Xorg
crash with a black screen on both displays.
I still get the same error in dmesg:
[
Paul Gardiner li...@... writes:
For some time, I've been using an X1250 and the radeon driver to drive
a TV via a VGA = SCART circuit. For some reason, with my latest
installation my mode line is refused with the message interlace mode
not supported. I at first assumed this meant that
https://bugs.freedesktop.org/show_bug.cgi?id=31724
--- Comment #12 from Felix Blanke felixbla...@gmail.com 2010-11-30 11:34:05
PST ---
I don't use any kind of compositing manager, just a clean xorg-server :)
The patch seems to work for me. Pulled the newest version from the master tree,
applied
https://bugs.freedesktop.org/show_bug.cgi?id=31724
--- Comment #13 from Matthew Cox m...@mattcox.ca 2010-11-30 12:31:56 PST ---
Created an attachment (id=40678)
-- (https://bugs.freedesktop.org/attachment.cgi?id=40678)
dmesg output
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=31724
--- Comment #14 from Matthew Cox m...@mattcox.ca 2010-11-30 12:32:23 PST ---
Created an attachment (id=40679)
-- (https://bugs.freedesktop.org/attachment.cgi?id=40679)
Xorg log
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=31724
--- Comment #15 from Matthew Cox m...@mattcox.ca 2010-11-30 12:34:30 PST ---
Alex's patch from comment 9 works for me, applied on top of 90f831.
Dmesg and xorg log attached.
--
Configure bugmail:
On Tue, Nov 30, 2010 at 1:47 PM, Derek mon...@monkeynet.ca wrote:
Paul Gardiner li...@... writes:
For some time, I've been using an X1250 and the radeon driver to drive
a TV via a VGA = SCART circuit. For some reason, with my latest
installation my mode line is refused with the message
On Tue, Nov 30, 2010 at 4:14 PM, Derek The Monkey Wueppelmann
mon...@monkeynet.ca wrote:
On Tue, 2010-11-30 at 15:47 -0500, Alex Deucher wrote:
I was wondering if you ever got this issue sorted out? I am currently
having the
same issue. I have tried several different items to get this
Hi all,
xdpyinfo reports:
screen #0:
dimensions:3520x1200 pixels (410x310 millimeters)
resolution:218x98 dots per inch
depths (7):24, 1, 4, 8, 15, 16, 32
Well, I have two screens... So the dimension in pixels is right, but in
millimeters it is only the dimension of one
Bernd Schubert wrote:
Hi all,
xdpyinfo reports:
screen #0:
dimensions:3520x1200 pixels (410x310 millimeters)
resolution:218x98 dots per inch
depths (7):24, 1, 4, 8, 15, 16, 32
Well, I have two screens... So the dimension in pixels is right, but in
millimeters it
On Tue, Nov 30, 2010 at 8:08 PM, Bernd Schubert
bernd.schub...@fastmail.fm wrote:
Bernd Schubert wrote:
Hi all,
xdpyinfo reports:
screen #0:
dimensions: 3520x1200 pixels (410x310 millimeters)
resolution: 218x98 dots per inch
depths (7): 24, 1, 4, 8, 15, 16, 32
Well, I
Alex Deucher wrote:
And that results in Xorg logs in
[ 33.246] (II) RADEON(0): Setting screen physical size to 410 x 310
So instead of correcting the size for one screen, it corrects the overall
screen size... Same with manually setting it with xrandr. At least I have
a workaround now.
20 matches
Mail list logo
