RPI4 freezes at boot after update

mitu

Are you running with the default config.txt or your overclock settings are still there ? Try using the default one and see if you get the same behavior.

pamput

Hi @mitu,

Yeah, in the end it was the overclocking. Strangely I can't touch the gpu_freq. Whenever I change it it goes belly up at boot. Also I've lost some fluidity since the update. Quite sad :/

Where can I find the default config.txt? I'm a bit confused which project on github is responsible for it.

Update: nvm, I've found the default one provided in Buster.

pamput

Interestingly: https://github.com/raspberrypi/firmware/issues/1290

It seems with the latest kernel gpu_freq is broken.

quicksilver

@pamput i noticed this as well when I ran rpi-update. Part of the reason why I restored my back-up :/

Also why there is warning to users not to update unless they have been instructed to do so.

pamput

@quicksilver, silly me, I didn't do a backup before messing around today :( oh well. Live and learn.

pamput

Has anyone used rpi-update to rollback the firmware/kernel?

It seems you can run the updater as rpi-update <git-hash>
If you check here you can find the hash of the previous release. Worth a try?

@quicksilver could you check for me on what version you are atm?

uname -a

Thanks :)

quicksilver

@pamput it says: Linux pi4 4.19.75-v71+ #1270 SMP The Sep 24 18:51:41 BST 2019 armv71 GNU/Linux

VictimRLSH

I have had problems updating even on the Pi 3B. On my controller mount I had to do a fresh install just to get the controller working again. Update will bork an Xbox 360 controller.

If it ain't broke, I'm not gonna fix it...

roslof

BACKUP before messing with kernels

I also ran a Raspbian upgrade and unexpectedly got the new DVFS kernel.

Release for the older "safe" kernel:
https://github.com/Hexxeh/rpi-firmware/commit/4b2c270e493a978c0427b1fa52ba5bef6436b88b

I downgraded with:

sudo rpi-update afbea38

...then rebooted. I'm now back to kernel 4.19.83-v7

gpu_freq overclock seems to be working again.

pamput

@quicksilver said in RPI4 freezes at boot after update:

Also why there is warning to users not to update unless they have been instructed to do so.

Late reply, sorry: this is because rpi-update updates the firmware to the latest development version, which is not stable at best, breaking at worst. You can read more info here including a guide to rollback to a stable state.

@roslof said in RPI4 freezes at boot after update:

Release for the older "safe" kernel:
https://github.com/Hexxeh/rpi-firmware/commit/4b2c270e493a978c0427b1fa52ba5bef6436b88b

Is this the latest commit with the overclock still working? It's in between releases. What about the following commit?

https://github.com/Hexxeh/rpi-firmware/commit/b9ecbe8d0e3177afed08c54fc938938100a0b73f

pamput

@roslof said in RPI4 freezes at boot after update:

Release for the older "safe" kernel:

I've tried your kernel and it breaks audio for me in several emulators: N64, Neo, etc.

I'm going to try one that isn't an in between commit and see.

pamput

I've tried @quicksilver 's kernel and it works fine. No audio issues:

sudo rpi-update d9321aceacfc6619b4238c6c764203b1122f2f9b.

Probably there is a better sweet spot in between, but I can't be bothered for the moment. Will test this one out a bit first.

pamput

I've done some additional testing and it seems this is a better kernel overall:

4.19.81
https://github.com/Hexxeh/rpi-firmware/commit/77444b020fe5b70f76d1921ae9c4cefd045d74bc

sudo rpi-update 77444b020fe5b70f76d1921ae9c4cefd045d74bc

It does support gpu overclocking, it doesn't have sound issues and doesn't have external HDD issues I've experienced with previous kernels.

Enjoy!

roslof

Is this the latest commit with the overclock still working? It's in between releases. What about the following commit?

https://github.com/Hexxeh/rpi-firmware/commit/b9ecbe8d0e3177afed08c54fc938938100a0b73f

The version that I posted wasn't the latest pre-DVFS version. It was tagged as the latest "safe" version they released, which preceded the latest DVFS safe version they included with a standard Raspbian update. Also, I'm not having any audio issues. Wondering why others are. Great that other kernels exist, that could be better for some.

Another note: The Raspberry Pi group who worked on the Kernel were fully aware that this change broke GPU overclocking, but blessed it anyway. They were more focused on reducing heat with DVFS, despite overclocking. I get it... More people having heat problems than retrogamers wanting to overclock.

You can read more about the history in this thread from November 2019:
https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=257394&start=25#p1570599

roslof

@pamput said in RPI4 freezes at boot after update:

It does support gpu overclocking, it doesn't have sound issues and doesn't have external HDD issues I've experienced with previous kernels.

The version you posted is actually a bit older than the one I posted. I'd love to learn more about your audio issues. I'm not having them. Would you mind sharing:

RetroArch/ Settings/ Audio/ Output / Audio
Are you using alsa, alsathread, tinyalsa or sdl2?

RetroArch/ Settings/ Audio/ Resampler/ Audio Resampler
Are you using sinc, CC or nearest?

Also, are the N64, Neo, etc. emulators you are using libretro (lr_) based?

pamput

@roslof said in RPI4 freezes at boot after update:

RetroArch/ Settings/ Audio/ Output / Audio
Are you using alsa, alsathread, tinyalsa or sdl2?

Alsa

RetroArch/ Settings/ Audio/ Resampler/ Audio Resampler
Are you using sinc, CC or nearest?

sinc

Also, are the N64, Neo, etc. emulators you are using libretro (lr_) based?

Mostly lr-*, I definitely had problems with lr-fbneo, lr-mupen64-next and lr-pcsx-rearmed. I also tested it with all not lr-* N64 emulators, and had the same problem. In general it felt like every emulator using CD like tracks was having issues. I did try nes and snes and didn't have any issue (both lr).

Are you on rpi4 also?

pamput

@roslof said in RPI4 freezes at boot after update:

Another note: The Raspberry Pi group who worked on the Kernel were fully aware that this change broke GPU overclocking, but blessed it anyway. They were more focused on reducing heat with DVFS, despite overclocking. I get it... More people having heat problems than retrogamers wanting to overclock.

Yeah, I understand the sentiment. Maybe from a development perspective I'd disable the parameter by ignoring it instead of releasing a kernel that hangs if the param is in the config.txt. Maybe also add a message in the logs explaining what is happening. Not necessary the end of the world though, I know I'm just neat picking.

VictimRLSH

Different users have different needs. I lean towards portable builds so having less heat and power usage to deal with is preferable to a slight performance increase, especially considering the pi 4 is such a huge performance increase over the 3B+. I am sure a high performance fork would have a demand as well.

roslof

@pamput said in RPI4 freezes at boot after update:

@roslof said in RPI4 freezes at boot after update:

RetroArch/ Settings/ Audio/ Output / Audio
Are you using alsa, alsathread, tinyalsa or sdl2?

Alsa

RetroArch/ Settings/ Audio/ Resampler/ Audio Resampler
Are you using sinc, CC or nearest?

sinc

Also, are the N64, Neo, etc. emulators you are using libretro (lr_) based?

Mostly lr-*, I definitely had problems with lr-fbneo, lr-mupen64-next and lr-pcsx-rearmed. I also tested it with all not lr-* N64 emulators, and had the same problem. In general it felt like every emulator using CD like tracks was having issues. I did try nes and snes and didn't have any issue (both lr).

Are you on rpi4 also?

Yes, I am. Also set for "alsa" and "sinc" like you. Would you give an example of a ROM or CD that is having the issue? So far, everything is fine with me on the "safe" version. Hoping I can help figure out what's happening.

quicksilver

https://github.com/raspberrypi/firmware/issues/1290

Looks like they are working to get at least partial GPU overclocking restored. With the test firmware listed at the bottom of the page I linked you can try it out. Core_freq is still locked but you can set v3d frequency higher than 600mhz now. I am not convinced that v3d is really a bottleneck but glad to see they are working on it.