[SOLVED] Flickering & Blanking screen upon switching window

[darksky]

I downloaded and tested the new kernel and all is good here.

$this->bbcode_second_pass_code('', '[ray@pi4 ~]$ uname -a
Linux pi4 5.10.88-2-rpi-ARCH #1 SMP PREEMPT Fri Dec 31 12:16:23 UTC 2021 aarch64 GNU/Linux')

Additional:

After the big upgrade today here I had to rebuild kodi-rpi.

[TrevorB]

I'm running the armv7, Pi 4, 2 gigs ram. With latest 5.10.89-1-rpi-ARCH Jan 2

Just double checked

All still works still fine with
from
dtoverlay=vc4-kms-v3d
to
dtoverlay=vc4-fkms-v3d

BUT, now if I delete the f and change back to just "dtoverlay=vc4-kms-v3d"
I boot into a black screen, no cursor no nothing, before it would boot okay just had the flickering screen problem, so it actually seems worse.

I just re-added the f connecting the sdflash to my main arch Linux setup so that I could modify the config file

[unformatted]

I have exactly the same issue on a RPi4 running 5.10.89-1-rpi-ARCH on aarch64.

Before upgrading yesterday, running the previous kernel with kms causes blanking while fkms was fine. Now with new kernel and kms I have no display (monitor says no signal) so I changed to fkms.

However on 2 other RPi4's with different monitors the upgrade solved the blanking while using kms.

Using kms can be a real pita because it heavily relies on your monitor's EDID reporting capabilities. At least the blanking screen issue has been resolved but with the new kernel my monitor cannot be used with kms. From the frying pan into the fire..

[graysky]

$this->bbcode_second_pass_quote('unformatted', 'U')sing kms can be a real pita because it heavily relies on your monitor's EDID reporting capabilities. At least the blanking screen issue has been resolved but with the new kernel my monitor cannot be used with kms. From the frying pan into the fire..

[jyno]

I works fine here. Thank you!

[unformatted]

Thank you @graysky for the edid suggestion but at the moment I'm busy upgrading other Pi's using the Pi in question. I just wait until the next kernel upgrade and see what happens. If the problem remains I will try the edid stuff and report back.

[TrevorB]

I tried the following

2. Run this cp /sys/devices/platform/gpu/drm/card1/card1-HDMI-A-1/edid /lib/firmware/edid.dat (need to be sudo for it to work)

3. Edit /boot/cmdline.txt appending drm.edid_firmware=edid.dat video=HDMI-A-1:D to the end of the line (note there is a leading space in there)

So my cmdline reads
root=/dev/mmcblk0p2 rw rootwait console=serial0,115200 console=tty1 selinux=0 plymouth.enable=0 smsc95xx.turbo_mode=N drm.edid_firmware=edid.dat video=HDMI-A-1:D

I then switched back to dtoverlay=vc4-kms-v3d (deleteing the f)

Rebooted, still booted into black screen
Reapplied the dtoverlay=vc4-fkms-v3d (with the f)

Boots correctly
So should I leave the drm.edid_firmware=edid.dat video=HDMI-A-1:D or should I delete it ?, as don't know what that does

Thanks

[graysky]

No need to leave the changes if they did not fix your problem. The idea was that something is broken with edid reading so you provide the edid for the kernel to see if it helps.

[TrevorB]

Did an Syu this morning which installed the Kernel 5.10.90-1

Switched back to dtoverlay=vc4-kms-v3d (deleting the f before the kms)

Rebooted, all seems OK, No flickering screen