Installing Zoom on AntiX

[Member Xecure]

Helpful

Up

0

::

andfree wrote:

How can I do it, please?

antiX wiki – Boot Parameters – Installed antiX Linux

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

[Member andfree]

Helpful

Up

0

::

Thank you, Xecure.
Adding the word “safe” or the word “failsafe” after the word “quiet” in the GRUB, and then pressing F10, doesn’t seem to make any difference. The same grey window opens when I run Zoom.

[Member Xecure]

Helpful

Up

0

::

I think the boot option is xorg=safe to use the vesa driver, but I have been testing and those special boot options only seem to work on the live USB and not an installed system.
Changing to vesa in order to test zoom should only be done on a live USB (using safe video boot menu or xorg=safe), as the only solution I found for changing to vesa on an installed system is creating a xorg.conf file in /etc/X11/, and that leaded to a broken boot, so this is not recommended for the average user.

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

[Member andfree]

Helpful

Up

0

::

Xecure wrote:

Changing to vesa in order to test zoom should only be done on a live USB (using safe video boot menu …

It worked. Zoom seems to work properly on a live USB, using safe video boot option.

System:
  Host: antix1 Kernel: 4.9.235-antix.1-486-smp i686 bits: 32 compiler: gcc 
  v: 8.3.0 Desktop: IceWM 1.8.3 
  Distro: antiX-19.3_386-base Manolis Glezos 14 October 2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Laptop System: TOSHIBA product: Satellite 2450 v: PS245E-03TE0-GK 
  serial: <filter> 
  Mobo: TOSHIBA model: Portable PC v: Version A0 serial: <filter> 
  BIOS: TOSHIBA v: Version 1.30 date: 03/20/2003 
CPU:
  Topology: Single Core model: Intel Pentium 4 bits: 32 type: MCP 
  arch: Netburst Northwood rev: 7 L2 cache: 512 KiB 
  flags: pae sse sse2 bogomips: 5585 
  Speed: 2793 MHz min/max: N/A Core speed (MHz): 1: 2793 
Graphics:
  Device-1: NVIDIA NV17M [GeForce4 420 Go] 
  vendor: Toshiba America Info Systems driver: N/A bus ID: 01:00.0 
  Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1024x768~N/A 
  OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 
  direct render: Yes 
Audio:
  Device-1: Intel 82801DB/DBL/DBM AC97 Audio 
  vendor: Toshiba America Info Systems driver: snd_intel8x0 v: kernel 
  bus ID: 00:1f.5 
  Sound Server: ALSA v: k4.9.235-antix.1-486-smp 
Network:
  Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter 
  vendor: Toshiba America Info Systems driver: 8139too v: 0.9.28 port: ce00 
  bus ID: 02:09.0 
  IF: eth0 state: down mac: <filter> 
Drives:
  Local Storage: total: 100.63 GiB used: 2.65 GiB (2.6%) 
  ID-1: /dev/sda vendor: Toshiba model: MK1032GAX size: 93.16 GiB 
  ID-2: /dev/sdb type: USB model: USB FLASH DRIVE size: 7.47 GiB 
Partition:
  ID-1: / size: 2.89 GiB used: 647.2 MiB (21.9%) fs: overlay source: ERR-102 
Sensors:
  System Temperatures: cpu: 61.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 124 Uptime: 2m Memory: 1000.4 MiB used: 127.0 MiB (12.7%) 
  Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 
  inxi: 3.0.36

[Member Xecure]

Helpful

Up

0

::

andfree wrote:

It worked. Zoom seems to work properly on a live USB, using safe video boot option.

Good news. At least now we know that nouveau driver is to blame.

In your installed system you could try booting with nomodeset boot parameter and see if that disables nouveau at boot.
Blacklisting nouveau directly would be a possible solution, but it would be risky if you later need to un-blacklist it and don’t like using the terminal.

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

[Member andfree]

Helpful

Up

0

::

Xecure wrote:

In your installed system you could try booting with nomodeset boot parameter and see if that disables nouveau at boot.

As iamercado wrote (post #43541):

iamercado wrote:

I tried “nomodeset” in the boot options, but that just made antiX boot to a command prompt.

I tried “startx”, but a known from the past X server error occured (I copy here three lines):

xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

xserver-xorg-legacy is already the newest version (2:1.20.4-1+deb10u1) and the following line already exists in /etc/X11/Xwrapper.config:

needs_root_rights=yes

• This reply was modified 2 years, 6 months ago by andfree.

[Member Xecure]

Helpful

Up

0

::

andfree wrote:

As iamercado wrote (post #43541):
[…]

Sorry. I didn’t properly pay attention. So it was tested with no positive results. Then, probably nouveau.blacklist=1 will not work either.

For now, you could probably manage with the live system (maybe even with some persistence) until someone can propose a better solution.

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

[Member andfree]

Helpful

Up

0

::

Xecure wrote:

Then, probably nouveau.blacklist=1 will not work either.

nouveau.blacklist=1 as a boot parameter, you mean? It boots properly, but the grey (or white, I’m not sure about the exact color) Zoom window opens again.

[Member Xecure]

Helpful

Up

0

::

Well. It was worth a try.

If you are ok risking a failed boot in your installed antiX system, I can help you try to blacklist nouveau (and see if on the next boot it uses vesa).
On the running system, open a terminal and execute:

sudo bash -c "echo blacklist nouveau > /etc/modprobe.d/blacklist-nvidia-nouveau.conf"
sudo bash -c "echo options nouveau modeset=0 >> /etc/modprobe.d/blacklist-nvidia-nouveau.conf"

This will create a file named blacklist-nvidia-nouveau.conf with instructions to not load the nouveau driver.

Reboot and see if the system uses vesa.

If on next reboot you boot to a terminal (and not to the gui environment), you can fix it by:
1. log in in the terminal with your user and password.
2. Run this command to remove the blacklist instructions:
sudo rm /etc/modprobe.d/blacklist-nvidia-nouveau.conf
3. Reboot and return to your system using nouveau driver.

I say it is risky because “maybe”, the system will still not boot to gui after removing the nouveau blacklist file. Some times you will also need to remove the /etc/X11/xorg.conf file and reboot again to restore xorg (what renders the graphical environment).

If you decide to try it out and you experience any problems, I will try to help out as best I can.

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

[Member andfree]

Helpful

Up

0

::

Thanks for your help. Blacklisting nouveau caused, as you say, booting to a terminal. I tried “startx”, but the X server error that I’ve already mentioned (post #43918) occured again. I removed the nouveau blacklist file and that was enough to reboot to gui again.

[Member Xecure]

Helpful

Up

0

::

There is nothing else I can think of. You could try creating a snapshot of your current installed system, make a frugal install of it and boot to it with safe video option. This way you could boot to it with the speed of an installed system when you need Zoom, and you would have the same programs and files as your main installed system. You could even set a static root persistence and use it as your main system.

Are there any better suggestions? I am just trying to come up with ideas.

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

[Forum Admin anticapitalista]

Helpful

Up

0

::

From my experience of using these sort of apps (MS Teams), they are very RAM/CPU intensive.
Are you sure your hardware is capable of running it (not just opening it)?

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

antiX with runit - leaner and meaner.

[Moderator Brian Masinick]

Helpful

Up

0

::

I agree, these resources can be useful, but they consume both memory and CPU, and therefore, the older (and less powerful) the system is, the less likely the tools would be effective.

They can, however, be quite useful, but only if you have the power, speed, and overall system and environment to support their requirements.

--
Brian Masinick

[Member Josu]

Helpful

Up

0

::

Zoom meetings functions on my old AMD Athlon 64 3000+ with 750MB of RAM but in windows XP SP3, when i finish installing XP then i install zoom for 32 bits, an the GUI of zoom meetings go well, the point here is that i did not install my Nvidia graphics controller driver before open zoom window, i think that the graphics driver or the graphics card is not the problem, i think is the new GUI libraries that zoom uses, i think that de GUI dependencies packages for zoom don’t work well in old computers with linux, there may be some alternative dependencies packages for that libraries, thank you for the support and for the antiX.

[Author]

Posts