Bug 901593 - Only first output is detected when using independent screens
Summary: Only first output is detected when using independent screens
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-18 15:32 UTC by Petr Pisar
Modified: 2014-01-03 07:18 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-03 07:18:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
xorg.conf for two-screen set-up (2.95 KB, application/octet-stream)
2013-01-18 15:32 UTC, Petr Pisar
no flags Details
Xorg.log for working independent screens in F17 (62.29 KB, text/plain)
2013-01-18 15:35 UTC, Petr Pisar
no flags Details
Xorg.log for working one-screen dual-head in F18 (37.36 KB, text/plain)
2013-01-18 15:37 UTC, Petr Pisar
no flags Details
Xorg.log for broken independent screens on F18 (31.56 KB, text/plain)
2013-01-18 16:46 UTC, Petr Pisar
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 923885 0 unspecified CLOSED KDE screensaver shows images for screen 1 on top of screen 0 when the screen is locked 2021-02-22 00:41:40 UTC

Internal Links: 923885

Description Petr Pisar 2013-01-18 15:32:07 UTC
Created attachment 682472 [details]
xorg.conf for two-screen set-up

I've been using in F17 independent screens on my dual-head NVIDIA Corporation G96 [Quadro FX 380] card:

Section "ServerLayout"
    Identifier     "Layout0"
    Screen          0  "Screen0" 0 0
    Screen          1  "Screen1" LeftOf "Screen0"
    InputDevice    "Mouse0" "CorePointer"
    InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

[etc.]

However it does not work in F18 anymore. Xorg loads configuration correctly, but reports failure between dri to drm, thus unloads dri and continues with dri2 which will find only first head DVI-I-1.

If I change ServerLayout to one-screen configuration:

Section "ServerLayout"
    Identifier     "Layout0"
    Screen         "Screen0"
    InputDevice    "Mouse0" "CorePointer"
    InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

xorg will detect both heads correctly.

I have xorg-x11-server-Xorg-1.13.1-4.fc18.x86_64 and xorg-x11-drv-nouveau-1.0.6-1.fc18.x86_64.

Comment 1 Petr Pisar 2013-01-18 15:35:20 UTC
Created attachment 682473 [details]
Xorg.log for working independent screens in F17

Comment 2 Petr Pisar 2013-01-18 15:37:33 UTC
Created attachment 682474 [details]
Xorg.log for working one-screen dual-head in F18

Comment 3 Petr Pisar 2013-01-18 16:46:44 UTC
Created attachment 682534 [details]
Xorg.log for broken independent screens on F18

The error message in this faulty log is:

[ 10303.576] (II) Loading sub module "dri"
[ 10303.576] (II) LoadModule: "dri"
[ 10303.576] (II) Module "dri" already built-in
[ 10303.576] (II) NOUVEAU(1): Loaded DRI module
[ 10303.576] (EE) NOUVEAU(1): [drm] failed to set drm interface version.
[ 10303.576] (EE) NOUVEAU(1): [drm] error opening the drm
[ 10303.576] (EE) NOUVEAU(1): 819: 
[ 10303.577] (II) UnloadModule: "nouveau"
[ 10303.577] (--) Depth 24 pixmap format is 32 bpp
[ 10303.577] (II) NOUVEAU(0): Opened GPU channel 0
[ 10303.581] (II) NOUVEAU(0): [DRI2] Setup complete
[ 10303.581] (II) NOUVEAU(0): [DRI2]   DRI driver: nouveau
[ 10303.581] (II) NOUVEAU(0): [DRI2]   VDPAU driver: nouveau

Comment 4 Paulo Fessel 2013-03-21 04:13:38 UTC
I'm also experiencing this. I've touched this bug when reporting an issue on KDE screensaver, see bug #923885.

Comment 5 Dan Callaghan 2013-03-29 04:00:47 UTC
(In reply to comment #3)
> [ 10303.576] (EE) NOUVEAU(1): [drm] failed to set drm interface version.
> [ 10303.576] (EE) NOUVEAU(1): [drm] error opening the drm
> [ 10303.576] (EE) NOUVEAU(1): 819: 
> [ 10303.577] (II) UnloadModule: "nouveau"

This happens on my Mac Mini 3,1 booted in EFI mode with kernel-3.8.4-202.fc18.x86_64 and xorg-x11-drv-nouveau-1.0.6-4.fc18.x86_64. It has an NV50 card. Everything seems to work okay on the kernel side, except for these three errors:

Mar 29 12:31:07 localhost kernel: nouveau E[   PFIFO][0000:02:00.0] CACHE_ERROR - Ch 127/5 Mthd 0x1ffc Data 0xfffffef7
Mar 29 12:31:07 localhost kernel: nouveau E[   PFIFO][0000:02:00.0] CACHE_ERROR - Ch 127/1 Mthd 0x0154 Data 0x80010000
Mar 29 12:31:07 localhost kernel: nouveau E[   PFIFO][0000:02:00.0] CACHE_ERROR - Ch 127/7 Mthd 0x1ffc Data 0xfffffffe

and some occasional display corruption on the console. But X fails to start.

Ben, Dave, I can bring it in to the office one day if you want to poke it in person :-)

Comment 6 Fedora End Of Life 2013-12-21 10:31:55 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Petr Pisar 2014-01-03 07:18:30 UTC
The independent screens works in F19 with 
xorg-x11-server-Xorg-1.14.4-3.fc19.x86_64 and xorg-x11-drv-nouveau-1.0.9-1.fc19.x86_64 again.


Note You need to log in before you can comment on or make changes to this bug.