Search Results for 'boot from iso'

[Member Xecure]

marcelocripe wrote:

Xecure, I know it’s out of the subject of this topic, but I found it interesting to know the name of the original English menu “Manage Packages”, I searched https://www.transifex.com/anticapitalista/antix-development/viewstrings/#pt_BR , but unfortunately I did not find “Manage Packages” in the searches that I did, the searches only find the texts in English.

As it is a Control Centre entry, you will find it in the antixcc.pot section
https://www.transifex.com/anticapitalista/antix-development/viewstrings/#pt_BR/antixccpot/4368954
As you can see, it says in English “Manage packages” and in pt_BR it says “Gerenciador de Pacotes Synaptic”. You just need to remove “Synaptic from this entry, as it can be any one, synaptic or cli-aptiX (depending on availability).

Thanks for confirming that everything worked well with vesa driver. It will probably need to be the default xorg driver.

Anonymous wrote:

the fbdev driver the icons disappeared but doesn’t support 24 or 32 bit depth
Here is the xorg.conf file I’m using

Thanks, linuxdaddy.
i will try to extract the related info and see if building a iso with a xorg.conf file will boot properly on different machines and VMs. If everything goes well, I will upload a new iso.

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

[Member Xecure]

The thing with kernels is a bit complicated.
antiX brings by default a 4.9 kernel, that has all security patches included, but has more support for older computers. New machines cannot boot with it because it doesn’t bring the new drivers and patches for new processors or very new motherboards, graphic cards, etc.
For extremely old computers, the 4.4 kernel (also available in repos) seems to perform much better (also includes security patches), but is even less compatible with newer machines.
Kernel 4.19 seems to be compatible with the wider number of machines. It usually can boot any computer more than 5 years old and even some new devices.
Kernel 5.X is the newest available and supports the newest on the cutting edge hardware. Gives almost zero support for very old machines (depends on modules included), and is needed for very very recent machines.

As you see, some patches may have been included in some versions or may be removed in others.
The great variety of kernel options is to try to support as many devices as possible, each catering for different time frames.
If there was only one big kernel, it would be as big as the whole antiX iso, and you would have to manually block some newer modules (or older ones) that bring updates for some devices that break others (regressions). It is too complicated to explain, and I am not an expert, so many things could be wrong.

For now, continue with the work around. If you find something that works, let us know.

If you see something else you would like to know or fix, come back and we will help as best we can.

Regards.

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

[Member Xecure]

Thanks for the important feedback, marcelocripe.
To summarize, your experience with the vesa driver was:
– better resolution, no graphical glitches (no information about how it compared to previous performance) compared to the openchrome driver on VIA based machines.
– No graphical glitches but worked a bit slower (slower response) compared to using the fbdev driver on SIS based machines.

In more detail:
1. Computer Gigabyte GA-8S661FXM-775 and SIS video chip.
Before (with graphical glitches and fbdev driver):
driver: fbdev resolution: 1024x768~N/A
Now (no graphical glitches but slower response on vesa driver):
driver: vesa resolution: 1024×768~61Hz

2. Computer Asus P5V800-MX and VIA video chip.
Before (smaller resolution but higher refresh rate, using openchrome driver):
driver: openchrome resolution: 800x600~85Hz
Now (higher resolution on vesa driver):
driver: vesa resolution: 1024×768~N/A

3. Computer ASUS P5S800-VM and SIS video chip.
Before (fbdev driver, not sure if there are graphical glitches)
– no inxi -G info (we asume similar to the other machine with SIS video chip).
Now (No glitches, not sure about response speed, on vesa driver)
driver: vesa resolution: 1024×768~N/A

It would be good to know if using fbdev with 24 bits color depth as linuxdaddy suggests can improve the experience on SIS machines without changing to a vesa driver (mainly the icons that disappear issue, that will probably influence other strange graphical behaviors). If all SIS video chips have a slower response on vesa, maybe fbdev with proper color depth can have an improved experience. Or maybe if compiling with linuxdaddy’s suggested driver may be even better.

marcelocripe wrote:

“Centro de Controle”, em Sistema, clicando em “Gerenciador de Pacotes Synaptic”, abre o programa “Gerenciador de Aplicativos via Terminal” ou em inglês “Command line apt-based package manager”.

This is normal. On antiX base, Synaptic package manager is not installed. What is wrong is the translated text for pt_BR. That button in the menu in English is “Manage Packages”, and will launch Synaptic Package Manager if it is installed. If it is not installed, it will launch cli-aptiX instead. So the translation shouldn’t mention Synaptic package manager, but only “Package manager”. Anyway, that is not an error so we can consider it normal behavior.

marcelocripe wrote:

Linuxdaddy, I would like to know more to be able to help you both in the development,

Your tests and experience are the most important feedback to let us know how everything is going. That is more than enough.

marcelocripe wrote:

If there is a way to install with “vesa” and after installation always start with “vesa” I believe that it will no longer present the problems in the display of ISO menus “antiX-19-legacy-bet1_386-base.iso” that occur in normal mode.

For live booting, using “xorg=safe” is enough (I think). For installed systems, uninstalling xserver-xorg-video-fbdev for SIS systems and xserver-xorg-video-openchrome for VIA computers should be enough, but that is not possible right now, as I didn’t install them separately from main xserver-xorg package.

I will improve that aspect and hopefully tomorrow get a new iso out, which you can test next week and weekend. Sleep well and make use only on big chunks of time. You say you spend a lot of time during the week moving on public transport, and getting home late and tired. Rest and leave the tests for the weekend.

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

[Member marcelocripe]

Xecure wrote:
For those, marcelocripe, follow linuxdaddy’s advice and load them on safe video mode (to use the vesa driver) and see if they perform better than with the vesa driver on antiX 19.3.

Test on the computer that has the Gigabyte GA-8S661FXM-775 motherboard, using the ISO “antiX-19-legacy-bet1_386-base.iso” and starting in “Safe Video Mode”

In “Boot options”: quiet splasht disable = lx nomodeset xorg = safe

Desktop: Rox-IceWM

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: vesa resolution: 1024 × 768 ~ 61Hz
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Table 18.3.6

The menu images do not disappear as they do when you start in normal mode, only once the submenus of the “Applications” menu have become disorganized or out of the normal order. After I clicked “Update the Menu”, they were all organized and in the normal order. I noticed that the response of the left mouse click is difficult, it takes time for antiX to receive the command. The “Synaptic Package Manager” is not displayed in the “System” submenu. Using the menu “Select the Application” or “Control Center”, in System, clicking on “Synaptic Package Manager”, opens the program “Application Manager via Terminal” in English “Command line apt-based package manager”.

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” and starting in “Safe Video Mode”

In “Boot options”: quiet splasht disable = lx nomodeset xorg = safe

Desktop: Rox-IceWM

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: vesa resolution: 1024×768 ~ N / A
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Table 18.3.6

The menu images do not disappear as they do when you start in normal mode, the submenus of the “Applications” menu are not displayed. After I clicked “Update the Menu”, it did not display the submenus of the “Applications” menu. In the terminal I again applied the PPC suggestion to use a command as an administrator (root) to allow updating the menu.

$ sudo free {Enter}

After applying the above command, I clicked on the “Update Menu” menu, the submenus of the “Applications” menu were displayed and they were all organized and in the normal order. Using the menu “Select the Application” or “Control Center”, in System, clicking on “Synaptic Package Manager”, opens the program “Application Manager via Terminal” in English “Command line apt-based package manager”.

In the case of the Asus P5V800-MX motherboard, a detail that I found important, when antiX was booted in normal mode, the resolution was 800×600. When started with Safe Video Mode, the resolution was 1024×768.

Test on the computer that has the ASUS P5S800-VM motherboard and SIS video card, using the ISO “antiX-19-legacy-bet1_386-base.iso” and starting in “Safe Video Mode”

In “Boot options”: quiet splasht disable = lx nomodeset xorg = safe

Desktop: Rox-IceWM

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: vesa resolution: 1024 × 768 ~ N / A
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Table 18.3.6

The menu images do not disappear as they do when you start in normal mode, the sub-menus of the “Applications” menu are organized normally. The “Synaptic Package Manager” is not displayed in the “System” submenu. Using the “Select the Application” or “Control Center” menu, under System, clicking on “Synaptic Package Manager”, opens the “Application Manager via Terminal” program or in English “Command line apt-based package manager” .

Linuxdaddy, I would like to know more to be able to help you both in the development, but unfortunately I do not understand several terms that you and Xecure use, such as: build-iso tool, make compilation (or I still don’t know how to do this) and other arguments.

If there is a way to install with “vesa” and after installation always start with “vesa” I believe that it will no longer present the problems in the display of ISO menus “antiX-19-legacy-bet1_386-base.iso” that occur in normal mode.

I hope this information is useful.

marcelocripe
(Original text in Brazilian Portuguese)

———-

Xecure wrote:
For those, marcelocripe, follow linuxdaddy’s advice and load them on safe video mode (to use the vesa driver) and see if they perform better than with the vesa driver on antiX 19.3.

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

Em “Opções de inicialização”: quiet splasht disable=lx nomodeset xorg=safe

Área de trabalho: Rox-IceWM

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: vesa resolution: 1024×768~61Hz
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6

As imagens dos menus não desaparecem como acontece quando inicia no modo normal, apenas uma vez os submenus do menu “Aplicações” ficaram desorganizados ou fora da ordem normal. Após eu clicar em “Atualizar o Menu”, ficaram todos organizados e na ordem normal. Eu observei que a resposta do clique do botão esquerdo do mouse está difícil, demora para o antiX receber o comando. O “Gerenciador de Pacotes Synaptic” não é exibido no submenu “Sistema”. Utilizando o menu “Selecione o Aplicativo” ou o “Centro de Controle”, em Sistema, clicando em “Gerenciador de Pacotes Synaptic”, abre o programa “Gerenciador de Aplicativos via Terminal” em inglês “Command line apt-based package manager”.

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” e inciando em “Modo de Vídeo Seguro”

Em “Opções de inicialização”: quiet splasht disable=lx nomodeset xorg=safe

Área de trabalho: Rox-IceWM

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: vesa resolution: 1024×768~N/A
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6

As imagens dos menus não desaparecem como acontece quando inicia no modo normal, os submenus do menu “Aplicações” não são exibidos. Após eu clicar em “Atualizar o Menu”, não exibiu os submenus do menu “Aplicações”. No terminal apliquei novamente a sugestão do PPC de usar um comando como administrador (root) para permitir a atualização do menu.

$ sudo free {Enter}

Após aplicar o comando acima, eu cliquei no menu “Atualizar o Menu”, os submenus do menu “Aplicações” forma exibidos e ficaram todos organizados e na ordem normal. Utilizando o menu “Selecione o Aplicativo” ou o “Centro de Controle”, em Sistema, clicando em “Gerenciador de Pacotes Synaptic”, abre o programa “Gerenciador de Aplicativos via Terminal” em inglês “Command line apt-based package manager”.

No caso da placa~mãe Asus P5V800-MX, um detalhe que eu achei importante, quando o antiX foi inicializado com o modo normal, a resolução foi de 800×600. Com a inicialização com o Modo de Vídeo Seguro a resolução foi de 1024×768.

Teste no computador que possui a placa~mãe ASUS P5S800-VM e placa de vídeo SIS, utilizando a ISO “antiX-19-legacy-bet1_386-base.iso” e inciando em “Modo de Vídeo Seguro”

Em “Opções de inicialização”: quiet splasht disable=lx nomodeset xorg=safe

Área de trabalho: Rox-IceWM

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: vesa resolution: 1024×768~N/A
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6

As imagens dos menus não desaparecem como acontece quando inicia no modo normal, os submenus do menu “Aplicações” estão organizados normalmente. O “Gerenciador de Pacotes Synaptic” não é exibido no submenu “Sistema”. Utilizando o menu “Selecione o Aplicativo” ou o “Centro de Controle”, em Sistema, clicando em “Gerenciador de Pacotes Synaptic”, abre o programa “Gerenciador de Aplicativos via Terminal” ou em inglês “Command line apt-based package manager”.

Linuxdaddy, eu gostaria de conhecer mais para poder ajudar vocês dois no desenvolvimento, mas infelizmente eu não compreendo diversos termos que você e o Xecure utilizam, como por exemplo: ferramenta build-iso, fazer compilação (ou ainda não sei como fazer isso) e outros argumentos.

Se houver um meio de instalar com o “vesa” e após a instalação sempre iniciar com “vesa” eu acredito que não apresentará mais os problemas na exibição dos menus da ISO “antiX-19-legacy-bet1_386-base.iso” que ocorrem no modo normal.

Eu espero que estas informações sejam úteis.

marcelocripe
(Texto original em Português do Brasil)

[Member Xecure]

If possible, try downloading the latest 19.3 iso with 4.19 kernel from cica (Andalucia/Spain):
https://ftp.cica.es/mirrors/Linux/MX-ISOs/ANTIX/Final/antiX-19/4.19_kernel/antiX-19.3_x64-full.iso

If you cannot use a USB stick to install and can only use a CD, let me know and I will try to make a base iso smaller.

roland wrote:

I’m not sure how to locate and install the kernel you suggest (4.19.152) if it doesn’t appear in the kernel list presented by the package installer.

It is somewhat difficult to see in the package installer, you are right. This is the way to see the version that will be installed:

But first try booting the linked iso live and see if on a live session connecting to wifi also freezes the computer.

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

[Member marcelocripe]

linuxdaddy wrote:
As far as the menus repeating hit refresh menu upon first boot and that straightens them up.

Tests with the Gigabyte GA-8S661FXM-775 motherboard and ISO “antiX-19-legacy-bet1_386-base.iso”,

I tried to update the menu, all images appear again in the menu. If you slide the mouse cursor over the menus, all of them disappear, except the first of each menu or submenu.

In the terminal I tried:

$ sudo free {Enter}

$ sudo desktop-menu –write-out-global {Enter}

But the same effect happens.

Linuxdaddy, did I do the tests right?

Thankful.
marcelocripe

———-

linuxdaddy wrote:
As far as the menus repeating hit refresh menu upon first boot and that straightens them up.

Testes com a placa-mãe Gigabyte GA-8S661FXM-775 e a ISO “antiX-19-legacy-bet1_386-base.iso”,

Eu tentei fazer a atualização do menu, todas as imagens aparecem novamente no menu. Se deslizar o cursor do mouse sobre os menus, todos desaparecem, exceto o primeiro de cada menu ou submenu.

No terminal eu tentei:

$ sudo free {Enter}

$ sudo desktop-menu –write-out-global {Enter}

Mas o mesmo efeito acontece.

Linuxdaddy, eu fiz certo os testes?

Grato.
marcelocripe

[Member kouroukinos77]

Hello,

I save all my data on an external hard drive, and format for reinstall this distro. Very difficult for me. And because I don’t want to reinstall all program, I need to reuse old program and old config. For some applications, so I need to use Android and Etch Droid for create antix boot iso on USB key.

I’m sorry for doing this, and I would like to know what not to do took it all. so as not to reproduce this formatting loop that I do every month for my computer and smartphone. Thank you all.

$ uname -r
4.9.212-antix.1-amd64-smp
Mon retour de inxi -Fxz : https://pastebin.com/kqRMrRZZ
my xmpp : weerbor@jabber.fr

[Member Xecure]

Thanks for the tests, marcelo. If it is similar experience to antiX 16 but better than the default 19 for those old sis and via chips, then we are improving. If the experience is worse than original antiX 19, then this project is going nowhere.
I will try to figure out what is going on with the menu script, but probably it would be fixed as linuxdaddy suggests.

Anonymous wrote:

As far as the menus repeating hit refresh menu upon first boot and that straightens them up.

Thanks for helping, linuxdaddy. If you can test it on your sis machine and it boots to a graphical interface using openchrome xorg driver, then we can confirm that this project has a future. It isn’t the safest antiX version, but it can complement it for machines that have problems booting with the original.

I will try building a new iso on the weekend and see if some improvements can be made (including autolog-in and figuring out the icon and menu problems).
About the firmware package firmware-netronome, as it doesn’t seem to be common, I will remove it from the lists.

Thanks everyone for your input.

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

[Anonymous]

hi eveyone,

I haven’t been on much and will have to read this whole thread over the weekend.
have one tower with the sis 760lv chip on a via board with an amd sempron. It has never
worked right on linux except on vesa drivers.
I can set it up as a test box for the iso on bare-metal live/install.
As far as the menus repeating hit refresh menu upon first boot and that straightens them up.

[Member Xecure]

Those RAM results are too strange. I think something must be broken on the iso because of some misconfiguration while building it.
Autologing can be set from the Control Centre, so it is only a loss on live boot.
I should have reinstalled Virtualbox-guest packages to recompile the driver for the old xorg version and the 4.4 kernel. I was just glad this iteration worked after too many fails, and decided to publish it after some light tests on the VM so marcelo could test if the openchrome driver worked out of the box. There is still a lot to fine tune, and now I need to figure out what things I broke before next version.

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

[Member PPC]

@Xecure – thinking about trying your antiX version on my parents old 32 bits laptop, I downloaded the iso and tried it as a live cd, on virtual box:
– Conky says it uses 70.4Mb out of the box
– Menus look fine, even the desktop entries
– I missed the Old log in screen picture!- it comes out every time, that’s not bad- it’s a nice security feature (that I myself don’t normally use) not using auto-log-on – it’s a tiny detail, I can change the log-on wallpaper to the blured lines one, to better match the default wallpaper (or change the default wallpaper to match the very nice log-on)
– Virtualbox video from the grub screen does not seem to work- safe video mode works fine- it even allows viewing youtube videos comfortably on smtube
– extremely fast and light on RAM!
– My virtual system has only half Gig of RAM- I did that on purpose, to test how antiX would behave that way- Firefox slows to a crawl in no time, because of heavy swap use- as is to be expected!
– I tried twice installing Palemoon- it freezes the system, after installing from package manager…
– It would be nice if we had some kind of portable office we could test in 32bits (LibreOffice appimages are 64 bits only)- since Palemoon gave me trouble on a VM, I won’t even try LO)
– As it is, except for the palemoon trouble (it could be VM related), it’s a nice, fast, light, and very legacy compatible system…

EDIT: just to see how low this could go: I booted the live VM in min-fluxbox: “free -h” on rox-term reports “47Mb” being used 😮 !!! If this system doesn’t run on a computer it’s because it’s on the bottom of a trash compactor 🙂

P.

• This reply was modified 2 years, 5 months ago by PPC.

[Member marcelocripe]

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:~

[Member marcelocripe]

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

[Anonymous]

> 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?

[Member ModdIt]

You ask.
if i customize my antiX by removing and adding certain packages, is there a way to compare what i’ve added or removed against the normal base install, and create a script replicating those changes? if so, clean installs between major releases might sound less daunting since it’d remove the need for me to redo everything.

AntiX is somewhat like an operating system swiss army knife, most tools are already present. please just take your time to find your way around.

Usually no need to write anything for what you envisage because the antiX snapshot tool creates an ISO with all the changes you have made to an installed system.
You would need to select personal when you use the tool as that preserves your changes.
Just make sure you are able to boot a stick or DVD prepared with that tool.

You write: i don’t think i have an interest in using a remaster, since i only use antiX on a single low-end laptop from its HDD.

You would, to be safe create some kind of a backup of your system, the remaster/snapshot is that and a portable system all rolled in to one ISO file.
If you end up with a huge remaster or snapshot some BIOS may not allow it to boot, way round is trim during snapshot, backup data.

I reinstall my anchient EEPC (fitted with SSD) in roundabout 10 to 12 Minutes. That is, a complete reinstall and back to desktop and uses a
snapshot made on a completely different system.
Differences-Snapshot/Remaster. I remaster a live USB boot running system after changes. Snapshot creates an ISO image of the installed system.

I make risky changes where possible on the live system, it takes longer but my installed system is safe, if I break something a reboot brings me back
to working state.

Please take a read https://antixlinux.com/the-most-extensive-live-usb-on-the-planet
Silly for me to repeat more here.

• This reply was modified 2 years, 5 months ago by ModdIt.
• This reply was modified 2 years, 5 months ago by ModdIt.