Hello!
I have already asked in the Klipper Forum, and they redirected me to this Discord! Here iam. They said that this problem might be hard coded...
My problem: I have two warnings in Klipper regarding Moonraker. After sending my Moonraker log to the supporter i got the response: "interesting, the log is saying it is looking at /home/pi, but your user is not called pi usually mainsailOS like you to use pi and not your own but in moonraker.conf, try.." i tried his advice (pictures).
Sadly nothing changed. What can i do now?
If you need more Info tell me.
thanks in advance
edit: iam using a Pi4 B+, with a Genius Pro and a STM32F401 board
#Moonraker Warnings, user is not pi but *own name
150 messages Β· Page 1 of 1 (latest)
Your updater section is wrong, correct your path
type: git_repo
path: ~/crowsnest
origin: https://github.com/mainsail-crew/crowsnest.git
install_script: tools/pkglist.sh
managed_services: crowsnest``` works for any user
After you change that you also need to restart the moonraker service
I changed it, but the warnings are still there
Have you restart moonraker? And also did a force refresh of your browser
i did it yes
The problem is something else. The install_script is linking to a wrong symlink. That is a currently known bug of crowsnest in MainsailOS.
To fix it, just run
rm -rf ~/crowsnest/tools/pkglist.sh
ln -sf ~/crowsnest/tools/libs/pkglist-rpi.sh ~/crowsnest/tools/pkglist.sh
i have same issue
You don't need to write that, if you already created another post or if I already provided the solution. You could tell us that it worked but as I wrote in the message above yours, this bug is known
Restart moonraker. It's normal that you don't have any output
still there
Is it still the same warning or a different one?
Then the smylink got created at least. Send the output of ls -l ~/crowsnest/tools/libs
but because i changed in in previous approaches
a helper of the klipper discord that that my installation is calling a wrong path because i named my pi with my own name, so we changed it to "farispi4-2"
Yes that's right. Because crowsnest failed something with MainsailOS and didn't have time to fix it yet
My commands should have deleted the wrong link and created the correct one.
Send the output of ls -l ~/crowsnest/tools/libs and ls -l ~/crowsnest/tools
Also send your moonraker.conf
Send your crowsnest.log
how do i get the crowsnest.log?
It should be under machine tab, then select logs at the top and there you can find it
it is not giving me the option in the machine tap
there is only klipper and moonraker
At the top of the machine tab
There is a drop down
Click on that and select logs instead of config
That drop down
Then please run:
cd ~/crowsnest
git checkout legacy/v3
make uninstall
git checkout master
That way it will be uninstalled and the warning fixed. If you want to install it for future use just run
cd ~/crowsnest
sudo make install
You have to uninstall it once, that it will work in future and to remove the warning
Ok then just delete the section inside moonraker ^^
but is there ? ..
Only the repo
Try make uninstall again
Maybe this time it will make something
Your setup seems very scuffed somehow
Your filestructure was the legacy/outdated one, but your moonraker.conf entry was the new one
And to top it of, it isn't even installed π
Then just delete the crowsnest entry from moonraker.conf
i had problems with my genius pro
he needed to pe put in DFU-Mode and in the beginning it worked, then the printer could not connect anymore with the Pi...
okey
the update manger?
Yes
warnings gone
hahah
but somehow i think i sould worry... that crowsnest is not working with my printer/pi
You can install it and hook up a usb cam if you want to
Here the commands to install
but will the warnings return?
Nope
This is only a problem with pre-installed crowsnest of MainsailOS
You might want to udpate crowsnest before installing it, just to be sure that you are on the latest version
Run cd ~/crowsnest git pullThis will update crowsnest
Then```
cd ~/crowsnest
sudo make install
cat /etc/os-release
Seems like your added some sources that doesn't work inside your sources.list
Send output of cat /etc/apt/sources.list and ls /etc/apt/sources.list.d
Edit the /etc/apt/sources.list and comment out the last line
To edit run nano /etc/apt/sources.list
I will try it tomorrow! Thank you for everything until now
done
Then try sudo apt update again
reboot once and try again
In my region we say: "ein harter Brocken" ^^
ah π
Then send the output of cat /etc/apt/sources.list.d/raspi.list
I'm wondering what I forgot, as the source from here is already commented out
Can you copy me the lines there and paste it here? I will google with that line
I think I'm just dumb right now and missing something obvious
deb http://archive.raspberrypi.org/debian/ bullseye main
#Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://archive.raspberrypi.org/debian/ bullseye main
sorry
I meant the error ^^
Get:1 http://ftp.debian.org/debian bullseye-backports InRelease [49.0 kB]
Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:3 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Err:1 http://ftp.debian.org/debian bullseye-backports InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131
Reading package lists... Done
W: GPG error: http://ftp.debian.org/debian bullseye-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131
E: The repository 'http://ftp.debian.org/debian bullseye-backports InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
π
Try to run sudo apt-key add 0E98404D386FA1D9 && sudo apt-key add 6ED0E7B82643E131
How about doing a clean install β¦
Yeah, would be a lot faster ig
Just saying β¦
Oh I messed that command up ig
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 0E98404D386FA1D9
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 6ED0E7B82643E131
```That should work
And you are completely right with that once again π
Fresh installation is pretty fast and not that hard
A lot faster than me trying out commands through a user ^^
i had problems with the installation
Is sudo apt update working now?
Now the installation will work π
That was a "schwierige Geburt"
i will try it
HAHA yes
Β΄BUT: das letzte wort ist noch nicht gesprochen
i will try the installation
should i update crownest before installing?
If there are updates, yes
okey, ich nehme mal an ja, i will do it then
okey it is up to date
OKEY
it worked π
wow everything is finde now
thank you very much
wie kann ich dir nur danken
I've got ko-fi: https://ko-fi.com/mryel
But you don't need to donate anything. Closing this post would be already enough π
π ich werde gucken was ich da machen kann