Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plymouth script module based themes broken #256

Open
devshanky opened this issue Feb 22, 2021 · 5 comments
Open

Plymouth script module based themes broken #256

devshanky opened this issue Feb 22, 2021 · 5 comments

Comments

@devshanky
Copy link

Facing issues with Plymouth script based themes on RaspiOS 64-bit arm64 updated to latest firmware. It may randomly show up during boot and sometimes it flashes and disappears. Mostly observed when the screen resolution changes from 720p to 1080p or vice-versa.

2-step throbber based themes works fine.

-R

@devshanky
Copy link
Author

Always works with hdmi_safe=1.

It was working reliably on 5.4.79-v8+ without hdmi_safe=1.

-R

@popcornmix
Copy link
Collaborator

Does switching

dtoverlay=vc4-fkms-v3d

to

dtoverlay=vc4-kms-v3d

in config.txt help?

@devshanky
Copy link
Author

No. Tried both.

-R

@devshanky
Copy link
Author

devshanky commented Feb 22, 2021

I have a feeling it may have to do with initramfs.

I am able to consistently see the plymouth screens if I do update-initramfs -c -k $(uname -r) after a change in screen resolution. However I lose it again on subsequent reboot. I am unable to understand this behavior. It is not desirable to update-initramfs after change in screen resolution.

I do xrandr -s for immediate effect and also update config.txt with hdmi_mode and hdmi_group with appropriate values.

-R

ps.
I also have initramfs initrd.img-5.4.79-v8+ followkernel in config.txt.

@devshanky
Copy link
Author

devshanky commented Feb 22, 2021

@popcornmix WELL WELL WELL....

I commented out dtoverlay=vc4-fkms-v3d and now the things are back to normal.

I compared output of dmesg from both the scenarios when things work good and when it doesn't with dtoverlay=vc4-fkms-v3d enabled.

Looks like a timing issue with loading overlay drm driver. Please look a the image attached with this message.

drm_timing_issue

Unfortunately, I will not be able to use kms or fkms driver with this update.
This also means I will not be able to xrandr to change the settings on the fly...
-R

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants