Bug 1941849 - Corrupted mouse cursor using nouveau on Kepler [GK104]
Summary: Corrupted mouse cursor using nouveau on Kepler [GK104]
Keywords:
Status: CLOSED DUPLICATE of bug 1941291
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 33
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-22 22:05 UTC by Lyosha Alexeev
Modified: 2021-03-22 22:08 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-22 22:08:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Lyosha Alexeev 2021-03-22 22:05:07 UTC
1. Please describe the problem:

After upgrading Fedora 33, pulling in the 5.11.x kernel, the mouse cursor was displayed as a block of offset horizontal lines, rendering it unusable.
The GPU is a Nvidia GeForce 770 (GK104), using nouveau and Wayland.


2. What is the Version-Release number of the kernel:

kernel-5.11.7-200.fc33.x86_64


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?

It works flawlessly on 5.10.23-200.fc33.x86_64 and first appeared on kernel-5.11.3-50.fc33.x86_64 iirc, downgrading works just fine.


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Install any kernel from the 5.11 tree.


5. Does this problem occur with the latest Rawhide kernel?

Yes. But applying https://lists.x.org/archives/nouveau/2021-March/038260.html as stated here https://gitlab.freedesktop.org/drm/nouveau/-/issues/55 fixes the issue.


6. Are you running any modules that not shipped with directly Fedora's kernel?:

No.


7. Please attach the kernel logs.

There seems nothing worth attaching in there.

Comment 1 Hans de Goede 2021-03-22 22:08:41 UTC
Known issue, a fix is on its way (this should be fixed in the first Fedora kernel released after the current 5.11.8 one). As a workaround you can stick with a 5.10 kernel for now.

*** This bug has been marked as a duplicate of bug 1941291 ***


Note You need to log in before you can comment on or make changes to this bug.