Advanced Search

None of those are “bleeding edge” if you look at the progression of the mainline kernel, which is well past the 6.1 series.
Quite honestly, after going through the process, as it stands the most usable route for the RPi 5 is a Raspberry OS image with a real time kernel of the appropriate version and Linuxcnc either installed via self built packages, which doesn’t take that long. The other secret is to change from Wayland to X as the compatibility layer is not optimum for UIs that have calls to X libs. This is a must if a user has a preference for a xfce desktop.
Another thing to keep in mind is eventually sysfs will be dropped from RPi kernels as it a depreciated feature. This will mean some changes to user land access to GPIO, not that it will affect Linuxcnc, but it would be something worth tracking. This info comes from the RPi forum, mainly from when questions arise from access regarding The RPi 5, which seems to be a little messy and unclear to a great many users. Libgiod seems to be the recommended way. Whilst it’s neither here nor there, some of these developments would be worth tracking.

On another note, keep safe and I hope that the fire nor floods affect you mate, seems like the last thing you need on your plate.

Cornholio, I have just followed the commits on the raspberry pi kernel git
github.com/raspberrypi/linux/commits/rpi-6.1.y
It is desirable to match the mainline kernel with the preempt-rt kernel
6.1.67 was committed on 11 Dec but it has not been merged into 6.1.y
The next merge ocurred after committing 6.1.68 so there is not a clean match with the 6.1.67 RT patch.
Previoulsy there was 1 for 1 mapping with the kernel versions. The sudden flurry I assume is due to the Pi 5.
The production 6.1.63 kernel would need to use the 6.1.47 patch so quite a gap.

Probably the best commit to clone from would be e41b05a8fc73f95425aceaf15a68fc25da1d1fe5 where 6.1.68 was merged in as that should include the 6.1.67 changes and only be one version away from preempt_rt

When you use kernel source from kernel.org there are ways to match the versions eactly.

Re:one panel at the top.. not entirely sure what you mean but I think you are right

Yeah it was a toss up between the pineberry and the one I got. I chose mine because it was cheaper and had a cool design on the back haha, plus the company is a bit older.

rodw wrote:

cornholio wrote:

If it's Rod's image can you change the resolution and does it identify the display\monitor? From what I've seen it's stuck at a single resolution and it can't identify the dsiaplay as the RPi4 images can.
Yes, my image uses debian so it won't have the pi specific menu options.. Some settings can be changed using  sudo menuconfig.
But if you could try adding
video=HDMI-A-1:1920x1080M@60D 
to cmdline.txt or equivalent, It would be helpful. If it works, I can add it to the installer.

Its still a pain because the Pi 5 needs to be at the bleeding edge of the raspberry kernel and the PREEMPT_RT is lagging behind that.

 


Latest RPi production kerenl (2023-12-05) is Linux kernel 6.1.63 for the most recent Raspberry OS Image,latest 6.1 series RT is 6.1.67, so it would not seem that the RPi 5 does not need a "bleeding edge" kernel, it's just there is a mismatch between latest RPi production kernel and the latest rt-preempt. If anything the preferred RPi kernel is behind the rt-preempt patch.
www.raspberrypi.com/software/operating-s...spberry-pi-os-64-bit

In actual fact the latest 64 bit image is the same for all models. After running a self (same recipe) made image for the RPi5 and using the official image and installing a RT kernel & linuxcnc, the official image appears to be a more "smoother & integrated" experience for the 5, tho I did change from Wayland to X so I could run a xfce desktop. The pre made images for the 4 are fine.

Although in saying that Rod if you have sources of info to the contrary I'd be quite happy to see it and amend my answer.

I've gone for the Pineberry one
pineberrypi.com/products/hatdrive-bottom...0-2242-2280-for-rpi5

Yeap. I have one of these on the way

shop.pimoroni.com/products/nvme-base?variant=41219587178579

Edit. I find this the most awkward forum when replying to people.

flyingbrick wrote:

Hi mate.

Yes, this seems to function fine, resolution changes when settings modified as per this image attached.

I am using image Lcnc210_pi5 within image_pi5_rt.zip shared earlier by elovalvo

 

Ok looks like that might be based on a official Raspberry Pi image. Is there just one panel at the top ?

cornholio wrote:

If it's Rod's image can you change the resolution and does it identify the display\monitor? From what I've seen it's stuck at a single resolution and it can't identify the dsiaplay as the RPi4 images can.

Yes, my image uses debian so it won't have the pi specific menu options.. Some settings can be changed using  sudo menuconfig.
But if you could try adding
video=HDMI-A-1:1920x1080M@60D 
to cmdline.txt or equivalent, It would be helpful. If it works, I can add it to the installer.

Its still a pain because the Pi 5 needs to be at the bleeding edge of the raspberry kernel and the PREEMPT_RT is lagging behind that.

 

If you need me to install rods image to check the same thing, this is no problem.

Hi mate.

Yes, this seems to function fine, resolution changes when settings modified as per this image attached.

I am using image Lcnc210_pi5 within image_pi5_rt.zip shared earlier by elovalvo
 

rodw wrote:

From the screen dump, you have nothing to upgrade so its not an issue.
That raspberry pi bug seems to have returned to Debian core code. Its not a Linuxcnc thing
SO the error is in relation to the  rasppi firmware it thinks is installed.

try sudo apt remove z50-raspi-firmware or
sudo apt remove raspi-firmware if it errors

Hi MR.Rodw
I same problem and try to your solution , but can't solve.
have any solution ?
Thank you

Asis.

asis@192:~/Downloads$ sudo apt remove z50-raspi-firmware
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package z50-raspi-firmware
asis@192:~/Downloads$ sudo apt remove raspi-firmware
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'raspi-firmware' is not installed, so not removed
The following packages were automatically installed and are no longer required:
  linux-headers-6.1.0-11-amd64 linux-headers-6.1.0-11-common linux-headers-6.1.0-11-common-rt linux-headers-6.1.0-11-rt-amd64
  linux-headers-6.1.0-13-amd64 linux-headers-6.1.0-13-common linux-image-6.1.0-11-rt-amd64
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up initramfs-tools (0.142) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-6.1.0-13-rt-amd64 (6.1.55-1) ...
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-13-rt-amd64.
dkms: autoinstall for kernel: 6.1.0-13-rt-amd64.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-13-rt-amd64
live-boot: core filesystems dm-verity devices utils udev blockdev dns.
raspi-firmware: missing /boot/firmware, did you forget to mount it?
run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-6.1.0-13-rt-amd64 (--configure):
 installed linux-image-6.1.0-13-rt-amd64 package post-installation script subprocess returned error exit status 1
Setting up linux-image-6.1.0-16-rt-amd64 (6.1.67-1) ...
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-16-rt-amd64.
dkms: autoinstall for kernel: 6.1.0-16-rt-amd64.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-16-rt-amd64
live-boot: core filesystems dm-verity devices utils udev blockdev dns.
raspi-firmware: missing /boot/firmware, did you forget to mount it?
run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-6.1.0-16-rt-amd64 (--configure):
 installed linux-image-6.1.0-16-rt-amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-rt-amd64:
 linux-image-rt-amd64 depends on linux-image-6.1.0-16-rt-amd64 (= 6.1.67-1); however:
  Package linux-image-6.1.0-16-rt-amd64 is not configured yet.

dpkg: error processing package linux-image-rt-amd64 (--configure):
 dependency problems - leaving unconfigured
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-16-rt-amd64
live-boot: core filesystems dm-verity devices utils udev blockdev dns.
raspi-firmware: missing /boot/firmware, did you forget to mount it?
run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 linux-image-6.1.0-13-rt-amd64
 linux-image-6.1.0-16-rt-amd64
 linux-image-rt-amd64
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
asis@192:~/Downloads$ 
 

seuchato wrote:

phillc54 wrote:

.... wrote:

I have only tried this 64bit version on a sim so far.
...
 

Phil
here you wrote "you tried this ... on a sim". I am trying to get *any* pi3/4/5 running on a sim - yet in vain. Could you shed some lights on hoe you got there, please?
My test environment

• OpenSuse 15.5 host (can change to what is promising, I am not stubbern, well my late wife used to say I was
  • 128 GB Ram
    • AMD 7900 or intel i9 13900
      • free disk space > 20T
        
        
        Aims:
        • Test environment for pi3/4/5 to improve the script here
          
          Any help greatly appreciated
          Greez
          chris

With the RPi once an image is created that gets good latency it will work on any Pi of the same model.
EG A RPi4 image with known good latency user xxx creates will be the same for user yyy & aaa. The only factors that can make a difference is whether wifi\bt & sound are on or any personal changes to config.txt, but the Linuxcnc RPi4 image is usable out of the box. Unlike PC's there is no variance ( apart from which model) tho I don't know if firmware will makes any difference, but generally older firmware don't seem to boot the latest image. Good cooling is a must.
RP-400 (1.8GHz) have a faster Processor than a RPi4 (1.5GHz), although they are the same platform, just different form factor and the keyboard controller is built into the RP-400.
RPi5 is a different beast due to the RP1 I\O chip (read the Raspberry Pi's version of a southbridge).

If it's Rod's image can you change the resolution and does it identify the display\monitor? From what I've seen it's stuck at a single resolution and it can't identify the dsiaplay as the RPi4 images can.

Hi Rod.

I used the iso a few pages back together with the raspberry pi image installer. I have never done any of this before so was surprised that it all just seemed to work without any issues.

From what I can see, resolution etc is working as it should, but please let me know if there is anything specifically that I can check for you.

My opinion is of limited value as I have not tried to drive a machine with the pi yet (card is stuck in customs) but over all it seems like a fantastic solution.

I understand that latency etc should not be a primary concern when using a mesa card HOWEVER I can tell you after trying four computers (with all the usual tricks) and getting poor usability and poor latency, this pi appearing to just simply work is 10/10.

Again, let me know if there is anything you would like me to check.