[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mesa (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911030
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm not seeing this bug at all in a newly installed 21.04 Pi4. Can you
please update and retest?
** Changed in: mesa (Ubuntu)
Status: New => Incomplete
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
** Changed in: mesa (Ubuntu)
Importance: Low => Medium
**
Ah right, sorry. Your workaround is to force software rendering :)
** Summary changed:
- Graphical flashes on a raspi 4 when software rendering is forced
+ Graphical flashes on a raspi 4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
hmm? No this issue is with the default fkms out of the box overlay - so
nothing is forced here.
What I was also saying that the v3d overlay overcomes the flashes issue
... but only if you copy the overlay into the overlays folder as
upstream pi maintainers say should be happening with the Ubuntu
I think the issue here is that you've discovered the software renderer
by choosing a dtoverlay value that wasn't supported.
So yes it's a bug, but not one we plan on devoting any time to.
** Summary changed:
- Graphical flashes on a raspi 4
+ Graphical flashes on a raspi 4 when software
Daniel - FYI - I raised the issue of the dtoverlay vc4-kms-v3d vs vc4
-kms-v3d-pi4.
TL;DR - the v3d overlay is not activating the accelerated driver.
Upstream confirmed this is an issue with Ubuntu's kernel - I'm hoping
this will be caught and resolved in an upcoming raspi kernel update.
think we are going to have to wait for the raspi v5.10 kernels - even
after installing the 5.10 arm debs, the raspi ignores them and boots
with the 5.8 raspi kernel.
On Tue, 19 Jan 2021 at 03:00, Daniel van Vugt
<1911...@bugs.launchpad.net> wrote:
>
> Full KMS hardware support is available in
Full KMS hardware support is available in newer kernels (5.10.x I think)
so please try installing a newer arm64 kernel like:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10.8/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Further testing. Using the KMS driver results in mesa defaulting to
llvmpipe software rendering making YouTube a painful experience.
So the fkms is needed for 3d acceleration but glitchy graphics... ho-
hum.
On Thu, 14 Jan 2021, 16:34 David Mohammed, wrote:
> Do note.
>
> If I change in
Do note.
If I change in /boot/firmware/config.txt the default
dtoverlay=vc4-fkms-v3d
To
dtoverlay=vc4-kms-v3d
Then the graphical issues disappear. Maybe something to consider?
On Tue, 12 Jan 2021, 02:25 Daniel van Vugt, <1911...@bugs.launchpad.net>
wrote:
> ** Tags added: raspi raspi-gfx
>
** Tags added: raspi raspi-gfx
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- graphical flashes on a raspi 4
+ Graphical flashes on a raspi 4
--
You received this bug notification
** Attachment added: "Video of the issue"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1911030/+attachment/5451810/+files/20210111_164733.mp4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
13 matches
Mail list logo
