Issues since kernel got updated to 4.19.93

[kerry_s]

i don't have the "overlay=1"

i do however have:

Code: Select all

arm_freq=2000
over_voltage=5
gpu_mem=96

these extra's in my config.txt

[Plee82]

the fist pair worked

the second pair froze at startup, had to turn off via switch, pull the sdcard, copy the first pair back to boot up again.

worked, i'm using now.

Code: Select all

Did the first pair of files when updated together (start4.elf/fixup4.dat) work correctly?

did not even boot, froze at multi colored screen. hard power off needed.

Code: Select all

Did the second pair of files when updated together (start4.elf/fixup4.dat) work correctly?

You said the first pair worked but then you said it didn't. Confused.

[kerry_s]

the fist pair worked

the second pair froze at startup, had to turn off via switch, pull the sdcard, copy the first pair back to boot up again.

worked, i'm using now.

Code: Select all

Did the first pair of files when updated together (start4.elf/fixup4.dat) work correctly?

[/color]

did not even boot, froze at multi colored screen. hard power off needed.

Code: Select all

Did the second pair of files when updated together (start4.elf/fixup4.dat) work correctly?

[/color]

You said the first pair worked but then you said it didn't. Confused.

no i clearly said the first pair worked and the second did not.

[mikeschn]

If you re-post the two files that worked, for clarity, I'll be home in 4 hours. I can test it. Thanks,

Mike...

[donegana]

Sorry, over_voltage=1 NOT overlay=1. My mistake.

[kerry_s]

Code: Select all

https://github.com/raspberrypi/firmware/blob/63bdbe0ea609a69f5c0a2212d608ef3d9915a7ad/boot/start4.elf?raw=true

https://github.com/raspberrypi/firmware/blob/63bdbe0ea609a69f5c0a2212d608ef3d9915a7ad/boot/fixup4.dat?raw=true

these 2 are the 1s that work.

[hectorkvs]

Sorry, over_voltage=1 NOT overlay=1. My mistake.

I can confim..first pair did the job..i boot up the system again..it worked..second pair ended up freezing the system...btw..my system is OC..over_voltage=5 arm_freq=2000..

[dom]

I can confim..first pair did the job..i boot up the system again..it worked..second pair ended up freezing the system...btw..my system is OC..over_voltage=5 arm_freq=2000..

Does removing the overclock have a difference with the firmware that fails?

@kerry_s do you have any non-default settings in config.txt?

[dom]

@kerry_a @hectorkvs (and anyone else with the issue)
Does this firmware work okay for you?
It is latest firmware with the suspected commit reverted.

[kerry_s]

I can confim..first pair did the job..i boot up the system again..it worked..second pair ended up freezing the system...btw..my system is OC..over_voltage=5 arm_freq=2000..

Does removing the overclock have a difference with the firmware that fails?

@kerry_s do you have any non-default settings in config.txt?

no, they were commented out during testing. i uncommented them after several reboots to make sure i could boot first. i don't think those settings have any bearing on the working or not working files.

[hectorkvs]

@kerry_a @hectorkvs (and anyone else with the issue)
Does this firmware work okay for you?
It is latest firmware with the suspected commit reverted.

no matter if it's OC or not second pair ending up in boot failure..first pair works well..i tried with OC and without OC several times,did again sudo apt update and upgrade, rebooted several times and it seems to work for now..but few times when i did sudo reboot from terminal, sistem didn't booted properly, i needed to unplug the cable and from zero start it boot normaly..i guess this is unsolved issue from 20200205 firmware/kernel update, not the last one from 20200210..

[kerry_s]

@kerry_a @hectorkvs (and anyone else with the issue)
Does this firmware work okay for you?
It is latest firmware with the suspected commit reverted.

it froze on reboot, but booted fine after that, 3 reboots no issues getting to the desktop.

just to remind you, my install is raspbian lite + gnome-core, so a minimal gnome install, only enough gnome for it to work.

[dom]

no matter if it's OC or not second pair ending up in boot failure..first pair works well..i tried with OC and without OC several times,did again sudo apt update and upgrade, rebooted several times and it seems to work for now..but few times when i did sudo reboot from terminal, sistem didn't booted properly, i needed to unplug the cable and from zero start it boot normaly..i guess this is unsolved issue from 20200205 firmware/kernel update, not the last one from 20200210..

Yes, failure to reboot in some circumstances is an issue with older firmware (like the first one of pair I linked to earlier).
The latest google drive firmware shouldn't have the reboot issue.
Can you confirm the google drive firmware fixes the failure to boot with PLL error issue?

[kerry_s]

no matter if it's OC or not second pair ending up in boot failure..first pair works well..i tried with OC and without OC several times,did again sudo apt update and upgrade, rebooted several times and it seems to work for now..but few times when i did sudo reboot from terminal, sistem didn't booted properly, i needed to unplug the cable and from zero start it boot normaly..i guess this is unsolved issue from 20200205 firmware/kernel update, not the last one from 20200210..

Yes, failure to reboot in some circumstances is an issue with older firmware (like the first one of pair I linked to earlier).
The latest google drive firmware shouldn't have the reboot issue.
Can you confirm the google drive firmware fixes the failure to boot with PLL error issue?

i can confirm "it is working" i am using it right now. i'm like 15 reboots in without oc for like the first 5 reboots, then i uncommented the oc, so it can go up to 2ghz as needed. i think it's good now.

[hectorkvs]

no matter if it's OC or not second pair ending up in boot failure..first pair works well..i tried with OC and without OC several times,did again sudo apt update and upgrade, rebooted several times and it seems to work for now..but few times when i did sudo reboot from terminal, sistem didn't booted properly, i needed to unplug the cable and from zero start it boot normaly..i guess this is unsolved issue from 20200205 firmware/kernel update, not the last one from 20200210..

Yes, failure to reboot in some circumstances is an issue with older firmware (like the first one of pair I linked to earlier).
The latest google drive firmware shouldn't have the reboot issue.
Can you confirm the google drive firmware fixes the failure to boot with PLL error issue?

i can confirm "it is working" i am using it right now. i'm like 15 reboots in without oc for like the first 5 reboots, then i uncommented the oc, so it can go up to 2ghz as needed. i think it's good now.

I can confirm as well..with firmware you provided from google drive everything now works like a charm...rebooted 10-15 times, OCed and non OCed,from terminal and from menu, everything is good..hope problem is solved..

[mikeschn]

These two files work for me too! Thanks...

Mike...

Code: Select all

https://github.com/raspberrypi/firmware/blob/63bdbe0ea609a69f5c0a2212d608ef3d9915a7ad/boot/start4.elf?raw=true

https://github.com/raspberrypi/firmware/blob/63bdbe0ea609a69f5c0a2212d608ef3d9915a7ad/boot/fixup4.dat?raw=true

these 2 are the 1s that work.

[dom]

@kerry_s @mikeschn @hectorkvs (and any others with the issue)

Can you try this firmware ?

Rather the reverting the commit it attempts to make it safe.
That means we still have the fix for gpu overclock settings causing a failure to boot.

[mikeschn]

Dom,

Firmware file(s) applied; all 8 of them. It boots fine. Run update and upgrade... reboot... runs fine... shutdown... startup... runs fine.

I think you got it!

Mike...

[pica200]

Rather the reverting the commit it attempts to make it safe.
That means we still have the fix for gpu overclock settings causing a failure to boot.

Can you elaborate? It would be a shame if the GPU overclock fix causes problems for everyone else and must be reverted

[dom]

@mikeschn Thanks for report. If we can get a couple more confirmations we'll push the updated version out tomorrow.

@pica200 The latest test firmware I linked to should still support gpu overclock (in a slightly safer implementation).
Feel free to test it if that is an important feature for you.

[sun_wu]

@kerry_s @mikeschn @hectorkvs (and any others with the issue)
Can you try this firmware ?

I copied the files via ssh in the /boot-Dir and reboot.
First it freez at the colored screen and i need to powercycle the Pi. After that it boot well and reboot too.

[hectorkvs]

@mikeschn Thanks for report. If we can get a couple more confirmations we'll push the updated version out tomorrow.

@pica200 The latest test firmware I linked to should still support gpu overclock (in a slightly safer implementation).
Feel free to test it if that is an important feature for you.

Tried the latest firmware you provided, work awesome..first try OC Gpu to 600Mhz; Cpu to 2000,OV 6,works fine...rebooting,Update,everything seems ok..will push Gpu a little bit more..i need to check stability of the system

[hectorkvs]

@mikeschn Thanks for report. If we can get a couple more confirmations we'll push the updated version out tomorrow.

@pica200 The latest test firmware I linked to should still support gpu overclock (in a slightly safer implementation).
Feel free to test it if that is an important feature for you.

Tried the latest firmware you provided, work awesome..first try OC Gpu to 600Mhz; Cpu to 2000,OV 6,works fine...rebooting,Update,everything seems ok..will push Gpu a little bit more..i need to check stability of the system

new results..OC to 2100 for cpu and 650 for gpu..everything is stable..run some tests,reboot,update..no issues at all..awesome job with this new firmware

[donegana]

Excellent work to detect the problem, but shouldn't you be looking seriously at your quality control, and perhaps a representative sample of RPi4s to test firmware on?

I have used RPi1, 2, 3 for several years but find it hard to remember stable apt upgrades before RPi4 which (a) disabled USB functionality and (a few weeks later) (b) disabled all functionality.

Perhaps something like the Debian testing release might be appropriate?

[kerry_s]

@kerry_s @mikeschn @hectorkvs (and any others with the issue)

Can you try this firmware ?

Rather the reverting the commit it attempts to make it safe.
That means we still have the fix for gpu overclock settings causing a failure to boot.

sorry, it's shopping day for us. just got home.

i'll let the other guys test, i'm saving my gnome install till things are stable. just running the standard raspbian desktop on a different microsd, this is a clean install & never had the boot problems, checked for updates & there are none.