"error finishing read" with Mesa 7i92T on fresh install

  • rodw
  • rodw's Avatar
  • Away
  • Platinum Member
  • Platinum Member
More
23 Feb 2025 07:44 #322343 by rodw
Great!
Debian 13 (Trixie) is only a few months away from release (its in alpha release now) and it uses the 6.12 kernel
I did save my 6.3 build steps here.
docs.google.com/document/d/1-vj8OuACyzkk...aWE/edit?usp=sharing
You can modify them to do another kernel

Just keep the kernel version the same as the RT patch which is why we do a git clone.
The following user(s) said Thank You: Vector

Please Log in or Create an account to join the conversation.

More
23 Feb 2025 08:05 #322345 by Vector
Fabulous!

Yeah, I think if your 6.3 is working, I'll just wait and see.

Cheers!

Please Log in or Create an account to join the conversation.

More
14 Nov 2025 10:43 - 14 Nov 2025 10:59 #338351 by Jensner
Hi,

I also did a fresh installation on a DELL Optiplex 3060 Micro PC (RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller)
Everything incl. IRQ-Optimizing (Latency) works fine, but i also run into this error "Error finishing read" with my MESA 7i96s.
--- 10.10.10.10 ping statistics --- 46085 packets transmitted, 46085 received, 0% packet loss, time 46101ms rtt min/avg/max/mdev = 0.050/0.062/[color=#e74c3c]3.014[/color]/0.039 ms


In my old installation (at this PC) i run the 3.6.0 rt11 Kernel and did not have this problems, so i think, last time i updated it for the same reason. Sadly i don`t know how to do this update again.
Is there an easy way only updating the kernel?
(Sorry but I`m not in the Linux-Space, so its a little hard for me)

Thanks a lot
Jens
Last edit: 14 Nov 2025 10:59 by Jensner.

Please Log in or Create an account to join the conversation.

More
14 Nov 2025 10:53 #338353 by Jensner
Here is a screenshot from the Latency Test of the old configuration. Only for the Kernel-Infos.
The latency was horrible at this time (without irq-optimisation at this time)
   
Attachments:

Please Log in or Create an account to join the conversation.

More
14 Nov 2025 12:09 #338354 by Jensner
I Installed the 
r8168-dkms Package and till now the error hasn`t appeared again...
WIll have a look at it.

Best regards
Jens

Please Log in or Create an account to join the conversation.

More
14 Nov 2025 17:03 #338365 by Jensner
OK, after 2 hours of testing, the error appeares again...
Someone who can help me..

Best regards
Jens

Please Log in or Create an account to join the conversation.

  • tommylight
  • tommylight's Avatar
  • Away
  • Moderator
  • Moderator
More
14 Nov 2025 17:15 #338367 by tommylight
If you do not need the latest features, you would probably be much better off by using the 2.8.4 ISO of LinuxCNC, and it is very easy to test if that works for you if you already have a working config:
-download 2.8.4 ISO from the downloads page
-burn to a USB
-boot the PC from said USB - do NOT install
-use file explorer to find the config on the internal drive
-make a copy of the configs folder to be safe
-open the copy of the config folder
-find the file that ends up in .ini
-right click on it, select open with
-near the bottom click on "use custom command" or similar
-type linuxcnc
-enter
That should run the machine as usual so you can check if it drops the link or errors out.
If that is successful you can install on internal hard drive.

Please Log in or Create an account to join the conversation.

More
14 Nov 2025 17:36 #338369 by Jensner
Hey Tommy,

many thanks for your support.
At the moment i would like trying to solve it at this configuration.
The last 3 days i installed everything new (serveral times). with Probe basic, IRQ-Optimization, automatic tool probe.
At the moment everything works very well, only thisone problem.

Is there no way just use another driver or kernel?

Here some infos from ethtool.
Maybe there ist something, that could fix the problem.
cnc@CNCRechner:~$ sudo ethtool enp1s0
Settings for enp1s0:
    Supported ports: [ TP ]
    Supported link modes:   10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
    Supported pause frame use: Symmetric Receive-only
    Supports auto-negotiation: Yes
    Supported FEC modes: Not reported
    Advertised link modes:  Not reported
    Advertised pause frame use: No
    Advertised auto-negotiation: No
    Advertised FEC modes: Not reported
    Speed: 100Mb/s
    Duplex: Full
    Auto-negotiation: off
    Port: Twisted Pair
    PHYAD: 0
    Transceiver: internal
    MDI-X: Unknown
    Supports Wake-on: pumbg
    Wake-on: g
        Current message level: 0x00000033 (51)
                               drv probe ifdown ifup
    Link detected: yes
 
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

More
14 Nov 2025 18:07 #338371 by Jensner
I did a nother check in my BIOS and maybe i did annother improvement.
The ping performance looks mutch better then before.
--- 10.10.10.10 ping statistics ---
120393 packets transmitted, 120393 received, 0% packet loss, time 120405ms
rtt min/avg/max/mdev = 0.049/0.106/0.306/0.031 ms

Maybe this could solve the problem.
Fingers crossed...
Jens

 

Please Log in or Create an account to join the conversation.

  • tommylight
  • tommylight's Avatar
  • Away
  • Moderator
  • Moderator
More
14 Nov 2025 20:22 #338382 by tommylight
Yes, that looks much better.

Please Log in or Create an account to join the conversation.

Moderators: PCWjmelson
Time to create page: 0.117 seconds
Powered by Kunena Forum