[Kernel-packages] [Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Fix Committed Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
Yes, the Gentoo image is running 4.19.67. Thanks, I can wait for a more stable version. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Fix Committed Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
@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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Fix Committed Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
