beam position problem under linux

1
I'm wondering if anyone has had success with the  ScreenToHead settings under linux using a recent Nvidia card.

I'm running an Nvidia GTX 670 under Ubuntu 12.04 (gnome classic- no effects) with the low latency kernel and the latest nvidia drivers (302.17). despite switching the cable between the DVI outputs on the card, and trying several permutations of values to ScreenToHead, I can't get precise timing.

Is this card too new? It's unrecognized, but PTB-INFO reports that beamposition timestamping is enabled.
I'm pasting the output from octave below, and the results are the same with Matlab.

Thanks!
-Adam

PTB-INFO: Display ':0.0' : X-Screen 0 : Output 0 [DVI-I-0]: Primary output : Off
line : CRTC -1 [XID 0]
PTB-INFO: Display ':0.0' : X-Screen 0 : Output 1 [DVI-I-1]: Secondary output : Connected : CRTC 0 [XID 633]
PTB-INFO: Display ':0.0' : X-Screen 0 : Output 2 [HDMI-0]: Secondary output : Offline : CRTC -1 [XID 0]
PTB-INFO: Display ':0.0' : X-Screen 0 : Output 3 [DP-0]: Secondary output : Offline : CRTC -1 [XID 0]
PTB-INFO: Display ':0.0' : X-Screen 0 : Output 4 [DVI-D-0]: Secondary output : Offline : CRTC -1 [XID 0]
PTB-INFO: Display ':0.0' : X-Screen 0 : Output 5 [DP-1]: Secondary output : Offline : CRTC -1 [XID 0]
PTB-INFO: Display ':0.0' : X-Screen 0 : Assigning primary output as 1 with RandR-CRTC 0 and GPU-CRTC 0.
PsychGPUControl:FullScreenWindowDisablesCompositor: Desktop composition for fullscreen windows on screen 0 disabled.
rc =

   0   0

ans =

   0
   0

Will draw 200 gabor patches per frame.


PTB-INFO: This is Psychtoolbox-3 for GNU/Linux X11, under GNU/Octave-3 (Version 3.0.9 - Build date: May 23 2012).
PTB-INFO: Type 'PsychtoolboxVersion' for more detailed version information.
PTB-INFO: Most parts of the Psychtoolbox distribution are licensed to you under terms of the MIT License, with
PTB-INFO: some restrictions. See file 'License.txt' in the Psychtoolbox root folder for the exact licensing conditions.

PTB-INFO: NVIDIA Corporation - (null) GPU found. Trying to establish low-level access...
PTB-DEBUG: Unknown NVidia chipset 0x0e4090a2
PTB-INFO: Connected to NVidia (null) GPU of NV-00 family. Beamposition timestamping enabled.

WARNING: Querying rasterbeam-position doesn't work on your setup! (Returns a constant value 4352)
WARNING: This can happen if Psychtoolbox gets the mapping of connected displays to graphics card
WARNING: outputs wrong. See 'help DisplayOutputMappings' for tips on how to resolve this problem.


WARNING: Couldn't determine end-line of vertical blanking interval for your display! Trouble with beamposition queries?!?

WARNING: Detected end-line is -1, which is either lower or more than 25% higher than vbl startline 1050 --> Out of sane range!


PTB-INFO: OpenGL-Renderer is NVIDIA Corporation :: GeForce GTX 670/PCIe/SSE2 :: 4.2.0 NVIDIA 302.17
PTB-INFO: VBL startline = 1050 , VBL Endline = -1
PTB-INFO: Beamposition queries unsupported or defective on this system. Using basic timestamping as fallback: Timestamps returned by Screen('Flip') will be less robust and accurate.
PTB-INFO: Measured monitor refresh interval from VBLsync = 8.336678 ms [119.951863 Hz]. (50 valid samples taken, stddev=0.040541 ms.)
PTB-INFO: Reported monitor refresh interval from operating system = 8.333542 ms [119.997002 Hz].
PTB-INFO: Small deviations between reported values are normal and no reason to worry.
:

2
--- In psychtoolbox@yahoogroups.com, "Naples, Adam" <adam.naples@...> wrote:
>
> Thanks!
> I'm running 64 bit octave and matlab.

Good choice. Get an updated Screen.mex for 64-Bit octave from:

<https://github.com/kleinerm/Psychtoolbox-3/blob/4222dca0c8540abdfd8c83769157e790188651d5/Psychtoolbox/PsychBasic/Octave3LinuxFiles64/Screen.mex?raw=true>

Let's see what happens.
-mario

> If I was going to downgrade for accurate timing what would you suggest? A fermi based card or should I go AMD?
> Thanks again.
> -a
>
> From: Mario <mario.kleiner@...<mailto:mario.kleiner@...>>
> Reply-To: "psychtoolbox@yahoogroups.com<mailto:psychtoolbox@yahoogroups.com>" <psychtoolbox@yahoogroups.com<mailto:psychtoolbox@yahoogroups.com>>
> Date: Friday, July 6, 2012 3:24 PM
> To: "psychtoolbox@yahoogroups.com<mailto:psychtoolbox@yahoogroups.com>" <psychtoolbox@yahoogroups.com<mailto:psychtoolbox@yahoogroups.com>>
> Subject: [psychtoolbox] Re: beam position problem under linux
>
>
>
>
> --- In psychtoolbox@yahoogroups.com<mailto:psychtoolbox%40yahoogroups.com>, "Naples, Adam" <adam.naples@> wrote:
> >
> > I'm wondering if anyone has had success with the ScreenToHead settings under linux using a recent Nvidia card.
> >
> > I'm running an Nvidia GTX 670 under Ubuntu 12.04 (gnome classic- no effects) with the low latency kernel and the latest nvidia drivers (302.17). despite switching the cable between the DVI outputs on the card, and trying several permutations of values to ScreenToHead, I can't get precise timing.
> >
> > Is this card too new? It's unrecognized, but PTB-INFO reports that beamposition timestamping is enabled.
>
> Yes, it is too new. The card isn't recognized by the latest PTB, so it makes an educated and wrong guess about how to perform beamposition queries.
>
> Is your octave 32 bit or 64 bit? I could update the detection code relatively quickly, so it at least chooses the right code path. However, we don't know yet if the current implementation will work at all on the latest NVidia generation "Kepler" GPU's, because NVidia changed the display engines quite a bit to add support for more than 2 displays. But worth a try.
>
> -mario
>
> > I'm pasting the output from octave below, and the results are the same with Matlab.
> >
> > Thanks!
> > -Adam
> >
> > PTB-INFO: Display ':0.0' : X-Screen 0 : Output 0 [DVI-I-0]: Primary output : Off
> > line : CRTC -1 [XID 0]
> > PTB-INFO: Display ':0.0' : X-Screen 0 : Output 1 [DVI-I-1]: Secondary output : Connected : CRTC 0 [XID 633]
> > PTB-INFO: Display ':0.0' : X-Screen 0 : Output 2 [HDMI-0]: Secondary output : Offline : CRTC -1 [XID 0]
> > PTB-INFO: Display ':0.0' : X-Screen 0 : Output 3 [DP-0]: Secondary output : Offline : CRTC -1 [XID 0]
> > PTB-INFO: Display ':0.0' : X-Screen 0 : Output 4 [DVI-D-0]: Secondary output : Offline : CRTC -1 [XID 0]
> > PTB-INFO: Display ':0.0' : X-Screen 0 : Output 5 [DP-1]: Secondary output : Offline : CRTC -1 [XID 0]
> > PTB-INFO: Display ':0.0' : X-Screen 0 : Assigning primary output as 1 with RandR-CRTC 0 and GPU-CRTC 0.
> > PsychGPUControl:FullScreenWindowDisablesCompositor: Desktop composition for fullscreen windows on screen 0 disabled.
> > rc =
> >
> > 0 0
> >
> > ans =
> >
> > 0
> > 0
> >
> > Will draw 200 gabor patches per frame.
> >
> >
> > PTB-INFO: This is Psychtoolbox-3 for GNU/Linux X11, under GNU/Octave-3 (Version 3.0.9 - Build date: May 23 2012).
> > PTB-INFO: Type 'PsychtoolboxVersion' for more detailed version information.
> > PTB-INFO: Most parts of the Psychtoolbox distribution are licensed to you under terms of the MIT License, with
> > PTB-INFO: some restrictions. See file 'License.txt' in the Psychtoolbox root folder for the exact licensing conditions.
> >
> > PTB-INFO: NVIDIA Corporation - (null) GPU found. Trying to establish low-level access...
> > PTB-DEBUG: Unknown NVidia chipset 0x0e4090a2
> > PTB-INFO: Connected to NVidia (null) GPU of NV-00 family. Beamposition timestamping enabled.
> >
> > WARNING: Querying rasterbeam-position doesn't work on your setup! (Returns a constant value 4352)
> > WARNING: This can happen if Psychtoolbox gets the mapping of connected displays to graphics card
> > WARNING: outputs wrong. See 'help DisplayOutputMappings' for tips on how to resolve this problem.
> >
> >
> > WARNING: Couldn't determine end-line of vertical blanking interval for your display! Trouble with beamposition queries?!?
> >
> > WARNING: Detected end-line is -1, which is either lower or more than 25% higher than vbl startline 1050 --> Out of sane range!
> >
> >
> > PTB-INFO: OpenGL-Renderer is NVIDIA Corporation :: GeForce GTX 670/PCIe/SSE2 :: 4.2.0 NVIDIA 302.17
> > PTB-INFO: VBL startline = 1050 , VBL Endline = -1
> > PTB-INFO: Beamposition queries unsupported or defective on this system. Using basic timestamping as fallback: Timestamps returned by Screen('Flip') will be less robust and accurate.
> > PTB-INFO: Measured monitor refresh interval from VBLsync = 8.336678 ms [119.951863 Hz]. (50 valid samples taken, stddev=0.040541 ms.)
> > PTB-INFO: Reported monitor refresh interval from operating system = 8.333542 ms [119.997002 Hz].
> > PTB-INFO: Small deviations between reported values are normal and no reason to worry.
> > :
> >
>