User name rpi-first-boot-wizard

Now it's morning time I'll have a look into this in a couple of hours.
Note to self, you're too old for late nights.

Thanks Tommy for picking up the slack in my less than ideal state of alertness.

One thing I would like the OP to confirm, is when using halcmd do you get proper comms with the board ? Just to confirm we aren't dealing with a hardware issue.

Once again I apologise for my lack of alertness.

With an older 4B you may need to upgrade the firmware for things to stick when installing the image.. I had this problem.

When y'all say the first boot wizard, do you mean `raspi-config` or `piwiz`? Neither of them are starting for me on first boot with a card imaged with the latest Debian Trixie image I downloaded earlier today. I can't imagine I'm supposed to run a machine while logged into user `rpi-first-boot-wizard`, so something is supposed to change. 

I can `useradd` with the best of them, and I even know how to add a `udev` rules file that opens up the permissions on the GPIO. What I don't know is how the image is designed to be used out of the box.

EDIT: Forgot to mention that `piwiz`isn't found when I try to run it from terminal. `raspi-config` is there and usable, though, so I can get the thing on WiFi to update packages.

There is a new image coming that has some additional fixes.

For issues in the future please post on GitHub as I'm winding back forum use.
github.com/ozzyrob/linuxcnc-rpi-2.9.7-image-issues

I explain a little better.
It's been a hard slog making these images, and like the previous issue I want to keep all the fixes, issues, tips in one place.
So rather then the forum where it's going to be many different threads I'm want a single point of support.
I did try with the previous, one big thread, and an index to that thread but I still kept having to refer people to the index for the same questions.

The making of these images involved learning the RPi guys build them, working out what can and can't be taken out, some stuff is burried in meta packages, so for instance like piwiz it's burried in a meta package, so it is a little trial and error.
I'll take the blame, as when writing the image I was only setting everything via RPi Imager, which people had tried on the 2.9.3 images. So I thought well let's do that, and have it mentioned in the download section, and in the announcement thread. So that kind of didn't work.
It would have been easier if someone offered to help test in the early days but no one put their hand up. Whilst I knew how to get the image going as recommended, I wasn't aware of what happens when you don't follow the recommended way.
In saying that I have realised a few things. The main being to take a little longer to push them out, and to be clearer when explaining.
So guys if you can work with me on this, especially with reporting issues via GitHub, as I get emails when issues are raised, that would be great.
Thanks
Rob

Can confirm: Rob fixed two issues that I had with the images before I even reported them. Don't be like me, folks, check to make sure the issue is still an issue in the latest image BEFORE you report it.