Some people ? Strange i am the only one replied to ur problem...but still I can't see the tearing in video no 2....have you tried the solution from the given link ? ....does it solve your issue ?

    I can see some tearing in that video, but I have no solution to offer ^^

      viyoriya Not at all. Because that problem is not only ON firefox. But on the telegram Solus app too and surely on another.

      And the tearing when I scroll looks like this :

      I showed it to a Debian user friend who is sysadmin in a company. He can't help me anymore because we tried so much things and nothing worked. Overmore, he is not a Solus dev, neither a Solus user and he doesn't know how the volunteers configured the Solus kernel.

          The same problems over here. And there was another thing : in some website FF does not do what you want. So today for many years I moved from FF to Chrome...............End of the story : all problems solved.

            evert in some website FF does not do what you want

            Like?

              Ok, so, I tried another thing.

              On the/etc/X11/xorg.conf.d/20-intel.conf file, I deleted Tearfree, I replaced it by AccelMethod uxa AND… The tearing at scrolling on Telegram and Firefox just disappeared BUT… The problem is not solved because the tearing on my multimedia content (Vivaldi, Firefox, VLC, Gnome MPV)… Just reappeared.

              As everyone knows, I just cannot put on the file Tearfree and Accelmethod uxa together, because these two options are not compatibles.

              Justin So, are you sure the Intel builds configuration for Solus is right on my CPU ?

              I mean : maybe a bad configuration for the Intel builds in Solus kernel is… What it causes my bug.

              When I was a Linux Mint Cinnamon user, I never had this problem.

              I suppose this is a very specific Solus problem with my very specific SandyBridge CPU…

              Otherwise, thank you so much for trying to help me. If someone knows something, I will be eternally grateful.

                  alan-g59 Which driver were you using on Linux mint? modesetting? xf86-video-intel? I don't know much about your card, but I think Debian (and Debian-based distributions) uses the modesetting driver by default (at least they did it for a while) for 4th generation GPU (and newer). According to the Gentoo's wiki https://wiki.gentoo.org/wiki/Intel , Sandy Bridge is a 6th generation GPU. Maybe this is the difference.

                    Ok. I've tried intel.modeset=0 in the kernel parameters and nothing worked.

                    Do you think I have to remove the KMS ?

                      alan-g59 Well, my point was more about trying to find out what Mint is doing differently than Solus; I was not really trying to suggest that you should try anything, other than finding what driver you were using with Mint ...
                      I don't really know what you are trying to do with the intel.modset=0, and no, I would not mess with any of this.
                      In MY COMPUTER, if I want to use the modesetting driver, I just edit 20-intel.conf file, and replace the driver by modesetting, similar to the config example here https://wiki.gentoo.org/wiki/Intel. However, I don't know if this is the Solus way of doing thing; I just did it as some point for testing purposes.

                          Hothr Well, I rode it. However, I'm sad to announce that /etc/portage/make.conf file in Solus doesn't exist. That's why I can't enable glamour on the /etc/X11/xorg.conf.d/20-modesetting.conf file, wich does exist.

                              alan-g59 The /etc/portage/make.conf is something specific to Gentoo; it doesn't exist in Solus, and doesn't have to. Maybe I was not clear enough in my link (sorry about that), so forget about it. What I wanted to show was simply where in the 20-intel.conf the modesetting argument should be.

                                  Hothr Sorry. I'm not a native english-speaker so sometimes I've got comprehension problems. This is even worst when someone doesn't write but… Speak.

                                  Well, to get it better, I have to ask you the next thing : in the /etc/X11/xorg.conf.d/20-intel.conf file, do I have to replace Driver "intel" by driver "intel" "modesetting" ?

                                  I just get myself lost. Please, help me.

                                      alan-g59 For my computer, I would just put Driver "modesetting" (but keep the Section "Device", Identifier, EndSection), logout and login. But be prudent when playing with drivers ... It can lead to black screen ...

                                          Hothr It could totally work but everything was slower. At scrolling, at minimizing a window, at maximizing a window, etc. Even a new tearing appeared scrolling on Vivaldi browser..

                                          But it was right on Telegram for example.

                                          So I think something is missing in the configuration you proposed me.

                                          I truly believe we can do it but we need patience.

                                              Hothr

                                              Section "Device"
                                              Identifier "Intel Graphics"
                                              Driver "intel"
                                              Option "TearFree" "true"
                                              Option "AccelMethod" "sna"
                                              EndSection

                                              AND

                                              Graphics:
                                              Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
                                              vendor: Micro-Star MSI driver: i915 v: kernel bus ID: 00:02.0
                                              Display: x11 server: X.Org 1.20.5 driver: intel resolution: 1920x1080~60Hz
                                              OpenGL: renderer: Mesa DRI Intel Sandybridge Desktop v: 3.3 Mesa 19.0.6
                                              direct render: Yes

                                                6 days later

                                                Any news ? I still have that problem