#uninstallting v4 after upgrading it
1 messages · Page 1 of 1 (latest)
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
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
Please fix your tags #readme
For raspicams please have a look at: https://crowsnest.mainsail.xyz/faq/how-to-setup-a-raspicam#troubleshooting
Would be awesome if you could post what you made wrong, that maybe our people can find it later
something broke with the debian update i made a new sd card with mainsail os and update everything along the way maybe thats fixing some of my problems
klipperscreen crashed and pip also didnt do anything
well this evolves in kind of a bigger thing hehe
now moonraker cant communicate with klipper
That has nothing to do with your camera. Just fyi
i know xD
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
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.
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.
To fix that bug, run: curl -sSL https://raw.githubusercontent.com/mainsail-crew/MainsailOS/develop/patches/udev-fix.sh | bash
For more information: https://github.com/mainsail-crew/MainsailOS/blob/develop/patches/Readme.md#udev-fixsh
After that you got your /dev/serial/by-id paths back