# HOWTO: 10 bpc laptop running Linux

**URL:** <https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351>\
**Category:** Uncategorized\
**Created:** [December 20, 2016, 12:41am UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351 "2016-12-20T00:41:37Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![hormet.yiltiz](https://avatars.discourse-cdn.com/v4/letter/h/4af34b/32.png) [@hormet.yiltiz](https://psychtoolbox.discourse.group/u/hormet.yiltiz)\
**Post date:** [December 20, 2016, 12:41am UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/1 "2016-12-20T00:41:37Z")

</div>

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.&nbsp;

  

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](http://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&nbsp;&nbsp;(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.&nbsp;

  

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

  

**# &nbsp;octave --version**

GNU Octave, version 3.8.1

  

**\> PsychtoolboxVersion&nbsp;**

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](http://neuro.debian.net/pkgs/octave-psychtoolbox-3.html)

  

**# &nbsp;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&nbsp;

deb [http://neuro.debian.net/debian](http://neuro.debian.net/debian) data main contrib non-free

#deb-src [http://neuro.debian.net/debian](http://neuro.debian.net/debian) data main contrib non-free

deb [http://neuro.debian.net/debian](http://neuro.debian.net/debian) trusty main contrib non-free

#deb-src [http://neuro.debian.net/debian](http://neuro.debian.net/debian) trusty main contrib non-free

​  

**\> [a,b] = Screen(' ReadNormalizedGammaTable',0)**

a =

  

&nbsp; &nbsp;0.00000 &nbsp; 0.00000 &nbsp; 0.00000

&nbsp; &nbsp;0.00392 &nbsp; 0.00392 &nbsp; 0.00392

&nbsp; &nbsp;0.00784 &nbsp; 0.00784 &nbsp; 0.00784

&nbsp; &nbsp;0.01176 &nbsp; 0.01176 &nbsp; 0.01176

&nbsp; &nbsp;0.01569 &nbsp; 0.01569 &nbsp; 0.01569

&nbsp; &nbsp;0.01961 &nbsp; 0.01961 &nbsp; 0.01961

&nbsp; &nbsp;0.02353 &nbsp; 0.02353 &nbsp; 0.02353

&nbsp; &nbsp;0.02745 &nbsp; 0.02745 &nbsp; 0.02745

&nbsp; &nbsp;0.03137 &nbsp; 0.03137 &nbsp; 0.03137

&nbsp; &nbsp;0.03529 &nbsp; 0.03529 &nbsp; 0.03529

&nbsp; &nbsp;0.03922 &nbsp; 0.03922 &nbsp; 0.03922

&nbsp; &nbsp;0.04314 &nbsp; 0.04314 &nbsp; 0.04314

&nbsp; &nbsp;0.04706 &nbsp; 0.04706 &nbsp; 0.04706

&nbsp; &nbsp;0.05098 &nbsp; 0.05098 &nbsp; 0.05098

&nbsp; &nbsp;0.05490 &nbsp; 0.05490 &nbsp; 0.05490

&nbsp; &nbsp;0.05882 &nbsp; 0.05882 &nbsp; 0.05882

&nbsp; &nbsp;0.06275 &nbsp; 0.06275 &nbsp; 0.06275

&nbsp; &nbsp;0.06667 &nbsp; 0.06667 &nbsp; 0.06667

&nbsp; &nbsp;0.07059 &nbsp; 0.07059 &nbsp; 0.07059

&nbsp; &nbsp;0.07451 &nbsp; 0.07451 &nbsp; 0.07451

&nbsp; &nbsp;0.07843 &nbsp; 0.07843 &nbsp; 0.07843

&nbsp; &nbsp;0.08235 &nbsp; 0.08235 &nbsp; 0.08235

&nbsp; &nbsp;0.08627 &nbsp; 0.08627 &nbsp; 0.08627

&nbsp; &nbsp;0.09020 &nbsp; 0.09020 &nbsp; 0.09020

&nbsp; &nbsp;0.09412 &nbsp; 0.09412 &nbsp; 0.09412

&nbsp; &nbsp;0.09804 &nbsp; 0.09804 &nbsp; 0.09804

&nbsp; &nbsp;0.10196 &nbsp; 0.10196 &nbsp; 0.10196

&nbsp; &nbsp;0.10588 &nbsp; 0.10588 &nbsp; 0.10588

&nbsp; &nbsp;0.10980 &nbsp; 0.10980 &nbsp; 0.10980

&nbsp; &nbsp;0.11373 &nbsp; 0.11373 &nbsp; 0.11373

&nbsp; &nbsp;0.11765 &nbsp; 0.11765 &nbsp; 0.11765

&nbsp; &nbsp;0.12157 &nbsp; 0.12157 &nbsp; 0.12157

&nbsp; &nbsp;0.12549 &nbsp; 0.12549 &nbsp; 0.12549

&nbsp; &nbsp;0.12941 &nbsp; 0.12941 &nbsp; 0.12941

&nbsp; &nbsp;0.13333 &nbsp; 0.13333 &nbsp; 0.13333

&nbsp; &nbsp;0.13725 &nbsp; 0.13725 &nbsp; 0.13725

&nbsp; &nbsp;0.14118 &nbsp; 0.14118 &nbsp; 0.14118

&nbsp; &nbsp;0.14510 &nbsp; 0.14510 &nbsp; 0.14510

&nbsp; &nbsp;0.14902 &nbsp; 0.14902 &nbsp; 0.14902

&nbsp; &nbsp;0.15294 &nbsp; 0.15294 &nbsp; 0.15294

&nbsp; &nbsp;0.15686 &nbsp; 0.15686 &nbsp; 0.15686

&nbsp; &nbsp;0.16078 &nbsp; 0.16078 &nbsp; 0.16078

&nbsp; &nbsp;0.16471 &nbsp; 0.16471 &nbsp; 0.16471

&nbsp; &nbsp;0.16863 &nbsp; 0.16863 &nbsp; 0.16863

&nbsp; &nbsp;0.17255 &nbsp; 0.17255 &nbsp; 0.17255

&nbsp; &nbsp;0.17647 &nbsp; 0.17647 &nbsp; 0.17647

&nbsp; &nbsp;0.18039 &nbsp; 0.18039 &nbsp; 0.18039

&nbsp; &nbsp;0.18431 &nbsp; 0.18431 &nbsp; 0.18431

&nbsp; &nbsp;0.18824 &nbsp; 0.18824 &nbsp; 0.18824

&nbsp; &nbsp;0.19216 &nbsp; 0.19216 &nbsp; 0.19216

&nbsp; &nbsp;0.19608 &nbsp; 0.19608 &nbsp; 0.19608

&nbsp; &nbsp;0.20000 &nbsp; 0.20000 &nbsp; 0.20000

&nbsp; &nbsp;0.20392 &nbsp; 0.20392 &nbsp; 0.20392

&nbsp; &nbsp;0.20784 &nbsp; 0.20784 &nbsp; 0.20784

&nbsp; &nbsp;0.21176 &nbsp; 0.21176 &nbsp; 0.21176

&nbsp; &nbsp;0.21569 &nbsp; 0.21569 &nbsp; 0.21569

&nbsp; &nbsp;0.21961 &nbsp; 0.21961 &nbsp; 0.21961

&nbsp; &nbsp;0.22353 &nbsp; 0.22353 &nbsp; 0.22353

&nbsp; &nbsp;0.22745 &nbsp; 0.22745 &nbsp; 0.22745

&nbsp; &nbsp;0.23137 &nbsp; 0.23137 &nbsp; 0.23137

&nbsp; &nbsp;0.23529 &nbsp; 0.23529 &nbsp; 0.23529

&nbsp; &nbsp;0.23922 &nbsp; 0.23922 &nbsp; 0.23922

&nbsp; &nbsp;0.24314 &nbsp; 0.24314 &nbsp; 0.24314

&nbsp; &nbsp;0.24706 &nbsp; 0.24706 &nbsp; 0.24706

&nbsp; &nbsp;0.25098 &nbsp; 0.25098 &nbsp; 0.25098

&nbsp; &nbsp;0.25490 &nbsp; 0.25490 &nbsp; 0.25490

&nbsp; &nbsp;0.25882 &nbsp; 0.25882 &nbsp; 0.25882

&nbsp; &nbsp;0.26275 &nbsp; 0.26275 &nbsp; 0.26275

&nbsp; &nbsp;0.26667 &nbsp; 0.26667 &nbsp; 0.26667

&nbsp; &nbsp;0.27059 &nbsp; 0.27059 &nbsp; 0.27059

&nbsp; &nbsp;0.27451 &nbsp; 0.27451 &nbsp; 0.27451

&nbsp; &nbsp;0.27843 &nbsp; 0.27843 &nbsp; 0.27843

&nbsp; &nbsp;0.28235 &nbsp; 0.28235 &nbsp; 0.28235

&nbsp; &nbsp;0.28627 &nbsp; 0.28627 &nbsp; 0.28627

&nbsp; &nbsp;0.29020 &nbsp; 0.29020 &nbsp; 0.29020

&nbsp; &nbsp;0.29412 &nbsp; 0.29412 &nbsp; 0.29412

&nbsp; &nbsp;0.29804 &nbsp; 0.29804 &nbsp; 0.29804

&nbsp; &nbsp;0.30196 &nbsp; 0.30196 &nbsp; 0.30196

&nbsp; &nbsp;0.30588 &nbsp; 0.30588 &nbsp; 0.30588

&nbsp; &nbsp;0.30980 &nbsp; 0.30980 &nbsp; 0.30980

&nbsp; &nbsp;0.31373 &nbsp; 0.31373 &nbsp; 0.31373

&nbsp; &nbsp;0.31765 &nbsp; 0.31765 &nbsp; 0.31765

&nbsp; &nbsp;0.32157 &nbsp; 0.32157 &nbsp; 0.32157

&nbsp; &nbsp;0.32549 &nbsp; 0.32549 &nbsp; 0.32549

&nbsp; &nbsp;0.32941 &nbsp; 0.32941 &nbsp; 0.32941

&nbsp; &nbsp;0.33333 &nbsp; 0.33333 &nbsp; 0.33333

&nbsp; &nbsp;0.33725 &nbsp; 0.33725 &nbsp; 0.33725

&nbsp; &nbsp;0.34118 &nbsp; 0.34118 &nbsp; 0.34118

&nbsp; &nbsp;0.34510 &nbsp; 0.34510 &nbsp; 0.34510

&nbsp; &nbsp;0.34902 &nbsp; 0.34902 &nbsp; 0.34902

&nbsp; &nbsp;0.35294 &nbsp; 0.35294 &nbsp; 0.35294

&nbsp; &nbsp;0.35686 &nbsp; 0.35686 &nbsp; 0.35686

&nbsp; &nbsp;0.36078 &nbsp; 0.36078 &nbsp; 0.36078

&nbsp; &nbsp;0.36471 &nbsp; 0.36471 &nbsp; 0.36471

&nbsp; &nbsp;0.36863 &nbsp; 0.36863 &nbsp; 0.36863

&nbsp; &nbsp;0.37255 &nbsp; 0.37255 &nbsp; 0.37255

&nbsp; &nbsp;0.37647 &nbsp; 0.37647 &nbsp; 0.37647

&nbsp; &nbsp;0.38039 &nbsp; 0.38039 &nbsp; 0.38039

&nbsp; &nbsp;0.38431 &nbsp; 0.38431 &nbsp; 0.38431

&nbsp; &nbsp;0.38824 &nbsp; 0.38824 &nbsp; 0.38824

&nbsp; &nbsp;0.39216 &nbsp; 0.39216 &nbsp; 0.39216

&nbsp; &nbsp;0.39608 &nbsp; 0.39608 &nbsp; 0.39608

&nbsp; &nbsp;0.40000 &nbsp; 0.40000 &nbsp; 0.40000

&nbsp; &nbsp;0.40392 &nbsp; 0.40392 &nbsp; 0.40392

&nbsp; &nbsp;0.40784 &nbsp; 0.40784 &nbsp; 0.40784

&nbsp; &nbsp;0.41176 &nbsp; 0.41176 &nbsp; 0.41176

&nbsp; &nbsp;0.41569 &nbsp; 0.41569 &nbsp; 0.41569

&nbsp; &nbsp;0.41961 &nbsp; 0.41961 &nbsp; 0.41961

&nbsp; &nbsp;0.42353 &nbsp; 0.42353 &nbsp; 0.42353

&nbsp; &nbsp;0.42745 &nbsp; 0.42745 &nbsp; 0.42745

&nbsp; &nbsp;0.43137 &nbsp; 0.43137 &nbsp; 0.43137

&nbsp; &nbsp;0.43529 &nbsp; 0.43529 &nbsp; 0.43529

&nbsp; &nbsp;0.43922 &nbsp; 0.43922 &nbsp; 0.43922

&nbsp; &nbsp;0.44314 &nbsp; 0.44314 &nbsp; 0.44314

&nbsp; &nbsp;0.44706 &nbsp; 0.44706 &nbsp; 0.44706

&nbsp; &nbsp;0.45098 &nbsp; 0.45098 &nbsp; 0.45098

&nbsp; &nbsp;0.45490 &nbsp; 0.45490 &nbsp; 0.45490

&nbsp; &nbsp;0.45882 &nbsp; 0.45882 &nbsp; 0.45882

&nbsp; &nbsp;0.46275 &nbsp; 0.46275 &nbsp; 0.46275

&nbsp; &nbsp;0.46667 &nbsp; 0.46667 &nbsp; 0.46667

&nbsp; &nbsp;0.47059 &nbsp; 0.47059 &nbsp; 0.47059

&nbsp; &nbsp;0.47451 &nbsp; 0.47451 &nbsp; 0.47451

&nbsp; &nbsp;0.47843 &nbsp; 0.47843 &nbsp; 0.47843

&nbsp; &nbsp;0.48235 &nbsp; 0.48235 &nbsp; 0.48235

&nbsp; &nbsp;0.48627 &nbsp; 0.48627 &nbsp; 0.48627

&nbsp; &nbsp;0.49020 &nbsp; 0.49020 &nbsp; 0.49020

&nbsp; &nbsp;0.49412 &nbsp; 0.49412 &nbsp; 0.49412

&nbsp; &nbsp;0.49804 &nbsp; 0.49804 &nbsp; 0.49804

&nbsp; &nbsp;0.50196 &nbsp; 0.50196 &nbsp; 0.50196

&nbsp; &nbsp;0.50588 &nbsp; 0.50588 &nbsp; 0.50588

&nbsp; &nbsp;0.50980 &nbsp; 0.50980 &nbsp; 0.50980

&nbsp; &nbsp;0.51373 &nbsp; 0.51373 &nbsp; 0.51373

&nbsp; &nbsp;0.51765 &nbsp; 0.51765 &nbsp; 0.51765

&nbsp; &nbsp;0.52157 &nbsp; 0.52157 &nbsp; 0.52157

&nbsp; &nbsp;0.52549 &nbsp; 0.52549 &nbsp; 0.52549

&nbsp; &nbsp;0.52941 &nbsp; 0.52941 &nbsp; 0.52941

&nbsp; &nbsp;0.53333 &nbsp; 0.53333 &nbsp; 0.53333

&nbsp; &nbsp;0.53725 &nbsp; 0.53725 &nbsp; 0.53725

&nbsp; &nbsp;0.54118 &nbsp; 0.54118 &nbsp; 0.54118

&nbsp; &nbsp;0.54510 &nbsp; 0.54510 &nbsp; 0.54510

&nbsp; &nbsp;0.54902 &nbsp; 0.54902 &nbsp; 0.54902

&nbsp; &nbsp;0.55294 &nbsp; 0.55294 &nbsp; 0.55294

&nbsp; &nbsp;0.55686 &nbsp; 0.55686 &nbsp; 0.55686

&nbsp; &nbsp;0.56078 &nbsp; 0.56078 &nbsp; 0.56078

&nbsp; &nbsp;0.56471 &nbsp; 0.56471 &nbsp; 0.56471

&nbsp; &nbsp;0.56863 &nbsp; 0.56863 &nbsp; 0.56863

&nbsp; &nbsp;0.57255 &nbsp; 0.57255 &nbsp; 0.57255

&nbsp; &nbsp;0.57647 &nbsp; 0.57647 &nbsp; 0.57647

&nbsp; &nbsp;0.58039 &nbsp; 0.58039 &nbsp; 0.58039

&nbsp; &nbsp;0.58431 &nbsp; 0.58431 &nbsp; 0.58431

&nbsp; &nbsp;0.58824 &nbsp; 0.58824 &nbsp; 0.58824

&nbsp; &nbsp;0.59216 &nbsp; 0.59216 &nbsp; 0.59216

&nbsp; &nbsp;0.59608 &nbsp; 0.59608 &nbsp; 0.59608

&nbsp; &nbsp;0.60000 &nbsp; 0.60000 &nbsp; 0.60000

&nbsp; &nbsp;0.60392 &nbsp; 0.60392 &nbsp; 0.60392

&nbsp; &nbsp;0.60784 &nbsp; 0.60784 &nbsp; 0.60784

&nbsp; &nbsp;0.61176 &nbsp; 0.61176 &nbsp; 0.61176

&nbsp; &nbsp;0.61569 &nbsp; 0.61569 &nbsp; 0.61569

&nbsp; &nbsp;0.61961 &nbsp; 0.61961 &nbsp; 0.61961

&nbsp; &nbsp;0.62353 &nbsp; 0.62353 &nbsp; 0.62353

&nbsp; &nbsp;0.62745 &nbsp; 0.62745 &nbsp; 0.62745

&nbsp; &nbsp;0.63137 &nbsp; 0.63137 &nbsp; 0.63137

&nbsp; &nbsp;0.63529 &nbsp; 0.63529 &nbsp; 0.63529

&nbsp; &nbsp;0.63922 &nbsp; 0.63922 &nbsp; 0.63922

&nbsp; &nbsp;0.64314 &nbsp; 0.64314 &nbsp; 0.64314

&nbsp; &nbsp;0.64706 &nbsp; 0.64706 &nbsp; 0.64706

&nbsp; &nbsp;0.65098 &nbsp; 0.65098 &nbsp; 0.65098

&nbsp; &nbsp;0.65490 &nbsp; 0.65490 &nbsp; 0.65490

&nbsp; &nbsp;0.65882 &nbsp; 0.65882 &nbsp; 0.65882

&nbsp; &nbsp;0.66275 &nbsp; 0.66275 &nbsp; 0.66275

&nbsp; &nbsp;0.66667 &nbsp; 0.66667 &nbsp; 0.66667

&nbsp; &nbsp;0.67059 &nbsp; 0.67059 &nbsp; 0.67059

&nbsp; &nbsp;0.67451 &nbsp; 0.67451 &nbsp; 0.67451

&nbsp; &nbsp;0.67843 &nbsp; 0.67843 &nbsp; 0.67843

&nbsp; &nbsp;0.68235 &nbsp; 0.68235 &nbsp; 0.68235

&nbsp; &nbsp;0.68627 &nbsp; 0.68627 &nbsp; 0.68627

&nbsp; &nbsp;0.69020 &nbsp; 0.69020 &nbsp; 0.69020

&nbsp; &nbsp;0.69412 &nbsp; 0.69412 &nbsp; 0.69412

&nbsp; &nbsp;0.69804 &nbsp; 0.69804 &nbsp; 0.69804

&nbsp; &nbsp;0.70196 &nbsp; 0.70196 &nbsp; 0.70196

&nbsp; &nbsp;0.70588 &nbsp; 0.70588 &nbsp; 0.70588

&nbsp; &nbsp;0.70980 &nbsp; 0.70980 &nbsp; 0.70980

&nbsp; &nbsp;0.71373 &nbsp; 0.71373 &nbsp; 0.71373

&nbsp; &nbsp;0.71765 &nbsp; 0.71765 &nbsp; 0.71765

&nbsp; &nbsp;0.72157 &nbsp; 0.72157 &nbsp; 0.72157

&nbsp; &nbsp;0.72549 &nbsp; 0.72549 &nbsp; 0.72549

&nbsp; &nbsp;0.72941 &nbsp; 0.72941 &nbsp; 0.72941

&nbsp; &nbsp;0.73333 &nbsp; 0.73333 &nbsp; 0.73333

&nbsp; &nbsp;0.73725 &nbsp; 0.73725 &nbsp; 0.73725

&nbsp; &nbsp;0.74118 &nbsp; 0.74118 &nbsp; 0.74118

&nbsp; &nbsp;0.74510 &nbsp; 0.74510 &nbsp; 0.74510

&nbsp; &nbsp;0.74902 &nbsp; 0.74902 &nbsp; 0.74902

&nbsp; &nbsp;0.75294 &nbsp; 0.75294 &nbsp; 0.75294

&nbsp; &nbsp;0.75686 &nbsp; 0.75686 &nbsp; 0.75686

&nbsp; &nbsp;0.76078 &nbsp; 0.76078 &nbsp; 0.76078

&nbsp; &nbsp;0.76471 &nbsp; 0.76471 &nbsp; 0.76471

&nbsp; &nbsp;0.76863 &nbsp; 0.76863 &nbsp; 0.76863

&nbsp; &nbsp;0.77255 &nbsp; 0.77255 &nbsp; 0.77255

&nbsp; &nbsp;0.77647 &nbsp; 0.77647 &nbsp; 0.77647

&nbsp; &nbsp;0.78039 &nbsp; 0.78039 &nbsp; 0.78039

&nbsp; &nbsp;0.78431 &nbsp; 0.78431 &nbsp; 0.78431

&nbsp; &nbsp;0.78824 &nbsp; 0.78824 &nbsp; 0.78824

&nbsp; &nbsp;0.79216 &nbsp; 0.79216 &nbsp; 0.79216

&nbsp; &nbsp;0.79608 &nbsp; 0.79608 &nbsp; 0.79608

&nbsp; &nbsp;0.80000 &nbsp; 0.80000 &nbsp; 0.80000

&nbsp; &nbsp;0.80392 &nbsp; 0.80392 &nbsp; 0.80392

&nbsp; &nbsp;0.80784 &nbsp; 0.80784 &nbsp; 0.80784

&nbsp; &nbsp;0.81176 &nbsp; 0.81176 &nbsp; 0.81176

&nbsp; &nbsp;0.81569 &nbsp; 0.81569 &nbsp; 0.81569

&nbsp; &nbsp;0.81961 &nbsp; 0.81961 &nbsp; 0.81961

&nbsp; &nbsp;0.82353 &nbsp; 0.82353 &nbsp; 0.82353

&nbsp; &nbsp;0.82745 &nbsp; 0.82745 &nbsp; 0.82745

&nbsp; &nbsp;0.83137 &nbsp; 0.83137 &nbsp; 0.83137

&nbsp; &nbsp;0.83529 &nbsp; 0.83529 &nbsp; 0.83529

&nbsp; &nbsp;0.83922 &nbsp; 0.83922 &nbsp; 0.83922

&nbsp; &nbsp;0.84314 &nbsp; 0.84314 &nbsp; 0.84314

&nbsp; &nbsp;0.84706 &nbsp; 0.84706 &nbsp; 0.84706

&nbsp; &nbsp;0.85098 &nbsp; 0.85098 &nbsp; 0.85098

&nbsp; &nbsp;0.85490 &nbsp; 0.85490 &nbsp; 0.85490

&nbsp; &nbsp;0.85882 &nbsp; 0.85882 &nbsp; 0.85882

&nbsp; &nbsp;0.86275 &nbsp; 0.86275 &nbsp; 0.86275

&nbsp; &nbsp;0.86667 &nbsp; 0.86667 &nbsp; 0.86667

&nbsp; &nbsp;0.87059 &nbsp; 0.87059 &nbsp; 0.87059

&nbsp; &nbsp;0.87451 &nbsp; 0.87451 &nbsp; 0.87451

&nbsp; &nbsp;0.87843 &nbsp; 0.87843 &nbsp; 0.87843

&nbsp; &nbsp;0.88235 &nbsp; 0.88235 &nbsp; 0.88235

&nbsp; &nbsp;0.88627 &nbsp; 0.88627 &nbsp; 0.88627

&nbsp; &nbsp;0.89020 &nbsp; 0.89020 &nbsp; 0.89020

&nbsp; &nbsp;0.89412 &nbsp; 0.89412 &nbsp; 0.89412

&nbsp; &nbsp;0.89804 &nbsp; 0.89804 &nbsp; 0.89804

&nbsp; &nbsp;0.90196 &nbsp; 0.90196 &nbsp; 0.90196

&nbsp; &nbsp;0.90588 &nbsp; 0.90588 &nbsp; 0.90588

&nbsp; &nbsp;0.90980 &nbsp; 0.90980 &nbsp; 0.90980

&nbsp; &nbsp;0.91373 &nbsp; 0.91373 &nbsp; 0.91373

&nbsp; &nbsp;0.91765 &nbsp; 0.91765 &nbsp; 0.91765

&nbsp; &nbsp;0.92157 &nbsp; 0.92157 &nbsp; 0.92157

&nbsp; &nbsp;0.92549 &nbsp; 0.92549 &nbsp; 0.92549

&nbsp; &nbsp;0.92941 &nbsp; 0.92941 &nbsp; 0.92941

&nbsp; &nbsp;0.93333 &nbsp; 0.93333 &nbsp; 0.93333

&nbsp; &nbsp;0.93725 &nbsp; 0.93725 &nbsp; 0.93725

&nbsp; &nbsp;0.94118 &nbsp; 0.94118 &nbsp; 0.94118

&nbsp; &nbsp;0.94510 &nbsp; 0.94510 &nbsp; 0.94510

&nbsp; &nbsp;0.94902 &nbsp; 0.94902 &nbsp; 0.94902

&nbsp; &nbsp;0.95294 &nbsp; 0.95294 &nbsp; 0.95294

&nbsp; &nbsp;0.95686 &nbsp; 0.95686 &nbsp; 0.95686

&nbsp; &nbsp;0.96078 &nbsp; 0.96078 &nbsp; 0.96078

&nbsp; &nbsp;0.96471 &nbsp; 0.96471 &nbsp; 0.96471

&nbsp; &nbsp;0.96863 &nbsp; 0.96863 &nbsp; 0.96863

&nbsp; &nbsp;0.97255 &nbsp; 0.97255 &nbsp; 0.97255

&nbsp; &nbsp;0.97647 &nbsp; 0.97647 &nbsp; 0.97647

&nbsp; &nbsp;0.98039 &nbsp; 0.98039 &nbsp; 0.98039

&nbsp; &nbsp;0.98431 &nbsp; 0.98431 &nbsp; 0.98431

&nbsp; &nbsp;0.98824 &nbsp; 0.98824 &nbsp; 0.98824

&nbsp; &nbsp;0.99216 &nbsp; 0.99216 &nbsp; 0.99216

&nbsp; &nbsp;0.99608 &nbsp; 0.99608 &nbsp; 0.99608

&nbsp; &nbsp;1.00000 &nbsp; 1.00000 &nbsp; 1.00000

  

b = &nbsp;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.&nbsp; For details, type 'warranty'.

  

Octave was configured for "x86\_64-pc-linux-gnu".

  

Additional information about Octave is available at [http://www.octave.org](http://www.octave.org).

  

Please contribute if you find this software useful.

For more information, visit [http://www.octave.org/get- involved.html](http://www.octave.org/get-involved.html)

  

Read [http://www.octave.org/bugs. html](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 = &nbsp;1

maxsmooth = &nbsp;8192

&nbsp;

  

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](http://www.psychtoolbox.org) and the

INFO: examples in the PDF presentation in PsychDocumentation/ Psychtoolbox3-Slides.pdf for more info and timing tips.

  

**\>\> DotDemo &nbsp;% 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 =

  

&nbsp; &nbsp; &nbsp;1

  

  

maxsmooth =

  

&nbsp; &nbsp; &nbsp; &nbsp; 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').

\>\>&nbsp;

  

**\>\> 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)

&nbsp; &nbsp; error('Sorry, this M-File cannot execute on your combination of graphics hardware and driver due to

&nbsp; &nbsp; complete lack of GLSL support.');

  

  

Error in LoadShaderFromFile (line 33)

AssertGLSL;

  

Error in PsychColorCorrection (line 578)

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; icmShaders = LoadShaderFromFile(' ICMSimpleGammaCorrectionShader .frag.txt', [], debuglevel);

  

Error in PsychImaging\>PostConfiguration (line 3879)

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; [icmshader icmstring icmconfig icmoverrideMain] =

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; PsychColorCorrection(' GetCompiledShaders', win, 1);

  

Error in PsychImaging (line 2161)

&nbsp; &nbsp; PostConfiguration(reqs, win, clearcolor, slavewin);

  

Error in AdditiveBlendingForLinearSuper positionTutorial (line 357)

&nbsp; &nbsp; [w, wRect]=PsychImaging(' OpenWindow', screenNumber, 0.5, lrect);

&nbsp;

  

**# 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)

---

<div class="post-metadata">

**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\
**Post date:** [December 20, 2016, 9:43am UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/2 "2016-12-20T09:43:13Z")

</div>

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&nbsp; 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&nbsp; 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

---

<div class="post-metadata">

**Author:** ![hormet.yiltiz](https://avatars.discourse-cdn.com/v4/letter/h/4af34b/32.png) [@hormet.yiltiz](https://psychtoolbox.discourse.group/u/hormet.yiltiz)\
**Post date:** [December 20, 2016, 11:32pm UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/3 "2016-12-20T23:32:33Z")

</div>

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.&nbsp;

  

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&nbsp;xserver-xorg-video-all installed though).&nbsp;
  

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

&nbsp; &nbsp; load\_packages\_and\_dependencies at line 47 column 5

&nbsp; &nbsp; load\_packages at line 60 column 3

&nbsp; &nbsp; pkg at line 422 column 7

&nbsp; &nbsp; /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 &nbsp;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 = &nbsp;1

maxsmooth = &nbsp;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') &nbsp;% 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 &nbsp;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.

---

<div class="post-metadata">

**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\
**Post date:** [December 21, 2016, 1:15am UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/4 "2016-12-21T01:15:25Z")

</div>

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.&nbsp;

  

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&nbsp;xserver-xorg-video-all installed though).&nbsp;
  
-\> 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

&nbsp; &nbsp; load\_packages\_and\_dependencies at line 47 column 5

&nbsp; &nbsp; load\_packages at line 60 column 3

&nbsp; &nbsp; pkg at line 422 column 7

&nbsp; &nbsp; /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 &nbsp;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 = &nbsp;1

maxsmooth = &nbsp;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') &nbsp;% 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 &nbsp;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.

---

<div class="post-metadata">

**Author:** ![hormet.yiltiz](https://avatars.discourse-cdn.com/v4/letter/h/4af34b/32.png) [@hormet.yiltiz](https://psychtoolbox.discourse.group/u/hormet.yiltiz)\
**Post date:** [December 22, 2016, 12:13am UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/5 "2016-12-22T00:13:45Z")

</div>

About "fglrx":&nbsp;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 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;blacklist-modem.conf &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;disable-mmc.conf

amddeepcolor-psychtoolbox.conf &nbsp;blacklist-opensource-graphics.conf &nbsp;dkms.conf

blacklist-ar8161.conf &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; blacklist-oss.conf@ &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; fbdev-blacklist.conf

blacklist-ath\_pci.conf &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;blacklist-psychtoolbox.conf &nbsp; &nbsp; &nbsp; &nbsp; intel-microcode-blacklist.conf

blacklist.conf &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;blacklist-rare-network.conf &nbsp; &nbsp; &nbsp; &nbsp; iwlwifi.conf

blacklist-firewire.conf &nbsp; &nbsp; &nbsp; &nbsp; blacklist-thinkpad.conf &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; mlx4.conf

blacklist-framebuffer.conf &nbsp; &nbsp; &nbsp;blacklist-watchdog.conf &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 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).&nbsp;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&nbsp;  

  

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&nbsp;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.&nbsp;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 %%%%%%%%%%%%%%%%

---

<div class="post-metadata">

**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\
**Post date:** [December 22, 2016, 1:52am UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/6 "2016-12-22T01:52:24Z")

</div>

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](https://youtu.be/KIHrjgZJHZA?t=4h38m43s)  
  
-mario

---

<div class="post-metadata">

**Author:** ![hormet.yiltiz](https://avatars.discourse-cdn.com/v4/letter/h/4af34b/32.png) [@hormet.yiltiz](https://psychtoolbox.discourse.group/u/hormet.yiltiz)\
**Post date:** [December 22, 2016, 2:20am UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/7 "2016-12-22T02:20:46Z")

</div>

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](http://psychtoolbox.org/ubuntu/)

 

 |   

  |
 |   

  |  
 
   [Psychtoolbox-3 - Using Psychophysics Toolbox on Ubuntu](http://psychtoolbox.org/ubuntu/)
Psychtoolbox-3 Psychophysics Toolbox Version 3 (PTB-3) is a free set of Matlab and GNU Octave functions for vision and neuroscience research. 

 
  |   

  |
|   
 [View on psychtoolbox.org](http://psychtoolbox.org/ubuntu/)
  |   
  Preview by Yahoo  
  |
|   

  |
 
 

  

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

  

  

You are right!&nbsp;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. &nbsp;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. &nbsp;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. &nbsp;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

---

<div class="post-metadata">

**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\
**Post date:** [December 22, 2016, 2:52am UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/8 "2016-12-22T02:52:11Z")

</div>

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&nbsp; 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

---

<div class="post-metadata">

**Author:** ![hormet.yiltiz](https://avatars.discourse-cdn.com/v4/letter/h/4af34b/32.png) [@hormet.yiltiz](https://psychtoolbox.discourse.group/u/hormet.yiltiz)\
**Post date:** [December 22, 2016, 5:40pm UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/9 "2016-12-22T17:40:43Z")

</div>

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?&nbsp;
  

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).&nbsp;

  

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

  

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

root@HP-ZBook-17-G2 /h/hyiltiz# glxgears -info

GL\_RENDERER &nbsp; = Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits)

GL\_VERSION &nbsp; &nbsp;= 3.0 Mesa 11.2.0

GL\_VENDOR &nbsp; &nbsp; = 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&nbsp;

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

&nbsp; &nbsp; load\_packages\_and\_dependencies at line 47 column 5

&nbsp; &nbsp; load\_packages at line 60 column 3

&nbsp; &nbsp; pkg at line 422 column 7

&nbsp; &nbsp; /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 &nbsp;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 = &nbsp;1

maxsmooth = &nbsp;255

&nbsp;

  

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&nbsp; 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

  

&nbsp;

---

<div class="post-metadata">

**Author:** ![hormet.yiltiz](https://avatars.discourse-cdn.com/v4/letter/h/4af34b/32.png) [@hormet.yiltiz](https://psychtoolbox.discourse.group/u/hormet.yiltiz)\
**Post date:** [December 22, 2016, 6:16pm UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/10 "2016-12-22T18:16:26Z")

</div>

OK. I found out that, Ubuntu along with their "collaborators" _gracefully_ tripped free software drivers in more than one way.&nbsp;
  

In /etc/modprobe.d/, not only there blacklisted radeon, they also blacklisted **radeonfb** &nbsp;(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 **&nbsp; 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

&nbsp; &nbsp; load\_packages\_and\_dependencies at line 47 column 5

&nbsp; &nbsp; load\_packages at line 60 column 3

&nbsp; &nbsp; pkg at line 422 column 7

&nbsp; &nbsp; /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 &nbsp;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 = &nbsp;1

maxsmooth = &nbsp;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.

  

&nbsp;

---

<div class="post-metadata">

**Author:** ![hormet.yiltiz](https://avatars.discourse-cdn.com/v4/letter/h/4af34b/32.png) [@hormet.yiltiz](https://psychtoolbox.discourse.group/u/hormet.yiltiz)\
**Post date:** [December 22, 2016, 6:36pm UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/11 "2016-12-22T18:36:49Z")

</div>

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 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 1515520 &nbsp;43

i2c\_algo\_bit &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 16384 &nbsp;1 radeon

ttm &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;94208 &nbsp;1 radeon

drm\_kms\_helper &nbsp; &nbsp; &nbsp; &nbsp;155648 &nbsp;1 radeon

drm &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 364544 &nbsp;6 ttm,drm\_kms\_helper,radeon

root@HP-ZBook-17-G2 # cat /sys/module/radeon/parameters/deep\_color&nbsp;

1

root@HP-ZBook-17-G2 # cat /sys/module/drm/parameters/debug&nbsp;

0

root@HP-ZBook-17-G2 # echo 1 \> &nbsp;/sys/module/drm/parameters/debug&nbsp;

root@HP-ZBook-17-G2 # cat /sys/module/drm/parameters/debug&nbsp;

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

&nbsp; &nbsp;1920x1080 &nbsp; &nbsp; 60.02\*+

&nbsp; &nbsp;1680x1050 &nbsp; &nbsp; 59.95 &nbsp;

&nbsp; &nbsp;1400x1050 &nbsp; &nbsp; 59.98 &nbsp;

&nbsp; &nbsp;1280x1024 &nbsp; &nbsp; 59.89 &nbsp;

&nbsp; &nbsp;1440x900 &nbsp; &nbsp; &nbsp;59.89 &nbsp;

&nbsp; &nbsp;1280x960 &nbsp; &nbsp; &nbsp;59.94 &nbsp;

&nbsp; &nbsp;1280x854 &nbsp; &nbsp; &nbsp;59.89 &nbsp;

&nbsp; &nbsp;1280x800 &nbsp; &nbsp; &nbsp;59.81 &nbsp;

&nbsp; &nbsp;1280x720 &nbsp; &nbsp; &nbsp;59.86 &nbsp;

&nbsp; &nbsp;1152x768 &nbsp; &nbsp; &nbsp;59.78 &nbsp;

&nbsp; &nbsp;1024x768 &nbsp; &nbsp; &nbsp;59.92 &nbsp;

&nbsp; &nbsp;800x600 &nbsp; &nbsp; &nbsp; 59.86 &nbsp;

&nbsp; &nbsp;848x480 &nbsp; &nbsp; &nbsp; 59.66 &nbsp;

&nbsp; &nbsp;720x480 &nbsp; &nbsp; &nbsp; 59.71 &nbsp;

&nbsp; &nbsp;640x480 &nbsp; &nbsp; &nbsp; 59.38 &nbsp;

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

&nbsp; &nbsp;1920x1080 &nbsp; &nbsp; 60.02\*+

&nbsp; &nbsp;1680x1050 &nbsp; &nbsp; 59.95 &nbsp;

&nbsp; &nbsp;1400x1050 &nbsp; &nbsp; 59.98 &nbsp;

&nbsp; &nbsp;1280x1024 &nbsp; &nbsp; 59.89 &nbsp;

&nbsp; &nbsp;1440x900 &nbsp; &nbsp; &nbsp;59.89 &nbsp;

&nbsp; &nbsp;1280x960 &nbsp; &nbsp; &nbsp;59.94 &nbsp;

&nbsp; &nbsp;1280x854 &nbsp; &nbsp; &nbsp;59.89 &nbsp;

&nbsp; &nbsp;1280x800 &nbsp; &nbsp; &nbsp;59.81 &nbsp;

&nbsp; &nbsp;1280x720 &nbsp; &nbsp; &nbsp;59.86 &nbsp;

&nbsp; &nbsp;1152x768 &nbsp; &nbsp; &nbsp;59.78 &nbsp;

&nbsp; &nbsp;1024x768 &nbsp; &nbsp; &nbsp;59.92 &nbsp;

&nbsp; &nbsp;800x600 &nbsp; &nbsp; &nbsp; 59.86 &nbsp;

&nbsp; &nbsp;848x480 &nbsp; &nbsp; &nbsp; 59.66 &nbsp;

&nbsp; &nbsp;720x480 &nbsp; &nbsp; &nbsp; 59.71 &nbsp;

&nbsp; &nbsp;640x480 &nbsp; &nbsp; &nbsp; 59.38 &nbsp;

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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;494.116879] [drm:radeon\_get\_monitor\_bpc] eDP-1: Display bpc=0, returned bpc=6

  

  

~\> octave --no-gui&nbsp;

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. &nbsp;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

&nbsp; &nbsp; load\_packages\_and\_dependencies at line 47 column 5

&nbsp; &nbsp; load\_packages at line 60 column 3

&nbsp; &nbsp; pkg at line 422 column 7

&nbsp; &nbsp; /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 &nbsp;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.

  

> 

\>\>&nbsp;

---

<div class="post-metadata">

**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\
**Post date:** [December 22, 2016, 6:43pm UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/12 "2016-12-22T18:43:02Z")

</div>

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?&nbsp;
  
--\> 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).&nbsp;

  

I looked around in the Ubuntu forums, but none of the posts about not&nbsp;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 &nbsp; = Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits)

GL\_VERSION &nbsp; &nbsp;= 3.0 Mesa 11.2.0

GL\_VENDOR &nbsp; &nbsp; = 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&nbsp;

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

&nbsp; &nbsp; load\_packages\_and\_dependencies at line 47 column 5

&nbsp; &nbsp; load\_packages at line 60 column 3

&nbsp; &nbsp; pkg at line 422 column 7

&nbsp; &nbsp; /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 &nbsp;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 = &nbsp;1

maxsmooth = &nbsp;255

&nbsp;

  

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&nbsp; 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

  

&nbsp;

---

<div class="post-metadata">

**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\
**Post date:** [December 22, 2016, 8:05pm UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/13 "2016-12-22T20:05:13Z")

</div>

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.&nbsp;
  
-\> 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_&nbsp;_OS_&nbsp;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

---

<div class="post-metadata">

**Author:** ![hormet.yiltiz](https://avatars.discourse-cdn.com/v4/letter/h/4af34b/32.png) [@hormet.yiltiz](https://psychtoolbox.discourse.group/u/hormet.yiltiz)\
**Post date:** [December 22, 2016, 8:59pm UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/14 "2016-12-22T20:59:48Z")

</div>

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.

  

[https://gist.github.com/hyiltiz/c62df8f470b471bce2b75df04b331232](https://gist.github.com/hyiltiz/c62df8f470b471bce2b75df04b331232)

---

<div class="post-metadata">

**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\
**Post date:** [December 22, 2016, 9:57pm UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/15 "2016-12-22T21:57:11Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![hormet.yiltiz](https://avatars.discourse-cdn.com/v4/letter/h/4af34b/32.png) [@hormet.yiltiz](https://psychtoolbox.discourse.group/u/hormet.yiltiz)\
**Post date:** [December 22, 2016, 11:44pm UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/16 "2016-12-22T23:44:56Z")

</div>

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: [&nbsp; &nbsp;6.353789] [drm] Radeon Display Connectors

8889:Dec 22 13:17:31 HP-ZBook-17-G2 kernel: [&nbsp; &nbsp;6.353789] [drm] Connector 0:

8895:Dec 22 13:17:31 HP-ZBook-17-G2 kernel: [&nbsp; &nbsp;6.353793] [drm] Connector 1:

8901:Dec 22 13:17:31 HP-ZBook-17-G2 kernel: [&nbsp; &nbsp;6.353796] [drm] Connector 2:

8907:Dec 22 13:17:31 HP-ZBook-17-G2 kernel: [&nbsp; &nbsp;6.353799] [drm] Connector 3:

8913:Dec 22 13:17:31 HP-ZBook-17-G2 kernel: [&nbsp; &nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;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: [&nbsp;498.459512] [drm:drm\_ioctl] pid=1373, dev=0xe200, auth=1, DRM\_IOCTL\_MODE\_GETCONNECTOR

---

<div class="post-metadata">

**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\
**Post date:** [December 23, 2016, 4:44pm UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/17 "2016-12-23T16:44:23Z")

</div>

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](https://wiki.archlinux.org/index.php/kernel_mode_setting#Forcing_modes_and_EDID)
 

 |   

  |
 |   

  |  
 
   [Kernel mode setting - ArchWiki](https://wiki.archlinux.org/index.php/kernel_mode_setting#Forcing_modes_and_EDID)
Related articles ATI Intel graphics Nouveau This article or section needs expansion. Reason: KMS and rootless X (1.16), see Talk:Kernel mode setting and Xorg#Rootless Xorg (v1.16). 

 
  |   

  |
|   
 [View on wiki.archlinux.org](https://wiki.archlinux.org/index.php/kernel_mode_setting#Forcing_modes_and_EDID)
  |   
  Preview by Yahoo  
  |
|   

  |
 
 

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

---

<div class="post-metadata">

**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\
**Post date:** [December 23, 2016, 10:24pm UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/18 "2016-12-23T22:24:59Z")

</div>

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: [&nbsp; 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: [&nbsp; 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

---

<div class="post-metadata">

**Author:** ![hormet.yiltiz](https://avatars.discourse-cdn.com/v4/letter/h/4af34b/32.png) [@hormet.yiltiz](https://psychtoolbox.discourse.group/u/hormet.yiltiz)\
**Post date:** [December 24, 2016, 5:02pm UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/19 "2016-12-24T17:02:06Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![hormet.yiltiz](https://avatars.discourse-cdn.com/v4/letter/h/4af34b/32.png) [@hormet.yiltiz](https://psychtoolbox.discourse.group/u/hormet.yiltiz)\
**Post date:** [December 24, 2016, 5:21pm UTC](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351/20 "2016-12-24T17:21:46Z")

</div>

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

root@HP-ZBook-17-G2 ~# get-edid | edid-decode&nbsp;

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: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;00 ff ff ff ff ff ff 00

serial number: &nbsp; 30 e4 fc 02 00 00 00 00 00 14

version: &nbsp; &nbsp; &nbsp; &nbsp; 01 04

basic params: &nbsp; &nbsp;b0 26 15 78 0a

chroma info: &nbsp; &nbsp; b8 25 af 4e 36 b7 25 0b 50 54

established: &nbsp; &nbsp; 00 00 00

standard: &nbsp; &nbsp; &nbsp; &nbsp;01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01

descriptor 1: &nbsp; &nbsp;2e 36 80 a0 70 38 1f 40 30 20 35 00 7e d7 10 00 00 19

descriptor 2: &nbsp; &nbsp;58 2b 80 a0 70 38 1f 40 30 20 35 00 7e d7 10 00 00 19

descriptor 3: &nbsp; &nbsp;00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

descriptor 4: &nbsp; &nbsp;26 2d 80 a0 70 38 1f 40 30 20 35 00 7e d7 10 00 00 19

extensions: &nbsp; &nbsp; &nbsp;00

checksum: &nbsp; &nbsp; &nbsp; &nbsp;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

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1920 1968 2000 2080 hborder 0

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1080 1083 1088 1111 vborder 0

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;-hsync -vsync&nbsp;

Detailed mode: Clock 110.960 MHz, 382 mm x 215 mm

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1920 1968 2000 2080 hborder 0

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1080 1083 1088 1111 vborder 0

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;-hsync -vsync&nbsp;

Manufacturer-specified data, tag 0

Detailed mode: Clock 115.580 MHz, 382 mm x 215 mm

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1920 1968 2000 2080 hborder 0

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1080 1083 1088 1111 vborder 0

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;-hsync -vsync&nbsp;

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

[Next page](https://psychtoolbox.discourse.group/t/howto-10-bpc-laptop-running-linux/351.md?page=2)