Advanced Search

After about a year, I am back to trying to get this to work. I have updated to Bookworm.
I enable spi in config.
I have been able to talk to the 7c81/7i76 with mesaflash.
I edited my 7i76e hal file replacing 7i76e with 7c81.
When I tried to start linuxcnc I got an error associated with this line:
loadrt hm2_eth board_ip="10.10.10.10" config="num_encoders=0 num_pwmgens=0 num_stepgens=3 sserial_port_0=0xxxxx"
I assume I need to replace hm2_eth with hm2_rspi and take out the board_ip="10.10.10.10"
Anything else I need to do?
Thanks in advance,
Alan

Thank you for you kind reply and offer, no worries , the error is on my side not being up to date, you are all busy enough.

I had a 7i76e.pncconf file which I was able to open with pncconf and my settings were there at least seems ok for the default machine.

I was using a xbox controller, a two button crane control with emergency stop and the laser was with a M7 command- button set to the mist hal output.

I will read the documentation and hopefully get all working with the qtplasmac machine setup again.
I assume the additional config is the same, custom hal etc.

thank you
Roman

 

The lack of yellow (100BT) LED illuminated the RJ45
suggests a problem with the 7I76E Ethernet interface
or the host Ethernet interface.

I would try a known working  Ethernet connection, and if you
do not get both Green (activity) and Yellow (100BT) LEDs
illuminated on the 7I76E RJ45 connection, I would return the
7I76E  for warranty repair. Note that especially for plasma systems
it's important to ground the frame ground connection on the 7I76E.

Can you check if get any LEDs illuminated on the 7I76E RJ45 connector
with the Ethernet cable unplugged?
 

Could be cabling problem but the "ip a" report shows
the link as up,  could also a be a host PC issue, or be a
7I76E issue.

What do the LEDs on the 7I76E RJ45 connector show?

 

You would need to

ping 10.10.10.10

To check connectivity to the 7I76E
 

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"