linuxcnc-2.8.0-pi4.img - no USB on raspberry pi 4 - 8GB & 2GB

Exactly that image works here. But as I said, I did not put it on the SD-card but a USB thumbdrive plugged into the USB3 port. When I remove the 3GB limit, it does not boot (USB is unavailable), but otherwise it just works.

Oh, and it does not boot on the RPI3+

... but there is something fishy with the kernel. I see these in the logfile - and I can imagine that you cannot boot reliably from mmc:

[ 77.284159] mmc0: Timeout waiting for hardware cmd interrupt.
[ 77.289904] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 77.296338] mmc0: sdhci: Sys addr: 0x00000000 | Version: 0x00001002
[ 77.302771] mmc0: sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000000
[ 77.309204] mmc0: sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[ 77.315637] mmc0: sdhci: Present: 0x1fff0001 | Host ctl: 0x00000001
[ 77.322070] mmc0: sdhci: Power: 0x0000000f | Blk gap: 0x00000080
[ 77.328502] mmc0: sdhci: Wake-up: 0x00000000 | Clock: 0x0000f447
[ 77.334935] mmc0: sdhci: Timeout: 0x00000000 | Int stat: 0x00000000
[ 77.341367] mmc0: sdhci: Int enab: 0x00ff1003 | Sig enab: 0x00ff1003
[ 77.347800] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[ 77.354232] mmc0: sdhci: Caps: 0x45ee6432 | Caps_1: 0x0000a525
[ 77.360664] mmc0: sdhci: Cmd: 0x00000502 | Max curr: 0x00080008
[ 77.367096] mmc0: sdhci: Resp[0]: 0x00000000 | Resp[1]: 0x00000000
[ 77.373529] mmc0: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000
[ 77.379961] mmc0: sdhci: Host ctl2: 0x00000000
[ 77.384396] mmc0: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000
[ 77.390828] mmc0: sdhci: ============================================

Followup: I compiled a kernel without MMC, but that does not only disable MMC, it also disables USB, so no win there.

First, following the peremptory shout from Linuxcnc: /quote: 'This SD image is reported not to work with the Raspberry Pi4 8GB model. Note also that this version of the SD image limits available memory to 3GB as this is necessary to persuade it to run with both WiFi and USB working on some versions of the Pi. You can experiment with removing this limit by editing the config-rt.txt file in the boot directory.'
Thus I've corrected a config-rt.txt extending 3,072 up to the 8,192 which is translation for 8 Gigs, I've noticed /boot/config.txt has a reference on it so far.
Being an outright noob in Pis (native OS X user since 1999) so I made a clean copy of Rasp OS with Rasp Pi Imager firsthand, which later has happened to be much of avail.
After I found when booting up from solely SD image with my exact memory in the above mentioned file USB appears completely irresponsive. Once I've rolled back all changes to the 3,072 I have achieved a booting of freshly installed Pi OS with a LinuxCNC precompiled and present in the Pi menu.

For in my case it was imperatively necessary. Yes, one more thingy please do not pay any heed to any actual software start failure, for me it had started working with 'legacy lathe' preconfig from the 3rd time, yet it does comparably stable and it generates report files storing it at /tmp in your /pi home dir. Yes and no browser will be at start as reported, never tried to fix it yet, though. Please check out how its working in the overall:

To manipulate vector graphics in the prog please make sure to have a 3 buttons mouse at a hand, a stock Rasp Pi wheeled one just does the whole trick very well for me.

Hello,
I have install Linuxcnc-2.8.1-pi4.img on my pi4 4 Go.

I have one issue:
Debug file information:
Note: Using POSIX realtime
HAL_PI_GPIO: ERROR: board revision 6 not supported
hal_pi_gpio: rtapi_app_main: Invalid argument (-22)
./aselec-jeulin_microtour.hal:21: waitpid failed /usr/bin/rtapi_app hal_pi_gpio
./aselec-jeulin_microtour.hal:21: /usr/bin/rtapi_app exited without becoming ready
./aselec-jeulin_microtour.hal:21: insmod for hal_pi_gpio failed, returned -1
1791
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

The issue come from HAL_PI_GPIO where my rpi 4 board was not support.
But the issue come from more deeper, in cpuinfo.c my rpi4 revision C03114 was present in file from 15 january and I suppose that this img file Linuxcnc-2.8.1-pi4.img was created before this modification.

I think make a new img file with actual source can solve the issu, but I haven't the knowledge to built this new version.

Do you know who can help me to built a new version please?

BR

You could probably just update instead of build a whole new one ? Or does he have to rebuild to apply the changes to the driver section?

Might be less help than intended, but I usually do it this way, using this as a guide
forum.linuxcnc.org/32-documents/34495-in...al-version-git-clone

full disclosure i dont know how to use the terminal file thing or how to do a global install. i also have to do it twice, because the first time doesnt work. the image looks like it was made after the update but I dont know how these things work. I was just curious about the revision numbers.

Also , the compute modules use a different revision code it seems . a/b/c/d03140

Just in case the normal debian user is here
and sees the rpi imager is for ubuntu...
the github source
github.com/raspberrypi/rpi-imager
has details how to build raspberry pi imager for debian
also for Fedora/RHEL/CentOS Linux
hth
tomp

I get erors building on debian 9 after deps installed

tomp ( who will try with dd )