-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OctoPi 1.0.0 RC1 Status #770
Comments
I will admit I'm still not completely sold on the version number being 1.0.0. We get enough people already confusing OctoPi and OctoPrint, I feel like this might make it worse? What about just 'OctoPi 19.0' - there's no API involved, and it's not possible to update it, so the SemVer type versioning doesn't need to apply? Just specifying that it's the release after 0.18. |
@cp2004 I had a talk about this, which I can't seem to find anywhere now. |
Great news and really want to try it - will backup my current 0.18 on an RPi-4 and restore it to a new SD card to see how it goes. Will we be able to upgrade to the full release once it's out, or will we have to install/restore it again? |
Reflash and restore, there's no way to upgrade from one version of OctoPi to another. |
Why are 32-bit and 64-bit links pointing to the same file? Talking about confusion ... :-) |
And 32bits and 64 bits are the same MD5 as well |
Yes, and all the talk about bullseye, and then Ubuntu in the name of the image ... |
I would hope so, they're pointing at the same file |
Yes, I can see that. But the text that led me here looks like false advertising then about bullseye ... :-) |
|
Congrats on 1.0! Well deserved! 🥳 |
Thanks! :-) |
I just tested the 32bit distribution with the Weedo X40 printer. As with all previous distributions, the connection will not be established due to the outdated CH340 driver. Thanks |
Tried to restore a backup and got
Restore failed! Check the above output and octoprint.log for reasons as to why. |
Same as @eblieb restoring a backup does not working correctly. I am restoring a backup made from a 32-bit installation, maybe this has something to do with it. I get the same latin-1 error, but with a different plugin. output: https://pastebin.com/zNcXtnqP |
For plugins you have to reinstall some of them because of the differences in Python versions: https://community.octoprint.org/t/pios-bullseye-killed-octoprint/38790 Basically restore the backup to the plugin error point. install the plugin manually and then restore the backup again after the reboot and rinse and repeat for each failed plugin. |
Etcher had problems verifying the 64 image on Windows 11, but I was still able to start the import of the back up and almost got through installing all the plugins including those that I had to manually install. One of the last few plugins but I thought it might be something I needed to update on the OS level. SSH connection was refused. I tried enabling it manually through the ssh file with no luck. Plugged it into a keyboard and monitor and quickly realized the raspi-config couldn't be found either after finally being able to ssh. Back to the nightly builds I go: https://github.com/guysoft/OctoPi/actions/workflows/build.yml |
Sounds like a windows issue. I used Raspberry Pi Imager tool on macOS with the 64-bit .img and SSH was setup and works just fine. |
This |
@robness The issue that was linked about dealing with an upgraded version of python is not relevant in this case, because it talks about having an existing python environment, and then upgrading it and fixing all the paths. But the case here is a brand new python environment that was built. So the path changes should not be an issue. |
@x40-Community Is there some move to get that driver in to mainline kernel or raspberrypi/linux? |
No license attached to this arbitrary driver either, so it can't be included. |
It was with Etcher. No problems using the imager tool. I need to figure out how to get that working with another PI project I am involved with. So convenient to use. |
I have never had an issue with Rufus.
…On Tue, Mar 1, 2022, 06:42 robness ***@***.***> wrote:
Etcher had problems verifying the 64 image on Windows 11, but I was still
able to start the import of the back up and almost got through installing
all the plugins including those that I had to manually install. One of the
last few plugins but I thought it might be something I needed to update on
the OS level. SSH connection was refused. I tried enabling it manually
through the ssh file with no luck. Plugged it into a keyboard and monitor
and quickly realized the raspi-config couldn't be found either after
finally being able to ssh. Back to the nightly builds I go:
https://github.com/guysoft/OctoPi/actions/workflows/build.yml
Sounds like a windows issue. I used Raspberry Pi Imager tool on macOS with
the 64-bit .img and SSH was setup and works just fine.
It was with Etcher. No problems using the imager tool. I need to figure
out how to get that working with another PI project I am involved with. So
convenient to use.
—
Reply to this email directly, view it on GitHub
<#770 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE4D4LI75XQPQT6Z2FK4DVLU5X7BPANCNFSM5POZVWTQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Arc Welder also had the UnicodeDecodeError, but when I tried to install it manually I got the following error: Installing plugin "Arc Welder" from https://github.com/FormerLurker/ArcWelderPlugin/archive/master.zip... |
Still a Latin-1 error from logs: |
@robness As I explained above it is not an issue with specific plugins it's a problem with the current version of OctoPrint and the new version of pip released a few weeks ago, already fixed but not released, and it will impact any plugin that requires downloading dependencies. |
I figured that, but for this one, even trying to manually install it, it wasn't working. It was meant more as a heads up that the plugin wouldn't even work in a manual install because of the newer version of pip. Thanks for everything that you do to support the project. |
Would it be possible to copy the It is not good policy to have files with passwords readable by everyone. |
The network settings should work in the ubuntu build. I tested them a few months ago. That is something I should fix. |
Yeah, network does work, but neither password nor hostname |
I am considering adding a setting to my fork of rpi imager, which would let us disable username changes. |
Still having camera issues where the camera freezes in the control panel |
@eblieb What camera? details please. I got both a pi camera and a webcam working here, so I need information to differentiate |
@guysoft I am getting this error a lot in DMESG
|
|
@guysoft yes the camera works it just randomly freezes in the web viewer. It works fine with OctoApp and never freezes in that. |
Doesn't seem to be able to connect to my wifi network on a pi 3. Wired works without issue, and have configured The pi was previously running a very old build of octopi from 2020 and I just swapped out the SD card. Not sure what other information I can provide but happy to provide whatever helps. |
Late to the party but it seems like input_raspicam.so is not present on 0.18 so webcamd is failing to start up/work with camera="raspi". Was that intentional and I'm jsut not finding it? |
Running on a raspi 4 with a Logitech C920 USB webcam and getting the same video stream freezing issue. Seems to be related to webcamd thinking that mjpg_streamer hasn't successfully started (it has) and so kills and restarts it over and over again. Can document here or create an issue, have been collecting logs and troubleshooting - which works better for you? |
Has anyone tested HLS streaming on these images? Only interested in 32 bit at the moment, who knows what is different with the 64 bit one since it's ubuntu not RPi OS. It's mainly to test the changes from Buster -> Bullseye. |
I have only tested this in a nightly image which is based on a different version of the underlying OS (end of Apr release, the selected nightly above is Jan). Since the I doubt I will be able to figure it out as I am relatively new to using ffmpeg. If I do, of course I will post a PR - but if anyone else knows what to do that would be wonderful to know. |
Hey, Also Looks like 64bit on rpi is officially supported: RPi-Distro/pi-gen#481 (comment) |
Personally I'd prefer to stick with Raspbian for this release, instead of switching targets now mid RC phase, and there's also this:
|
This RC1 has an ubuntu build for 64bit. It would be "switching to raspbian 64 bit". |
Currently, the Raspberry Pi cam support won't be working with the RPi OS 64 bit builds. That's one of the reasons they switched to libcamera, to get that working. As far as I know, enabling the legacy camera stack only works on the 32 bit images. Arducam actually forked mjpg-streamer & added support for libcamera to it, but last I checked there was no motion on mjpg streamer to patch it directly. jacksonliam/mjpg-streamer#336 Regular USB cameras still work the same as before, but HLS streaming doesn't work in the bullseye images on either 32/64. |
I have a Pi running 64 bit Raspbian bullseye running motioneye with the legacy camera enabled. Works. |
That's good news - I don't actually have an RPi camera so just going on what I read/would remember. My Pi cam broke so I haven't been able to test that kind of thing |
As others have noted, the Pi Cam freezes constantly in this RC. I am using the 32bit variant on a Zero 2. |
Hey, I think we are ready for an RC 2 finally. Things got stable. Will set it in motion |
You mean RC2, right? ;) |
I agree, I have been using it for a while now and the last issue I had was related to the PI Cam issues that was fixed and has been working ever since. |
I do, fixed 😅 |
Use RC2 #788 |
First release candidate for OctoPi 1.0.0
There are both 32bit and 64bit images available. Which give support to new Raspberry Pi 4B hardware pis that have been shipping out there.
The 64bit image is based on Ubuntu 20.04.4, since it seemed more stable than RaspberryPi OS when testing 64bit, it might improve later on.
Raspsberrypi 3 and up can try the 64bit version. No performance gain in normal OctoPi is expected. It might help future plugins.
Please try the release candidate so we know it works.
32bit armf:
Download it at:
https://unofficialpi.org/Distros/OctoPi/nightly/2022-02-27_2022-01-28-octopi-bullseye-armhf-lite-1.0.0.zip
Md5:
672cc74db5c863e8378d994b8ef25504
.64bit arm64/aarch64:
Download it at:
https://unofficialpi.org/Distros/OctoPi/nightly-arm64/2022-02-27_octopi-20.04.4-preinstalled-server-arm64+raspi-1.0.0.zip
Md5:
a78e25bda751e0253981020d2ddf4298
.Changes in the image
The text was updated successfully, but these errors were encountered: