Reboot fails #177
Comments
|
Hey, First of all: which pm2 script are you using? Did you choose the one that is waiting for internet connection? |
|
Yes, this is definitely a last minute present :-D I tried both versions, with and without waiting, both seem to stuck. How can I reach the logs, when the pi is totally freezed? |
|
Do you have ssh access to the pi? Or is this also frozen? |
|
let me try :) |
|
Here are the log with the frame on first boot up, working fine: pi@raspberrypi:~ $ pm2 logs 0 /home/pi/.pm2/logs/TeleFrame-out.log last 15 lines: |
|
Ok, and then you do a reboot and it stops working? |
|
Now I did the reboot and the pi is frozen. I can ping the pi, but can not connect through SSH |
|
What is also strange to me: I would like configure the frame the way, that it does not start from boot up. |
|
how did you disable it? |
|
if you don't want to run teleframe at boot, you don't need pm2... |
|
I mean when setting up the frame. |
|
did you just run the install script again? |
|
yes, sevaral times. |
|
Ok, this might be the problem. I am honestly not sure what happens when you run it multiple times. My advice would be to flash a new raspberry pi os and run the script only once with the desired settings... |
|
okay, sorry. I mean totally from new, with new OS. |
|
It must be outside of the TeleFrame. Is the installation of the teleframe changing anything else anywhere for the bootup? |
|
Not really. What happens when you reboot a new OS? |
|
But you could also try the manual installation... |
|
@AAAbrAkAdAbrAAA |
|
EDITED: Freeze after Boot solved - see two posts below. Hey everybody. If anybody has an idea what went wrong or if I anyhow can get the PI back to life or avoid this behaivour at next installation I would be happy. Thanks in advance. PS: Raspberry Pi OS was installed yesterday and kodi was compiled manually to run parallel to teleframe. Nothing else was changed systemwise. Installation log: (unfortunately it is german) |
|
reading the log again I guess I should have tried installing the npm package manually? |
|
Hello together, I made a fresh PiOs installation and used the install.sh script again. got the same result as yesterday. Therefore I tried to install npm manually and try again. Unsuccessfull - see below. I copied the install-script from line 131 where the error appeared into teleframe2.sh and finished installation Now I tried to run teleframe: Now I removed the ~/Teleframe folder and restarted the installation process. Teleframe started automatically with a blank screen all approx. 5 seconds and closed automatically again NPM Log looks like this: I rebooted the PI with and got again into the stucked mode I was yesterday. After SSH authentification SSH stops working (cant write or send). |
|
Boot-Lock solved, NPM error still persistent Wondering that it still stuck beside the service beeing disabled I had a closer look at the installation script and made a change in /boot/config.txt having the SD card inserted into a Windows machine: I commented the added dtoverlay now it is booting again. A first google search revealed, that it could be the combination of the newest Raspberry Pi OS with the display (mine is Waveshare 10.1 Touchscreen) and dtoverlay=vc4-fkms-v3d. Nevertheless, teleframe is still not starting. Showing the white starting screen shortly but crashing a second later after using In terminal again I get: I don't know if this error is related to the boot problem and the overlay but I guess it is not. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First of all thanks for this Open Source Project.
It is awesome and I hope to make my grandma happy this Christmas with a frame :)
But, when installing TeleFrame and booting it first, everything works fine.
Pictures are received and displayed.
So far, so good.
But when rebooting, the raspberry loops into infinity and input does not work.
I already disabled and deinstalled pm2, but it is still an issue.
The raspberry tries to boot TeleFrame right from the start.
The TeleFrame Logo shows up first when rebooting.
Then the screen goes off again.
Then the screen is on without any text or output.
The text was updated successfully, but these errors were encountered: