/homeI am not a dense person. I have read A LOT on configuring. I have set up a couple other machines with StepConf. 
Why does this:

look absolutely nothing like this:

when trying to configure this: 

I want to install Probe_Basic. I already had Trixie installed but i couldn't get Probe_Basic to work. Than i got the hint from a community member that Probe_Basic needs Debian Bookworm as the homepage mentions.

Hi everyone,

I’ve just released version 1.1.0 of the io_decoder driver. This update focuses on architectural stability and addressing initial feedback from the community.

What's new in v1.1.0:

Asynchronous Threading: I have moved the keyboard emulation logic (uinput) out of the Real-Time HAL thread and into a dedicated user-space thread. This ensures that any system-level delay in processing keystrokes will never interfere with the real-time performance of the CNC HAL components.

Config File Optimization (Credits to COFHAL): Following COFHAL's feedback regarding parsing errors with comments and blank lines, I have refined the io_decoder-keymap.cfg structure. I've implemented a stricter formatting requirement to keep the driver lightweight and added clear instructions within the config file to prevent GUI warnings.

Full English Translation: The source code and all comments have been fully translated to English for better accessibility.

Clean Exit: Improved the cleanup routine to ensure proper thread termination and resource release upon hal_exit.

You can find the updated source code, documentation, and the new pre-packaged ZIP on GitHub and the project landing page:

GitHub Repository: github.com/bobwolfrst/io_decoder-linuxCNC Project Page & Downloads: bobwolfrst.github.io/io_decoder-linuxCNC/

A big thanks to COFHAL for the valuable feedback. I’m looking forward to hearing from more testers about how the new threading model performs on different hardware setups!

Happy milling!

Thanks a lot.
I am attaching my ldscript which I made based on existing ldscripts included in repository. And attaching my platformio.ini.

Hello,
I've been trying unsuccessfully all weekend to get the latest Debian Bookworm with the latest Linuxcnc preempt-rt up and running. Since I have little experience with Linux, I'm reaching my limits. 
I downloaded and installed Debian Bookworm 12.13. Now I wanted to follow these instructions linuxcnc.org/docs/html/getting-started/g...th_preempt_rt_kernel , point 7 (with preempt-RT kernel). Would that be correct so far? 
At point 3, Open Applications Menu > System > Synaptic Package Manager, search for linux-image, right-click on the original non-rt, and select Mark for Complete Removal, I don't know which original non-rt I have to select. I have attached a screenshot.
Otherwise, please attach Linux terminal commands so I can quickly achieve my goal.

Greetings from Germany and many thanks.

Translated with DeepL.com (free version)
 

Hello everyone, we've now integrated several pushbuttons and switches. The signals are being received and are functioning correctly. However, a new problem has arisen: as soon as I switch on the machine, the X and Y axes start moving immediately, and Linux CNC goes into error mode. I don't recall ever having this problem before. Nothing has been changed in the wiring. Perhaps someone has a crucial suggestion.

You might try increasing the interval (it's in microseconds so 1000 is just one ms)
And that may be too fast for the Omron

I will look into getting a MX2 to try to have some way of duplicating the issue.
The GS10 setup was straightforword
 

I guess you summarize all your servo drives, so 4x400W would roughly be a FN 2090-16-06?

OK 
I have given up on making it work after messing up several versions of my hals and inis
Instead i now want to make new ones by using mesaCT like i did from the beginning (the way that so far let me get the most successfull result)

I get an "OK" when trying to test the configuration
But when building the configuration i get this message from meseCT:

File "../../usr/lib/python3/dist-packages/libmesact/buildconfig.py", line 61, in build
    parent.updateini.update(parent, iniFile)
  File "../../usr/lib/python3/dist-packages/libmesact/updateini.py", line 135, in update
    self.update_key(item[0], item[1], item[2])
  File "../../usr/lib/python3/dist-packages/libmesact/updateini.py", line 765, in update_key
    start = self.sections[f'[{section}]'][0]
            ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^

KeyError
'[MESA]'

First download the deb and reinstall
to be sure you have the latest build date

Then please file an issue at
github.com/jethornton/mesact/issues

 

Hello everyone. Who has ever worked with socket raw on linux cnc? raw socket requires a set cap, does it break Linux Cnc? I wrote a test driver, on raw socket, receiving data via mmap. As a controller, I use STM32F7 (4 PWM encoders). Maybe I'm doing something wrong, I don't understand the specifics of Mesa, but the first tests show some kind of prohibitive bandwidth, the jitter is lower than on mesa.

Ill try the other release and see how it shakes out. Its killing me because I see the T470/T480 in use in that thread and this is just the newer version of that laptop. Also I figured I was safe because this one can be bought from Lenovo with Debian preinstalled.

Sorry to clarify the bios is not password locked its just extremely limited by the manufacturer. Locked down in terms of restricted to basics.

ip a: