How to use antiX on computers with a motherboard with SIS or VIA chipset

Forum Forums antiX-development Development How to use antiX on computers with a motherboard with SIS or VIA chipset

  • This topic has 85 replies, 11 voices, and was last updated Mar 1-6:22 pm by Wallon.
Viewing 15 posts - 1 through 15 (of 85 total)
  • Author
    Posts
  • #45488
    Member
    marcelocripemarcelocripe

    Original title in Brazilian Portuguese: How to use antiX on computers with a motherboard with SIS or VIA chipset

    Hello Anticapitalista and antiX Developers

    You already know that I am a beginner in this “world of Linux distributions”, I arrived here at antiX in June 2020, since then, I am learning a lot from our colleagues in the forum. I know I still have a lot to learn, so my considerations below are still of a limited view on the subject.

    The information I searched for on the internet indicates “that most drivers are in the kernel”

    Motherboard of the brand ASUS, as it will be in the following example, of the model P5S800-VM (with chipset SIS), when they arrived in Brazil they were the dream of consumption of several computer users (including mine), at the time who did not have financial conditions to buy an ASUS or Gigabyte motherboard, I bought MSI 238318 or STI 910090 (with Via chipset) or one made in China and then suffered to find the drives, Two other computers from the NGO arrived for me to prepare, but because they are computers with motherboard with SIS chipset and another with VIA antiX 19.3 or 19.2 make the video very slow, failing and with “ghosts”. It is impossible to use the operating system like that.

    I applied all the teachings on the topic https://www.antixforum.com/forums/topic/how-to-set-the-set-gfxmode-1024x768x16-1024×768/ to identify ASUS P5S800- branded motherboard devices VM. (Commands are available after the original Brazilian Portuguese text)

    Due to the teachings of the topic I mentioned earlier, antiX 16.3 will certainly work, with these two computers that have only 1GB of DDR RAM. I will need to install a full 32-bit version in order to save as much RAM as possible, but I have some doubts:

    1-antiX 16.3 had its “end of life” on June 6, 2020 or I can also understand that it was discontinued. Do the repositories still work for antiX 16.3 full 32 bits and antiXfull 64 bits?

    2- If the repositories still work for antiX 16.3 32 bits and antiX 64 bits, how much longer will they be available?

    The antiX 16.3 64 bits that I prepared for the computer with the VIA motherboard and 2GB of DDR RAM, from the topic I mentioned earlier. At the time, for example, I was unable to install the LibreOffice translations that already come with antiX. What I did to get around this, was to download the LibreOfficetraduced AppImage for PT-BR and the other programs were with AppIamge. I managed to make antiX 16.3 64 bits friendly to the end user with the programs and with the Menu translated to PT-BR added in the Personal Menu. All of these were palliative solutions, but 32-bit AppImage practically does not exist, it will be difficult to use antiX 16.3 32 bits. I still don’t know how to prepare AppImage to be able to use in antiX 16.3 32 bits. When I learn to create AppImage, if ever I will learn to do it, as I cannot find consultation material in Portuguese teaching how to create the 32-bit AppImage. All the material is available for consultation in the English language and usually refer to to 64 bits. Translations remain a daily challenge, it is not enough to translate the words, it is necessary to adapt the text so that the words can make complete sense in the sentences, but this is not always possible, as they depend on the context being used. Therefore, I continue to dedicate myself to make each text the best possible on the site transifex for PT-BR for antiX.

    After this long introduction, there are the next questions, which are the important ones in this topic:

    3-Would it be possible to create antiX 19.3 with the antiX 16.3 kernel?

    Since I got here (on antiX and the forum), I have stopped searching for other Linux distributions. I already know that this is my place, I met excellent people here. But if it is not possible to use an antiX due to the drivers, unfortunately, I will have to continue the search, just so that I can continue saving old computers (that are working) from being thrown in the trash.

    I hope, Anticapitalista, that you and the developers can evaluate this topic and analyze if this is possible or if it is feasible to accomplish. I know that there are already several antiX options and these options require a lot of work time to be produced and made available.

    Regardless of the answer, I thank you for creating and making antiX available.

    Thank you.

    marcelocripe
    (Original text in Brazilian Portuguese)

    ———-

    Título original em Português do Brasil: Como utilizar o antiX em computadores com placa-mãe com chipset SIS ou VIA

    Olá Anticapitalista e Desenvolvedores do antiX

    Vocês já sabem que eu sou iniciante neste “mundo das distribuições Linux”, cheguei aqui no antiX em Junho de 2020, desde então, eu estou aprendendo muito com os nossos colegas do fórum. Eu sei que ainda tenho muito o que aprender, por isso as minhas considerações a seguir ainda são de uma visão limitada sobre o assunto.

    As informações que eu pesquisei na internet indicam “que a maioria dos drivers estão no kernel”

    Placa-mãe da marca ASUS, como será no exemplo a seguir, do modelo P5S800-VM (com chipset SIS), quando chegaram no Brasil eram o sonho de consumo de vários usuários de computador (inclusive o meu), na época quem não tinha condições financeiras de comprar placa-mãe ASUS ou Gigabyte, comprava MSI 238318 ou STI 910090 (com chipset Via) ou alguma fabricada na China e depois sofria para encontrar os drives, Chegaram outros dois computadores da ONG para eu preparar, mas por serem computadores com placa-mãe com chipset SIS e outra com VIA o antiX 19.3 ou 19.2 ficam com o vídeo muito lento, falhando e com “fantasmas”. É impossível utilizar o sistema operacional assim.
     
    Eu apliquei todos os ensinamentos do tópico https://www.antixforum.com/forums/topic/how-to-set-the-set-gfxmode-1024x768x16-1024×768/ para identificar os dispositivos da placa-mãe da marca ASUS P5S800-VM. (Os comandos estão disponíveis após o texto original em Português do Brasil)

    Devido aos ensinamentos do tópico que citei anteriormente, o antiX 16.3 certamente irá funcionar, com estes dois computadores que possuem apenas 1GB de memória RAM DDR. Eu precisarei instalar o uma versão full 32 bits para poder economizar o máximo possível de memória RAM, mas tenho algumas dúvidas:      

    1-O antiX 16.3 teve o seu “fim de vida” no dia 06 de junho de 2020 ou também posso compreender que foi descontinuado. Os repositórios ainda funcionam para antiX 16.3 full 32 bits e para o antiXfull 64 bits?

    2- Se os repositórios ainda funcionam para antiX 16.3 32 bits e para o antiX 64 bits, por quanto tempo mais estarão disponíveis?

    O antiX 16.3 64 bits que eu preparei para o computador com a placa-mãe VIA e 2GB de memória RAM DDR, do tópico que citei anteriormente. Na ocasião, por exemplo, eu não consegui instalar as traduções do LibreOffice que já vem com o antiX. O que eu fiz para contornar isso, foi baixar o AppImage do LibreOfficetraduzidos para PT-BR e os demais programas foram com os AppIamge. Eu consegui tornar antiX 16.3 64 bits amigável para o usuário final com os programas e com o Menu traduzido para PT-BR adicionado no Menu Pessoal. Todas estas foram soluções paliativas, mas AppImage de 32 bits praticamente não existem, ficará difícil utilizar o antiX 16.3 32 bits. Eu ainda não sei preparar AppImage para poder usar no antiX 16.3 32 bits. Quando eu aprender a criar AppImage, se é que um dia eu conseguirei aprender a fazer isso, pois não encontro material de consulta em Português ensinando a criar o AppImage de 32 bits Todo o material está disponível a para consulta em idioma Inglês e normalmente se referem a 64 bits. As traduções continuam sendo um desafio diário, não basta traduzir as palavras, é preciso adaptar o texto para que as palavras possam fazer sentido completo nas frases, mas nem sempre isso é possível, pois dependem do contexto que estão sendo utilizadas. Por isso, continuo me dedicando para fazer cada texto o melhor possível no site transifex para PT-BR para o antiX.            

    Depois desta longa introdução, vem as próxima perguntas, sendo estas as importantes deste tópico: 

    3-Seria possível criar o antiX 19.3 com o kernel do antiX 16.3?  

    Desde que eu cheguei aqui (no antiX e no fórum), eu parei de pesquisar outras distribuições Linux. Eu já sei que aqui é o meu lugar, eu encontrei aqui pessoas excelentes. Mas se não for possível utilizar um antiX devido aos drivers, infelizmente, eu terei que continuar a busca, só para eu poder continuar salvando computadores antigos (que estão funcionando) de serem jogados no lixo.

    Eu espero, Anticapitalista, que você e os desenvolvedores possam avaliar este tópico e analisar se isso é possível ou se é viável de ser realizado. Eu sei que já existem várias opções de antiX e estas opções exigem bastante tempo de trabalho para serem produzidas e disponibilizadas.

    Independentemente da resposta, eu agradeço por criarem e disponibilizarem o antiX.

    Muito obrigado.   

    marcelocripe
    (Texto original em Português do Brasil)

    demo@antix1:~
    $ inxi -Fxz
    System:
    Host: antix1 Kernel: 4.9.235-antix.1-486-smp i686 bits: 32 compiler: gcc
    v: 8.3.0 Desktop: IceWM 1.8.3
    Distro: antiX-19.3_386-full Manolis Glezos 15 October 2020
    base: Debian GNU/Linux 10 (buster)
    Machine:
    Type: Desktop Mobo: ASUSTeK model: P5S800-VM v: Rev 1.xx serial: <filter>
    BIOS: American Megatrends v: 1022.001 date: 05/11/2006
    CPU:
    Topology: Single Core model: Intel Celeron bits: 64 type: MCP
    arch: Netburst Smithfield rev: 9 L2 cache: 256 KiB
    flags: lm pae sse sse2 sse3 bogomips: 5306
    Speed: 2653 MHz min/max: N/A Core speed (MHz): 1: 2653
    Graphics:
    Device-1: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or
    662/761Gx PCIE VGA Display Adapter
    vendor: ASUSTeK driver: N/A bus ID: 01:00.0
    Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1024×768~N/A
    OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6
    direct render: Yes
    Audio:
    Device-1: Silicon Integrated Systems [SiS] SiS7012 AC97 Sound
    vendor: ASUSTeK driver: snd_intel8x0 v: kernel bus ID: 00:02.7
    Sound Server: ALSA v: k4.9.235-antix.1-486-smp
    Network:
    Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
    vendor: ASUSTeK P5P800-MX Mainboard driver: 8139too v: 0.9.28 port: e400
    bus ID: 00:0b.0
    IF: eth0 state: down mac: <filter>
    Drives:
    Local Storage: total: 7.27 GiB used: 14.3 MiB (0.2%)
    ID-1: /dev/sda type: USB vendor: Kingston model: DT 101 G2 size: 7.27 GiB
    RAID:
    Hardware-1: Silicon Integrated Systems [SiS] RAID bus controller 180
    SATA/PATA [SiS]
    driver: sata_sis v: 1.0 bus ID: 00:05.0
    Partition:
    ID-1: / size: 744.0 MiB used: 2.3 MiB (0.3%) fs: overlay source: ERR-102
    Sensors:
    Message: No sensors data was found. Is sensors configured?
    Info:
    Processes: 133 Uptime: 12m Memory: 964.9 MiB used: 103.2 MiB (10.7%)
    Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3
    inxi: 3.0.36

    demo@antix1:~
    $ inxi -G
    Graphics:
    Device-1: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or
    662/761Gx PCIE VGA Display Adapter
    driver: N/A
    Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1024×768~N/A
    OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6

    demo@antix1:~
    $ inxi -v8
    System:
    Host: antix1 Kernel: 4.9.235-antix.1-486-smp i686 bits: 32 compiler: gcc
    v: 8.3.0
    parameters: vga=0x0317 lang=pt_BR tz=America/Sao_Paulo quiet splasht
    disable=lxF xorg=safe
    Desktop: IceWM 1.8.3 dm: SLiM 1.3.6
    Distro: antiX-19.3_386-full Manolis Glezos 15 October 2020
    base: Debian GNU/Linux 10 (buster)
    Machine:
    Type: Desktop Mobo: ASUSTeK model: P5S800-VM v: Rev 1.xx
    serial: <root required> BIOS: American Megatrends v: 1022.001
    date: 05/11/2006
    Memory:
    RAM: total: 964.9 MiB used: 105.8 MiB (11.0%)
    RAM Report:
    permissions: Unable to run dmidecode. Root privileges required.
    PCI Slots:
    Permissions: Unable to run dmidecode. Root privileges required.
    CPU:
    Topology: Single Core model: Intel Celeron bits: 64 type: MCP
    arch: Netburst Smithfield family: F (15) model-id: 4 stepping: 9
    microcode: 3 L2 cache: 256 KiB bogomips: 5306
    Speed: 2653 MHz min/max: N/A Core speed (MHz): 1: 2653
    Flags: acpi apic bts cid clflush cmov constant_tsc cx16 cx8 de ds_cpl
    dtes64 dts fpu fxsr ht lahf_lm lm mca mce mmx monitor msr mtrr pae pat pbe
    pebs pge pni pse pse36 sep ss sse sse2 tm tm2 tsc vme xtpr
    Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable
    Type: l1tf status: Vulnerable
    Type: mds
    status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
    Type: meltdown status: Vulnerable
    Type: spec_store_bypass status: Vulnerable
    Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
    Type: spectre_v2
    mitigation: Full generic retpoline, STIBP: disabled, RSB filling
    Type: srbds status: Not affected
    Type: tsx_async_abort status: Not affected
    Graphics:
    Device-1: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or
    662/761Gx PCIE VGA Display Adapter
    vendor: ASUSTeK driver: N/A bus ID: 01:00.0 chip ID: 1039:6330
    Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1024×768~N/A
    OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6
    compat-v: 3.1 direct render: Yes
    Audio:
    Device-1: Silicon Integrated Systems [SiS] SiS7012 AC97 Sound
    vendor: ASUSTeK driver: snd_intel8x0 v: kernel bus ID: 00:02.7
    chip ID: 1039:7012
    Sound Server: ALSA v: k4.9.235-antix.1-486-smp
    Network:
    Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
    vendor: ASUSTeK P5P800-MX Mainboard driver: 8139too v: 0.9.28 port: e400
    bus ID: 00:0b.0 chip ID: 10ec:8139
    IF: eth0 state: down mac: XX:XX:XX:XX:XX:XX (I changed the MAC to XX/eu alterei o MAC para XX)
    WAN IP: No WAN IP data found. Connected to the web? SSL issues?
    Drives:
    Local Storage: total: 7.27 GiB used: 14.3 MiB (0.2%)
    ID-1: /dev/sda type: USB vendor: Kingston model: DT 101 G2 size: 7.27 GiB
    block size: physical: 512 B logical: 512 B
    serial: 001CC0EC330FEB816605000A rev: PMAP scheme: MBR
    Floppy-1: /dev/fd0
    RAID:
    Hardware-1: Silicon Integrated Systems [SiS] RAID bus controller 180
    SATA/PATA [SiS]
    driver: sata_sis v: 1.0 port: 0000 bus ID: 00:05.0 chip ID: 1039.0180
    rev: 01
    Partition:
    ID-1: / raw size: N/A size: 744.0 MiB used: 2.3 MiB (0.3%) fs: overlay
    source: ERR-102 label: N/A uuid: N/A
    ID-2: /live/boot-dev raw size: 1.17 GiB size: <root required>
    used: <root required> fs: N/A dev: /dev/ventoy label: N/A uuid: N/A
    ID-3: /live/linux raw size: 1.14 GiB size: <root required>
    used: <root required> fs: squashfs dev: /dev/loop0 label: N/A uuid: N/A
    ID-4: /media/VTOYEFI raw size: 32.0 MiB size: 31.9 MiB (99.75%)
    used: 12.0 MiB (37.4%) fs: vfat dev: /dev/sda2 label: VTOYEFI
    uuid: ADB8-4480
    Unmounted:
    ID-1: /dev/dm-0 size: 1.17 GiB fs: <root required> label: N/A uuid: N/A
    ID-2: /dev/sda1 size: 7.24 GiB fs: exfat label: Ventoy uuid: 4E21-0000
    USB:
    Hub: 1-0:1 info: Full speed (or root) Hub ports: 8 rev: 2.0
    speed: 480 Mb/s chip ID: 1d6b:0002
    Device-1: 1-4:2 info: Toshiba Kingston DataTraveler 102/2.0 / HEMA Flash
    Drive 2 GB / PNY Attache 4GB Stick
    type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0
    speed: 480 Mb/s chip ID: 0930:6545 serial: 001CC0EC330FEB816605000A
    Device-2: 1-8:3 info: Alcor Micro Flash Card Reader/Writer
    type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0
    speed: 480 Mb/s chip ID: 058f:6362 serial: 058F312D81B
    Hub: 2-0:1 info: Full speed (or root) Hub ports: 3 rev: 1.1 speed: 12 Mb/s
    chip ID: 1d6b:0001
    Hub: 3-0:1 info: Full speed (or root) Hub ports: 3 rev: 1.1 speed: 12 Mb/s
    chip ID: 1d6b:0001
    Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
    chip ID: 1d6b:0001
    Sensors:
    Message: No sensors data was found. Is sensors configured?
    Repos:
    Active apt repos in: /etc/apt/sources.list.d/antix.list
    1: deb http://mirror.ufam.edu.br/mx/antix/buster buster main nonfree nosystemd
    Active apt repos in: /etc/apt/sources.list.d/buster-backports.list
    1: deb http://deb.debian.org/debian buster-backports main contrib non-free
    Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://ftp.br.debian.org/debian/ buster-updates main contrib non-free
    Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://ftp.br.debian.org/debian/ buster main contrib non-free
    2: deb http://security.debian.org/ buster/updates main contrib non-free
    No active apt repos in: /etc/apt/sources.list.d/onion.list
    No active apt repos in: /etc/apt/sources.list.d/various.list
    Processes:
    CPU top: 5
    1: cpu: 34.5% command: xorg pid: 3302 mem: 47.3 MiB (4.8%)
    2: cpu: 0.9% command: [rcu_sched] pid: 7 mem: 0.00 MiB (0.0%)
    3: cpu: 0.6% command: slim pid: 3284 mem: 10.2 MiB (1.0%)
    4: cpu: 0.6% command: conky pid: 3640 mem: 10.4 MiB (1.0%)
    5: cpu: 0.5% command: [ksoftirqd/0] pid: 3 mem: 0.00 MiB (0.0%)
    Memory top: 5
    1: mem: 47.3 MiB (4.8%) command: xorg pid: 3302 cpu: 34.5%
    2: mem: 26.0 MiB (2.6%) command: roxterm pid: 4081 cpu: 0.2%
    3: mem: 25.5 MiB (2.6%) command: rox pid: 3558 cpu: 0.1%
    4: mem: 16.4 MiB (1.6%) command: volumeicon pid: 3571 cpu: 0.0%
    5: mem: 14.3 MiB (1.4%) command: fbxkb pid: 3591 cpu: 0.0%
    Info:
    Processes: 133 Uptime: 14m 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

    demo@antix1:~
    $ lspci -v
    00:00.0 Host bridge: Silicon Integrated Systems [SiS] 661FX/M661FX/M661MX Host (rev 11)
    Subsystem: ASUSTeK Computer Inc. 661FX/M661FX/M661MX Host
    Flags: bus master, medium devsel, latency 32
    Memory at e0000000 (32-bit, non-prefetchable)
    Capabilities: <access denied>
    Kernel driver in use: agpgart-sis

    00:01.0 PCI bridge: Silicon Integrated Systems [SiS] AGP Port (virtual PCI-to-PCI bridge) (prog-if 00 [Normal decode])
    Flags: bus master, 66MHz, fast devsel, latency 64
    Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
    I/O behind bridge: 0000d000-0000dfff
    Memory behind bridge: dfe00000-dfefffff
    Prefetchable memory behind bridge: cfd00000-dfcfffff
    Kernel modules: shpchp

    00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] LPC Controller (rev 36)
    Flags: bus master, medium devsel, latency 0
    Kernel modules: i2c_sis630

    00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 IDE Controller (rev 01) (prog-if 80 [ISA Compatibility mode-only controller, supports bus mastering])
    Subsystem: ASUSTeK Computer Inc. 5513 IDE Controller
    Flags: bus master, medium devsel, latency 128, IRQ 16
    I/O ports at 01f0
    I/O ports at 03f4
    I/O ports at 0170
    I/O ports at 0374
    I/O ports at ffa0
    Capabilities: <access denied>
    Kernel driver in use: pata_sis

    00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS7012 AC’97 Sound Controller (rev a0)
    Subsystem: ASUSTeK Computer Inc. SiS7012 AC’97 Sound Controller
    Flags: bus master, medium devsel, latency 64, IRQ 18
    I/O ports at e800
    I/O ports at ec00
    Capabilities: <access denied>
    Kernel driver in use: snd_intel8x0
    Kernel modules: snd_intel8x0

    00:03.0 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI])
    Subsystem: ASUSTeK Computer Inc. USB 1.1 Controller
    Flags: bus master, medium devsel, latency 64, IRQ 20
    Memory at dfff4000 (32-bit, non-prefetchable)
    Kernel driver in use: ohci-pci

    00:03.1 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI])
    Subsystem: ASUSTeK Computer Inc. USB 1.1 Controller
    Flags: bus master, medium devsel, latency 64, IRQ 21
    Memory at dfff5000 (32-bit, non-prefetchable)
    Kernel driver in use: ohci-pci

    00:03.2 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI])
    Subsystem: ASUSTeK Computer Inc. USB 1.1 Controller
    Flags: bus master, medium devsel, latency 64, IRQ 22
    Memory at dfff6000 (32-bit, non-prefetchable)
    Kernel driver in use: ohci-pci

    00:03.3 USB controller: Silicon Integrated Systems [SiS] USB 2.0 Controller (prog-if 20 [EHCI])
    Subsystem: ASUSTeK Computer Inc. USB 2.0 Controller
    Flags: bus master, medium devsel, latency 64, IRQ 23
    Memory at dfff7000 (32-bit, non-prefetchable)
    Capabilities: <access denied>
    Kernel driver in use: ehci-pci

    00:05.0 RAID bus controller: Silicon Integrated Systems [SiS] RAID bus controller 180 SATA/PATA [SiS] (rev 01) (prog-if 85)
    Subsystem: ASUSTeK Computer Inc. RAID bus controller 180 SATA/PATA [SiS]
    Flags: bus master, 66MHz, medium devsel, latency 128, IRQ 17
    I/O ports at eff0
    I/O ports at efe4
    I/O ports at efa8
    I/O ports at efe0
    I/O ports at ef90
    I/O ports at 0000
    Kernel driver in use: sata_sis

    00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10)
    Subsystem: ASUSTeK Computer Inc. P5P800-MX Mainboard
    Flags: bus master, medium devsel, latency 64, IRQ 19
    I/O ports at e400
    Memory at dfff3c00 (32-bit, non-prefetchable)
    Capabilities: <access denied>
    Kernel driver in use: 8139too
    Kernel modules: 8139cp, 8139too

    01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter (prog-if 00 [VGA controller])
    Subsystem: ASUSTeK Computer Inc. SiS Real 256E (ASUS P5S800-VM motherboard)
    Flags: 66MHz, medium devsel, IRQ 11
    BIST result: 00
    Memory at d0000000 (32-bit, prefetchable)
    Memory at dfee0000 (32-bit, non-prefetchable)
    I/O ports at dc00
    [virtual] Expansion ROM at 000c0000 [disabled]
    Capabilities: <access denied>

    demo@antix1:~
    $ cat /proc/cmdline
    vga=0x0317 lang=pt_BR tz=America/Sao_Paulo quiet splasht disable=lxF xorg=safe
    demo@antix1:~

    #45615
    Member
    XecureXecure

    Because of my inexperience, I have been fighting with the Build-iso (created and used by the antiX team for building all antiX releases), and think I have a “more or less” got it to work.
    I had to use the initrd and boot folders from the latest iso-template-antix package as nothing else worked for me.
    I got it to boot in a VM with safe videomode (and it doesn’t auto log-in 🙁 ), but didn’t test on real hardware yet.

    Test at your own risk. Just try to boot it once or twice with and without safe video options and see if you can get to a graphical environment on the problematic sis and via machines. If it doesn’t work, I will keep experimenting on the coming weekend.

    This iso is built on antiX 19.3 i386 base + updates (for some reason I couldn’t install the broadcom drivers package, so hopefully you don’t need them).
    Differences with main antiX release:
    – Kernel: 4.4.240-antix.2-486 i686 (not sure if it is the right one).
    – Xorg version 1.16.4 (same as antiX 16) put on hold.
    – ISO size: 770 MBs
    Only download and test if you have free time. This is probably a failed experiment, so I don’t have much hope anything good can come from it.

    Special thanks to anticapitalista for updating the build-iso project on my request.

    Download link: https://drive.google.com/file/d/1PSMBcPy5kjVCTa07bQhkvw4jvrOBcITn/view?usp=sharing

    #45616
    Forum Admin
    anticapitalistaanticapitalista

    @Xecure – had a very quick look – seems to be working very well (well done).

    Philosophers have interpreted the world in many ways; the point is to change it.

    antiX with runit - leaner and meaner.

    #45618
    Member
    Avatarskidoo

    Test at your own risk

    virtualbox instance, FTW

    First boot, as soon as I attempted apt update, it’s trying to ?setup “firmware-b43legacy-installer” and apparently tries to download something from openwrt.org … and fails with an errormsg “some problem occurred during the firmware download. Please check your network connection.”

    apt purge firmware-b43legacy-installer
    and carry on…

    Hmm, buster-backports is permanently enabled, from the get-go.
    I’ve been operating under the impression that leaving it permantly enabled was inadvisable.

    suggest:
    add a line to /etc/skel/.profile
    export NO_AT_BRIDGE=1
    to suppress gtk accessibility warning messages

    privacy-unfriendly:
    app called “celluloid” ships with default preferences set to “automatically retrieve metadata” ~~ calls out to a webserver

    noted: at start of session, conky shows 59.5MB used

    it’s a very solid result. Congrats on your quick mastery of build-iso !

    #45636
    Member
    XecureXecure

    Thanks for the feedback, anticapitalista and skidoo. I am glad this attempt worked.

    I hope this works on marcelo’s problematic systems.

    I have copied your suggestions, skidoo, and will add them to the next version. If more people are interested, I will probably pin older firmware versions of the intel and amd graphics firmware, and see if I can slim the iso down to CD size (probably remove firefox and keep dillo as the default browser).

    Let us hope it works on marcelocripe’s systems first.

    #45660
    Member
    marcelocripemarcelocripe

    Hello @Xecure.

    I managed to download the ISO “antiX-19-legacy-bet1_386-base.iso” last night, as I was unable to download with the aid of a download manager program I thought the ISO could get corrupted, but it seems like everything is well with ISO.

    I managed to do a quick test on the computer described above, with ventoy-1.0.21 everything got faster, at startup I selected the language pt-BR, the time zone and started in normal mode.

    Displayed a message on the screen “No frames were in use … the ‘Default’ frame was selected. Use ‘rox -p = Defaut’ to enable it in the future. ‘”, Ok. Sometimes this message displays in antiX 19.2 .

    The video is similar to antiX 19.3 full 64 or 32 bytes in compatible video driver.

    Conky exhibits impressive 64.5 MB RAM consumption of the 936 MB available (two 512 MB DDR cards).

    This memory consumption is lower than that of Puppy Linux and SliTaz.

    I was able to capture the screens with RAM consumption and processing information before opening any programs, remembering that the moment the program performs the capture, the consumption goes up a little. In the following order, Conky, $ free {Enter}, $ htop {Enter}, Task Manager and lastly $ uname -a {Enter}.

    Antes-da-Instalacao-anti-X-19-legacy-bet1-386-base-23-11-2020-1
    Antes-da-Instalacao-anti-X-19-legacy-bet1-386-base-23-11-2020-2
    Antes-da-Instalacao-anti-X-19-legacy-bet1-386-base-23-11-2020-3
    Antes-da-Instalacao-anti-X-19-legacy-bet1-386-base-23-11-2020-4
    Antes-da-Instalacao-anti-X-19-legacy-bet1-386-base-23-11-2020-5

    Some menus fail or are repeated, others are repeated, but I know it was just a test. I thank you anyway, I already hope to revive these computers with antiX.

    I also tested a 21 min YouTube video with Firefox, with internet connection via cable, I managed to play the video with a low quality, but for the computer’s specifications, it was excellent.

    You are a genius!

    If it is possible to include many drivers, the more the better. It won’t matter if the size doesn’t fit on a CD. I know that the ideal condition is to fit everything on a CD, but if that is not possible, it will not be a problem. Even if you have a size of an entire DVD of 4.2 GB, this giant ISO will serve to make several old computers revive with antiX, regardless of the chipset.

    I am participating in the MX Linux Telegram groups, PCLinux, DuZeru (discontinued on 10/29/2020), either in the messenger conversations or in the internet searches on these SIS and Via chipsets, what most experienced colleagues report is that for these chipset Linux distributions are not supported or that they have always been a weakness for Linux distributions.

    If antiX can solve this and other driver problems, it will have the highest compatibility available for hardware for computers and notebooks.

    If you need me to send you the results of the test ISO commands, similar to the commands I applied with antiX 19.3 on the computer I mentioned above, please let me know. Today I intend to test the ISO on the other computer with Via chipset.

    @Skidoo, I was going to call you to participate in this topic. It’s good that @Anticapitalista and you saw this topic and are already able to collaborate.

    @Anticapitalista, please help @Xecure with what he needs.

    We have many computers and notebooks in Brazil with chipset SIS, Via and others from China. Some colleagues call these drives from China “aliens”, they have always been extremely difficult to find to be downloaded and installed when these types of computers used Windows.

    You are very fast, I am slow and I cannot keep up with your speed.

    Thank you!

    marcelocripe
    (Original text in Brazilian Portuguese)

    ———-

    Olá @Xecure.

    Eu consegui baixar a ISO “antiX-19-legacy-bet1_386-base.iso” ontem à noite, como eu não consegui baixar com o auxílio de um programa gerenciador de download eu pensei que a ISO poderia ficar corrompida, mas parece que está tudo bem com a ISO.

    Eu consegui fazer um teste rápido no computador descrito acima, com o ventoy-1.0.21 tudo ficou mais rápido, na inicialização eu selecionei o idioma pt-BR, o fuso horário e iniciei no modo normal.

    Exibiu uma mensagem na tela “Nenhum quadro estava em uso … o quadro ‘Padrão’ foi selecionado. Use ‘rox -p=Defaut’ para habilitá-lo no futuro.'”, Ok. Às vezes exibe esta mensagem no antiX 19.2.

    O vídeo está semelhante ao antiX 19.3 full 64 ou 32 bites em driver de vídeo compatível. 

    O Conky exibe impressionantes consumo de memória RAM de 64,5 MB dos 936 MB disponíveis (duas placas de 512 MB DDR).

    Este consumo de memória está inferior ao do Puppy Linux e do SliTaz.

    Eu consegui capturar as telas com informações de consumo de memória RAM e processamento antes da abrir qualquer programas, lembrando que no momento que o programa realiza a captura, o consumo sobe um pouco. Na seguinte ordem, Conky, comando $ free {Enter}, $ htop {Enter}, Gerenciador de Tarefas e por último $ uname -a {Enter}.

    (Links das imagens estão no texto traduzido para o idioma inglês)

    Alguns menus falham ou estão se repetindo, outros estão repetidos, mas eu sei que era apenas um teste. Eu agradeço mesmo assim, eu já tenho esperanças de reviver estes computadores com o antiX.

    Eu testei ainda um vídeo no Youtube de 21 min com o Firefox, com conexão à internet via cabo, eu conseguiu tocar o vídeo com uma qualidade baixa, mas para as especificações do computador, ficou excelente.

    Você é um gênio!

    Se for possível incluir muitos drivers, quanto mais melhor. Não importará se o tamanho não couber em um CD. Eu sei que a condição ideal é caber tudo em um CD, mas se isso não for possível, não será problema algum. Mesmo que se tiver um tamanho de um DVD inteiro de 4,2 GB, esta ISO gigante servirá para fazer vários computadores antigos reviverem com o antiX, independentemente do chipset.

    Eu estou participando dos grupos de Telegram do MX Linux, PCLinux, DuZeru (descontinuado no dia 29-10-2020), tanto nas conversas do mensageiro ou nas pesquisas na internet sobre estes chipset SIS e Via, o que mais os colegas experientes informam é que para estes chipset as distribuições Linux não oferecem suporte ou que sempre foram um ponto fraco para as distribuições Linux.

    Se o antiX conseguir resolver este e outros problemas de drivers passará a ter a maior compatibilidade disponível para hardware para computadores e notebook.

    Se você precisar que eu te envie o resultado dos comandos das ISOs de testes, semelhante aos comandos que eu apliquei com o antiX 19.3 no computador que citei acima, por favor me avise. Hoje eu pretendo testar a ISO no outro computador com chipset Via.

    @Skidoo, eu ia te chamar para participar deste tópico. Que bom que o @Anticapitalista e você viram este tópico e já estão podendo colaborar.

    @Anticapitalista, por favor ajude o @Xecure com o que ele precisar.

    Temos muitos computadores e notebook no Brasil com chipset SIS, Via e outros vindos da China. Alguns colegas chamam esses drives da China de “alienígenas”, sempre foram extremamente difíceis de serem encontrados para serem baixados e instalados quando estes tipos de computadores utilizavam Windows.

    Vocês são muito rápidos, eu sou lento e não consigo acompanhar a velocidade de vocês.

    Muito obrigado!

    marcelocripe
    (Texto original em Português do Brasil)

    #45664
    Member
    AvatarPPC

    Hi Marcelo
    Glad Xecure’s efforts made it possible for you to rescue some more computers from the dumpster.

    Compiling all skidoo’s suggestions into easy to use instructions:

    
    sudo apt purge firmware-b43legacy-installer
    sudo echo "export NO_AT_BRIDGE=1" >> /etc/skel/.profile

    Menu > Applications > Multimedia > Celluloid > click the icon with 3 vertical dots > click the third Tab > uncheck the third option > Click “Save”

    As always, the usual suggestion- to play YouTube videos in very slow/old computers, use smplayer (or mpv from the command line, if you feel comfortable with that)- most computers can play 480 dpi videos that way- which is about the same quality as non HD TV…

    Edit: I just noticed how fast the (single core) CPU is, Marcelo! Smtube/mpv would have no problem rendering even higher resolution videos, if MPV is correctly configured… Let me know if you need help with that!

    P.

    • This reply was modified 4 months, 2 weeks ago by PPC.
    #45666
    Forum Admin
    rokytnjirokytnji

    Most drivers are in the kernel. Unless you are the only driver maintainer . You did not submit your open source driver to the xorg foundation quick enough < they are kinda uppity when it comes to their rules>.

    LINK to Debian search

    https://www.phoronix.com/scan.php?page=search&q=Kevin+Brace

    After spending hours with BitJam and I sussing out my SIS and Via screens and finding xorg don’t like sis or via anymore.
    Something you guys in Brazil noticed.

    We decided to roll with vesa and call it day. Bitjam did all the heavy lifting. With making it so one could bypass xorg politics where time schedules rule .

    Here is quote off that link I supplied

    Someone Wants To Step Up To Take Over The VIA OpenChrome Driver

    At the time we trouble shooting antiX alphas . No one was maintaining old chips in tune with xorgs schedule.

    Sometimes I drive a crooked road to get my mind straight.
    Not all who Wander are Lost.
    I'm not outa place. I'm from outer space.

    Linux Registered User # 475019
    How to Search for AntiX solutions to your problems

    #45672
    Member
    XecureXecure

    You are being too greedy, marcelocripe. anticapitalista has already given us the tools (including both the build-iso tool, patches and compiles old kernels for us, maintains and packages new software version for us, maintains the antiX repos, including the old antiX 16 jessie repos, etc.) and has always helped me when I asked for it. This effort should be more community driven and impose less on the little time the devs have.
    Also, until you test it on VIA systems, I cannot guaranty this project will move very far (if the tests fail). We will have to hope roky and others can provide some of their experience with xorg and via chipsets so we can keep moving further.

    I was lucky all of these things aligned, and that Debian still hasn’t stopped the jessie repos, I was able to download 32bit xorg + all its dependencies. Hopefully we can keep moving this forward, and little by little keep some old hardware alive. But I think antiX 19 will probably be the last bastion for old 32 bits computers, as new Debian releases are more hardware demanding (and there is less emphasis in 32 bits since Ubuntu said byebye to the i386 architectures). Spotily no longer works on 32 bits Debian Buster, and Bullseye’s repos are almost cleared of gtk2 and qt4 dependent programs.

    marcelocripe, I don’t need the terminal output but simply need to know your experience with the systems. I am barely knowledgeable enough to edit some files, don’t expect me to have the knowledge and skill that anticapitalista, Bitjam, Dave, fehlix, masinick, SamK, skidoo and other real developers and knowledgeable people that help with antiX have.

    It is a surprise to see the low Memory footprint. Probably I broke something and services that should be running aren’t. It could also be related to the 4.4 kernel anticapitalista built or that simply new xorg versions now uses way more RAM than before.

    #45679
    Member
    Avatarskidoo

    > sudo apt purge firmware-b43legacy-installer

    clarification: that was not a suggestion. It was just an observation, an explanation of what I needed to do to move forward with the testing. Prior to purging, all “apt” operations stalled, with the msg “openwrt… failed… check your network connection”.

    > sudo echo “export NO_AT_BRIDGE=1” >> /etc/skel/.profile

    hold that thought…

    > “Menu > Applications > Multimedia > Celluloid > click the icon with 3 vertical dots”

    That tackles the detail from a user perspective.
    From a builder’s perspective, after checking and selecting “sane defaults” one must determine where each app stores its preferences and copy the customized files into a “holding pen” directory within the build-iso project, along with rules describing where each file is to be injeceted into the filesystem tree (in most cases, the location will be within /etc/skel/).

    Although some of the detailing steps like injecting the NO_AT_BRIDGE line into profile _can_ be performed by a scriped action, it is probably better (easier to see, to assess) if, instead, one preps the content of the “holding pen” copies of injected files with the edited details in place.

    #45681
    Member
    Avatarskidoo

    > if I can slim the iso down to CD size

    observed:
    After quick add/purge customizing, as part of my habitual testing regimen, I test iso-snapthot generation (and I boot the produced snapshot to verify success).

    With xz compression applied (chosen via dropdown within isosnapshot gui), ISO size was 584MB.
    A followup pass, using lz4 compression resulted in an ISO size of 915MB.
    Upon booting the generated ISOs, the highly-compressed version was slightly (but noticeably) laggy,
    both during startup and when loading (e.g. firefox) large programs during the test session.

    > if I can slim the iso down to CD size

    firmware-netronome
    147MB
    ^—- WTF? This is present in recent antix 19.x Full as a preinstalled package.

    from a websearch:

    https://dev.goodwu.net/post/2018-04-11-netronome-getting-started/
    The DKMS-based kernel module you will find at support.netronome.com is made of poo.
    It only works for old versions of RHEL and Ubuntu. The current kernel module
    that actually does work is located in this GitHub repo.

    What izza netronome?
    How prevalent is the associated hardware?
    izzit preinstalled in {cough} lean-n-mean antiX b/c someone had requested it?

    #45687
    Member
    AvatarPPC

    netronome

    I’m assuming that, like me, you searched on-line and found out that company makes server hardware (like https://www.netronome.com/products/agilio-cx/)… I’ve never heard of them before… I’m assuming that, for desktop use, antiX can do without that package?

    P.

    #45698
    Member
    marcelocripemarcelocripe

    To all present, I would like to express my sincere apologies for any misunderstanding that has occurred.

    I apologize. When I wrote, I was very happy, euphoric, anxious and hopeful.

    @Xecure, @Anticapitalista, @Skidoo, @Rokytnji, @PPC and other colleagues, I apologize for my words.

    The adrenaline made me not evaluate the words correctly, the translation certainly helped to make things worse.

    The same adrenaline rush made me forget that everyone here is a volunteer, sorry.

    I hope you can understand and accept my apologies.

    @Xecure, it’s not greed. It is happiness, euphoria, anxiety and hope.

    I am always grateful that the antiX community has accepted and received me, even though I don’t know how to speak the English language.

    I also thank friends for alerting me about the text translated into the English language. When I read the reverse translation (from the English text to Portuguese) I was able to understand …

    Thank you.

    I’m sorry …

    marcelocripe
    (Original text in Brazilian Portuguese)

    ———-

    A todos os presentes, registro os meus sinceros pedidos de desculpas por qualquer mal entendido que tenha ocorrido.

    Peço desculpas. Quando eu escrevi, eu estava muito feliz, eufórico, ansioso e esperançoso.

    @Xecure, @Anticapitalista, @Skidoo, @Rokytnji, @PPC e demais colegas, eu peço desculpas pelas minhas palavras.

    A adrenalina me fez não avaliar corretamente as palavras, a tradução certamente colaborou para piorar o que estava ruim.

    A mesma adrenalina me fez esquecer que todos aqui são voluntários, me desculpem.

    Eu espero que consigam compreender e aceitarem os meus pedidos de desculpas.

    @Xecure, não é ganancia. É felicidade, euforia, ansiedade e esperança.

    Eu sempre agradeço pela comunidade do antiX ter me aceitado e recebido, mesmo eu não sabendo falar o idioma Inglês.

    Eu agradeço também aos amigos por me alertarem sobre o texto traduzido para o idioma Inglês. Quando eu li a tradução inversa (do texto em Inglês para o Português) eu consegui compreender …

    Muito obrigado.

    Me desculpem …

    marcelocripe
    (Texto original em Português do Brasil)

    #45699
    Member
    marcelocripemarcelocripe

    Test on the computer that has the Asus P5V800-MX motherboard and VIA graphics card, using the ISO “antiX-19-legacy-bet1_386-base.iso”

    It worked even better than with SIS video, less flaws in the menus. And the video is similar to antiX 19.3 full 64 or 32 bytes in compatible video driver.

    Did not display the message you had displayed on the other computer

    I repeated the test, playing a 21 min YouTube video with Firefox, with an internet connection via cable. The video played at a low quality, but for computer specifications, it was excellent. Consumption of RAM memory during the video being played, according to Conky consumption of approximately 395 MB and in the htop consumption of RAM memory of approximately 450 MB and processing at 100%. The purpose of this test with Youtube directly in the browser is to simulate a user action where it forces the computer to the maximum.

    marcelocripe
    (Original text in Brazilian Portuguese)

    ———-

    Teste no computador que possui a placa~mãe Asus P5V800-MX e placa de vídeo VIA, utilizando a ISO “antiX-19-legacy-bet1_386-base.iso”

    Funcionou ainda melhor do que com o vídeo SIS, menos falhas nos menus. E o vídeo está semelhante ao antiX 19.3 full 64 ou 32 bites em driver de vídeo compatível.

    Não exibiu a mensagem que havia exibido no outro computador

    Eu repeti o teste, tocando um vídeo no Youtube de 21 min com o Firefox, com conexão à internet via cabo. O vídeo tocou com uma qualidade baixa, mas para as especificações do computador, ficou excelente. Consumo de memória RAM durante o vídeo em execução, segundo o Conky consumo de cerca 395 MB e no htop consumo de memória RAM em cerca de 450 MB e processamento em 100%. O objetivo deste teste com o Youtube diretamente no navegador é de simular uma ação do usuário onde força o computador ao máximo.

    marcelocripe
    (Texto original em Português do Brasil)

    demo@antix1:~
    $ inxi -Fxz
    System:
      Host: antix1 Kernel: 4.4.240-antix.2-486-smp i686 bits: 32 compiler: gcc v: 8.3.0 
      Desktop: IceWM 1.9.2 
      Distro: antiX-19-legacy-bet1_386-base Lazarus 23 November 2020 
      base: Debian GNU/Linux 10 (buster) 
    Machine:
      Type: Desktop Mobo: ASUSTeK model: P5V800-MX v: Rev 1.xx serial: <filter> 
      BIOS: American Megatrends v: 0802 date: 07/12/2006 
    CPU:
      Topology: Single Core model: Intel Celeron bits: 64 type: MCP 
      arch: Netburst Smithfield rev: 9 L2 cache: 256 KiB 
      flags: lm pae sse sse2 sse3 bogomips: 5054 
      Speed: 2527 MHz min/max: N/A Core speed (MHz): 1: 2527 
    Graphics:
      Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] 
      vendor: ASUSTeK driver: N/A bus ID: 01:00.0 
      Display: x11 server: X.Org 1.16.4 driver: openchrome 
      unloaded: fbdev,modesetting,vesa resolution: 800x600~85Hz 
      OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6 
      direct render: Yes 
    Audio:
      Device-1: VIA VT8237A/VT8251 HDA vendor: ASUSTeK driver: snd_hda_intel v: kernel 
      bus ID: 02:01.0 
      Sound Server: ALSA v: k4.4.240-antix.2-486-smp 
    Network:
      Device-1: VIA VT6102/VT6103 [Rhine-II] vendor: ASUSTeK A7V600-X driver: via-rhine 
      v: N/A port: d400 bus ID: 00:12.0 
      IF: eth0 state: down mac: <filter> 
    Drives:
      Local Storage: total: 81.80 GiB used: 14.4 MiB (0.0%) 
      ID-1: /dev/sda vendor: Maxtor model: STM380815AS size: 74.53 GiB 
      ID-2: /dev/sdb type: USB vendor: Kingston model: DT 101 G2 size: 7.27 GiB 
    Partition:
      ID-1: / size: 724.0 MiB used: 2.4 MiB (0.3%) fs: overlay source: ERR-102 
      ID-2: swap-1 size: 1.89 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3 
    Sensors:
      Message: No sensors data was found. Is sensors configured? 
    Info:
      Processes: 123 Uptime: 9m Memory: 936.3 MiB used: 87.7 MiB (9.4%) Init: SysVinit 
      runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.36 
    demo@antix1:~
    $ inxi -G
    Graphics:
      Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] 
      driver: N/A 
      Display: x11 server: X.Org 1.16.4 driver: openchrome 
      unloaded: fbdev,modesetting,vesa resolution: 800x600~85Hz 
      OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6 
    demo@antix1:~
    $ inxi -v8
    System:
      Host: antix1 Kernel: 4.4.240-antix.2-486-smp i686 bits: 32 compiler: gcc v: 8.3.0 
      parameters: vga=0x0317 lang=pt_BR tz=America/Sao_Paulo quiet splasht disable=lx 
      Desktop: IceWM 1.9.2 dm: SLiM 1.3.6 
      Distro: antiX-19-legacy-bet1_386-base Lazarus 23 November 2020 
      base: Debian GNU/Linux 10 (buster) 
    Machine:
      Type: Desktop Mobo: ASUSTeK model: P5V800-MX v: Rev 1.xx serial: <root required> 
      BIOS: American Megatrends v: 0802 date: 07/12/2006 
    Memory:
      RAM: total: 936.3 MiB used: 91.8 MiB (9.8%) 
      RAM Report: permissions: Unable to run dmidecode. Root privileges required. 
    PCI Slots:
      Permissions: Unable to run dmidecode. Root privileges required. 
    CPU:
      Topology: Single Core model: Intel Celeron bits: 64 type: MCP 
      arch: Netburst Smithfield family: F (15) model-id: 4 stepping: 9 microcode: 3 
      L2 cache: 256 KiB bogomips: 5054 
      Speed: 2527 MHz min/max: N/A Core speed (MHz): 1: 2527 
      Flags: acpi apic bts cid clflush cmov constant_tsc cx16 cx8 de ds_cpl dtes64 dts 
      fpu fxsr ht lahf_lm lm mca mce mmx monitor msr mtrr pae pat pbe pebs pge pni pse 
      pse36 sep ss sse sse2 tm tm2 tsc vme xtpr 
      Vulnerabilities: Type: itlb_multihit status: Processor vulnerable 
      Type: l1tf status: Vulnerable 
      Type: mds 
      status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
      Type: meltdown status: Vulnerable 
      Type: spec_store_bypass status: Vulnerable 
      Type: spectre_v1 
      mitigation: usercopy/swapgs barriers and __user pointer sanitization 
      Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
      Type: srbds status: Not affected 
      Type: tsx_async_abort status: Not affected 
    Graphics:
      Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] 
      vendor: ASUSTeK driver: N/A bus ID: 01:00.0 chip ID: 1106:3344 
      Display: x11 server: X.Org 1.16.4 driver: openchrome 
      unloaded: fbdev,modesetting,vesa resolution: 800x600~85Hz 
      OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6 
      direct render: Yes 
    Audio:
      Device-1: VIA VT8237A/VT8251 HDA vendor: ASUSTeK driver: snd_hda_intel v: kernel 
      bus ID: 02:01.0 chip ID: 1106:3288 
      Sound Server: ALSA v: k4.4.240-antix.2-486-smp 
    Network:
      Device-1: VIA VT6102/VT6103 [Rhine-II] vendor: ASUSTeK A7V600-X driver: via-rhine 
      v: N/A port: d400 bus ID: 00:12.0 chip ID: 1106:3065 
      IF: eth0 state: down mac: XX:XX:XX:XX:XX:XX (I changed the MAC to XX/ Eu alterei o MAC para XX)
      WAN IP: No WAN IP data found. Connected to the web? SSL issues? 
    Drives:
      Local Storage: total: 81.80 GiB used: 14.4 MiB (0.0%) 
      ID-1: /dev/sda vendor: Maxtor model: STM380815AS size: 74.53 GiB block size: 
      physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: 5RA8KAGS rev: B 
      scheme: MBR 
      ID-2: /dev/sdb type: USB vendor: Kingston model: DT 101 G2 size: 7.27 GiB 
      block size: physical: 512 B logical: 512 B serial: 001CC0EC330FEB816605000A 
      rev: PMAP scheme: MBR 
      Floppy-1: /dev/fd0 
      Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVD-RAM GSA-H54N rev: 1.00 
      dev-links: cdrom,cdrw,dvd,dvdrw 
      Features: speed: 1 multisession: yes audio: yes dvd: no rw: none state: running 
    RAID:
      Message: No RAID data was found. 
    Partition:
      ID-1: / raw size: N/A size: 724.0 MiB used: 2.4 MiB (0.3%) fs: overlay 
      source: ERR-102 label: N/A uuid: N/A 
      ID-2: /live/boot-dev raw size: 767.0 MiB size: <root required> 
      used: <root required> fs: N/A dev: /dev/ventoy label: N/A uuid: N/A 
      ID-3: /live/linux raw size: 736.9 MiB size: <root required> used: <root required> 
      fs: squashfs dev: /dev/loop0 label: N/A uuid: N/A 
      ID-4: /media/VTOYEFI raw size: 32.0 MiB size: 31.9 MiB (99.75%) 
      used: 12.0 MiB (37.4%) fs: vfat dev: /dev/sdb2 label: VTOYEFI uuid: ADB8-4480 
      ID-5: swap-1 size: 1.89 GiB used: 0 KiB (0.0%) fs: swap swappiness: 60 (default) 
      cache pressure: 100 (default) dev: /dev/sda3 label: N/A 
      uuid: e33c0fb1-fafa-4a12-b1f8-8c17b554a89d 
    Unmounted:
      ID-1: /dev/dm-0 size: 767.0 MiB fs: <root required> label: N/A uuid: N/A 
      ID-2: /dev/sda1 size: 36.32 GiB fs: ext4 label: N/A 
      uuid: f495c019-7e84-41d4-98ac-ef47d3bb2467 
      ID-3: /dev/sda2 size: 36.32 GiB fs: ext4 label: rootantiX19 
      uuid: b581b717-125a-4e5e-af99-9801969e56b0 
      ID-4: /dev/sdb1 size: 7.24 GiB fs: exfat label: Ventoy uuid: 4E21-0000 
    USB:
      Hub: 1-0:1 info: Full speed (or root) Hub ports: 8 rev: 2.0 speed: 480 Mb/s 
      chip ID: 1d6b:0002 
      Device-1: 1-4:4 info: Toshiba Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 
      GB / PNY Attache 4GB Stick 
      type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s 
      chip ID: 0930:6545 serial: 001CC0EC330FEB816605000A 
      Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
      chip ID: 1d6b:0001 
      Device-2: 2-1:2 info: Dell RT7D50 Keyboard type: Keyboard 
      driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 1.5 Mb/s 
      chip ID: 413c:2005 
      Device-3: 2-2:3 info: Trust B.V. Optical Mouse type: Mouse 
      driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 1.5 Mb/s 
      chip ID: 15d9:0a4f 
      Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
      chip ID: 1d6b:0001 
      Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
      chip ID: 1d6b:0001 
      Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
      chip ID: 1d6b:0001 
    Sensors:
      Message: No sensors data was found. Is sensors configured? 
    Repos:
      Active apt repos in: /etc/apt/sources.list.d/antix.list 
      1: deb http://repo.antixlinux.com/buster buster main nonfree nosystemd
      Active apt repos in: /etc/apt/sources.list.d/buster-backports.list 
      1: deb http://deb.debian.org/debian buster-backports main contrib non-free
      Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
      1: deb http://ftp.br.debian.org/debian/ buster-updates main contrib non-free
      Active apt repos in: /etc/apt/sources.list.d/debian.list 
      1: deb http://ftp.br.debian.org/debian/ buster main contrib non-free
      2: deb http://security.debian.org/ buster/updates main contrib non-free
      No active apt repos in: /etc/apt/sources.list.d/onion.list 
      No active apt repos in: /etc/apt/sources.list.d/various.list 
    Processes:
      CPU top: 5 
      1: cpu: 2.5% command: slim pid: 3346 mem: 10.0 MiB (1.0%) 
      2: cpu: 2.5% command: x pid: 3377 mem: 40.2 MiB (4.2%) 
      3: cpu: 0.9% command: conky pid: 3573 mem: 10.1 MiB (1.0%) 
      4: cpu: 0.6% command: icewm pid: 3473 mem: 12.9 MiB (1.3%) 
      5: cpu: 0.4% command: rox pid: 3580 mem: 24.7 MiB (2.6%) 
      Memory top: 5 
      1: mem: 40.2 MiB (4.2%) command: x pid: 3377 cpu: 2.5% 
      2: mem: 26.2 MiB (2.7%) command: roxterm pid: 4040 cpu: 0.4% 
      3: mem: 24.7 MiB (2.6%) command: rox pid: 3580 cpu: 0.4% 
      4: mem: 16.5 MiB (1.7%) command: volumeicon pid: 3497 cpu: 0.1% 
      5: mem: 13.0 MiB (1.3%) command: fbxkb pid: 3511 cpu: 0.1% 
    Info:
      Processes: 123 Uptime: 11m 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 
    demo@antix1:~
    $ inxi -v
    CPU: Single Core Intel Celeron (-MCP-) speed: 2527 MHz 
    Kernel: 4.4.240-antix.2-486-smp i686 Up: 12m Mem: 87.5/936.3 MiB (9.3%) 
    Storage: 81.80 GiB (0.0% used) Procs: 123 Shell: bash 5.0.3 inxi: 3.0.36 
    demo@antix1:~
    $ lspci -v
    00:00.0 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
    	Subsystem: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
    	Flags: bus master, medium devsel, latency 8
    	Memory at f0000000 (32-bit, prefetchable) 
    	Capabilities: <access denied>
    	Kernel driver in use: agpgart-via
    	Kernel modules: via_agp
    
    00:00.1 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
    	Subsystem: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
    	Flags: bus master, medium devsel, latency 0
    
    00:00.2 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
    	Subsystem: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
    	Flags: bus master, medium devsel, latency 0
    
    00:00.3 Host bridge: VIA Technologies, Inc. PT890 Host Bridge
    	Flags: bus master, medium devsel, latency 0
    	Kernel modules: via_agp
    
    00:00.4 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
    	Subsystem: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
    	Flags: bus master, medium devsel, latency 0
    
    00:00.7 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
    	Flags: bus master, medium devsel, latency 0
    
    00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge (prog-if 00 [Normal decode])
    	Flags: bus master, 66MHz, medium devsel, latency 0
    	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
    	Memory behind bridge: fc900000-fe9fffff
    	Prefetchable memory behind bridge: d7f00000-dfefffff
    	Capabilities: <access denied>
    	Kernel modules: shpchp
    
    00:0f.0 IDE interface: VIA Technologies, Inc. VT8251 AHCI/SATA 4-Port Controller (prog-if 8f [PCI native mode controller, supports both channels switched to ISA compatibility mode, supports bus mastering])
    	Subsystem: VIA Technologies, Inc. VT8251 AHCI/SATA 4-Port Controller
    	Flags: bus master, medium devsel, latency 64, IRQ 26
    	I/O ports at ec00 
    	I/O ports at e880 
    	I/O ports at e800 
    	I/O ports at e480 
    	I/O ports at e400 
    	Memory at febffc00 (32-bit, non-prefetchable) 
    	Capabilities: <access denied>
    	Kernel driver in use: ahci
    
    00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07) (prog-if 8a [ISA Compatibility mode controller, supports both channels switched to PCI native mode, supports bus mastering])
    	Subsystem: VIA Technologies, Inc. VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE
    	Flags: bus master, medium devsel, latency 32
    	[virtual] Memory at 000001f0 (32-bit, non-prefetchable) 
    	[virtual] Memory at 000003f0 (type 3, non-prefetchable)
    	[virtual] Memory at 00000170 (32-bit, non-prefetchable) 
    	[virtual] Memory at 00000370 (type 3, non-prefetchable)
    	I/O ports at fc00 
    	Capabilities: <access denied>
    	Kernel driver in use: pata_via
    
    00:10.0 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev 90) (prog-if 00 [UHCI])
    	Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller
    	Flags: bus master, medium devsel, latency 64, IRQ 20
    	I/O ports at e080 
    	Capabilities: <access denied>
    	Kernel driver in use: uhci_hcd
    
    00:10.1 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev 90) (prog-if 00 [UHCI])
    	Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller
    	Flags: bus master, medium devsel, latency 64, IRQ 22
    	I/O ports at e000 
    	Capabilities: <access denied>
    	Kernel driver in use: uhci_hcd
    
    00:10.2 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev 90) (prog-if 00 [UHCI])
    	Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller
    	Flags: bus master, medium devsel, latency 64, IRQ 21
    	I/O ports at dc00 
    	Capabilities: <access denied>
    	Kernel driver in use: uhci_hcd
    
    00:10.3 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev 90) (prog-if 00 [UHCI])
    	Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller
    	Flags: bus master, medium devsel, latency 64, IRQ 23
    	I/O ports at d880 
    	Capabilities: <access denied>
    	Kernel driver in use: uhci_hcd
    
    00:10.4 USB controller: VIA Technologies, Inc. USB 2.0 (rev 90) (prog-if 20 [EHCI])
    	Subsystem: VIA Technologies, Inc. USB 2.0 Controller
    	Flags: bus master, medium devsel, latency 64, IRQ 22
    	Memory at febff800 (32-bit, non-prefetchable) 
    	Capabilities: <access denied>
    	Kernel driver in use: ehci-pci
    
    00:11.0 ISA bridge: VIA Technologies, Inc. VT8251 PCI to ISA Bridge
    	Subsystem: VIA Technologies, Inc. VT8251 PCI to ISA Bridge
    	Flags: medium devsel
    	Capabilities: <access denied>
    	Kernel modules: i2c_viapro
    
    00:11.7 Host bridge: VIA Technologies, Inc. VT8237/8251 Ultra VLINK Controller
    	Subsystem: VIA Technologies, Inc. VT8237/8251 Ultra VLINK Controller
    	Flags: bus master, medium devsel, latency 128
    	Capabilities: <access denied>
    
    00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102/VT6103 [Rhine-II] (rev 7c)
    	Subsystem: ASUSTeK Computer Inc. A7V600-X Motherboard
    	Flags: bus master, medium devsel, latency 64, IRQ 23
    	I/O ports at d400 
    	Memory at febff400 (32-bit, non-prefetchable) 
    	Capabilities: <access denied>
    	Kernel driver in use: via-rhine
    	Kernel modules: via_rhine
    
    00:13.0 PCI bridge: VIA Technologies, Inc. VT8251 Host Bridge (prog-if 00 [Normal decode])
    	Flags: bus master, fast devsel, latency 0
    	Bus: primary=00, secondary=02, subordinate=04, sec-latency=0
    	Memory behind bridge: fea00000-feafffff
    	Kernel modules: shpchp
    
    00:13.1 PCI bridge: VIA Technologies, Inc. VT8251 PCI to PCI Bridge (prog-if 01 [Subtractive decode])
    	Flags: bus master, fast devsel, latency 0
    	Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
    
    01:00.0 VGA compatible controller: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01) (prog-if 00 [VGA controller])
    	Subsystem: ASUSTeK Computer Inc. CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro]
    	Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11
    	Memory at d8000000 (32-bit, prefetchable) 
    	Memory at fd000000 (32-bit, non-prefetchable) 
    	Expansion ROM at fe9f0000 [disabled] 
    	Capabilities: <access denied>
    
    02:00.0 PCI bridge: VIA Technologies, Inc. VT8251 PCIE Root Port (prog-if 00 [Normal decode])
    	Flags: bus master, fast devsel, latency 0, IRQ 24
    	Bus: primary=02, secondary=03, subordinate=03, sec-latency=0
    	Capabilities: <access denied>
    	Kernel driver in use: pcieport
    	Kernel modules: shpchp
    
    02:00.1 PCI bridge: VIA Technologies, Inc. VT8251 PCIE Root Port (prog-if 00 [Normal decode])
    	Flags: bus master, fast devsel, latency 0, IRQ 25
    	Bus: primary=02, secondary=04, subordinate=04, sec-latency=0
    	Capabilities: <access denied>
    	Kernel driver in use: pcieport
    	Kernel modules: shpchp
    
    02:01.0 Audio device: VIA Technologies, Inc. VT8237A/VT8251 HDA Controller
    	Subsystem: ASUSTeK Computer Inc. VT8237A/VT8251 HDA Controller
    	Flags: bus master, fast devsel, latency 0, IRQ 27
    	Memory at feafc000 (32-bit, non-prefetchable) 
    	Capabilities: <access denied>
    	Kernel driver in use: snd_hda_intel
    	Kernel modules: snd_hda_intel
    
    demo@antix1:~
    $ cat/proc/cmdline
    bash: cat/proc/cmdline: Arquivo ou diretório inexistente
    
    #45701
    Member
    marcelocripemarcelocripe

    Test on the computer that has the Gigabyte GA-8S661FXM-775 motherboard and SIS video card, using the ISO “antiX-19-legacy-bet1_386-base.iso”

    It worked similar to the test of the other motherboard with SIS video, flaws in the menus. And the video is similar to antiX 19.3 full 64 or 32 bytes in compatible video driver.

    He did not display the message he had displayed on the other computer.

    Due to the amount of memory of 512 MB, I was unable to play a video on Youtube with Firefox. The internet connection is via cable. Testing video and audio with MSTube, the video played with much higher quality than in Firefox. Consumption of RAM memory during the video in execution, according to Conky consumption of about 287 MB and in the htop consumption of RAM memory in about 323 MB and processing between 99.2 and 100%.

    I had forgotten to report that in the three tests the audio and the cable network connection worked perfectly.

    Thank you.
    marcelocripe
    (Original text in Brazilian Portuguese)

    ———-

    Teste no computador que possui a placa~mãe Gigabyte GA-8S661FXM-775 e placa de vídeo SIS, utilizando a ISO “antiX-19-legacy-bet1_386-base.iso”

    Funcionou semelhante ao teste da outra placa mãe com vídeo SIS, falhas nos menus. E o vídeo está semelhante ao antiX 19.3 full 64 ou 32 bites em driver de vídeo compatível.

    Não exibiu a mensagem que havia exibido no outro computador.

    Devido a quantidade de memória de 512 MB, não consegui tocar um vídeo no Youtube com o Firefox. A conexão com a internet é via cabo. Teste de vídeo e áudio com o MSTube, o vídeo tocou com qualidade muito superior do que no Firefox. Consumo de memória RAM durante o vídeo em execução, segundo o Conky consumo de cerca 287 MB e no htop consumo de memória RAM em cerca de 323 MB e processamento entre 99.2 e 100%.

    Eu havia me esquecido de informar que nos três testes o áudio e a conexão de rede via cabo funcionaram perfeitamente.

    Muito obrigado.
    marcelocripe
    (Texto original em Português do Brasil)

    demo@antix1:~
    $ inxi -Fxz
    System:
      Host: antix1 Kernel: 4.4.240-antix.2-486-smp i686 bits: 32 compiler: gcc 
      v: 8.3.0 Desktop: IceWM 1.9.2 
      Distro: antiX-19-legacy-bet1_386-base Lazarus 23 November 2020 
      base: Debian GNU/Linux 10 (buster) 
    Machine:
      Type: Desktop System: Hewlett-Packard product: HP dx2090 MT (AA123AV) 
      v: N/A serial: <filter> 
      Mobo: Hewlett-Packard model: 0A30 serial: <filter> BIOS: Award v: F12 
      date: 04/25/2006 
    CPU:
      Topology: Single Core model: Intel Celeron bits: 64 type: MCP 
      arch: Netburst Smithfield rev: 9 L2 cache: 256 KiB 
      flags: lm nx pae sse sse2 sse3 bogomips: 6401 
      Speed: 3201 MHz min/max: N/A Core speed (MHz): 1: 3201 
    Graphics:
      Device-1: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 
      662/761Gx PCIE VGA Display Adapter 
      vendor: Gigabyte SiS661FX GUI 2D/3D Accelerator driver: N/A 
      bus ID: 01:00.0 
      Display: x11 server: X.Org 1.16.4 driver: fbdev unloaded: modesetting,vesa 
      resolution: 1024x768~N/A 
      OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6 
      direct render: Yes 
    Audio:
      Device-1: Silicon Integrated Systems [SiS] SiS7012 AC97 Sound 
      vendor: Gigabyte driver: snd_intel8x0 v: kernel bus ID: 00:02.7 
      Sound Server: ALSA v: k4.4.240-antix.2-486-smp 
    Network:
      Device-1: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet 
      vendor: Gigabyte driver: sis900 v: kernel port: a800 bus ID: 00:04.0 
      IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
    Drives:
      Local Storage: total: 7.27 GiB used: 14.4 MiB (0.2%) 
      ID-1: /dev/sda type: USB vendor: Kingston model: DT 101 G2 size: 7.27 GiB 
    Partition:
      ID-1: / size: 320.0 MiB used: 2.4 MiB (0.8%) fs: overlay source: ERR-102 
    Sensors:
      Message: No sensors data was found. Is sensors configured? 
    Info:
      Processes: 118 Uptime: 9m Memory: 429.8 MiB used: 83.8 MiB (19.5%) 
      Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 
      inxi: 3.0.36 
    demo@antix1:~
    $ inxi -G
    Graphics:
      Device-1: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 
      662/761Gx PCIE VGA Display Adapter 
      driver: N/A 
      Display: x11 server: X.Org 1.16.4 driver: fbdev unloaded: modesetting,vesa 
      resolution: 1024x768~N/A 
      OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6 
    demo@antix1:~
    $ inxi -v8
    System:
      Host: antix1 Kernel: 4.4.240-antix.2-486-smp i686 bits: 32 compiler: gcc 
      v: 8.3.0 
      parameters: vga=0x0317 lang=pt_BR tz=America/Sao_Paulo quiet splasht 
      disable=lx 
      Desktop: IceWM 1.9.2 dm: SLiM 1.3.6 
      Distro: antiX-19-legacy-bet1_386-base Lazarus 23 November 2020 
      base: Debian GNU/Linux 10 (buster) 
    Machine:
      Type: Desktop System: Hewlett-Packard product: HP dx2090 MT (AA123AV) 
      v: N/A serial: <root required> Chassis: type: 3 serial: <root required> 
      Mobo: Hewlett-Packard model: 0A30 serial: <root required> BIOS: Award 
      v: F12 date: 04/25/2006 
    Memory:
      RAM: total: 429.8 MiB used: 87.7 MiB (20.4%) 
      RAM Report: 
      permissions: Unable to run dmidecode. Root privileges required. 
    PCI Slots:
      Permissions: Unable to run dmidecode. Root privileges required. 
    CPU:
      Topology: Single Core model: Intel Celeron bits: 64 type: MCP 
      arch: Netburst Smithfield family: F (15) model-id: 4 stepping: 9 
      microcode: 3 L2 cache: 256 KiB bogomips: 6401 
      Speed: 3201 MHz min/max: N/A Core speed (MHz): 1: 3201 
      Flags: acpi apic bts cid clflush cmov constant_tsc cx16 cx8 de ds_cpl 
      dtes64 dts fpu fxsr ht lahf_lm lm mca mce mmx monitor msr mtrr nx pae pat 
      pbe pebs pge pni pse pse36 sep ss sse sse2 tm tm2 tsc vme xtpr 
      Vulnerabilities: Type: itlb_multihit status: Processor vulnerable 
      Type: l1tf status: Vulnerable 
      Type: mds 
      status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
      Type: meltdown status: Vulnerable 
      Type: spec_store_bypass status: Vulnerable 
      Type: spectre_v1 
      mitigation: usercopy/swapgs barriers and __user pointer sanitization 
      Type: spectre_v2 
      mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
      Type: srbds status: Not affected 
      Type: tsx_async_abort status: Not affected 
    Graphics:
      Device-1: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 
      662/761Gx PCIE VGA Display Adapter 
      vendor: Gigabyte SiS661FX GUI 2D/3D Accelerator driver: N/A 
      bus ID: 01:00.0 chip ID: 1039:6330 
      Display: x11 server: X.Org 1.16.4 driver: fbdev unloaded: modesetting,vesa 
      alternate: sis resolution: 1024x768~N/A 
      OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6 
      direct render: Yes 
    Audio:
      Device-1: Silicon Integrated Systems [SiS] SiS7012 AC97 Sound 
      vendor: Gigabyte driver: snd_intel8x0 v: kernel bus ID: 00:02.7 
      chip ID: 1039:7012 
      Sound Server: ALSA v: k4.4.240-antix.2-486-smp 
    Network:
      Device-1: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet 
      vendor: Gigabyte driver: sis900 v: kernel port: a800 bus ID: 00:04.0 
      chip ID: 1039:0900 
      IF: eth0 state: up speed: 100 Mbps duplex: full mac: XX:XX:XX:XX:XX:XX (I changed the MAC to XX/ Eu alterei o MAC para XX)
      IP v4: 192.168.0.106/24 scope: global broadcast: 192.168.0.255 
      IP v6: fe80::20f:eaff:fed1:9e59/64 scope: link 
      WAN IP: 138.99.61.252 
    Drives:
      Local Storage: total: 7.27 GiB used: 14.4 MiB (0.2%) 
      ID-1: /dev/sda type: USB vendor: Kingston model: DT 101 G2 size: 7.27 GiB 
      block size: physical: 512 B logical: 512 B 
      serial: 001CC0EC330FEB816605000A rev: PMAP scheme: MBR 
      Floppy-1: /dev/fd0 
      Optical-1: /dev/sr0 vendor: TSSTcorp model: CDDVDW SH-S223C rev: SB04 
      dev-links: cdrom,cdrw,dvd,dvdrw 
      Features: speed: 52 multisession: yes audio: yes dvd: yes 
      rw: cd-r,cd-rw,dvd-r,dvd-ram state: running 
    RAID:
      Message: No RAID data was found. 
    Partition:
      ID-1: / raw size: N/A size: 320.0 MiB used: 2.4 MiB (0.8%) fs: overlay 
      source: ERR-102 label: N/A uuid: N/A 
      ID-2: /live/boot-dev raw size: 767.0 MiB size: <root required> 
      used: <root required> fs: N/A dev: /dev/ventoy label: N/A uuid: N/A 
      ID-3: /live/linux raw size: 736.9 MiB size: <root required> 
      used: <root required> fs: squashfs dev: /dev/loop0 label: N/A uuid: N/A 
      ID-4: /media/VTOYEFI raw size: 32.0 MiB size: 31.9 MiB (99.75%) 
      used: 12.0 MiB (37.4%) fs: vfat dev: /dev/sda2 label: VTOYEFI 
      uuid: ADB8-4480 
    Unmounted:
      ID-1: /dev/dm-0 size: 767.0 MiB fs: <root required> label: N/A uuid: N/A 
      ID-2: /dev/sda1 size: 7.24 GiB fs: exfat label: Ventoy uuid: 4E21-0000 
    USB:
      Hub: 1-0:1 info: Full speed (or root) Hub ports: 8 rev: 2.0 
      speed: 480 Mb/s chip ID: 1d6b:0002 
      Device-1: 1-4:2 info: Toshiba Kingston DataTraveler 102/2.0 / HEMA Flash 
      Drive 2 GB / PNY Attache 4GB Stick 
      type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0 
      speed: 480 Mb/s chip ID: 0930:6545 serial: 001CC0EC330FEB816605000A 
      Hub: 2-0:1 info: Full speed (or root) Hub ports: 3 rev: 1.1 speed: 12 Mb/s 
      chip ID: 1d6b:0001 
      Hub: 3-0:1 info: Full speed (or root) Hub ports: 3 rev: 1.1 speed: 12 Mb/s 
      chip ID: 1d6b:0001 
      Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
      chip ID: 1d6b:0001 
    Sensors:
      Message: No sensors data was found. Is sensors configured? 
    Repos:
      Active apt repos in: /etc/apt/sources.list.d/antix.list 
      1: deb http://repo.antixlinux.com/buster buster main nonfree nosystemd
      Active apt repos in: /etc/apt/sources.list.d/buster-backports.list 
      1: deb http://deb.debian.org/debian buster-backports main contrib non-free
      Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
      1: deb http://ftp.br.debian.org/debian/ buster-updates main contrib non-free
      Active apt repos in: /etc/apt/sources.list.d/debian.list 
      1: deb http://ftp.br.debian.org/debian/ buster main contrib non-free
      2: deb http://security.debian.org/ buster/updates main contrib non-free
      No active apt repos in: /etc/apt/sources.list.d/onion.list 
      No active apt repos in: /etc/apt/sources.list.d/various.list 
    Processes:
      CPU top: 5 
      1: cpu: 1.8% command: slim pid: 3194 mem: 9.81 MiB (2.2%) 
      2: cpu: 1.4% command: x pid: 3232 mem: 38.6 MiB (8.9%) 
      3: cpu: 0.5% command: conky pid: 3421 mem: 10.2 MiB (2.3%) 
      4: cpu: 0.4% command: icewm pid: 3321 mem: 13.2 MiB (3.0%) 
      5: cpu: 0.3% command: rox pid: 3419 mem: 24.8 MiB (5.7%) 
      Memory top: 5 
      1: mem: 38.6 MiB (8.9%) command: x pid: 3232 cpu: 1.4% 
      2: mem: 25.5 MiB (5.9%) command: roxterm pid: 3630 cpu: 0.2% 
      3: mem: 24.8 MiB (5.7%) command: rox pid: 3419 cpu: 0.3% 
      4: mem: 16.6 MiB (3.8%) command: volumeicon pid: 3346 cpu: 0.0% 
      5: mem: 13.4 MiB (3.1%) command: fbxkb pid: 3360 cpu: 0.0% 
    Info:
      Processes: 118 Uptime: 9m 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 
    demo@antix1:~
    $ inxi -v
    CPU: Single Core Intel Celeron (-MCP-) speed: 3201 MHz 
    Kernel: 4.4.240-antix.2-486-smp i686 Up: 9m Mem: 83.3/429.8 MiB (19.4%) 
    Storage: 7.27 GiB (0.2% used) Procs: 118 Shell: bash 5.0.3 inxi: 3.0.36 
    demo@antix1:~
    $ lspci -v
    00:00.0 Host bridge: Silicon Integrated Systems [SiS] 661FX/M661FX/M661MX Host (rev 11)
    	Subsystem: Silicon Integrated Systems [SiS] 661FX/M661FX/M661MX Host
    	Flags: bus master, medium devsel, latency 32
    	Memory at e8000000 (32-bit, non-prefetchable) 
    	Capabilities: <access denied>
    	Kernel driver in use: agpgart-sis
    	Kernel modules: sis_agp
    
    00:01.0 PCI bridge: Silicon Integrated Systems [SiS] AGP Port (virtual PCI-to-PCI bridge) (prog-if 00 [Normal decode])
    	Flags: bus master, 66MHz, fast devsel, latency 32
    	Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
    	I/O behind bridge: 00009000-00009fff
    	Memory behind bridge: ed000000-ed0fffff
    	Prefetchable memory behind bridge: e0000000-e7ffffff
    	Kernel modules: shpchp
    
    00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] LPC Controller (rev 36)
    	Flags: bus master, medium devsel, latency 0
    	Kernel modules: i2c_sis630
    
    00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 IDE Controller (rev 01) (prog-if 80 [ISA Compatibility mode-only controller, supports bus mastering])
    	Subsystem: Gigabyte Technology Co., Ltd 5513 IDE Controller
    	Flags: bus master, medium devsel, latency 32, IRQ 16
    	I/O ports at 01f0 
    	I/O ports at 03f4
    	I/O ports at 0170 
    	I/O ports at 0374
    	I/O ports at f000 
    	Kernel driver in use: pata_sis
    
    00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS7012 AC'97 Sound Controller (rev a0)
    	Subsystem: Gigabyte Technology Co., Ltd SiS7012 AC'97 Sound Controller
    	Flags: bus master, medium devsel, latency 32, IRQ 18
    	I/O ports at a000 
    	I/O ports at a400 
    	Capabilities: <access denied>
    	Kernel driver in use: snd_intel8x0
    	Kernel modules: snd_intel8x0
    
    00:03.0 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI])
    	Subsystem: Gigabyte Technology Co., Ltd USB 1.1 Controller
    	Flags: bus master, medium devsel, latency 32, IRQ 20
    	Memory at ed104000 (32-bit, non-prefetchable) 
    	Kernel driver in use: ohci-pci
    
    00:03.1 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI])
    	Subsystem: Gigabyte Technology Co., Ltd USB 1.1 Controller
    	Flags: bus master, medium devsel, latency 32, IRQ 21
    	Memory at ed100000 (32-bit, non-prefetchable) 
    	Kernel driver in use: ohci-pci
    
    00:03.2 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI])
    	Subsystem: Gigabyte Technology Co., Ltd USB 1.1 Controller
    	Flags: bus master, medium devsel, latency 32, IRQ 22
    	Memory at ed101000 (32-bit, non-prefetchable) 
    	Kernel driver in use: ohci-pci
    
    00:03.3 USB controller: Silicon Integrated Systems [SiS] USB 2.0 Controller (prog-if 20 [EHCI])
    	Subsystem: Gigabyte Technology Co., Ltd USB 2.0 Controller
    	Flags: bus master, medium devsel, latency 32, IRQ 23
    	Memory at ed102000 (32-bit, non-prefetchable) 
    	Capabilities: <access denied>
    	Kernel driver in use: ehci-pci
    
    00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90)
    	Subsystem: Gigabyte Technology Co., Ltd SiS900 PCI Fast Ethernet
    	Flags: bus master, medium devsel, latency 64, IRQ 19
    	I/O ports at a800 
    	Memory at ed103000 (32-bit, non-prefetchable) 
    	[virtual] Expansion ROM at 1c000000 [disabled] 
    	Capabilities: <access denied>
    	Kernel driver in use: sis900
    	Kernel modules: sis900
    
    00:05.0 IDE interface: Silicon Integrated Systems [SiS] RAID bus controller 180 SATA/PATA  [SiS] (rev 01) (prog-if 85 [PCI native mode-only controller, supports bus mastering])
    	Subsystem: Gigabyte Technology Co., Ltd RAID bus controller 180 SATA/PATA  [SiS]
    	Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17
    	I/O ports at ac00 
    	I/O ports at b000 
    	I/O ports at b400 
    	I/O ports at b800 
    	I/O ports at bc00 
    	I/O ports at c000 
    	Capabilities: <access denied>
    	Kernel driver in use: sata_sis
    
    00:0b.0 Modem: Motorola SM56 Data Fax Modem (rev 04) (prog-if 00 [Generic])
    	Subsystem: Motorola SM56 Data Fax Modem
    	Flags: stepping, medium devsel, IRQ 19
    	Memory at ed105000 (32-bit, non-prefetchable) 
    	I/O ports at c400 
    	Capabilities: <access denied>
    
    01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter (prog-if 00 [VGA controller])
    	Subsystem: Gigabyte Technology Co., Ltd SiS661FX GUI 2D/3D Accelerator
    	Flags: 66MHz, medium devsel, IRQ 5
    	BIST result: 00
    	Memory at e0000000 (32-bit, prefetchable) 
    	Memory at ed000000 (32-bit, non-prefetchable) 
    	I/O ports at 9000 
    	Expansion ROM at <unassigned> [disabled]
    	Capabilities: <access denied>
    demo@antix1:~
    $ cat/proc/cmdline
    bash: cat/proc/cmdline: Arquivo ou diretório inexistente
    demo@antix1:~
Viewing 15 posts - 1 through 15 (of 85 total)
  • You must be logged in to reply to this topic.