Screen artifacting

shadow_rider

New Member
Joined
Oct 23, 2024
Messages
2
Reaction score
0
Credits
22
I'm running Kali-rolling 2024.3 (6.10.11-amd64) on an Intel Core i7-9750H with GTX 1660Ti.
I started experiencing screen artifacting a while back, and thought it had to do with the resolution. I changed the resolution to a lower one and refresh rate, then changed it back, and the issue resolved. However, after some time the issue came back, and would randomly clear itself for less than an hour, then go back to artifacting. I read online that it had to do with the GPU drivers, so I installed the Nvidia drivers using the steps on the Kali forum. The issue still persisted, and I eventually decided to clean install Kali. The issue still persists, even in the BIOS.
attached is my lscpi output and images of the artifacting
lspci.pngartifact1.jpgartifact1.jpg
 

Attachments

  • artifact.jpg
    artifact.jpg
    107.7 KB · Views: 100
Last edited:


It looks like a compositor problem to me
Open Windows Task Manager Tweaks and click on the Compositor Tab and uncheck "Enable display compositing"
now we need to install Compton which is an independent compositor
sudo apt install compton
Now Open Session and Startup
Go to Application Autostart tab
now add this command
/usr/bin/compton --backend glx --paint-on-overlay --vsync opengl-swc
Now save reboot - You can always undo this if it does not work

1.png
 
It looks like a compositor problem to me
Open Windows Task Manager Tweaks and click on the Compositor Tab and uncheck "Enable display compositing"
now we need to install Compton which is an independent compositor

Now Open Session and Startup
Go to Application Autostart tab
now add this command

Now save reboot - You can always undo this if it does not work

View attachment 22578
It doesn't work and when i try to run the command or compton in terminal it outputs 'PCRE regular expression support not compiled in.'.
 
This is the issue:
The issue still persists, even in the BIOS.
If it is happening before the OS has started, that has zero to do with OS drivers. I'm presuming you're on a laptop based on the outputs. So either your GPU is cooked or your display. I'll go out on a limb and say display because what I'm seeing looks a lot like a trashed display. However, the best way to rule it out is to see if the issue persists while connected to an external monitor. If your laptop screen fails but the external is fine, then you know for sure. If both fail, well you're up shite creek with a laptop. Let us know what happens.

PS: You're not running the nvidia driver, you're on nouveau...
I read online that it had to do with the GPU drivers, so I installed the Nvidia drivers using the steps on the Kali forum.
According to your picture, your nvidia driver is not installed (you're on nouveau):
View attachment 22575
 
If your laptop screen fails but the external is fine, then you know for sure.

NOTE: You may need to press a button, or a combination of buttons, to tell the laptop that you want to output to an external monitor. This is often an Fn button and may require Fn + Shift + moderator (whatever button it is that you have to push to send video outbound).

The button will often have something that looks like a monitor on it. Some have two monitor icons on them. There's no default standard, I'm afraid. So, this may take some poking and proding until you get it right.

On the other hand, you may need to do nothing of the sort and the device will recognize it and use it without user intervention. It can happen. As mentioned, there's no standard for this. There probably should be, but there isn't (as far as I know).
 
This is the issue:

If it is happening before the OS has started, that has zero to do with OS drivers. I'm presuming you're on a laptop based on the outputs. So either your GPU is cooked or your display. I'll go out on a limb and say display because what I'm seeing looks a lot like a trashed display. However, the best way to rule it out is to see if the issue persists while connected to an external monitor. If your laptop screen fails but the external is fine, then you know for sure. If both fail, well you're up shite creek with a laptop. Let us know what happens.

PS: You're not running the nvidia driver, you're on nouveau...

According to your picture, your nvidia driver is not installed (you're on nouveau):
View attachment 22575
But the nouveau drivers does support his GTX 1660 Ti -https://nouveau.freedesktop.org/CodeNames.html#NV190
I missed that little bit about the BIOS but his terminal image is just fine
I believe the terminal does not use graphics drivers or the compositor - I might be wrong about that though
 
@KGIII Pretty much any laptop from the last decade auto detects. Some makes used to have a dedicated Fn toggle to either have both or one or the other. Today most seem to default to both.

@GatorsFan Yeah, nouveau supports most cards, I was just pointing it out coz s/he said s/he installed the nvidia driver.
The actual terminal (as in no graphical session) still uses generic video drivers (technically should not be used interchangeably with the phrase "graphics drivers"). It's just that there are standards, think of it as a single universal generic driver, which every monitor and card are expected to support when it comes to "text mode" (which uses a 2D array to store characters in as opposed to graphics using it to store pixels -- there's more to it, but let's keep simple -- which is why the MSHERC driver would've allowed Childhood Me's Hercules Monochrome Monitor to bloody draw graphics had I had access to it) and basic video modes like VGA and SVGA, the former being supported by 99%* of things, the latter about 90%*.

*Totally rough guestimate.
 


Members online


Top