If GUP-ineligible pages are passed to a GEM userptr object, -EFAULT is
returned only when the object is actually bound.
The xf86-video-intel userspace driver cannot differentiate this
condition, and marks the GPU as wedged. This disables graphics
acceleration and may cripple other functionalities
If GUP-ineligible pages are passed to a GEM userptr object, -EFAULT is
returned only when the object is actually bound.
The xf86-video-intel userspace driver cannot differentiate this
condition, and marks the GPU as wedged. This disables graphics
acceleration and may cripple other functionalities
If GUP-ineligible pages are passed to a GEM userptr object, -EFAULT is
returned only when the object is actually bound.
The xf86-video-intel userspace driver cannot differentiate this
condition, and marks the GPU as wedged. This disables graphics
acceleration and may cripple other functionalities
When using some Intel integrated graphic cards on Qubes R4.0, screen
glitches may manifest after switching VTs or entering suspend mode.
A known workaround does exist for this bug, which is to add a
configuration file with the following contents within
/etc/X11/xorg.conf.d:
> Section "Device"
>
On 12/23/20 12:59 PM, 'P. Hofmann' via qubes-devel wrote:
> Hi,
>
> after setting up Qubes R4.1 Alpha on a new laptop I found that my old,
> restored Windows Qubes would not work anymore with R4.1, the reason
> being the updated qrexec protocol (from version 2 to 3). During my
> research on the ma
Hi,
after setting up Qubes R4.1 Alpha on a new laptop I found that my old,
restored Windows Qubes would not work anymore with R4.1, the reason
being the updated qrexec protocol (from version 2 to 3). During my
research on the mailing list I stumbled upon the qwt-crossbuild project
by tabit-pr
