Search Results for 'swap'

Forum Forums Search Search Results for 'swap'

Viewing 15 results - 1,126 through 1,140 (of 1,706 total)
  • Author
    Search Results
  • #40306
    Member
    Xecure

      1. No idea
      2. You could label your boot partition as boot. Maybe that helps.
      You could also update/upgrade your live system before installation (as there is a newer minstaller version available). test things first with the newest version (you should always do that first before reporting).
      3. antiX screenshot delay is only for fullscreen. Window screenshot is always for next window you click on.
      4. Not my experience. Maybe gparted reports more than what is real. Recent install of antiX 19.2 base: 2.68 GBs. I will later try installing antiX full and see how much it takes on my machine.
      5. If I want control of the swap size, I do a custom install and create the partitions I want.
      6. No idea.

      antiX Live system enthusiast.
      General Live Boot Parameters for antiX.

      Anonymous

        Trying to install antiX-19.2-runit_x64-full.iso

        1. My initial intention was having separate

        /tmp
        /var
        /var/log
        /usr

        partitions but antiX Linux Installer will not allow for my wish.

        I thought that the cli-installer might be flexible enough, but it says from the start:

        This installer does NOT offer encryption

        Is there a way to fulfill partition separation?

        If I install antiX without additional partitions, and after installation manually edit /etc/fstab and put directories’ contents via tar(1) or cpio(1) to additional partitions, for example:

        # (cd /var && tar cf - .) | (cd <future-var-temporary-mount> && tar xpf - ) \
        && rm -rf /var \
        && mkdir /var \
        && mount -a   # provided that /ets/fstab is prepared

        will it work without breaking the system?
        Or am I advised to not tinker arbitrarily, accepting the default install layout?

        2. antiX Linux Installer
        Custom install on existing partitions
        I chose boot location to sda1
        boot location to sda1
        then home location to sda10
        home location to sda10
        boot location dropped to root
        check drop-down list – sda1 is not displayed
        drop-down list - sda1 is not displayed
        change home location to sda9 – sda1 for boot location is available again
        change home location to sda9 - sda1 for boot location is available again
        change home location to sda9 - sda1 for boot location is available again
        change home location to sda9 - sda1 for boot location is available again
        try sda10 for home again – boot drops to root again
        try sda10 for home again - boot drops to root again

        I have played with it and it seems that sda9 and below for home do not affect presence of sda1
        but sda10 and above for home hide sda1 from drop-down menu

        3. bug? in antiXscreenshot:
        want to shoot a drop-down list,
        Region to capture – Window
        set Delay to e.g. 1 (or leave the default 5) counting that it will provide time for drop-down menu to be displayed
        press OK in antiXscreenshot
        press on drop-down list in the target window – screenshot is taken immediately regardless of delay and drop-down menu is not activated

        4. antiX Linux Installer of antiX-19.2-runit_x64-full.iso says:

        Installation requires about 3.5 GB of space. 5 GB or more is preferred.

        But after auto-installation Gparted reported that 7+ GB are used on / partition.
        Send me a screenshot of 7+ GB successfully crammed into 3.5 GB 😉

        5. antiX Linux Installer’s auto-install created a 2 GB swap partition whereas my laptop has 3 GB RAM (2 GB + 1 GB). I would expect swap to be 3+ in my case.

        6. Samba option present in antiX Linux Installer is grey = unactivatable

        Member
        anilkagi

          Hello there,

          I wanted to;

          Boot antiX Frugal-only From HDD Without Any Full-Installed OS – with Extlinux

          as suggested in this thread because I was attracted in this prospect of “booting without already having a linux distribution fully-installed to use the bootloader”.

          I carried out all the steps described here meticulously.

          First I tried in VBox and then on a HD partition. However I was not successful in booting into the frugal-only-install in both.

          I did the following;

          1] Boot into USB live antix-19.2.1-x64-Base > F5 > Frugal_only > Enter to boot.

          2] Menu > Applications -> System -> Gparted > Device -> Create partition table > Select “msdos” > Create new partitions for System and Swap > Right click on System partition > Manage flags > boot > Close Gparted.

          3] In the Root Terminal run the following commands:

          `mkdir /media/sda1
          mount /dev/sda1 /media/sda1
          mkdir /media/sda1/boot
          mkdir /media/sda1/boot/extlinux`

          4] Drag-and-drop-copy in ROXfiler-as-root > “antiX” directory from /live/boot-dev to /media/sda1

          5] In root terminal run the following commands:

          `extlinux –install /media/sda1/boot/extlinux
          dd if=/usr/lib/EXTLINUX/mbr.bin of=/dev/sda bs=440 count=1`

          6] Drag-and-drop-copy in ROXfiler-as-root > cmenu.c32, libcom32.c32, libmenu.c32, libutil.c32, menu.c32, vesamenu.c32. (ldlinux.sys & ldlinux.c32 are already there) from /usr/lib/syslinux/modules/bios to /media/sda1/boot/extlinux

          7] In the Root Terminal run the following command:

          touch /media/sda1/boot/extlinux/extlinux.conf

          8] Drag-and-drop-copy in ROXfiler-as-root > “splash.png” from /usr/share/wallpaper to /media/sda1/boot/extlinux
          (Downloaded it from this page, as I liked it.)

          9] In the Root Terminal run the following command:

          sudo blkid

          Add the UUID from the above returns into extlinux.conf.

          10] Rox-filer > /media/sda1/boot/extlinux/extlinux.conf > Right click > Edit as root > as below;

          UI vesamenu.c32
          TIMEOUT 200
          MENU TITLE antiX Linux frugal installs
          MENU BACKGROUND splash.png
          MENU COLOR border 30;44 #40ffffff #a0000000 std

          LABEL l0
          MENU LABEL antiX 19.2.1 Base, frugal only, zram enabled
          LINUX /antiX/vmlinuz root=UUID=1071a266-a5ce-4cfd-b0b5-2765e54e5f02 bdir=antix-19 buuid=1071a266-a5ce-4cfd-b0b5-2765e54e5f02
          APPEND frugal_only vga=default quiet splasht=va
          INITRD /antiX/initrd.gz

          #LABEL l1
          # MENU LABEL MX Linux 18, static persistence, zram enabled
          # LINUX /MX/vmlinuz root=UUID=1071a266-a5ce-4cfd-b0b5-2765e54e5f02 bdir=MX buuid=1071a266-a5ce-4cfd-b0b5-2765e54e5f02
          # APPEND persist_static vga=default quiet splasht=va
          # INITRD /MX/initrd.gz

          11] Shutdown
          12] Remove USB live
          13] Reboot

          Then I get this error.

          fatal error: device found but could not find antix-19/linuxfs file on device

          I got the errors as shown in the attached images below;

          I repeated this process several times but with no success.

          My guess is the issue may be in performing the step ‘6a’;

          6. Installing the Extlinux bootloader:
          a. We need the following packages, WHICH ARE ALREADY INSTALLED IN ANTIX BY 
          DEFAULT: extlinux, syslinux, syslinux-common. I list these to be complete, 
          in case the installed applications ever change in future antiX releases.

          However, I get the boot-menu and I see “Syslinux” displayed on the screen before that.

          I don’t know what am I doing wrong. Please throw some light on this.

          Thank you & Regards.

          • This reply was modified 2 years, 9 months ago by anilkagi.
          #40131
          Member
          marcelocripe

            Seaken64,

            Unfortunately I will be in debt, I didn’t get as much detailed information as yours. Mine are limited by the command $ free {Enter}, $ htop {Enter}, or some task manager.

            Tiny Core Plus (CorePlus-current.iso or Tiny Core Plus 11.0)

            Before installing to HD:
            Terminal, with the command “free”, total memory 964532 KB of RAM, 89060 KB in use and 797756 KB free.

            After installing on HD:
            Terminal, with the command “free”, total memory 964532 KB, 50988 KB in use and 866016 KB free.

            Programs already installed on Tiny Core Plus 11.0 and 11.1
            Wbar menu: Exit, Editor, ControlPanel, Apps, RunProgram, MountTool, Terminal, eZremaster, Wifi.

            In Tiny Core Plus 11.0 and 11.1 the default Video is xvesa.tcz, Audio by default is not available at ISO, LAN and WiFi network cards are initialized by default at the startup of the operating system.

            Puppy Linux BionicPup 32 (bionicpup32-8.0-uefi.iso)
            Before installing to HD:
            With the “Task Manager”, of the 1607 MB, 126 MB are in use and 5% CPU.

            After installing on HD:
            $ free {Enter}
            Memory: total: 1646012 KB, 76468 KB in use and 1408204 MB free.
            With the Task Manager, of the 1607 MB, 92 MB are in use and 16% CPU.

            SliTaz (slitaz-rolling-core64.iso version 20-05-2020)

            Before installing to HD:
            $ free {Enter}
            XTerm Terminal
            Memory: total: 2088424 KB of RAM, 101276 KB in use and 1701092 KB free

            Sakura Terminal
            Memory: total: 2048424 KB of RAM, 101608 KB in use and 1700716 KB free.

            Task manager LXTask 0.1.9:
            Displays CPU usage between 0% and 2%, memory consumption 93 MB of 2000 MB

            After installing on HD:
            $ free {Enter}
            XTerm Terminal
            Memory: total: 1991712 KB of RAM, 72264 KB in use and 1866784 KB free

            Sakura Terminal
            Memory: total: 1991712 KB of RAM, 72996 KB in use and 1864176 KB free.

            Task manager LXTask 0.1.9:
            Displays CPU usage between 1% and 3%, memory consumption 66 MB of 1945 MB.

            https://www.slax.org/introduction.php

            System requirements for running Slax

            32bit Slax
            Processor: i686 CPU or later, all Intel and AMD processors will work
            Memory: 128 MB of RAM for the desktop, 512 MB of RAM to run the web browser
            Peripherals: To boot from CD or USB or HD drive
            Optionally: network card, sound card

            64bit Slax
            Processor: x86_64 CPU, such as AMD Athlon 64, Opteron, Sempron, Intel Core 2 / i3 / i5 / i7 and others
            Memory: 128 MB of RAM for the desktop, 512 MB of RAM to run the web browser
            Peripherals: To boot from CD or USB or HD drive
            Optionally: network card, sound card

            After installing on HD:

            Slax Linux (slax-64bit-9.11.0.iso):
            Using the free command on the terminal the consumption of RAM was about 134 MB or using the task manager the consumption of RAM was about 155 MB.

            Slax Linux (slax-32bit-9.11.0.iso)
            Using the free command on the terminal the RAM memory consumption was about 97912 KB (97.91 MB) or using the task manager the RAM memory consumption was about 109 MB.

            Void (void-live-x86_64-20191109-lxde.iso)

            -Before installation, running Void Linux via pendrive:
            [anon @ void-live: ~] $ free {Enter}
            Memory: total: 2028996, used: 116344, free: 1306088 KB, shared: 23368, buff / cache: 606564, avaliable: 1743776 (values ​​in KB).

            -After installing Void Linux on the HD:
            Memory: total: 2029456, used: 121328, free: 1727560 KB, shared: 26048, buff / cache: 180568, available: 1741848 (values ​​in KB), Swap: total: 2096476, used: 0, free: 2096476.

            antiX (antiX-19.2_x64-full.iso)

            Before installing to HD:
            Information displayed by Conky before installation: Resolution 1366×768, dpi 96, Automount enable, CPU varying between 2% and 4%, Frequency varying between 800 and 1600, RAM 174M Used / 1.56GB Total (for onboard video – Via VT8237R Plus) or Used 144M RAM / 1.96GB Total (for offboard video – nVidia GeForce MX 4000 Version 4.18.20.36.00 64 MB), Swap 0 / 5GB, Disk (Pendrive) 2.59M / 1.23 GB.

            With Terminal, command demo @ antixl: ~ $ free {Enter}, total memory: 1641436 KB of RAM, 171304 KB in use and 900160 KB free, shared 11502.

            After installing on HD:
            Information displayed by Conky, Resolution 1366×768, dpi 96, Automount enable, CPU varying between 2% and 4%, Frequency varying between 800 and 1600, RAM 172M Used / 1.56GB Total, Swap 0 / 4GB, Disk (HD) 3, 24G / 224 GB.

            Terminal, the command Usuario @ antixl: ~ $ free {Enter}, total memory: 1641436 KB of RAM, 175864 KB are in use and 1230832 KB are free, shared 2092, Swap 4194300.

            I do not know how to disable Conky from antiX startup, I believe it can reduce memory consumption even more. Do you know in which configuration file we can get Conky from? Ideally, Conky would be loaded into memory if the user opened it, instead of being loaded by default.

            antiX Linux (antiX-17.4.1_x64-full.iso)

            Before installing to HD:
            Information displayed by Conky, 1280×1024 resolution, 96 dpi, Automount enable, CPU ranging from 52% to 54%, Frequency ranging from 2528, Used RAM 114M / 1.89GB Total (for onboard video), Swap 0 / 0B, Disk (Pendrive) 1.87M / 1.49 GB.
            Terminal, with the command demo @ antixl: ~ $ free {Enter}, total memory: 1985696 KB of RAM, 113592 KB are in use and 1511040 KB are free, shared 8876, buff / cache 361064 avaliable 1725964.

            After installing on HD:
            Information displayed by Conky, Resolution 1024×768, dpi 96, Automount enable, CPU varying between 51% and 53%, Frequency varying between 2528, 131M RAM Used / 1.96GB Total, Swap 0 / 2GB, Disk (HD) 2,83G / 34.5 GB.
            Terminal, with the command Usuario @ antixl: ~ $ free {Enter}, total memory: 1985708 KB of RAM, 138836 KB are in use and 1681044 KB are free, shared 1712, buff / cache 165828 avaliable 1710044, Swap 2096124.

            antiX Linux (antiX-16.3_x64-full.iso)

            Before installing to HD:
            Information displayed by Conky, 1024×768 resolution, 96 dpi, Automount enable, CPU ranging from 2% to 4%, Frequency ranging from 2528, RAM 103M Used / 1.89GB Total (for onboard video), Swap 0 / 0B, Disk (Pendrive) 2.43M / 1.49 GB.
            Terminal, with the command demo @ antixl: ~ $ free {Enter}, total memory: 1985244 KB of RAM, 454408 KB are in use and 1530836 KB are free, shared 7324, buffers 68448 cached 268368 – / + buffers / cache 117592 used and 1867652 free.

            After installing on HD:
            Information displayed by Conky, Resolution 1024×768, dpi 96, Automount enable, CPU varying between 3% and 5%, Frequency varying between 2528, 118M RAM Used / 1.89GB Total, Swap 0 / 2GB, Disk (HD) 2.44G / 28.9 GB.
            Terminal, with the command Usuario @ antix: ~ $ free {Enter}, total memory: 1985244 KB of RAM, 282176 KB are in use and 1703068 KB are free, shared 1012, buffers 20100 cached 126868 +/- buffers / cached 135208 free 1850036, Swap 2097148 total 0 used 2097148 free.

            GoboLinux (GoboLinux-017-x86_64.iso)

            https://gobolinux.org/release_notes_017.html
            Hardware requirements
            Processor
            GoboLinux is compiled to run on x86-64-class systems. You shouldn’t have problems to run it on any modern x86 machine, including Macs. This release contains 64-bit binaries.

            Memory
            To load the Live CD environment, 128 MB of RAM is the recommended minimum for a text-mode system, 512 MB is the recommended minimum to load the graphic Awesome desktop; 1 GB is recommended for a comfortable Live-boot experience.

            Once the system is installed in the hard disk, memory requirements vary greatly depending on the kind of applications executed, but the values ​​stated above related to the Live CD experience serves as a good guideline.

            Before installing to HD:
            $ free {Enter}
            Memory: total: 2026848 KB, used: 115776 KB, free: 1360880 KB, shared: 110308 KB, buff / cache: 550192 KB, available: 1648868 KB, swap: total: 0 KB, used: 0, free: 0 KB.

            In the Menu, System Tools, Htop, displays memory consumption values ​​of 1.93G of RAM, 192MB are in use, displays CPU usage between 1.3% and 2%

            After installing on HD:
            $ free {Enter}
            Memory: total: 2026860 KB, used: 102568 KB, free: 1664500 KB, shared: 69260 KB, buff / cache: 259792 KB, available: 1710960, swap: total: 2097148 KB, used: 0, free: 2097148 KB.

            Htop, displays memory consumption values, of the 1.93G of RAM, 147MB are in use, displays CPU usage between 0% and 1.3%.

            marcelocripe

            • This reply was modified 2 years, 9 months ago by marcelocripe.
            #40130
            Member
            marcelocripe

              Seaken64,

              Infelizmente eu vou ficar devendo, eu não consegui tantas informações detalhadas quanto as suas. A minhas ficam limitadas pelo comando $ free {Enter}, $ htop {Enter}, ou de algum gerenciador de tarefas.

              Tiny Core Plus (CorePlus-current.iso ou Tiny Core Plus 11.0)

              Antes da instalação no HD:
              Terminal, com o comando “free”, memória total 964532 KB de memória RAM, 89060 KB em uso e 797756 KB livres.

              Após a instalação no HD:
              Terminal, com o comando “free”, memória total 964532 KB, 50988 KB em uso e 866016 KB livres.

              Programas já instalados no Tiny Core Plus 11.0 e 11.1
              Menu Wbar: Exit, Editor, ControlPanel, Apps, RunProgram, MountTool, Terminal, eZremaster, Wifi.

              No Tiny Core Plus 11.0 e 11.1 o Vídeo padrão é o xvesa.tcz, o Áudio por padrão não está disponível na ISO, Placa de rede LAN e WiFi são inicializadas por padrão na inicialização do sistema operacional.

              Puppy Linux BionicPup 32 (bionicpup32-8.0-uefi.iso)
              Antes da instalação no HD:
              Com o “Task Manager”, dos 1607 MB, 126 MB estão em uso e 5% de CPU.

              Após a instalação no HD:
              $ free {Enter}
              Memória: total: 1646012 KB, 76468 KB em uso e 1408204 MB livres.
              Com o Task Manager,dos 1607 MB, 92 MB estão em uso e 16% de CPU.

              SliTaz (slitaz-rolling-core64.iso versão 20-05-2020)

              Antes da instalação no HD:
              $ free {Enter}
              XTerm Terminal
              Memória: total: 2088424 KB de memória RAM, 101276 KB em uso e 1701092 KB livres

              Sakura Terminal
              Memória: total: 2048424 KB de memória RAM, 101608 KB em uso e 1700716 KB livres.

              Gerenciador de tarefas LXTask 0.1.9:
              Exibe uso da CPU entre 0% e 2%, consumo de memória 93 MB de 2000 MB

              Após a instalação no HD:
              $ free {Enter}
              XTerm Terminal
              Memória: total: 1991712 KB de memória RAM, 72264 KB em uso e 1866784 KB livres

              Sakura Terminal
              Memória: total: 1991712 KB de memória RAM, 72996 KB em uso e 1864176 KB livres.

              Gerenciador de tarefas LXTask 0.1.9:
              Exibe uso da CPU entre 1% e 3%, consumo de memória 66 MB de 1945 MB.

              https://www.slax.org/introduction.php

              Requisitos de sistema para executar o Slax

              Slax 32bit
              Processador: CPU i686 ou mais recente, todos os processadores Intel e AMD funcionarão
              Memória: 128 MB de RAM para a área de trabalho, 512 MB de RAM para executar o navegador da Web
              Periféricos: Para inicializar a partir de unidade de CD ou USB ou HD
              Opcionalmente: placa de rede, placa de som

              Slax 64bit
              Processador: CPU x86_64, como AMD Athlon 64, Opteron, Sempron, Intel Core 2 / i3 / i5 / i7 e outros
              Memória: 128 MB de RAM para a área de trabalho, 512 MB de RAM para executar o navegador da Web
              Periféricos: Para inicializar a partir de unidade de CD ou USB ou HD
              Opcionalmente: placa de rede, placa de som

              Após a instalação no HD:

              Slax Linux (slax-64bit-9.11.0.iso):
              Utilizando o comando free no terminal o consumo de memória RAM foi de cerca de 134 MB ou utilizando o gerenciador de tarefas o consumo de memória RAM foi de cerca 155 MB.

              Slax Linux (slax-32bit-9.11.0.iso)
              Utilizando o comando free no terminal o consumo de memória RAM foi de cerca de 97912 KB (97,91 MB) ou utilizando o gerenciador de tarefas o consumo de memória RAM foi de cerca 109 MB.

              Void (void-live-x86_64-20191109-lxde.iso)

              -Antes da instalação, executando o Void Linux via pendrive:
              [anon@void-live:~] $ free {Enter}
              Memória: total: 2028996, used: 116344, free: 1306088 KB , shared: 23368, buff/cache: 606564, avaliable: 1743776 (valores em KB).

              -Após a instalação do Void Linux no HD:
              Memória: total: 2029456, usada: 121328, livre: 1727560 KB , compartilhada: 26048, buff/cache: 180568, disponível: 1741848 (valores em KB), Swap: total: 2096476, usada: 0, livre: 2096476.

              antiX (antiX-19.2_x64-full.iso)

              Antes da instalação no HD:
              Informações exibidas pelo Conky antes da instalação: Resolução 1366×768, dpi 96, Automount enable, CPU variando entre 2% e 4 %, Frequencia variando entre 800 e 1600, RAM 174M Usada / 1,56GB Total (para vídeo onboard -Via VT8237R Plus) ou RAM 144M Usada / 1,96GB Total (para vídeo offboard – nVidia GeForce MX 4000 Version 4.18.20.36.00 64 MB), Swap 0 / 5GB, Disco (Pendrive) 2,59M / 1,23 GB.

              Com o Terminal, comando demo@antixl:~ $ free {Enter}, memória total: 1641436 KB de memória RAM, 171304 KB em uso e 900160 KB livres, shared 11502.

              Após a instalação no HD:
              Informações exibidas pelo Conky, Resolução 1366×768, dpi 96, Automount enable, CPU variando entre 2% e 4 %, Frequencia variando entre 800 e 1600, RAM 172M Usada / 1,56GB Total, Swap 0 / 4GB, Disco (HD) 3,24G / 224 GB.

              Terminal, o comando Usuario@antixl:~ $ free {Enter}, memória total: 1641436 KB de memória RAM, 175864 KB estão em uso e 1230832 KB estão livres, shared 2092, Swap 4194300.

              Eu não sei desabilitar o Conky da inicialização do antiX, eu acredito que possa diminuir ainda mais o consumo de memória. Você sabe em qual arquivo de configuração onde podemos retirar o Conky? O ideal seria que o Conky fosse carregado na memória se o usuário o abrisse, ao invés de ser carregado por padrão.

              antiX Linux (antiX-17.4.1_x64-full.iso)

              Antes da instalação no HD:
              Informações exibidas pelo Conky, Resolução 1280×1024, dpi 96, Automount enable, CPU variando entre 52% e 54 %, Frequencia variando 2528, RAM 114M Usada / 1,89GB Total (para vídeo onboard), Swap 0 / 0B, Disco (Pendrive) 1,87M / 1,49 GB.
              Terminal, com o comando demo@antixl:~ $ free {Enter}, memória total: 1985696 KB de memória RAM, 113592 KB estão em uso e 1511040 KB estão livres, shared 8876, buff/cache 361064 avaliable 1725964.

              Após a instalação no HD:
              Informações exibidas pelo Conky, Resolução 1024×768, dpi 96, Automount enable, CPU variando entre 51% e 53 %, Frequencia variando entre 2528, RAM 131M Usada / 1,96GB Total, Swap 0 / 2GB, Disco (HD) 2,83G / 34.5 GB.
              Terminal, com o comando Usuario@antixl:~ $ free {Enter}, memória total: 1985708 KB de memória RAM, 138836 KB estão em uso e 1681044 KB estão livres, shared 1712, buff/cache 165828 avaliable 1710044, Swap 2096124.

              antiX Linux (antiX-16.3_x64-full.iso)

              Antes da instalação no HD:
              Informações exibidas pelo Conky, Resolução 1024×768, dpi 96, Automount enable, CPU variando entre 2% e 4 %, Frequencia variando 2528, RAM 103M Usada / 1,89GB Total (para vídeo onboard), Swap 0 / 0B, Disco (Pendrive) 2,43M / 1,49 GB.
              Terminal, com o comando demo@antixl:~ $ free {Enter}, memória total: 1985244 KB de memória RAM, 454408 KB estão em uso e 1530836 KB estão livres, shared 7324, buffers 68448 cached 268368 -/+ buffers/cache 117592 used e 1867652 free.

              Após a instalação no HD:
              Informações exibidas pelo Conky, Resolução 1024×768, dpi 96, Automount enable, CPU variando entre 3% e 5%, Frequencia variando entre 2528, RAM 118M Usada / 1,89GB Total, Swap 0 / 2GB, Disco (HD) 2,44G / 28.9 GB.
              Terminal, com o comando Usuario@antix:~ $ free {Enter}, memória total: 1985244 KB de memória RAM, 282176 KB estão em uso e 1703068 KB estão livres, shared 1012, buffers 20100 cached 126868 +/- buffers/cached 135208 free 1850036, Swap 2097148 total 0 used 2097148 free.

              GoboLinux (GoboLinux-017-x86_64.iso)

              https://gobolinux.org/release_notes_017.html
              Hardware requirements
              Processor
              GoboLinux is compiled to run on x86-64-class systems. You shouldn’t have problems to run it on any modern x86 machine, including Macs. This release contains 64-bit binaries.

              Memory
              To load the Live CD environment, 128 MB of RAM is the recommended minimum for a text-mode system, 512 MB is the recommended minimum to load the graphic Awesome desktop; 1 GB is recommended for a comfortable Live-boot experience.

              Once the system is installed in the hard disk, memory requirements vary greatly depending on the kind of applications executed, but the values stated above related to the Live CD experience serve as a good guideline.

              Antes da instalação no HD:
              $ free {Enter}
              Memória: total: 2026848 KB, usada: 115776 KB, livre: 1360880 KB, compartilhada: 110308 KB, buff/cache: 550192 KB, disponível: 1648868 KB, swap: total: 0 KB, usada: 0, livre: 0 KB.

              No Menu, System Tools, Htop, exibe valores de consumo de memória dos 1.93G de memória RAM, 192MB estão em uso, exibe uso da CPU entre 1.3% e 2%

              Após a instalação no HD:
              $ free {Enter}
              Memória: total: 2026860 KB, usada: 102568 KB, livre: 1664500 KB, compartilhada: 69260 KB, buff/cache: 259792 KB, disponível: 1710960, swap: total: 2097148 KB, usada: 0, livre: 2097148 KB.

              Htop, exibe valores de consumo de memória, dos 1.93G de memória RAM, 147MB estão em uso, exibe uso da CPU entre 0% e 1.3%.

              marcelocripe

              • This reply was modified 2 years, 9 months ago by marcelocripe.
              • This reply was modified 2 years, 9 months ago by marcelocripe.
              #40100
              Member
              seaken64

                This a continuation of a discussion we started over here (we got off topic):

                https://www.antixforum.com/forums/topic/still-using-antix-16-in-2020/page/3/#post-40082

                @marcelocripe,

                Here is my recommendations for system requirements for antiX, MX, MX-Fluxbox, Q4OS and Debian. My tests were all done in 32-bit on old P-3 and P-4 equipment.

                Seaken64

                System Requirements for Linux on Old Computers

                Here I will make a comparison of the officially documented “system requirements”, when provided, and my system specifications as I have them on the actual hardware.

                The antiX system requirements say at least 256MB RAM for the FULL version with 5GB hard disk space. On my computers this seems to be a reasonable minimum. But with only 256MB RAM you can only run a simple browser like NetSurf or Dillo, maybe SeaMonkey or Palemoon-nonsse2 will work for simple pages. My installs are between 3.6GB and 4.9GB of hard disk space. That leaves no room for data. I suggest at least 512MB of RAM and a 6GB hard drive or an 8GB USB.

                The MX system requirements say at least 1GB RAM and 6GB hard drive space and recommends 2GB RAM and 20GB hard drive space. I can run MX 32-bit in 512MB RAM if I use the MX-Fluxbox desktop. The hard drive space is under 5GB on my P-III machine. When running the full XFCE system I agree that 1GB is the minimum and 2GB would be better. And MX uses over 8.5GB on my P4 machine. For standard MX I recommend 2GB of RAM and a 20GB hard drive or 16GB USB. For MX-Fluxbox I recommend 1GB of RAM and 20GB HD or 16GB USB.

                Q4OS system requirements say at least 128MB RAM and 3GB storage for the TDE desktop. Recommended is 1GB RAM and 5GB of storage. On my P-III it needs at least 256MB and runs slower than antiX in 512MB. The installation uses over 5GB of storage. On my P-4 it needs at least 512MB and uses over 8GB of storage. For Q4OS Trinity (the TDE version) I recommend at least 512MB of RAM and it runs better with 1GB or more. I recommend at least an 8GB hard drive but it is better with 15GB or more.

                Debian system requirements say a minimum of 256MB RAM and 10GB drive space. They recommend 1GB of RAM and 10GB hard drive. On my P-III Debian uses at least 256MB of RAM and up to 6.5 GB of storage when installed with the XFCE desktop. It runs okay in 512MB as long as I limit the browser to SeaMonkey. I recommend at least 512MB of RAM and 1GB would be better. I recommend at least 10GB of storage and 15GB would be better.

                I will use the Pentium-III 1.0Ghz with 512MB and the P-4 3.2Ghz w/ 3GB.

                P-III Coppermine 1.0 Ghz, 512M
                p3—–
                antiX-17.4 32-bit, Kernel=4.10.5-antix.1-486-smp i686, Debian=9 (Stretch)
                15GB HD Partition, 4.87G used, 1GB Swap Partition
                IceWM Window Manager, “rox-icewm” desktop, antiX Adblock activated
                Memory used reported in Conkey
                Initial Idle Memory – 78M
                Firefox ESR Loaded, with NoScript active, one tab on antiX forum – 240M
                SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 185M
                PaleMoon-nonsse2 Loaded, with NoScript, one tab on antiX forum – 158M
                Netsurf, open to antiX forum – 108M
                LibreOffice Writer loaded, all browsers closed, single document – 150M

                p3—–
                antix-19.1 32-bit, Kernel=4.9.200-antix.1-486-smp i686, Debian=10 (Buster)
                15GB HD Partition, 3.61G used, 1GB Swap Partition
                IceWM Window Manager, “icewm” desktop, antiX Adblock activated
                Memory used reported in Conkey
                Initial Idle Memory – 70M
                Firefox ESR Loaded, with NoScript active, one tab on antiX forum – 248M
                SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 171M
                PaleMoon-nonsse2 Loaded, NoScript NOT installed, one tab on antiX forum – 150M
                Note: PM w/o NoScript = CPU 100% on antiX Forum, CPU 82% on MX Forum
                Netsurf, open to antiX forum – 110M
                SMTube, 360p mp4 video playing in mpv, all browsers closed – 195M, CPU=70%

                p3—–
                Q4OS Trinity 32-bit, Kernel=4.9.0-12-686-pae i686, Debian=9 (Stretch)
                15GB HD Partition, 5.1G used, 1GB Swap Partition
                Trinity Desktop Environment (TDE – KDE Plasma 3), “Q4OS_Default” theme
                Memory used reported in “htop”
                Initial Idle Memory – 136M
                SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 255M
                PaleMoon-nonsse2 Loaded, NoScript NOT installed, one tab on antiX forum – unusable
                Note: PM w/o NoScript = CPU 100% on antiX Forum, unusable. Install NoScript.
                PaleMoon-nonsse2 Loaded, NoScript activated, one tab on antiX forum – 210M
                Midori, open to antiX forum – 248M CPU=100%
                Konqueror, open to antiX forum – 209M
                Netsurf, open to antiX forum – 170M
                SMTube, 360p mp4 video playing in mpv, all browsers closed – 228M, CPU=70%
                LibreOffice Writer loaded, all browsers closed, single document – 242M

                p3—–
                MX-Fluxbox 19.2 32-bit, Kernel=4.19.0-6-686-pae i686, Debian=10 (Buster)
                (Note – might be better off installing 4.9 kernel)
                15GB HD Partition, 3.61G used, 1GB Swap Partition
                XFCE Desktop Environment, “Fluxbox” desktop
                Memory used reported in “htop”
                Initial Idle Memory – 93M
                Firefox ESR Loaded, with NoScript active, one tab on antiX forum – 310M
                Note: ESR version is not installed by default. Used MXPI to install.
                SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 222M
                Note: SeaMonkey must be installed from archive file downloaded from website.
                PaleMoon-nonsse2 Loaded, with NoScript active, one tab on antiX forum – 191M
                Note – installed PM from .deb file using gdebi. MX-17 repository.
                Netsurf, open to antiX forum – 150M
                LibreOffice Writer loaded, all browsers closed, single document – 228M

                SMTube, 360p mp4 video playing in VNC, all browsers closed – 189M, CPU=100%
                Note – mpv not installed. Installed mplayer and mpv from MXPI. Didn’t work. Maybe need non-SSE2 version. Check antiX repos. Installed SMPlayer. SMPlayer starts but video does not play. Maybe related to youtube-dl? Installed youtube-dl. Didn’t help.

                p3—–
                Debian 9 (Stretch) 32-bit, Kernel=4.9.0-12-686-pae i686
                13GB HD Partition, 6.3G used, 1GB Swap Partition
                XFCE Desktop Environment, “IceWM” desktop
                Memory used reported in “htop”
                Initial Idle Memory – 80M
                Firefox ESR Loaded, with NoScript active, one tab on antiX forum – 401M
                SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 227M

                p3—–
                Debian 10 (Buster) 32-bit, Kernel=4.19.0-8-686-pae i686
                13GB HD Partition, 4.14G used, 1GB Swap Partition
                XFCE Desktop Environment, “IceWM” desktop
                Memory used reported in “htop”
                Initial Idle Memory – 90M
                Firefox ESR Loaded, could not install NoScript. CPU=100% hung up.
                SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 215M

                P-4 Prescott HT 3.2 Ghz, 3Gb
                p4—–
                MX-19.2 32-bit, Kernel=4.19.0-6-686-pae i686, Debian=10 (Buster)
                23GB HD Partition, 8.56G used, 3GB Swap Partition
                XFCE Desktop Environment, “XFCE” desktop
                Memory used reported in Conkey
                Initial Idle Memory – 429M
                Firefox Loaded, one tab on antiX forum – 726M
                Falkon Loaded, one tab on antiX forum – 681M
                PaleMoon Loaded, one tab on antiX forum – 674M
                Vivaldi Loaded, one tab on antiX forum- 667M
                SlimJet Loaded, one tab on antiX forum – 629M
                Chromium Loaded, one tab on antiX forum – 583M
                SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 571M
                LibreOffice Writer loaded, all browsers closed, single document – 660M

                p4—–
                MX-Fluxbox 19.2 32-bit, Kernel=4.19.0-6-686-pae i686, Debian=10 (Buster)
                23GB HD Partition, 8.56G used, 3GB Swap Partition
                XFCE Desktop Environment, “Fluxbox” desktop
                Memory used reported in “htop”
                Initial Idle Memory – 237M
                Firefox Loaded, one tab on antiX forum – 446M
                Falkon Loaded, one tab on antiX forum – 404M
                PaleMoon Loaded, one tab on antiX forum – 403M
                Vivaldi Loaded, one tab on antiX forum- 427M
                SlimJet Loaded, one tab on antiX forum – 392M
                Chromium Loaded, one tab on antiX forum – 362M
                SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 405M
                LibreOffice Writer loaded, all browsers closed, single document – 332M

                p4—–
                antix-19.1 32-bit, Kernel=4.9.193-antix.1-486-smp i686, Debian=10 (Buster)
                Frugal install on 8GB HD Partition, 2.44G used, 3GB Swap Partition
                IceWM Window Manager, “space-icewm” desktop, antiX Adblock activated
                Memory used reported in Conkey
                Initial Idle Memory – 73M
                Firefox ESR Loaded, one tab on antiX forum – 285M
                SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 200M
                Chromium Loaded – one tab on antiX forum – 230M
                SMTube, 360p mp4 video playing in mpv, all browsers closed – 192M, CPU=16%
                LibreOffice Writer loaded, all browsers closed, single document – 140M
                SeaMonkey open one tab, SMTube video playing, Writer document – 375M, CPU=42%

                p4—–
                Q4OS Trinity 32-bit, Kernel=4.9.0-13-686-pae i686, Debian=9 (Stretch)
                12GB HD Partition, 8G used, 3GB Swap Partition
                Trinity Desktop Environment (TDE – KDE Plasma 3), “Debonaire” theme
                Memory used reported in “htop”
                Initial Idle Memory – 160M
                SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 284M
                Chromium, open to antiX forum – 321M
                Konqueror, open to antiX forum – 274M
                SMTube, 360p mp4 video playing in VLC, all browsers closed – 302M, CPU=16%
                LibreOffice Writer loaded, all browsers closed, single document – 327M
                SeaMonkey open one tab, SMTube video playing, Writer document – 408M, CPU=17%

                #39969

                In reply to: End of an Era for me

                Moderator
                BobC

                  One of this weekend’s projects is to either get it working or strip it for usable parts. My guess is I goofed up the MB when trying to replace the CMOS battery. I’ll inspect it for obvious damage just in case. I’m pretty sure I can use one of the CPU’s to replace a much slower slot 1 P II CPU in a machine with a similar MB, and will see if I can use the memory because the other machine doesn’t have enough. Also the DVD will swap, and WiFi and the ATI video. It has a big PS but will have to look if I can use that in anything else.

                  I’m not good enough at electronics to fix anything tricky unless I have a full shop manual, like my old Heathkit radio stuff used to come with, where they gave check voltages at pin outs, etc.

                  The only value it has is sentimental at this point…

                  Member
                  nkizz

                    Hello!
                    I have an older N-Vidia card with an S-Video output, and I’m trying to get it output in NTSC, instead of PAL.
                    According to this link, I should be able to set this with the tv_norm parameter, however, I can’t seem to get it to work. I’ve some hopefully relevant command outputs below. Also, in terms of my general problem, I’ve also tried setting it with xrandr and nvtv, neither of which work. I also tried setting the parameter in GRUB, which didn’t seem to work either.

                    Thanks!

                    nkizz@doot:~
                    $ head /etc/sysctl.conf 
                    #
                    # /etc/sysctl.conf - Configuration file for setting system variables
                    # See /etc/sysctl.d/ for additional system variables.
                    # See sysctl.conf (5) for information.
                    #
                    nouveau.tv_norm = NTSC-M
                    #kernel.domainname = example.com
                     
                    # Uncomment the following to stop low-level messages on console
                    #kernel.printk = 3 4 1 3
                    nkizz@doot:~ 
                    $ sudo sysctl -p:
                    sysctl: cannot stat /proc/sys/nouveau/tv_norm: No such file or directory
                    vm.swappiness = 10
                    vm.vfs_cache_pressure = 50
                    vm.dirty_bytes = 20000000
                    nkizz@doot:~
                    $ ls /proc/sys
                    debug  dev  fbcondecor  fs  fscache  kernel  net  sunrpc  user  vm
                    nkizz@doot:~
                    $ sudo lspci -k
                     
                    01:00.0 VGA compatible controller: NVIDIA Corporation NV34 [GeForce FX 5200] (rev a1)
                    	Subsystem: NVIDIA Corporation NV34 [GeForce FX 5200]
                    	Kernel driver in use: nouveau
                    	Kernel modules: nouveau
                    • This topic was modified 2 years, 9 months ago by nkizz.
                    • This topic was modified 2 years, 9 months ago by nkizz.
                    Member
                    drinkWine

                      Possible to fix it ?
                      or
                      madeing the forced sound increase above the maximum ?

                      $ inxi -Fxx
                      System:    Host: antix2 Kernel: 4.9.212-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: IceWM 1.6.5 dm: SLiM 
                                 Distro: antiX-19.2.1_x64-base Hannie Schaft 29 March 2020 base: Debian GNU/Linux 10 (buster) 
                      Machine:   Type: Laptop System: Hewlett-Packard product: Presario CQ56 Notebook PC v: 059A110000202810010000100 
                                 serial: <root required> Chassis: type: 10 serial: <root required> 
                                 Mobo: Hewlett-Packard model: 1605 v: 90.17 serial: <root required> BIOS: Hewlett-Packard v: F.14 date: 02/01/2011 
                      Battery:   ID-1: BAT0 charge: 0% condition: 47.3/47.3 Wh (100%) volts: 2.7/10.8 model: Hewlett-Packard Primary serial:   
                                 status: Unknown 
                      CPU:       Topology: Dual Core model: Celeron T3500 bits: 64 type: MCP arch: Penryn rev: A L2 cache: 1024 KiB 
                                 flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 8378 
                                 Speed: 2095 MHz min/max: N/A Core speeds (MHz): 1: 2095 2: 2095 
                      Graphics:  Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 
                                 chip ID: 8086:2a42 
                                 Display: x11 server: X.Org 1.20.4 driver: intel resolution: 1366x768~60Hz 
                                 OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express v: 2.1 Mesa 18.3.6 direct render: Yes 
                      Audio:     Device-1: Intel 82801I HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
                                 chip ID: 8086:293e 
                                 Sound Server: ALSA v: k4.9.212-antix.1-amd64-smp 
                      Network:   Device-1: Ralink RT3090 Wireless 802.11n 1T/1R PCIe vendor: Hewlett-Packard driver: rt2800pci v: 2.3.0 port: 4000 
                                 bus ID: 02:00.0 chip ID: 1814:3090 
                                 IF: wlan0 state: up mac: e0:2a:82:df:37:46 
                                 Device-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet vendor: Hewlett-Packard RTL810xE driver: r8169 
                                 v: 2.3LK-NAPI port: 2000 bus ID: 03:00.0 chip ID: 10ec:8136 
                                 IF: eth0 state: down mac: 98:4b:e1:bd:cd:5e 
                                 Device-3: Ralink Motorola BC4 Bluetooth 3.0+HS Adapter type: USB driver: btusb bus ID: 8-1:2 chip ID: 148f:1000 
                      Drives:    Local Storage: total: 74.53 GiB used: 3.66 GiB (4.9%) 
                                 ID-1: /dev/sda vendor: Seagate model: ST980811AS size: 74.53 GiB speed: 1.5 Gb/s serial: 3LY073Q7 
                      Partition: ID-1: / size: 13.48 GiB used: 3.66 GiB (27.2%) fs: ext4 dev: /dev/sda3 
                                 ID-2: swap-1 size: 1.95 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda4 
                      Sensors:   System Temperatures: cpu: 65.0 C mobo: N/A 
                                 Fan Speeds (RPM): N/A 
                      Info:      Processes: 153 Uptime: 1h 16m Memory: 1.89 GiB used: 749.5 MiB (38.7%) Init: SysVinit v: 2.93 runlevel: 5 
                                 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: roxterm inxi: 3.0.36 
                      
                      #39864

                      In reply to: new kernels available

                      Member
                      namida12

                        Typing this from another computer, not the Ryzen 5 3400G that will not boot:

                        Cannot boot newer Kernel, installed 5.6.10 from package manager

                        starts to boot – I get a black screen, about 20 seconds then line after line rapidly scroll.

                        Then it appears is is going to boot yet I have a few errors
                        [ 66.816718] kfd kfd: error getting iommu info. is the iommu enabled?
                        [ 66.816723] kfd kfd: Error initiallizing iommuv2
                        [ 66.816825] kfd kfd: device 1002:15d8 NOT added due to errors
                        [ 66.877416] udevd[607]: error opening ATTR{/sys/devices/pci0000:00/0000:00:08:.1/0000:07:00.0/firmware/amdgpu!picasso_ta.bin/loading) for writing: No such file or Directory

                        Then just before it stops <———-
                        [ ok ] Starting slim:slim
                        [ ok ] Starting OpenBSD Secure Shell server: sshd
                        Applying power save settings…done
                        Applying battery charge thresholds…done
                        [ ok ] Virtualbox Additions disabled, not in a Virtual Machine

                        Welcome to antiX. Powered by Debian.
                        green611 login: [ 68.861662] [drm:mod_hcdcp_add_display_topology {amdgpu}} *ERROR* Failed to add display topology, DTM TA is not Initialized

                        I included inxi -F from older Kernel to show system info

                        $ inxi -F
                        System:    Host: green611 Kernel: 4.19.100-antix.1-amd64-smp x86_64 bits: 64 Desktop: IceWM 1.6.6 
                                   Distro: antiX-19.2-4.19_kernel_x64-full Hannie Schaft 6 April 2020 
                        Machine:   Type: Desktop Mobo: ASRock model: B450M Pro4 serial: <root required> UEFI [Legacy]: American Megatrends v: P3.90 
                                   date: 12/09/2019 
                        CPU:       Topology: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP L2 cache: 2048 KiB 
                                   Speed: 1945 MHz min/max: 1400/3700 MHz Core speeds (MHz): 1: 1300 2: 1354 3: 1647 4: 1370 5: 1334 6: 1406 7: 1407 
                                   8: 1260 
                        Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Picasso driver: N/A 
                                   Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1920x1080~N/A 
                                   OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 
                        Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel 
                                   Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel 
                                   Sound Server: ALSA v: k4.19.100-antix.1-amd64-smp 
                        Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
                                   IF: eth0 state: up speed: 1000 Mbps duplex: full mac: a8:a1:59:0d:db:5a 
                        Drives:    Local Storage: total: 465.76 GiB used: 182.40 GiB (39.2%) 
                                   ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS500G3XHC-00SJG0 size: 465.76 GiB 
                        Partition: ID-1: / size: 14.70 GiB used: 5.35 GiB (36.4%) fs: ext4 dev: /dev/nvme0n1p2 
                                   ID-2: /home size: 434.06 GiB used: 177.05 GiB (40.8%) fs: ext4 dev: /dev/nvme0n1p4 
                                   ID-3: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p3 
                        Sensors:   System Temperatures: cpu: 37.6 C mobo: N/A 
                                   Fan Speeds (RPM): N/A 
                        Info:      Processes: 217 Uptime: 2m Memory: 13.62 GiB used: 672.3 MiB (4.8%) Shell: bash inxi: 3.0.36 
                        
                        • This reply was modified 2 years, 9 months ago by namida12. Reason: adding inxi-F info from older Kernel
                        • This reply was modified 2 years, 9 months ago by namida12.
                        • This reply was modified 2 years, 9 months ago by namida12.
                        Anonymous

                          Greetings!

                          The antiX installation program has an option to use a swap partition on one of the disks it detects on the computer during the operating system installation, and it can encrypt the root/home directory of the system, along with the swap partition. I would like to set up the LUKS encrypted swap partition I made so it’s automatically enabled at start up, and so it works with pm-hibernate or hibernate.

                          Does anybody know how to do all of this without reinstalling the system? I’m short of partitions in the disk, and I can’t use external storage mediums either, because I don’t have many, and the ones I have lack the space I need or are broken.

                          Member
                          AR

                            In my antiX 19.2 full I never had the lack of memory on my 2Gb RAM EeePC 1215P. With IceWM (without ROX and wallpapers), and Chrome browser (where I has suppressed all ads), my using of swap had maximum of approximately 50Mb with about 4-6 opened tabs in Chrome plus 1-2 other applications opened. Even if one of other applications was GIMP, and the second was Double Commander. And yes, I use zswap with lz4, but I suspect that my 50Mb of swap doesn’t fit in zswap thresold.

                            Member
                            rayluo

                              @rayluo Maybe list standard pages each in own tab used to reach and test the condition as well as firefox setup would help others to replicate
                              as far as browser is concerned. Is only firefox open, What is running in background.

                              Well, I don’t think it is necessary to “replicate as far as browser is concerned”. Because:

                              1. On my machine I use an almost-original antix image, so I don’t think there are much “running in background”. “htop” also shows no other activities, besides Firefox and some extremely-lightweight terminal apps (tmux, vim, etc.)

                              2. And I don’t even think it has much to do with Ads, because the memory-intensive web pages I referred to, was just a couple big-name online email or online chat application inside a web page. Those pages contains no ads by its nature. Perhaps still contains some tracking, but I doubt we can – or should – mess up with a modern rich-client application in a web page.

                              So, perhaps these all boil down to what particular web pages an individual would need to visit in a whatever browser, with some particular computer specs. If the workload is approaching the (ram) limit, then so be it. To that end, the title and the original intention of this thread, was to see whether antiX can be configured to NOT getting into thrashing. I found no answer to that specific question, but the zswap+swap seems a reasonable workaround.

                              #39629
                              Member
                              Budgie

                                Earlier in this thread seaken64 suggested I do new install and after the strange behaviour with my lan connection that has been the only option so I have installed Antix 19.2 base. I have been quite surprised by the difference from my previous install and so will explore and adjust system to suit my preferences.

                                No real understanding of problem I ran into but it is just possible my connection had been blocked by my Sophos UTM but that is another story!

                                I shall now work on my original problem taking into the advice given above. From what I have seen during the installation however I find that now both Ceni and Connman are installed and are shown on Control Centre > Network page and from was written earlier I should only use one of these and not swap between.

                                Will report progress in due course and meanwhile grateful thanks for those who have helped and for an excellent Forum.

                                Member
                                ModdIt

                                  Thanks@all for interesting info.
                                  I asked around, very few of us have more than 2 Gig Memory, Firefox seems to be part of the puzzle as is ads tracking telemetry.

                                  We get the system going non responsive with Tor Browser. CPU @100% Pages full of blinking ads, trackers firing away, CSS running rife
                                  and suspect we are also running other more hidden nefarious things in background as network traffic is very high, swap too.

                                  With Latest Firefox, a comprehensive hosts file to reduce ads and tracking. Hidden extensions removed from Fox. No Pocket, No Safe Browsing,
                                  No Snippets and search suggestions, Policy file (from Enterprise policy Generator Addon), Ghacks user.js are used as is u block origin.
                                  Memory usage very rarely reaches swap level even with 5 or 6 (sometimes more) tabs open. No direct google search as the first 15 or 20 results
                                  are always crappy paid redirecting tracking rubbish. Mostly use Metager, Ecosia, Duck.

                                  I also look where popup ads and trash are coming from in the firefox java inspector keep an eye out for tracking stuff and extend blocklist.
                                  For Netflix and Amazon video an extra user is created as hardened browser will not allow drm..

                                  We have Claws on desk 1, Palemoon on 2, Calc on 3 Writer, on 4 Firefox opens on 6 and is the only non auto start mentioned.

                                  @rayluo Maybe list standard pages each in own tab used to reach and test the condition as well as firefox setup would help others to replicate
                                  as far as browser is concerned. Is only firefox open, What is running in background.

                                  • This reply was modified 2 years, 9 months ago by ModdIt. Reason: spelling again
                                Viewing 15 results - 1,126 through 1,140 (of 1,706 total)