-
Notifications
You must be signed in to change notification settings - Fork 119
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
Initialization failed #343
Comments
I have retried a clean install and followed Chris' basement video step by step. i attempted to do a docker install, but got nothing from that. I saw there was another issue posted and that pointed me to a 3.5 screen, but that didn't help either. |
Well, what does the log file report? |
I can't find the file. I go to where it should be and it isn't there. Unless I'm looking in the wrong place. |
Same thing with mine |
When I look through the config I see there is a thing asking where I want the file to be, but changing that didn't work either. |
I think it might be related with the new raspbian, even Touch_UI wont work either. |
I believe DiogoBasto is right! I tried to upgrade one of my pi's that I use on my printers and used the new Raspi imager. Got the Octoprint to work on my laptop but nothing I try can get Octoscreen to work. I use the deb files on the Octoscreen page with and without the initial sequence above the deb file. There is a /esc/octoscreen/config folder but nothing in it to configure the program to accept my Pi original 7" screen. I just go back to the pi showing pi login: Something is screwed up. |
I had the same issue |
Thanks a lot. I'll give it a try!!!
Tom
On Thursday, June 30, 2022, 12:02:42 PM EDT, Darthyson ***@***.***> wrote:
I had the same issue initialization failed: readConfig() failed... under OctoScreen 2.7.4.
For me it worked to set the correct path of the OctoPrint config file in /esc/octoscreen/config
OCTOPRINT_CONFIG_FILE=/home/USERNAME/.octoprint/config.yaml
Make sure that USERNAME is the username Octoprint is running. There is no user pi on newer Raspberry Pi OS.
Attached are two debug-level logs. log_failed.txt is without OCTOPRINT_CONFIG_FILE set and log_success.txt is with correct path to OctoPrint config file.
log_failed.txt
log_success.txt
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
@Darthyson Thanks a ton, this worked for me. |
I had to make certain that these variables had values in them as follows OCTOPRINT_CONFIG_FILE=/home/USERNAME/.octoprint/config.yaml where USERNAME is the login name for your RPi logfile.txt did not exist on my installation. Once I set that up it worked. |
hey guys, I have the same error. But unfortunately I'm completely new to the topic. So unfortunately I don't understand how you solved the problem. However, I understand that you have solved it, which gives me great hope. Would someone be kind enough to give me step by step instructions or help me with Disord? |
I did a clean install a few times and the touch screen says:
initialization failed: readConfig() failed, see log for errors
I have a raspberry pi 4 and a hyper pixel 4 that I am trying to set up.
This has been what I have been getting. in putty. After rebooting I get the same error as before
The text was updated successfully, but these errors were encountered: