Advanced Search

Thank you! Will try it out on friday.

Ok I’ll make a note of that.
Thanks for testing.

No image appeared on the screen, not working

Much appreciated Sir.

ok I'm trying right now

ok cool.

I've just built a new image could you give it a whirl if it doesn't work I'll say that its not recommended for the 5 with 16GB only tested with 4GB.

drive.google.com/file/d/1MEgxQ1IrdI2hnnw.../view?usp=drive_link

rpi-5-debian-bookworm-6.6.44-rt39-arm64-ext4-2024-08-12-2032.img this image worked

Ok, the 16GB board was only released at the beginning of the year, maybe you were thinking of the 8GB boards rod. So I don't think it's a Linuxcnc issue but a kernel issue.

What I would suggest you do is load up an sd card with an Raspberry Pi image, boot it up and relay the output of
I'm thinking it may require a 6.13.x or 6.12.x kernel. As the 6.6.y branch is active that keren may work but can't certain.

I think linuxcnc only works on 2-4-8gb,right?

I think the 16gb has historically not been good for linuxcnc

6.1.69 Fully preempt kernel
SPI enabled by default
Linuxcnc 2.9 built from git repo today just uspace & dev packages no docs
Mesaflash built from source today, version 3.5.10
Instead of xfce I built the image with Mate, std debian config looks different to std Mint install.





Tested mesaflash to just get the pins from my 7c81 clone tested ok
Test loading the hm2_spix driver for the rpi via a halrun session ok
Quick latency test ok

drive.google.com/file/d/1MEgxQ1IrdI2hnnw...ilQ/view?usp=sharing

hello,I can install on both raspberry pi5 4gb and 8gb but the new 16gb I bought gives an error. What is the reason for this?

Ok it was a typo I made, but if you tried to edit the file it should not of existed.

as superuser edit /boot/broadcom/config.txt & change the line from

#dtparam=i2c_arm=on
to
dtparam=i2c_arm=on

Then reboot.

I’m using a raspberry pi 5 8gb with the latest 2.93 image that’s linked on the first page of this thread. I’ve attached a screen shot of what I’m getting when run the commands. 

Wow, thank you @cornholio! That will make it much easier for us
@PCW thank you as well for the info.