LinuxCNC on Intel Clear Linux

Thank you NTULINUX. A few years ago I started running my machines with QtDragon. I have not used axis ever since. I think your Gentoo build gives me the perfect reason to start gaining some experience with FlexGUI, which I think is a great initiative.

rebelx wrote:

Thank you NTULINUX. A few years ago I started running my machines with QtDragon. I have not used axis ever since. I think your Gentoo build gives me the perfect reason to start gaining some experience with FlexGUI, which I think is a great initiative.

JT made like a 5 line change to get FlexGUI working in Gentoo, ever since, FlexGUI has been rock solid with Gentoo.

Turboss and someone else (Lcvette I think) is working on porting qtpyvcp to pyside6. Once their migration is complete, I'll be pushing out a new Gentoo image with support for qtpyvcp. qtpyvcp currently is on Qt5, and Qt5 has been getting purged by the Gentoo devs and they've been dropping support for it all across the board. QtDragon is also based on Qt5. FlexGUI is your best bet right now as it uses Qt6 and I haven't had any troubles with it. Gmoccapy also works flawlessly.

Clear Linux is now EOL.

community.clearlinux.org/t/all-good-thin...clear-linux-os/10716

github.com/clearlinux/distribution

Quite typical of Intel. I paid a developer to do some work in Intel hardware that required a $50 annual licence from Intel. they shut it all down before the year was up.

<duplicate message; deleted>

Hi NTULINUX,

I finally had the chance to try out your Gentoo-based LinuxCNC distro on my N100 system — thanks for putting it together!

At first, I was a bit surprised (and honestly a little disappointed) because the initial latency results were significantly worse compared to my Debian 13 / KDE setup. I even posted my findings yesterday to share what I saw. However, after digging a bit deeper today, I discovered that when I installed your Gentoo distro onto a new NVMe drive, the BIOS settings had somehow been reset to defaults. That definitely explained the poor initial performance!
Once I re-applied the correct BIOS settings, the latency results improved considerably. While it's still not quite as good as what I get with my Debian 13 setup, it's much closer now. This seems to reinforce just how well LinuxCNC performs on Debian 13 — especially considering that my Debian system has full driver support, including for sound, whereas your Gentoo distro doesn’t include those drivers by default. When I disable the sound drivers on Debian, I get even lower latency, though honestly the out-of-the-box performance is already excellent, so no need to disable them.

I also noticed one strange behavior on Gentoo: although the Latency Histogram window is otherwise responsive, the graph and Elapsed Time sometimes appear to freeze and stop updating. Pressing the Reset button restarts the process, which confirms that the application itself isn't hanging — just the display updates seem to stop intermittently.

Below are the latency graphs for both systems after running for 30 minutes under the same conditions:

• 5x glxgears
• Heavy internet browsing with YouTube videos playing
• System stress via:
  

  $ stress-ng --cpu 4 --iomix 2 --vm 1 --vm-bytes 1G --timeout 2000s --metrics-brief

  
  
  
  
  
  
  
  
  Thanks again for your work on the Gentoo distro — curious to hear your thoughts!