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

[Anonymous]

Helpful

Up

0

::

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

marcelocripe wrote:
If I am not mistaken in Windows there is an option to change the amount of colors from 32 bits to 24 bits for the video card. Would it be something equivalent to that depth?
that is exactly correct. we are only changing this for the driver.

[Member Xecure]

Helpful

Up

0

::

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.

[Anonymous]

Helpful

Up

0

::

@xecure,

did an experiment and
apparently it is a problem only with buster version of xorg. this
is a sid/bullseye core build up and it works in 16 bit and 24 bit
with no icon disappearing problem.
I had to add a display subsection under screen for the desktop
resolutions though in xorg.conf for my monitor. it was trying to set it
for 1600×1200 but my monitor stops at 1280×1024 and was going to sleep
… so not an automatic fits all solution.
could try putting bullseye xorg on hold with the buster iso and not hold any
other packages back.

[Moderator Brian Masinick]

Helpful

Up

0

::

great find linuxdaddy! Glad you found a solution for your configuration.

--
Brian Masinick

[Member Xecure]

Helpful

Up

0

::

Anonymous wrote:

did an experiment and
apparently it is a problem only with buster version of xorg. this
is a sid/bullseye core build up and it works in 16 bit and 24 bit
with no icon disappearing problem.

This means that (probably) building an iso for testing with the new xorg version instead of trying to hold the old xorg package from jessie is a better path.
Then this will probably be the last iso I build, as this will become a fruitless endeavor if newer xorg versions fix the issues with SIS and VIA video cards.

It is good news for the future of old machines. Less work for reviving them. This was going to be the next beta2 iso (740MB, autologin, semifix to virtualbox video, removed the firmware, included some of skidoo’s suggestions, added synaptic, could not get a good way to setup xorg.conf automatically that worked, so this will not be included), but I will next try to build an iso with bullseyes repos to see if it will boot for marcelocripe.

Thanks for all the tests, linuxdaddy. It lead to a possible better path than keeping an alternative separate version with low support.

Thank you everyone for participating. This was a learning experience for me.

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

[Member seaken64]

Helpful

Up

0

::

I’ve been reading this thread with interest. Unfortunately, I don’t think I grasp everything. I understand that Marcelocripe has some old machines that don’t work well with the standard antiX-19 and that Xecure has been trying to provide an alternate iso that may work better on those machines. One approach was to replace the Xorg package with the package from antiX-16, is that correct? I’ve never quite got a handle on how all of this works, but will an older Xorg package continue to work with other programs that may require a dependency on the current Xorg files? Maybe a desktop environment or video editor, or something like that?

For what it is worth, I have one laptop that use the VIA Graphics. So far, I have been able to use this machine in antiX-16, antiX-17, and antiX-19 with no problems. It always uses the OpenChrome driver for Xorg and I am able to use the default screen size of 1280×768. I’ve had no video problems with the apps that I use, such as SMTube or Streamlight, or mpv, or VLC, etc. Apparently marcelocripe has different chips and get different results. I have another system that uses an Intel integrated graphics chip that was not supported and I had to get help from BitJam and others on this forum to set it up with the GUI. So I understand that sometimes the video does not get setup correctly from the standard iso download. But if I recall I only had to force an install of an alternate driver module. Apparently this is not always the case and no driver will solve the problem. In these cases is it a combination of the kernel, Xorg, and drivers? Is it that the driver files have not been maintained to support the newer Xorg and/or kernel?

I also have a keen interest in keeping old computers alive and out of the trash. I hope I can learn how all of these parts of the puzzle fit together so I can contribute to efforts such as those on display here in this forum. If marcelocripe and xecure are successful in getting marcelocripes computers working with antiX-19 it will go a long way toward all of us learning how to massage linux to our own goals. I only have this one laptop that uses the VIA graphics but if my testing will help I will do what I can.

I downloaded the legacy-bet1 iso file that xecure provided and booted it on this Gateway MX3210 laptop, which uses the VIA graphics chipset. It booted to the GUI with no problem and inxi shows the OpenChrome driver for Xorg. But the WiFi does not work. I compared the inxi to the previously installed antiX-19.1 which has been fully upgraded as of today. The graphics driver is the same with the correct resolution for this laptop on both. I’ll paste the inxi output below.

Also, it seems to me that a working WiFi is at least as important as a working graphics. Maybe this beta1 test is only focused on the graphics for now? and the WiFi will be working later?

Thank you all for you hard work. This has always been one of my favorite things about antiX. antiX developers and users appreciate that an old piece of equipment still has some value, even if only to a small handful of the world’s computer users.

Seaken64

Here’s the inxi outputs. The first is the beta1 test on a LiveUSB, the second is my installed and current antiX-19 on the hard drive.

$ 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: Portable System: Gateway product: MX3210 v: 73.03 serial: <filter> 
  Mobo: Gateway model: N/A v: Rev1.73.03 serial: <filter> BIOS: Phoenix 
  v: 73.03 date: 01/06/2006 
Battery:
  ID-1: BAT0 charge: 20.9 Wh condition: 21.1/48.8 Wh (43%) 
  model: Gateway W32044L status: Charging 
CPU:
  Topology: Single Core model: Intel Celeron M bits: 32 type: MCP 
  arch: M Dothan rev: 8 L2 cache: 1024 KiB 
  flags: pae sse sse2 bogomips: 2793 
  Speed: 1397 MHz min/max: N/A Core speed (MHz): 1: 1397 
Graphics:
  Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] 
  vendor: Gateway driver: N/A bus ID: 01:00.0 
  Display: x11 server: X.Org 1.16.4 driver: openchrome 
  unloaded: fbdev,modesetting,vesa resolution: 1280x768~60Hz 
  OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6 
  direct render: Yes 
Audio:
  Device-1: VIA VT8233/A/8235/8237 AC97 Audio vendor: Gateway 
  driver: snd_via82xx v: kernel bus ID: 00:11.5 
  Sound Server: ALSA v: k4.4.240-antix.2-486-smp 
Network:
  Device-1: Broadcom Limited BCM4318 [AirForce One 54g] 802.11g Wireless LAN 
  driver: N/A bus ID: 00:0e.0 
  Device-2: VIA VT6102/VT6103 [Rhine-II] vendor: Gateway driver: via-rhine 
  v: N/A port: 1800 bus ID: 00:12.0 
  IF: eth0 state: down mac: <filter> 
Drives:
  Local Storage: total: 44.72 GiB used: 789.2 MiB (1.7%) 
  ID-1: /dev/sda vendor: Hitachi model: HTS424040M9AT00 size: 37.26 GiB 
  ID-2: /dev/sdb type: USB vendor: Lexar model: USB Flash Drive 
  size: 7.46 GiB 
Partition:
  ID-1: / size: 364.0 MiB used: 2.2 MiB (0.6%) fs: overlay source: ERR-102 
  ID-2: swap-1 size: 896.0 MiB used: 52 KiB (0.0%) fs: swap dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 56.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 114 Uptime: 4m Memory: 479.1 MiB used: 98.2 MiB (20.5%) 
  Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 
  inxi: 3.0.36 

$ inxi -Fxz
System:
  Host: 3210antix19 Kernel: 4.9.200-antix.1-486-smp i686 bits: 32 
  compiler: gcc v: 8.3.0 Desktop: IceWM 1.9.2 
  Distro: antiX-19.1_386-base Marielle Franco 23 December 2019 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Portable System: Gateway product: MX3210 v: 73.03 serial: <filter> 
  Mobo: Gateway model: N/A v: Rev1.73.03 serial: <filter> BIOS: Phoenix 
  v: 73.03 date: 01/06/2006 
Battery:
  ID-1: BAT0 charge: 20.9 Wh condition: 21.1/48.8 Wh (43%) 
  model: Gateway W32044L status: Charging 
CPU:
  Topology: Single Core model: Intel Celeron M bits: 32 type: MCP 
  arch: M Dothan rev: 8 L2 cache: 1024 KiB 
  flags: pae sse sse2 bogomips: 2793 
  Speed: 1397 MHz min/max: N/A Core speed (MHz): 1: 1397 
Graphics:
  Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] 
  vendor: Gateway driver: N/A bus ID: 01:00.0 
  Display: x11 server: X.Org 1.20.4 driver: openchrome 
  unloaded: fbdev,modesetting,vesa resolution: 1280x768~60Hz 
  OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 
  direct render: Yes 
Audio:
  Device-1: VIA VT8233/A/8235/8237 AC97 Audio vendor: Gateway 
  driver: snd_via82xx v: kernel bus ID: 00:11.5 
  Sound Server: ALSA v: k4.9.200-antix.1-486-smp 
Network:
  Device-1: Broadcom Limited BCM4318 [AirForce One 54g] 802.11g Wireless LAN 
  driver: b43-pci-bridge v: N/A bus ID: 00:0e.0 
  Device-2: VIA VT6102/VT6103 [Rhine-II] vendor: Gateway driver: via-rhine 
  v: N/A port: 1800 bus ID: 00:12.0 
  IF: eth0 state: down mac: <filter> 
  IF-ID-1: wlan0 state: up mac: <filter> 
Drives:
  Local Storage: total: 44.72 GiB used: 4.69 GiB (10.5%) 
  ID-1: /dev/sda vendor: Hitachi model: HTS424040M9AT00 size: 37.26 GiB 
  ID-2: /dev/sdb type: USB vendor: Lexar model: USB Flash Drive 
  size: 7.46 GiB 
Partition:
  ID-1: / size: 7.65 GiB used: 3.92 GiB (51.2%) fs: ext4 dev: /dev/sda7 
  ID-2: swap-1 size: 896.0 MiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 51.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 128 Uptime: 2m Memory: 477.3 MiB used: 90.6 MiB (19.0%) 
  Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 
  inxi: 3.0.36 

[Moderator Brian Masinick]

Helpful

Up

0

::

@seaken64: Nice work with that system. I used to have a Gateway 2000 17″ “portable”; I hesitated to call it a laptop because it was pretty big, heavy, but it could be moved easier than a desktop.

I’m not sure about your model(s) but it looks like your hardware comes from a very similar time period as my old Gateway. I used that old system for more distributions than anything else; the closest may have been my “ancient” Dell 4100 desktop computer. I had the Gateway 2000 17″ PA6A from 2007-2018 and I had the Dell 4100 desktop from 2001-2009.

My current laptop is a Dell Inspiron 5558.
‘
I have a few other units given to me “free” instead of landing in a recycling center or a dump. I run either antiX or MX Linux on all of them.

--
Brian Masinick

[Member Xecure]

Helpful

Up

0

::

Thanks for testing seaken64.
Marcelo wasn’t able too get the antiX 19 to boot with the openchrome driver, and the vesa driver on his machine was very slow. He tested also antiX 17, with openchrome and vesa, and it also performed to slow graphically. The only acceptable result was using an antix 16 release.
As he states in the first page, he has had trouble with the newer xorg version released in Debian buster, and has been trying different linux distros.
We weren’t sure how to get the newer versions of antiX to work on his machines, so I tried with the lowest supported antiX kernel and with the xorg version in antiX 16. This is what lead to me trying to build it using the build-iso tool created by anticapitalista and co.

If your experience is almost the same between normal antiX and this version, then there is hope that there is no need for what I am trying to do and there is a better workaround, which we may find may also work on marcelocripe’s old machines.

seaken64 wrote:

Network:
Device-1: Broadcom Limited BCM4318 [AirForce One 54g] 802.11g Wireless LAN
driver: b43-pci-bridge

My guess is that you used Network Assistant to unblacklist the b43 broadcom drivers on your antiX 19.1 installation, and that is why wifi works on your system. But maybe I have made some mistake and blacklisted drivers that are available on the default antiX 19 version. I experimented with editing many files, but I don’t remember touching modprobe files, but I can entirely be to blame for this. Sorry for that.

If linuxdaddy’s discovery of using the xorg version in Debian Testing/sid for getting SIS video chips to work properly also applies to marcelocripe’s case, then it would be even better. Hopefully Debian is working on keeping and maintaining old hardware working, and I was completely wrong. Debian Bullseye may be a better release compared to buster and bring back life to old systems. Let us hope.

Again, thanks for testing. This has been a learning experience for me. If on the next iso based on testing I send to marcelocripe works on his machines, we can say that these tests were worth it.

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

[Member seaken64]

Helpful

Up

0

::

Thank you Xecure. That is a good synopsis. I appreciate your work. Ultimately you may be instrumental in teaching us how to keep these old machines alive with antiX.

Yes, I may have modified the blacklist file. It’s been awhile and I can’t remember. I will try to look at that on the beta1 test iso LiveUSB and let you know what happens.

Seaken64

Edit: Yes, I can confirm that using the Network Assistant in the CC I was able to get WiFi working on the beta1 test iso LiveUSB. Thanks again.

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

[Member marcelocripe]

Helpful

Up

0

::

Seaken64,

Thank you very much for participating in this topic.

Xecure,

Thank you very much for all your effort and work.

Today I can send the results of the first tests with the ISO “antiX-19-legacy-bet2_386-base.iso”.

ASUS P5S800-VM motherboard:
-I started in normal mode, Rox-IceWM, displayed a message on the screen “No frame was in use … the ‘Standard’ frame was selected. Use ‘rox -p = Defaut’ to enable it in the future. ”

Conky displays the 62.9 MB RAM consumption of the 936 MB available (two 512 MB DDR cards), $ sudo free {Enter} 63.62 MB RAM consumption of the 958 MB.

The images of the menu icons disappear when the mouse arrow passes over the menus, the submenus of “Applications” are out of the normal order and appear disorganized, it has only antiX, Accessories and System. When I click on the “Update Menu” menu, all the icons appear again, but disappear when the mouse arrow passes over the menus. The opening of the programs is very similar to that of antiX 19.3 on a compatible motherboard. The “bet2” system is more fluid than the “bet1” version, there is a clear improvement in the response and in the movement of the windows of open programs, I opened several programs until the consumption of RAM reached 302 MB.

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

$ inxi -S
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-bet__386-base Lazarus 29 November 2020
base: Debian GNU / Linux 10 (buster)

I changed from Rox-IceWM to Space-IceWM, the images of the menu icons do not disappear when the mouse arrow passes over the menus, the submenus of “Applications” are out of the normal order and appear disorganized, it has only antiX, Accessories and System .

The Minimal-IceWM and IceWM workspace menus are similar to Rox-IceWM.

I kept the various programs open and checked how the menus behave in each work area: Fluxbox, Minimal-Fluxbox, Rox-Fluxbox, Space-Fluxbox, during the change from Space-Fluxbox to JWM a crash occurred, the two memories are tested and approved with antiX 19.3 64 bit full memtest. All menus are OK and have no defects.

I restarted the computer with the power button, antiX started with Rox-IceWM, changed it to JWM, the images of the menu icons do not disappear when the mouse arrow passes over the menus, the submenus of “Applications” are out of the normal order and appear disorganized, it has only the antiX submenu. Then Minimal-JWM, Rox-JWM, Space-JWM, all behave as I described JWM.

I restarted the computer, safe video mode, Rox-IceWM, the images of the menu icons do not disappear when the mouse arrow passes over the menus, the submenus of “Applications” are out of the normal order and appear disorganized, it has only antiX, Accessories and System.

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.1 Table 18.3.6

Using Firefox 78.5.0esr (32 bit) playing a 21min4s video from YouTube, antiX started in safe mode has a much higher quality in the image than if the same video is played in normal antiX startup mode.

As soon as possible I will repeat the same tests on the other two computers.

Thanks.

marcelocripe
(Original text in Brazilian Portuguese)

———-

Seaken64,

Muito obrigado por participar deste tópico.

Xecure,

Muito obrigado por todo o seu empenho e trabalho.

Hoje eu consigo enviar os resultados dos primeiros testes com a ISO “antiX-19-legacy-bet2_386-base.iso”.

Placa-mãe da marca ASUS P5S800-VM:
-Iniciei no modo normal, Rox-IceWM, 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.”.

O Conky exibe o consumo de memória RAM de 62,9 MB dos 936 MB disponíveis (duas placas de 512 MB DDR), $ sudo free {Enter} consumo de memória RAM de 63,62 MB dos 958 MB.

As imagens dos ícones do menus somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão fora da ordem normal e surgem desorganizados, possui apenas antiX, Acessórios e Sistema. Quando eu clico no menu “Atualizar o Menu”, todos os ícones aparecem novamente, mas somem quando a seta do mouse passa sobre os menus. A abertura dos programas está muito semelhante a do antiX 19.3 em placa-mãe compatível. O sistema “bet2” está mais fluído do que a versão “bet1”, é nítido a melhora na resposta e na movimentação das janelas dos programas abertos, eu abri vários programas até o consumo de memória RAM chegar até 302 MB.

demo@antix1:~
$ inxi -G
Resultado do comando no texto em inglês

$ inxi -S
Resultado do comando no texto em inglês

Alterei de Rox-IceWM para Space-IceWM, as imagens dos ícones do menus não somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão fora da ordem normal e surgem desorganizados, possui apenas antiX, Acessórios e Sistema.

O menus da área de trabalho Minimal-IceWM e IceWM estão semelhantes ao Rox-IceWM.

Eu mantive os vários programas abertos e verifiquei como os menus se comportam em cada área de trabalho: Fluxbox, Minimal-Fluxbox, Rox-Fluxbox, Space-Fluxbox, durante a troca de Space-Fluxbox para JWM ocorreu um travamento, as duas placas de memórias estão testadas e aprovadas com o memtest do antiX 19.3 64 bits full. Todos os menus estão Ok e não apresentam qualquer tipo de defeito.

Reiniciei o computador com o botão liga/desliga, o antiX iniciou com o Rox-IceWM, alterei para JWM, as imagens dos ícones do menus não somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão fora da ordem normal e surgem desorganizados, possui apenas o submenu antiX. Em seguida Minimal-JWM, Rox-JWM, Space-JWM, todos se comportam como descrevi o JWM.

Reiniciei o computador, modo de vídeo seguro, Rox-IceWM, as imagens dos ícones do menus não somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão fora da ordem normal e surgem desorganizados, possui apenas antiX, Acessórios e Sistema.

demo@antix1:~
Resultado do comando no texto em inglês

Utilizando o Firefox 78.5.0esr(32 bit) tocando um vídeo de 21min4s do YouTube, no antiX iniciado no modo seguro possui uma qualidade muito superior na imagem do que se for tocado o mesmo vídeo no modo normal da inicialização do antiX.

Assim que possível irei repetir os mesmos testes nos outros dois computadores.

Obrigado.

marcelocripe
(Texto original em Português do Brasil)

[Member Xecure]

Helpful

Up

0

::

Thanks for the tests, marccelocripe. If you see safe video works as fast as with normal video on the SIS systems, try installing the beta2 on the machine (booted in safe video mode) and see how it goes. You installed porteus in one of them, so install antiX and compare the fluidity in comparison. It should work exactly the same as normal antiX on a similar system.

I think the ISO already is production ready for your machine. I will probably experiment a bit more in the future by holding older amd/intel graphics firmware package if more people report having issues with antiX 19.3 (for now only one case).

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

[Member marcelocripe]

Helpful

Up

0

::

Xecure,

I did test Porteus, but they weren’t good tests (I think I wasted my time …):

The latest version “Porteus-OPENBOX-v5.0rc2-x86_64.iso” has not even booted in graphical mode. I reported the tests I did and the flaws I found in the English language and in Portuguese.

The Porteus community, unfortunately, falls far short of this antiX community, the answers were extremely technical and aimed at those who have known Porteus for many years, they are not useful or sufficient for a beginner in this operating system.

The previous version “Porteus-OPENBOX-v5.0rc1-x86_64.iso”, starts in graphical mode, in a fluid way similar to the ISO “antiX-19-legacy-bet2_386-base.iso”. But, as the Porteus RAM memory consumption is approximately 155 MB, the response when opening programs is slower than in antiX. When trying to install, the Porteus partition manager does not start, I tried to install on an existing partition and the process started, I received the message “completed successfully”. After restarting the computer (which I described in the tests below with the ISO “antiX-19-legacy-bet2_386-base.iso”) it stopped on the black screen, in addition to displaying several errors. I will not waste any more time reporting failures in that community. I reported on the 17th and 18th of November 2020, I returned to the forum today, just to be able to inform you of the links and answer you with as much information as possible and complete. The forum answers do not help a beginner to solve the problem alone. The problem seems to be with the ISO. I got tired of seeing this in SliTaz, with each new ISO several new problems for users to be testing and having to solve everything on their own. In people’s lives, there are already many problems, operating systems need to offer solutions, instead of new problems.

Let’s go to what really interests us, antiX. This one is worth it, the community and antiX make every minute spent worthwhile, whether in tests or to collaborate with the operating system.

Results of tests with ISO “antiX-19-legacy-bet2_386-base.iso”.

ASUS P5V800-MX motherboard:
-I started in normal mode, Rox-IceWM, displayed a message on the screen “No frame was in use … the ‘Standard’ frame was selected. Use ‘rox -p = Defaut’ to enable it in the future. ”

Conky displays the 79.4 MB RAM consumption of the 936 MB available, $ sudo free {Enter} 75.16 MB RAM consumption of the 958 MB.

The images of the menu icons do not disappear when the mouse arrow passes over the menus, the submenus of “Applications” are out of the normal order and appear disorganized, it has only antiX and Graphics. Program opening is faster than antiX 19.3 on a compatible motherboard. The “bet2” system is more fluid than the “bet1” version, there is a clear improvement in the response and in the movement of the windows of open programs, I opened several programs until the consumption of RAM reached 181 MB. It is interesting how the same ISO “antiX-19-legacy-bet2_386-base.iso” behaves differently, initialized in normal mode, but on a different motherboard. While I was looking for the programs through the menus that were disorganized, at some point, the “Applications” submenus organized themselves.

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: 800 × 600 ~ 85Hz
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Table 18.3.6

demo @ antix1: ~
$ inxi -S
System:
Host: antix1 Kernel: 4.4.240-antix.2-486-smp i686 bits: 32
Desktop: IceWM 1.9.2
Distro: antiX-19-legacy-bet2_386-base Lazarus 29 November 2020

I changed from Rox-IceWM to Space-IceWM, the images of the menu icons do not disappear when the mouse arrow passes over the menus, the submenus of “Applications” are in the normal order after they have been organized by themselves.

The Minimal-IceWM and IceWM workspace menus are similar to Rox-IceWM, after organizing themselves.

I kept the various programs open and checked how the menus behave in each work area: Fluxbox, Minimal-Fluxbox, Rox-Fluxbox, Space-Fluxbox. All menus and submenus are OK and are free from defects.

I kept the various programs open and checked how the menus behave for the desktop for JWM, the images of the menu icons do not disappear when the mouse arrow passes over the menus, the submenus of “Applications” are all OK and not have any type of defect. Then Minimal-JWM, Rox-JWM, Space-JWM, all behave as I described JWM.

I went back to Rox-IceWM, closed the various programs that I had opened, the RAM memory displayed by Conky went down to about163 MB, I opened Firefox 78.5.0esr (32 bit), playing a 21min36s video from YouTube, antiX started in normal mode has a low quality, but the idea of ​​this test is to simulate the condition that requires more processing resources and RAM memory, Conky displays consumption at about 487 MB while the video is played, $ htop {Enter} command CPU: between 67% and most of the time at 100%, Mem 582MB / 936MB and Swp 18.4MB / 1.89GB .

I restarted the computer, safe video mode, Rox-IceWM, the message that occurs in normal video mode did not appear that the images of the menu icons do not disappear when the mouse arrow passes over the menus, the submenus of “Applications ”Are out of the normal order and appear disorganized, have only antiX and Development.

Conky displays the 70.5 MB RAM consumption of the 936 MB available, $ sudo free {Enter} 72.97 MB RAM consumption of the 958 MB.

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

demo @ antix1: ~
$ inxi -S
System:
Host: antix1 Kernel: 4.4.240-antix.2-486-smp i686 bits: 32
Desktop: IceWM 1.9.2
Distro: antiX-19-legacy-bet2_386-base Lazarus 29 November 2020

Still on Rox-IceWM, without opening any other program, besides the terminal, using Firefox 78.5.0esr (32 bit) playing a 21min36s YouTube video (the same test video with the normal video mode), the RAM memory displayed by Conky 407MB while the video is played, in secure video mode has a better quality than normal video mode, but the idea of ​​this test is to simulate the condition that requires more processing resources and RAM, Conky displays consumption in less than about 80 MB, command $ htop {Enter} CPU: between 67% and most of the time at 100%, Mem 511MB / 936MB and Swp 31.8MB / 1.89GB.

I changed from Rox-IceWM to Space-IceWM, the images of the menu icons do not disappear when the mouse arrow passes over the menus, the submenus of “Applications” are in the normal order. I returned to Rox-IceWM and the “Applications” submenus are now in the normal order. Only the Package Manager (Synaptic) menu that is not in the “System” list. In the Control Center Synaptic opens

The Minimal-IceWM and IceWM workspace menus are similar to Rox-IceWM, after organizing themselves.

I kept the various programs open and checked how the menus behave in each work area: Fluxbox, Minimal-Fluxbox, Rox-Fluxbox, Space-Fluxbox. All menus and submenus are OK and are free from defects.

I kept the various programs open and checked how the menus behave for the desktop for JWM, the images of the menu icons do not disappear when the mouse arrow passes over the menus, the submenus of “Applications” are all OK and not have any type of defect. Then Minimal-JWM, Rox-JWM, Space-JWM, all behave as I described JWM.

Before doing the installation test, I would like to repeat the same tests on the other computer that is missing, so we will have more information available.

Xecure wrote:
I will probably experiment a bit more in the future by holding older amd/intel graphics firmware package if more people report having issues with antiX 19.3 (for now only one case).

My opinion is to have as many drivers available as possible. Thus it serves as many people as possible. Even if it makes the ISO bigger than a CD.

Removing Firefox can make the initial user experience bad if you access YouTube or other sites that require a more complete internet browser. Dillo and Links 2 have very specific characteristics. The way to watch YouTube videos that @PPC explained is the next step for the average or basic user, when they want to explore and learn about the available antiX resources (Thanks PPC). Myself, I haven’t had time to study and learn these valuable antiX resources, like watching videos without advertisements.

Thanks.

marcelocripe
(Original text in Brazilian Portuguese)

———-

Xecure,

Eu testei sim o Porteus, mas não foram bons testes (eu acho que perdi o meu tempo …):

A versão mais recente “Porteus-OPENBOX-v5.0rc2-x86_64.iso” sequer inicializou em modo gráfico. Eu relatei os testes que fiz e as falhas que encontrei na área em idioma Inglês e em Português do fórum.

A comunidade do Porteus, infelizmente, está muito aquém desta comunidade antiX, as repostas foram extremamente técnicas e direcionadas para aqueles que conhecem o Porteus há muitos anos, não são úteis ou suficientes para um iniciante neste sistema operacional.

A versão anterior “Porteus-OPENBOX-v5.0rc1-x86_64.iso”, inicia em modo gráfico, de forma fluída semelhante a ISO “antiX-19-legacy-bet2_386-base.iso”. Mas, como o consumo de memória RAM do Porteus é de aproximadamente 155 MB, a resposta na abertura dos programas é mais lenta do que no antiX. Nas tentativas de instalação, o gerenciador de partições do Porteus não inicia, eu tentei instalar em uma partição existente e o processo iniciou, recebi a mensagem de “concluído com sucesso”. Após reiniciar o computador (que descrevei nos testes abaixo com a ISO “antiX-19-legacy-bet2_386-base.iso”) parou na tela preta, além de exibir vários erros. Eu não vou perder mais tempo reportando falhas naquela comunidade. Eu reportei nos dias 17 e 18 de Novembro de 2020, retornei no fórum no dia de hoje, só para poder te informar os links e te responder com o máximo de informações possíveis e completas. As repostas do fórum não ajudam um iniciante a resolver sozinho o problema. O problema parece estar mesmo na ISO. Eu cansei de ver isso no SliTaz, a cada nova ISO vários problemas novos para os usuários ficarem testando e terem que resolverem tudo sozinho. Na vida das pessoas, já existem muitos problemas, os sistemas operacionais precisam oferecer soluções, ao invés de novos problemas.

Vamos para o que realmente nos interessa, o antiX. Este sim vale a pena, a comunidade e o antiX fazem valer a pena cada minuto desprendido, seja em testes ou para colaborar com o sistema operacional.

Resultados dos testes com a ISO “antiX-19-legacy-bet2_386-base.iso”.

Placa-mãe da marca ASUS P5V800-MX:
-Iniciei no modo normal, Rox-IceWM, 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.”.

O Conky exibe o consumo de memória RAM de 79,4 MB dos 936 MB disponíveis, $ sudo free {Enter} consumo de memória RAM de 75,16 MB dos 958 MB.

As imagens dos ícones do menus não somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão fora da ordem normal e surgem desorganizados, possui apenas antiX e Gráficos. A abertura dos programas está mais rápida do que no antiX 19.3 em placa-mãe compatível. O sistema “bet2” está mais fluído do que a versão “bet1”, é nítido a melhora na resposta e na movimentação das janelas dos programas abertos, eu abri vários programas até o consumo de memória RAM chegar até 181 MB. É interessante como se comporta diferente a mesma ISO “antiX-19-legacy-bet2_386-base.iso” inicializada em modo normal, mas em placa-mãe diferente. Enquanto eu ia buscando os programas pelos menus que estavam desorganizados, em algum momento, os submenus de “Aplicativos” se organizaram sozinho.

demo @ antix1: ~
$ inxi -G
Dados do comando no texto em inglês

demo @ antix1: ~
$ inxi -S
Dados do comando no texto em inglês

Alterei de Rox-IceWM para Space-IceWM, as imagens dos ícones do menus não somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão na ordem normal após se organizaram sozinho.

O menus da área de trabalho Minimal-IceWM e IceWM estão semelhantes ao Rox-IceWM, após se organizaram sozinho.

Eu mantive os vários programas abertos e verifiquei como os menus se comportam em cada área de trabalho: Fluxbox, Minimal-Fluxbox, Rox-Fluxbox, Space-Fluxbox. Todos os menus e submenus estão Ok e não apresentam qualquer tipo de defeito.

Eu mantive os vários programas abertos e verifiquei como os menus se comportam para a área de trabalho para JWM, as imagens dos ícones dos menus não somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão todos Ok e não apresentam qualquer tipo de defeito. Em seguida Minimal-JWM, Rox-JWM, Space-JWM, todos se comportam como descrevi o JWM.

Voltei para o Rox-IceWM, fechei os vários programas que eu havia aberto, a memória RAM exibida pelo Conky baixou para cerca de 163 MB, abri o Firefox 78.5.0esr(32 bit), tocando um vídeo de 21min36s do YouTube, no antiX iniciado em modo normal possui uma qualidade baixa, mas a ideia deste teste é simular a condição que exige mais recursos de processamento e memória RAM, o Conky exibe consumo em cerca de 487 MB enquanto o vídeo é tocado, comando $ htop {Enter} CPU: entre 67% e na maior parte do tempo em 100%, Mem 582MB/936MB e Swp 18.4MB/1.89GB.

Reiniciei o computador, modo de vídeo seguro, Rox-IceWM, não foi a exibida a mensagem que ocorre no modo de vídeo normal que as imagens dos ícones do menus não somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão fora da ordem normal e surgem desorganizados, possui apenas antiX e Desenvolvimento.

O Conky exibe o consumo de memória RAM de 70,5 MB dos 936 MB disponíveis, $ sudo free {Enter} consumo de memória RAM de 72,97 MB dos 958 MB.

demo @ antix1: ~
$ inxi -G
Dados do comando no texto em inglês

demo @ antix1: ~
$ inxi -S
Dados do comando no texto em inglês

Ainda no Rox-IceWM, sem abrir qualquer outro programa, além o terminal, utilizando o Firefox 78.5.0esr(32 bit) tocando um vídeo de 21min36s do YouTube (o mesmo vídeo do teste com o modo de vídeo normal), a memória RAM exibida pelo Conky 407MB enquanto o vídeo é tocado, em modo de vídeo seguro possui uma qualidade melhor do que modo de vídeo normal, mas a ideia deste teste é simular a condição que exige mais recursos de processamento e memória RAM, o Conky exibe consumo em menor de cerca de 80 MB, comando $ htop {Enter} CPU: entre 67% e na maior parte do tempo em 100%, Mem 511MB/936MB e Swp 31.8MB/1.89GB.

Alterei de Rox-IceWM para Space-IceWM, as imagens dos ícones do menus não somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão na ordem normal. Voltei para o Rox-IceWM e os submenus de “Aplicativos” agora estão na ordem normal. Só o menu do Gerenciador de Pacotes (Synaptic) que não está no sumenu “Sistema”. No Centro de Controle o Synaptic abre

O menus da área de trabalho Minimal-IceWM e IceWM estão semelhantes ao Rox-IceWM, após se organizaram sozinho.

Eu mantive os vários programas abertos e verifiquei como os menus se comportam em cada área de trabalho: Fluxbox, Minimal-Fluxbox, Rox-Fluxbox, Space-Fluxbox. Todos os menus e submenus estão Ok e não apresentam qualquer tipo de defeito.

Eu mantive os vários programas abertos e verifiquei como os menus se comportam para a área de trabalho para JWM, as imagens dos ícones dos menus não somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão todos Ok e não apresentam qualquer tipo de defeito. Em seguida Minimal-JWM, Rox-JWM, Space-JWM, todos se comportam como descrevi o JWM.

Antes de fazer o teste de instalação, eu gostaria de repetir os mesmos testes no outro computador que falta, assim teremos mais informações disponíveis.

Xecure wrote:
I will probably experiment a bit more in the future by holding older amd/intel graphics firmware package if more people report having issues with antiX 19.3 (for now only one case).

A minha opinião é de ter disponível o maior número possível de drivers disponíveis. Assim atende um maior número possível de pessoas. Mesmo que isso faça a ISO ficar maior que um CD.

Remover o Firefox pode tornar a experiência inicial do usuário ruim, no caso de acessar o Youtube ou outros sites que exigem um navegador de internet mais completo. O Dillo e o Links 2 possuem características bem específicas. A forma de assistir vídeos do Youtube que o @PPC explicou é a próxima etapa do usuário comum ou básico, quando desejar explorar e conhecer os recursos disponíveis do antiX (Obrigado PPC). Eu mesmo, ainda não tive tempo de estudar e aprender estes recursos valiosos do antiX, como por exemplo assistir vídeos sem propagandas.

Obrigado.

marcelocripe
(Texto original em Português do Brasil)

[Member Xecure]

Helpful

Up

0

::

Thanks, Marcelo, for the feedback. It seems the VIA graphic chips don’t have the “disappearing icons” glitch, but the SIS do when running fbdev.

You are better off only testing on safe video mode. The VIA chips have better resolution and work well on them, and the SIS chips don’t have the “icon glitch” if they use vesa drivers (safe video mode).

So, when you test the installation, try it only with safe video mode and see if vesa drivers continue to be loaded on the installed system.

About streaming youtube, you are better off testing it using Streamlight as SamK recommends on a separate topic. You will probably have much better video experience.

About Porteus, it is unfortunate. But I understand they cannot attend to all posts. You were also testing a non-final release (it was a release candidate, which means it may need polish, fixing but is more stable than a beta). They are more interested in feedback of normal use, and it isn’t intended as a final stable release.

About more fluidity in this beta2, not much has changed, except for better installation sequence and package holding (but that shouldn’t influence much else). Performance is entirely thanks to the antiX Linux dev team’s effort. I barely only changed some things on what to add/remove from the build-iso process. Nothing can be attributed to me.

About firefox and drivers, Firefox may be replaced at some time in the future with a non-sse2 supported browser. Drivers are the same (they are in the 4.4 kernel) and I will not change that. I saw that “presumably” (not confirmed), a amd firmware update made an antiX user not able to boot (after said update). The firmware update was suspected, but not confirmed. This could mean that an update brought a regression for some older chips. If more people confirm this, I may pin (hold back) a certain firmware version that is known to work on those machines.

As there is little information related to this, I will wait for more confirmed cases.

Thanks again for testing things out. If after confirming that installation works and the system performs well, I think you can use this version.
Remember that antiX has a Snapshot tool that lets you create your won ISO files with the customization you make. Some people who have created “re-spins” have moved some of the home configs to /etc/skel/ before creating the snapshot so that their customized version of antiX can be easily installed on any system. This way you can set it up for the users before even booting and installing antiX on their machines.

Regards.

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

[Member marcelocripe]

Helpful

Up

0

::

Xecure,

I send the test results with the ISO “antiX-19-legacy-bet2_386-base.iso”.

Gigabyte GA-8S661FXM-775 brand motherboard:

I started in normal mode, Rox-IceWM, did not display a message on the screen “No frames were in use… the‘ Standard ’frame was selected. Use ‘rox -p = Defaut’ to enable it in the future. ”

The images of the menu icons disappear when the mouse arrow passes over the menus, the submenus of “Applications” are out of the normal order and appear disorganized.

Conky displays the 60.9 MB RAM consumption of the 256 MB available (it was 1 GB, but I had to use the cards on another computer), $ sudo free {Enter} 62.07 MB RAM consumption of the 285 MB.

After the command “sudo” and click “Update Menus”, the submenus of “Applications” are in the normal order and appear organized. The images of the menu icons disappear when the mouse arrow passes over the menus. The “bet2” system is more fluid than the “bet1” version, there is a clear improvement in the response and movement of the windows of open programs. A freeze has occurred. I need to check if it occurred again on the same motherboard or if it was on a different motherboard.

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

$ inxi -S
System:
Host: antix1 Kernel: 4.4.240-antix.2-486-smp i686 bits: 32
Desktop: IceWM 1.9.2 Distro: antiX-19-legacy-bet_386-base Lazarus 29 November 2020

I restarted the computer, started again in normal video mode, changed from Rox-IceWM to Space-IceWM, the images of the menu icons disappear when the mouse arrow passes over the menus, after clicking on “Update the Menu”, the submenus “Applications” are in normal order.

The Minimal-IceWM and IceWM workspace menus are similar to Rox-IceWM.

In the work areas: Fluxbox, Minimal-Fluxbox, Rox-Fluxbox, Space-Fluxbox, all menus and submenus are OK and have no defects.

In the work areas: Minimal-JWM, Rox-JWM, Space-JWM, all menus and submenus are OK and have no defects.

As in this test the computer is less than 512MB, it will not be possible to test behavior with Firefox 78.5.0esr (32 bit) and playing a 21min36s YouTube video.

I restarted the computer, secure video mode, Rox-IceWM, did not display a message on the screen “No frames were in use… the‘ Standard ’frame was selected. Use ‘rox -p = Defaut’ to enable it in the future. ”

The images of the menu icons do not disappear when the mouse arrow passes over the menus, the submenus of “Applications” are in the normal order, I checked in all work areas, everything is ok with the menus.

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.1 Mesa 18.3.6

Xecure, at the end of all tests I realize that loading the “driver: vesa” is always the best option for the three computers.

My doubts:

1-To install the ISO “antiX-19-legacy-bet2_386-base.iso”, should I start in secure video mode and then start the installation process?

2-After installation, will “antiX-19-legacy-bet2_386-base.iso” start normally in the normal video mode with vesa?

Xedure wrote:
Remember that antiX has a Snapshot tool that lets you create your won ISO files with the customization you make. Some people who have created “re-spins” have moved some of the home configs to / etc / skel / before creating the snapshot so that their customized version of antiX can be easily installed on any system. This way you can set it up for the users before even booting and installing antiX on their machines.

These guidelines are very important to me, I still don’t know how to use Snapshot and create an ISO from a complete system and even with this ISO it is possible to install it on any other computer. In the case of the ISO “antiX-19-legacy-bet2_386-base.iso”, it will be dedicated to make computers with a motherboard with SIS or VIA chipset work with antiX.

The next tests I will send will be the result of the installation process.

Thank you.

marcelocripe
(Original text in Brazilian Portuguese)

———-

Xecure,

Envio os resultados dos testes com a ISO “antiX-19-legacy-bet2_386-base.iso”.

Placa-mãe da marca Gigabyte GA-8S661FXM-775:

Iniciei no modo normal, Rox-IceWM, não 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.”.

As imagens dos ícones do menus somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão fora da ordem normal e surgem desorganizados.

O Conky exibe o consumo de memória RAM de 60,9 MB dos 256 MB disponíveis (estava com 1 GB, mas precisei utilizar as placas em outro computador), $ sudo free {Enter} consumo de memória RAM de 62,07 MB dos 285 MB.

Após o comando “sudo” e clicar em “Atualizar o Menus”, os submenus de “Aplicativos” estão em da ordem normal e surgem organizados. As imagens dos ícones do menus somem quando a seta do mouse passa sobre os menus. O sistema “bet2” está mais fluído do que a versão “bet1”, é nítido a melhora na resposta e na movimentação das janelas dos programas abertos. Ocorreu um congelamento. Eu preciso verificar se ocorreu novamente na mesma placa-mãe ou se foi em uma placa diferente.

demo @ antix1: ~
$ inxi -G
(Dados do comando no texto em inglês)

 

$ inxi -S
(Dados do comando no texto em inglês)

Reiniciei o computador, iniciei novamente no modo de vídeo normal, alterei de Rox-IceWM para Space-IceWM, as imagens dos ícones do menus somem quando a seta do mouse passa sobre os menus, após clique em “Atualizar o Menu”, os submenus de “Aplicativos” estão em ordem normal.

O menus da área de trabalho Minimal-IceWM e IceWM estão semelhantes ao Rox-IceWM.

Nas áreas de trabalho: Fluxbox, Minimal-Fluxbox, Rox-Fluxbox, Space-Fluxbox, todos os menus e submenus estão Ok e não apresentam qualquer tipo de defeito.

Nas áreas de trabalho: Minimal-JWM, Rox-JWM, Space-JWM, todos os menus e submenus estão Ok e não apresentam qualquer tipo de defeito.

Como neste teste o computador está com menos de 512MB, não será possível testar comportamento com o Firefox 78.5.0esr(32 bit) e tocando um vídeo de 21min36s do YouTube.

Reiniciei o computador, modo de vídeo seguro, Rox-IceWM, não 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.”.

As imagens dos ícones do menus não somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão na ordem normal, eu conferi em todas as áreas de trabalho, tudo está ok com os menus.

demo @ antix1: ~
$ inxi -G
(Dados do comando no texto em inglês)

Xecure, ao final de todos os testes eu percebo que carregar o “driver: vesa” é sempre a melhor opção para os três computadores.

As minhas dúvidas:

1-Para instalar a ISO “antiX-19-legacy-bet2_386-base.iso” eu devo iniciar no modo de vídeo seguro para depois inciar o processo de instalação?

2-Após a instalação o “antiX-19-legacy-bet2_386-base.iso” iniciará normalmente no modo de vídeo normal com o vesa?

Xecure wrote:
Remember that antiX has a Snapshot tool that lets you create your won ISO files with the customization you make. Some people who have created “re-spins” have moved some of the home configs to /etc/skel/ before creating the snapshot so that their customized version of antiX can be easily installed on any system. This way you can set it up for the users before even booting and installing antiX on their machines.

Estas suas orientações são importantíssimas para mim, eu ainda não sei utilizar o Snapshot e criar uma ISO a partir de sistema todo pronto e ainda com esta ISO ser possível de instalar em qualquer outro computador. No caso da ISO “antiX-19-legacy-bet2_386-base.iso”, ela será dedicada para fazer computadores com placa-mãe com chipset SIS ou VIA funcionarem com o antiX.

Os próximos testes que enviarei serão do resultado do processo de instalação.

Muito Obrigado.

marcelocripe
(Texto original em Português do Brasil)

[Member marcelocripe]

Helpful

Up

0

::

@Xecure,

I started the ISO “antiX-19-legacy-bet2_386-base.iso” in “Safe Video Mode”, successfully completed the first installation test with the ASUS P5V800-MX Motherboard:

Conky displays the 65.6 MB RAM consumption of the 939 MB available, in the terminal: $ free {Enter} the 75.58 MB RAM consumption of the 962 MB available and the Task Manager displays the memory consumption 74 MB RAM of the 939 MB available. All these data refer to the Rox-IceWM workspace.

antix@antix:~
$ 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

Test with Firefox 78.5.0esr (32 bit) playing the 21min47s YouTube video, Conky displays the RAM consumption in approximately 384 MB of the 939 MB available, the Task Manager displays the 473 MB RAM consumption ( was the maximum value, average value of 379 MB) of the 939 MB available. in the terminal: $ free {Enter} the RAM consumption of 349.24 MB of the 962 MB available. All these data refer to the Rox-IceWM workspace.

I changed to the Minimal-Fluxbox desktop, restarted the computer:

Conky does not load the Minimal-Fluxbox desktop in the terminal: $ free {Enter} the 48.14 MB RAM consumption of the 962.20 MB available and the Task Manager displays the 53 MB RAM consumption of the 939 MB available. All these data refer to the Minimal-Fluxbox work area.

Test with Firefox 78.5.0esr (32 bit) playing a 21min47s YouTube video, Conky displays the RAM consumption in approximately 396 MB of the 939 MB available, in the terminal: $ free {Enter} the RAM memory consumption of 393.32 MB of the 962 MB available and the Task Manager displays the RAM consumption of 444 MB (was the maximum value) of the 939 MB available. All these data refer to the Minimal-Fluxbox work area.

I changed to the Minimal-JWM desktop, restarted the computer:

Conky displays the 50.4 MB RAM consumption of the 939 MB available, in the terminal: $ free {Enter} the 46.50 MB RAM consumption of the 962 MB available and the Task Manager displays the memory consumption 59 MB RAM of the 939 MB available. All these data refer to the Minimal-JWM work area.

Test with Firefox 78.5.0esr (32 bit) playing the same 21min47s YouTube video, Conky displays the RAM consumption in approximately 372 MB of the 939 MB available, in the terminal: $ free {Enter} the RAM memory consumption 347.24 MB of the 962.20 MB available and the Task Manager displays the RAM consumption of 341 MB (was the maximum value) of the 939 MB available. All these data refer to the Minimal-JWM work area.

The ISO “antiX-19-legacy-bet2_386-base.iso” is ready for use, all menus are organized and there is no fault, audio and LAN network working normally.

The next test results that I intend to send will be more summarized, it will not be as extensive as this one. However, this information may prove to be useful in the future for other users.

As soon as possible I will do the installation test of the other two computers with SIS graphics card.

Thank you so much!
marcelocripe
(Original text in Brazilian Portuguese)

———-

@Xecure,

Eu iniciei em “Modo de Vídeo Seguro” a ISO “antiX-19-legacy-bet2_386-base.iso”, conclui com sucesso o primeiro teste de instalação com a Placa-mãe ASUS P5V800-MX:

O Conky exibe o consumo de memória RAM de 65,6 MB dos 939 MB disponíveis, no terminal: $ free {Enter} o consumo de memória RAM de 75,58 MB dos 962 MB disponíveis e o Gerenciador de Tarefas exibe o consumo de memória RAM de 74 MB dos 939 MB disponíveis. Todos estes dados são referentes a área de trabalho Rox-IceWM.

antix@antix:~
$ 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

Teste com o Firefox 78.5.0esr(32 bit) tocando o vídeo de 21min47s do YouTube, o Conky exibe o consumo de memória RAM em aproximadamente 384 MB dos 939 MB disponíveis, o Gerenciador de Tarefas exibe o consumo de memória RAM de 473 MB (foi o valor máximo, valor médio de 379 MB) dos 939 MB disponíveis. no terminal: $ free {Enter} o consumo de memória RAM de 349,24 MB dos 962 MB disponíveis. Todos estes dados são referentes a área de trabalho Rox-IceWM.

Alterei para a área de trabalho Minimal-Fluxbox, reiniciei o computador:

O Conky não carrega na área de trabalho Minimal-Fluxbox, no terminal: $ free {Enter} o consumo de memória RAM de 48,14 MB dos 962,20 MB disponíveis e o Gerenciador de Tarefas exibe o consumo de memória RAM de 53 MB dos 939 MB disponíveis. Todos estes dados são referentes a área de trabalho Minimal-Fluxbox.

Teste com o Firefox 78.5.0esr(32 bit) tocando um vídeo de 21min47s do YouTube, o Conky exibe o consumo de memória RAM em aproximadamente 396 MB dos 939 MB disponíveis, no terminal: $ free {Enter} o consumo de memória RAM de 393,32 MB dos 962 MB disponíveis e o Gerenciador de Tarefas exibe o consumo de memória RAM de 444 MB (foi o valor máximo) dos 939 MB disponíveis. Todos estes dados são referentes a área de trabalho Minimal-Fluxbox.

Alterei para a área de trabalho Minimal-JWM, reiniciei o computador:

O Conky exibe o consumo de memória RAM de 50,4 MB dos 939 MB disponíveis, no terminal: $ free {Enter} o consumo de memória RAM de 46,50 MB dos 962 MB disponíveis e o Gerenciador de Tarefas exibe o consumo de memória RAM de 59 MB dos 939 MB disponíveis. Todos estes dados são referentes a área de trabalho Minimal-JWM.

Teste com o Firefox 78.5.0esr(32 bit) tocando o mesmo vídeo de 21min47s do YouTube, o Conky exibe o consumo de memória RAM em aproximadamente 372 MB dos 939 MB disponíveis, no terminal: $ free {Enter} o consumo de memória RAM de 347,24 MB dos 962,20 MB disponíveis e o Gerenciador de Tarefas exibe o consumo de memória RAM de 341 MB (foi o valor máximo) dos 939 MB disponíveis. Todos estes dados são referentes a área de trabalho Minimal-JWM.

A ISO “antiX-19-legacy-bet2_386-base.iso” está pronta para uso, todos os menus estão organizados e não há qualquer tipo de falha, áudio e rede LAN funcionando normalmente.

Os próximos resultados dos testes que eu pretendo enviar serão de forma mais resumida, não ficará tão extenso como este. Contudo estas informações podem vir a serem úteis no futuro para outros usuários.

Assim que possível irei fazer o teste de instalação dos outros dois computadores com placa de vídeo SIS.

Muito Obrigado!
marcelocripe
(Texto original em Português do Brasil)

[Author]

Posts