For me it’s lack of information that’s the most frustrating.
I’ve been watching these forums for a while and Visible activity by Libre Computer was way down in 2024 compared to previous years. There were fewer software releases and official posts on this forum were much less frequent.
I’ve noticed that most posts by customers looking for help this past year go unanswered for weeks or months if they get answered at all. It makes me wonder what’s happening at Libre.
Raspberry Pi keeps changing their imaging tool behavior in an inconsistent manner. We’re tired of their half-baked flashing tool. Use dd or any other tool. We will no longer support crap software.
Use Debian with Gnome. The remote desktop support is based on XDP and works great and fast.
This forum is maintained on a best effort basis. Commercial support is not free especially for issues that were already answered repeatedly and can be searched for.
Reality is last update of images was well over a year ago - “We will no longer support crap software” - Unfortunately given the circumstances of lack of support generally - I’m not sure anyone will be too concerned by this !
Debian 12 was released 1.5 years ago. We will update the images with Debian 13. Raspbian 12 was released 1.5 years ago as well since it’s based on Debian. When Raspbian 13 comes out, we will release that.
October 2024 ??
The new images are expected to land on the second week of October due to a lot of updates throughout the stack.
On a positive note - at least we have a response now - Thx !
I couldn’t get the ssh/userconf.txt headless setup to work with Bookworm to save my life. I tried with Bullseye and it worked right away. Both freshly downloaded images yesterday from your site. Flashed with Balena Etcher. I copied the same ssh & userconf.txt in both cases. With Bookworm, ssh never even started (port 22 connection refused). With Bullseye, everything worked right away as expected.
Had the same issue. Here’s how I got it to work -
Burned image 2023-10-10-raspbian-bookworm-arm64+aml-s905x-cc.img.xz
with the Raspberry Pi imager version 1.9.4 (imager_1.9.4.exe)
Within the imager, I selected the option the create a user and password, and checked the box to enable ssh (don’t know if that mattered or not but that’s what I did).
By itself, that did not work (connection refused on port 22). I saw it pulled an IP address from the DHCP server but no sshd.
So I plugged the microSD card back into my Windows machine and created an empty file “ssh” (no quotes and no extension) on the root of the microSD card. Put it back in the Le Potato and booted. This time it did answer on port 22 and I was able to log in with the account I created using the Raspberry Pi imager.
I did not use the userconf.txt file at all.
Hope this helps…