Reboot on Pi 3B not working about pidesktop

[hoopsurfer]

Can you provide the output of pd-check? Reboot from the menu or the command line should work exactly the same. For me with a 3B or 3B+ reboot either way takes just seconds before the Pi Desktop top LED stops flashing.

First thing I would check is if you have the latest Raspian Stretch kernel and matching firmware via pd-check and you should see dates after March. If you see March or earlier you should:

sudo apt update
sudo apt full-upgrade

And try pd-check again to see the new dates.

[hoopsurfer]

Here is what I see:

OS & Firmware versions:

raspberrypi-firmware soc:firmware: Attached to firmware from 2018-04-16 18:16
Linux 4.14.34-v7+ #1110 SMP Mon Apr 16 15:18:51 BST 2018 GNU/Linux

[robynjayqueerie]

Hi, sorry for the delay, I have been trying to get node and sqlite working I have attached the output from the pd-check, it has not line breaks but hopefully you will find what you want. It was all the latest stretch Raspbian installed and pd-check shows todays date Kind regards Robyn Robyn Hannah PhD BE (Hons 1) Grad Dip Counselling. <http://nrie.com.au/NRIEWB9Version/index.html> NRIE Logo NRI Electronics Pty. Ltd. PO Box 20, Alstonville, NSW, 2477. Phone: [phone] or 0427 068 257 email: <mailto:[email protected]> mailto:[email protected] www.nrie.com.au From: hoopsurfer [mailto:[email protected]] Sent: Thursday, 24 May 2018 14:36 To: hoopsurfer/pidesktop Cc: robynjayqueerie; Author Subject: Re: [hoopsurfer/pidesktop] Reboot on Pi 3B not working (#18) Can you provide the output of pd-check? Reboot from the menu or the command line should work exactly the same. For me with a 3B or 3B+ reboot either way takes just seconds before the Pi Desktop top LED stops flashing. First thing I would check is if you have the latest Raspian Stretch kernel and matching firmware via pd-check and you should see dates after March. If you see March or earlier you should: sudo apt update sudo apt full-upgrade And try pd-check again to see the new dates. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#18 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AFEuiTAafNjjVovXYA4ttSnCk0biqhkJks5t1jjAgaJpZM4UIINH> . <https://github.com/notifications/beacon/AFEuiQVqejyImzrepMUzSkzwetyKPBZfks5t1jjAgaJpZM4UIINH.gif> OS & Firmware versions: raspberrypi-firmware soc:firmware: Attached to firmware from 2018-04-16 18:16 Linux 4.14.34-v7+ #1110 SMP Mon Apr 16 15:18:51 BST 2018 GNU/Linux pidesktop Script files: /usr/share/pidesktop/python: total 36 drwxr-xr-x 2 pi pi 4096 May 22 17:11 . drwxr-xr-x 4 pi pi 4096 May 22 17:11 .. -rwxr-xr-x 1 pi pi 1700 Apr 11 14:43 pd-bootssd.py -rwxr-xr-x 1 pi pi 1125 Apr 11 14:43 pd-clonessd.py -rwxr-xr-x 1 pi pi 4393 Apr 11 15:01 pd-fixrtc.py -rwxr-xr-x 1 pi pi 970 Apr 11 14:43 pd-powerkey.py -rwxr-xr-x 1 pi pi 866 Apr 11 14:43 pd-reboot.py -rwxr-xr-x 1 pi pi 1690 Apr 11 14:43 pd-shutdown.py /usr/share/pidesktop/script: total 20 drwxr-xr-x 2 pi pi 4096 May 22 17:11 . drwxr-xr-x 4 pi pi 4096 May 22 17:11 .. -rwxr-xr-x 1 pi pi 621 Apr 11 16:38 pd-check -rwxr-xr-x 1 pi pi 175 Apr 11 14:43 pd-clonessd -rwxr-xr-x 1 pi pi 70 Apr 11 14:43 pd-rtcsync Links to commands: lrwxrwxrwx 1 root root 41 May 22 17:11 /usr/bin/pd-bootssd -> /usr/share/pidesktop/python/pd-bootssd.py lrwxrwxrwx 1 root root 36 May 22 17:11 /usr/bin/pd-check -> /usr/share/pidesktop/script/pd-check lrwxrwxrwx 1 root root 39 May 22 17:11 /usr/bin/pd-clonessd -> /usr/share/pidesktop/script/pd-clonessd lrwxrwxrwx 1 root root 40 May 22 17:11 /usr/bin/pd-fixrtc -> /usr/share/pidesktop/python/pd-fixrtc.py Systemd services: pidesktop-powerkey.service enabled pidesktop-reboot.service enabled pidesktop-shutdown.service enabled System and hardware clocks: Local time: Fri 2018-05-25 15:26:28 AEST Universal time: Fri 2018-05-25 05:26:28 UTC RTC time: Fri 2018-05-25 05:26:29 Time zone: Australia/Sydney (AEST, +1000) Network time on: yes NTP synchronized: yes RTC in local TZ: no Package status: Package: pidesktop-base Status: install ok installed Priority: optional Section: free Maintainer: hoopsurfer Architecture: all Version: 0.1.6 Description: Pi DeskTop Case Power+RTC+mSATA Support

[hoopsurfer]

It looks like you have the correct firmware, I'm expecting when you say it works with the 3B+ you are using the same mSATA SSD with the exact same raspian image on it just changing the underlying board correct?

IF that is true, one possibility is you have /boot/config.txt setup to be board specific, check to make sure this line is in your config.txt and it is not specific to any one model using what are called section headers. You should see the gpio option in your config.txt and it must be executed to turn off the flashing from the power management controller (else it shuts the system down after ~30 seconds as you are seeing)

gpio=6=op,pn,dl

When this happens during boot (early stage boot), it causes the case top LED to stop flashing. I will do some retesting on a 3B myself when I get a chance.

[robynjayqueerie]

Yes, all I am doing is swapping the underlying board from a 3B to a 3B+ I will run the thing up and do the tests on Monday, thanks for your help Robyn Robyn Hannah PhD BE (Hons 1) Grad Dip Counselling. <http://nrie.com.au/NRIEWB9Version/index.html> NRIE Logo NRI Electronics Pty. Ltd. PO Box 20, Alstonville, NSW, 2477. Phone: [phone] or 0427 068 257 email: <mailto:[email protected]> mailto:[email protected] www.nrie.com.au From: hoopsurfer [mailto:[email protected]] Sent: Saturday, 26 May 2018 14:33 To: hoopsurfer/pidesktop Cc: robynjayqueerie; Author Subject: Re: [hoopsurfer/pidesktop] Reboot on Pi 3B not working (#18) It looks like you have the correct firmware, I'm expecting when you say it works with the 3B+ you are using the same mSATA SSD with the exact same raspian image on it just changing the underlying board correct? IF that is true, one possibility is you have /boot/config.txt setup to be board specific, check to make sure this line is in your config.txt and it is not specific to any one model using what are called section headers. You should see the gpio option in your config.txt and it must be executed to turn off the flashing from the power management controller (else it shuts the system down after ~30 seconds as you are seeing) gpio=6=op,pn,dl When this happens during boot (early stage boot), it causes the case top LED to stop flashing. I will do some retesting on a 3B myself when I get a chance. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#18 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AFEuiSMrtR3EJKS6H9bXNnJBAZkqRG3Cks5t2Nr1gaJpZM4UIINH> . <https://github.com/notifications/beacon/AFEuiYQy0JT2ykS11J7F36Ae0HY4-cqlks5t2Nr1gaJpZM4UIINH.gif>

[robynjayqueerie]

Just checked, the config.txt is attached, it looks as you are expecting it. Robyn Robyn Hannah PhD BE (Hons 1) Grad Dip Counselling. <http://nrie.com.au/NRIEWB9Version/index.html> NRIE Logo NRI Electronics Pty. Ltd. PO Box 20, Alstonville, NSW, 2477. Phone: [phone] or 0427 068 257 email: <mailto:[email protected]> mailto:[email protected] www.nrie.com.au From: hoopsurfer [mailto:[email protected]] Sent: Saturday, 26 May 2018 14:33 To: hoopsurfer/pidesktop Cc: robynjayqueerie; Author Subject: Re: [hoopsurfer/pidesktop] Reboot on Pi 3B not working (#18) It looks like you have the correct firmware, I'm expecting when you say it works with the 3B+ you are using the same mSATA SSD with the exact same raspian image on it just changing the underlying board correct? IF that is true, one possibility is you have /boot/config.txt setup to be board specific, check to make sure this line is in your config.txt and it is not specific to any one model using what are called section headers. You should see the gpio option in your config.txt and it must be executed to turn off the flashing from the power management controller (else it shuts the system down after ~30 seconds as you are seeing) gpio=6=op,pn,dl When this happens during boot (early stage boot), it causes the case top LED to stop flashing. I will do some retesting on a 3B myself when I get a chance. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#18 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AFEuiSMrtR3EJKS6H9bXNnJBAZkqRG3Cks5t2Nr1gaJpZM4UIINH> . <https://github.com/notifications/beacon/AFEuiYQy0JT2ykS11J7F36Ae0HY4-cqlks5t2Nr1gaJpZM4UIINH.gif> # For more options and information see # http://rpf.io/configtxt # Some settings may impact device functionality. See link above for details # uncomment if you get no picture on HDMI for a default "safe" mode #hdmi_safe=1 # uncomment this if your display has a black border of unused pixels visible # and your display can output without overscan #disable_overscan=1 # uncomment the following to adjust overscan. Use positive numbers if console # goes off screen, and negative if there is too much border #overscan_left=16 #overscan_right=16 #overscan_top=16 #overscan_bottom=16 # uncomment to force a console size. By default it will be display's size minus # overscan. #framebuffer_width=1280 #framebuffer_height=720 # uncomment if hdmi display is not detected and composite is being output #hdmi_force_hotplug=1 # uncomment to force a specific HDMI mode (this will force VGA) #hdmi_group=1 #hdmi_mode=1 # uncomment to force a HDMI mode rather than DVI. This can make audio work in # DMT (computer monitor) modes #hdmi_drive=2 # uncomment to increase signal to HDMI, if you have interference, blanking, or # no display #config_hdmi_boost=4 # uncomment for composite PAL #sdtv_mode=2 #uncomment to overclock the arm. 700 MHz is the default. #arm_freq=800 # Uncomment some or all of these to enable the optional hardware interfaces #dtparam=i2c_arm=on #dtparam=i2s=on #dtparam=spi=on # Uncomment this to enable the lirc-rpi module # Additional overlays and parameters are documented /boot/overlays/README # Enable audio (loads snd_bcm2835) dtparam=audio=on dtoverlay=i2c-rtc,pcf8563 gpio=6=op,pn,dl

[robynjayqueerie]

Interesting, if I run the unit up and do a reboot it works, reboots fine but then second time always goes to shutdown. Robyn Robyn Hannah PhD BE (Hons 1) Grad Dip Counselling. <http://nrie.com.au/NRIEWB9Version/index.html> NRIE Logo NRI Electronics Pty. Ltd. PO Box 20, Alstonville, NSW, 2477. Phone: [phone] or 0427 068 257 email: <mailto:[email protected]> mailto:[email protected] www.nrie.com.au From: hoopsurfer [mailto:[email protected]] Sent: Saturday, 26 May 2018 14:33 To: hoopsurfer/pidesktop Cc: robynjayqueerie; Author Subject: Re: [hoopsurfer/pidesktop] Reboot on Pi 3B not working (#18) It looks like you have the correct firmware, I'm expecting when you say it works with the 3B+ you are using the same mSATA SSD with the exact same raspian image on it just changing the underlying board correct? IF that is true, one possibility is you have /boot/config.txt setup to be board specific, check to make sure this line is in your config.txt and it is not specific to any one model using what are called section headers. You should see the gpio option in your config.txt and it must be executed to turn off the flashing from the power management controller (else it shuts the system down after ~30 seconds as you are seeing) gpio=6=op,pn,dl When this happens during boot (early stage boot), it causes the case top LED to stop flashing. I will do some retesting on a 3B myself when I get a chance. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#18 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AFEuiSMrtR3EJKS6H9bXNnJBAZkqRG3Cks5t2Nr1gaJpZM4UIINH> . <https://github.com/notifications/beacon/AFEuiYQy0JT2ykS11J7F36Ae0HY4-cqlks5t2Nr1gaJpZM4UIINH.gif>

[hoopsurfer]

Are you seeing any LEDs blink on the Pi board? If that still won't boot, perhaps try:

sudo touch /forcefsck

And shutdown/start to repair a possible damaged boot partition. I have seen reboot failures from crashes and from my observations the 3B+ appears to be more sensitive.

[hoopsurfer]

Another approach to force fsck at boot is to add the following to /boot/cmdline.txt. I have seen both the sudo touch /forcefsck and this approach fix a system that didn't boot.

...fsck.mode=force fsck.repair=yes

more info at: https://www.freedesktop.org/software/systemd/man/[email protected]

[robynjayqueerie]

Thanks, I will try it, sorry to have been a bit slack on this, there has been so much to do here. I will report the results Robyn Robyn Hannah PhD BE (Hons 1) Grad Dip Counselling. <http://nrie.com.au/NRIEWB9Version/index.html> NRIE Logo NRI Electronics Pty. Ltd. PO Box 20, Alstonville, NSW, 2477. Phone: [phone] or 0427 068 257 email: <mailto:[email protected]> mailto:[email protected] www.nrie.com.au From: hoopsurfer [mailto:[email protected]] Sent: Saturday, 16 June 2018 17:17 To: hoopsurfer/pidesktop Cc: robynjayqueerie; Author Subject: Re: [hoopsurfer/pidesktop] Reboot on Pi 3B not working (#18) Another approach to force fsck at boot is to add the following to /boot/config.txt and just comment them when not needed. I have seen both the sudo touch /forcefsck and this approach fix a system that didn't boot. fsck,mode=force fsck.repair=yes more info at: https://www.freedesktop.org/software/systemd/man/[email protected] — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#18 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AFEuiZOli2zaCDTOik4ZX7ZTLulDRYmkks5t9LDdgaJpZM4UIINH> . <https://github.com/notifications/beacon/AFEuiT9N1sF2xo_ZGNitQtK1x7z4f8lzks5t9LDdgaJpZM4UIINH.gif>

[hoopsurfer]

**NOTE: CHECK THAT FIRMWARE IN pd-check IS DATED 2018-06-29 OR NEWER! A needed firmware update that we requested has been made that dramatically improves reboot reliability. You can wait for the patch to make it into a formal release or if you do want to use the pre-release firmware you can run rpi-update to install the newest firmware build. Shutdown and restart and recheck that you have newer firmware with the pd-check command again.

[robynjayqueerie]

after reboot the Version is 0.1.6 which is what it was before the upgrade, I think. I did not write it down though.
However the Pi3B is now rebooting reliably so something must have changed.
Thanks
robyn

[hoopsurfer]

If you updated to firmware dated 2018-06-29 or later then you have a specific reboot fix that would explain the improvement, otherwise what I've found is there are some Pi devices that tend to work on boot (without that new fix) and some that do not. Glad it is working for you.