Mesa 7i96 Ethernet Socket Problems - LC2.9.2 on Raspberry Pi 4B

Using the official download image without any modifications.

I cannot find Network Manager on this release.

Used Terminal to launch "menu-config".
Get a dialog box with options to edit entries.
All wifi channels deactivated.
Only one one wired channel activated and edited per:
- Device: eth0 ( ::::: ) as reported by "ip a",
- IPv4 config: Auto,
- Address: 10.10.10.11/8,
- Gateway" 10.10.10.1,
- IPv6: Ignore,
- Automatically connect: [x],
- Available all users: [x].

All workshop equipment and ancillaries de-energized.
Steppers powered off.
VFD in adjacent cubicle powered on, but not operating spindle.
Operation as reported earlier with lost packets.

John.

Where the network symbol is in the top right, click on that and that opens the network manager. Can't remember whether Rod left this off to reduce image size, so it may not be there. I was assisting Rod when he was putting the image together and I was including a "little bit extra" in the images I was putting together, so that's why the old memory maybe a bit hazy.

I there any reason you have a /8 mask (16,777,216 hosts from memory this is a publcily routable network, it's be a while since my networking course) rather than a /24 mask (256 hosts which is reserved for private\home networks ) and there is no need for a gateway as there are no other devices on that network subnet. Who recommended these values ?

Forgot about this one, the RPi4 network interface is known to go "sleep", some users reported this occurring after boot.

It would be interesting to see if the ping issues happen when the Mesa card is connected to a non-RPi device.

This may not help but try downloading the latest version of rpi imager and using it to update the Pi's firmware.
Some of the older Pi 4B's require this.

There is no network symbol anywhere, and I have searched.

I will later connect the RPi to the WiFi extender via ethernet and see if I can install Network Manager.

I am quite unsure about IP addressing.
The /8 mask and gateway entry are as returned from Terminal commands, and what I gleaned searching the Forum.

I will try the workshop desktop connected to the Mesa in 6 hours time, busy during the day.

My records seem to show the LC2.9.2 image was flashed to the SD card with RPi Imager.
I tried Balena Etcher, but couldn't get it to work.
I will do another SD card with a fresh download and RPi Imager to confirm.

rodw
Are you saying the RPi4 itself needs an update ?

Cold start in workshop, 15 degrees.
Changed W5 and W6 to default 192.168.1.121.
Used menu-config to remove gateway and change address to match.

ping results:
- 123 packets 0% loss,
- 391 packets 73 % loss.

John.

With either cable connected, either way around, finger stressing the connection at the 7i96 socket interrupts packets.
The same stressing at the RPi socket is reliable.

I'm a little confused, If this is the case (clearly a hardware problem) , why are you looking for software solutions?

Forum member Kam visited with a new (old stock) 7i96, got the same packet loss problem.
Tried Windows laptop and Linux laptop, with different cables, all fail.

I note that my install shows as LC2.9.1, not LC2.9.2 as listed in download page.

Replaced LC2.9.2 (1) SD card with a new SD card fresh Imager burn of my old image of LC2.8.4, SUCCESS.
2950 packets for 0% lost.

Both the LC2.9.2(1) and LC2.8.4 were official downloads.

LC2.8.4 loads and opens AXIS.
But still grappling with the Custom Hal to get my E-Stop control working.

Basically back to where I was prior to trying to get WiFi operational.

Now, some more investigation of why my LC2.9.2(1) fails.

Stay well,
John.

Seems to be a kernel issue, to many PC's having the same issue, i though this was already fixed by using new kernels.

I was just posting that but then got distracted.
I feel that too many are ready to jump to the latest kernel without really testing.

Trying to get the LC2.8.4 set-up, I screwed up the install badly, so reverted to the LC2.9.2.
Installed the new (old stock) replacement 7i96 and the original RPi 4B 4GB.

The set-up went smoothly with the help and assistance of fellow Forum Members residing here in Sydney .

Axis opens and ping tests perform flawlessly.
Now to make chips.

I will make a desktop system with the old 7i96 and the RPi 4B 8GB to see if the original "perceived" sensitivity of physical movement of the ethernet plug exhibits itself.

But, considering how I screwed up two LC2.8.4 installs, I fear it will be a 'mea culpa' event.

This is my setup:
- download LC2.9.2 from official site,
- Raspberry Imager flashed the SD card,
- nil adjustments to the RPi 4B 4GB operation,
- Mesa jumpers 192.168.1.121.

$menu-config:
Wired connection 1
eth0 (::::
IPv4 <Manual>
192.168.1.120/24
255.255.255.0
(No custom routing)
[x] Require IPv4 addressing
IPv6 <Ignore>
[x] Auto connect
[x] Available all users

Keep well,
John.