Skip to content
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

Boot failure updating from 9fdd5ca79b8fea585ad92b36190158cca2b07eb6 to next versions #168

Closed
Sharktear opened this issue Feb 5, 2018 · 2 comments

Comments

@Sharktear
Copy link

Hi all,
I updated my Raspberry 3 firmware after about a month from last update and I get the last release (eb13a28) but after reboot I can't connect to my Raspi.
So I tried many times to reboot without success.
The strange thing:
if I use a poor power supply the red led blynk but the Raspberry boot correctly... if I use a good 2,5A power supply the red led is stable on but the boot fail...
I tried to restore to the SD memory a previous backup (containing the 9fdd5ca release of the firmware) and all is fine and the raspberry boot correctly... then I tried to "rpi-update" againg and I fall in the same issue.
I tried to update to a different revision (c66bc1e) but same error...
So I think the problem is in a release next eb13a28, but I don't know which...
Does anyone have a suggestion?

@pelwell
Copy link
Collaborator

pelwell commented Feb 5, 2018

Something in firmware release 23a0077 ("kernel: Bump to 4.9.78") is causing problems for a few users that sound like what you are experiencing, but it isn't something we've been able to reproduce sufficiently to be able to pinpoint the issue. That undervoltage seems to make the problem go away is a useful datapoint.

One thing you could try is preventing the ARM speed from changing with the good power supply - add either arm_freq=600 or force_turbo=1 to config.txt. The first of these effectively disables turbo mode, but you will notice a significant slowdown. The second locks you permanently in turbo mode, but this will cause your Pi3 to heat up and has the potential to shorten the life of your Pi a little.

If you find that these settings make your Pi boot reliably then you could try a compromise setting of:

arm_freq=1000
force_turbo=1

Either way, let me know what you find.

@pelwell
Copy link
Collaborator

pelwell commented Feb 5, 2018

This report is essentially a duplicate of #165 - please see the updated firmware files linked from that issue and continue the discussion there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants