Advanced Search

I wonder how the were inserted? Thank You , I will try it tommorrow.

[TRAJ}Axis XAxis YDelete .ini from those lines.

 
This is the .ini that I modified while working on the Z Axis Homing . 

Bumped into this today:
- Linux is a tool you use to extract value from your hardware.
- Windows is a tool Microsoft uses to extract value from you
-
Original comment here

User name @neilbrideau8520

Go give the man some likes.

Were are the error files located ? var/ Error ? This ubuntu is very unfamiliar to me .

Thx Peter. Really appreciate your help. Last question …. Can you tell if my realtek nic is using the dkms driver or not? I attached the output of a script that you posted somewhere.Like I said in the first posting, I didn’t know that Linux headers might have been necessary when I installed dkms.  

Might be usable with a 2 ms servo thread.

I would check how LinuxCNC runs now

 

Alright. I applied that command in the grub configurator, rebooted and ran the pinIRQ script again.
ping times look much better (dropped from 8 to 1.2), but I am still too high... right?

first

sudo ./pinirq.txt enp1s0
Cores: 4
Old CPU Mask: f
Set device enp1s0 IRQ 121 CPU mask to 8

then

cnc@linuxcnc:~/gcodes$ sudo chrt 99 ping -i .001 -q 10.10.10.10
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.
^C
--- 10.10.10.10 ping statistics ---
142832 packets transmitted, 142831 received, 0.000700123% packet loss, time 143400ms
rtt min/avg/max/mdev = 0.056/0.108/1.211/0.035 ms

 

No idea if I did anything wrong, but after I applied that line from above and rebooted, Debian won’t launch the desktop environment anymore. I can manually start xfce. Never mind 

Definitely do the grub (kernel command line) change, also the pinirq script will have
minimal effect unless you add the isolcpus line.

 

Hello everyone. 
I know there are plenty of other threads about this topic, and I think I read them all, still I struggle to solve the issues that I am having.

My setup is:

• Dell Wyse 5070 with Celeron J4105 4-core cpu THIN CLIENT
• realtek onboard NIC
• fresh Linuxcnc 2.9.3 install
• brandnew Mesa 7i76eu, flashed with pktUART firmware

I experience issues when I startup Linuxcnc / probebasic.
Most of the time the system errors out right after startup with "error following read...". Sometimes I am "lucky" and it works for maybe 5minutes before it errors out. 

What I did so far (after reading in this forum for 2 nights):

• I ran sudo chrt 99 ping -1.001 -q 10.10.10.10 to get some statistics. Here is the result:
  
  179555 packets transmitted, 179555 received, 0% packet loss, time 180656ms
  rtt min/avg/max/mdev = 0.052/0.065/8.974/0.036
  
• disabled all BIOS options regarding power management, hyperthreading, ... etc
• Installed R8168-dkms driver (sudo apt-get install r8168-dkms)
  While searching in this forum, I found that some people had to install linux headers first. I did not do that. 
  When I run a script to identify the used drivers (JCW posted this somewhere a while ago), i get the followig result:
  ./edriver.txt
  xargs: warning: options --max-args and --replace/-I/-i are mutually exclusive, ignoring previous --max-args value
  enp1s0 : r8169
  wlp0s12f0 : iwlwifi
  
  Is this result "expected? Or did the driver installation not work?
  Other people posted that they had to install linux-headers and purge the old driver... 
  
• then I found a script that JCW posted in another thread that pins the IRQ somewhere (I honestly dont really understand whats behind this, but still this is the output):
  cnc@linuxcnc:~/gcodes$ sudo ./pinirq.txt enp1s0
  Cores: 4
  Old CPU Mask: f
  Set device enp1s0 IRQ 122 CPU mask to 8
  
  However, it did not improve my ping / latency at all. Do I need to do anything prior to that? Isolating something?

What I have not done yet:

• editing the kernel parameters in grub customizer (quiet isolcpus= 3 pcie.aspm=0 r8168.eee_enable=0 pcie_aspm=off idle=poll).
  I dont really understand what this does, therefore I hesitated to run it. 
• .... 

Another question... almost all other threads regarding this issue link to a tutorial / troubleshooting file that was hosted by @rodw on google drive, but the link is dead. Could someone provide this file?

regards and thx.
Sebastian