RPI4 Raspbian 64 bit & LinuxCNC

I built it again last night but th epi complained about missing firmware on boot. It seems my board.txt file is corrupt
Here are some notes I posted on the developers email thismorning.
I've had some issues here last night but I think it's a corrupt environment at my end. I will reclone and build again tonight as it was working.
Follow the steps in instructions.txt in the linuxcnc branch
do a make purge-all before you start again
You may need to run  "make ncompile" after "make ccompile"

I would also suggest you edit  userdata.txt and set
MENUCONFIG="1"
CUSTOM_DEFCONFIG="0"

This will open the kernel menuconfig and prevent the use of  the custom defconfig (which may be corrupt)
When menuconfig opens, open general settings and look for preemption model. Set it to fully preemptible kernel
If that option is not there, go back one level and further down general settings, there is a menu option with "expert" in the name.  Set that to true and the fully preemptible kernel option will be displayed.
I have found this to be a very confusing recent change at kernel.org...

This is my next plan.

Cornholio: That seems better in terms of general responsiveness.

dtoverlay=disable-wifi was already commented out in config.txt so WiFi was enabled but it ignored wpa_supplicant.conf and I had to setup the WiFi from menu-config.

It didn't auto-login as cnc but setting autologin-user=cnc in the "[Seat:*]" section of the /etc/lightdm/lightdm.conf does the trick.

There's still no raspi-config installed or available in the repos but maybe that's a generic bookworm change.

There's no dhcpcd installed so setting a static IP for the ethernet port (used for talking to my 7i76E in my use case) involves more Linux hackery than a Google search for setting a static IP on a Pi would suggest. A simple old school edit of /etc/network/interfaces sorts it.

When the screen is woken from screensaver, it asks for the cnc users password.

On the Good News front, running up linuxcnc worked and I could jog my steppers (I'm testing on my Lathe project which is currently just a pile of electronics and wires on the bench).

Is this feedback useful? I'm assuming the aim is to produce a RPi bookworm image that works for most folk.

That image gives me bad latency

How bad was it ? Compared to what ?
It's based on the same sources as was Rod uses, the only difference is I was experimenting with a 10Hz tick rate rather than a 250Hz.
I have found my self the image I use more regulary based on RPi OS or Raspbian or whatever they call it with a 5 series kernel is better.

OK for some reason the cmdline.txt is not being setup as it should. It is supposed to isolate cores 2 & 3. Config.txt is being setup as it should.

All feedback is useful as we sort this out.
Auto login is not enabled by default. I'm not sure if even th elinuxcnc installer does that.
I did think about it trying to enable it but I don't know how to edit settings in the middle of a file from a script.
We will leave i tto the user and we documented it here 
linuxcnc.org/docs/2.9/html/getting-start...sec:_bookworm_tweaks

Using menu-config is the correct way to configure wireless. Its mentioned in my repository read.me
github.com/rodw-au/rpi-img-builder-lcnc

To set a static IP address, please follow the method in the hm2_eth docs 
linuxcnc.org/docs/2.9/html/man/man9/hm2_...h%20static%20address

I have had a couple of technical issues here due to a corrupt file. I've recompiled and am rebuilding now
There is one thing I don't yet understand in the build procees which is how to skip the confusing menuconfig screen. If you have played with kernels before you will know what to do Working on it.

Comments saying you are getting bad latency is not helpful, please share a screen dump after a few minutes running It would be good to see what people are getting.
For screenshots, I have been using flameshot (sudo apt install flameshot)

Cheers guys, its great to see a few giving it a go. It is very time consuming building and testing...
​​​​​​​
 

ruffle wrote:

Cornholio: That seems better in terms of general responsiveness.

dtoverlay=disable-wifi was already commented out in config.txt so WiFi was enabled but it ignored wpa_supplicant.conf and I had to setup the WiFi from menu-config.

It didn't auto-login as cnc but setting autologin-user=cnc in the "[Seat:*]" section of the /etc/lightdm/lightdm.conf does the trick.

There's still no raspi-config installed or available in the repos but maybe that's a generic bookworm change.

There's no dhcpcd installed so setting a static IP for the ethernet port (used for talking to my 7i76E in my use case) involves more Linux hackery than a Google search for setting a static IP on a Pi would suggest. A simple old school edit of /etc/network/interfaces sorts it.

When the screen is woken from screensaver, it asks for the cnc users password.

On the Good News front, running up linuxcnc worked and I could jog my steppers (I'm testing on my Lathe project which is currently just a pile of electronics and wires on the bench).

Is this feedback useful? I'm assuming the aim is to produce a RPi bookworm image that works for most folk.
 

Thanks for the feedback.
The screen saver thing is easily fixed in power settings (I can look into changing that without having to boot the image). For your Mesa card you have to give it a manual config, as the interface can't connect to a DHCP server(there should only be the motion card and computer directly connected). I thought network manager was installed for configuring the Network (It is set to install via the build config). I'll check that for sure. The setup should disable wifi & bluetooth during the build process.
I've never been a fan of auto login for Linux.
Raspberry config is a Rasp OS thing, this is based on Debian, apart from the kernel sources which are pulled from the RPi github page (the standard kernel has patches one of which is to work with the overlays), RT patches are from kernel.org. One thing that does annoy we, which I should fix, is that sudo doesn't require a user password. You might as well be running as root.