Upgraded to 2.7.13 -- W T F --

Found some info on installing Debian Stretch on your little PC.

forums.debian.net/viewtopic.php?f=17&t=127662

wiki.debian.org/InstallingDebianOn/Intel/NUC5PPYH

Update BIOS to version 50
Set BIOS boot configuration to "Linux" (necessary for newer kernels)
Install Debian netinst image and nonfree firmware

A great bit of info from JT about install fron the netinst cd.
Ignore the first line regarding the Wheezy install and precede with the Debian 9 instructions. Which covers the Recommendation to in the 2 above links to Install Debian netinst image and nonfree firmware
mesaus.com/info/debian-9-uspace.txt

My BIOS is version 54
downloadmirror.intel.com/26220/eng/PY_0055_ReleaseNotes.pdf
Have boot set to Linux

Will follow the Debian net install and see what happens.

Later...

OK done that and the first I run is latency-histogram --nobase >>> FREEZING!

So it's boots ok and the graphics is good.

Running the debian rt kernel ok, apart from the latency-histogram ?
Linuxcnc was installed as per JT's instructions, should be version 2.7.13 ?

Before you run the latency-histogram run [ (may have to use su or sudo)
That will display the messages and then start with an empty buffer so anything new wont be lost in a 1000 other messages.
Have you tried
When you go to close the latency-histogram window it does close ?

Is there anything in dmesg that looks odd ?

Did manage to get grub.cfg edited with isolcpus=2,3 before freezing again.
Did manage to get Axis to run and Gmoccapy after reboot
Now running latency test with 6 GLX gears

Will take a short brake and get my morning shower now that my water is heated up

So far so good, will do more extensive test during the day.

ozzyrob wrote: So it's boots ok and the graphics is good.

Running the debian rt kernel ok, apart from the latency-histogram ?
Linuxcnc was installed as per JT's instructions, should be version 2.7.13 ?

Before you run the latency-histogram run [

Code:

dmesg -c

(may have to use su or sudo)
That will display the messages and then start with an empty buffer so anything new wont be lost in a 1000 other messages.
Have you tried

Code:

latency-histogram --nobase --verbose

When you go to close the latency-histogram window it does close ?

Is there anything in dmesg that looks odd ?

Nothing in dmesg and yes window closes OK