Advanced Search

You don't seem to have "addf"ed the lowpass and abs to the servo thread.
(See the other components in the HAL file for examples)

Hello I have Raspberry pi 5 and byte 2 bot hat on my mill and it works very fine and now i try to convert it to my lathe with a problem with the spindle speed reading and the index and phase a for cutting thread in the lathe . I have tried to read and understand the Hal mystery with a minor of luck . In Hal Meter i there are a signal at => lowpass.0.in but reading zero at  lowpass.0.out  => abs.0.in pyvcp_options.hal . Can somone helpfull help me with this problem / krister

There is a Linuxcnc image for the RPi. There is nothing special about the image, it is just Debian Bookworm with the Linuxcnc packages installed and a realtime kernel built from the Raspberry Pi official GitHub sources with the RT-Preempt enabled, no non RPi patches are added.
I can confirm booting from SD card, USB and Nvme all work.
For touchscreen I would be more inclined to use one with a USB interface that enumerates as HID, it is far easier to setup and basically "just works". This has been confirmed with a generic touchscreen bought from AliExpress, 10.1" in this case.
For a small form factor, x86/64 is the best bang for buck, I would suggest looking into the Odroid H series, I have been using an Odroid H3 since its release and it has not let me down.
Even a 3rd gen I5 is a better solution than the RPi 4 or 5. The only advantage is the small form factor and being able to connect to a Mesa SPI board. Compared to an ex corporate PC it is quite an expensive option.
The above opinion comes from use of the RPi-400, RPi5 with an Nvme drive and use of an Lenovo ThinkCentre with an i5 I found by the side of the road that someone was throwing away.

Moved to "computer and hardware".

Note that those are all Linux questions, not LinuxCNC questions
so perhaps better asked in a general Linux forum.

Hi I trying to make a cnc control panel with touch screen and tactile switch and communicate to control box via EtherCat.and to my
unknowledgeable I thought a modern mini pc multi core ddr5 would be better to run high speed real time instruction and purchase MSI
cubi NUC 1m turn out a 8 core cpu is no good with real time kernal and worse an onboard vga is MSI SOC proprietary driver which
bookworm not support and general intel driver is not support either only for the late 6.8 kernal support it but it bring tons of latency.So I decide to shift to raspberry pi 5 and then see a uconsole for raspberry cm5 and it NVME support.
So my question are follow
Does Linuxcnc support raspberry CM5
Does Linuxcnc Support CM5 EMMC memory
Does Linuxcnc support NVME SSD
Does Linuxcnc support CM5 carrier board
Does Linuxcnc support touch screen with SPI connection
Thank in advance
Oat.   

Hi! The LinuxCNC ISO distribution includes Raspberry Pi firmware packages (raspi-firmware) that serve no purpose on AMD64 systems since they're specifically designed for Raspberry Pi hardware. However, these packages create a significant problem: they prevent the installation of other firmware packages that are actually needed for proper hardware support on x86_64 systems. The main issue is with Realtek Ethernet hardware, which requires specific firmware to function correctly. The presence of raspi-firmware packages blocks the installation of these necessary Realtek firmware packages, leaving users with non-functional network adapters.

This is essentially a packaging conflict where Pi-specific firmware interferes with the installation of legitimate x86_64 hardware drivers. The fix is straightforward but important for users who need working Ethernet connectivity (Realtek).

Temporary solution: apt purge raspi-firmware

The guidelines would be in the raspberry pi config.txt docs. As I'm sure has been mentioned previously.
You will have to read the main thread to find the location of this file as it is not in the same location as the raspberry pi images.
Honestly for your case use I would ditch the Linuxcnc image, install Linuxcnc via apt to a RaspiOS, there is information on the forum regarding this, or as I mentioned earlier build from source, you don't require an RT kernel to build from source.
The zswap fix is to actually have swap a compressed swap in memory. It is not just to "fix an error log message", which you don't seem to understand.
If you aren't going to bother to try I can't be fucked to give you help on what is really a non issue for an image created to run a CNC machine which is something you admitted you are not intending to do. And in that case you have been given suggestions to overcome what is a very minor issue.
Regarding the zswap it seems you didn't see or ignored the issue it caused for a user when the system was left idle. I'll repeat this one more time, it is not a fix for an error log message, the error log message pointed to an actual issue and the fix was to fix the actual issue.
So far I have offered some suggestions, yet you have not bothered to attempt any. Maybe this image is not suitable for your intended use and another solution maybe a better path to take.
Good luck in your endeavours but I have exhausted my patience and will to help

The zswap fix seems intended to fix a system log error message "Failed to start zramswap.service" but I checked systemctl and have no failed units, so it doesn't seem relevant to this case, is it?

Is there a guideline on how much memory to allocate to the GPU? This is a 4GB Pi 400. One idea I have is to compare the config.txt with that of other images that work well.

The other thought is regarding codecs or configuration that may be missing as suggested by the attached report from the chrome://gpu

Have you implemented the zswap fix or tried looking at the memory allocated to the GPU ?

To be quite blunt this is a low priority issue, as the primary function of the image is to run a CNC machine. Which by all accounts it has done quite well, the only show stopper was the zswap issue for one user, but this was resolved.
I may sound like an ass and appear to be unhelpful, but as I said before it's a low priority issue and so far has not, no reports, has affected the operation of a Linuxcnc session.

Good point about checking chrome://gpu, it shows a number of problems with graphics features, such as hardware decode being software only.

Graphics Feature Status
Canvas: Hardware accelerated
Direct Rendering Display Compositor: Disabled
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
OpenGL: Enabled
Rasterization: Hardware accelerated on all pages
Raw Draw: Disabled
Skia Graphite: Disabled
TreesInViz: Disabled
Video Decode: Software only. Hardware acceleration disabled
Video Encode: Software only. Hardware acceleration disabled
Vulkan: Disabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated
WebGPU: Disabled
WebNN: Disabled

 

Problems Detected
WebGPU has been disabled via blocklist or the command line.
Disabled Features: webgpu
Accelerated video encode has been disabled, either via blocklist, about:flags or the command line.
Disabled Features: video_encode
Accelerated video decode has been disabled, either via blocklist, about:flags or the command line.
Disabled Features: video_decode
Disable partial swaps on Mesa drivers (detected with GL_VERSION): 339493
Applied Workarounds: disable_post_sub_buffers_for_onscreen_surfaces
Disable KHR_blend_equation_advanced until cc shaders are updated: 661715
Applied Workarounds: disable(GL_KHR_blend_equation_advanced), disable(GL_KHR_blend_equation_advanced_coherent)
Expose WebGL's disjoint_timer_query extensions on platforms with site isolation: 808744, 870491
Applied Workarounds: enable_webgl_timer_query_extensions
Some drivers can't recover after OUT_OF_MEM and context lost: 893177
Applied Workarounds: exit_on_context_lost
Avoid waiting on a egl fence before swapping buffers and rely on implicit sync on Broadcom GPUs: 938286
Applied Workarounds: rely_on_implicit_sync_for_swap_buffers
Disable GL_MESA_framebuffer_flip_y for desktop GL: 964010
Applied Workarounds: disable(GL_MESA_framebuffer_flip_y)

Full report attached below.

I don't think the issue is hardware or resolution, since it is just this image that has these problems.

How is the monitor connected?

VGA? DisplayPort? HDMI? DVI?

Maybe try a different resolution?

Those screenshots remind me of these screenshots of Minecraft looking really strange sometimes on my Dell XPS L702X with a NVIDIA GeForce 550M GPU.

www3.langdonstaab.ca/Minecraft%20bug%20screenshots/

Why is accessing Chrome necessary?

Check chrome://gpu

Consider submitting a bug report to Chromium, maybe they'll fix this.

You can also submit a bug report for Firefox, though in my experience they don't actually fix bugs.

Ok the screenshots are interesting. Unfortunately I haven't had a chance to check as life has got in the way.
To tell the truth when I test the images I use an old 19" 4:3 monitor. Another thing to be aware of is that the images aren't meant to be for a daily driver, the sole purpose is to run Linuxcnc which is what is concentrated on. So yes there will be packages left out that are part of a standard Desktop install.
The kernel was built using the official RPi sources, with the only mod being enabling the RT section in the kernel config. So there is really nothing fancy in that area.
It very well be an issue related to resolution, in config.txt you should be able to adjust the memory allocated to the graphics system, something you'll have to look at the config.txt documentation, 2 things to be aware of, there is no raspi-config utility so the config.txt will need to be hand edited and the location of it is different to the Raspberry OS, the main thread for the images has this info.
If you just want to explore what Linuxcnc has to offer without running a machine or connecting to any hardware there is also the option of running the amd64 version as a live session on a PC or installing in a virtual machine such as VirtualBox. RT capabilities will be non existent but it will run the simulations fine.
Another option would be to install RaspiOS and build Linuxcnc from source, a real time kernel would not be required in your case and use at ad a Run In Place install. How to do this can be found in the docs.

Thanks for the replies. I finally got a chance to check out the suggestions on the RPi400. For testing I made a new fresh image on a new SD card, and the graphical glitches could be reproduced, but it may be just an issue in chromium browser, which is not installed by default. I did not reproduce the issue in Firefox, and though it is painfully slow to load pages, Youtube does play... eventually.

The SD cards used are 64GB Kingston Canvas Select Plus. Nothing fancy, but I doubt it is the issue, since I've used multiple, and other images (default RPi OS, Ubuntu 24.04) don't have the same issue.

For reference, here are some screenshots of the glitches in chromium. Btw, I had to install xfce4-screenshooter to be able to take screenshots, as it is not installed by default in the LinuxCNC rpi image.

The first screenshot shows a horizontal section of the web page with corrupted graphics. The second is chromium's setting page which never displays correctly. The third is a pdf document opened in chromium, with the controls (download, zoom, etc) at the top not showing. The fourth shows the graphical glitches in the Youtube player controls (buttons for play, pause, settings, etc).

They work in Firefox (very slow though, which is why I installed chromium) so perhaps this is not an issue specifically with LinuxCNC's image, though I can't tell. I don't have these issues with chromium on the other RPi OS images, but I have not tried debian 12 directly. I imagine that also precludes hardware issues. The monitor is a 22" Dell at 1680x1050, though I doubt that is too relevant.

Aside from isolcpu, were there other optimizations made which may impact graphical or general performance?