Re: chromium flickering rectangle corruption (with workaround)
Salil <[email protected]>
| Newsgroups | gmane.os.netbsd.current |
|---|---|
| Message-ID | <gw7vLzXjoag-x09VQRR83b_EW0s_YL_dmOAWe2JKhY8HUXoVMQbOidVC0f-teAVTS_uZQn7yRRWvminTgtSA0GJmNCCqu5bvkQLKMP1iAaU=@proton.me> |
On Thursday, January 1st, 2026 at 7:48 AM, David Brownlee <[email protected]> wrote: > > > On Thu, 1 Jan 2026 at 14:14, Robert Bagdan [email protected] wrote: > > > > Further to this - I'm not suggesting --force-gpu-mem-available-mb=128 > > > should necessarily be the default for all builds, but if (say) on > > > NetBSD-11 and later 141+ shows the issue, then it could be defaulted > > > on for just the believed affected platforms > > > > I use the radeon kms driver, and chromium for me works with the > > fallback swiftshader software render. > > I don't know if this issue depends on the drivers or all affected, > > this is why I just added this workaround > > to the README. > > > Could I ask if you had to set anything explicitly in chromium or xorg > settings, or did everything work "Out Of The Box"? > > I'm using the modesetting driver on a T14Gen1 under recent NetBSD-11_BETA > i915drmkms0 at pci0 dev 2 function 0: Intel UHD Graphics (rev. 0x02) > > Would anyone else seeing the issue like to comment on their setup? I like to confirm that I see the same issue, and my setup is similar to yours: i915drmkms0 at pci0 dev 2 function 0: Intel UHD Graphics 620 (GT2) (rev. 0x07) > > Thanks > > David