7fh3498f
Posts: 28
Joined: Sat Apr 14, 2018 10:09 am

Init 6 causing turning off after last update...

Sat Jun 30, 2018 1:56 pm

I just updated my RPi3B+ to #1122 firmware.
After update my device behaves strange. Init 6 command is causing some sort of turn off state. Weird thing is that all LED's are off and device is not responding. Usualy red LED stayed solid on. I have no clue how to even start troubleshooting. I tried from clean image dated 2018-06-27, same thing. Init 0 also working same way. Any help appreciate. Thank you.

User avatar
DougieLawson
Posts: 35519
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: Init 6 causing turning off after last update...

Sat Jun 30, 2018 4:21 pm

Try sudo rpi-update - there's a fix for the not rebooting from a USB device in there today.
Note: Having anything remotely humorous in your signature is completely banned on this forum. Wear a tinfoil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

User avatar
B.Goode
Posts: 8021
Joined: Mon Sep 01, 2014 4:03 pm
Location: UK

Re: Init 6 causing turning off after last update...

Sat Jun 30, 2018 4:56 pm

Could this be related to the issue you have found with your use of Eltech's Exagear Desktop?

viewtopic.php?f=29&t=217093


Can the problem be replicated in a standard unmodified installation of Raspbian?

7fh3498f
Posts: 28
Joined: Sat Apr 14, 2018 10:09 am

Re: Init 6 causing turning off after last update...

Sat Jun 30, 2018 5:07 pm

DougieLawson wrote:
Sat Jun 30, 2018 4:21 pm
Try sudo rpi-update - there's a fix for the not rebooting from a USB device in there today.
Solution works. Firmware bumped to #1123 Thank you for your help.

7fh3498f
Posts: 28
Joined: Sat Apr 14, 2018 10:09 am

Re: Init 6 causing turning off after last update...

Sat Jun 30, 2018 5:07 pm

B.Goode wrote:
Sat Jun 30, 2018 4:56 pm
Could this be related to the issue you have found with your use of Eltech's Exagear Desktop?

viewtopic.php?f=29&t=217093


Can the problem be replicated in a standard unmodified installation of Raspbian?
Looks like it has nothing to do with Exagear. Thanks anyway...

Return to “Troubleshooting”