Created attachment 1765711 [details]
dmesg output with vc4 module blacklisted kernel 5.11.7
1. Please describe the problem:
when booting with kernel 5.11.7 graphics is good but keyboard gets no response and windows opened refuse to take focus. mouse works.
After adding module_blacklist=vc4 to the options in boot/loader/entries/8adec69191ab478896f0c027f7ef27a8-5.11.7-200.fc33.aarch64.conf the system boots and functions normally with keyboard and windows focus.
2. What is the Version-Release number of the kernel:
3. Did it work previously in Fedora? If so, what kernel version did the issue
*first* appear? Old kernels are available for download at
kernel 5.8.15-301 on the release ISO worked. Linux-firmware-20200918 released on the same ISO worked. No 5.10 releases worked. no linux-firmware updates worked until linux-firmware-20210315-119 was released
4. Can you reproduce this issue? If so, please provide the steps to reproduce
the issue below:
Boot the 5.11.7 aarch64 kernel without blacklisting vc4 module.
5. Does this problem occur with the latest Rawhide kernel? To install the
Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
``sudo dnf update --enablerepo=rawhide kernel``:
halts at black screen and produces a kernel oops. I have that data but abrt tells me there is not enough backtrace to send a report.
When I add the same module_blacklist=vc4 to the /boot/loader/entries/8adec69191ab478896f0c027f7ef27a8-5.12.0-0.rc3.20210319git8b12a62a4e3e.172.fc35.aarch64.conf file it boots normally although there is a small black border around the display and xrandr reports 1824x984 @77hz instead of 1920x1080 @60hz
6. Are you running any modules that not shipped with directly Fedora's kernel?:
7. Please attach the kernel logs. You can get the complete kernel log
for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
issue occurred on a previous boot, use the journalctl ``-b`` flag.
Created attachment 1765712 [details]
dmesg output with vc4 module active kernel 5.11.7
Created attachment 1765713 [details]
dmesg output with vc4 module blacklisted kernel 5.12.0
Created attachment 1765714 [details]
dmesg output with vc4 module active kernel 5.12.0
Created attachment 1765715 [details]
data from kernel oops booting from 5.12.0 with module vc4 loaded
My system with the problem is a Raspberry PI version 4B.
I will be glad to test any potential fixes.
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
EOL for F33 and no longer using fedora 33 on R Pi 4B