Mach3 -> Camtronics -> Parallel P Replacement

I'll keep on the hunt regarding this ping time.

There was another thread you replied to with a Realtek having similar ping response.

I checked the BIOS on this ZBOXNANO-AD12 PC and its as up to date as possible. Version 2K131128.

root@cnc:~# dmesg | egrep -a "ZOTAC"
[ 0.000000] DMI: ZOTAC ZBOXNANO-AD12/ZBOXNANO-AD12, BIOS A261P020 11/28/2013

What made you think you had to build Linuxcnc from source ?

The whole point of the images was to enable a quick and easy setup to get going.

Unless of course you wanted a version other than 2.8

bbsr_5a wrote:

hi we got a external user that has quite a Good if not the best follow throu
gnipsel.com/linuxcnc/uspace/debian9-emc.html

look here

as you are new to the Linux system why dident you go for the almost redy to run Version on DVD Debian
just insertt the DVD and go ahed cabeling ans configurating

The forum supplied Mint images have the same functionality as the official Debian ones.
The Mint ones are setup for qtvcp out of the box.
Some little extras are all the HTML docs available offline via the cnc menu, desktop shortcuts to the forums and the linuxcnc GitHub page and lastly a desktop shortcut to a script that installs the dependencies to build linuxcnc. The desktop shortcut to the read me even has a reference to JT’s page regarding rebuilding linuxcnc.
If stable packages become available for qtpyvcp they’d go in as well.

This would be the reason.

Compiling from source is typically straight forward and is the least of my concern.

Ok cool just be aware that the HTML docs in the cnc menu will point to the 2.8 version unless of course you removed that package.

I stopped on the compile for the html docs 2.7.15 for it was complaining about a "convert" package that I was not talented enough to decipher using apt. I'm more of a yum dnf person.

I later learned about the dpkg-buildpackage stuff but was on my way to just using the online docs.

Ok that’s interesting.
Did you use the shortcut on the desktop to pull in the dependencies ? If you did and something is missing I’d like to know as I can add it to the script. I know there are some cryptic messages when building the docs but mostly it completes.
I usually use debuild -us -uc to build the packages. Which I think is mentioned somewhere in the docs forum or wiki and never had an issue.

Oh! humm I did not even bother with that install build deps thank you for letting me know that.

One thing that did not work since you are the one.. I choose to install over LVM. That all appeared to go ok until the very end building grub.

It was not a total requirement of mine just a habit building over LVM vols.

Last night I spent a bit of time trying to figure out if I could potentially improve the ping response and consistency.

After several attempts I ended up replacing the loaded r8169 with r8168 8.048.00-1module.

If this is a major item that I need to address please let me know as I am moving on with what I got.

I am not seeing a definitive difference between r8168 8.048.01/.02 (off realtek support) versions.

mirrors.edge.kernel.org/ubuntu/pool/univ...s_8.048.00-1_all.deb
dpkg -i r8168-dkms_8.048.00-1_all.deb

rdeeming@cnc:~$ modinfo r8168 | grep ver
version: 8.048.00-NAPI # Note: I believe the version is .01 it just does not reflect it here

rdeeming@cnc:~$ ping 192.168.1.121
PING 192.168.1.121 (192.168.1.121) 56(84) bytes of data.
64 bytes from 192.168.1.121: icmp_seq=1 ttl=64 time=0.278 ms
64 bytes from 192.168.1.121: icmp_seq=2 ttl=64 time=0.191 ms
64 bytes from 192.168.1.121: icmp_seq=3 ttl=64 time=0.193 ms
64 bytes from 192.168.1.121: icmp_seq=4 ttl=64 time=0.138 ms
64 bytes from 192.168.1.121: icmp_seq=5 ttl=64 time=0.152 ms
64 bytes from 192.168.1.121: icmp_seq=6 ttl=64 time=0.168 ms
64 bytes from 192.168.1.121: icmp_seq=7 ttl=64 time=0.196 ms
64 bytes from 192.168.1.121: icmp_seq=8 ttl=64 time=0.219 ms
64 bytes from 192.168.1.121: icmp_seq=9 ttl=64 time=0.205 ms
64 bytes from 192.168.1.121: icmp_seq=10 ttl=64 time=0.197 ms
64 bytes from 192.168.1.121: icmp_seq=11 ttl=64 time=0.156 ms
64 bytes from 192.168.1.121: icmp_seq=12 ttl=64 time=0.198 ms
64 bytes from 192.168.1.121: icmp_seq=13 ttl=64 time=0.173 ms
64 bytes from 192.168.1.121: icmp_seq=14 ttl=64 time=0.204 ms
64 bytes from 192.168.1.121: icmp_seq=15 ttl=64 time=0.154 ms
64 bytes from 192.168.1.121: icmp_seq=16 ttl=64 time=0.196 ms
^C
--- 192.168.1.121 ping statistics ---
16 packets transmitted, 16 received, 0% packet loss, time 15347ms
rtt min/avg/max/mdev = 0.138/0.188/0.278/0.035 ms.

All I've really done is installed the following to the Image
realtime kernel
linuxcnc
midnight commander
geany
gftp
Usually do the whole upgrade thing on the day of creating the ISO
Added a few bits and pieces to /etc/skel
Took away gimp's ability to be the default app for PDFs.
Added the deps for qtvcp and the required shortcuts
And the desktop shortcuts....... I guess no one really pays much attention to readmes or notes that come with the release announcements.

Apart from that everything else is standard Mint. Hard to tell what went wrong, my ESP is run down ATM .

I used to use LVM but went away from it. And it's probably a bit OTT for a machine that just sits around running a cnc machine. If all you are going to do is run a machine a 64GB partition is heaps.
As long as you clean out your apt cache after installing extra packages or upgrading things shouldn't get out of hand.