Raspberry Pi Forums

That should read 500000. It might have been intended , it might even have worked at a point in the past, Idk, but...setting absolute microvolts is removed, or broken, now . Fortunately it is totally unnecessary since the range of meaningful arm core voltages is largely covered by the relative over_...

But today I downloaded latest Raspbian Desktop, put it on a new SD card. Initial reboots etc were fine, until the automated setup installed updates and then wanted to reboot. The reboot hung on the splash screen. Was this just the first reboot after updating or is it every reboot? First is possible...

@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.

@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.

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...

@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.

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 c...

@kerry_s

Can you just clarify:
Did the first pair of files when updated together (start4.elf/fixup4.dat) work correctly?
Did the second pair of files when updated together (start4.elf/fixup4.dat) work correctly?

the start4.elf booted to a black screen (winner)the fixup4.dat booted all the way to the desktop. important to know: this is on my raspbian lite + gnome-core build, it's the only other sdcard i have that got the pll no boot issue. i fully updated & rebooted several times, looking good so far. You s...

Currently we can't reproduce the PLL issue. Can anyone with the PLL issue try: Add over_voltage=1 to config.txt. If that fails try with 2. Could you download start4.elf and fixup4.dat and replace the ones on boot partition of scard? If that fixes it then could you confirm if start4.elf and fixup4.da...

Interesting, thank you ! Are the "advanced" extensions still checked against some bounds (for sanity) rather than applied bluntly ? Also, please confirm the unit which the mentionned "microvoltage" corrections employ, both absolute and relative. Are they really given in units of µVolt ? It does not...

Slightly off-topic, but... regarding the "overvoltage" adjustments (config.txt), I've seen occasional mentions of non-integer values (e.g., '5.5') in some posts. Are those for real ? Does whatever parses our "config.txt" interpret non-integral values correctly, and what is the granularity (if any) ...

jahboater wrote: ↑
Wed Jan 29, 2020 12:51 am
For fun, try:
Code: Select all
arm_freq=1600
in config.txt
It will run at this speed fine with no special cooling or over-voltage.

There is no guarantee this will be stable on all Pi 4s.

On a PC copy start4*.elf fixup4*.dat to a safe place from boot partition of sdcard. Open first zip file and overwrite the files on boot partition of sdcard with contents of zip. Test if problem occurs (without over_voltage=1). Open second zip file and overwrite the files on boot partition of sdcard ...

Anyone who has this issue and finds it resolved with over_voltage=1
can you try:
test firmware scb125
test firmware volts

with over_voltage=1 removed and report if either firmware fixes the USB issue.

I think you expect too much. In window mode you already get lost frames when you play a 1080p50 video (not in overlay mode!) on a 1080p screen. It will get worse on larger screens or double screens. But I'm not sure what is possible with the new H265 decoder. In an X window, the bottleneck is rende...

Hi with the new version can i play my 3840x1080 videos to fullscreen hdmi outputs? So 1920x1080 (left part of the video) to hdmi1 and 1920x1080 (right part of the video) to hdmi2? thanks I imagine you can do that from desktop in windowed mode (with window occupying almost whole of both screens). Pe...

echmain wrote: ↑
Tue Jan 28, 2020 7:25 pm
Does anyone know if this issue also applies to the Pi Zero?

No, this issue is related to running at low voltages with dvfs which only occurs on a Pi4.

rosioara wrote: ↑
Wed Jan 22, 2020 12:19 pm
over_voltage=1 still works fine.

Could you try this firmware without the over_voltage line?

What would be the issue? Hardware related? I never did overclocking. The firmware commit identified was the main one that reduces power by reducing voltage when idle. It seems like there is a clock required by USB that is not happy (on some boards) at the reduced voltage. Do you have anything non-d...

jamesh wrote: ↑
Thu Jan 02, 2020 4:55 pm
It could be in the VC firmware, but @6by9 would need to confirm.

Yes, raspberrypi/firmware is best (it is the interface between firmware and kernel, so a fix is likely to affect both).
It doesn't appear to be a mesa issue (problem not observed on vc4-kms-v3d on Pi3).

I note that the 64-bit kernel keeps my Pi4 significantly cooler than the 32-bit one. Are you comparing the updating firmware/kernel with and without arm_64bit=1? Or are you comparing and old firmware/kernel with a new one? The temperature difference seems more likely to come from firmware improveme...

There is no problem playing 4k videos on a 1080p display (you can display them on SD composite display if you want).
Your issue is probably down to memory. What have you set gpu_mem to? Probably want at least 360M for 4k decode.
Make sure video files are HEVC format.

can't figure out the forum's private messaging, so here is a one-time link to the cut: https://send.firefox.com/download/cf3b065f2ae3dc1b/#7LlZEy_vi3iLrbAd3P2x7Q Downloaded the file. From mediainfo this is the problem: Chroma subsampling : 4:4:4 which we can't decode in hardware (I'm not sure any h...

Pi 4 here, cma=512M set, it seems the new VLC build can't play my video... Can you start by posting mediainfo (apt install mediainfo) of file? Assuming that is okay, we'll probably need a sample of the video (e.g. cut a 1 minute chunk and upload to a file hosting site like google drive or dropbox).

Search found 5262 matches

Re: Issues since kernel got updated to 4.19.93

Re: Issues since kernel got updated to 4.19.93

Re: Issues since kernel got updated to 4.19.93

Re: Issues since kernel got updated to 4.19.93

Re: Issues since kernel got updated to 4.19.93

Re: Issues since kernel got updated to 4.19.93

Re: Issues since kernel got updated to 4.19.93

Re: Issues since kernel got updated to 4.19.93

Re: Issues since kernel got updated to 4.19.93

Re: Issues since kernel got updated to 4.19.93

Re: Issues since kernel got updated to 4.19.93

Re: Issues since kernel got updated to 4.19.93

Re: ARM Frequency

Re: Issues since kernel got updated to 4.19.93

Re: Issues since kernel got updated to 4.19.93

Re: VLC testing

Re: VLC testing

Re: Issues since kernel got updated to 4.19.93

Re: Issues since kernel got updated to 4.19.93

Re: Issues since kernel got updated to 4.19.93

Re: Tearing in kmscube on Pi4

Re: Pi4 64-bit raspbian kernel for testing - Focus on Pi4

Re: Is it possible to play 4k movies only when a 4k monitor/tv is connected?

Re: VLC testing

Re: VLC testing