Weird graphics issue

[0ne_Up]

This often happens after opening my laptop cover (or returning from suspend):



As soon as I try to use that window everything returns to normal. I took this picture using my phone, when I take a screenshot everything looks normal.

Code: Select all

inxi -Fxxxrz
System:    Kernel: 5.4.0-81-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 5.0.5 wm: muffin 5.0.1 
           dm: LightDM 1.30.0 Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal 
Machine:   Type: Laptop System: ASUSTeK product: VivoBook_ASUSLaptop X571GD_X571GD v: 1.0 serial: <filter> 
           Mobo: ASUSTeK model: X571GD v: 1.0 serial: <filter> UEFI: American Megatrends v: X571GD.308 date: 05/20/2020 
Battery:   ID-1: BAT1 charge: 31.6 Wh condition: 33.7/42.3 Wh (80%) volts: 4.0/11.6 model: ASUS A32-K55 type: Li-ion 
           serial: <filter> status: Charging 
CPU:       Topology: Quad Core model: Intel Core i5-8300H bits: 64 type: MT MCP arch: Kaby Lake rev: A L2 cache: 8192 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 36799 
           Speed: 800 MHz min/max: 800/4000 MHz Core speeds (MHz): 1: 800 2: 801 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 
Graphics:  Device-1: Intel UHD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3e9b 
           Device-2: NVIDIA GP107M [GeForce GTX 1050 Mobile] vendor: ASUSTeK driver: nvidia v: 460.91.03 bus ID: 01:00.0 
           chip ID: 10de:1c92 
           Display: x11 server: X.Org 1.20.11 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 1050/PCIe/SSE2 v: 4.6.0 NVIDIA 460.91.03 direct render: Yes 
Audio:     Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           chip ID: 8086:a348 
           Sound Server: ALSA v: k5.4.0-81-generic 
Network:   Device-1: Intel Wireless-AC 9560 [Jefferson Peak] driver: iwlwifi v: kernel port: 5000 bus ID: 00:14.3 
           chip ID: 8086:a370 
           IF: wlo1 state: up mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel port: 3000 
           bus ID: 03:00.0 chip ID: 10ec:8168 
           IF: enp3s0 state: down mac: <filter> 
Drives:    Local Storage: total: 476.94 GiB used: 206.31 GiB (43.3%) 
           ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKNW512G8 size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> 
           rev: 002C scheme: GPT 
RAID:      Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 port: 5060 bus ID: 00:17.0 
           chip ID: 8086.282a rev: 10 
Partition: ID-1: / size: 460.85 GiB used: 206.31 GiB (44.8%) fs: ext4 dev: /dev/nvme0n1p3 
           ID-2: swap-1 size: 7.63 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p2 
Sensors:   System Temperatures: cpu: 47.0 C mobo: 27.8 C gpu: nvidia temp: 41 C 
           Fan Speeds (RPM): cpu: 0 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 
           1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/microsoft-prod.list 
           1: deb [arch=amd64,arm64,armhf] https://packages.microsoft.com/debian/10/prod buster main
           Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
           1: deb http://packages.linuxmint.com uma main upstream import backport #id:linuxmint_main
           2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
           3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
           4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
           5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
           6: deb http://archive.canonical.com/ubuntu/ focal partner
           Active apt repos in: /etc/apt/sources.list.d/teams.list 
           1: deb [arch=amd64] https://packages.microsoft.com/repos/ms-teams stable main
           Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
           1: deb https://linux.teamviewer.com/deb stable main
           Active apt repos in: /etc/apt/sources.list.d/vscode.list 
           1: deb [arch=amd64,arm64,armhf] http://packages.microsoft.com/repos/code stable main
Info:      Processes: 289 Uptime: 2d 23h 02m Memory: 7.63 GiB used: 2.08 GiB (27.2%) Init: systemd v: 245 runlevel: 5 
           Compilers: gcc: 9.3.0 alt: 9 Shell: bash v: 5.0.17 running in: gnome-terminal inxi: 3.0.38

[SMG]

I took this picture using my phone, when I take a screenshot everything looks normal.

That is usually an indication the issue is hardware related.

Returning from suspend is often times related to acpi settings. It's possible something in the hardware was not fully wakened at the time you saw this and moving the mouse gave it the full "wake up" call.

A number of people with 8th-gen Intel processors have found a newer kernel than the 5.4 is a better match for their hardware. The 5.11 kernel is available in Update Manager if you would like to give it a try. Let us know if you need/want directions on how to install it.

[0ne_Up]

Thanks. I thought it may have something to do with the graphics drivers.

A number of people with 8th-gen Intel processors have found a newer kernel than the 5.4 is a better match for their hardware. The 5.11 kernel is available in Update Manager if you would like to give it a try. Let us know if you need/want directions on how to install it.

I always install the latest kernel updates, I don't know how to install another version.

[SMG]

I always install the latest kernel updates, I don't know how to install another version.

Installing a newer kernel will install a newer i915 Intel driver, so if the driver is the issue then this will give you a newer one. (Often, Intel drives the graphics on a laptop, but I do not know if that is true for your laptop.)

Open Update Manager. Select View > Linux Kernels and click Continue. Make sure 5.11 is selected on the left panel and then click the top-most option on the right panel. An "Install" button will appear. Install the kernel and then reboot for it to become active.

If, for some reason, you want to go back to the 5.4 kernel, boot into grub, select the Advanced Options, and select a 5.4 kernel. You would then want to go into Update Manager to remove the 5.11 kernel as the system automatically boots to the highest number installed kernel.

[0ne_Up]

Thanks! I just installed the 5.11.0-27 kernel, I will see...

Update manager often installs kernel updates. Why doesn't this install the latest kernel?

[SMG]

Update manager often installs kernel updates. Why doesn't this install the latest kernel?

The LTS (long-term support) kernel for Mint 20 is the 5.4 kernel. Other kernels are for newer hardware and are supported for a much shorter time. They are not part of "standard" Mint and thus are available, but not required.

The instructions I gave you were to upgrade the kernel to a newer version. You went from 5.4.0-xx to 5.11.0-xx. When the 5.11 kernel goes end of life in February 2022, there will be a higher number version to replace it.

What you have seen in the past in Update Manager is an update to your existing kernel. Going from 5.4.0-75 to 5.4.0-76 is an update.

[0ne_Up]

Another strange issue, which does show up on a screenshot:



As you can see the title bar is larger than the browser window. Resizing the window "solves" the problem and everything returns to normal.

[SMG]

As you can see the title bar is larger than the browser window. Resizing the window "solves" the problem and everything returns to normal.

This is another issue which only happens when returning from suspend?

It is possible newer drivers, either Nvidia or Intel from the kernel, may help with these issues.

[0ne_Up]

This is another issue which only happens when returning from suspend?

Yes, but something tells me it's the same problem

It is possible newer drivers, either Nvidia or Intel from the kernel, may help with these issues.

I don't know why it was using "nvidia-driver-460" but I changed this to the recommended "nvidia-driver-470".



The NVIDIA drivers are installed but "System Info" says a different graphics card is being used

[0ne_Up]

Even when using the latest kernel or NVIDIA drivers the issues I described still occur. But I just started using the open source nouveau display driver and that actually seemed to have solved the problem.

[SMG]

This is another issue which only happens when returning from suspend?

Yes, but something tells me it's the same problem

If it happens when returning from suspend then, yes, it is probably the same problem. That's why I wanted to know when it was happening. I wanted to make sure it was not a different problem that we should investigate.

I don't know why it was using "nvidia-driver-460" but I changed this to the recommended "nvidia-driver-470".

The NVIDIA drivers are installed but "System Info" says a different graphics card is being used

Your system has two different graphic drivers and you should be able to switch between the two. Just because you have the Nvidia driver files installed does not mean it will automatically be the one running.

You should have an applet in the lower right corner of your screen in the panel that is either an Intel icon or an Nvidia icon. You can use that applet to change which GPU is being used. You would change the setting and then reboot your computer for the change to take effect.

But I just started using the open source nouveau display driver and that actually seemed to have solved the problem.

Please provide the output of inxi -Gx so we can get an idea of what driver and renderer your system is using.

[0ne_Up]

If it happens when returning from suspend then, yes, it is probably the same problem. That's why I wanted to know when it was happening. I wanted to make sure it was not a different problem that we should investigate.

Yes, it both happens when returning from suspend, and I just experienced it right after booting. It always happens when I return to my computer, never while things are running.

Your system has two different graphic drivers and you should be able to switch between the two. Just because you have the Nvidia driver files installed does not mean it will automatically be the one running.

You should have an applet in the lower right corner of your screen in the panel that is either an Intel icon or an Nvidia icon. You can use that applet to change which GPU is being used. You would change the setting and then reboot your computer for the change to take effect.

I do have that applet and I'm using "NVIDIA (Performance Mode)". But "System Info" still says my graphics card is "Intel Corporation UHD Graphics 630 (Mobile) (prog-if 00 [VGA controller])"

But I just started using the open source nouveau display driver and that actually seemed to have solved the problem.

I thought using the nouveau driver solved the problem and it seemed at first but the problem with the title bar just occurred after booting with that driver. The problem I described in my OP hasn't occurred yet...

Please provide the output of inxi -Gx so we can get an idea of what driver and renderer your system is using.

Code: Select all

inxi -Gx
Graphics:  Device-1: Intel UHD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel 
   bus ID: 00:02.0 
   Device-2: NVIDIA GP107M [GeForce GTX 1050 Mobile] vendor: ASUSTeK driver: nouveau 
   v: kernel bus ID: 01:00.0 
   Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
   resolution: 1920x1080~60Hz, 1440x900~60Hz 
   OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 21.0.3 
   direct render: Yes

It's not really such a big deal, as soon as I try to use these windows they return to normal and everything is working fine but I just thought it was interesting and I was curious what other people had to say about this. And if this solves a problem I may be able to contribute by reporting it

[SMG]

I do have that applet and I'm using "NVIDIA (Performance Mode)". But "System Info" still says my graphics card is "Intel Corporation UHD Graphics 630 (Mobile) (prog-if 00 [VGA controller])"

Did you reboot after making changes to the applet?

I thought using the nouveau driver solved the problem and it seemed at first but the problem with the title bar just occurred after booting with that driver. The problem I described in my OP hasn't occurred yet...

My initial thought was the Nvidia driver might be the source of the issue, and it might have been the source of the original problem which has not returned.

But this issue you are now seeing with the extended title bar might be a different issue.

Your inxi output seems to indicate you are rendering with Intel, but maybe both Intel and nouveau are in use. We would need to see the output of the X Server log to know for sure. If you would like me to check, please post the url returned by this command:
cat /var/log/Xorg.0.log | nc termbin.com 9999
This command uploads the X Server log file to termbin.

[0ne_Up]

Did you reboot after making changes to the applet?

I didn't make any changes to the applet, I only used the Driver Manager to start using the nouveau driver instead of the NVIDIA driver and then I rebooted. But System Info says my graphics card is Intel but I have an NVIDIA applet in my system tray which is configured to use the NVIDIA GPU which it was by default.

Your inxi output seems to indicate you are rendering with Intel, but maybe both Intel and nouveau are in use. We would need to see the output of the X Server log to know for sure. If you would like me to check, please post the url returned by this command:
cat /var/log/Xorg.0.log | nc termbin.com 9999
This command uploads the X Server log file to termbin.

https://termbin.com/hodj

I've never heard of termbin, that's actually pretty cool

[SMG]

I've never heard of termbin, that's actually pretty cool

It's a short-term way to share the data. Data is deleted after a month.

As I read the log, it appears both Intel and nouveau are in use which I would interpret to mean your system is running in On-Demand mode. On-Demand mode would mostly use Intel, but switch to nouveau for tasks which might have more demands on the GPU.

Code: Select all

[     7.302] (II) modeset(0): glamor X acceleration enabled on Mesa Intel(R) UHD Graphics 630 (CFL GT2)
[     7.491] (II) modeset(G0): glamor X acceleration enabled on NV137
[     7.595] (II) modeset(0): [DRI2] Setup complete
[     7.595] (II) modeset(0): [DRI2]   DRI driver: iris
[     7.595] (II) modeset(0): [DRI2]   VDPAU driver: va_gl
[     7.603] (II) modeset(G0): [DRI2] Setup complete
[     7.603] (II) modeset(G0): [DRI2]   DRI driver: nouveau
[     7.603] (II) modeset(G0): [DRI2]   VDPAU driver: nouveau

It is my understanding the nvidia-prime-applet would show which driver is in use. Maybe that is why Performance mode is showing? I did not think that was how it was responding in the past, but there have been recent changes to the code for that applet so maybe it changed. I would have thought the mode would show On-Demand.

It is possible that glitch with the extended title bar may be related to the Intel i915 driver. My laptop has Intel and in the past I've noticed issues when turning the screen back on that I would get odd black segments on the screen that went away after moving the pointer a bit. It no longer does that so I assumed fixes were added to the kernel (the Intel driver is in the kernel).