So I took the plunge and build a whole new raspberry pi OS (32bit) and flashed my Octopus V1.1 for my new system.
It seems ok so far and as nothing is yet connected to the MCU, the temperature out of range cause a shutdown. This is not a problem. The problem is that I can remember starting my previous OS, and used a monitor, it would start up and finish on the klipper menu screen, with or without any messages. From this screen you could choose from the menus such as restart and shut down. But with this new OS it stops on a login prompt, see attached photo.
Is this an issue I caused during the OS setup? or will this go away once the MCU has things hanging off it so it simply continues???
I am worrying now that if I do more work now it will all be in vain at the end because I have done something wrong during the installation of the OS.
Please somebody say something comforting and be gentle, its my first build I do myself.
At least I do not see any “dirty” in the klippy log anymore
Hi Mykepredko,
I used pi imager, like you showed, and selected those things to what I wanted. This is also the password I use to ssh into the pi via my terminal, and it works.
I selected a 32 bit version from github and selected in pi imager to chose my own file via the browser, that also worked and I had no errors or warnings.
The only thing I left out is the wifi because I will run the printer on a cable.
I have klipper and mainsail on the pi. I have not tried a keyboard on the pi yet, I just read it should work with any wired keyboard (is this true?).
So I have not yet logged in on the pi screen itself but I have logged in via ssh on linux, that works using the credentials I set up during the installation with pi imager.
My question is I never saw this login prompt on my previous (2) versions of klipper, it always simply proceeded to the klipper menu screen. Even though both had passwords which I used to ssh into them.
My worry is that I have done something different that I should not have done. This is my first time I do it myself, the 2 previous ones were done by others.
If you want to have the Mainsail/Fluidd display coming from the Raspberry Pi rather than through the SSH device then you’ll have to install KlipperScreen with the HDMI set up as described here:
Note, you’ll also have to have a mouse attached to the rPi.
Probably your KlipperScreen is crashing upon start.
Generally speaking:
Working “headless”, i.e. via SSH is perfectly fine and the usual way to administrate such devices (if SSH is working, no need for mouse or keyboard)
You can use the command systemctl status KlipperScreen (from SSH) to see what the service is doing or complaining about
and also @mykepredko
My apologies, I have used the word klipperscreen completely in the wrong context. I did not mean klipperscreen at all and I have caused mayhem by doing so.
I have looked it up and now realise what is in fact klipperscreen, and I will not use this.
What I meant was the following:
My pi has a piggy back screen, the BTT 50 tft. This screen shows the startup of the OS of the pi as you power it up. On my previous two klippers this ended up showing a large klipper logo and the menu choices in the bottom. One of them is the shut down, another is the restart firmware. The others I don’t remember.
This screen I erroneously called klipperscreen, again my apologies.
The thing is that my latest build I did myself does not show this klipper logo at all, it stops at a prompt for the password.
Since my previous 2 klippers did not do this, I now worry I have done something different from what I should have done?
I always planned to use klipper via mainsail on my laptop with a browser. I will not use klipperscreen. I know already that mainsail works, because I have actually had mainsail up and connect. Then it shut down due to the missing printer. This is as expected. My question is purely about this login prompt from the PI.
Such touch screens are typically used to display a UI similar to Mainsail / Fluidd directly at the printer.
The software component that is responsible for showing this UI is called KlipperScreen (can be conveniently installed via KIAUH).
If this component is not installed, such screen will act as if you connected a regular monitor / screen like on your laptop.
What you show on your screenshot is the typical end of the boot process of a headless Linux installation, i.e. the login prompt that will take you to the shell, once you have logged in.
Ok, much more clear now.
So If I want to show mainsail similar components, I have to install klipperscreen as well?
Also, if my previous klippers went past this login, and ended up showing the klipper logo and menus, what is different this time? Simply the missing klipperscreen?
Thank you, I reckon this is my next step and see what it brings. Those instructions on readthedocs seem very well written out so I will follow them.
@hcet14 Thank you for the link, If I run into trouble with readthe docs I will see if he has a fix.
@EddyMI3D Oh yes, the dreaded locale. Since I have lived more then half my life in different countries, all I have to say is “Do not ever simply change your keyboard layout, or risk loosing access to your password!”. Thanks, it is set and all the locales have been updated and all on the list are the same
I had to change my screen settings in config anyway since I decided to use the BTT50tft instead of this standard voron turn-wheel thing. So thanks everybody sofar, back to the drawing table.
Many thanks again to all for the superb advise. The klipperscreen docs worked a treat and I did not encounter any problems.
Up to the next step, actually connecting hardware to the MCU and re-writing the configs.
