Advanced Search

That error means there is no communication with the 7I76E
what does the command

ip a

report?

Hello, hope someone of you can help me.I have 2 machines defined on one mesa 7i76e card a mill and a plasma cutter. Both was working well until an error came up. In the most cases an reboot of hard and software fixed all the troubles I had so far. But this one seams to be different. On rebooting on both of the machines I get the same error (please see the attached file) Hopefully I have no hardware damage.Thanks for your afford in advance. BR. Tom 

That should do it (until you reboot)

you can verify with

ethtool -c enp0s25

You might retry the ping test

Did I do these steps correctly? Do I have IRQ coalescing disabled now?
 

Anyone tested the new kernels, 6.8 and up?

It seem to me its would be better to have the released ISO work with RealTek hardware
(which requires the DKMS driver) regardless of possible issue when upgrading the kernel
(which should be a rare operation)

Is it possible that you have information on when Mesa Cards will be available, I mean 7i76EU for example?

PCW wrote:

"An essential feature of DKMS is that it automatically recompiles all DKMS modules if a new kernel version is installed. This allows drivers and devices outside of the mainline kernel to continue working after a Linux kernel upgrade"

Yes, from what I have observed, the R8168-dkms driver is recompiled  as you describe. It requires the RT Linux-headers, It is quite time consuming to build. If it fails and it has a few times for me, you can end up with a system with no network. The solution is to sudo apt purge r8168-dkms. This is mentioned in the Debian package page for the driver, but its not intuitive. A couple of times, I had to boot into a different kernel (eg the non-rt one) to recover. Just in my experience it brings with it some issues so it may be better for the user to have control.

Since they are loadable kernel modules a DKMS RealTek driver
should have no effect on a system without RealTek hardware.
(since the driver would never be loaded)

"An essential feature of DKMS is that it automatically recompiles all DKMS modules if a new kernel version is installed. This allows drivers and devices outside of the mainline kernel to continue working after a Linux kernel upgrade"

Some of these things were not well known and understood when 2.91 was released

PCW post=307735 userid=481This brings up the question is why in the world is ethtool not included in the
LinuxCNC distribution (plus the RT8168 DKMS driver should be as well)

These affect all LinuxCNC Ethernet connected motion devices, not just Mesa

You can send a PR adding ethtool to here github.com/LinuxCNC/linuxcnc-live-build/...sts/desktop.list#L49

The R8168-dkms driver is a bit of a funny one. Its excluded from the default kernel. I suspect the reason is political. I suspect it includes Realtek binaries so not technically open source. But where do you stop? What about the R8125dkms driver many of the recent  micro PCs like the Odroid H3 need?

Plus I am not sure the dkms drivers are benign where no realtek hardware is installed and it then needs compiling on every kernel upgrade

I've heard that ethtools been replaced by ip but AFAIK ip
does not have low level driver control options so cannot
change IRQ coalescing for example.

Just saying that regardless of distribution used, a LinuxCNC
ISO should include it.

Just checked, not included in Mint 22.

This brings up the question is why in the world is ethtool not included in the
LinuxCNC distribution (plus the RT8168 DKMS driver should be as well)

These affect all LinuxCNC Ethernet connected motion devices, not just Mesa

Find a USB-wireless dongle and connect to internet.

ip a