#uninstallting v4 after upgrading it

1 messages · Page 1 of 1 (latest)

unborn stirrup
#

hi, i upgraded onto v4 without checking here
now i have this problem

#

i did as the crystal guided me on the upgrade from v3 on v4 page but now it dosent wanna let me do that anymore

#

ah im on debian buster how can i update this?

#

found it doing that now

#

im not getting it to work somehow

#

ah found my error

unborn stirrup
#

i have updated it but my camera still dosent work, anything i can troubleshoot?

#

the camera is connected via the raspberry camera slot with the wide connection band

brisk oar
#

Please fix your tags #readme

brisk oar
unborn stirrup
#

klipperscreen crashed and pip also didnt do anything

#

well this evolves in kind of a bigger thing hehe

#

now moonraker cant communicate with klipper

brisk oar
#

That has nothing to do with your camera. Just fyi

unborn stirrup
#

i know xD

unborn stirrup
#

yeah i close it and make a new one when i run into problems

#

im just setting up a new system so maybe it fixes itself

grim granite
#

I've run into a similar mcu connection problem when trying to upgrade from v3 to v4. A bug has been introduced in Debian Bullseye (which includes current MainsailOS), which prevents the symlinks in /dev/serial/by-id/ from being created. I solved it by getting the serial via by-path.

brisk oar
#

Not "directly" the fault of v4 ^^
v4 is updating your system packages, as they might not be up-to-date, and you really want up-to-date packages for the new backend.

brisk oar
#

After that you got your /dev/serial/by-id paths back