HOWTO: 10 bpc laptop running Linux

1
Dear Mario and all,

We got the HP ZBook 15 Mobile Workstation. I have installed Ubuntu 14.04 LTS and Psychtoolbox from Neurodebian. I installed GNU Octave and MATLAB R2016b. 

I experienced several segfaults while testing out some demos shipped with Psychtoolbox in Octave, and Matlab also didn't work well; DotDemo didn't work with an error message (included in the information section below) with Matlab, while it worked without issues with Octave.

We are mostly interested in getting true 10 bpc performance out of this machine. I tried some methods to see if we get it by some methods recommended in psychtoolbox.org, and I think we not seem to have 10 bpc performance. Specifically, the output of Screen ReadNormalizedGammaTable showed up as 8, and AdditiveBlendingForLinearSuper positionTutorial('Native10Bit' ) showed Gabors in Octave then crashed with segmentation fault when I pressed ESC, while it simply didn't run at Matlab  (output from psychtoolbox included below).


I am including as much information as I can find in diagnosing 10 bpc performance out of this laptop. I imagine reading logs from email is not comfortable, so please copy them into your editor (I didn't want to attach a file in case this will get archived in the forum) then read them using your favorite filtering methods. Hopefully, all that is needed is some tweaks before we can get it. 

Below are some outputs coming from OS, Psychtoolbox, XOrg.*.log, get-edid, xrandr and lscpi etc.:

#  octave --version
GNU Octave, version 3.8.1

> PsychtoolboxVersion 
ans = 3.0.12 - Flavor: Debian package - psychtoolbox-3 (3.0.12.20160514.dfsg1-1~nd14. 04+1)
For more info visit:
http://neuro.debian.net/pkgs/ octave-psychtoolbox-3.html

#  lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty

​# cat /etc/apt/sources.list.d/ neurodebian.sources.list 
deb http://neuro.debian.net/debian data main contrib non-free
#deb-src http://neuro.debian.net/debian data main contrib non-free
deb http://neuro.debian.net/debian trusty main contrib non-free
#deb-src http://neuro.debian.net/debian trusty main contrib non-free
​
> [a,b] = Screen(' ReadNormalizedGammaTable',0)
a =

   0.00000   0.00000   0.00000
   0.00392   0.00392   0.00392
   0.00784   0.00784   0.00784
   0.01176   0.01176   0.01176
   0.01569   0.01569   0.01569
   0.01961   0.01961   0.01961
   0.02353   0.02353   0.02353
   0.02745   0.02745   0.02745
   0.03137   0.03137   0.03137
   0.03529   0.03529   0.03529
   0.03922   0.03922   0.03922
   0.04314   0.04314   0.04314
   0.04706   0.04706   0.04706
   0.05098   0.05098   0.05098
   0.05490   0.05490   0.05490
   0.05882   0.05882   0.05882
   0.06275   0.06275   0.06275
   0.06667   0.06667   0.06667
   0.07059   0.07059   0.07059
   0.07451   0.07451   0.07451
   0.07843   0.07843   0.07843
   0.08235   0.08235   0.08235
   0.08627   0.08627   0.08627
   0.09020   0.09020   0.09020
   0.09412   0.09412   0.09412
   0.09804   0.09804   0.09804
   0.10196   0.10196   0.10196
   0.10588   0.10588   0.10588
   0.10980   0.10980   0.10980
   0.11373   0.11373   0.11373
   0.11765   0.11765   0.11765
   0.12157   0.12157   0.12157
   0.12549   0.12549   0.12549
   0.12941   0.12941   0.12941
   0.13333   0.13333   0.13333
   0.13725   0.13725   0.13725
   0.14118   0.14118   0.14118
   0.14510   0.14510   0.14510
   0.14902   0.14902   0.14902
   0.15294   0.15294   0.15294
   0.15686   0.15686   0.15686
   0.16078   0.16078   0.16078
   0.16471   0.16471   0.16471
   0.16863   0.16863   0.16863
   0.17255   0.17255   0.17255
   0.17647   0.17647   0.17647
   0.18039   0.18039   0.18039
   0.18431   0.18431   0.18431
   0.18824   0.18824   0.18824
   0.19216   0.19216   0.19216
   0.19608   0.19608   0.19608
   0.20000   0.20000   0.20000
   0.20392   0.20392   0.20392
   0.20784   0.20784   0.20784
   0.21176   0.21176   0.21176
   0.21569   0.21569   0.21569
   0.21961   0.21961   0.21961
   0.22353   0.22353   0.22353
   0.22745   0.22745   0.22745
   0.23137   0.23137   0.23137
   0.23529   0.23529   0.23529
   0.23922   0.23922   0.23922
   0.24314   0.24314   0.24314
   0.24706   0.24706   0.24706
   0.25098   0.25098   0.25098
   0.25490   0.25490   0.25490
   0.25882   0.25882   0.25882
   0.26275   0.26275   0.26275
   0.26667   0.26667   0.26667
   0.27059   0.27059   0.27059
   0.27451   0.27451   0.27451
   0.27843   0.27843   0.27843
   0.28235   0.28235   0.28235
   0.28627   0.28627   0.28627
   0.29020   0.29020   0.29020
   0.29412   0.29412   0.29412
   0.29804   0.29804   0.29804
   0.30196   0.30196   0.30196
   0.30588   0.30588   0.30588
   0.30980   0.30980   0.30980
   0.31373   0.31373   0.31373
   0.31765   0.31765   0.31765
   0.32157   0.32157   0.32157
   0.32549   0.32549   0.32549
   0.32941   0.32941   0.32941
   0.33333   0.33333   0.33333
   0.33725   0.33725   0.33725
   0.34118   0.34118   0.34118
   0.34510   0.34510   0.34510
   0.34902   0.34902   0.34902
   0.35294   0.35294   0.35294
   0.35686   0.35686   0.35686
   0.36078   0.36078   0.36078
   0.36471   0.36471   0.36471
   0.36863   0.36863   0.36863
   0.37255   0.37255   0.37255
   0.37647   0.37647   0.37647
   0.38039   0.38039   0.38039
   0.38431   0.38431   0.38431
   0.38824   0.38824   0.38824
   0.39216   0.39216   0.39216
   0.39608   0.39608   0.39608
   0.40000   0.40000   0.40000
   0.40392   0.40392   0.40392
   0.40784   0.40784   0.40784
   0.41176   0.41176   0.41176
   0.41569   0.41569   0.41569
   0.41961   0.41961   0.41961
   0.42353   0.42353   0.42353
   0.42745   0.42745   0.42745
   0.43137   0.43137   0.43137
   0.43529   0.43529   0.43529
   0.43922   0.43922   0.43922
   0.44314   0.44314   0.44314
   0.44706   0.44706   0.44706
   0.45098   0.45098   0.45098
   0.45490   0.45490   0.45490
   0.45882   0.45882   0.45882
   0.46275   0.46275   0.46275
   0.46667   0.46667   0.46667
   0.47059   0.47059   0.47059
   0.47451   0.47451   0.47451
   0.47843   0.47843   0.47843
   0.48235   0.48235   0.48235
   0.48627   0.48627   0.48627
   0.49020   0.49020   0.49020
   0.49412   0.49412   0.49412
   0.49804   0.49804   0.49804
   0.50196   0.50196   0.50196
   0.50588   0.50588   0.50588
   0.50980   0.50980   0.50980
   0.51373   0.51373   0.51373
   0.51765   0.51765   0.51765
   0.52157   0.52157   0.52157
   0.52549   0.52549   0.52549
   0.52941   0.52941   0.52941
   0.53333   0.53333   0.53333
   0.53725   0.53725   0.53725
   0.54118   0.54118   0.54118
   0.54510   0.54510   0.54510
   0.54902   0.54902   0.54902
   0.55294   0.55294   0.55294
   0.55686   0.55686   0.55686
   0.56078   0.56078   0.56078
   0.56471   0.56471   0.56471
   0.56863   0.56863   0.56863
   0.57255   0.57255   0.57255
   0.57647   0.57647   0.57647
   0.58039   0.58039   0.58039
   0.58431   0.58431   0.58431
   0.58824   0.58824   0.58824
   0.59216   0.59216   0.59216
   0.59608   0.59608   0.59608
   0.60000   0.60000   0.60000
   0.60392   0.60392   0.60392
   0.60784   0.60784   0.60784
   0.61176   0.61176   0.61176
   0.61569   0.61569   0.61569
   0.61961   0.61961   0.61961
   0.62353   0.62353   0.62353
   0.62745   0.62745   0.62745
   0.63137   0.63137   0.63137
   0.63529   0.63529   0.63529
   0.63922   0.63922   0.63922
   0.64314   0.64314   0.64314
   0.64706   0.64706   0.64706
   0.65098   0.65098   0.65098
   0.65490   0.65490   0.65490
   0.65882   0.65882   0.65882
   0.66275   0.66275   0.66275
   0.66667   0.66667   0.66667
   0.67059   0.67059   0.67059
   0.67451   0.67451   0.67451
   0.67843   0.67843   0.67843
   0.68235   0.68235   0.68235
   0.68627   0.68627   0.68627
   0.69020   0.69020   0.69020
   0.69412   0.69412   0.69412
   0.69804   0.69804   0.69804
   0.70196   0.70196   0.70196
   0.70588   0.70588   0.70588
   0.70980   0.70980   0.70980
   0.71373   0.71373   0.71373
   0.71765   0.71765   0.71765
   0.72157   0.72157   0.72157
   0.72549   0.72549   0.72549
   0.72941   0.72941   0.72941
   0.73333   0.73333   0.73333
   0.73725   0.73725   0.73725
   0.74118   0.74118   0.74118
   0.74510   0.74510   0.74510
   0.74902   0.74902   0.74902
   0.75294   0.75294   0.75294
   0.75686   0.75686   0.75686
   0.76078   0.76078   0.76078
   0.76471   0.76471   0.76471
   0.76863   0.76863   0.76863
   0.77255   0.77255   0.77255
   0.77647   0.77647   0.77647
   0.78039   0.78039   0.78039
   0.78431   0.78431   0.78431
   0.78824   0.78824   0.78824
   0.79216   0.79216   0.79216
   0.79608   0.79608   0.79608
   0.80000   0.80000   0.80000
   0.80392   0.80392   0.80392
   0.80784   0.80784   0.80784
   0.81176   0.81176   0.81176
   0.81569   0.81569   0.81569
   0.81961   0.81961   0.81961
   0.82353   0.82353   0.82353
   0.82745   0.82745   0.82745
   0.83137   0.83137   0.83137
   0.83529   0.83529   0.83529
   0.83922   0.83922   0.83922
   0.84314   0.84314   0.84314
   0.84706   0.84706   0.84706
   0.85098   0.85098   0.85098
   0.85490   0.85490   0.85490
   0.85882   0.85882   0.85882
   0.86275   0.86275   0.86275
   0.86667   0.86667   0.86667
   0.87059   0.87059   0.87059
   0.87451   0.87451   0.87451
   0.87843   0.87843   0.87843
   0.88235   0.88235   0.88235
   0.88627   0.88627   0.88627
   0.89020   0.89020   0.89020
   0.89412   0.89412   0.89412
   0.89804   0.89804   0.89804
   0.90196   0.90196   0.90196
   0.90588   0.90588   0.90588
   0.90980   0.90980   0.90980
   0.91373   0.91373   0.91373
   0.91765   0.91765   0.91765
   0.92157   0.92157   0.92157
   0.92549   0.92549   0.92549
   0.92941   0.92941   0.92941
   0.93333   0.93333   0.93333
   0.93725   0.93725   0.93725
   0.94118   0.94118   0.94118
   0.94510   0.94510   0.94510
   0.94902   0.94902   0.94902
   0.95294   0.95294   0.95294
   0.95686   0.95686   0.95686
   0.96078   0.96078   0.96078
   0.96471   0.96471   0.96471
   0.96863   0.96863   0.96863
   0.97255   0.97255   0.97255
   0.97647   0.97647   0.97647
   0.98039   0.98039   0.98039
   0.98431   0.98431   0.98431
   0.98824   0.98824   0.98824
   0.99216   0.99216   0.99216
   0.99608   0.99608   0.99608
   1.00000   1.00000   1.00000

b =  8

# octave --eval 'DotDemo'
warning: function ./Speak.m shadows a core library function
GNU Octave, version 3.8.1
Copyright (C) 2014 John W. Eaton and others.
This is free software; see the source code for copying conditions.
There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE.  For details, type 'warranty'.

Octave was configured for "x86_64-pc-linux-gnu".

Additional information about Octave is available at http://www.octave.org.

Please contribute if you find this software useful.
For more information, visit http://www.octave.org/get- involved.html

Read http://www.octave.org/bugs. html to learn how to submit bug reports.
For information about changes from previous versions, type 'news'.

warning: function /usr/share/octave/packages/ strings-1.1.0/base64decode.m shadows a core library function
warning: function /usr/share/octave/packages/ strings-1.1.0/base64encode.m shadows a core library function
warning: function /usr/share/octave/packages/ strings-1.1.0/strjoin.m shadows a core library function
warning: dx does not seem to be present some functionalities will be disabled
PTB-INFO: Display ':0' : X-Screen 0 : Assigning primary output as 0 with RandR-CRTC 0 and GPU-CRTC 0.


PTB-INFO: This is Psychtoolbox-3 for GNU/Linux X11, under GNU/Octave 64-Bit (Version 3.0.12 - Build date: May 16 2016).
PTB-INFO: Support status on this operating system release: Linux 3.13.0-105-generic Supported.
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: Advanced Micro Devices, Inc. [AMD/ATI] - Bonaire XT [Radeon R9 M280X] GPU found. Trying to establish low-level access...
PTB-INFO: Connected to Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon R9 M280X] GPU with DCE-8.0 display engine [2 heads]. Beamposition timestamping enabled.


PTB-INFO: OpenGL-Renderer is ATI Technologies Inc. :: AMD Radeon R9 M280X :: 4.5.13399 Compatibility Profile Context FireGL 14.30
PTB-INFO: VBL startline = 1080 , VBL Endline = 1109
PTB-INFO: Measured monitor refresh interval from beamposition = 16.661245 ms [60.019524 Hz].
PTB-INFO: Will use beamposition query for accurate Flip time stamping.
PTB-INFO: Measured monitor refresh interval from VBLsync = 16.649141 ms [60.063158 Hz]. (50 valid samples taken, stddev=0.095508 ms.)
PTB-INFO: Reported monitor refresh interval from operating system = 16.661390 ms [60.019001 Hz].
PTB-INFO: Small deviations between reported values are normal and no reason to worry.
minsmooth =  1
maxsmooth =  8192
 

INFO: PTB's Screen('Flip', 10) command seems to have missed the requested stimulus presentation deadline
INFO: a total of 3 times out of a total of 36 flips during this session.

INFO: This number is fairly accurate (and indicative of real timing problems in your own code or your system)
INFO: if you provided requested stimulus onset times with the 'when' argument of Screen('Flip', window [, when]);
INFO: If you called Screen('Flip', window); without the 'when' argument, this count is more of a ''mild'' indicator
INFO: of timing behaviour than a hard reliable measurement. Large numbers may indicate problems and should at least
INFO: deserve your closer attention. Cfe. 'help SyncTrouble', the FAQ section at www.psychtoolbox.org and the
INFO: examples in the PDF presentation in PsychDocumentation/ Psychtoolbox3-Slides.pdf for more info and timing tips.

>> DotDemo  % in matlab
PTB-INFO: Display ':0' : X-Screen 0 : Assigning primary output as 0 with RandR-CRTC 0 and GPU-CRTC 0.


PTB-INFO: This is Psychtoolbox-3 for GNU/Linux X11, under Matlab 64-Bit (Version 3.0.12 - Build date: May 13 2016).
PTB-INFO: Support status on this operating system release: Linux 3.13.0-105-generic Supported.
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: Advanced Micro Devices, Inc. [AMD/ATI] - Bonaire XT [Radeon R9 M280X] GPU found. Trying to establish low-level access...
PTB-INFO: Connected to Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon R9 M280X] GPU with DCE-8.0 display engine [2 heads]. Beamposition timestamping enabled.


PTB-INFO: OpenGL-Renderer is ATI Technologies Inc. :: AMD Radeon R9 M280X :: 2.1 (4.5.13399 Compatibility Profile Context FireGL 14.30)
PTB-INFO: VBL startline = 1080 , VBL Endline = 1109
PTB-INFO: Measured monitor refresh interval from beamposition = 16.661284 ms [60.019384 Hz].
PTB-INFO: Will use beamposition query for accurate Flip time stamping.
PTB-INFO: Measured monitor refresh interval from VBLsync = 16.647482 ms [60.069145 Hz]. (50 valid samples taken, stddev=0.186439 ms.)
PTB-INFO: Reported monitor refresh interval from operating system = 16.661390 ms [60.019001 Hz].
PTB-INFO: Small deviations between reported values are normal and no reason to worry.
PTB-WARNING: GPU reports that pageflipping isn't used - or under our control - for Screen('Flip')! [pflip_status = 0]
PTB-WARNING: Returned Screen('Flip') timestamps might be wrong! Please fix this now (read 'help SyncTrouble').
PTB-WARNING: GPU reports that pageflipping isn't used - or under our control - for Screen('Flip')! [pflip_status = 0]
PTB-WARNING: Returned Screen('Flip') timestamps might be wrong! Please fix this now (read 'help SyncTrouble').
PTB-WARNING: GPU reports that pageflipping isn't used - or under our control - for Screen('Flip')! [pflip_status = 0]
PTB-WARNING: Returned Screen('Flip') timestamps might be wrong! Please fix this now (read 'help SyncTrouble').
PTB-WARNING: GPU reports that pageflipping isn't used - or under our control - for Screen('Flip')! [pflip_status = 0]
PTB-WARNING: Returned Screen('Flip') timestamps might be wrong! Please fix this now (read 'help SyncTrouble').

minsmooth =

     1


maxsmooth =

        8192

PTB-WARNING: GPU reports that pageflipping isn't used - or under our control - for Screen('Flip')! [pflip_status = 0]
PTB-WARNING: Returned Screen('Flip') timestamps might be wrong! Please fix this now (read 'help SyncTrouble').
Error in function DrawDots: Usage error
Point smoothing unsupported on your system and our shader based implementation failed as well in Screen('DrawDots').
>> 

>> AdditiveBlendingForLinearSuper positionTutorial('Native10Bit' )


PTB-INFO: This is Psychtoolbox-3 for GNU/Linux X11, under Matlab 64-Bit (Version 3.0.12 - Build date: May 13 2016).
PTB-INFO: Support status on this operating system release: Linux 3.13.0-105-generic Supported.
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: Advanced Micro Devices, Inc. [AMD/ATI] - Bonaire XT [Radeon R9 M280X] GPU found. Trying to establish low-level access...
PTB-INFO: Connected to Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon R9 M280X] GPU with DCE-8.0 display engine [2 heads]. Beamposition timestamping enabled.
PTB-INFO: Trying to enable at least 10 bpc fixed point framebuffer.
PTB-INFO: Native 10 bit per color framebuffer requested, but the OS doesn't allow it. It only provides 8 bpc.
PTB-INFO: Will now try to use our own high bit depth setup code as an alternative approach to fullfill your needs.
PTB-INFO: Assuming kernel driver provided color resolution of the GPU framebuffer will be 10 bits per RGB color component.


PTB-INFO: OpenGL-Renderer is ATI Technologies Inc. :: AMD Radeon R9 M280X :: 2.1 (4.5.13399 Compatibility Profile Context FireGL 14.30)
PTB-INFO: VBL startline = 1080 , VBL Endline = 1109
PTB-INFO: Measured monitor refresh interval from beamposition = 16.661264 ms [60.019454 Hz].
PTB-INFO: Will use beamposition query for accurate Flip time stamping.
PTB-INFO: Measured monitor refresh interval from VBLsync = 16.649923 ms [60.060337 Hz]. (50 valid samples taken, stddev=0.169034 ms.)
PTB-INFO: Reported monitor refresh interval from operating system = 16.661390 ms [60.019001 Hz].
PTB-INFO: Small deviations between reported values are normal and no reason to worry.
PTB-INFO: System framebuffer switched to ARGB2101010 mode for screen 0 [head 0].
PTB-INFO: Psychtoolbox imaging pipeline starting up for window with requested imagingmode 5125 ...
PTB-INFO: Will use 32 bits per color component floating point framebuffer for stimulus drawing. Alpha blending should work correctly.
PTB-INFO: Will use 32 bits per color component floating point framebuffer for stimulus post-processing (if any).
PTB-WARNING: GPU reports that pageflipping isn't used - or under our control - for Screen('Flip')! [pflip_status = 0]
PTB-WARNING: Returned Screen('Flip') timestamps might be wrong! Please fix this now (read 'help SyncTrouble').
PTB-WARNING: GPU reports that pageflipping isn't used - or under our control - for Screen('Flip')! [pflip_status = 0]
PTB-WARNING: Returned Screen('Flip') timestamps might be wrong! Please fix this now (read 'help SyncTrouble').
PTB-WARNING: GPU reports that pageflipping isn't used - or under our control - for Screen('Flip')! [pflip_status = 0]
PTB-WARNING: Returned Screen('Flip') timestamps might be wrong! Please fix this now (read 'help SyncTrouble').
PTB-WARNING: GPU reports that pageflipping isn't used - or under our control - for Screen('Flip')! [pflip_status = 0]
PTB-WARNING: Returned Screen('Flip') timestamps might be wrong! Please fix this now (read 'help SyncTrouble').
PTB-WARNING: GPU reports that pageflipping isn't used - or under our control - for Screen('Flip')! [pflip_status = 0]
PTB-WARNING: Returned Screen('Flip') timestamps might be wrong! Please fix this now (read 'help SyncTrouble').
PTB-INFO: System framebuffer switched to standard ARGB8888 mode for screen 0 [head 0].
Error using AssertGLSL (line 37)
Sorry, this M-File cannot execute on your combination of graphics hardware and driver due to complete
lack of GLSL support.

Error in AssertGLSL (line 37)
    error('Sorry, this M-File cannot execute on your combination of graphics hardware and driver due to
    complete lack of GLSL support.');


Error in LoadShaderFromFile (line 33)
AssertGLSL;

Error in PsychColorCorrection (line 578)
            icmShaders = LoadShaderFromFile(' ICMSimpleGammaCorrectionShader .frag.txt', [], debuglevel);

Error in PsychImaging>PostConfiguration (line 3879)
            [icmshader icmstring icmconfig icmoverrideMain] =
            PsychColorCorrection(' GetCompiledShaders', win, 1);

Error in PsychImaging (line 2161)
    PostConfiguration(reqs, win, clearcolor, slavewin);

Error in AdditiveBlendingForLinearSuper positionTutorial (line 357)
    [w, wRect]=PsychImaging(' OpenWindow', screenNumber, 0.5, lrect);
 

# get-edid | parse-edid
This is read-edid version 3.0.1. Prepare for some fun.
Attempting to use i2c interface
Looks like no busses have an EDID. Sorry!
Attempting to use the classical VBE interface

Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
Function supported
Call successful

VBE version 300
VBE string at 0xc0248 "AMD ATOMBIOS"

VBE/DDC service about to be called
Report DDC capabilities

Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0

(Message over 64 KB, truncated)
2
Hi,

first you should upgrade to Ubuntu 16.04-LTS. No good reason to use an outdated 14.04 anymore on a new laptop. That will also give you a more recent Octave-4 as bonus. Also absolutely get rid of that proprietary Catalyst driver. PTB hasn't been tested on Catalyst since at least 8 years. We always want to use the open-source drivers whenever possible. The 10 bpc mode has only been tested on the open-source standard driver that already comes installed by default - Linux 3.16 and later support it in principle, so 3.13 of your Ubuntu 14.04 would be too old, but 4.4 of Ubuntu 16.04 is fine. Then you'll need the latest PTB from us. The Neurodebian version is currently very outdated, over 8 months and 3 releases behind. I made improvements for 10 bpc setup on AMD and to the instructions sometime in the last few months, which are all missing in the ND version atm. the bit depth output from 'ReadNormalizedGammatable' is meaningless on Linux and Windows - always returns hard-coded 8 bpc as a safe answer. It was probably a bad idea to not return zero instead to signal that that info is unknown. On OSX where that used to give reasonable results in the good old past, i suspect the info returned by the OS is now more often than not just bogus - Apple  worked hard the last few years to sabotage that reporting.

The 'matlab-support' package should have taken care of fixing bugs in Matlab which impair compatibility, assuming Matlab was installed before the ptb from neurodebian? However, Octave-4 should be pretty sufficient for running most PTB scripts.

The recent PTB beta will install a config file during execution of PsychLinuxConfiguration to enable 10 bpc mode in the driver for supported displays - after a reboot. Verifying if the driver thinks it set up 10 bpc mode is an extra  step once you've done all the above. After that, verifying if the display does really output 10 bpc will require a photometer etc.

But first things first.
-mario
3
Dear Mario,

Thank you so much for the helpful suggestions. I was using the old OS because it was shipped with the Laptop from factory, and I thought maybe it contained some kernel patches, drivers and some dark magic from HP, and didn't want to lose those. I upgraded it. Except the Fn keys for screen luminance does not actually change luminance (the HUD indicator for screen luminance does show up, though), everything seems to be working. 

Upgraded to Ubuntu 16.04.1 LTS, Octave 4.0.0 and PTB to the latest beta release, as well as the drivers. After running PsychLinuxConfiguration, I did several reboots. Astonishingly, PTB is complaining that it might be running within a Virtual Box. I guess, I need to install some graphics driver (I do have xserver-xorg-video-all installed though). 

Below are the output from `DotDemo`. Please advise what needs to be done so that we could actually run Psychtoolbox with 10 bpc support with this hardware and software setup.

p.s.: For anyone out there who also bought a Laptop that "comes" with Linux: please simply download a latest ISO image from Ubuntu directly, and install that (or better, go with Debian, another GNU Linux). This laptop was partitioned in a very insane way: /boot was FAT32, thus no hardlinks or symbolic linksk work there. That made the system upgrading almost feel like a manual drive in a jungle.

Command outputs:

> octave --no-gui --eval 'DotDemo'
warning: function /usr/share/octave/packages/plot-1.1.0/zoom.m shadows a core library function
warning: called from
    load_packages_and_dependencies at line 47 column 5
    load_packages at line 60 column 3
    pkg at line 422 column 7
    /usr/share/octave/4.0.0/m/startup/octaverc at line 22 column 1
PTB-INFO: Display ':0' : X-Screen 0 : Assigning primary output as 0 with RandR-CRTC 0 and GPU-CRTC 0.


PTB-INFO: This is Psychtoolbox-3 for GNU/Linux X11, under GNU/Octave 64-Bit (Version 3.0.13 - Build date: Dec  1 2016).
PTB-INFO: Support status on this operating system release: Linux 4.4.0-57-generic Supported.
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: Advanced Micro Devices, Inc. [AMD/ATI] - Bonaire XT [Radeon R9 M280X] GPU found. Trying to establish low-level access...
PTB-INFO: Connected to Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon R9 M280X] GPU with DCE-8.0 display engine [2 heads]. Beamposition timestamping enabled.
PTB-WARNING: Your graphics driver doesn't allow me to control syncing wrt. vertical retrace!
PTB-WARNING: Please update your display graphics driver as soon as possible to fix this.
PTB-WARNING: Until then, you can manually enable syncing to VBL somehow in a manner that is
PTB-WARNING: dependent on the type of gfx-card and driver. Google is your friend...


PTB-INFO: Seems like Psychtoolbox is running inside a Virtual Machine? This doesn't provide sufficient
PTB-INFO: visual stimulus timing precision for research grade visual stimulation. I will disable most
PTB-INFO: tests and calibrations so you can at least get your scripts running for demo purposes. Other
PTB-INFO: presentation modalities and various Psychtoolbox functions will only work with limited functionality
PTB-INFO: and precision. Only use this for demos and simple tests, not for real experiment sessions!

PTB-WARNING: At least one test call for OpenML OML_sync_control extension failed! Will disable OpenML and revert to fallback implementation.


PTB-INFO: OpenGL-Renderer is VMware, Inc. :: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) :: 3.0 Mesa 11.2.0
PTB-INFO: VBL startline = 1080 , 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 = 0.000000 ms [inf Hz]. (0 valid samples taken, stddev=0.000000 ms.)
PTB-INFO: Reported monitor refresh interval from operating system = 12.987182 ms [76.999001 Hz].
PTB-INFO: Small deviations between reported values are normal and no reason to worry.
PTB-INFO: All display tests and calibrations disabled. Assuming a refresh interval of 76.999001 Hz. Timing will be inaccurate!
minsmooth =  1
maxsmooth =  255
^[

INFO: PTB's Screen('Flip', 10) command seems to have missed the requested stimulus presentation deadline
INFO: a total of 4 times out of a total of 160 flips during this session.

INFO: This number is fairly accurate (and indicative of real timing problems in your own code or your system)
INFO: if you provided requested stimulus onset times with the 'when' argument of Screen('Flip', window [, when]);
INFO: If you called Screen('Flip', window); without the 'when' argument, this count is more of a ''mild'' indicator
INFO: of timing behaviour than a hard reliable measurement. Large numbers may indicate problems and should at least
INFO: deserve your closer attention. Cfe. 'help SyncTrouble', the FAQ section at www.psychtoolbox.org and the
INFO: examples in the PDF presentation in PsychDocumentation/Psychtoolbox3-Slides.pdf for more info and timing tips.



WARNING: This session of your experiment was run by you with the setting Screen('Preference', 'SkipSyncTests', 2).
WARNING: This means that some internal self-tests and calibrations were skipped. Your stimulus presentation timing
WARNING: may have been wrong. This is fine for development and debugging of your experiment, but for running the real
WARNING: study, please make sure to set Screen('Preference', 'SkipSyncTests', 0) for maximum accuracy and reliability.


# apt search xserver video|grep installed

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

xserver-xorg-video-all/xenial,now 1:7.7+13ubuntu3 amd64 [installed]
xserver-xorg-video-amdgpu/xenial,now 1.1.0-1 amd64 [installed,automatic]
xserver-xorg-video-ati/xenial,now 1:7.7.0-1 amd64 [installed]
xserver-xorg-video-cirrus/xenial,now 1:1.5.3-1ubuntu3 amd64 [installed]
xserver-xorg-video-fbdev/xenial,now 1:0.4.4-1build5 amd64 [installed]
xserver-xorg-video-intel/xenial-updates,now 2:2.99.917+git20160325-1ubuntu1.2 amd64 [installed,automatic]
xserver-xorg-video-mach64/xenial,now 6.9.5-1build2 amd64 [installed]
xserver-xorg-video-mga/xenial,now 1:1.6.4-1build2 amd64 [installed]
xserver-xorg-video-neomagic/xenial,now 1:1.2.9-1build2 amd64 [installed]
xserver-xorg-video-nouveau/xenial,now 1:1.0.12-1build2 amd64 [installed]
xserver-xorg-video-openchrome/xenial,now 1:0.3.3+git20160310-1 amd64 [installed]
xserver-xorg-video-qxl/xenial,now 0.1.4-3ubuntu3 amd64 [installed]
xserver-xorg-video-r128/xenial,now 6.10.0-1build2 amd64 [installed]
xserver-xorg-video-radeon/xenial,now 1:7.7.0-1 amd64 [installed]
xserver-xorg-video-savage/xenial,now 1:2.3.8-1ubuntu3 amd64 [installed]
xserver-xorg-video-siliconmotion/xenial,now 1:1.7.8-1ubuntu6 amd64 [installed]
xserver-xorg-video-sisusb/xenial,now 1:0.9.6-2build5 amd64 [installed]
xserver-xorg-video-tdfx/xenial,now 1:1.4.6-1build2 amd64 [installed]
xserver-xorg-video-trident/xenial,now 1:1.3.7-1build2 amd64 [installed]
xserver-xorg-video-vesa/xenial,now 1:2.3.4-1build2 amd64 [installed]
xserver-xorg-video-vmware/xenial,now 1:13.1.0-2ubuntu3 amd64 [installed]


# cat /proc/version
Linux version 4.4.0-57-generic (buildd@lgw01-54) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #78-Ubuntu SMP Fri Dec 9 23:50:32 UTC 2016

# octave --version
GNU Octave, version 4.0.0

> octave --no-gui --eval 'PsychtoolboxVersion'
ans = 3.0.13 - Flavor: beta - Corresponds to SVN Revision 8319

>> AdditiveBlendingForLinearSuperpositionTutorial('Native10Bit')  % in Octave
libptbdrawtext_ftgl: External 'DrawText' text rendering plugin initialized.
libptbdrawtext_ftgl: Maximum number of cacheable fonts is 40, minimum number of supported concurrent windows is 10.
libptbdrawtext_ftgl: This plugin uses multiple excellent free software libraries to do its work:
libptbdrawtext_ftgl: OGLFT (http://oglft.sourceforge.net/) the OpenGL-FreeType library.
libptbdrawtext_ftgl: The FreeType-2 (http://freetype.sourceforge.net/) library.
libptbdrawtext_ftgl: The FontConfig (http://www.fontconfig.org) library.
libptbdrawtext_ftgl: Thanks!

PTB-INFO: Display ':0' : X-Screen 0 : Assigning primary output as 0 with RandR-CRTC 0 and GPU-CRTC 0.


PTB-INFO: This is Psychtoolbox-3 for GNU/Linux X11, under GNU/Octave 64-Bit (Version 3.0.13 - Build date: Dec  1 2016).
PTB-INFO: Support status on this operating system release: Linux 4.4.0-57-generic Supported.
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: Advanced Micro Devices, Inc. [AMD/ATI] - Bonaire XT [Radeon R9 M280X] GPU found. Trying to establish low-level access...
PTB-INFO: Connected to Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon R9 M280X] GPU with DCE-8.0 display engine [2 heads]. Beamposition timestamping enabled.
PTB-INFO: Trying to enable at least 10 bpc fixed point framebuffer.
PTB-WARNING: Your graphics driver doesn't allow me to control syncing wrt. vertical retrace!
PTB-WARNING: Please update your display graphics driver as soon as possible to fix this.
PTB-WARNING: Until then, you can manually enable syncing to VBL somehow in a manner that is
PTB-WARNING: dependent on the type of gfx-card and driver. Google is your friend...
PTB-INFO: Native 10 bit per color framebuffer requested, but the OS doesn't allow it. It only provides 8 bpc.
PTB-INFO: Will now try to use our own high bit depth setup code as an alternative approach to fullfill your needs.
PTB-INFO: Assuming kernel driver provided color resolution of the GPU framebuffer will be 10 bits per RGB color component.


PTB-INFO: Seems like Psychtoolbox is running inside a Virtual Machine? This doesn't provide sufficient
PTB-INFO: visual stimulus timing precision for research grade visual stimulation. I will disable most
PTB-INFO: tests and calibrations so you can at least get your scripts running for demo purposes. Other
PTB-INFO: presentation modalities and various Psychtoolbox functions will only work with limited functionality
PTB-INFO: and precision. Only use this for demos and simple tests, not for real experiment sessions!

PTB-WARNING: At least one test call for OpenML OML_sync_control extension failed! Will disable OpenML and revert to fallback implementation.


PTB-INFO: OpenGL-Renderer is VMware, Inc. :: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) :: 3.0 Mesa 11.2.0
PTB-INFO: VBL startline = 1080 , 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 = 0.000000 ms [inf Hz]. (0 valid samples taken, stddev=0.000000 ms.)
PTB-INFO: Reported monitor refresh interval from operating system = 12.987182 ms [76.999001 Hz].
PTB-INFO: Small deviations between reported values are normal and no reason to worry.
PTB-INFO: All display tests and calibrations disabled. Assuming a refresh interval of 76.999001 Hz. Timing will be inaccurate!
PTB-INFO: System framebuffer switched to ARGB2101010 mode for screen 0 [head 0].
PTB-INFO: Psychtoolbox imaging pipeline starting up for window with requested imagingmode 5125 ...
PTB-INFO: Will use 32 bits per color component floating point framebuffer for stimulus drawing. Alpha blending should work correctly.
PTB-INFO: Will use 32 bits per color component floating point framebuffer for stimulus post-processing (if any).
Building a fragment shader:Reading shader from file /home/hyiltiz/Documents/Psychtoolbox/PsychOpenGL/PsychGLSLShaders/ICMSimpleGammaCorrectionShader.frag.txt ...
Compiling all shaders matching RGBMultiLUTLookupCombine_FormattingShader * into a GLSL program.
Building a fragment shader:Reading shader from file /home/hyiltiz/Documents/Psychtoolbox/PsychOpenGL/PsychGLSLShaders/RGBMultiLUTLookupCombine_FormattingShader.frag.txt ...
LoadIdentityClut: Info: Used GPU low-level setup code to configure (hopefully) perfect identity pixel passthrough.
Average redraw rate in demo was 14.309124 Hz.
Average update rate in pipeline was 25.209203 Hz.
PTB-INFO: System framebuffer switched to standard ARGB8888 mode for screen 0 [head 0].


INFO: PTB's Screen('Flip', 10) command seems to have missed the requested stimulus presentation deadline
INFO: a total of 26 times out of a total of 327 flips during this session.

INFO: This number is fairly accurate (and indicative of real timing problems in your own code or your system)
INFO: if you provided requested stimulus onset times with the 'when' argument of Screen('Flip', window [, when]);
INFO: If you called Screen('Flip', window); without the 'when' argument, this count is more of a ''mild'' indicator
INFO: of timing behaviour than a hard reliable measurement. Large numbers may indicate problems and should at least
INFO: deserve your closer attention. Cfe. 'help SyncTrouble', the FAQ section at www.psychtoolbox.org and the
INFO: examples in the PDF presentation in PsychDocumentation/Psychtoolbox3-Slides.pdf for more info and timing tips.



WARNING: This session of your experiment was run by you with the setting Screen('Preference', 'SkipSyncTests', 2).
WARNING: This means that some internal self-tests and calibrations were skipped. Your stimulus presentation timing
WARNING: may have been wrong. This is fine for development and debugging of your experiment, but for running the real
WARNING: study, please make sure to set Screen('Preference', 'SkipSyncTests', 0) for maximum accuracy and reliability.



4
XX---In PSYCHTOOLBOX@yahoogroups.com, <hormet.yiltiz@...> wrote :

Dear Mario,

Thank you so much for the helpful suggestions. I was using the old OS because it was shipped with the Laptop from factory, and I thought maybe it contained some kernel patches, drivers and some dark magic from HP, and didn't want to lose those. I upgraded it. Except the Fn keys for screen luminance does not actually change luminance (the HUD indicator for screen luminance does show up, though), everything seems to be working. 

Upgraded to Ubuntu 16.04.1 LTS, Octave 4.0.0 and PTB to the latest beta release, as well as the drivers. After running PsychLinuxConfiguration, I did several reboots. Astonishingly, PTB is complaining that it might be running within a Virtual Box. I guess, I need to install some graphics driver (I do have xserver-xorg-video-all installed though). 

-> The Catalyst driver "fglrx" did not uninstall cleanly. I've seen the same problem on a machine here when people mistakenly installed it and then it didn't cleanly uninstall. Currently you are using the llvmpipe software renderer. Look into /etc/modprobe.d/ if there is some file with a filename containing fglrx or firegl or such and delete that file (maybe fglrx.blacklist or such?). Then reboot. That file prevents the open-source kernel driver from loading, therefore hw acceleration gets disabled. Might also explain the non-working backlight control for the panel.

The same folder should contain some amddeepcolor-psychtoolbox.conf file which will request 10 bpc output on deep color capable digital display devices.

Probably a good idea to also execute "sudo update-initramfs -u -k all" again, in case that is needed to pick up the removal of that fglrx config file into the initrd boot ram disc. Not sure if it is needed, but won't hurt. If everything worked you should see radeon listed in the "lsmod | grep radeon" output, and PTB should report "Gallium 0.4 on AMD Bonaire" or something like that instead of "llvmpipe".

cat /sys/modules/radeon/parameters/deep_color should return '1' for deep color support enabled.

Once that works, you can either reboot the machine with a special kernel command line option:

1. When the boot loader menu shows up, select "Advanced options", then the latest kernel, then "e" for edit boot options. Then you can append to the line that boots the linux kernel (where there are also options like "splash" and "quiet" this snippet "drm.debug=1". Then boot with F10.

or try to enable verbose graphics debug output at runtime:

1. sudo su
2. echo 1 > /sys/modules/drm/parameters/debug
3. Maybe use xrandr to query or switch display resolution in the hope this will trigger redetection of the displays capabilities.

After boot/enable of debug output the /var/log/syslog should contain status messages a la:
"Display bpc=10, returned bpc=10" and "Assigning EDID-1.4 digital sink color depth as 10 bpc."

-> This indicates the display was recognized as a 10 bpc capable Displayport display, and that the radeon driver will try to enable 10 bpc mode over Displayport or HDMI.

Then you can "echo 0 > /sys/modules/drm/parameters/debug" again to disable verbose logging.

Assuming you got the right debug output you can be at least certain that the system knows it is a 10 bpc display and tried to enable 10 bpc video output to the display. That is about as far as software based methods get you.

If the 10 bit demos work without visual artifacts or errors/warnings then you should have PTB rendering into a 10 bpc framebuffer and that being scanned out and sent as a 10 bpc signal to the panel. Make sure to read "help PsychImaging" sections about 10 bit mode carefully for infos about gamma table setup and dithering.

Report back when you've reached the point that the software side seems to work. I have more things to explain then.

If the driver/hardware/panel work correctly and the panel actually displays 10 bpc precision can only be found out via photometer in the end.

-mario


Below are the output from `DotDemo`. Please advise what needs to be done so that we could actually run Psychtoolbox with 10 bpc support with this hardware and software setup.

p.s.: For anyone out there who also bought a Laptop that "comes" with Linux: please simply download a latest ISO image from Ubuntu directly, and install that (or better, go with Debian, another GNU Linux). This laptop was partitioned in a very insane way: /boot was FAT32, thus no hardlinks or symbolic linksk work there. That made the system upgrading almost feel like a manual drive in a jungle.

Command outputs:

> octave --no-gui --eval 'DotDemo'
warning: function /usr/share/octave/packages/plot-1.1.0/zoom.m shadows a core library function
warning: called from
    load_packages_and_dependencies at line 47 column 5
    load_packages at line 60 column 3
    pkg at line 422 column 7
    /usr/share/octave/4.0.0/m/startup/octaverc at line 22 column 1
PTB-INFO: Display ':0' : X-Screen 0 : Assigning primary output as 0 with RandR-CRTC 0 and GPU-CRTC 0.


PTB-INFO: This is Psychtoolbox-3 for GNU/Linux X11, under GNU/Octave 64-Bit (Version 3.0.13 - Build date: Dec  1 2016).
PTB-INFO: Support status on this operating system release: Linux 4.4.0-57-generic Supported.
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: Advanced Micro Devices, Inc. [AMD/ATI] - Bonaire XT [Radeon R9 M280X] GPU found. Trying to establish low-level access...
PTB-INFO: Connected to Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon R9 M280X] GPU with DCE-8.0 display engine [2 heads]. Beamposition timestamping enabled.
PTB-WARNING: Your graphics driver doesn't allow me to control syncing wrt. vertical retrace!
PTB-WARNING: Please update your display graphics driver as soon as possible to fix this.
PTB-WARNING: Until then, you can manually enable syncing to VBL somehow in a manner that is
PTB-WARNING: dependent on the type of gfx-card and driver. Google is your friend...


PTB-INFO: Seems like Psychtoolbox is running inside a Virtual Machine? This doesn't provide sufficient
PTB-INFO: visual stimulus timing precision for research grade visual stimulation. I will disable most
PTB-INFO: tests and calibrations so you can at least get your scripts running for demo purposes. Other
PTB-INFO: presentation modalities and various Psychtoolbox functions will only work with limited functionality
PTB-INFO: and precision. Only use this for demos and simple tests, not for real experiment sessions!

PTB-WARNING: At least one test call for OpenML OML_sync_control extension failed! Will disable OpenML and revert to fallback implementation.


PTB-INFO: OpenGL-Renderer is VMware, Inc. :: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) :: 3.0 Mesa 11.2.0
PTB-INFO: VBL startline = 1080 , 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 = 0.000000 ms [inf Hz]. (0 valid samples taken, stddev=0.000000 ms.)
PTB-INFO: Reported monitor refresh interval from operating system = 12.987182 ms [76.999001 Hz].
PTB-INFO: Small deviations between reported values are normal and no reason to worry.
PTB-INFO: All display tests and calibrations disabled. Assuming a refresh interval of 76.999001 Hz. Timing will be inaccurate!
minsmooth =  1
maxsmooth =  255
^[

INFO: PTB's Screen('Flip', 10) command seems to have missed the requested stimulus presentation deadline
INFO: a total of 4 times out of a total of 160 flips during this session.

INFO: This number is fairly accurate (and indicative of real timing problems in your own code or your system)
INFO: if you provided requested stimulus onset times with the 'when' argument of Screen('Flip', window [, when]);
INFO: If you called Screen('Flip', window); without the 'when' argument, this count is more of a ''mild'' indicator
INFO: of timing behaviour than a hard reliable measurement. Large numbers may indicate problems and should at least
INFO: deserve your closer attention. Cfe. 'help SyncTrouble', the FAQ section at www.psychtoolbox.org and the
INFO: examples in the PDF presentation in PsychDocumentation/Psychtoolbox3-Slides.pdf for more info and timing tips.



WARNING: This session of your experiment was run by you with the setting Screen('Preference', 'SkipSyncTests', 2).
WARNING: This means that some internal self-tests and calibrations were skipped. Your stimulus presentation timing
WARNING: may have been wrong. This is fine for development and debugging of your experiment, but for running the real
WARNING: study, please make sure to set Screen('Preference', 'SkipSyncTests', 0) for maximum accuracy and reliability.


# apt search xserver video|grep installed

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

xserver-xorg-video-all/xenial,now 1:7.7+13ubuntu3 amd64 [installed]
xserver-xorg-video-amdgpu/xenial,now 1.1.0-1 amd64 [installed,automatic]
xserver-xorg-video-ati/xenial,now 1:7.7.0-1 amd64 [installed]
xserver-xorg-video-cirrus/xenial,now 1:1.5.3-1ubuntu3 amd64 [installed]
xserver-xorg-video-fbdev/xenial,now 1:0.4.4-1build5 amd64 [installed]
xserver-xorg-video-intel/xenial-updates,now 2:2.99.917+git20160325-1ubuntu1.2 amd64 [installed,automatic]
xserver-xorg-video-mach64/xenial,now 6.9.5-1build2 amd64 [installed]
xserver-xorg-video-mga/xenial,now 1:1.6.4-1build2 amd64 [installed]
xserver-xorg-video-neomagic/xenial,now 1:1.2.9-1build2 amd64 [installed]
xserver-xorg-video-nouveau/xenial,now 1:1.0.12-1build2 amd64 [installed]
xserver-xorg-video-openchrome/xenial,now 1:0.3.3+git20160310-1 amd64 [installed]
xserver-xorg-video-qxl/xenial,now 0.1.4-3ubuntu3 amd64 [installed]
xserver-xorg-video-r128/xenial,now 6.10.0-1build2 amd64 [installed]
xserver-xorg-video-radeon/xenial,now 1:7.7.0-1 amd64 [installed]
xserver-xorg-video-savage/xenial,now 1:2.3.8-1ubuntu3 amd64 [installed]
xserver-xorg-video-siliconmotion/xenial,now 1:1.7.8-1ubuntu6 amd64 [installed]
xserver-xorg-video-sisusb/xenial,now 1:0.9.6-2build5 amd64 [installed]
xserver-xorg-video-tdfx/xenial,now 1:1.4.6-1build2 amd64 [installed]
xserver-xorg-video-trident/xenial,now 1:1.3.7-1build2 amd64 [installed]
xserver-xorg-video-vesa/xenial,now 1:2.3.4-1build2 amd64 [installed]
xserver-xorg-video-vmware/xenial,now 1:13.1.0-2ubuntu3 amd64 [installed]


# cat /proc/version
Linux version 4.4.0-57-generic (buildd@lgw01-54) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #78-Ubuntu SMP Fri Dec 9 23:50:32 UTC 2016

# octave --version
GNU Octave, version 4.0.0

> octave --no-gui --eval 'PsychtoolboxVersion'
ans = 3.0.13 - Flavor: beta - Corresponds to SVN Revision 8319

>> AdditiveBlendingForLinearSuperpositionTutorial('Native10Bit')  % in Octave
libptbdrawtext_ftgl: External 'DrawText' text rendering plugin initialized.
libptbdrawtext_ftgl: Maximum number of cacheable fonts is 40, minimum number of supported concurrent windows is 10.
libptbdrawtext_ftgl: This plugin uses multiple excellent free software libraries to do its work:
libptbdrawtext_ftgl: OGLFT (http://oglft.sourceforge.net/) the OpenGL-FreeType library.
libptbdrawtext_ftgl: The FreeType-2 (http://freetype.sourceforge.net/) library.
libptbdrawtext_ftgl: The FontConfig (http://www.fontconfig.org) library.
libptbdrawtext_ftgl: Thanks!

PTB-INFO: Display ':0' : X-Screen 0 : Assigning primary output as 0 with RandR-CRTC 0 and GPU-CRTC 0.


PTB-INFO: This is Psychtoolbox-3 for GNU/Linux X11, under GNU/Octave 64-Bit (Version 3.0.13 - Build date: Dec  1 2016).
PTB-INFO: Support status on this operating system release: Linux 4.4.0-57-generic Supported.
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: Advanced Micro Devices, Inc. [AMD/ATI] - Bonaire XT [Radeon R9 M280X] GPU found. Trying to establish low-level access...
PTB-INFO: Connected to Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon R9 M280X] GPU with DCE-8.0 display engine [2 heads]. Beamposition timestamping enabled.
PTB-INFO: Trying to enable at least 10 bpc fixed point framebuffer.
PTB-WARNING: Your graphics driver doesn't allow me to control syncing wrt. vertical retrace!
PTB-WARNING: Please update your display graphics driver as soon as possible to fix this.
PTB-WARNING: Until then, you can manually enable syncing to VBL somehow in a manner that is
PTB-WARNING: dependent on the type of gfx-card and driver. Google is your friend...
PTB-INFO: Native 10 bit per color framebuffer requested, but the OS doesn't allow it. It only provides 8 bpc.
PTB-INFO: Will now try to use our own high bit depth setup code as an alternative approach to fullfill your needs.
PTB-INFO: Assuming kernel driver provided color resolution of the GPU framebuffer will be 10 bits per RGB color component.


PTB-INFO: Seems like Psychtoolbox is running inside a Virtual Machine? This doesn't provide sufficient
PTB-INFO: visual stimulus timing precision for research grade visual stimulation. I will disable most
PTB-INFO: tests and calibrations so you can at least get your scripts running for demo purposes. Other
PTB-INFO: presentation modalities and various Psychtoolbox functions will only work with limited functionality
PTB-INFO: and precision. Only use this for demos and simple tests, not for real experiment sessions!

PTB-WARNING: At least one test call for OpenML OML_sync_control extension failed! Will disable OpenML and revert to fallback implementation.


PTB-INFO: OpenGL-Renderer is VMware, Inc. :: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) :: 3.0 Mesa 11.2.0
PTB-INFO: VBL startline = 1080 , 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 = 0.000000 ms [inf Hz]. (0 valid samples taken, stddev=0.000000 ms.)
PTB-INFO: Reported monitor refresh interval from operating system = 12.987182 ms [76.999001 Hz].
PTB-INFO: Small deviations between reported values are normal and no reason to worry.
PTB-INFO: All display tests and calibrations disabled. Assuming a refresh interval of 76.999001 Hz. Timing will be inaccurate!
PTB-INFO: System framebuffer switched to ARGB2101010 mode for screen 0 [head 0].
PTB-INFO: Psychtoolbox imaging pipeline starting up for window with requested imagingmode 5125 ...
PTB-INFO: Will use 32 bits per color component floating point framebuffer for stimulus drawing. Alpha blending should work correctly.
PTB-INFO: Will use 32 bits per color component floating point framebuffer for stimulus post-processing (if any).
Building a fragment shader:Reading shader from file /home/hyiltiz/Documents/Psychtoolbox/PsychOpenGL/PsychGLSLShaders/ICMSimpleGammaCorrectionShader.frag.txt ...
Compiling all shaders matching RGBMultiLUTLookupCombine_FormattingShader * into a GLSL program.
Building a fragment shader:Reading shader from file /home/hyiltiz/Documents/Psychtoolbox/PsychOpenGL/PsychGLSLShaders/RGBMultiLUTLookupCombine_FormattingShader.frag.txt ...
LoadIdentityClut: Info: Used GPU low-level setup code to configure (hopefully) perfect identity pixel passthrough.
Average redraw rate in demo was 14.309124 Hz.
Average update rate in pipeline was 25.209203 Hz.
PTB-INFO: System framebuffer switched to standard ARGB8888 mode for screen 0 [head 0].


INFO: PTB's Screen('Flip', 10) command seems to have missed the requested stimulus presentation deadline
INFO: a total of 26 times out of a total of 327 flips during this session.

INFO: This number is fairly accurate (and indicative of real timing problems in your own code or your system)
INFO: if you provided requested stimulus onset times with the 'when' argument of Screen('Flip', window [, when]);
INFO: If you called Screen('Flip', window); without the 'when' argument, this count is more of a ''mild'' indicator
INFO: of timing behaviour than a hard reliable measurement. Large numbers may indicate problems and should at least
INFO: deserve your closer attention. Cfe. 'help SyncTrouble', the FAQ section at www.psychtoolbox.org and the
INFO: examples in the PDF presentation in PsychDocumentation/Psychtoolbox3-Slides.pdf for more info and timing tips.



WARNING: This session of your experiment was run by you with the setting Screen('Preference', 'SkipSyncTests', 2).
WARNING: This means that some internal self-tests and calibrations were skipped. Your stimulus presentation timing
WARNING: may have been wrong. This is fine for development and debugging of your experiment, but for running the real
WARNING: study, please make sure to set Screen('Preference', 'SkipSyncTests', 0) for maximum accuracy and reliability.



5
About "fglrx": found no file that contains fglrx or firegl in its content or filename (see output below).

root@HP-ZBook-17-G2 /e/modprobe.d# ls
alsa-base.conf                  blacklist-modem.conf                disable-mmc.conf
amddeepcolor-psychtoolbox.conf  blacklist-opensource-graphics.conf  dkms.conf
blacklist-ar8161.conf           blacklist-oss.conf@                 fbdev-blacklist.conf
blacklist-ath_pci.conf          blacklist-psychtoolbox.conf         intel-microcode-blacklist.conf
blacklist.conf                  blacklist-rare-network.conf         iwlwifi.conf
blacklist-firewire.conf         blacklist-thinkpad.conf             mlx4.conf
blacklist-framebuffer.conf      blacklist-watchdog.conf             vmwgfx-fbdev.conf
root@HP-ZBook-17-G2 /e/modprobe.d# grep -ir fglrx .
root@HP-ZBook-17-G2 /e/modprobe.d# grep -ir glrx .
root@HP-ZBook-17-G2 /e/modprobe.d# grep -ir firegl .
root@HP-ZBook-17-G2 /e/modprobe.d# cat amddeepcolor-psychtoolbox.conf
# AMD deep color config file. Enabled "deep color" output with
# more than 8 bpc color depths to digital high precision displays
# which are connected via HDMI or DisplayPort.
#
# This file was installed by Psychtoolbox-3.

options radeon deep_color=1
options amdgpu deep_color=1


Then I did an "apt search" for fglrx, and "apt purge"d the following packages along with anything that are automatically installed with them as dependencies/recommendations:
volatile-task-core fglrx-core fglrx oem-video-fglrx-datong

After purging those packages, I checked /etc/modprobe.d, and again found no file that contains fglrx in its content or filename (see output below). Then udpated initramfs though I deleted no modprobe file. After reboot, nothing changed; PTB still complained about llvmpipe.

Then, I deleted all the following graphics driver packages:
xserver-xorg-video-cirrus xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-mach64 xserver-xorg-video-mga xserver-xorg-video-neomagic xserver-xorg-video-openchrome xserver-xorg-video-qxl xserver-xorg-video-r128 xserver-xorg-video-savage xserver-xorg-video-siliconmotion xserver-xorg-video-sisusb xserver-xorg-video-tdfx xserver-xorg-video-trident xserver-xorg-video-vesa xserver-xorg-video-vmware

and only left these:
xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-radeon xserver-xorg-video-nouveau 

After updating initramfs and reboot, I found that X can no longer load (and of course no lightdm as well), showing only black screen. I logged into TTY1, installed back xserver-xorg-video-all, then after updating initramfs and reboot, I was able to log into X (Unity). However, still couldn't find the modproble file. And PTB still complains about llvmpipe.

p.s. About graphics driver, for a Linux environment to use with Octave to get best performance, is it true that, from now on, only free-software drivers are recommended? Psychtoolbox.org still recommends proprietary drivers. If so, since most computers have either nVidia or ATI based graphics cards, is it true that we only need either nouveau (for nVidia based ones) or Radeon (for ATI based graphics cards) and never any other grahpics cards drivers?


%%% BELOW IS FROM PREVIOUS EMAIL %%%%%%%%%%%%%%%%



6
Ok, so these geniuses at the proprietary driver team didn't fix their installer to properly uninstall everything, but they went to the trouble of changing the filename of the config file that doesn't get properly uninstalled!

Look at blacklist-opensource-graphics.conf. I bet it contains something like "blacklist radeon" and/or "blacklist amdgpu". That would be the one to delete, update initramfs, reboot.

Wrt. the Psychtoolbox website recommending use of proprietary drivers, where is that recommended? It shouldn't be anymore.

The recommendation on Linux is to always try with the open-source drivers first, which is easy because you don't have to do anything after a standard installation - except to reject the suggestion of the system to install the proprietary drivers if it proposes such a thing at some point.

Only if the open-source drivers don't work at all or with satisfactory performance should you try the proprietary drivers, and probably only after checking back on the forum, because the OSS drivers are much more tweakable. In practice this means to always use the OSS drivers for Intel and AMD gpu's. These gpu's are recommended for use with PTB because they have generally very good open-source drivers. With a NVidia card you should try with the OSS driver, but on the latest generations of NVidia cards that driver currently only provides a fraction of the performance of the proprietary driver, so sometimes one doesn't have a choice if one needs higher performance or special features. NVidia wasn't very cooperative with the OSS developers in the past, and they are only very slowly improving and only in some areas.

I can only contribute code/testing/improvements/bug fixes to the open source drivers, and only the OSS drivers provide some special features useful for neuroscience applications, so only then will you have maximal advantage for visual stimulation when using Linux.

That said, the NVidia drivers are generally of rather high quality, but they lack the special neuroscience goodies that i co-implemented for PTB and similar software. In some areas they are behind the OSS drivers for our purposes, in others ahead.

The AMD proprietary drivers are currently transitioning away from a purely proprietary design (fglrx/Catalyst) to a hybrid design called amdgpu-pro, where large parts of the driver are open-source and only some parts will stay proprietary for the time being. Luckily the to-be-open-source parts are the low-level parts most interesting to us, so that will open up new opportunities. Unluckily their former proprietary team, new to open-source development processes, made some design mistakes when designing some low level components for Linux, which prevents that work from moving fast. Essentially they will need to backtrack quite a bit and redesign things, so that will probably take most or all of 2017 until useful results for our purpose come out of this. See the talk of Harry Wentland about AMD DAL here:

https://youtu.be/KIHrjgZJHZA?t=4h38m43s

-mario
7
About the recommendation for evil drivers:
Choice of Graphics Driver

Use the proprietary driver for NVidia. For Intel and probably ATI, the open-source drivers should be sufficient, except for 30 bit support.

Psychtoolbox-3 - Using Psychophysics Toolbox on Ubuntu



It only recommends evil drivers for nVidia though (above nouveau?) This reminds me of the famous Linux finger for nVidia:  https://youtu.be/iYWzMvlj2RQ?t=29s


You are right! blacklist-opensource-graphics.conf did blacklisted radeon. I deleted it, updated initramfs then rebooted (twice). PTB still complains llvmpipe.

Some files seem interesting.

root@HP-ZBook-17-G2 /e/modprobe.d# ag radeon
fbdev-blacklist.conf
6:blacklist radeonfb

blacklist-framebuffer.conf
7:blacklist radeonfb

amddeepcolor-psychtoolbox.conf
7:options radeon deep_color=1
root@HP-ZBook-17-G2 /e/modprobe.d# ag amd
blacklist.conf
51:# EDAC driver for amd76x clashes with the agp driver preventing the aperture
55:blacklist amd76x_edac

amddeepcolor-psychtoolbox.conf
1:# AMD deep color config file. Enabled "deep color" output with
8:options amdgpu deep_color=1
root@HP-ZBook-17-G2 /e/modprobe.d# ag gpu
amddeepcolor-psychtoolbox.conf
8:options amdgpu deep_color=1
root@HP-ZBook-17-G2 /e/modprobe.d#


All the files and their contents in /etc/modprobe.d/:

root@HP-ZBook-17-G2 /e/modprobe.d# tail -n +1 -- *.conf
==> alsa-base.conf <==
# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7

# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-ioctl32 ; /sbin/modprobe --quiet --use-blacklist snd-seq ; }
#
# Workaround at bug #499695 (reverted in Ubuntu see LP #319505)
install snd-pcm /sbin/modprobe --ignore-install snd-pcm $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-pcm-oss ; : ; }
install snd-mixer /sbin/modprobe --ignore-install snd-mixer $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-mixer-oss ; : ; }
install snd-seq /sbin/modprobe --ignore-install snd-seq $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; /sbin/modprobe --quiet --use-blacklist snd-seq-oss ; : ; }
#
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; : ; }
# Cause optional modules to be loaded above sound card driver modules
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-emu10k1-synth ; }
install snd-via82xx /sbin/modprobe --ignore-install snd-via82xx $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq ; }

# Load saa7134-alsa instead of saa7134 (which gets dragged in by it anyway)
install saa7134 /sbin/modprobe --ignore-install saa7134 $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist saa7134-alsa ; : ; }
# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options saa7134-alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
options snd-usb-audio index=-2
options snd-usb-caiaq index=-2
options snd-usb-ua101 index=-2
options snd-usb-us122l index=-2
options snd-usb-usx2y index=-2
# Ubuntu #62691, enable MPU for snd-cmipci
options snd-cmipci mpu_port=0x330 fm_port=0x388
# Keep snd-pcsp from being loaded as first soundcard
options snd-pcsp index=-2
# Keep snd-usb-audio from beeing loaded as first soundcard
options snd-usb-audio index=-2

==> amddeepcolor-psychtoolbox.conf <==
# AMD deep color config file. Enabled "deep color" output with
# more than 8 bpc color depths to digital high precision displays
# which are connected via HDMI or DisplayPort.
#
# This file was installed by Psychtoolbox-3.

options radeon deep_color=1
options amdgpu deep_color=1

==> blacklist-ar8161.conf <==
blacklist alx

==> blacklist-ath_pci.conf <==
# For some Atheros 5K RF MACs, the madwifi driver loads buts fails to
# correctly initialize the hardware, leaving it in a state from
# which ath5k cannot recover. To prevent this condition, stop
# madwifi from loading by default. Use Jockey to select one driver
# or the other. (Ubuntu: #315056, #323830)
blacklist ath_pci


==> blacklist-firewire.conf <==
# Select the legacy firewire stack over the new CONFIG_FIREWIRE one.

blacklist ohci1394
blacklist sbp2
blacklist dv1394
blacklist raw1394
blacklist video1394

#blacklist firewire-ohci
#blacklist firewire-sbp2

==> blacklist-framebuffer.conf <==
# Framebuffer drivers are generally buggy and poorly-supported, and cause
# suspend failures, kernel panics and general mayhem.  For this reason we
# never load them automatically.
blacklist aty128fb
blacklist atyfb
blacklist bochs-drm
blacklist radeonfb
blacklist cirrusfb
blacklist cyber2000fb
blacklist cyblafb
blacklist gx1fb
blacklist hgafb
blacklist i810fb
blacklist intelfb
blacklist kyrofb
blacklist lxfb
blacklist matroxfb_base
blacklist neofb
blacklist nvidiafb
blacklist pm2fb
blacklist rivafb
blacklist s1d13xxxfb
blacklist savagefb
blacklist sisfb
blacklist sstfb
blacklist tdfxfb
blacklist tridentfb
#blacklist vesafb
blacklist vfb
blacklist viafb
blacklist vt8623fb
blacklist udlfb

==> blacklist-modem.conf <==
# Uncomment these entries in order to blacklist unwanted modem drivers
# blacklist snd-atiixp-modem
# blacklist snd-intel8x0m
# blacklist snd-via82xx-modem

==> blacklist-oss.conf <==
blacklist ac97
blacklist ac97_codec
blacklist ac97_plugin_ad1980
blacklist ad1848
blacklist ad1889
blacklist adlib_card
blacklist aedsp16
blacklist ali5455
blacklist btaudio
blacklist cmpci
blacklist cs4232
blacklist cs4281
blacklist cs461x
blacklist cs46xx
blacklist emu10k1
blacklist es1370
blacklist es1371
blacklist esssolo1
blacklist forte
blacklist gus
blacklist i810_audio
blacklist kahlua
blacklist mad16
blacklist maestro
blacklist maestro3
blacklist maui
blacklist mpu401
blacklist nm256_audio
blacklist opl3
blacklist opl3sa
blacklist opl3sa2
blacklist pas2
blacklist pss
blacklist rme96xx
blacklist sb
blacklist sb_lib
blacklist sgalaxy
blacklist sonicvibes
blacklist sound
blacklist sscape
blacklist trident
blacklist trix
blacklist uart401
blacklist uart6850
blacklist via82cxxx_audio
blacklist v_midi
blacklist wavefront
blacklist ymfpci
blacklist ac97_plugin_wm97xx
blacklist ad1816
blacklist audio
blacklist awe_wave
blacklist dmasound_core
blacklist dmasound_pmac
blacklist harmony
blacklist sequencer
blacklist soundcard
blacklist usb-midi

==> blacklist-psychtoolbox.conf <==
# Blacklist the lp modules for parallel port line printers.
# It would prevent exclusive use of ppdev for low-level
# parallel port access by Psychtoolbox.
blacklist lp
install lp /bin/false

==> blacklist-rare-network.conf <==
# Many less commonly used network protocols have recently had various
# security flaws discovered. In an effort to reduce the scope of future
# vulnerability exploitations, they are being blacklisted here so that
# unprivileged users cannot use them by default. System owners can still
# either modify this file, or specifically modprobe any needed protocols.

# ax25
alias net-pf-3 off
# netrom
alias net-pf-6 off
# x25
alias net-pf-9 off
# rose
alias net-pf-11 off
# decnet
alias net-pf-12 off
# econet
alias net-pf-19 off
# rds
alias net-pf-21 off
# af_802154
alias net-pf-36 off

==> blacklist-thinkpad.conf <==
blacklist hdaps
blacklist tp_smapi
blacklist thinkpad_ec

==> blacklist-watchdog.conf <==
# Watchdog drivers should not be loaded automatically, but only if a
# watchdog daemon is installed.
blacklist acquirewdt
blacklist advantechwdt
blacklist alim1535_wdt
blacklist alim7101_wdt
blacklist booke_wdt
blacklist cpu5wdt
blacklist eurotechwdt
blacklist i6300esb
blacklist i8xx_tco
blacklist ib700wdt
blacklist ibmasr
blacklist indydog
blacklist iTCO_wdt
blacklist it8712f_wdt
blacklist it87_wdt
blacklist ixp2000_wdt
blacklist ixp4xx_wdt
blacklist machzwd
blacklist mixcomwd
blacklist mpc8xx_wdt
blacklist mpcore_wdt
blacklist mv64x60_wdt
blacklist pc87413_wdt
blacklist pcwd
blacklist pcwd_pci
blacklist pcwd_usb
blacklist s3c2410_wdt
blacklist sa1100_wdt
blacklist sbc60xxwdt
blacklist sbc7240_wdt
blacklist sb8360
blacklist sc1200wdt
blacklist sc520_wdt
blacklist sch311_wdt
blacklist scx200_wdt
blacklist shwdt
blacklist smsc37b787_wdt
blacklist softdog
blacklist twl4030_wdt
blacklist w83627hf_wdt
blacklist w83697hf_wdt
blacklist w83697ug_wdt
blacklist w83877f_wdt
blacklist w83977f_wdt
blacklist wafer5823wdt
blacklist wdt
blacklist wdt_pci
blacklist wm8350_wdt

==> blacklist.conf <==
# This file lists those modules which we don't want to be loaded by
# alias expansion, usually so some other driver will be loaded for the
# device instead.

# evbug is a debug tool that should be loaded explicitly
blacklist evbug

# these drivers are very simple, the HID drivers are usually preferred
blacklist usbmouse
blacklist usbkbd

# replaced by e100
blacklist eepro100

# replaced by tulip
blacklist de4x5

# causes no end of confusion by creating unexpected network interfaces
blacklist eth1394

# snd_intel8x0m can interfere with snd_intel8x0, doesn't seem to support much
# hardware on its own (Ubuntu bug #2011, #6810)
blacklist snd_intel8x0m

# Conflicts with dvb driver (which is better for handling this device)
blacklist snd_aw2

# causes failure to suspend on HP compaq nc6000 (Ubuntu: #10306)
blacklist i2c_i801

# replaced by p54pci
blacklist prism54

# replaced by b43 and ssb.
blacklist bcm43xx

# most apps now use garmin usb driver directly (Ubuntu: #114565)
blacklist garmin_gps

# replaced by asus-laptop (Ubuntu: #184721)
blacklist asus_acpi

# low-quality, just noise when being used for sound playback, causes
# hangs at desktop session start (Ubuntu: #246969)
blacklist snd_pcsp

# ugly and loud noise, getting on everyone's nerves; this should be done by a
# nice pulseaudio bing (Ubuntu: #77010)
blacklist pcspkr

# EDAC driver for amd76x clashes with the agp driver preventing the aperture
# from being initialised (Ubuntu: #297750). Blacklist so that the driver
# continues to build and is installable for the few cases where its
# really needed.
blacklist amd76x_edac

==> disable-mmc.conf <==
install rtsx_pci sleep 3; /sbin/modprobe disable_mmc; /sbin/modprobe --ignore-install rtsx_pci

==> dkms.conf <==
# modprobe information used for DKMS modules
#
# This is a stub file, should be edited when needed,
# used by default by DKMS.

==> fbdev-blacklist.conf <==
# This file blacklists most old-style PCI framebuffer drivers.

blacklist arkfb
blacklist aty128fb
blacklist atyfb
blacklist radeonfb
blacklist cirrusfb
blacklist cyber2000fb
blacklist kyrofb
blacklist matroxfb_base
blacklist mb862xxfb
blacklist neofb
blacklist pm2fb
blacklist pm3fb
blacklist s3fb
blacklist savagefb
blacklist sisfb
blacklist tdfxfb
blacklist tridentfb
blacklist vt8623fb

==> intel-microcode-blacklist.conf <==
# The microcode module attempts to apply a microcode update when
# it autoloads.  This is not always safe, so we block it by default.
blacklist microcode

==> iwlwifi.conf <==
# /etc/modprobe.d/iwlwifi.conf
# iwlwifi will dyamically load either iwldvm or iwlmvm depending on the
# microcode file installed on the system.  When removing iwlwifi, first
# remove the iwl?vm module and then iwlwifi.
remove iwlwifi \
(/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \
&& /sbin/modprobe -r mac80211

==> mlx4.conf <==
# mlx4_core gets automatically loaded, load mlx4_en also (LP: #1115710)
softdep mlx4_core post: mlx4_en

==> vmwgfx-fbdev.conf <==
options vmwgfx enable_fbdev=1





8
Ok, that page hasn't been updated since 3 years :(. Updating the Wiki is just another thing i can't keep up with. And i'm not a technical writer. I can't seem to ever update that Wiki without introducing some new confusing info somewhere while fixing some other outdated info. Seems most problems on Linux are caused when people try to be too clever and do needless things.

Does lsmod | grep radeon  show radeon as loaded?

What does a run of "glxgears -info" say?

Does PTB work in octave and only fail under Matlab? In that case run PsychLinuxConfiguration again. It applies workarounds for Matlab bugs in recent Matlab versions wrt. OpenGL.

-mario
9
About the Wiki page, since you are meticulously writing the git commits with details for each Beta release merge, it should be possible for the community to find out the update changes, and incorporate that into the Wiki page, perhaps? 

It is still using llvmpipe. Octave can run DotDemo, but complains about llvmpipe. Matlab is started with Software OpenGL, and does not OpenWindow at all (see below). 

I looked around in the Ubuntu forums, but none of the posts about not using llvmpipe helped.

root@HP-ZBook-17-G2 /h/hyiltiz# lsmod | grep radeon
root@HP-ZBook-17-G2 /h/hyiltiz# glxgears -info
GL_RENDERER   = Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits)
GL_VERSION    = 3.0 Mesa 11.2.0
GL_VENDOR     = VMware, Inc.
GL_EXTENSIONS = GL_ARB_multisample GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_copy_texture GL_EXT_polygon_offset GL_EXT_subtexture GL_EXT_texture_object GL_EXT_vertex_array GL_EXT_compiled_vertex_array GL_EXT_texture GL_EXT_texture3D GL_IBM_rasterpos_clip GL_ARB_point_parameters GL_EXT_draw_range_elements GL_EXT_packed_pixels GL_EXT_point_parameters GL_EXT_rescale_normal GL_EXT_separate_specular_color GL_EXT_texture_edge_clamp GL_SGIS_generate_mipmap GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_ARB_framebuffer_sRGB GL_ARB_multitexture GL_EXT_framebuffer_sRGB GL_IBM_multimode_draw_arrays GL_IBM_texture_mirrored_repeat GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_transpose_matrix GL_EXT_blend_func_separate GL_EXT_fog_coord GL_EXT_multi_draw_arrays GL_EXT_secondary_color GL_EXT_texture_env_add GL_EXT_texture_lod_bias GL_INGR_blend_func_separate GL_NV_blend_square GL_NV_light_max_exponent GL_NV_texgen_reflection GL_NV_texture_env_combine4 GL_S3_s3tc GL_SUN_multi_draw_arrays GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_EXT_framebuffer_object GL_EXT_texture_compression_s3tc GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_MESA_window_pos GL_NV_packed_depth_stencil GL_NV_texture_rectangle GL_ARB_depth_texture GL_ARB_occlusion_query GL_ARB_shadow GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_mirrored_repeat GL_ARB_window_pos GL_EXT_stencil_two_side GL_EXT_texture_cube_map GL_NV_depth_clamp GL_NV_fog_distance GL_APPLE_packed_pixels GL_APPLE_vertex_array_object GL_ARB_draw_buffers GL_ARB_fragment_program GL_ARB_fragment_shader GL_ARB_shader_objects GL_ARB_vertex_program GL_ARB_vertex_shader GL_ATI_draw_buffers GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_MESA_pack_invert GL_MESA_ycbcr_texture GL_NV_primitive_restart GL_ARB_depth_clamp GL_ARB_fragment_program_shadow GL_ARB_half_float_pixel GL_ARB_occlusion_query2 GL_ARB_point_sprite GL_ARB_shading_language_100 GL_ARB_sync GL_ARB_texture_non_power_of_two GL_ARB_vertex_buffer_object GL_ATI_blend_equation_separate GL_EXT_blend_equation_separate GL_OES_read_format GL_ARB_color_buffer_float GL_ARB_pixel_buffer_object GL_ARB_texture_compression_rgtc GL_ARB_texture_float GL_ARB_texture_rectangle GL_ATI_texture_compression_3dc GL_EXT_packed_float GL_EXT_pixel_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_rgtc GL_EXT_texture_mirror_clamp GL_EXT_texture_rectangle GL_EXT_texture_sRGB GL_EXT_texture_shared_exponent GL_ARB_framebuffer_object GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_packed_depth_stencil GL_ARB_vertex_array_object GL_ATI_separate_stencil GL_ATI_texture_mirror_once GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_gpu_program_parameters GL_EXT_texture_array GL_EXT_texture_compression_latc GL_EXT_texture_integer GL_EXT_texture_sRGB_decode GL_EXT_timer_query GL_OES_EGL_image GL_ARB_copy_buffer GL_ARB_depth_buffer_float GL_ARB_draw_instanced GL_ARB_half_float_vertex GL_ARB_instanced_arrays GL_ARB_map_buffer_range GL_ARB_texture_rg GL_ARB_texture_swizzle GL_ARB_vertex_array_bgra GL_EXT_texture_swizzle GL_EXT_vertex_array_bgra GL_NV_conditional_render GL_AMD_conservative_depth GL_AMD_draw_buffers_blend GL_AMD_seamless_cubemap_per_texture GL_AMD_shader_stencil_export GL_ARB_ES2_compatibility GL_ARB_blend_func_extended GL_ARB_debug_output GL_ARB_draw_buffers_blend GL_ARB_draw_elements_base_vertex GL_ARB_explicit_attrib_location GL_ARB_fragment_coord_conventions GL_ARB_provoking_vertex GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_shader_stencil_export GL_ARB_shader_texture_lod GL_ARB_texture_cube_map_array GL_ARB_texture_gather GL_ARB_texture_multisample GL_ARB_texture_rgb10_a2ui GL_ARB_uniform_buffer_object GL_ARB_vertex_type_2_10_10_10_rev GL_EXT_provoking_vertex GL_EXT_texture_snorm GL_MESA_texture_signed_rgba GL_ARB_get_program_binary GL_ARB_robustness GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ARB_base_instance GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_internalformat_query GL_ARB_map_buffer_alignment GL_ARB_shading_language_420pack GL_ARB_shading_language_packing GL_ARB_texture_storage GL_ARB_transform_feedback_instanced GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_transform_feedback GL_AMD_shader_trinary_minmax GL_ARB_ES3_compatibility GL_ARB_arrays_of_arrays GL_ARB_clear_buffer_object GL_ARB_explicit_uniform_location GL_ARB_invalidate_subdata GL_ARB_program_interface_query GL_ARB_stencil_texturing GL_ARB_texture_query_levels GL_ARB_texture_storage_multisample GL_ARB_texture_view GL_ARB_vertex_attrib_binding GL_KHR_debug GL_ARB_buffer_storage GL_ARB_multi_bind GL_ARB_seamless_cubemap_per_texture GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_stencil8 GL_ARB_vertex_type_10f_11f_11f_rev GL_EXT_shader_integer_mix GL_ARB_clip_control GL_ARB_conditional_render_inverted GL_ARB_get_texture_sub_image GL_EXT_polygon_offset_clamp GL_KHR_context_flush_control 
VisualID 420, 0x1a4
3831 frames in 5.0 seconds = 765.304 FPS
4208 frames in 5.0 seconds = 841.525 FPS

>> DotDemo %Matlab
PTB-INFO: Display ':0' : X-Screen 0 : Assigning primary output as 0 with RandR-CRTC 0 and GPU-CRTC 0.


PTB-INFO: This is Psychtoolbox-3 for GNU/Linux X11, under Matlab 64-Bit (Version 3.0.12 - Build date: May 13 2016).
PTB-INFO: Support status on this operating system release: Linux 4.4.0-57-generic Supported.
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: Advanced Micro Devices, Inc. [AMD/ATI] - Bonaire XT [Radeon R9 M280X] GPU found. Trying to establish low-level access...
PTB-INFO: Connected to Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon R9 M280X] GPU with DCE-8.0 display engine [2 heads]. Beamposition timestamping enabled.
PTB-WARNING: Your graphics driver doesn't allow me to control syncing wrt. vertical retrace!
PTB-WARNING: Please update your display graphics driver as soon as possible to fix this.
PTB-WARNING: Until then, you can manually enable syncing to VBL somehow in a manner that is
PTB-WARNING: dependent on the type of gfx-card and driver. Google is your friend...




PTB-WARNING: Seems that a Mesa OpenGL software renderer is active! This will likely cause miserable
PTB-WARNING: performance, lack of functionality and severe timing and synchronization problems.
PTB-WARNING: Most likely you are running Psychtoolbox on a Matlab version 8.4 (R2014b) or later and
PTB-WARNING: Matlab is causing this problem by overriding your operating systems OpenGL library with
PTB-WARNING: its own outdated software library. Please run the setup script PsychLinuxConfiguration()
PTB-WARNING: now from your Matlab command window and then quit and restart Matlab to fix this problem.


PTB-WARNING: Actually, it is pointless to continue with the software renderer, as that will cause more trouble than good.
PTB-WARNING: I will abort now. Read the troubleshooting tips above to fix the problem. You can override this if you add the following
PTB-WARNING: command: Screen('Preference', 'ConserveVRAM', 64); to get a functional, but close to useless window up and running.



> octave --no-gui --eval 'DotDemo'
warning: function /usr/share/octave/packages/plot-1.1.0/zoom.m shadows a core library function
warning: called from
    load_packages_and_dependencies at line 47 column 5
    load_packages at line 60 column 3
    pkg at line 422 column 7
    /usr/share/octave/4.0.0/m/startup/octaverc at line 22 column 1
PTB-INFO: Display ':0' : X-Screen 0 : Assigning primary output as 0 with RandR-CRTC 0 and GPU-CRTC 0.


PTB-INFO: This is Psychtoolbox-3 for GNU/Linux X11, under GNU/Octave 64-Bit (Version 3.0.13 - Build date: Dec  1 2016).
PTB-INFO: Support status on this operating system release: Linux 4.4.0-57-generic Supported.
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: Advanced Micro Devices, Inc. [AMD/ATI] - Bonaire XT [Radeon R9 M280X] GPU found. Trying to establish low-level access...
PTB-INFO: Connected to Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon R9 M280X] GPU with DCE-8.0 display engine [2 heads]. Beamposition timestamping enabled.
PTB-WARNING: Your graphics driver doesn't allow me to control syncing wrt. vertical retrace!
PTB-WARNING: Please update your display graphics driver as soon as possible to fix this.
PTB-WARNING: Until then, you can manually enable syncing to VBL somehow in a manner that is
PTB-WARNING: dependent on the type of gfx-card and driver. Google is your friend...


PTB-INFO: Seems like Psychtoolbox is running inside a Virtual Machine? This doesn't provide sufficient
PTB-INFO: visual stimulus timing precision for research grade visual stimulation. I will disable most
PTB-INFO: tests and calibrations so you can at least get your scripts running for demo purposes. Other
PTB-INFO: presentation modalities and various Psychtoolbox functions will only work with limited functionality
PTB-INFO: and precision. Only use this for demos and simple tests, not for real experiment sessions!

PTB-WARNING: At least one test call for OpenML OML_sync_control extension failed! Will disable OpenML and revert to fallback implementation.


PTB-INFO: OpenGL-Renderer is VMware, Inc. :: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) :: 3.0 Mesa 11.2.0
PTB-INFO: VBL startline = 1080 , 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 = 0.000000 ms [inf Hz]. (0 valid samples taken, stddev=0.000000 ms.)
PTB-INFO: Reported monitor refresh interval from operating system = 12.987182 ms [76.999001 Hz].
PTB-INFO: Small deviations between reported values are normal and no reason to worry.
PTB-INFO: All display tests and calibrations disabled. Assuming a refresh interval of 76.999001 Hz. Timing will be inaccurate!
minsmooth =  1
maxsmooth =  255
 

INFO: PTB's Screen('Flip', 10) command seems to have missed the requested stimulus presentation deadline
INFO: a total of 3 times out of a total of 89 flips during this session.

INFO: This number is fairly accurate (and indicative of real timing problems in your own code or your system)
INFO: if you provided requested stimulus onset times with the 'when' argument of Screen('Flip', window [, when]);
INFO: If you called Screen('Flip', window); without the 'when' argument, this count is more of a ''mild'' indicator
INFO: of timing behaviour than a hard reliable measurement. Large numbers may indicate problems and should at least
INFO: deserve your closer attention. Cfe. 'help SyncTrouble', the FAQ section at www.psychtoolbox.org and the
INFO: examples in the PDF presentation in PsychDocumentation/Psychtoolbox3-Slides.pdf for more info and timing tips.



WARNING: This session of your experiment was run by you with the setting Screen('Preference', 'SkipSyncTests', 2).
WARNING: This means that some internal self-tests and calibrations were skipped. Your stimulus presentation timing
WARNING: may have been wrong. This is fine for development and debugging of your experiment, but for running the real
WARNING: study, please make sure to set Screen('Preference', 'SkipSyncTests', 0) for maximum accuracy and reliability.



%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


---In PSYCHTOOLBOX@yahoogroups.com, <mario.kleiner@...> wrote :

Ok, that page hasn't been updated since 3 years :(. Updating the Wiki is just another thing i can't keep up with. And i'm not a technical writer. I can't seem to ever update that Wiki without introducing some new confusing info somewhere while fixing some other outdated info. Seems most problems on Linux are caused when people try to be too clever and do needless things.

Does lsmod | grep radeon  show radeon as loaded?

What does a run of "glxgears -info" say?

Does PTB work in octave and only fail under Matlab? In that case run PsychLinuxConfiguration again. It applies workarounds for Matlab bugs in recent Matlab versions wrt. OpenGL.

-mario

 
10
OK. I found out that, Ubuntu along with their "collaborators" gracefully tripped free software drivers in more than one way. 

In /etc/modprobe.d/, not only there blacklisted radeon, they also blacklisted radeonfb (frame buffer). In addition to that, in /etc/default/grub.d/, there are kernel parameters configured for grub to call that explicitly inhibits nouveau and radeon. I disabled all those, rebooted, but no help yet. There should be some more culprit than that.

I called  modprobe radeon modeset=1, and X got killed. After logging in, Psychtoolbox was happy!

~> octave --no-gui --eval 'DotDemo'
warning: function /usr/share/octave/packages/plot-1.1.0/zoom.m shadows a core library function
warning: called from
    load_packages_and_dependencies at line 47 column 5
    load_packages at line 60 column 3
    pkg at line 422 column 7
    /usr/share/octave/4.0.0/m/startup/octaverc at line 22 column 1
PTB-INFO: Display ':0' : X-Screen 0 : Assigning primary output as 0 with RandR-CRTC 0 and GPU-CRTC 0.


PTB-INFO: This is Psychtoolbox-3 for GNU/Linux X11, under GNU/Octave 64-Bit (Version 3.0.13 - Build date: Dec  1 2016).
PTB-INFO: Support status on this operating system release: Linux 4.4.0-57-generic Supported.
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: Advanced Micro Devices, Inc. [AMD/ATI] - Bonaire XT [Radeon R9 M280X] GPU found. Trying to establish low-level access...
PTB-INFO: Connected to Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon R9 M280X] GPU with DCE-8.0 display engine [2 heads]. Beamposition timestamping enabled.


PTB-INFO: OpenGL-Renderer is X.Org :: Gallium 0.4 on AMD BONAIRE (DRM 2.43.0, LLVM 3.8.0) :: 3.0 Mesa 11.2.0
PTB-INFO: VBL startline = 1080 , VBL Endline = 1109
PTB-INFO: Measured monitor refresh interval from beamposition = 16.688532 ms [59.921389 Hz].
PTB-INFO: Will try to use OS-Builtin OpenML sync control support for accurate Flip timestamping.
PTB-INFO: Measured monitor refresh interval from VBLsync = 16.688247 ms [59.922412 Hz]. (50 valid samples taken, stddev=0.000659 ms.)
PTB-INFO: Reported monitor refresh interval from operating system = 16.661390 ms [60.019001 Hz].
PTB-INFO: Small deviations between reported values are normal and no reason to worry.
minsmooth =  1
maxsmooth =  16384

I'll go ahead and do some of the stuff you asked previously. Before I do so, I WOULD LIKE TO STRONGLY RECOMMEND:

Use Debian if you want to use Linux for PTB. It respects your freedom from 0 to 1.

 
11
Now, I tried enabling debug information for drm module, changed resolution with xrandr (X screen reloaded to the lower resolution), then switched screen resolution back. Then checked syslog files. I also ran Psychtoolbox Native10Bit demo. It seems it is not running on 10 bpc.

root@HP-ZBook-17-G2 # lsmod | grep radeon
radeon               1515520  43
i2c_algo_bit           16384  1 radeon
ttm                    94208  1 radeon
drm_kms_helper        155648  1 radeon
drm                   364544  6 ttm,drm_kms_helper,radeon
root@HP-ZBook-17-G2 # cat /sys/module/radeon/parameters/deep_color 
1
root@HP-ZBook-17-G2 # cat /sys/module/drm/parameters/debug 
0
root@HP-ZBook-17-G2 # echo 1 >  /sys/module/drm/parameters/debug 
root@HP-ZBook-17-G2 # cat /sys/module/drm/parameters/debug 
1


root@HP-ZBook-17-G2 # xrandr --listproviders
Providers: number : 1
Provider 0: id: 0x5a cap: 0x9, Source Output, Sink Offload crtcs: 6 outputs: 5 associated providers: 0 name:BONAIRE @ pci:0000:01:00.0
root@HP-ZBook-17-G2 # xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1920x1080     60.02*+
   1680x1050     59.95  
   1400x1050     59.98  
   1280x1024     59.89  
   1440x900      59.89  
   1280x960      59.94  
   1280x854      59.89  
   1280x800      59.81  
   1280x720      59.86  
   1152x768      59.78  
   1024x768      59.92  
   800x600       59.86  
   848x480       59.66  
   720x480       59.71  
   640x480       59.38  
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
DisplayPort-2 disconnected (normal left inverted right x axis y axis)
VGA-0 disconnected (normal left inverted right x axis y axis)
root@HP-ZBook-17-G2 # xrandr --output VGA --mode 1024x768
warning: output VGA not found; ignoring
root@HP-ZBook-17-G2 # xrandr --output eDP --mode 1024x768
root@HP-ZBook-17-G2 # xrandr --output eDP --mode 1920x1080
root@HP-ZBook-17-G2 # xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1920x1080     60.02*+
   1680x1050     59.95  
   1400x1050     59.98  
   1280x1024     59.89  
   1440x900      59.89  
   1280x960      59.94  
   1280x854      59.89  
   1280x800      59.81  
   1280x720      59.86  
   1152x768      59.78  
   1024x768      59.92  
   800x600       59.86  
   848x480       59.66  
   720x480       59.71  
   640x480       59.38  
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
DisplayPort-2 disconnected (normal left inverted right x axis y axis)
VGA-0 disconnected (normal left inverted right x axis y axis)

root@HP-ZBook-17-G2 # ag 'EDID' /var/log/syslog*
/var/log/syslog
9464:Dec 22 13:17:34 HP-ZBook-17-G2 colord[1883]: (colord:1883): Cd-WARNING **: failed to get edid data: EDID length is too small
root@HP-ZBook-17-G2 # ag 'bpc' /var/log/syslog*
/var/log/syslog
64719:Dec 22 13:25:25 HP-ZBook-17-G2 kernel: [  485.116028] [drm:radeon_get_monitor_bpc] eDP-1: Display bpc=0, returned bpc=6
64720:Dec 22 13:25:25 HP-ZBook-17-G2 kernel: [  485.116030] [drm:radeon_get_monitor_bpc] eDP-1: Display bpc=0, returned bpc=6
64721:Dec 22 13:25:26 HP-ZBook-17-G2 kernel: [  485.614693] [drm:radeon_get_monitor_bpc] eDP-1: Display bpc=0, returned bpc=6
72785:Dec 22 13:25:34 HP-ZBook-17-G2 kernel: [  494.116858] [drm:radeon_get_monitor_bpc] eDP-1: Display bpc=0, returned bpc=6
72786:Dec 22 13:25:34 HP-ZBook-17-G2 kernel: [  494.116859] [drm:radeon_get_monitor_bpc] eDP-1: Display bpc=0, returned bpc=6
72787:Dec 22 13:25:34 HP-ZBook-17-G2 kernel: [  494.116879] [drm:radeon_get_monitor_bpc] eDP-1: Display bpc=0, returned bpc=6


~> octave --no-gui 
GNU Octave, version 4.0.0
Copyright (C) 2015 John W. Eaton and others.
This is free software; see the source code for copying conditions.
There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE.  For details, type 'warranty'.

Octave was configured for "x86_64-pc-linux-gnu".

Additional information about Octave is available at http://www.octave.org.

Please contribute if you find this software useful.
For more information, visit http://www.octave.org/get-involved.html

Read http://www.octave.org/bugs.html to learn how to submit bug reports.
For information about changes from previous versions, type 'news'.

warning: function /usr/share/octave/packages/plot-1.1.0/zoom.m shadows a core library function
warning: called from
    load_packages_and_dependencies at line 47 column 5
    load_packages at line 60 column 3
    pkg at line 422 column 7
    /usr/share/octave/4.0.0/m/startup/octaverc at line 22 column 1
>> AdditiveBlendingForLinearSuperpositionTutorial ('Native10Bit')
libptbdrawtext_ftgl: External 'DrawText' text rendering plugin initialized.
libptbdrawtext_ftgl: Maximum number of cacheable fonts is 40, minimum number of supported concurrent windows is 10.
libptbdrawtext_ftgl: This plugin uses multiple excellent free software libraries to do its work:
libptbdrawtext_ftgl: OGLFT (http://oglft.sourceforge.net/) the OpenGL-FreeType library.
libptbdrawtext_ftgl: The FreeType-2 (http://freetype.sourceforge.net/) library.
libptbdrawtext_ftgl: The FontConfig (http://www.fontconfig.org) library.
libptbdrawtext_ftgl: Thanks!

^[PTB-INFO: Display ':0' : X-Screen 0 : Assigning primary output as 0 with RandR-CRTC 0 and GPU-CRTC 0.


PTB-INFO: This is Psychtoolbox-3 for GNU/Linux X11, under GNU/Octave 64-Bit (Version 3.0.13 - Build date: Dec  1 2016).
PTB-INFO: Support status on this operating system release: Linux 4.4.0-57-generic Supported.
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: Advanced Micro Devices, Inc. [AMD/ATI] - Bonaire XT [Radeon R9 M280X] GPU found. Trying to establish low-level access...
PTB-INFO: Connected to Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon R9 M280X] GPU with DCE-8.0 display engine [2 heads]. Beamposition timestamping enabled.
PTB-INFO: Trying to enable at least 10 bpc fixed point framebuffer.
PTB-INFO: Native 10 bit per color framebuffer requested, but the OS doesn't allow it. It only provides 8 bpc.
PTB-INFO: Will now try to use our own high bit depth setup code as an alternative approach to fullfill your needs.
PTB-INFO: Assuming kernel driver provided color resolution of the GPU framebuffer will be 10 bits per RGB color component.


PTB-INFO: OpenGL-Renderer is X.Org :: Gallium 0.4 on AMD BONAIRE (DRM 2.43.0, LLVM 3.8.0) :: 3.0 Mesa 11.2.0
PTB-INFO: VBL startline = 1080 , VBL Endline = 1109
PTB-INFO: Measured monitor refresh interval from beamposition = 16.666388 ms [60.001003 Hz].
PTB-INFO: Will try to use OS-Builtin OpenML sync control support for accurate Flip timestamping.
PTB-INFO: Measured monitor refresh interval from VBLsync = 16.666398 ms [60.000967 Hz]. (50 valid samples taken, stddev=0.000697 ms.)
PTB-INFO: Reported monitor refresh interval from operating system = 16.661390 ms [60.019001 Hz].
PTB-INFO: Small deviations between reported values are normal and no reason to worry.
PTB-INFO: System framebuffer switched to ARGB2101010 mode for screen 0 [head 0].
PTB-INFO: Psychtoolbox imaging pipeline starting up for window with requested imagingmode 5125 ...
PTB-INFO: Will use 32 bits per color component floating point framebuffer for stimulus drawing. Alpha blending should work correctly.
PTB-INFO: Will use 32 bits per color component floating point framebuffer for stimulus post-processing (if any).
Building a fragment shader:Reading shader from file ~/Documents/Psychtoolbox/PsychOpenGL/PsychGLSLShaders/ICMSimpleGammaCorrectionShader.frag.txt ...
Compiling all shaders matching RGBMultiLUTLookupCombine_FormattingShader * into a GLSL program.
Building a fragment shader:Reading shader from file ~/Documents/Psychtoolbox/PsychOpenGL/PsychGLSLShaders/RGBMultiLUTLookupCombine_FormattingShader.frag.txt ...
LoadIdentityClut: Info: Used GPU low-level setup code to configure (hopefully) perfect identity pixel passthrough.
Average redraw rate in demo was 59.262530 Hz.
Average update rate in pipeline was 600.011158 Hz.
PTB-INFO: System framebuffer switched to standard ARGB8888 mode for screen 0 [head 0].


INFO: PTB's Screen('Flip', 10) command seems to have missed the requested stimulus presentation deadline
INFO: a total of 2 times out of a total of 615 flips during this session.

INFO: This number is fairly accurate (and indicative of real timing problems in your own code or your system)
INFO: if you provided requested stimulus onset times with the 'when' argument of Screen('Flip', window [, when]);
INFO: If you called Screen('Flip', window); without the 'when' argument, this count is more of a ''mild'' indicator
INFO: of timing behaviour than a hard reliable measurement. Large numbers may indicate problems and should at least
INFO: deserve your closer attention. Cfe. 'help SyncTrouble', the FAQ section at www.psychtoolbox.org and the
INFO: examples in the PDF presentation in PsychDocumentation/Psychtoolbox3-Slides.pdf for more info and timing tips.

>> 


12
XX---In PSYCHTOOLBOX@yahoogroups.com, <hormet.yiltiz@...> wrote :

About the Wiki page, since you are meticulously writing the git commits with details for each Beta release merge, it should be possible for the community to find out the update changes, and incorporate that into the Wiki page, perhaps? 

--> Yeah, a man can dream...

It is still using llvmpipe. Octave can run DotDemo, but complains about llvmpipe. Matlab is started with Software OpenGL, and does not OpenWindow at all (see below). 

I looked around in the Ubuntu forums, but none of the posts about not using llvmpipe helped.

root@HP-ZBook-17-G2 /h/hyiltiz# lsmod | grep radeon

--> It doesn't load the radeon kernel module. Apparently fglrx/Catalyst did a really good job at screwing up during uninstallation. Did you do that update of the initramfs + a reboot after deleting that config file?

What is the output of "dmesg" ?
And of "modinfo radeon" ?
And maybe also the content of /var/log/XOrg.0.log ?

This is this point where simply doing a clean install of the whole OS would probably have taken a fraction of the time - minus the learning experience.

-mario

root@HP-ZBook-17-G2 /h/hyiltiz# glxgears -info
GL_RENDERER   = Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits)
GL_VERSION    = 3.0 Mesa 11.2.0
GL_VENDOR     = VMware, Inc.
GL_EXTENSIONS = GL_ARB_multisample GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_copy_texture GL_EXT_polygon_offset GL_EXT_subtexture GL_EXT_texture_object GL_EXT_vertex_array GL_EXT_compiled_vertex_array GL_EXT_texture GL_EXT_texture3D GL_IBM_rasterpos_clip GL_ARB_point_parameters GL_EXT_draw_range_elements GL_EXT_packed_pixels GL_EXT_point_parameters GL_EXT_rescale_normal GL_EXT_separate_specular_color GL_EXT_texture_edge_clamp GL_SGIS_generate_mipmap GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_ARB_framebuffer_sRGB GL_ARB_multitexture GL_EXT_framebuffer_sRGB GL_IBM_multimode_draw_arrays GL_IBM_texture_mirrored_repeat GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_transpose_matrix GL_EXT_blend_func_separate GL_EXT_fog_coord GL_EXT_multi_draw_arrays GL_EXT_secondary_color GL_EXT_texture_env_add GL_EXT_texture_lod_bias GL_INGR_blend_func_separate GL_NV_blend_square GL_NV_light_max_exponent GL_NV_texgen_reflection GL_NV_texture_env_combine4 GL_S3_s3tc GL_SUN_multi_draw_arrays GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_EXT_framebuffer_object GL_EXT_texture_compression_s3tc GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_MESA_window_pos GL_NV_packed_depth_stencil GL_NV_texture_rectangle GL_ARB_depth_texture GL_ARB_occlusion_query GL_ARB_shadow GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_mirrored_repeat GL_ARB_window_pos GL_EXT_stencil_two_side GL_EXT_texture_cube_map GL_NV_depth_clamp GL_NV_fog_distance GL_APPLE_packed_pixels GL_APPLE_vertex_array_object GL_ARB_draw_buffers GL_ARB_fragment_program GL_ARB_fragment_shader GL_ARB_shader_objects GL_ARB_vertex_program GL_ARB_vertex_shader GL_ATI_draw_buffers GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_MESA_pack_invert GL_MESA_ycbcr_texture GL_NV_primitive_restart GL_ARB_depth_clamp GL_ARB_fragment_program_shadow GL_ARB_half_float_pixel GL_ARB_occlusion_query2 GL_ARB_point_sprite GL_ARB_shading_language_100 GL_ARB_sync GL_ARB_texture_non_power_of_two GL_ARB_vertex_buffer_object GL_ATI_blend_equation_separate GL_EXT_blend_equation_separate GL_OES_read_format GL_ARB_color_buffer_float GL_ARB_pixel_buffer_object GL_ARB_texture_compression_rgtc GL_ARB_texture_float GL_ARB_texture_rectangle GL_ATI_texture_compression_3dc GL_EXT_packed_float GL_EXT_pixel_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_rgtc GL_EXT_texture_mirror_clamp GL_EXT_texture_rectangle GL_EXT_texture_sRGB GL_EXT_texture_shared_exponent GL_ARB_framebuffer_object GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_packed_depth_stencil GL_ARB_vertex_array_object GL_ATI_separate_stencil GL_ATI_texture_mirror_once GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_gpu_program_parameters GL_EXT_texture_array GL_EXT_texture_compression_latc GL_EXT_texture_integer GL_EXT_texture_sRGB_decode GL_EXT_timer_query GL_OES_EGL_image GL_ARB_copy_buffer GL_ARB_depth_buffer_float GL_ARB_draw_instanced GL_ARB_half_float_vertex GL_ARB_instanced_arrays GL_ARB_map_buffer_range GL_ARB_texture_rg GL_ARB_texture_swizzle GL_ARB_vertex_array_bgra GL_EXT_texture_swizzle GL_EXT_vertex_array_bgra GL_NV_conditional_render GL_AMD_conservative_depth GL_AMD_draw_buffers_blend GL_AMD_seamless_cubemap_per_texture GL_AMD_shader_stencil_export GL_ARB_ES2_compatibility GL_ARB_blend_func_extended GL_ARB_debug_output GL_ARB_draw_buffers_blend GL_ARB_draw_elements_base_vertex GL_ARB_explicit_attrib_location GL_ARB_fragment_coord_conventions GL_ARB_provoking_vertex GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_shader_stencil_export GL_ARB_shader_texture_lod GL_ARB_texture_cube_map_array GL_ARB_texture_gather GL_ARB_texture_multisample GL_ARB_texture_rgb10_a2ui GL_ARB_uniform_buffer_object GL_ARB_vertex_type_2_10_10_10_rev GL_EXT_provoking_vertex GL_EXT_texture_snorm GL_MESA_texture_signed_rgba GL_ARB_get_program_binary GL_ARB_robustness GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ARB_base_instance GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_internalformat_query GL_ARB_map_buffer_alignment GL_ARB_shading_language_420pack GL_ARB_shading_language_packing GL_ARB_texture_storage GL_ARB_transform_feedback_instanced GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_transform_feedback GL_AMD_shader_trinary_minmax GL_ARB_ES3_compatibility GL_ARB_arrays_of_arrays GL_ARB_clear_buffer_object GL_ARB_explicit_uniform_location GL_ARB_invalidate_subdata GL_ARB_program_interface_query GL_ARB_stencil_texturing GL_ARB_texture_query_levels GL_ARB_texture_storage_multisample GL_ARB_texture_view GL_ARB_vertex_attrib_binding GL_KHR_debug GL_ARB_buffer_storage GL_ARB_multi_bind GL_ARB_seamless_cubemap_per_texture GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_stencil8 GL_ARB_vertex_type_10f_11f_11f_rev GL_EXT_shader_integer_mix GL_ARB_clip_control GL_ARB_conditional_render_inverted GL_ARB_get_texture_sub_image GL_EXT_polygon_offset_clamp GL_KHR_context_flush_control 
VisualID 420, 0x1a4
3831 frames in 5.0 seconds = 765.304 FPS
4208 frames in 5.0 seconds = 841.525 FPS

>> DotDemo %Matlab
PTB-INFO: Display ':0' : X-Screen 0 : Assigning primary output as 0 with RandR-CRTC 0 and GPU-CRTC 0.


PTB-INFO: This is Psychtoolbox-3 for GNU/Linux X11, under Matlab 64-Bit (Version 3.0.12 - Build date: May 13 2016).
PTB-INFO: Support status on this operating system release: Linux 4.4.0-57-generic Supported.
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: Advanced Micro Devices, Inc. [AMD/ATI] - Bonaire XT [Radeon R9 M280X] GPU found. Trying to establish low-level access...
PTB-INFO: Connected to Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon R9 M280X] GPU with DCE-8.0 display engine [2 heads]. Beamposition timestamping enabled.
PTB-WARNING: Your graphics driver doesn't allow me to control syncing wrt. vertical retrace!
PTB-WARNING: Please update your display graphics driver as soon as possible to fix this.
PTB-WARNING: Until then, you can manually enable syncing to VBL somehow in a manner that is
PTB-WARNING: dependent on the type of gfx-card and driver. Google is your friend...




PTB-WARNING: Seems that a Mesa OpenGL software renderer is active! This will likely cause miserable
PTB-WARNING: performance, lack of functionality and severe timing and synchronization problems.
PTB-WARNING: Most likely you are running Psychtoolbox on a Matlab version 8.4 (R2014b) or later and
PTB-WARNING: Matlab is causing this problem by overriding your operating systems OpenGL library with
PTB-WARNING: its own outdated software library. Please run the setup script PsychLinuxConfiguration()
PTB-WARNING: now from your Matlab command window and then quit and restart Matlab to fix this problem.


PTB-WARNING: Actually, it is pointless to continue with the software renderer, as that will cause more trouble than good.
PTB-WARNING: I will abort now. Read the troubleshooting tips above to fix the problem. You can override this if you add the following
PTB-WARNING: command: Screen('Preference', 'ConserveVRAM', 64); to get a functional, but close to useless window up and running.



> octave --no-gui --eval 'DotDemo'
warning: function /usr/share/octave/packages/plot-1.1.0/zoom.m shadows a core library function
warning: called from
    load_packages_and_dependencies at line 47 column 5
    load_packages at line 60 column 3
    pkg at line 422 column 7
    /usr/share/octave/4.0.0/m/startup/octaverc at line 22 column 1
PTB-INFO: Display ':0' : X-Screen 0 : Assigning primary output as 0 with RandR-CRTC 0 and GPU-CRTC 0.


PTB-INFO: This is Psychtoolbox-3 for GNU/Linux X11, under GNU/Octave 64-Bit (Version 3.0.13 - Build date: Dec  1 2016).
PTB-INFO: Support status on this operating system release: Linux 4.4.0-57-generic Supported.
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: Advanced Micro Devices, Inc. [AMD/ATI] - Bonaire XT [Radeon R9 M280X] GPU found. Trying to establish low-level access...
PTB-INFO: Connected to Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon R9 M280X] GPU with DCE-8.0 display engine [2 heads]. Beamposition timestamping enabled.
PTB-WARNING: Your graphics driver doesn't allow me to control syncing wrt. vertical retrace!
PTB-WARNING: Please update your display graphics driver as soon as possible to fix this.
PTB-WARNING: Until then, you can manually enable syncing to VBL somehow in a manner that is
PTB-WARNING: dependent on the type of gfx-card and driver. Google is your friend...


PTB-INFO: Seems like Psychtoolbox is running inside a Virtual Machine? This doesn't provide sufficient
PTB-INFO: visual stimulus timing precision for research grade visual stimulation. I will disable most
PTB-INFO: tests and calibrations so you can at least get your scripts running for demo purposes. Other
PTB-INFO: presentation modalities and various Psychtoolbox functions will only work with limited functionality
PTB-INFO: and precision. Only use this for demos and simple tests, not for real experiment sessions!

PTB-WARNING: At least one test call for OpenML OML_sync_control extension failed! Will disable OpenML and revert to fallback implementation.


PTB-INFO: OpenGL-Renderer is VMware, Inc. :: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) :: 3.0 Mesa 11.2.0
PTB-INFO: VBL startline = 1080 , 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 = 0.000000 ms [inf Hz]. (0 valid samples taken, stddev=0.000000 ms.)
PTB-INFO: Reported monitor refresh interval from operating system = 12.987182 ms [76.999001 Hz].
PTB-INFO: Small deviations between reported values are normal and no reason to worry.
PTB-INFO: All display tests and calibrations disabled. Assuming a refresh interval of 76.999001 Hz. Timing will be inaccurate!
minsmooth =  1
maxsmooth =  255
 

INFO: PTB's Screen('Flip', 10) command seems to have missed the requested stimulus presentation deadline
INFO: a total of 3 times out of a total of 89 flips during this session.

INFO: This number is fairly accurate (and indicative of real timing problems in your own code or your system)
INFO: if you provided requested stimulus onset times with the 'when' argument of Screen('Flip', window [, when]);
INFO: If you called Screen('Flip', window); without the 'when' argument, this count is more of a ''mild'' indicator
INFO: of timing behaviour than a hard reliable measurement. Large numbers may indicate problems and should at least
INFO: deserve your closer attention. Cfe. 'help SyncTrouble', the FAQ section at www.psychtoolbox.org and the
INFO: examples in the PDF presentation in PsychDocumentation/Psychtoolbox3-Slides.pdf for more info and timing tips.



WARNING: This session of your experiment was run by you with the setting Screen('Preference', 'SkipSyncTests', 2).
WARNING: This means that some internal self-tests and calibrations were skipped. Your stimulus presentation timing
WARNING: may have been wrong. This is fine for development and debugging of your experiment, but for running the real
WARNING: study, please make sure to set Screen('Preference', 'SkipSyncTests', 0) for maximum accuracy and reliability.



%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


---In PSYCHTOOLBOX@yahoogroups.com, <mario.kleiner@...> wrote :

Ok, that page hasn't been updated since 3 years :(. Updating the Wiki is just another thing i can't keep up with. And i'm not a technical writer. I can't seem to ever update that Wiki without introducing some new confusing info somewhere while fixing some other outdated info. Seems most problems on Linux are caused when people try to be too clever and do needless things.

Does lsmod | grep radeon  show radeon as loaded?

What does a run of "glxgears -info" say?

Does PTB work in octave and only fail under Matlab? In that case run PsychLinuxConfiguration again. It applies workarounds for Matlab bugs in recent Matlab versions wrt. OpenGL.

-mario

 
13
XX---In PSYCHTOOLBOX@yahoogroups.com, <hormet.yiltiz@...> wrote :

I think I was able to get rid of most left-overs from the evil drivers. I posted it right before your post, so you may have missed it. Can you please check that one? It successfully loaded radeon. 

-> Does it work after a reboot? I guess that would be the check.

Now, even after this, if this doesn't work out, maybe I'll just fresh install Debian, which is the OS anyone should be using anyway.

-> Calm down and *slow down*. This has all nothing to do with Debian vs. Ubuntu, or evil conspiracies related to Ubuntu.

Afaics is that somebody at AMD wrote a really horrible quality installer/uninstaller for the legacy proprietary Catalyst/fglrx driver, which apparently got way worse since i last had to deal with it not properly uninstalling about 9 month ago. I don't see how Ubuntu would be at fault here, or how this would be different on Debian.

There are some reasons why choosing Debian is probably not such a good idea for a total beginner which comes from Windows or even OSX:

1. Afaik installing Debian is less user-friendly than installing Ubuntu. Maybe that has changed, but last time i checked, it would be quite a bit of a culture shock especially for people that come from a Mac?

2. Afaik, if you choose a stable Debian distro, you have to deal with highly stable and mature and totally outdated software, which doesn't allow to get best results for low-level software like PTB. If you instead choose something like Debian 'unstable' or 'experimental' you get the latest software very quickly - and a large amount of instability to deal with on such a fast moving platform. In that sense i think the Ubuntu flavors roughly hit the right tradeoff between too fast and too slow, especially the LTS releases.

3. The Ubuntu LTS releases are the only ones that get extra thorough testing and lots of extra love from me wrt. PTB, usually long before the release happens, because it takes months to carefully test most of the stuff that matters. You'd need a whole team of people working full-time to cover more and faster moving distributions, or lots of money for state of the art automated testing infrastructure to automate this.

But back to your results:

Everything seems to work perfectly wrt. timing and operation of the 10 bpc framebuffer. What didn't work is actually outputting that 10 bpc framebuffer with 10 bpc precision. The driver/gpu downsamples/dithers the 10 bpc output to 6 bpc, because apparently it couldn't detect the correct color depth from the display panels EDID, and the DisplayPort spec says in such a situation 6 bpc should be used as a fail-safe default.

So why does that happen? For that i need the dmesg output and /var/log/XOrg.0.log.

-mario


14
Thanks! I was referring to Debian testing rather than stable, and since Debian does not support any proprietary software by default, we may not have to hassle with the fglrx / nVidia drivers in the first place. But true, it is always a good idea to be in the same environment with the active developer, and you are using Ubuntu (LTS?).

Now, dumping output from dmesg and /var/log/XOrg.0.log will be over 3k lines. I'll Gist.



15
Ok, dmesg doesn't contain anything useful anymore - too much unrelated info. I need /var/log/syslog, filtered for anything with edid, EDID, bpc, bpp, or Connector or Displayport in its name, in various states of captialization.

-mario
16
As requested:

# ag -i '(edid)|(bpc)|(bpp)|(Connector)|(Displayport)' /var/log/syslog
6545:Dec 22 13:08:55 HP-ZBook-17-G2 kernel: [ 1167.944005] [drm] Radeon Display Connectors
6546:Dec 22 13:08:55 HP-ZBook-17-G2 kernel: [ 1167.944006] [drm] Connector 0:
6552:Dec 22 13:08:55 HP-ZBook-17-G2 kernel: [ 1167.944010] [drm] Connector 1:
6558:Dec 22 13:08:55 HP-ZBook-17-G2 kernel: [ 1167.944013] [drm] Connector 2:
6564:Dec 22 13:08:55 HP-ZBook-17-G2 kernel: [ 1167.944017] [drm] Connector 3:
6570:Dec 22 13:08:55 HP-ZBook-17-G2 kernel: [ 1167.944020] [drm] Connector 4:
8888:Dec 22 13:17:31 HP-ZBook-17-G2 kernel: [    6.353789] [drm] Radeon Display Connectors
8889:Dec 22 13:17:31 HP-ZBook-17-G2 kernel: [    6.353789] [drm] Connector 0:
8895:Dec 22 13:17:31 HP-ZBook-17-G2 kernel: [    6.353793] [drm] Connector 1:
8901:Dec 22 13:17:31 HP-ZBook-17-G2 kernel: [    6.353796] [drm] Connector 2:
8907:Dec 22 13:17:31 HP-ZBook-17-G2 kernel: [    6.353799] [drm] Connector 3:
8913:Dec 22 13:17:31 HP-ZBook-17-G2 kernel: [    6.353802] [drm] Connector 4:
9464:Dec 22 13:17:34 HP-ZBook-17-G2 colord[1883]: (colord:1883): Cd-WARNING **: failed to get edid data: EDID length is too small
19294:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.294118] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
19295:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.304505] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
19304:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.304612] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
19307:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.316736] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
19308:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.316746] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
19311:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.329269] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
19312:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.329279] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
19315:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.341257] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
19316:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.341265] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
19317:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.353063] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
19461:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.356333] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
19471:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.366964] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
19480:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.366998] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
19483:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.377153] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
19484:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.377162] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
19485:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.388978] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
19486:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.388983] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
19489:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.401276] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
19490:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.401286] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
19493:Dec 22 13:23:58 HP-ZBook-17-G2 kernel: [  397.413062] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
22562:Dec 22 13:24:02 HP-ZBook-17-G2 kernel: [  401.714357] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
22565:Dec 22 13:24:02 HP-ZBook-17-G2 kernel: [  401.725524] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
22574:Dec 22 13:24:02 HP-ZBook-17-G2 kernel: [  401.725564] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
22575:Dec 22 13:24:02 HP-ZBook-17-G2 kernel: [  401.737542] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
22576:Dec 22 13:24:02 HP-ZBook-17-G2 kernel: [  401.737552] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
22579:Dec 22 13:24:02 HP-ZBook-17-G2 kernel: [  401.749626] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
22580:Dec 22 13:24:02 HP-ZBook-17-G2 kernel: [  401.749637] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
22583:Dec 22 13:24:02 HP-ZBook-17-G2 kernel: [  401.761626] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
22584:Dec 22 13:24:02 HP-ZBook-17-G2 kernel: [  401.761636] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
22587:Dec 22 13:24:02 HP-ZBook-17-G2 kernel: [  401.773413] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
51745:Dec 22 13:24:54 HP-ZBook-17-G2 kernel: [  453.807090] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
51748:Dec 22 13:24:54 HP-ZBook-17-G2 kernel: [  453.818490] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
51757:Dec 22 13:24:54 HP-ZBook-17-G2 kernel: [  453.818528] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
51758:Dec 22 13:24:54 HP-ZBook-17-G2 kernel: [  453.827967] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
51759:Dec 22 13:24:54 HP-ZBook-17-G2 kernel: [  453.827974] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
51762:Dec 22 13:24:54 HP-ZBook-17-G2 kernel: [  453.836672] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
51763:Dec 22 13:24:54 HP-ZBook-17-G2 kernel: [  453.836676] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
51764:Dec 22 13:24:54 HP-ZBook-17-G2 kernel: [  453.847087] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
51765:Dec 22 13:24:54 HP-ZBook-17-G2 kernel: [  453.847097] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
51768:Dec 22 13:24:54 HP-ZBook-17-G2 kernel: [  453.860553] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
64719:Dec 22 13:25:25 HP-ZBook-17-G2 kernel: [  485.116028] [drm:radeon_get_monitor_bpc] eDP-1: Display bpc=0, returned bpc=6
64720:Dec 22 13:25:25 HP-ZBook-17-G2 kernel: [  485.116030] [drm:radeon_get_monitor_bpc] eDP-1: Display bpc=0, returned bpc=6
64721:Dec 22 13:25:26 HP-ZBook-17-G2 kernel: [  485.614693] [drm:radeon_get_monitor_bpc] eDP-1: Display bpc=0, returned bpc=6
72785:Dec 22 13:25:34 HP-ZBook-17-G2 kernel: [  494.116858] [drm:radeon_get_monitor_bpc] eDP-1: Display bpc=0, returned bpc=6
72786:Dec 22 13:25:34 HP-ZBook-17-G2 kernel: [  494.116859] [drm:radeon_get_monitor_bpc] eDP-1: Display bpc=0, returned bpc=6
72787:Dec 22 13:25:34 HP-ZBook-17-G2 kernel: [  494.116879] [drm:radeon_get_monitor_bpc] eDP-1: Display bpc=0, returned bpc=6
79527:Dec 22 13:25:39 HP-ZBook-17-G2 kernel: [  498.400612] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
79530:Dec 22 13:25:39 HP-ZBook-17-G2 kernel: [  498.410909] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
79539:Dec 22 13:25:39 HP-ZBook-17-G2 kernel: [  498.410945] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
79540:Dec 22 13:25:39 HP-ZBook-17-G2 kernel: [  498.423796] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
79541:Dec 22 13:25:39 HP-ZBook-17-G2 kernel: [  498.423807] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
79544:Dec 22 13:25:39 HP-ZBook-17-G2 kernel: [  498.435797] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
79545:Dec 22 13:25:39 HP-ZBook-17-G2 kernel: [  498.435807] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
79548:Dec 22 13:25:39 HP-ZBook-17-G2 kernel: [  498.447784] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
79549:Dec 22 13:25:39 HP-ZBook-17-G2 kernel: [  498.447794] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR
79552:Dec 22 13:25:39 HP-ZBook-17-G2 kernel: [  498.459512] [drm:drm_ioctl] pid=1373, dev=0xe200, auth=1, DRM_IOCTL_MODE_GETCONNECTOR


17
Ok, still not enough info. Probably would need to set drm.debug=5 as kernel command line option for more verbose logging and then the whole syslog from boot, as the whole edid detection for a builtin panel happens during bootup, until the point where we reach the login screen.

Anyway, to shortcut this, we can manually inject the edid file i created from some earlier output you posted:

Injection procedure in detail: Kernel mode setting - ArchWiki


In your case:


1. Copy the attached edid file into /lib/firmware

2. Add the drm.debug=1 option to the kernel command line - Temporay at the grub bootloader prompt.

3. Add this to the kernel command line, probably also first temporary at grub for testing:

drm_kms_helper.edid_firmware=eDP-1:eDPEDID_LGD_764.bin

4. Boot and see what happens. syslog output, filtered for bpc, bpp, edid, EDID etc., and Xorg.0.log.


-mario





18
And it ends with "(Message over 64 KB, truncated)" ;-)

The good news is this:

1388920:Dec 23 15:18:12 HP-ZBook-17-G2 kernel: [   18.935922] [drm] Got external EDID base block and 0 extensions from "eDPEDID_LGD_764.bin" for connector "eDP-1"
1388922:Dec 23 15:18:12 HP-ZBook-17-G2 kernel: [   18.935938] [drm:drm_add_display_info] eDP-1: Assigning EDID-1.4 digital sink color depth as 10 bpc.

So it parsed the injected EDID and detected the panel as 10 bpc.

But i'd like to see the rest of the syslog as well. Also in case of the XOrg.0.log the whole log please, not just filtered.

-mario
19
Obviously, dumping was not a good option. Attaching the dump. It is true that the custom injection file was loaded by kernel, and deep_color was set at 1 (as well as debug information). But, somehow the color channels weren't still detected correctly; I guess it might still be due EDID not being recognized.

20
Also dumping EDID. I think the Byte 20 'b0' encodes what we need, and this tool is telling me that the monitor is  capable of 10 bpc.

root@HP-ZBook-17-G2 ~# get-edid | edid-decode 
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 3
No EDID on bus 4
No EDID on bus 5
No EDID on bus 7
No EDID on bus 8
No EDID on bus 9
No EDID on bus 10
No EDID on bus 11
1 potential busses found: 6
Bus 6 doesn't really have an EDID...
Couldn't find an accessible EDID on this computer.
Attempting to use the classical VBE interface

Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
Function supported
Call successful

VBE version 300
VBE string at 0xc0248 "AMD ATOMBIOS"

VBE/DDC service about to be called
Report DDC capabilities

Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
Function supported
Call successful

Monitor and video card combination does not support DDC1 transfers
Monitor and video card combination supports DDC2 transfers
0 seconds per 128 byte EDID block transfer
Screen is not blanked during DDC transfer

Reading next EDID block

VBE/DDC service about to be called
Read EDID

Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful

Looks like VBE was successful. Have a good day.
Extracted contents:
header:          00 ff ff ff ff ff ff 00
serial number:   30 e4 fc 02 00 00 00 00 00 14
version:         01 04
basic params:    b0 26 15 78 0a
chroma info:     b8 25 af 4e 36 b7 25 0b 50 54
established:     00 00 00
standard:        01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
descriptor 1:    2e 36 80 a0 70 38 1f 40 30 20 35 00 7e d7 10 00 00 19
descriptor 2:    58 2b 80 a0 70 38 1f 40 30 20 35 00 7e d7 10 00 00 19
descriptor 3:    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
descriptor 4:    26 2d 80 a0 70 38 1f 40 30 20 35 00 7e d7 10 00 00 19
extensions:      00
checksum:        0b

Manufacturer: LGD Model 2fc Serial Number 0
Made week 0 of 2010
EDID version: 1.4
Digital display
10 bits per primary color channel
Digital interface is not defined
Maximum image size: 38 cm x 21 cm
Gamma: 2.20
Supported color formats: RGB 4:4:4, YCrCb 4:2:2
First detailed timing is preferred timing
Established timings supported:
Standard timings supported:
Detailed mode: Clock 138.700 MHz, 382 mm x 215 mm
               1920 1968 2000 2080 hborder 0
               1080 1083 1088 1111 vborder 0
               -hsync -vsync 
Detailed mode: Clock 110.960 MHz, 382 mm x 215 mm
               1920 1968 2000 2080 hborder 0
               1080 1083 1088 1111 vborder 0
               -hsync -vsync 
Manufacturer-specified data, tag 0
Detailed mode: Clock 115.580 MHz, 382 mm x 215 mm
               1920 1968 2000 2080 hborder 0
               1080 1083 1088 1111 vborder 0
               -hsync -vsync 
Checksum: 0xb (valid)
EDID block does NOT conform to EDID 1.3!
Missing name descriptor
Missing monitor ranges
EDID block does not conform at all!
Invalid detailed timing descriptor ordering