GNOME Bugzilla – Bug 794106
Disable wayland when mgag200 graphic card is detected.
Last modified: 2018-05-24 11:47:10 UTC
In our SUSE's SLE 15 beta tseting, we received quite some GNOME issues caused by Wayland + mgag200 combination. Quote: > "SLES 15 Beta 5. The gnome desktop keyboard and mouse on the server is > extremely slow responding with all Lenovo systems I have tried. (The most > recent systems I have tested are ST550 and x3650 M5). This includes several > new purley-based systems and older broadwell/haswell systems as well. All of > these system use Matrox graphics controllers. " > "With sles15 beta4 I am observing both functionality and performance issues on > the HPE ilo graphical console when graphical.target is chosen. Interaction is > very sluggish, mouse very slow to follow physical mouse movement, keyboard is > subject to rapid, repeated keystrokes. For example, I noticed the > sluggishness, opened a terminal window, intending to type "ps" and got > "pppppppps". The first character typed after a pause seems most likely to > repeat. " > "sles 15 beta 5 gnome keyboard and mouse are extremely slow with Matrox > graphics controllers" So it should make sense to disable wayland by now on those chips using similar code path in: bgo#789081 gdm should never try wayland on Cirrus chipset
Created attachment 369373 [details] [review] Patch to disable wayland on runtime.
hmm comment 0 doesn't sounds like a mga specific problem though. some sort of mutter bug? maybe bug 774989 coming back? i think we should fix the bug instead of just cutting out slow hardware that happen to see it more frequently
Hi Ray, Thanks for the tracking on it. While I didn't observe things like bug 774989 in machines, except received similar issues with mgag200 at the moment. So I've been suspecting it's hardware specific. Do you have ideas to gather ad-hoc logs which might be more helpful for debugging from mutter/clutter side? Meanwhile I saw an issue for the keyboard/mouse slow issue is opened in gitlab: https://gitlab.gnome.org/GNOME/mutter/issues/59 Maybe it's better to track the issue there?
For another datapoint, same problem is also reported against ASPEED ast drivers: https://gitlab.gnome.org/GNOME/mutter/issues/106
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/364.