Thanks, Felix! Yours and Peter's comments gave me a new path for investigation. I logged into Gnome using X11, rather than Wayland, and now I'm using the intel driver: > inxi -Gxx Graphics: Device-1: Intel UHD Graphics 620 vendor: CLEVO/KAPOK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Device-2: Chicony Chicony USB2.0 Camera type: USB driver: uvcvideo bus ID: 1-7:3 chip ID: 04f2:b649 Display: x11 server: X.Org 1.20.8 compositor: gnome-shell driver: intel unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz s-dpi: 96 OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 20.1.4 compat-v: 3.0 direct render: Yes So it seems that Wayland doesn't use the intel DDX if it's installed, but X11 does. I'll run like this for a while to see how it goes. If it goes OK, I'll switch back to the modesetting DDX but stay with X11 to see if its the DDX or Wayland. Specific comments below. David On 7/31/20 6:53 AM, Felix Miata wrote:
You did run inxi to generate this after a full X restart, right?
Yes. I checked again just before switching from Wayland to X11, and it showed the same thing.
If so, then there may be a configuration file specifying use of the modesetting driver, or /etc/X11/xorg_pci_ids/modesetting_ids is more than 2 bytes and specifying an override. Does /etc/X11/xorg.conf.d/50-device.conf exist and contain uncommented lines, including one that specifies modesetting as device? If not, is there some other file specifying modesetting? If not, maybe you should susepaste /var/log/Xorg.0.log for us to examine.
None of these three files exist on my system. I have to admit it'd be nice to know where Xorg.0.log is; I'm running the 20200729 Tumbleweed snapshot and have always been staying pretty current.