antiX & i915 – how to achieve better performance

Forum › Forums › New users › New Users and General Questions › antiX & i915 – how to achieve better performance

  • This topic has 24 replies, 5 voices, and was last updated Nov 24-7:43 am by c0pA.
Viewing 15 posts - 1 through 15 (of 25 total)
  • Author
    Posts
  • #188883
    c0pA
    Member

      Hello.

      $ inxi -Gxxx
      Graphics:
        Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx
          Integrated Graphics vendor: Lenovo driver: i915 v: kernel arch: Gen-8
          ports: active: DSI-1 empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3
          bus-ID: 00:02.0 chip-ID: 8086:22b0 class-ID: 0300
        Display: server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting
          unloaded: fbdev,vesa dri: swrast gpu: i915 display-ID: :0.0 screens: 1
        Screen-1: 0 s-res: 1280x800 s-dpi: 96 s-size: 338x211mm (13.31x8.31")
          s-diag: 398mm (15.69")
        Monitor-1: DSI-1 res: mode: 800x1280 hz: 60 scale: 62% (1.6) to: 1280x800
          size: N/A modes: 800x1280
        API: EGL v: 1.5 platforms: device: 1 drv: swrast gbm: egl: 1.4
          drv: kms_swrast surfaceless: drv: swrast x11: drv: swrast
          inactive: wayland,device-0
        API: OpenGL v: 4.5 vendor: x.org mesa v: 22.3.6 glx-v: 1.4 es-v: 3.2
          direct-render: yes renderer: llvmpipe (LLVM 15.0.6 128 bits)
          device-ID: ffffffff:ffffffff
        Info: Tools: api: eglinfo,glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr

      I’m getting screen tearing and low performance.

      Any ideas on how to get this old PC to perform better?

      I’ve read up on using Mesa drivers and all that, but honestly, I don’t really get it.

      Any suggestions would be helpful.

      #188925
      Xunzi_23
      Member

        Hi COpa
        You leave potential helpers with far too much guessing

        Please tell us at least antiX version and the Desktop you are using,
        also how much memory your device has. HDD or SSD. Are you using ZRAM
        memory compression.

        And as below is an approximately 2016 device which Kernel are you using.
        “Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx” is braswell, so it’s a Gen 8 IGP

        Guessing: Please check if below is installed
        xserver-xorg intel driver
        libegl1-mesa libgl1-mesa-glx libgl1-mesa-dri

        #188934
        abc-nix
        Member

          dri: swrast

          This means software rendering. For this device, it should say crocus to be able to use hardware acceleration.

          As you say, this is a mesa issue. The list provided by Xunzi is a good start. Crocus should be included in libgl1-mesa-dri.

          There was another topic related to mesa-amber, that may be of interest to you. But I think crocus should work out of the box on your system.

          Corruption has two hands: the Right and the Left. Don't let them squeeze you.

          #188937
          c0pA
          Member

            @Xunzi_23: I’m using antiX 23.2 runit x64 ~ zzz-IceWM

            Memory:
              System RAM: total: 2 GiB available: 1.79 GiB used: 1.5 GiB (83.8%)

            HDD
            Not using zram
            Kernel 6.1.105-antix.1-amd64-smp

            xserver-xorg intel driver
            libegl1-mesa libgl1-mesa-glx libgl1-mesa-dri

            see attachments below please.

            @abc-nix: I actually followed that thread and the local repository instructions, but I ended up breaking my antiX installation. I guess that’s beyond my skill level.

            #188954
            abc-nix
            Member

              @abc-nix: I actually followed that thread and the local repository instructions, but I ended up breaking my antiX installation. I guess that’s beyond my skill level.

              You can always revert the changes by disabling the local repo (or removing the /etc/apt/sources.list.d/local.list file), and in console

              sudo apt update && sudo apt purge libegl-amber0 libglx-amber0

              and it should automatically reinstall the other mesa packages from Debian repos.

              If that doesn’t work, I will simulate it and give you proper tested steps.

              Corruption has two hands: the Right and the Left. Don't let them squeeze you.

              #188959
              c0pA
              Member

                @abc-nix: I’ve followed these instructions until step 6. On step 7 I followed your instructions mentioned here and ran sudo update-debs.sh which displays the following:

                $ sudo update-debs.sh
                dpkg-scanpackages: warning: Packages in archive but missing from override file:
                dpkg-scanpackages: warning:   libd3dadapter9-mesa libd3dadapter9-mesa-dev libegl-amber0 libegl-mesa0 libegl1-mesa libegl1-mesa-dev libgbm-dev libgbm1 libgl1-amber-dri libgl1-mesa-dev libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libgles2-mesa libgles2-mesa-dev libglx-amber0 libglx-mesa0 libosmesa6 libosmesa6-dev libwayland-egl1-mesa libxatracker-dev libxatracker2 mesa-common-dev mesa-opencl-icd mesa-va-drivers mesa-vdpau-drivers mesa-vulkan-drivers
                dpkg-scanpackages: info: Wrote 27 entries to output Packages file.
                
                #188962
                abc-nix
                Member

                  The warnings are OK. If you are at this step, then you haven’t installed yet, or am I missing something? I became worried when I read:

                  @abc-nix: I actually followed that thread and the local repository instructions, but I ended up breaking my antiX installation.

                  So I assumed the packages got installed and broke something. Did the mesa-amber package install and leave apt not able to update or did the graphical interface stop working after the installation?

                  Corruption has two hands: the Right and the Left. Don't let them squeeze you.

                  #188963
                  c0pA
                  Member

                    I’m going through the steps again. As I said before, I broke my antiX installation while following those instructions and had to reinstall. I’m open to giving it another shot, though.

                    When I saw those warnings, I thought maybe they had something to do with them.

                    So, after that, it should be OK to run:

                    sudo apt update
                    sudo apt upgrade
                    sudo apt install libegl-amber0 libglx-amber0 

                    ?

                    #188966
                    abc-nix
                    Member

                      As I said before, I broke my antiX installation while following those instructions

                      If you can explain a bit what broke, then I can decide if proceeding is worth it or not. If breaking means that it no longer boots to a graphical environment, then don’t continue. If it means apt dependency issues, then I can rebuilt the packages for your exact system. If you can share the
                      inxi -Saz

                      I will build for the correct antiX version and architecture. I assume this is antiX 23, but not sure if it is 32 or 64-bit system.

                      Corruption has two hands: the Right and the Left. Don't let them squeeze you.

                      #188973
                      c0pA
                      Member

                        I’m not sure what caused it, but essential system packages were removed and the computer was unable to boot. I only realized this after typing “yes” into the terminal, and it was too late.

                        It said something about dependencies, so I tried to manually install them. I guess that’s what caused it.

                        $  inxi -Saz
                        System:
                          Kernel: 6.1.105-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc
                            v: 12.2.0 clocksource: tsc avail: acpi_pm
                            parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.105-antix.1-amd64-smp
                            root=UUID=5826775b-f19d-4917-904e-f44cbb87e919 ro quiet splash selinux=0
                          Desktop: IceWM v: 3.9.0 tools: avail: slock,xlock dm: slimski v: 1.5.0
                            Distro: antiX-23.2-runit_x64-full Arditi del Popolo 5 October 2024
                            base: Debian GNU/Linux 12 (bookworm)
                        

                        Yes, antiX 23.2 runit x64.

                        #188976
                        abc-nix
                        Member

                          Thanks. In the original thread I was linking to the 32-bits version of the packages. I wrongly assumed it was also your case.

                          I have rebuilt them now for 64-bits so they can work on your machine. The same as before, I have separated them into two online folders:
                          – folder for mesa-no-i915 (bookworm 64-bits)
                          – folder for mesa-amber (bookworm 64-bits)

                          Remove all .deb packages from the local repo folder you previously created and add these instead. Then run the update-debs.sh script again, sudo apt update.

                          You can do a simulated installation using the -s option before doing it for real.
                          apt install -s libegl-amber0 libglx-amber0
                          If you still see dependency issues, then don’t install. I will then test on a virtual system to see what I did wrong when building the packages.

                          Corruption has two hands: the Right and the Left. Don't let them squeeze you.

                          #188980
                          Brian Masinick
                          Moderator

                            I’ll say this @c0pa and @abc-nix you have a well organized strategy for figuring this out. Process of elimination is sometimes necessary; try what your best guess is first, then eliminate the possibilities until you arrive at the right conclusion; I think you’re close already. I don’t have a “crystal ball” answer on this one, so I think @abc-nix is your “man” for this situation.

                            --
                            Brian Masinick
                            Alternate "Search B":
                            This search page

                            #188983
                            c0pA
                            Member

                              so I think @abc-nix is your “man” for this situation.

                              For sure.

                              First of all, thanks a lot for your help @abc-nix!

                              I downloaded those and replaced them in the debs folder. Did “sudo update-debs.sh” and got the same warnings as above:

                              $ sudo update-debs.sh
                              dpkg-scanpackages: warning: Packages in archive but missing from override file:
                              dpkg-scanpackages: warning:   libd3dadapter9-mesa libd3dadapter9-mesa-dev libegl-amber0 libegl-mesa0 libegl1-mesa libegl1-mesa-dev libgbm-dev libgbm1 libgl1-amber-dri libgl1-mesa-dev libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libgles2-mesa libgles2-mesa-dev libglx-amber0 libglx-mesa0 libosmesa6 libosmesa6-dev libwayland-egl1-mesa libxatracker-dev libxatracker2 mesa-common-dev mesa-opencl-icd mesa-va-drivers mesa-vdpau-drivers mesa-vulkan-drivers
                              dpkg-scanpackages: info: Wrote 27 entries to output Packages file.

                              Proceeded with “sudo apt update” and it told me 9 packages were available to upgrade. Did “sudo apt upgrade” and installed them.
                              Tested with ” apt install -s libegl-amber0 libglx-amber0″ and no errors or dependencies this time, so proceeded with the installation without the -s

                              Rebooted and i think it installed fine this time.

                              $ inxi -Ga
                              Graphics:
                                Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx
                                  Integrated Graphics vendor: Lenovo driver: i915 v: kernel arch: Gen-8
                                  process: Intel 14nm built: 2014-15 ports: active: DSI-1 empty: DP-1,
                                  DP-2, DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3 bus-ID: 00:02.0
                                  chip-ID: 8086:22b0 class-ID: 0300
                                Display: server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting
                                  unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
                                Screen-1: 0 s-res: 1280x800 s-dpi: 96 s-size: 338x211mm (13.31x8.31")
                                  s-diag: 398mm (15.69")
                                Monitor-1: DSI-1 res: mode: 800x1280 hz: 60 scale: 62% (1.6) to: 1280x800
                                  size: N/A modes: 800x1280
                                API: EGL v: 1.5 hw: drv: intel crocus drv: intel i965 platforms: device: 0
                                  egl: 1.4 drv: i965 device: 1 drv: swrast device: 2 drv: crocus device: 3
                                  drv: swrast gbm: drv: crocus surfaceless: egl: 1.4 drv: i965 x11: egl: 1.4
                                  drv: i965 inactive: wayland
                                API: OpenGL v: 4.6 vendor: intel mesa v: 22.3.6 glx-v: 1.4 es-v: 3.2
                                  direct-render: yes renderer: Mesa Intel HD Graphics (CHV)
                                  device-ID: 8086:22b0 memory: 1.46 GiB unified: yes
                                Info: Tools: api: eglinfo,glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr
                              

                              Is there anything else that needs to be done?

                              #188984
                              abc-nix
                              Member

                                Great. Now you need to test if video performance is better or the same. At least crocus is working, based on the terminal output, so that is good.

                                dri: crocus

                                EDIT: screen tearing may be a bit of an issue, even with hardware acceleration. Try enabling the compositor included in antiX (I think it can be enabled in the control centre). It that doesn’t work well, then creating an xorg configuration file for the screen to force the “TearFree” mode.

                                EDIT2: See this post: Test: X video drivers, screen tearing, and power consumption
                                It is a very interesting read on performance and screen tearing.

                                • This reply was modified 11 months ago by abc-nix.
                                • This reply was modified 11 months ago by abc-nix.

                                Corruption has two hands: the Right and the Left. Don't let them squeeze you.

                                #188987
                                c0pA
                                Member

                                  Honestly, the performance feels about the same, even with the compositor turned on. I’m still experiencing screen tearing, too.

                                  I guess I’ll need to use the TearFree option. As you pointed out in that thread, it seems to be the best option.

                                Viewing 15 posts - 1 through 15 (of 25 total)
                                • You must be logged in to reply to this topic.