the image uses the legacy rotating in cmdline.txt. you can try the “newer” options: for example https://www.raspberrypi.com/documentation/accessories/display.html#rotate-screen-without-a-desktop
but would not recommend it
@Rex could you shed some light into image packaging? On the Arch side it’s pretty old style, requiring users to know how to format the card, and unpack the rootfs tarball.
I would imagine that we ultimately get something like a .img distribution, that one can use standard tools like etcher for deployment, last mile driven home.
I was trying to do that the other day, but I didn’t find a 100% stable system yet. Having 0 knowledge on RPi things and such, what I had in mind was to create a stable system with the minimal config, and create an img of it, so when people flash it it “first boots” then. Isn’t the concept like this?
@yatli you don’t have to do any special unpacking or flashing. the only thing that doesn’t work is using custom setting with the raspberry pi imager. ive flashed with dd and rpi imager.
@estufa thats what im going for in this image. I want it to work with both colckworkpi devices, it still has the first boot wizard
1 Like
Yeah, kind of got the “idea” from you to be honest. Your img works flawless too. I do use KDE as usual, and it just works amazingly.
1 Like
So how messy would it be to build the 64 bit image that would run on the CM3 module. I have a DevTerm with CM3, but do need the 64 bit OS. Keeping the power consumption low is more important than speed for me.
This image should boot up on the cm3 too. just change the config.txt to the display panel that corresponds to the device you have after you flash your sd but before you boot.
I don’t have a cm3 to test but it should. Try it out and let us know if it works.
I have a CM3+, so I will enjoy using this 64 bit image with it. Do you think the image will work with ClockworkPi’s A04 also? I have A04 as well.
I have a a04 too, it wont work with this image. The development on the a04 is really lacking. I’ve offer mine up for free to someone that’s been working on the kernel. so hopefully the a04 people can get more support. i just use the cm4 in everything.
2 Likes
yeah i got the cm3 primarily for software support reasons. a04 is more powerful, but i had something that didn’t want to run on its gpu.
@Rex thanks for this, I have been able to do a list of things that were crippled by the official image kernel being outdated. Issues I have are the keyboard backlight not functioning (as stated previously in this thread) and gamepad is not operating on retroarch. does anyone know what I need to modify for the gamepad to be detected in retroarch? it worked natively in the uconsole official image.
Just an update, it appears the keyboard backlight is working, I was just in too bright of an area to notice.
Thank you Rex! Can it run on an A-06 Uconsole?
the gamepad should work ootb when the keyboard is working.
No, This image only works on RPi Boards. The Image only works on CM3, CM3+, CM4, and CM4s in the DevTerm or uConsole.
1 Like
looking to try retropie setup. Would be installed as regular app without autologin(as regular retropie image does)?
You should be able to install it normally, just as you would on a stock raspberry pi installation.
Well, I was able to test a little and it works well! On the other hand, I can’t block the kernel update. I am still a novice in the world of Linux.
Are you using the image with the date 20240419 at the end of the file name?
The newest image has the kernel already held and some other improvements.
Info is in the Original Post.
1 Like
i tested the system intensively in the last few days and have to report, that there is something not working as intended.
the hardware had random crashes, storage made problems, the video engine crashed a lot etc. didnt have any problems with the PMOS kernel with the same configuration on the same hardware, so i assume it is software based.
Need to investigate why this happens.