CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan

[Hui Wang]

We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D.

In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster.

Please refer to https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/32

[Impact]
Users reported that we should enable the DRM_V3D, then the GPU will
be fully used when running "ubuntu-desktop"

[Fix]
Enable the DRM_V3D, the v3d.ko will be built

[Test Case]
Users already tested it, it worked well.
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36

[Regression Risk]
Low, I already did building test for arm64 and armhf, all passed.
And uers already tested the kernel module, it worked as expected.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Szakács Levente (szvl)]

Does someone know when the fix will be ported to the Ubuntu arm64 image?

[Mark Dunn (mdunn-home)]

I tried upgrading from eoan-proposed, but it isn't there yet on the arm64 when is the next release please ?

[Hui Wang (hui.wang)]

So far, the latest kernel version is Ubuntu-raspi2-5.3.0-1012.14, it doesn't enable the V3D yet.

The next kernel version will include V3D driver module, maybe it will be named 5.3.0-1113. Anyway the kernel that is later than 1012 will include this driver.

[Hui Wang (hui.wang)]

We are going to release a new kernel soon, right now it is in the proposed channel, Welcome to test with the new kernel:

edit the $rpi_rootfs/etc/apt/sources.list and add:
deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed main restricted
deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed universe
deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed multiverse

boot the rpi board, then run:
sudo apt-get update
sudo apt install linux-image-5.3.0-1013-raspi2
sudo reboot

Then you could do the test with the proposed kernel.

At least the 1013 kernel fixed these bugs compared with 1012 kernel:
https://bugs.launchpad.net/bugs/1850876
https://bugs.launchpad.net/bugs/1852510

[Ian Pitt (idpitt)]

Thanks for the new kernel. I booted it and noted that the right drivers were now being used ( Accelerated video and glxinfo showing it was using VC4 rather than the original llvmpipe. However:

1) On Mate, the Pi locked up within a few seconds of resizing windows
2) On Ubuntu, it took a few minutes but again the machine locked up after using applications.

Ahead of failures, areas of the screens were flashing/jittering. Once locked, only a reboot would gain control of the console.

4GB Pi 4, all 64bit kernels - rock solid without acceleration on the former kernel, rock solid WITH acceleration when using Gentoo.

I reverted to the older kernel and the machine is back to being stable, albeit with out the acceleration.

[Hui Wang (hui.wang)]

@Ian,

"rock solid WITH acceleration when using Gentoo", could you please tell me what is the kernel version for Gentoo? Or could you paste the output of 'uname -a' under Gentoo?

I tested the branch rpi-5.3.y of upstream kernel (https://github.com/raspberrypi/linux.git), the v3d driver is better now, but still has some problems. So I guess the Gentoo uses 4.19 kernel?

BTW, we have another bug to track this issue https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852035, from the comment #14 and #15 of that bug, we could see even applying the latest patches of v3d, the driver still has some problems.

So we need to disable the driver v3d in the kernel until the branch rpi-5.3.y has the perfect fix for this driver.

[Ian Pitt (idpitt)]

Yes, the Gentoo image is running 4.19.67.

Thanks, I can wait for a more stable version.

[Ian Pitt (idpitt)]

@Hui, I tried the patched kernel you released and posted on https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852035 . It works fine ( other than the dmesg logs that the other tester posted ) under KDE Plasma and LXQt. It seems that only Mate suffers the flickering and other rendering artifacts. All desktops have accelerated compositing now as expected.

[Hui Wang (hui.wang)]

Thanks for your testing, I will post the remaining issues to upstream and let us wait for the fixes for the remaining issues.

[Mark Dunn (mdunn-home)]

short version:

With raspberry pi 4:
your binaries applied (https://people.canonical.com/~hwang4/v3d-fix/)
The screen flickers then blanks
I installed an built the latest mesa
The screen flickers then blanks
Back to the raspberry pi kernel (4.19)
Which still works...

long version:

downloaded ubuntu-19.10-preinstalled-server-arm64+raspi3.img and restored it to sdcard

sudo apt update
sudo apt upgrade
sudo apt install ubuntu-desktop

wget https://people.canonical.com/~hwang4/v3d-fix/linux-buildinfo-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
wget https://people.canonical.com/~hwang4/v3d-fix/linux-headers-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
wget https://people.canonical.com/~hwang4/v3d-fix/linux-image-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
wget https://people.canonical.com/~hwang4/v3d-fix/linux-modules-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb

sudo dpkg -i linux-modules-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
sudo dpkg -i linux-image-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
sudo dpkg -i linux-buildinfo-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb

sudo dpkg -i linux-headers-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
 linux-headers-5.3.0-1013-raspi2 depends on linux-raspi2-headers-5.3.0-1013; however:
  Package linux-raspi2-headers-5.3.0-1013 is not installed.
sudo apt --fix-broken install
The following packages will be REMOVED:
  linux-headers-5.3.0-1013-raspi2

sudo reboot
sudo apt-get install mesa-utils

glxinfo -B

name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Broadcom (0x14e4)
    Device: V3D 4.2 (0xffffffff)
    Version: 19.2.1
    Accelerated: yes
    Video memory: 3791MB
    Unified memory: yes
    Preferred profile: compat (0x2)
    Max core profile version: 0.0
    Max compat profile version: 2.1
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.0
OpenGL vendor string: Broadcom
OpenGL renderer string: V3D 4.2
OpenGL version string: 2.1 Mesa 19.2.1
OpenGL shading language version string: 1.20

OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.2.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

glxgears

Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
348 frames in 5.0 seconds = 69.440 FPS
247 frames in 5.0 seconds = 49.358 FPS
301 frames in 5.0 seconds = 60.029 FPS
301 frames in 5.0 seconds = 60.019 FPS
300 frames in 5.0 seconds = 59.999 FPS
300 frames in 5.0 seconds = 59.992 FPS
256 frames in 5.0 seconds = 51.041 FPS
300 frames in 5.0 seconds = 59.989 FPS
301 frames in 5.0 seconds = 60.011 FPS
X connection to :0 broken (explicit kill or server shutdown).

Eventually screen starts to flicker then blanks...
built and installed latest mesa - no change

sudo nano /etc/apt/sources.list (commented in all sources)
sudo apt update
sudo apt-get build-dep mesa

mkdir git
cd git
sudo apt-get build-dep mesa
sudo apt-get install -y pkg-config bison flex

git clone https://gitlab.freedesktop.org/mesa/drm.git
cd drm
meson build --prefix=/usr --libdir=/usr/lib/aarch64-linux-gnu
ninja -C build
sudo...

[Hui Wang (hui.wang)]

On 2019/11/29 下午11:15, Mark Dunn wrote:
> short version:
>
> With raspberry pi 4:
> your binaries applied (https://people.canonical.com/~hwang4/v3d-fix/)
> The screen flickers then blanks
> I installed an built the latest mesa
> The screen flickers then blanks
> Back to the raspberry pi kernel (4.19)
> Which still works...
>
> long version:
>
> downloaded ubuntu-19.10-preinstalled-server-arm64+raspi3.img and
> restored it to sdcard
>
> sudo apt update
> sudo apt upgrade
> sudo apt install ubuntu-desktop
>
> wget https://people.canonical.com/~hwang4/v3d-fix/linux-buildinfo-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
> wget https://people.canonical.com/~hwang4/v3d-fix/linux-headers-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
> wget https://people.canonical.com/~hwang4/v3d-fix/linux-image-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
> wget https://people.canonical.com/~hwang4/v3d-fix/linux-modules-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
>
> sudo dpkg -i linux-modules-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
> sudo dpkg -i linux-image-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
> sudo dpkg -i linux-buildinfo-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
>
> sudo dpkg -i linux-headers-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb
> linux-headers-5.3.0-1013-raspi2 depends on linux-raspi2-headers-5.3.0-1013; however:
> Package linux-raspi2-headers-5.3.0-1013 is not installed.
> sudo apt --fix-broken install
> The following packages will be REMOVED:
> linux-headers-5.3.0-1013-raspi2
>
> sudo reboot
> sudo apt-get install mesa-utils
>
> glxinfo -B
>
> name of display: :0
> display: :0 screen: 0
> direct rendering: Yes
> Extended renderer info (GLX_MESA_query_renderer):
> Vendor: Broadcom (0x14e4)
> Device: V3D 4.2 (0xffffffff)
> Version: 19.2.1
> Accelerated: yes
> Video memory: 3791MB
> Unified memory: yes
> Preferred profile: compat (0x2)
> Max core profile version: 0.0
> Max compat profile version: 2.1
> Max GLES1 profile version: 1.1
> Max GLES[23] profile version: 3.0
> OpenGL vendor string: Broadcom
> OpenGL renderer string: V3D 4.2
> OpenGL version string: 2.1 Mesa 19.2.1
> OpenGL shading language version string: 1.20
>
> OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.2.1
> OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
>
> glxgears
>
> Running synchronized to the vertical refresh. The framerate should be
> approximately the same as the monitor refresh rate.
> 348 frames in 5.0 seconds = 69.440 FPS
> 247 frames in 5.0 seconds = 49.358 FPS
> 301 frames in 5.0 seconds = 60.029 FPS
> 301 frames in 5.0 seconds = 60.019 FPS
> 300 frames in 5.0 seconds = 59.999 FPS
> 300 frames in 5.0 seconds = 59.992 FPS
> 256 frames in 5.0 seconds = 51.041 FPS
> 300 frames in 5.0 seconds = 59.989 FPS
> 301 frames in 5.0 seconds = 60.011 FPS
> X connection to :0 broken (explicit kill or server shutdown).

Are your sure you booted the system with the v3d-fix kernel? I remember
with that kernel, the glxgears at least could run without crash or
system hang, of course the v3d-fix has some other problems.

So could you please run 'uname -a' to check t...

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-raspi2 - 5.3.0-1014.16

---------------
linux-raspi2 (5.3.0-1014.16) eoan; urgency=medium

  * eoan/linux-raspi2: 5.3.0-1014.16 -proposed tracker (LP: #1854006)

  * Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel (LP: #1853789)
    - [config] raspi2: Revert "UBUNTU: [config] raspi2: CONFIG_DRM_V3D=m"

linux-raspi2 (5.3.0-1013.15) eoan; urgency=medium

  * eoan/linux-raspi2: 5.3.0-1013.15 -proposed tracker (LP: #1852220)

  * Eoan update: 5.3.9 upstream stable release (LP: #1851550)
    - raspi2: [Config] Remove CONFIG_GENERIC_COMPAT_VDSO and
      CONFIG_CROSS_COMPILE_COMPAT_VDSO

  * Eoan update: v5.3.8 upstream stable release (LP: #1850456)
    - raspi2: [Config] CAVIUM_TX2_ERRATUM_219=n

  * IO errors when writing large amounts of data to USB storage in eoan on
    RPI2/3 (armhf kernel) (LP: #1852510)
    - SAUCE: dwc_otg: checking the urb->transfer_buffer too early (#3332)

  * Incorrect raspi2 snapcraft.yaml file (LP: #1851469)
    - [Packaging] raspi2: Fix snapcraft.yaml

  * CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan (LP: #1850876)
    - [config] raspi2: CONFIG_DRM_V3D=m

  [ Ubuntu: 5.3.0-24.26 ]

  * eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
  * Eoan update: 5.3.9 upstream stable release (LP: #1851550)
    - io_uring: fix up O_NONBLOCK handling for sockets
    - dm snapshot: introduce account_start_copy() and account_end_copy()
    - dm snapshot: rework COW throttling to fix deadlock
    - Btrfs: fix inode cache block reserve leak on failure to allocate data space
    - btrfs: qgroup: Always free PREALLOC META reserve in
      btrfs_delalloc_release_extents()
    - iio: adc: meson_saradc: Fix memory allocation order
    - iio: fix center temperature of bmc150-accel-core
    - libsubcmd: Make _FORTIFY_SOURCE defines dependent on the feature
    - perf tests: Avoid raising SEGV using an obvious NULL dereference
    - perf map: Fix overlapped map handling
    - perf script brstackinsn: Fix recovery from LBR/binary mismatch
    - perf jevents: Fix period for Intel fixed counters
    - perf tools: Propagate get_cpuid() error
    - perf annotate: Propagate perf_env__arch() error
    - perf annotate: Fix the signedness of failure returns
    - perf annotate: Propagate the symbol__annotate() error return
    - perf annotate: Fix arch specific ->init() failure errors
    - perf annotate: Return appropriate error code for allocation failures
    - perf annotate: Don't return -1 for error when doing BPF disassembly
    - staging: rtl8188eu: fix null dereference when kzalloc fails
    - RDMA/siw: Fix serialization issue in write_space()
    - RDMA/hfi1: Prevent memory leak in sdma_init
    - RDMA/iw_cxgb4: fix SRQ access from dump_qp()
    - RDMA/iwcm: Fix a lock inversion issue
    - HID: hyperv: Use in-place iterator API in the channel callback
    - kselftest: exclude failed TARGETS from runlist
    - selftests/kselftest/runner.sh: Add 45 second timeout per test
    - nfs: Fix nfsi->nrequests count error on nfs_inode_remove_request
    - arm64: cpufeature: Effectively expose FRINT capability to userspace
    - arm64: Fix incorrect irqflag restore for priority masking fo...

[Mark Dunn (mdunn-home)]

I think the original 1013 had flicker and tearing before the screen went blank
(the os was still functional - ssh worked).

With your image/modules/buildinfo i get:

uname -a
Linux ubuntu 5.3.0-1013-raspi2 #15+v3d SMP Sun Nov 24 13:41:44 CST 2019 aarch64 aarch64 aarch64 GNU/Linux

Enlarging the glxgears window: I see flicker between the glxgears window, the background and terminal window when they overlap instead of just seeing the top one.
It hasn't gone blank ... yet

With pi 4.19 kernel/modules (from https://github.com/raspberrypi/linux) there is no flicker and the screen has never gone blank.

[Hui Wang (hui.wang)]

@Mark Dunn,

Ok, got it, will look for fixes from 4.19 branch.

thx.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-raspi2 - 5.3.0-1014.16

---------------
linux-raspi2 (5.3.0-1014.16) eoan; urgency=medium

  * eoan/linux-raspi2: 5.3.0-1014.16 -proposed tracker (LP: #1854006)

  * Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel (LP: #1853789)
    - [config] raspi2: Revert "UBUNTU: [config] raspi2: CONFIG_DRM_V3D=m"

linux-raspi2 (5.3.0-1013.15) eoan; urgency=medium

  * eoan/linux-raspi2: 5.3.0-1013.15 -proposed tracker (LP: #1852220)

  * Eoan update: 5.3.9 upstream stable release (LP: #1851550)
    - raspi2: [Config] Remove CONFIG_GENERIC_COMPAT_VDSO and
      CONFIG_CROSS_COMPILE_COMPAT_VDSO

  * Eoan update: v5.3.8 upstream stable release (LP: #1850456)
    - raspi2: [Config] CAVIUM_TX2_ERRATUM_219=n

  * IO errors when writing large amounts of data to USB storage in eoan on
    RPI2/3 (armhf kernel) (LP: #1852510)
    - SAUCE: dwc_otg: checking the urb->transfer_buffer too early (#3332)

  * Incorrect raspi2 snapcraft.yaml file (LP: #1851469)
    - [Packaging] raspi2: Fix snapcraft.yaml

  * CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan (LP: #1850876)
    - [config] raspi2: CONFIG_DRM_V3D=m

  [ Ubuntu: 5.3.0-24.26 ]

  * eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
  * Eoan update: 5.3.9 upstream stable release (LP: #1851550)
    - io_uring: fix up O_NONBLOCK handling for sockets
    - dm snapshot: introduce account_start_copy() and account_end_copy()
    - dm snapshot: rework COW throttling to fix deadlock
    - Btrfs: fix inode cache block reserve leak on failure to allocate data space
    - btrfs: qgroup: Always free PREALLOC META reserve in
      btrfs_delalloc_release_extents()
    - iio: adc: meson_saradc: Fix memory allocation order
    - iio: fix center temperature of bmc150-accel-core
    - libsubcmd: Make _FORTIFY_SOURCE defines dependent on the feature
    - perf tests: Avoid raising SEGV using an obvious NULL dereference
    - perf map: Fix overlapped map handling
    - perf script brstackinsn: Fix recovery from LBR/binary mismatch
    - perf jevents: Fix period for Intel fixed counters
    - perf tools: Propagate get_cpuid() error
    - perf annotate: Propagate perf_env__arch() error
    - perf annotate: Fix the signedness of failure returns
    - perf annotate: Propagate the symbol__annotate() error return
    - perf annotate: Fix arch specific ->init() failure errors
    - perf annotate: Return appropriate error code for allocation failures
    - perf annotate: Don't return -1 for error when doing BPF disassembly
    - staging: rtl8188eu: fix null dereference when kzalloc fails
    - RDMA/siw: Fix serialization issue in write_space()
    - RDMA/hfi1: Prevent memory leak in sdma_init
    - RDMA/iw_cxgb4: fix SRQ access from dump_qp()
    - RDMA/iwcm: Fix a lock inversion issue
    - HID: hyperv: Use in-place iterator API in the channel callback
    - kselftest: exclude failed TARGETS from runlist
    - selftests/kselftest/runner.sh: Add 45 second timeout per test
    - nfs: Fix nfsi->nrequests count error on nfs_inode_remove_request
    - arm64: cpufeature: Effectively expose FRINT capability to userspace
    - arm64: Fix incorrect irqflag restore for priority masking fo...

[natrium42 (alexei-karpenko)]

Fix is not released since it was reverted above. Any updates on this?

[Hui Wang (hui.wang)]

The 5.3.y branch doesn't have this fix yet, and looking for fix patches from branch 4.19.y is not easy. If possible, it is helpful if users could file V3D issues against 5.3.y (https://github.com/raspberrypi/linux/issues)

Thx.

[natrium42 (alexei-karpenko)]

You are right, compiling the 4.19.y kernel works and seems to be stable.

[spike speigel (frail-knight)]

Is this covered by https://github.com/raspberrypi/linux/issues/3162 ?

[Mark Dunn (mdunn-home)]

For 6 months I have been using the raspberry pi kernel grafted onto the rest of Ubuntu
to get V3D.

It is a shame that 6 month later this is still not fixed.
If you can supply a recipe for the building the official ubuntu kernel for the pi
I would be willing to try and fix it.

[Ian Steiger (isteiger)]

hello, are there any updates?

[Hui Wang (hui.wang)]

@Ian and anyone affected by this bug,

Now ubuntu focal kernel (5.4.0) for raspi2 is ready, and in that kernel the CONFIG_DRＭ_V3D is enabled by default (in the latest version of rasp2 focal kernel), could you please have a try that 5.4.0 kernel?

[Ian Steiger (isteiger)]

@Hui it doesn't work, the about screen in GNOME Settings lists llvmpipe for graphics, uname -a returns the kernel is 5.4.0-1012-raspi. I will try a new image and maybe then it will work.

[Ian Steiger (isteiger)]

ok i tried on a new install with the proposed updates on, still no luck. is there maybe a dtoverlay i need to enable?

[Hui Wang (hui.wang)]

5.4.0-1012.12 kernel set the CONFIG_DRＭ_V3D=m, so is the v3d.ko loaded into the kernel? Our ubuntu image of raspi is for server, there is no desktop in the image, so if you don't manually install the desktop, I guess the v3d will not be used.

and please track this issue in this bug as well (the 5.4.0 kernel uses #1876862):
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1876862

[Hui Wang (hui.wang)]

I backported some patches from rpi-5.4.y to ubuntu 5.3 kernel, and enabled V3D driver. Please test if it works or not:

https://people.canonical.com/~hwang4/lp1850876/

[Ian Steiger (isteiger)]

ok i tested it. it is still using llvmpipe but i think i found the relevant issue because the driver is there, i checked. issue: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880125

[Hui Wang (hui.wang)]

the clk_raspberrypi is not enabled in the kernel, let me build a new testing kernel to enable it.

[Hui Wang (hui.wang)]

Please test the v2 kernel: https://people.canonical.com/~hwang4/lp1850876/v2/

[Ian Steiger (isteiger)]

still using llvmpipe, if there is any debugging i could do just tell me

[Hui Wang (hui.wang)]

@Ian,

Did you add dtoverlay=vc4-fkms-v3d in the config.txt?

This is the log on my board, looks like there is no error so far:

ubuntu@ubuntu:~$ uname -a
Linux ubuntu 5.3.0-1027-raspi2 #29++v3dv2 SMP Mon Jun 15 22:26:13 CST 2020 aarch64 aarch64 aarch64 GNU/Linux

ubuntu@ubuntu:~$ dmesg | grep drm
[ 3.759090] [drm] Initialized v3d 1.0.0 20180419 for fec00000.v3d on minor 0
[ 3.790362] vc4-drm soc:gpu: bound fe600000.firmwarekms (ops vc4_fkms_ops [vc4])
[ 3.798578] fb0: switching to vc4drmfb from simple
[ 3.809972] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 3.816771] [drm] No driver support for vblank timestamp query.
[ 3.822817] [drm] Setting vblank_disable_immediate to false because get_vblank_timestamp == NULL
[ 3.866028] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 1
[ 3.905537] [drm:vc4_crtc_mode_set_nofb [vc4]] *ERROR* couldn't fill AVI infoframe
[ 4.031664] vc4-drm soc:gpu: fb0: vc4drmfb frame buffer device

ubuntu@ubuntu:~$ lsmod | grep v3d
v3d 73728 0
gpu_sched 40960 1 v3d
drm 516096 5 gpu_sched,drm_kms_helper,v3d,vc4

ubuntu@ubuntu:~$ ls /dev/dri/ -la
total 0
drwxr-xr-x 3 root root 120 Jun 16 12:03 .
drwxr-xr-x 15 root root 18720 Jun 16 12:04 ..
drwxr-xr-x 2 root root 100 Jun 16 12:03 by-path
crw-rw---- 1 root video 226, 0 Jun 16 12:03 card0
crw-rw---- 1 root video 226, 1 Jun 16 12:03 card1
crw-rw---- 1 root render 226, 128 Jun 16 12:03 renderD128

[Ian Steiger (isteiger)]

ok after adding that line to the config.txt it works, but GNOME is glitching with multiple windows open, thats another issue though.

[Hui Wang (hui.wang)]

I just installed the ubuntu-desktop, and run glxinfo -B, it indicates the v3d is used, and run glxgears, it could run without any crash, looks like the v3d driver is more stable than before.

And I already backported all v3d patches from rpi-5.4.x to ubuntu 5.3 kernel. I have no idea how to fix the issue of glitching with multiple windows open.

BTW, how to check if the render links to llvmpipe or not?

[Ian Steiger (isteiger)]

i dont have an idea, all i did to check was glxinfo | grep renderer

[Ian Steiger (isteiger)]

window glitching does not happen in XFCE, seems like a GNOME problem

[Hui Wang (hui.wang)]

OK, if there is no other problems, I will submit the SRU to ubuntu kernel to enable the V3D driver.

thx.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-raspi2 - 5.3.0-1030.32

---------------
linux-raspi2 (5.3.0-1030.32) eoan; urgency=medium

  * eoan/linux-raspi2: 5.3.0-1030.32 -proposed tracker (LP: #1887072)

  [ Ubuntu: 5.3.0-64.58 ]

  * eoan/linux: 5.3.0-64.58 -proposed tracker (LP: #1887088)
  * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
    - SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups"

linux-raspi2 (5.3.0-1029.31) eoan; urgency=medium

  * eoan/linux-raspi2: 5.3.0-1029.31 -proposed tracker (LP: #1885478)

  * CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan (LP: #1850876)
    - media: bcm2835-unicam: Add support for raw14 formats
    - media: bcm2835-unicam: Rework to not cache the list of active fmts
    - media: bcm2835-unicam: Support unpacking CSI format to 16bpp
    - media: bcm2835-unicam: Add support for luma/greyscale formats
    - drm/vc4: Add support for YUV color encodings and ranges
    - drm/vc4: Add support for H & V flips
    - drm/vc4: Correct handling of rotation parameter in fkms
    - configs: Add CONFIG_WIZNET_W5100=m and _SPI=m
    - overlays: Add w5500 overlay
    - bcm2711: Retain support for old dtbs
    - media: bcm2835-unicam: Replace hard coded loop limit with a define
    - media: bcm2835-unicam: Fix one-to-many mapping for YUYV formats
    - dt-bindings: Add binding for the Infineon IRS1125 sensor
    - media: i2c: Add a driver for the Infineon IRS1125 depth sensor
    - configs: Add CONFIG_VIDEO_IRS1125 to the defconfigs
    - dtoverlays: Add an overlay for the Infineon IRS1125
    - rpi-wm8804-soundcard: Fixed MCLKDIV for Allo Digione
    - dts: bcm2838: Disable DWC OTG block by default
    - staging:bcm2835-codec: Add support for ENUM_FRAMESIZES
    - staging: bcm2835-codec: Correct buffer type check on G_PARM
    - staging: bcm2835-codec: Set default and error check timeperframe
    - staging: bcm2835-codec: Fix imbalance in dma_buf_get/dma_buf_put
    - drm:vc4 Added calls for firmware display blank/unblank
    - configs: Add CGROUP_BPF and BPF_SYSCALL
    - drm/v3d: Don't clear MMU control bits on exception
    - v3d_drv: Handle missing clock more gracefully
    - v3d_drv: Allow clock retrieval by name
    - v3d_gem: Kick the clock so firmware knows we are using firmware clock
      interface
    - clk-raspberrypi: Allow cpufreq driver to also adjust gpu clocks
    - clk-raspberrypi: Also support v3d clock
    - clk-bcm2835: Disable v3d clock
    - config: Switch to upstream cpufreq driver
    - raspberrypi-cpufreq: Only report integer pll divisor frequencies
    - drm/v3d: drop use of drmP.h
    - drm/v3d: Suppress all but the first MMU error
    - drm/v3d: Plug dma_fence leak
    - drm/v3d: Set dma_mask as well as coherent_dma_mask
    - drm/v3d: Replace wait_for macros to remove use of msleep (#3510)
    - Revert "UBUNTU: [config] raspi2: Revert "UBUNTU: [config] raspi2:
      CONFIG_DRM_V3D=m""
    - [Config]: CLK_RASPBERRYPI=y
    - [Config]: CONFIG_ARM_RASPBERRYPI_CPUFREQ=m
    - [Config]: CONFIG_VIDEO_IRS1125=n

  [ Ubuntu: 5.3.0-63.57 ]

  * eoan/linux: 5.3.0-63.57 -proposed tracker (LP: #1885495)
  * seccomp_bpf fails on powerpc (LP: #1885757...