Bug 91109 - "modesetting" does not use my second card's output
Summary: "modesetting" does not use my second card's output
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/modesetting (show other bugs)
Version: 7.7 (2012.06)
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-25 14:43 UTC by monnier
Modified: 2018-12-13 18:11 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.2.log (28.25 KB, text/plain)
2015-06-25 14:43 UTC, monnier
no flags Details

Description monnier 2015-06-25 14:43:49 UTC
Created attachment 116715 [details]
Xorg.2.log

I have two video cards, each connected to one monitor via DVI.
The first card is a Poulsbo (using the gma500_gfx kernel module), the second is a displaylink (using the udl kernel module).  They both have an entry in /dev/dri.

My xorg.conf is just:

   Section "Device"
        Identifier      "Video Device"
        driver          "modesetting"
        Option  "ModeDebug" "true"
   EndSection

The X server does see both cards (e.g., "xrandr --listproviders" shows the two cards), but only sees (and sets up) the output of the Poulsbo ("xrandr" only lists the DVI-0 output).

The Xorg.log (attached) mentions a DVI-1-0 output connected on the displaylink card, but for some reason it doesn't try to get the EDID and "xrandr" can't use it (e.g. if I try "xrandr --output DVI-1-0 --auto" it tells me there's no such output).
Comment 1 GitLab Migration User 2018-12-13 18:11:11 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/51.


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.