Nouveau - Feb 2009 - [Bug 20006] New: powerpc64: Black screen using RandR12

http://bugs.freedesktop.org/show_bug.cgi?id=20006

           Summary: powerpc64: Black screen using RandR12
           Product: xorg
           Version: 7.4
          Platform: PowerPC
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau at lists.freedesktop.org
        ReportedBy: bmaass at math.uni-bremen.de
         QAContact: xorg-team at lists.x.org


Created an attachment (id=22680)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=22680)
Xorg log

Enabling Option RandR12 in xorg.conf results in black screen. Server starts up
fine, seems to be usable, only screen stays black. Monitor doesn't turn off.

VT switching works, albeit with picture degradation (bad resolution?) which
isn't recovered even when killing X (also, crash on killing X, with or
without
RandR12, see messages).

Operating system: Gentoo Linux ppc64 with 64bit userland (problem the same on
32bit userland).

Hardware: Apple G5 with DVI-only GeForce7800GT PCI-E Apple OEM version, screen
is a Dell 30 inch 2560x1600 display on DVI connector 1.

drm commit: 97fdadee6a79f9406a55c235ee46104814321152
xf86-video-nouveau commit: 98b8cada6c355d437925a92ef0413e96751ed567

Legacy render path with RandR12 disabled works fine.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #1 from bmaass <bmaass at math.uni-bremen.de>  2009-02-08
03:10:47 PST ---
Created an attachment (id=22681)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=22681)
drm messages


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #2 from bmaass <bmaass at math.uni-bremen.de>  2009-02-08
03:11:38 PST ---
Created an attachment (id=22682)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=22682)
xorg conf


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #3 from Danny <moondrake at gmail.com>  2009-02-09 01:07:58
PST ---
Can you attach a full kernel log? Or more precisely, I suspect you may be using
nvidiafb (or rivafb).

Danny


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #4 from bmaass <bmaass at math.uni-bremen.de>  2009-02-09
03:17:02 PST ---
(In reply to comment #3)
> Can you attach a full kernel log? Or more precisely, I suspect you may be
using
> nvidiafb (or rivafb).
> 
> Danny
> 
I'm using the OpenFirmware framebuffer, passing video=ofonly to the kernel.
Nvidiafb isn't even in the kernel.

Do you still need the full log?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #5 from Danny <moondrake at gmail.com>  2009-02-09 03:58:34
PST ---
Maybe not then (would not hurt though).

Are you sure you are not hitting bug 15206?

If so, I guess you should install the nouveau branch of radeontool and dump
registers with and without randr1.2 mode

d.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #6 from bmaass <bmaass at math.uni-bremen.de>  2009-02-09
04:21:42 PST ---
(In reply to comment #5)
> Maybe not then (would not hurt though).
> 
> Are you sure you are not hitting bug 15206?
> 
> If so, I guess you should install the nouveau branch of radeontool and dump
> registers with and without randr1.2 mode
> 
> d.
> 
I read that bug before but it states that the second display doesn't get a
signal. Mine does (it doesn't go into powersave), but it's black. So I
figured
I had something different going on.

I'll post a full log with drm debug later when I'm back at the machine,
though.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006


bmaass <bmaass at math.uni-bremen.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #22681|0                           |1
        is obsolete|                            |




--- Comment #7 from bmaass <bmaass at math.uni-bremen.de>  2009-02-09
10:14:06 PST ---
Created an attachment (id=22724)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=22724)
full dmesg

Full dmesg with drm debug=1. Kernel oops at the end happens on server kill, not
on its own.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #8 from bmaass <bmaass at math.uni-bremen.de>  2009-02-09
12:19:34 PST ---
Created an attachment (id=22726)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=22726)
non-randr12 mode register dump


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #9 from bmaass <bmaass at math.uni-bremen.de>  2009-02-09
12:45:45 PST ---
Created an attachment (id=22729)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=22729)
randr12 mode register dump


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #10 from Stuart Bennett <sb476 at cam.ac.uk>  2009-02-11
16:42:40 PST ---
Hi, from looking at the two dumps, it looks like either we're doing
something
very wrong (a possibility), or the two dumps were made with the monitor
connected to different dvi connectors.  If this was the case, can you please
re-make the dumps leaving the monitor on the same connector, otherwise it makes
side-by-side comparison very hard?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #11 from bmaass <bmaass at math.uni-bremen.de>  2009-02-12
01:02:32 PST ---
(In reply to comment #10)
> Hi, from looking at the two dumps, it looks like either we're doing
something
> very wrong (a possibility), or the two dumps were made with the monitor
> connected to different dvi connectors.  If this was the case, can you
please
> re-make the dumps leaving the monitor on the same connector, otherwise it
makes
> side-by-side comparison very hard?
> 
That would be stupid on my part, but absolutely a possibility. ;-) Now,
re-dumped registers follow.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006


bmaass <bmaass at math.uni-bremen.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #22726|0                           |1
        is obsolete|                            |




--- Comment #12 from bmaass <bmaass at math.uni-bremen.de>  2009-02-12
01:03:16 PST ---
Created an attachment (id=22851)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=22851)
non-randr12 register dump


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006


bmaass <bmaass at math.uni-bremen.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #22729|0                           |1
        is obsolete|                            |




--- Comment #13 from bmaass <bmaass at math.uni-bremen.de>  2009-02-12
01:03:53 PST ---
Created an attachment (id=22852)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=22852)
randr12 register dump


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #14 from Stuart Bennett <sb476 at cam.ac.uk>  2009-02-12
06:42:46 PST ---
Created an attachment (id=22859)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=22859)
changes which are unlikely to help, but should be ruled out

Hi, here's the first of three patches.  They apply on top of each other, but
please test the changes individually, i.e. test 1, then 1+2, then 1+2+3.  If
any changes in behaviour are observed please note what changed and which
patches were applied to cause the change.  Also, please do the test with the
monitor attached to the same port the earlier dumps were made with, or else the
results are not very helpful :-)  If there is no change with all three patches
applied, please make a new register dump of the "randr12 + patch 1 + patch
2 +
patch 3" case.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #15 from Stuart Bennett <sb476 at cam.ac.uk>  2009-02-12
06:43:15 PST ---
Created an attachment (id=22860)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=22860)
a more interesting change

2 / 3


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #16 from Stuart Bennett <sb476 at cam.ac.uk>  2009-02-12
06:44:16 PST ---
Created an attachment (id=22861)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=22861)
disable bios output scripts

3/3

Note all patches can be simply applied on top a clean git checkout using
"git
am $PATCHNAME"


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #17 from bmaass <bmaass at math.uni-bremen.de>  2009-02-13
02:32:16 PST ---
Created an attachment (id=22894)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=22894)
randr12 and patches register dump

Patch 0001 didn't do anything visibly, patch 0002 "fixes" the
problem (more in
a second) and I couldn't see if patch 0003 improved anything over 0002.

The "fix" is that I finally get a picture (can see xterms, xclock,
interact
with them), but it's still horribly wrong somehow. Looks like the picture is
missing vertical lines, but somehow still not everywhere (TWM resize lines may
disappear, but there are no gaps in the windows themselves).

This is consistent over all modes I've tried (2560x1600, 1920x1200,
1280x800)
and doesn't show up on a screenshot. It also doesn't get restored back
to
normal when quitting the X server: the brokenness remains when using the
console afterwards.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #18 from Stuart Bennett <sb476 at cam.ac.uk>  2009-02-13
03:12:12 PST ---
(In reply to comment #17)
> Created an attachment (id=22894)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=22894)
[details]
> randr12 and patches register dump
Thanks.  Some quick questions to help in making the next patch, and some other
things to try in the future:

This register dump is with all three patches, or just the first two?
> Patch 0001 didn't do anything visibly, patch 0002 "fixes" the
problem (more in
> a second) and I couldn't see if patch 0003 improved anything over 0002.
Just to clarify, you tried 0003 on top of 0002, but could see no difference?
> The "fix" is that I finally get a picture (can see xterms,
xclock, interact
> with them), but it's still horribly wrong somehow. Looks like the
picture is
> missing vertical lines, but somehow still not everywhere (TWM resize lines
may
> disappear, but there are no gaps in the windows themselves).
Hmm, might be interesting to see a picture should you have a digital camera,
but don't worry if it's not convenient.
> This is consistent over all modes I've tried (2560x1600, 1920x1200,
1280x800)
> and doesn't show up on a screenshot. It also doesn't get restored
back to
> normal when quitting the X server: the brokenness remains when using the
> console afterwards.
Is it worse than the "picture degradation (bad resolution?) which isn't
recovered even when killing X" you mentioned previously, or the same?

One other thing that would be interesting to know next time you test (using a
clean checkout (no patches)), if you add `Option "FPScale"
"off"' in the driver
section of your xorg.conf, and set 1280x800, whether that works any better.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #19 from bmaass <bmaass at math.uni-bremen.de>  2009-02-13
05:21:59 PST ---
(In reply to comment #18)
> (In reply to comment #17)
> This register dump is with all three patches, or just the first two?
All three. Do you want one with just 1+2?
> Just to clarify, you tried 0003 on top of 0002, but could see no
difference?
Exactly. I started seeing something with 1+2 and 1+2+3 didn't visibly change
anything.
> Hmm, might be interesting to see a picture should you have a digital
camera,
> but don't worry if it's not convenient.
I'm pretty happy you're taking so much time helping me, so I certainly
won't
complain about small inconveniences. I'll have to charge the camera's
batteries
first, though. :-)
> Is it worse than the "picture degradation (bad resolution?) which
isn't
> recovered even when killing X" you mentioned previously, or the same?
It is the same, only that before I couldn't see it in X but only after
killing
it. But it is exactly the same.
> One other thing that would be interesting to know next time you test (using
a
> clean checkout (no patches)), if you add `Option "FPScale"
"off"' in the driver
> section of your xorg.conf, and set 1280x800, whether that works any better.
I'll try that and report back along with the promised photo.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #20 from bmaass <bmaass at math.uni-bremen.de>  2009-02-13
07:51:05 PST ---
BIG CORRECTION!!!

As the picture error didn't get corrected when killing the server, I
didn't
notice that patches 1+2+3 actually give a GOOD PICTURE, until I retested after
a reboot.

Your other suggestion, concerning FPScale, didn't seem to have any effect. I
tested:

patches 1+2+3, FPScale on: good picture
patches 1+2, FPScale on: bad picture
patches 1+2, FPScale off: bad picture
no patches, FPScale on: no picture
no patches, FPScale off: no picture

Are you still interested in a photo of the screen distortion?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #21 from Stuart Bennett <sb476 at cam.ac.uk>  2009-02-13
10:04:50 PST ---
(In reply to comment #20)
> BIG CORRECTION!!!
> 
> As the picture error didn't get corrected when killing the server, I
didn't
> notice that patches 1+2+3 actually give a GOOD PICTURE, until I retested
after
> a reboot.
Ok, that's more like I expected (sorry, should have noted the reboot
requirement) :-)
> Your other suggestion, concerning FPScale, didn't seem to have any
effect. I
> tested:
Even at 1280x800?  interesting
> patches 1+2+3, FPScale on: good picture
> patches 1+2, FPScale on: bad picture
> patches 1+2, FPScale off: bad picture
> no patches, FPScale on: no picture
> no patches, FPScale off: no picture
> 
> Are you still interested in a photo of the screen distortion?
No, that's fine, I've a better idea of the problem now.  I'll try to
come up
with some more things next week.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #22 from bmaass <bmaass at math.uni-bremen.de>  2009-02-13
10:14:59 PST ---
(In reply to comment #21)
> No, that's fine, I've a better idea of the problem now.  I'll
try to come up
> with some more things next week.
That's fine, the patched version is working good so far, so no big hurry
here.
:-)


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #23 from Maarten Maathuis <madman2003 at gmail.com> 
2009-02-13 10:23:27 PST ---
The patched version is just a hack, try hotplugging a (2nd) dvi monitor and see
the failure ;-)


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #24 from Stuart Bennett <sb476 at cam.ac.uk>  2009-02-16
11:08:28 PST ---
Ok, a few more things I would like:
1) a copy of the video bios image.  this can be found in /proc/device-tree and
is called "NVDA,BMP"
2) using an *unpatched* copy, change the first "#if 0" of nv_bios.c
(around
line 41) to "#if 1", then attach the more verbose xorg.0.log to this
bug
(obviously it won't work, as it's unpatched)
3) (from a clean boot, if you've done 2) beforehand), see which of the
previous
patches are absolutely necessary.  I imagine just 2+3 will work, and it's
somewhat possible that 3 alone would do


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #25 from bmaass <bmaass at math.uni-bremen.de>  2009-02-17
00:52:53 PST ---
Created an attachment (id=23008)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=23008)
NVDA,BMP


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #26 from bmaass <bmaass at math.uni-bremen.de>  2009-02-17
00:54:55 PST ---
Created an attachment (id=23009)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=23009)
Xorg.0.log with "#if 1" in nv_bios.c


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #27 from bmaass <bmaass at math.uni-bremen.de>  2009-02-17
00:55:26 PST ---
Just patch 0003 wouldn't give me any picture, but 0002 + 0003 seem to work
fine.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006


Stuart Bennett <sb476 at cam.ac.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #22859|0                           |1
        is obsolete|                            |
  Attachment #22860|0                           |1
        is obsolete|                            |
  Attachment #22861|0                           |1
        is obsolete|                            |




--- Comment #28 from Stuart Bennett <sb476 at cam.ac.uk>  2009-02-17
03:14:39 PST ---
Created an attachment (id=23015)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=23015)
improved workaround

Please test with this patch on a clean checkout.  If it works, can you also try
removing the line it adds to nv_crtc.c and see if the change to nv_bios.c is
sufficient?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #29 from bmaass <bmaass at math.uni-bremen.de>  2009-02-18
02:41:37 PST ---
(In reply to comment #28)
> Created an attachment (id=23015)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=23015)
[details]
> improved workaround
> 
> Please test with this patch on a clean checkout.  If it works, can you also
try
> removing the line it adds to nv_crtc.c and see if the change to nv_bios.c
is
> sufficient?
Patch works fine, no picture again without the change to nv_crtc.c though.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006


Stuart Bennett <sb476 at cam.ac.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #23015|0                           |1
        is obsolete|                            |




--- Comment #30 from Stuart Bennett <sb476 at cam.ac.uk>  2009-02-18
13:44:34 PST ---
Created an attachment (id=23087)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=23087)
Partial fix

Ok, here's a partial fix, the other part being something wrong with scaling
modes which I don't presently understand.  To test the fix, apply the patch,
and to work-around the scaling problem add `Option "ScalingMode"
"panel"' to
the device section of your xorg.conf ("noscale" should work as well as
panel,
"aspect" and "fullscreen" won't).

Assuming this works and you feel like a new challenge, if booting with the
monitor on the other dvi port gets an image with randr12 turned off (or even
with the "nv" driver), feel free to make comparison regdumps of that
and we can
look at fixing it for randr12 :-)


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #31 from bmaass <bmaass at math.uni-bremen.de>  2009-02-19
06:50:14 PST ---
(In reply to comment #30)
> Created an attachment (id=23087)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=23087)
[details]
> Partial fix
> 
> Ok, here's a partial fix, the other part being something wrong with
scaling
> modes which I don't presently understand.  To test the fix, apply the
patch,
> and to work-around the scaling problem add `Option "ScalingMode"
"panel"' to
> the device section of your xorg.conf ("noscale" should work as
well as panel,
> "aspect" and "fullscreen" won't).
> 
> Assuming this works and you feel like a new challenge, if booting with the
> monitor on the other dvi port gets an image with randr12 turned off (or
even
> with the "nv" driver), feel free to make comparison regdumps of
that and we can
> look at fixing it for randr12 :-)
Alright, bear with me here, fresh clone, patch applied, 'Option
"ScalingMode"
"panel"'... black as ever. Am I missing something?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #32 from Stuart Bennett <sb476 at cam.ac.uk>  2009-02-19
12:22:00 PST ---
(In reply to comment #31)
> Alright, bear with me here, fresh clone, patch applied, 'Option
"ScalingMode"
> "panel"'... black as ever. Am I missing something?
Huh, weird.  maybe "noscale" would work better than "panel"?
otherwise (to
test I've not totally misdiagnosed this), in nv_crtc.c change the line with
SCALE_PANEL to "if (1 || nv_encoder->scaling_mode == SCALE_PANEL
||".  If that
doesn't work I'm confused :-)


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #33 from bmaass <bmaass at math.uni-bremen.de>  2009-02-19
13:44:39 PST ---
(In reply to comment #32)
> Huh, weird.  maybe "noscale" would work better than
"panel"?  otherwise (to
> test I've not totally misdiagnosed this), in nv_crtc.c change the line
with
> SCALE_PANEL to "if (1 || nv_encoder->scaling_mode == SCALE_PANEL
||".  If that
> doesn't work I'm confused :-)
I had tried both 'noscale' and 'panel', neither worked. Sorry
for the
confusion. But that's apparently really not the problem, since the
'1' didn't
fix anything either.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #34 from Stuart Bennett <sb476 at cam.ac.uk>  2009-02-19
15:12:32 PST ---
Created an attachment (id=23122)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=23122)
dpms lolz

ok, I think I see what I overlooked.  apply this patch on top of the previous
"partial fix", and hopefully it should work, even without a specific
scaling
mode.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #35 from bmaass <bmaass at math.uni-bremen.de>  2009-02-20
06:27:21 PST ---
Yes, this works!


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #36 from Stuart Bennett <sb476 at cam.ac.uk>  2009-02-20
09:59:23 PST ---
Fix pushed:
http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=e09f50e5f9126c682289b7ba790f16b93a80b876

I'd be interested in fixing the other dvi port, if non-randr12-mode or nv
can
work with it, so we reach parity of functionality.  Otherwise, I think this can
be resolved FIXED :)


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #37 from bmaass <bmaass at math.uni-bremen.de>  2009-02-22
02:03:24 PST ---
(In reply to comment #36)
> I'd be interested in fixing the other dvi port, if non-randr12-mode or
nv can
> work with it, so we reach parity of functionality.  Otherwise, I think this
can
> be resolved FIXED :)
Sure, what do you need? Register dumps using nv or non-randr12 nouveau, as you
said above? Does it matter that the second port can only drive the panel at
1920x1200?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #38 from Stuart Bennett <sb476 at cam.ac.uk>  2009-02-22
03:52:20 PST ---
(In reply to comment #37)
> Sure, what do you need? Register dumps using nv or non-randr12 nouveau, as
you
> said above? Does it matter that the second port can only drive the panel at
> 1920x1200?
So long as non-randr12/nv can get it to light up, and randr12-nouveau
doesn't,
1920x1200 is fine.  Register dumps and Xorg.0.logs would be great.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #39 from bmaass <bmaass at math.uni-bremen.de>  2009-02-23
08:46:38 PST ---
Created an attachment (id=23213)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=23213)
Xorg Log noveau without randr12

Xorg log. Somewhat of a WTF moment here, DVI-I-1 apparently will drive the
panel at 2560x1600 in non-randr12 mode. Thought this was supposed to be a
single link DVI port...

Good news: nouveau works on this port in randr12-mode, although only in
1920x1200 (as I would have had expected). Register dump non-randr12 follows.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #40 from bmaass <bmaass at math.uni-bremen.de>  2009-02-23
08:47:20 PST ---
Created an attachment (id=23214)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=23214)
Register dump nouveau no randr12


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #41 from Stuart Bennett <sb476 at cam.ac.uk>  2009-02-24
09:20:42 PST ---
(In reply to comment #39)
> Xorg log. Somewhat of a WTF moment here, DVI-I-1 apparently will drive the
> panel at 2560x1600 in non-randr12 mode. Thought this was supposed to be a
> single link DVI port...
> Good news: nouveau works on this port in randr12-mode, although only in
> 1920x1200 (as I would have had expected). Register dump non-randr12
follows.
Interesting, what resolution does OSX let you have on that connector (assuming
you've got OSX installed)?

You can allow dual-link modes on that connector in nouveau by editing
nv_output_mode_valid() in nv_output.c; a simple change being to replace the
MODE_CLOCK_HIGH after the (mode->Clock > 165000) test with MODE_OK, but
I've no
idea whether that would work :-)


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #42 from bmaass <bmaass at math.uni-bremen.de>  2009-02-27
12:38:05 PST ---
(In reply to comment #41)
> Interesting, what resolution does OSX let you have on that connector
(assuming
> you've got OSX installed)?
> 
> You can allow dual-link modes on that connector in nouveau by editing
> nv_output_mode_valid() in nv_output.c; a simple change being to replace the
> MODE_CLOCK_HIGH after the (mode->Clock > 165000) test with MODE_OK,
but I've no
> idea whether that would work :-)
Sorry this took so long, I needed to get hold of a copy of OSX. As anticipated,
OSX would only drive the panel at 1920x1200 on DVI-I-1 (just like nouveau in
non-randr12 mode).

However, with the change you proposed, nouveau will do dual-link on the second
connector without complaining.

What is this? Did Apple cripple a dual-dual-link card so the could sell more
high-end cards instead? Or might this break down if I tried to drive two
dual-link displays simultaneously?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #43 from bmaass <bmaass at math.uni-bremen.de>  2009-02-27
12:39:27 PST ---
(In reply to comment #42)
> ...(just like nouveau in
> non-randr12 mode)...
I meant, "randr12-mode" of course, not "non-randr12".


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006





--- Comment #44 from Stuart Bennett <sb476 at cam.ac.uk>  2009-02-28
06:32:01 PST ---
(In reply to comment #42)
> Sorry this took so long, I needed to get hold of a copy of OSX. As
anticipated,
> OSX would only drive the panel at 1920x1200 on DVI-I-1 (just like nouveau
in
> non-randr12 mode).
Thanks for the effort, I wasn't expecting you to have to find a copy :)
> However, with the change you proposed, nouveau will do dual-link on the
second
> connector without complaining.
> 
> What is this? Did Apple cripple a dual-dual-link card so the could sell
more
> high-end cards instead? Or might this break down if I tried to drive two
> dual-link displays simultaneously?
According to http://en.wikipedia.org/wiki/Nvidia_Quadro the fx4500 (the Apple
option for 2 x dual-link) is the same silicon as the 7800gtx, which according
to http://www.nvidia.com/object/extreme_hd_gpu.html is only 1 x dual-link; the
difference is normally whether the board manufacturer has connected up the
traces for the second link pins, and it seems your board manufacturer did, but
then crippled it in the bios image.  We can't really ignore the image
though,
as there's going to be a majority of cases where the extra link isn't
wired up.

As for using 2 x dual-link, I don't know :)  It's certainly possible
that the
card isn't clocked high enough for some part to have the bandwidth to drive
two
such displays, or (less likely) that the board is populated with some cheaper
components that can't handle the additional electrical demands.  Assuming
you
don't have access to another 30" :) we're probably not going to
find out.

Unless you can argue a good case for it, I think I'll leave things as they
are
-- an option for "let me do 2 x dual link on a card I bought thinking it
couldn't" seems like something with very low demand (I guess I could
add a pci
id based override for this Apple card, but that still doesn't resolve
whether
the hardware can run 2 x dual-link simultaneously).


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=20006


bmaass <bmaass at math.uni-bremen.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




--- Comment #45 from bmaass <bmaass at math.uni-bremen.de>  2009-02-28
07:30:03 PST ---
(In reply to comment #44)
> Thanks for the effort, I wasn't expecting you to have to find a copy :)
No problem, I was planning to do it some day so I could replay some of my old
games. :-)
> According to http://en.wikipedia.org/wiki/Nvidia_Quadro the fx4500 (the
Apple
> option for 2 x dual-link) is the same silicon as the 7800gtx, which
according
> to http://www.nvidia.com/object/extreme_hd_gpu.html is only 1 x dual-link;
the
> difference is normally whether the board manufacturer has connected up the
> traces for the second link pins, and it seems your board manufacturer did,
but
> then crippled it in the bios image.  We can't really ignore the image
though,
> as there's going to be a majority of cases where the extra link
isn't wired up.
> 
> As for using 2 x dual-link, I don't know :)  It's certainly
possible that the
> card isn't clocked high enough for some part to have the bandwidth to
drive two
> such displays, or (less likely) that the board is populated with some
cheaper
> components that can't handle the additional electrical demands. 
Assuming you
> don't have access to another 30" :) we're probably not going
to find out.
> 
> Unless you can argue a good case for it, I think I'll leave things as
they are
> -- an option for "let me do 2 x dual link on a card I bought thinking
it
> couldn't" seems like something with very low demand (I guess I
could add a pci
> id based override for this Apple card, but that still doesn't resolve
whether
> the hardware can run 2 x dual-link simultaneously).
There is some oddity about an Apple S-Video adapter only working on DVI-I-0 on
these cards, I think, so there actually may be cases where people would want to
drive their 30" on DVI-I-1. But considering that there probably are less
than a
10000 of these machine-card combinations out there, 99 per cent of which
probably will never run anything but OSX, the effort seems wasted.

Nevertheless, thanks a bunch for fixing this so promptly, I'm a happier
person
now. ;-)


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.