-
Search Results
-
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.36demo@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.6demo@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.36demo@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-sis00: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: shpchp00: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_sis63000: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_sis00: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_intel8x000: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-pci00: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-pci00: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-pci00: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-pci00: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_sis00: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, 8139too01: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:~4.4.240-antix.1-686-smp-pae is the only 4.4.240 antiX kernel I can see in Synaptic.
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list 1: deb http://la.mxrepo.com/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://mirror.eu.oneandone.net/debian/ buster-updates main contrib non-free Active apt repos in: /etc/apt/sources.list.d/debian.list 1: deb http://ftp.gr.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.listSystem: Host: dragon Kernel: 4.4.221-antix.2-486-smp i686 bits: 32 compiler: gcc v: 8.3.0 Desktop: IceWM 1.8.3 Distro: antiX-19_386-full Marielle Franco 16 October 2019 base: Debian GNU/Linux 10 (buster) Machine: Type: Laptop System: TOSHIBA product: Satellite 2450 v: PS245E-03TE0-GK serial: <filter> Mobo: TOSHIBA model: Portable PC v: Version A0 serial: <filter> BIOS: TOSHIBA v: Version 1.30 date: 03/20/2003 CPU: Topology: Single Core model: Intel Pentium 4 bits: 32 type: MCP arch: Netburst Northwood rev: 7 L2 cache: 512 KiB flags: pae sse sse2 bogomips: 5585 Speed: 2793 MHz min/max: N/A Core speed (MHz): 1: 2793 Graphics: Device-1: NVIDIA NV17M [GeForce4 420 Go] vendor: Toshiba America Info Systems driver: nouveau v: kernel bus ID: 01:00.0 Display: x11 server: X.Org 1.20.4 driver: nouveau unloaded: fbdev,modesetting,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI nv17 x86/MMX/SSE2 v: 1.2 Mesa 18.3.6 direct render: Yes Audio: Device-1: Intel 82801DB/DBL/DBM AC97 Audio vendor: Toshiba America Info Systems driver: snd_intel8x0 v: kernel bus ID: 00:1f.5 Sound Server: ALSA v: k4.4.221-antix.2-486-smp Network: Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter vendor: Toshiba America Info Systems driver: 8139too v: 0.9.28 port: ce00 bus ID: 02:09.0 IF: eth0 state: down mac: <filter> Device-2: Qualcomm Atheros TP-Link TL-WN821N v2 / TL-WN822N v1 802.11n [Atheros AR9170] type: USB driver: carl9170 bus ID: 1-3:6 IF: wlan0 state: up mac: <filter> Drives: Local Storage: total: 93.16 GiB used: 54.83 GiB (58.9%) ID-1: /dev/sda vendor: Toshiba model: MK1032GAX size: 93.16 GiB Partition: ID-1: / size: 89.19 GiB used: 54.83 GiB (61.5%) fs: ext4 dev: /dev/sda1 ID-2: swap-1 size: 2.00 GiB used: 164 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 69.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 132 Uptime: 1h 23m Memory: 1003.0 MiB used: 429.2 MiB (42.8%) Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.36