Bug 47066 - glxinfo says "nouveau" on dual seat when on a monitor drived by a radeon card
Summary: glxinfo says "nouveau" on dual seat when on a monitor drived by a radeon card
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: GLX (show other bugs)
Version: 8.0
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-07 10:09 UTC by diego.abelenda
Modified: 2019-09-18 17:44 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
display-related file in /etc/X11/xorg.conf.d/ that sets up the multi-head (584 bytes, text/plain)
2012-03-07 10:09 UTC, diego.abelenda
Details
output of DISPLAY=:0.0 glxinfo (44.12 KB, text/plain)
2012-03-07 10:10 UTC, diego.abelenda
Details
output of DISPLAY=:0.1 glxinfo (44.12 KB, text/plain)
2012-03-07 10:11 UTC, diego.abelenda
Details
dmesg after xorg start (fresh reboot) (81.06 KB, text/plain)
2012-03-07 11:54 UTC, diego.abelenda
Details
Xorg log after start (56.81 KB, text/plain)
2012-03-07 11:55 UTC, diego.abelenda
Details
glxinfo when only the radeon card is present (24.43 KB, text/plain)
2012-03-07 12:21 UTC, diego.abelenda
Details
Xorg log when only the radeon is present (52.08 KB, text/plain)
2012-03-07 12:22 UTC, diego.abelenda
Details
try to fix screen indexing in glxinfo (1006 bytes, patch)
2012-03-07 13:45 UTC, Brian Paul
Details | Splinter Review

Description diego.abelenda 2012-03-07 10:09:13 UTC
Created attachment 58132 [details]
display-related file in /etc/X11/xorg.conf.d/ that sets up the multi-head

After hitting #47064 I decided to play with my nvidia card and the radeon IGP I have in my new system.

So I set xorg configuration up so that I have a desktop spanning both cards and when I ask glxinfo for both displays I get the same answer... I would expect one to be radeon and the other nouveau not both nouveau...

I don't know if it is a bug in X in glxinfo or in mesa, if I can be of any help to find out tell me.
Comment 1 diego.abelenda 2012-03-07 10:10:39 UTC
Created attachment 58133 [details]
output of DISPLAY=:0.0 glxinfo
Comment 2 diego.abelenda 2012-03-07 10:11:07 UTC
Created attachment 58134 [details]
output of DISPLAY=:0.1 glxinfo
Comment 3 Alex Deucher 2012-03-07 11:36:17 UTC
Please attach your xorg log.
Comment 4 Alex Deucher 2012-03-07 11:37:31 UTC
And dmesg output.
Comment 5 diego.abelenda 2012-03-07 11:54:58 UTC
Created attachment 58137 [details]
dmesg after xorg start (fresh reboot)
Comment 6 diego.abelenda 2012-03-07 11:55:55 UTC
Created attachment 58138 [details]
Xorg log after start
Comment 7 diego.abelenda 2012-03-07 12:21:00 UTC
Created attachment 58140 [details]
glxinfo when only the radeon card is present

glxinfo output after unplugging the nvidia card, not even changing the Xorg configuration.
Comment 8 diego.abelenda 2012-03-07 12:22:15 UTC
Created attachment 58142 [details]
Xorg log when only the radeon is present

Xorg log after unplugging the nvidia card, not changing the xorg configuration.
Comment 9 diego.abelenda 2012-03-07 12:35:15 UTC
Ah I just found out that changing the screen number on the configuration
changes the output of glxinfo.

So if I have

Screen 0 "screen-nv"
Screen 1 "screen-ra" LeftOf "screen-nv"

glxinfo gives me "nouveau" for both screens.

But if I have
Screen 1 "screen-nv"
Screen 0 "screen-ra" LeftOf "screen-nv"

glxinfo gives me "Gallium 0.4 on AMD SUMO" for both screens.
Comment 10 diego.abelenda 2012-03-07 13:19:00 UTC
First report was with mesa-7.11 but after an update to 8.0.1 I get the same thing.
Comment 11 Brian Paul 2012-03-07 13:44:33 UTC
What's the output of glxinfo if you set DISPLAY=":0"?  Does it list both screens one after the other?

Also, please try "glxinfo -b" with DISPLAY=":0.0" and ":0.1".


Otherwise, I think the bug might be in glxinfo itself.

Here's the code to loop over the screens:

      numScreens = ScreenCount(dpy);
      print_display_info(dpy);
      for (scrnum = 0; scrnum < numScreens; scrnum++) {

For display=":0.1" I have a feeling that numScreens = 1 and scrnum is always zero so we're only querying the 0th screen.

I'll attach a patch to glxinfo for you to try.
Comment 12 Brian Paul 2012-03-07 13:45:43 UTC
Created attachment 58147 [details] [review]
try to fix screen indexing in glxinfo

Can you try applying this patch to glxinfo and see if it helps?  glxinfo is in the Mesa demos repository in src/xdemos/glxinfo.c
Comment 13 diego.abelenda 2012-03-08 10:48:23 UTC
Ok,
So when I start "DISPLAY=:0 glxinfo" I get both screens first the nouveau screen (0) then the radeon one (1).
when I start "DISPLAY=:0.0 glxinfo -b" I get "33"
when I start "DISPLAY=:0.1 glxinfo -b" I get "33"
with the patch applied when I do "DISPLAY=:0.0 glxinfo" I get both screens listed (correctly just as before when I used DISPLAY=:0). In fact it is nearly the same output as "DISPLAY=:0 glxinfo" except for the first line where after "name of display" it shows ":0" or ":0.0" Was it intended ?

(personnally if I ask for one specific screen I don't care about the other ones... but it is true that when starting glxinfo without changing DISPLAY variable it gets as default value the current screen I you can't tell if there are others, so I guess it is ok this way)
Comment 14 GitLab Migration User 2019-09-18 17:44:16 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/mesa/mesa/issues/84.


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.