Search Results for 'startx'

[Member Xecure]

If X won’t start (with sudo startx), save the output of inxi -Fxz in a file so you can share it with us.
(in your non working installed system) Log in and, in the terminal and, do:
inxi -Fxz > $HOME/Documents/brokeninxi.txt

You will now require a live system.
When booting to a live system, select the session Space-icewm (if you cannot see it, boot and, after launching the desktop, go to the menu > Desktop > Other desktops > Space-Icewm).
Open the File manager (it will now be SpaceFM). On the left side you will see your partitions. If you did a normal install, your home folder should be located in the partition named rootantiX (if yoou created a home partition during installation,it will be in the home partition). Click on it to mount that partition (it will open it in a new tab). Navigate to the home folder > user > Documents and you will se the file brokeninxi.txt you created earlier. Share it in the new reply.
Also, share your current inxi -Fxz (in the live system) to compare.
Finally, in the root partition of your installed system, navigate to /var/log/apt/ and open history.log file. Go down to the end of the file and look at all apt changes marked with today’s date. Copy them (from the first of today’s date to the end of the file) and also share them with us in the forum.

Summary:

A. Borken installed system. Log in and do
inxi -Fxz > $HOME/Documents/brokeninxi.txt

B. Start a live system with Spacefm-Icewm desktop.
1. In the file manager, click on your rootantiX partition. inside, go to home/user/Documents and share the brokeninxi.txt with us.
2. Share the inxi -Fxz of the live system.
3. Share the /var/log/apt/history.log entries for todays date with us (make sure this is the rootantiX partition)

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

[Member PPC]

According to this (for ubutu) https://ubuntuforums.org/archive/index.php/t-2403057.html

sudo startx

could do the trick… If not, read here https://ubuntuforums.org/archive/index.php/t-2340960.html.

Wait for someone else to answer this post – and publish more information: from your previous thread I know you are running a fully updated antiX core… 32 bits or 64 bits? Did you have the default IceWM desktop installed? Video driver? Please post all that info, so folks here can try to help… This is way more serious than a missing printer driver… I hope someone can help you fix this.

P.

So I tried installing my Canon printer (see other thread) and apparently I did something wrong.

After a reboot I get the following screen:

“Welcome to Antix. Powered by Debian.
antix1 login:”

I have never seen this screen before as I chose during the installation to login to my account automatically.
And when I enter my username fchopin it asks “Password:”
When I give my password and press enter I get the following:

Last login: Mon Jun 29 19:33:41 CEST 2020 on tty1
No mail.
fchopin@antix1:~
$

And nothing happens after this. How do I login to my account again?

When I try “sudo startx” the following message appears:

[sudo] password for fchopin:

When I give my password and press enter I get the following:

/etc/X11/xinit/xserverrc: 3: exec: /usr/bin/X: not found
xinit: giving up
xinit: unable to connect to x server: Connection refused
xinit: server error

• This topic was modified 2 years, 10 months ago by HateDogsBarking.
• This topic was modified 2 years, 10 months ago by HateDogsBarking.

[Member PPC]

You probably messed something up, when you were trying to install the driver, you did something that you should not have done (hard to know what).
To try to get to your desktop try this:
startx

If that does not help, I recommend that you start a new thread to ask for help for your current situation OR try to reinstall antiX (now you know how to install the driver). Don’t forget to backup your files (boot from live media and copy all your important stuff)
There’s always the chance the driver botched your install, since it was not made for antiX, but, being for debian, it “should” work fine in antiX…
Can you try to install the driver booting from live media (usb stick or cd-rom)?
P.

[Member Xecure]

Better ignore my last comment.
antiX 19.2 runnit sid x64 core edition comes with kernel 5.5, so no need for using any other version.

If you can use the LUM on another distro to burn the sid ISO to a USB (see https://www.youtube.com/watch?v=-8y_mL2Sctc), boot in your laptop, select persistent option, download and install kernel 5.6, save state, remaster, use live USB kernel selector/updater (all can be done from antiX-cli-cc, Live tools), and reboot, you should be able to then install xorg, wm, antix minstaller, then startX and it should work.

I cannot guess anything else, except if I am able to build an ISO from doing it here on my PC.
Can I build an ISO (based on the live system) from cli without a gui?

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

[Forum Admin anticapitalista]

Hello!

The sid versions do not include X (xorg) and use a cli installer which do not recognize UEFI (yet).
There are workarounds though, I think someone posted a ‘fix’ somewhere in this forum.

You could run live, install xorg, a window manager eg jwm and antix-installer, startx and you *should* now be able to install to UEFI.
(I have only tried this on a virtual machine though)

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

antiX with runit - leaner and meaner.

[Member marcelocripe]

Xecure,

I configured the BIOS to boot with the pendrive prepared with antiX 19.2 64 bits, I selected the Safe Video Mode option and loaded antiX in graphical mode, the actions were extremely slow due to the video response.

In the Terminal I applied the command:

$ cat / proc / cmdline {Enter}
vga = 791 quiet splasht disable = lxF xorg = safe

I restarted the computer, configured the computer’s BIOS to boot from HD, Advanced options for antiX-19.2 Hnnie Schaft, “e” key

I changed from:

vga = quiet

for

vga = 791 quiet splasht disable = lxF xorg = safe

F10.

The monitor remained with the image visible, loaded the command prompt, requested the user login and password in text mode and on the command line I applied:

$ startx {Enter}

Unfortunately it didn’t work.

I booted the computer via the pendrive, Safe Video Mode, deletes the file /etc/X11/xorg.conf.in (on the system installed on the hard drive).

I restarted the computer again with the boot via HD, Advanced options for antiX-19.2 Hnnie Schaft, “e” key

I changed from:

vga = quiet

for

vga = 791 quiet splasht disable = lxF xorg = safe

F10.

The monitor remained with the image visible, loaded the command prompt, requested the user login and password in text mode and on the command line I applied:

$ startx {Enter}

Unfortunately it didn’t work, it didn’t load the graphics mode.

marcelocripe

Original text in Brazilian Portuguese, translated into English by the Google translator.

—————-

Xecure,

Configurei a BIOS para inicializar com o pendrive preparado com o antiX 19.2 64 bits, selecionei a opção Safe Video Mode e carregou o antiX no modo gráfico, as ações ficaram extremamente lentas devido a resposta do vídeo.

No Terminal apliquei o comando:

$ cat /proc/cmdline {Enter}
vga=791 quiet splasht disable=lxF xorg=safe

Reiniciei o computador, configurei a BIOS do computador para inicializar a partir do HD, Opções avançadas para antiX-19.2 Hnnie Schaft, tecla “e”

Alterei de:

vga=quiet

para

vga=791 quiet splasht disable=lxF xorg=safe

F10.

O monitor permaneceu com a imagem visível, carregou o prompt de comando, solicitou o login e senha de usuário em modo texto e na linha de comando apliquei:

$ startx {Enter}

Infelizmente não deu certo.

Inicializei o computador via pendrive, Safe Video Mode, exclui o arquivo /etc/X11/xorg.conf.in (no sistema instalado no disco rígido).

Reiniciei o computador novamente com o boot via HD, Opções avançadas para antiX-19.2 Hnnie Schaft, tecla “e”

Alterei de:

vga=quiet

para

vga=791 quiet splasht disable=lxF xorg=safe

F10.

O monitor permaneceu com a imagem visível, carregou o prompt de comando, solicitou o login e senha de usuário em modo texto e na linha de comando apliquei:

$ startx {Enter}

Infelizmente não deu certo, não carregou o modo gráfico.

marcelocripe

Texto original no idioma português do Brasil, traduzido para inglês pelo tradutor do Google.

[Member marcelocripe]

Hi BobC and Xecure,

I thank you for helping me.

Xecure, I hope I’m not bothering you too much. You are helping me a lot in this forum, I am able to learn a lot from you and other colleagues who contribute by sharing their knowledge on antiX Linux. The other post was solved thanks to your explanations at the link: https://www.antixforum.com/forums/topic/reporting-crashes-before-and-after-updates-on-antix-19-2-x64-full/ # post-37769, thank you.

I try to detail as much as possible the steps I am taking, as I know that this post can be of help to other colleagues new to antiX. That is why I keep the texts in Portuguese and with the translation done by Google translator for the English language, I have no idea of ​​how the understanding in the text translated by you should be.

When I search for any kind of information or help on the internet, both in Portuguese and in English related to problems about antiX, I do not find anything similar to what I research, most of the information is about MX Linux (about 80% ) and about the antiX 17 version (about 20%), I still don’t know what the connection is between MX Linux and antiX, there is almost no information about antiX 19.2, YouTube videos have a lot about antix information 17, few videos in Spanish language about antiX 19, but all related to analysis or installation, none with problem solving, so new users of antix 19.2 depend on the help of this forum. Other forums in Portuguese do not have answers or when they have answers, they are not useful to be applied.

Xecure, I joined the BobC guidelines with yours and got the results below:

1 Test: I edited the text:

Advanced options for antiX-19.2 Hnnie Schaft, “e” key

vga = quiet tovga = 791 xorg = vesa quiet, F10.

The video on the monitor remains visible with the command prompt, I entered the username and password,

user @ antix: ~
$ startx {Enter}

X.Org X Server 1.20.4
… Linux 4.9.0-8-amd64 x86_64 Debian
…
…
…
user / .local / share / xorg / Xorg.0.log “for additional information. (EE) (EE) Server terminate with error (1). Closinglog file
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

2 Test: I edited the text:

Advanced options for antiX-19.2 Hnnie Schaft, “e” key

vga = quiet tovga = 791 xorg = 1024x768 quiet, F10.

The initialization took a little longer than in the first test, the video on the monitor remains visible with the command prompt, I entered the user and password,

user @ antix: ~
$ startx {Enter}

X.Org X Server 1.20.4
… Linux 4.9.0-8-amd64 x86_64 Debian
…
…
…
user / .local / share / xorg / Xorg.0.log “for additional information. (EE) (EE) Server terminate with error (1). Closinglog filexinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

3 Test: I edited the text:

Advanced options for antiX-19.2 Hnnie Schaft, “e” key

vga = quiet tovga = 791 xorg = safe quiet, F10.

The initialization took a little longer than in the first test, the video on the monitor remains visible with the command prompt, I entered the user and password,

user @ antix: ~
$ startx {Enter}

X.Org X Server 1.20.4
… Linux 4.9.0-8-amd64 x86_64 Debian
…
…
…
user / .local / share / xorg / Xorg.0.log “for additional information. (EE) (EE) Server terminate with error (1). Closinglog file
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

4 Test: I edited the text:

Advanced options for antiX-19.2 Hnnie Schaft, “e” key

vga = quiet tovga = 791 xorg = xvesa, F10.

The startup was fast similar to the time of the first test, the video on the monitor remains visible with the command prompt, I entered the username and password,

user @ antix: ~
$ startx {Enter}

X.Org X Server 1.20.4
… Linux 4.9.0-8-amd64 x86_64 Debian
…
…
…
user / .local / share / xorg / Xorg.0.log “for additional information. (EE) (EE) Server terminate with error (1). Closinglog file
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Tomorrow I will try to follow the step by step of Xecure.

“Let us see how this evolves once marcelocripe has time to test these out.

If it is too much of a bother, we can stop after testing BobC’s xorg = vesa suggestion. All these tests take time and sooner or later will drain oneself of energy. We are not trying to pressure you to do more than you are willing to do, marcelocripe. “

I hope I don’t exhaust you, I may even take a while to apply and return, on the 4.9 to 4.8 kernel I can install the kernel in graphical mode using the offboard video card, then I can remove the video card offboard video and verify that the onboard video card will work in graphics mode.

Thank you for helping me.

marcelocripe

Original text in Brazilian Portuguese, translated into English by the Google translator.

——————

Olá BobC e Xecure,

Eu agradeço por estarem me ajudando.

Xecure, eu espero não estar te incomodando demais. Você está me ajudando muito neste fórum, estou podendo aprender bastante com você e com os outros colegas que contribuem compartilhando o seu conhecimento no antiX Linux. A outra postagem foi solucionada graças a suas explicações no link: https://www.antixforum.com/forums/topic/reporting-crashes-before-and-after-updates-on-antix-19-2-x64-full/#post-37769, obrigado.

Eu procuro detalhar o máximo possível os passos que estou realizando, pois eu sei que esta postagem poderá servir de ajuda para outros colegas iniciantes no antiX. Por isso mantenho os textos em português e com a tradução feita pelo Google tradutor para o idioma inglês, eu não tenho ideia de como deve ser a compreensão no texto traduzido por vocês.

Quando eu procuro qualquer tipo de informação ou ajuda na internet, tanto em língua portuguesa quanto em língua inglesa relacionadas a problemas sobre o antiX, eu não encontro nada semelhante ao que pesquiso, a maioria das informações são sobre o MX Linux (cerca de 80%) e sobre a versão do antiX 17 (cerca de 20%), eu ainda não sei qual é a ligação entre o MX Linux e o antiX, quase não há informações sobre o antiX 19.2, os vídeos do YouTube tem muita sobre informação o antix 17, poucos vídeos em idioma espanhol sobre o antiX 19, mas todos relacionados a análises ou instalação, nenhum com resolução de problemas, por tanto usuários novos do antix 19.2 dependem das ajudas deste fórum. Outros fóruns em português não possuem respostas o quando possuem respostas, não são úteis para serem aplicadas.

Xecure, eu juntei as orientações do BobC com as suas e obtive os resultados abaixo:

1 Teste: Editei o texto:

Opções avançadas para antiX-19.2 Hnnie Schaft, tecla “e”

vga=quiet para vga=791 xorg=vesa quiet, F10.

O vídeo no monitor permanece visível com o prompt de comando, entrei com o usuário e a senha,

usuario@antix:~
$ startx {Enter}

X.Org X Server 1.20.4
… Linux 4.9.0-8-amd64 x86_64 Debian
…
…
…
usuario/.local/share/xorg/Xorg.0.log” for additional information. (EE) (EE) Server terminate with error (1) . Closinglog file
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

2 Teste: Editei o texto:

Opções avançadas para antiX-19.2 Hnnie Schaft, tecla “e”

vga=quiet para vga=791 xorg=1024x768 quiet, F10.

A inicialização demorou um pouco mais do que no primeiro teste, o vídeo no monitor permanece visível com o prompt de comando, entrei com o usuário e a senha,

usuario@antix:~
$ startx {Enter}

X.Org X Server 1.20.4
… Linux 4.9.0-8-amd64 x86_64 Debian
…
…
…
usuario/.local/share/xorg/Xorg.0.log” for additional information. (EE) (EE) Server terminate with error (1) . Closinglog filexinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

3 Teste: Editei o texto:

Opções avançadas para antiX-19.2 Hnnie Schaft, tecla “e”

vga=quiet para vga=791 xorg=safe quiet, F10.

A inicialização demorou um pouco mais do que no primeiro teste, o vídeo no monitor permanece visível com o prompt de comando, entrei com o usuário e a senha,

usuario@antix:~
$ startx {Enter}

X.Org X Server 1.20.4
… Linux 4.9.0-8-amd64 x86_64 Debian
…
…
…
usuario/.local/share/xorg/Xorg.0.log” for additional information. (EE) (EE) Server terminate with error (1) . Closinglog file
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

4 Teste: Editei o texto:

Opções avançadas para antiX-19.2 Hnnie Schaft, tecla “e”

vga=quiet para vga=791 xorg=xvesa, F10.

A inicialização foi rápida semelhante ao tempo do primeiro teste, o vídeo no monitor permanece visível com o prompt de comando, entrei com o usuário e a senha,

usuario@antix:~
$ startx {Enter}

X.Org X Server 1.20.4
… Linux 4.9.0-8-amd64 x86_64 Debian
…
…
…
usuario/.local/share/xorg/Xorg.0.log” for additional information. (EE) (EE) Server terminate with error (1) . Closinglog file
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Amanhã eu vou tentar seguir o passo a passo do Xecure.

“Let us see how this evolves once marcelocripe has time to test these out.

If it is too much of a bother, we can stop after testing BobC’s xorg=vesa suggestion. All these tests take time and sooner or later will drain oneself of energy. We are not trying to pressure you to do more than you are willing to do, marcelocripe.”

Eu espero não esgotar vocês, eu posso até demorar um pouco para aplicar e para dar um retorno, sobre o kernel 4.9 para o 4.8 eu posso fazer a instalação do kernel em modo gráfico utilizando a placa de vídeo offboard, depois posso retirar a placa de vídeo offboard e verificar se a placa de vídeo onboard funcionará no modo gráfico.

Agradeço por vocês estarem me ajudando.

marcelocripe

Texto original no idioma português do Brasil, traduzido para inglês pelo tradutor do Google.

[Member marcelocripe]

BobC,

After several attempts, I managed to make changes to the advanced options of antiX 19.2 with the onboard video card, finally I was able to set the vga = 791 1024 × 768, the hard part was finding the key to save the changes, I think it was the key F10, I’m not sure …

Requested the user login and password in text mode and on the command line I applied the command below:

user @ antix:
~ $ inxi -Fxz {Enter}

Graphics Device-1: VIA CN700 / P4M800 Pro / P4M800 CE / VN800 Graphics [S3 UniChrome Pro] vendor: Micro-Star MSI driver: N / A
bus ID: 01: 00.0
Display: server: X.org 1.20.4 driver: fbdev, modesetting, vesa unloaded: openchrome tty: 128×48

Then I tried:

user @ antix:
~ $ startx {Enter}

X.org 1.20.4
…
…
vga = 791 1024 × 768
…
…
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Xecure,

I applied the command below:

user @ antix:
~ $ inxi -G {Enter}

Graphics Device-1: VIA CN700 / P4M800 Pro / P4M800 CE / VN800 Graphics [S3 UniChrome Pro] vendor: Micro-Star MSI driver: N / A
Display: server: X.org 1.20.4 driver: fbdev, modesetting, vesa unloaded: openchrome tty: 128×48
Message: Advanced graphics data unavaliable in console. Try -G –display

user @ antix:
~ $ inxi -G –display {Enter}

Graphics Device-1: VIA CN700 / P4M800 Pro / P4M800 CE / VN800 Graphics [S3 UniChrome Pro] driver: N / A
Display: server: X.org 1.20.4 driver: fbdev, modesetting, vesa unloaded: openchrome tty: 128×48
Message: No advanced graphics data found on this system.

If I use the pendrive prepared to boot / install with antiX 19.2, starting the computer via pendrive, I will be able to make changes directly to text files in graphical mode, you would know how to guide me through this method which changes should I make to the files of text?

Thankful.

marcelocripe

Original text in Brazilian Portuguese, translated into English by the Google translator.

————–

BobC,

Após várias tentativas, eu consegui fazer as alterações nas opções avançadas do antiX 19.2 com a placa de vídeo onboard, enfim consegui definir o vga=791 1024×768, o difícil foi descobrir a tecla para salvar as alterações, eu acho que foi a tecla F10, eu não tenho certeza …

Solicitou o login e senha de usuário em modo texto e na linha de comando apliquei o comando abaixo:

usuario@antix:
~$ inxi -Fxz {Enter}

Graphics Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] vendor: Micro-Star MSI driver: N/A
bus ID: 01:00.0
Display: server: X.org 1.20.4 driver: fbdev,modesetting,vesa unloaded: openchrome tty: 128×48

Em seguida tentei:

usuario@antix:
~$ startx {Enter}

X.org 1.20.4
…
…
vga=791 1024×768
…
…
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Xecure,

Apliquei o comando abaixo:

usuario@antix:
~$ inxi -G {Enter}

Graphics Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] vendor: Micro-Star MSI driver: N/A
Display: server: X.org 1.20.4 driver: fbdev,modesetting,vesa unloaded: openchrome tty: 128×48
Message: Advanced graphics data unavaliable in console. Try -G –display

usuario@antix:
~$ inxi -G –display {Enter}

Graphics Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] driver: N/A
Display: server: X.org 1.20.4 driver: fbdev,modesetting,vesa unloaded: openchrome tty: 128×48
Message: No advanced graphics data found on this system.

Se eu usar o pendrive preparado para inicializar/instalar com o antiX 19.2, partindo o computador via pendrive, eu conseguirei fazer as alterações diretamente nos arquivos de texto no modo gráfico, vocês saberiam me orientar por meio deste método quais alterações eu devo fazer nos arquivos de texto?

Grato.

marcelocripe

Texto original no idioma português do Brasil, traduzido para inglês pelo tradutor do Google.

[Member frogprince]

Running

sudo dmesg | tail

gives me only information on my optical mouse. The nvidia driver I need is 340.

I found

nouveau.modeset=0

Already at the end of that line. Setting it equal to one, or adding

`nvidia-drm.modeset=1′

gives the same result, no desktop. Running

startx

gives me the Xorg error. The Xorg.0 log says something about a missing framebuffer.
I’m typing this on another machine, so I can’t cut and paste.

I could reinstall, it would be a pain, but there’s no data at risk here. I would like
to know how to successfully install the nvidia driver; it’s faster and clearer.
One advantage of Antix is that nouveau works better with this distro than any other
I’ve tried.

• This reply was modified 2 years, 11 months ago by frogprince.

Vas you efer in Zinzinnati?

[Member stevesr0]

hi anticapitalista,

UPDATE: The 4.19 kernel booted to a full GRAPHIC desktop.

Thanks.

So, why did that work?

stevesr0
—————————————————————————————————-
(initial response before trying the 4.19 kernel version.)

thanks for suggestion. I will try it.

I am curious – does a video card get selected before the liveusb starts running? if so, do we need to add the linux driver for that video card in order to run a graphic display? if so, then we would start with a command line and then add the missing driver to the usb (with persistence) and then either reboot or use startx or equivalent to boot X?

stevesr0

• This reply was modified 2 years, 11 months ago by stevesr0.

[Moderator BobC]

So on my respin, without slim or lightdm, here is what I do…

in ~/.bashrc

xrunning=$(ps -ef | grep "/usr/lib/xorg/Xorg" | wc -l)
if [[ "$xrunning" -lt 2 ]]; then  
  # x not running
  echo ""
  echo "Starting X-Windows for antixbc..."
  antixbc
fi

and antixbc is

#!/bin/bash

. $HOME/.desktop-session/desktop-session.conf
. /usr/local/bin/desktop-session icewm
startx

• This reply was modified 2 years, 11 months ago by BobC.

[Forum Admin anticapitalista]

You can boot into level 3 (no Xorg) by adding a 3 to the grub menu list.

If you then want to get to desktop, after logging in as user, don’t use startx but

startx /usr/local/bin/desktop-session rox-icewm

(if you use rox-icewm)

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

antiX with runit - leaner and meaner.

I have a new Dell Vostro 5581 which hangs when booting antiX 19.2 from USB. The same USB boots fine on an older Lenovo laptop. The Dell has no problem booting Ubuntu from USB.

The boot process gets as far as Starting X and then nothing happens.

Reading /var/log/Xorg.0.log I see the following errors:

VESA(0): V_BIOS address 0x790 out of range
Screen(s) found, but none have a usable configuration.

no screens found(EE)

Server terminated with error (1). Closing log file.

This is after having tried to startx from the shell manually.

What can I do to find out what went wrong and/or fix it?

It is the same end result regardless of which option I select from the boot menu. I also find it inordinately hard to switch virtual terminals.

[Forum Admin anticapitalista]

It is possible to install apps before running the installer.
So anyone can actually install their ‘desktop’ before running the installer.
This *should* work.

eg for antiX-core (since it comes with wireless drivers)

1. Boot live-usb (with or without persistence)
2. login as root
3. Use ceni to set up network
3. apt update
4. apt install xorg antix-installer jwm (I chose jwm since it is tiny)
5. startx
6. open a terminal and type sudo minstall and follow the instructions
7. If you want to set keyboard as shown on the first screen, you also need to install fskbsetting
8. Enjoy!

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

antiX with runit - leaner and meaner.