The latest kernel/kernel headers and the 2 latest raspberrypi-bootloader packages has been pushed to the unstable branch when the mirrors sync.
The 2 new raspberrypi-bootloader packages has a ton of changes:
https://github.com/raspberrypi/firmware/commit/afdb60cc1a8a4aa0c6af68f02b6c1efe6256ba5d
linux-rpi4 5.10.42-1
linux-rpi4-headers 5.10.42-1
linux-rpi4-mainline 5.12.9-1
linux-rpi4-mainline-headers 5.12.9-1
raspberrypi-bootloader 20210608-1
raspberrypi-bootloader-x 20210608-1vlc can not play sup subtitle.
switch to mpvā¦no audio.
Using xfce here and I am not seeing any of these issues with the latest kernel so I do not believe they are kernel issues as per this thread. Try converting sup to srt. I do not have any sup subtitles here to test but mpv audio works just fine.
sorry, guess it was Pi4 related thread.
The latest kernels/kernel headers has been pushed to the unstable branch when the mirrors sync.
Nothing new yet with the raspberrypi-bootloader packages.
linux-rpi4 5.10.43-1
linux-rpi4-headers 5.10.43-1
linux-rpi4-mainline 5.12.10-1
linux-rpi4-mainline-headers 5.12.10-1The latest kernel/kernel headers and rpi-eeprom packages has been pushed to the unstable branch when the mirrors sync.
A minor upgrade with the rpi-eeprom package involving ābetaā (no changes else where):
https://github.com/raspberrypi/rpi-eeprom/commit/4b7fcc65e98dc42baef6e5eab5268e87f932b5c2
Nothing new yet with the raspberrypi-bootloader packages.
linux-rpi4 5.10.44-1
linux-rpi4 headers-5.10.44-1
rpi-eeprom 20210611-1yea, that just broke dtoverlay=vc4-kms-v3d, left me with a frozen cursor on a gray desktop.
switched to dtoverlay=vc4-fkms-v3d & was able to boot.
iām using sway on a rpi400.
I used fkms (because my vizio tv will not boot kms) and my pi4 when I tested the new kernel. I just now hooked up my gateway monitor and my pi 400 and changed the config.txt to boot kms and all is good with xfce.
At this point I do not know if it is your DE or some new code changes which affects your monitor or a combination of all of the above.
Looks like you had it configured for kodi.
yes, i played with it. it runs good with those settings so i been using it on the desktop.
no luck, gray screen
I will keep an eye out on the issues on the kernel tree with the new kernel. The Pi OS uses fkms in their image bt default and that is all I can use on my vizio tv because of it not providing the right edid info. I have no issue with fkms. From what I understand is fkms is their brain child and it uses their firmware but kms bypasses their firmware and uses what the kernel provides.
yea, there kms is still pretty young. iāll watch over there see if anything about it comes up.
i donāt like to ask, cause they got a thing about other osās than raspberry.
i used the 64bit raspberry to fix the config.txt, itās my backup os. 
I totally understand. I walk on pins and needles with them. I only open issues with their kernel but before that I compile their kernel to verify the issue is still there. I use their defconfig for a base though but add extra modules for things people want here.
exactly, i prefer to roll up my sleeve & fix it myself.
i turned off āquiet splashā see if i could spot anything, in journalctl i see 2 kernel blips about shared memory.
itās something with sway, booting to cli is fine, as soon as i execute sway, gray screen with cursor no response from mouse or keyboard.
i toasted my install, got to start over.
I stumbled upon a package called connman. It has some appeal, so I may mess around with it. But in the Arch wiki on connman, I find this concerning the use of iwd verses wpa_supplicant:
"... the ping times seem to be much more consistent and the connection seems to be more reliable."
@Darksky do you have any thoughts on that?
I messed around with replacing wpa_supplicant with iwd a little while back. Back when it had the issue of hanging on reboot. I changed back, when the issue was fixed. iwd worked well enough but I did not know of a compelling reason to stick with it. But if it helps with better wifi connections, that might be enough of a reason.
Edit: I have since learned that both the connman and iwd projects are by Intel. So maybe that is more of a bias, than a real difference.
the minimal install is cli, it uses iwd for wifi connection.
when i build up i use the minimal, then:
iwctl --passphrase passphrase station device connect SSID
then i can the install whatever wm or desktop i want to play with.
the last time i did a minimal build, i did jwm, firefox & used lxterminal to run mc as the file manager & editor. fun times.
once you setup iwd, your done you donāt need a network manager, you can if you want, like for example you can set iwd as the back end for network manager.
https://wiki.archlinux.org/title/NetworkManager#Using_iwd_as_the_Wi-Fi_backend
in sway we use network managerās cli interface nmtui.
