Bug 16285 - First display corrupted when second screen plugged at boot
Summary: First display corrupted when second screen plugged at boot
Status: RESOLVED NOTABUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: 7.3 (2007.09)
Hardware: PowerPC Linux (All)
: medium major
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-09 17:21 UTC by Benjamin Cama
Modified: 2008-06-09 21:52 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
drm messages (528 bytes, text/plain)
2008-06-09 17:21 UTC, Benjamin Cama
no flags Details
xorg log (79.27 KB, text/plain)
2008-06-09 17:21 UTC, Benjamin Cama
no flags Details

Description Benjamin Cama 2008-06-09 17:21:10 UTC
Created attachment 17019 [details]
drm messages

With card :
0000:00:10.0 VGA compatible controller: nVidia Corporation NV34M [GeForce FX Go5200] (rev a1)
On a 12" powerbook G4.

When I don't plug my second monitor at boot (LCD on DVI), I only see one available screen with xrandr. My internal monitor is OK but I don't get any output on the second one.
When plugging the second monitor at boot, I have a clone on it but the first display becomes corrupted when X starts. Xrandr still shows me only one output :

Screen 0: minimum 640 x 400, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
   1024x768       75.0*    72.0     70.0     60.0  
   832x624        75.0  
   800x600        75.0     72.0     60.0     56.0  
   640x480        75.0     73.0     67.0     60.0  
   720x400        70.0  

Tried by using both nvidiafb and offb (after some advices by marcheu on IRC) but got the same result.

The "corrupted" screen looks like pixels are too evenly spaced, showing wired colors, and no meaningfull kind of windows.

Part of my xorg.conf :

Section "Device"
        Identifier      "nVidia Corporation NV34M [GeForce FX Go5200]"
        Driver          "nouveau"
        BusID           "PCI:0:16:0"
        Option          "UseFBDev"              "true"
        Option          "AccelMethod"           "EXA"
EndSection
Comment 1 Benjamin Cama 2008-06-09 17:21:48 UTC
Created attachment 17020 [details]
xorg log
Comment 2 Danny 2008-06-09 19:40:54 UTC
Why do you have usefbdev in the conf? Not sure if it is causing trouble but it is better to remove it I think.

Also, log indicates you are not using randr12, which means you probably are using an older copy of nouveau, in which it was not default. Without randr12 dual screen cannot really work well, so consider updating to git.

d.
Comment 3 Benjamin Cama 2008-06-09 21:52:55 UTC
OK, it was my fault, updating to the latest git did it work ... Sorry for not having tested that prior to reporting this problem. For the record, the version that make it work :
drm commit 4b8aecbde8e62af5370d5401d49a8ab8d089fe8e
DDX commit e034616ab2bbbc486f90c5f64e2bd2de194cf92e

And it works really well actually : it even detected the extended resolution (1680x1050) of my LCD without a itch. This is really nice. Even Xv works quite well.

The only "problem" is that since I switched to offb, I don't have any more console VT ... but now I am not stuck anymore because of some strange DMA problem it seems (I didn't extensively test that) when switching VT.

Concerning UseFBDev, I didn't change anything and it's still set to true. If someone could explain me the meaning of this option, I'd be glad, as it never changed anything on all the linux boxes I touched ...

Thanks for all !


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.