Page 4 of 4 FirstFirst ... 234
Results 31 to 36 of 36

Thread: Information about Nvidia optimus support

  1. #31
    Join Date
    Aug 2008
    Beans
    39

    Re: Information about Nvidia optimus support

    Hi All,

    Thanks very much to pogopuschel, for the most recent guide on reply 20! This seems to have worked for me! at least the compiling xorg part.

    It seems I can now set the provider and use DRI_PRIME to get the appropriate output from glxinfo. here is an excerpt:

    Code:
    matthew@sibelius:~/Sources/prime/xprime/bin$ ./xrandr --listproviders
    Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
    LVDS1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 382mm x 215mm
       1920x1080      60.0*+   59.9  
       1680x1050      60.0     59.9  
       1600x1024      60.2  
       1400x1050      60.0  
       1280x1024      60.0  
       1440x900       59.9  
       1280x960       60.0  
       1360x768       59.8     60.0  
       1152x864       60.0  
       1024x768       60.0  
       800x600        60.3     56.2  
       640x480        59.9  
    VGA1 disconnected (normal left inverted right x axis y axis)
    HDMI1 disconnected (normal left inverted right x axis y axis)
    DP1 disconnected (normal left inverted right x axis y axis)
    Providers: number : 2 
    Provider 0: id: 137 cap: b nc: 3 no: 4 nap 0 name:Intel
    Provider 1: id: 98 cap: 5 nc: 2 no: 1 nap 0 name:nouveau
    matthew@sibelius:~/Sources/prime/xprime/bin$ ./xrandr --setprovideroffloadsink 98 137 
    matthew@sibelius:~/Sources/prime/xprime/bin$ glxinfo | grep render
    direct rendering: Yes 
    OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile 
        GL_NV_conditional_render, GL_AMD_draw_buffers_blend, 
    matthew@sibelius:~/Sources/prime/xprime/bin$ DRI_PRIME=1 glxinfo | grep render
    direct rendering: Yes 
    OpenGL renderer string: Gallium 0.4 on NVCE
        GL_NV_conditional_render, GL_AMD_conservative_depth,
    Very nice! It should however be noted that it takes a very long time for the nvidia glxinfo command to return.

    However I now try to run glxgears for both intel and nouveau.
    With intel, it works fine and produces the following output when I kill glxgears:

    Code:
    XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"^M
          after 318 requests (318 known processed) with 0 events remaining.^M
    Running synchronized to the vertical refresh.  The framerate should be
    approximately the same as the monitor refresh rate.
    Now when I try with my nvidia chip, I get a weird garbled glxgears window for a little bit, when then crashes with a segfault. the log output is:

    Code:
    nouveau: kernel rejected pushbuf: Invalid argument
    nouveau: ch2: krec 0 pushes 1 bufs 0 relocs 0
    The backtrace which appeared in dmesg is:

    Code:
    [  436.024137] [drm] nouveau 0000:01:00.0: PFIFO: unknown status 0x00000100
    [  436.024141] [drm] nouveau 0000:01:00.0: PFIFO: unknown status 0x40000000
    [  438.023137] [drm] nouveau 0000:01:00.0: PFIFO - playlist update failed
    [  499.093183] [drm] nouveau 0000:01:00.0: Failed to idle channel 2.
    [  502.091648] [drm] nouveau 0000:01:00.0: Failed to idle channel 2.
    [  505.090110] [drm] nouveau 0000:01:00.0: Failed to idle channel 2.
    [  508.088574] [drm] nouveau 0000:01:00.0: Failed to idle channel 2.
    [  510.087648] [drm] nouveau 0000:01:00.0: 0x2634 != chid: 0x00100002
    [  510.087733] [drm] nouveau 0000:01:00.0: PFIFO: unknown status 0x00000100
    [  512.086736] [drm] nouveau 0000:01:00.0: PFIFO - playlist update failed
    [  560.930086] [drm] nouveau 0000:01:00.0: PFIFO: unknown status 0x00000100
    [  562.929059] [drm] nouveau 0000:01:00.0: PFIFO - playlist update failed
    [  568.993975] [drm] nouveau 0000:01:00.0: push 0 buffer not in list
    [  568.994113] show_signal_msg: 30 callbacks suppressed
    [  568.994118] glxgears[2754]: segfault at 1000000000 ip 00007fba34beb460 sp 00007fffe51cf620 error 4 in libdrm_nouveau.so.2.0.0[7fba34be9000+5000]
    [  572.811376] [drm] nouveau 0000:01:00.0: Failed to idle channel 2.
    [  574.810531] [drm] nouveau 0000:01:00.0: 0x2634 != chid: 0x00100002
    [  574.810624] [drm] nouveau 0000:01:00.0: PFIFO: unknown status 0x00000100
    [  576.809623] [drm] nouveau 0000:01:00.0: PFIFO - playlist update failed
    So, Progress! However I'm not sure exactly who is to blame here. my gut tells me it's nouveau and that this is the result of my card not being supported. However I don't know if this kind of error is the result of me doing something slightly wrong.

    Please let me know your thoughts!

  2. #32
    Join Date
    Aug 2008
    Beans
    39

    Re: Information about Nvidia optimus support

    Strange, I'm getting varied results.

    I tried it again a second ago, and no crash, but my computer basically slowed to a crawl while displaying the garbled glxgears screen and ran for a while before I killed it.

    Here was the output.

    Code:
    matthew@sibelius:~$ DRI_PRIME=1 glxgears
    Running synchronized to the vertical refresh.  The framerate should be
    approximately the same as the monitor refresh rate.
    206 frames in 6.6 seconds = 31.277 FPS
    2 frames in 6.0 seconds =  0.333 FPS
    2 frames in 6.0 seconds =  0.333 FPS
    2 frames in 6.0 seconds =  0.333 FPS
    2 frames in 6.0 seconds =  0.333 FPS
    ^C
    So.. I guess it doesn't crash all the time? I'll try to get a screenshot of the glxgears screen.

    EDIT:

    Okay I tried it again, but instead of a garbled glxgears screen, I got a glxgears window with just black inside. I tried to get the screenshot, but the result was simply blackness.

    In anycase, it seems to 'work' without crashing, but without actually drawing anything and at an absolutely unworkable framerate just look at the statistics from the glxgears run above.

    Also it seems to slow all other graphics production down. I had to switch to a tty terminal to kill the glxgears because xorg wasn't refreshing my cursor once the forwarding began.
    Last edited by Mahler122; September 10th, 2012 at 09:45 PM. Reason: Extra information

  3. #33
    Join Date
    May 2007
    Beans
    98
    Distro
    Ubuntu

    Re: Information about Nvidia optimus support

    Quote Originally Posted by Mahler122 View Post
    Okay I tried it again, but instead of a garbled glxgears screen, I got a glxgears window with just black inside. I tried to get the screenshot, but the result was simply blackness.
    Does resizing the window help? I always get a black screen when I first run something on the nouveau card (and nouveau floods the syslog with PGRAPH errors), but resizing it smaller or bigger even slightly fixes the problem.

    My tests with glxspheres, which comes with virtualgl in the bumblebee package, showed that the nouveau card is a bit faster than the intel card, but not hugely. I get 120-130 fps with intel if I turn off vsync by setting the env var vblank_mode=0 and maybe 150 fps with nouveau.

  4. #34
    Join Date
    Aug 2012
    Beans
    35

    Re: Information about Nvidia optimus support

    @Mahler122

    If resizing windows does not help...
    ...maybe your problems are due to you are running a NVCE, a Kepler GPU, which are not pretty good supported by nouveau atm.
    Suggest to jump in irc channel #nouveau and ask the devs directly, showing your kern.log, maybe you can help them fixing the issue.
    Last edited by pogopuschel; September 11th, 2012 at 02:20 PM. Reason: + link phoronix

  5. #35
    Join Date
    Aug 2008
    Beans
    39

    Re: Information about Nvidia optimus support

    Quote Originally Posted by pogopuschel View Post
    If resizing windows does not help...
    ...maybe your problems are due to you are running a NVCE, a Kepler GPU, which are not pretty good supported by nouveau atm.
    Suggest to jump in irc channel #nouveau and ask the devs directly, showing your kern.log, maybe you can help them fixing the issue.
    The resizing did not help. I'm going to try asking the devs.

  6. #36
    Join Date
    Dec 2008
    Beans
    23

    Re: Information about Nvidia optimus support

    An stupid question.
    How to turn the "DRI_PRIME=1" default in quantal environment?
    More specific in unity/compiz?

Page 4 of 4 FirstFirst ... 234

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •