Advanced Search

I doubt very much whether this would be an issue related to the hm2_spix driver. I would suggest you start another topic related to the qtdragon issue.

With qtdragon I have blank toolpath screen, but it only appearing when exit prompt appear.
I tried with fkms,kms -pi5 etc but without results, regular axis display working correctly.

We don't use it but I have in the past.. Debian do offer an image for the pi
raspi.debian.net//
Its very minimal (command line only), You can build it up to run linuxcnc. Its interesting to read their FAQ page for reasons why they don't include configuration packages and why they don't include a build for the Pi5

Our approach to compile the Pi kernel instead of using Debian's solves some issues but we follow their minimalisitc approach. be thankful we provide menu-config

I concur with Rod, and will also state again that the linuxcnc images are not meant to be daily drivers.
The partition managers and such are not required to run a cnc machine.
Forget about the Raspberry Pi utils, this is a Debian installation, apart from the kernel and overlays.
I’d stay away from anything KDE, there will be libraries and other stuff installed that will be basically only for that particular application. GTK apps will be far lighter weight.
The Linuxcnc images are purely for running a cnc machine, if you need want other programs you are free to install what you want but don’t hope them to be included in the supplied image.

No. The linuxcnc image uses Debian so it uses the Debian repository for all packages.
You can find what is available in APT by checking with the Debian Package Seatch.
packages.debian.org/index
If you want to run PI OS, burn another image from the official  Pi images
None of what you mention is required for a Linuxcnc installation

The image is deliberately minimal because of the limited resources of these single board computers.
 

Many of the choices I made during this bumpy configuration journey were driven by reliance on general Linux configuration information sources as I tried to figure out what problem I was actually having at any given moment.

Since I have an inventory of additional uSD & NVME cards I assumed that as my Linux understanding crept up from the near-zero mark I would be starting over at least once reevaluating those choices targeting a less 'chaotic hackers playground' configuration.

Examples of this were installing both GDebi / Synaptic package managers as well as GParted / KDE Partition managers.

I had no idea in either case which would work best or what I would like to choose in the long term, but when I'm in the early learning phase I always know that there will be outright mistakes and sub-optimal choices to say the least.

BTW, I do get your point about the RPi config tools not being necessary for those who know where to go in the Linux config hierarchy to achieve possibly better optimized results but the installation of those tools could always be rolled up in a script as I suspect their inclusion into the XFce application menu for those at their first rodeo.

Now one last actual question:

Even in the situation where someone was going to take a pass on installing the GUI config tools wouldn't it still be valid for all Raspberry builds to have updated APT sources and PGP / keyrings signatures to enable archive.raspberrypi.com (and maybe archive.raspbian.org).

Please correct me if I'm off the mark but wouldn't that be the appropriate 'deb' sources for things other than GUI config tools. Guessing out loud: firmware, eeprom (etc) and possibly purpose built Pi kernels or OS components.

Just wondering.