OctoPi 1.1.0 RC3 Status

[guysoft]

Third release candidate for OctoPi 1.1.0

There are both 32bit and 64bit images available for Raspberry Pi

There is also a new beta release for Le Potato AML-S905X-CC.
Its beta because I is not as tested as OctoPi for Raspberrypi. And I hope that having it available might let people play with it and tell me what can be done to get the wifi and cameras working correctly.

This image brings support to Raspberry Pi 5. It also drops wpa-supplicant support due to raspberrypi/bookworm-feedback#72
Please try the release candidate so we know it works.

Also a request for help in OctoPi - Our second mirror that was supplied by @wille on discord has been removed, so if anyone wants to help host a second mirror for https://unofficialpi.org/Distros/ that would help a lot so we don't loose OctoPi images.

32bit armf:
Download it at:
https://unofficialpi.org/Distros/OctoPi/nightly/2025-03-10_2024-11-19-octopi-bookworm-armhf-lite-1.1.0.zip

Md5: 00613a6a64130c4aae9d2375485e3dc2.

64bit arm64/aarch64:
Download it at:
https://unofficialpi.org/Distros/OctoPi/nightly-arm64/2025-03-10_2024-11-19-octopi-bookworm-arm64-lite-1.1.0.zip

Md5: 74cfd8e6c5b6ff9d8443aaa357201bcd.

Let Potato AML-S905X-CC (based on Debian):
https://unofficialpi.org/Distros/OctoPi/debian_lepotato/nightly/2025-03-10_debian-12-base-arm64+aml-s905x-cc-1.1.0.zip
Md5: 8a6db7245e6bced1222852072dc86458

Changes in the image

• Raspberry Pi 5 support Debian 12 Bookworm / Raspberry Pi 5 support #823
• Beta support for Le Potato AML-S905X-CC
• Images uses Debian bookworm
• Due to bookworkm /boot/config.txt has moved to /boot/firmware/config.txt See The file /boot/config.txt has moved to /boot/firmware/config.txt CustomPiOS#220
• Support changing default user name on rpi-imager
  • Move octoprint python virtualenv to /opt/custompios/oprint and add a symlink e62bada
• Dropped support for wpa supplicant due to wpa_supplicant autoconfigure removed in bookworm but not replaced with other mechanism raspberrypi/bookworm-feedback#72
  Please try the release candidate so we know it works.
• New NetworkManager headless support added, its pretty basic for now since it is expected most people configure the wifi via rpi-imager. There is a new wifi.nmconnection file in the /boot/firmware folder that lets you configure wifi headless. Its more limited at the moment than the wpa supplicant version
• Remove camera ID 046d:0825 Fixes Camera model 046d:0825 is known to not work with -f parameter, stripping it out #759

Changes from RC1:

• Fixed issue with webcam not working OctoPi 1.1.0 RC1 Status #837 (comment)
• Fixed wifi blocking guysoft/CustomPiOS@e553cad
• Network check has been fixed Adding missing if closing statement #840 (Thanks @david-forster10)

Changes from RC2:

• Updated install-desktop 430a00e
• Remove network monitoring (networkcheck) which only works on wpa-supplicant ea5d502
• switch to modern OS dependencies for latest numpy versions

[guysoft]

No complaints so far, I think we finally have a release.

[Deskwared]

It is likely that I am just missing something simple, but I cannot get this build to successfully connect via wifi or ethernet cable. I am not a programmer, so very likely just doing something wrong. I simply downloaded the 64 bit .img file and selected it when running the Pi imager, saving directing to a USB formatted FAT32. I ensured that the OS customization settings were all accurate for my network, and I can see the information properly included in the firstrun SH file as well. The ethernet lights do not even illuminate at all. Is there a step I am missing? (My Pi 4Bs all connect as expected, using the released OctoPi build and Pi imager). Please don't waste much time trying to help me, if it is not a simple answer. I was just going to try playing with the build this weekend since I had a few hours. Thank you!

[guysoft]

@Deskwared The Ethernet setting should be default if you don't enable any customization settings. I don't know how that would fail

[Deskwared]

@Deskwared The Ethernet setting should be default if you don't enable any customization settings. I don't know how that would fail

Huh…maybe it’s something strange in my router settings. Beats me. Thanks for the reply!

UPDATE: Got it working today! It simply would not boot from usb. When I tried SD card, it worked on both LAN and WiFi. However, played with the webcam, including making changes to the /boot/firmware/config.txt camera_auto_detect=1 (or 0) with no change. I was able to get a response from the rpicam-hello command, but never got a stream to work.

[foosel]

Still quite busy with OctoPrint 1.11.0rcs, thus only now gotten around to throw that against the testrig and e2e tests:

• 32bit run
• 64bit run

All green, manual smoke test on the 64bit image also looked good (plugin installation, connection to virtual printer, update to 1.11.0rc7).

Also ran the 32bit image through the UpToDate scripts, alas, that seems to have an issue, but that's something I need to look into on my end. Just in case that's interesting: The modified image currently boots, but then immediatly shuts down again. Doesn't even seem to run firstrun script, I'm suspecting the firmware/bootloader updates, but unsure at the moment. Very hard to debug given it just shuts down, no way to access dmesg and such. That's going to be fun to debug (not), will probably need to connect a serial terminal as the screen just goes black right after.

[guysoft]

@foosel do you have an image I can test? can try and find time to have a look

[foosel]

Already figured out what's causing the issue, now I just need to figure out why...

It doesn't like the kernel command line that fires off the firstrun.sh script, or at least that's my current guess. Will experiment a bit. Have it on a KVM now so I can record the boot and thus see the errors.

Built image is here: https://github.com/OctoPrint/OctoPi-UpToDate/releases/tag/1.1.0rc3-1.10.3-20250407090131

But again, don't worry about that, that's on my end.

edit: Looks like it's maybe the same issue as RPi-Distro/pi-gen#754. I've manually removed the firstrun.sh line from the cmdline.txt and that let it boot and a look into journalctl -u kernel-command-line then gave me this:

I tried just forcing an initramfs build in the kernel/bootload update script, but that didn't help, so I have to continue to search. It would probably work out fine to just change the path to /boot/firmware/firstrun.sh, but that will then cause issues with other versions...

edit 2: Not only issues with other versions, but issues with the RPi imager itself too. As I just found out, letting that customize the config of the image will cause the same issue.

edit 3: Found it. The mount point of the boot partition needs to be changed on CustoPiZer from /boot to /boot/firmware with these newer kernels. That's probably also something you want to look at on your end @guysoft, as that will produce the same issues with later base images. Will adjust CustoPiZer tomorrow, stomach is rumbling and I'm getting hangry due to that ;)

[foosel]

CustoPiZer is now fixed to be able to deal with this new situation (and I also fixed some other stuff), and the updated image now also booted and ran successfully through the E2E tests.

Related commit: OctoPrint/CustoPiZer@dd3a9af

[guysoft]

Ok, will release hopefully this week

[guysoft]

Released
https://github.com/guysoft/OctoPi/releases/tag/1.1.0