Search Results for 'boot from iso'

[Member marcelocripe]

Hello imnull.

Welcome to antiX Linux and the forum.

I don’t know how to write in English and I send my texts translated by the internet translator. I hope you can understand everything, if your native language is not English, please translate my original Brazilian Portuguese text directly into your language with the help of internet translators.

When you’re able to boot antiX and install it to your hard drive, read the excellent tutorials created by @PPC that I’ve linked at the end of this post.

If you can’t boot official antiX in graphical mode, try with ISO Remastering antiX 21 Full 32 and 64-bit with Kernel 4.4.0-296.

If it works with this ISO, don’t forget to read the tutorials and important tips:

What is antiX and how to try it out or install it.
Short essential how-to list for the complete Linux newbie.
How-to install applications – 2020 version.
How to: correctly use antiX forum.

When I first started using antiX, I read the tutorials that PPC created, these readings saved me a lot of time and I think it saves time for any new antiX user. Your time will not be wasted with these readings, everything will seem to be much easier than you could imagine. You won’t waste your time searching the internet or even creating new topics, on the contrary, you will gain a lot of time with these readings.I recommend you try out desktops that have “zzz” in their name. I usually use zzz-IceWM or zzz-JWM or zzz-Fluxbox (each of these desktops has its own characteristics and consumes more or less resources), zzzFM will be the default file manager for your desktop, it it is very similar to the other file managers of other GNU/Linux distributions and Windows XP. To access other antiX workspaces, click on Menu, Desktop, Other Desktops and click on the workspace name, instantly the workspace will be loaded.

Whenever you need to ask for help or technical support in this forum, please explain in detail what is happening, don’t mince words, be thorough when writing, tell your computer characteristics such as make and model. If possible, post the result of the command $ inxi -Fxz from the terminal, copy and paste here in the message of the topic that you are going to create in this forum.
When you start a topic or participate with a post, remember to check the option “Notify me of follow-up replies via email”, by checking this option, you will receive a message in your email box whenever there are replies from topic in question.

marcelocripe
(Original text in Brazilian Portuguese language)

– – – – –

Olá imnull.

Seja bem-vindo(a) ao antiX Linux e ao fórum.

Eu não sei escrever em idioma Inglês e envio os meus textos traduzidos pelo tradutor da internet. Eu espero que você consiga compreender tudo, caso o seu idioma nativo não seja o Inglês, por favor, traduza o meu texto original em idioma Português do Brasil diretamente para o seu idioma com a ajuda dos tradutores da internet.

Quando você conseguir inicializar o antiX e instalar no seu disco rígido, leia os excelentes tutoriais criados pelo @PPC que eu relacionei no final desta postagem.

Se você não consegue inicializar o antiX oficial no modo gráfico, tente com a ISO Remasterização do antiX 21 Full de 32 e 64 bits com o Kernel 4.4.0-296.

Se funcionar com esta ISO, não se esqueça de ler os tutoriais e as dicas importantes:

What is antiX and how to try it out or install it.
Short essential how-to list for the complete Linux newbie.
How-to install applications – 2020 version.
How to: correctly use antiX forum.

Quando eu comecei a utilizar o antiX, eu li os tutoriais que o PPC criou, estas leituras me pouparam muito do meu tempo e acho que poupa o tempo de qualquer novo usuário do antiX. O seu tempo não será perdido com estas leituras, tudo parecerá ser muito mais fácil do que você poderia imaginar. Você não perderá o seu tempo com pesquisas na internet ou até mesmo em criar novos tópicos, ao contrário, você ganhará muito tempo com estas leituras.Eu recomendo você experimentar as áreas de trabalho que possuem “zzz” em seu nome. Eu costumo utilizar o zzz-IceWM ou zzz-JWM ou zzz-Fluxbox (cada uma destas áreas de trabalho possuem características próprias e consomem mais ou menos recursos), o zzzFM será o gerenciador de arquivos padrão da sua área de trabalho, ele é muito semelhante aos outros gerenciadores de arquivos das outras distribuições GNU/Linux e do Windows XP. Para acessar as outras áreas de trabalho do antiX, clique no Menu, Área de Trabalho, Alternar Entre as Áreas de Trabalho e clique sobre o nome da área de trabalho, instantaneamente a área de trabalho será carregada.

Sempre que você precisar solicitar ajuda ou suporte técnico neste fórum, explique com detalhes o que está acontecendo, não economize as palavras, seja minucioso ao escrever, informe as características do seu computador, como a marca e o modelo. Se for possível, poste o resultado do comando $ inxi -Fxz do terminal, copie e cole aqui na mensagem do tópico que você for criar neste fórum.
Quando você iniciar algum tópico ou participar com alguma postagem, lembre-se de marcar a opção “Notify me of follow-up replies via email”, marcando esta opção, você receberá uma mensagem na sua caixa de e-mail sempre que houver respostas do tópico em questão.

marcelocripe
(Texto original em idioma Português do Brasil)

I tried install antiX22 net iso in Gnome Boxes VM in My UEFI MX 21 laptop following along with Dolphin oracles youtube antiX-MATE net iso install series. When I rebooted after the initial install the screen halted at a prompt “installing from HDD” and just stayed there. It failed to boot up into the install. Does it not work on UEFI machines in Boxes or just not in boxes.
I thought maybe that was the problem but so I tried to install KVM/virt manager and I could not get Libvirtd running! I get this error. Are these the the wrong commands? How do I start libvirtd to open qemu/kvm?

sudo service libvirtd start

$ sudo systemctl start libvirt.service
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
buck@jasonsmx22:~
$ 
  

           dev: /dev/sda3 label: swapMX uuid: 3989b883-576a-441b-863d-9fad2040b159 
Unmounted: Message: No unmounted partitions found. 
USB:       Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 speed: 480 Mb/s 
           chip-ID: 1d6b:0002 class-ID: 0900 
           Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0 
           speed: 480 Mb/s chip-ID: 8087:0024 class-ID: 0900 
           Hub-3: 1-1.3:3 info: O2 Micro Oz776 1.1 Hub ports: 4 rev: 1.1 speed: 12 Mb/s 
           power: 2mA chip-ID: 0b97:7761 class-ID: 0900 
           Device-1: 1-1.3.2:5 info: O2 Micro OZ776 CCID Smartcard Reader type: Smart Card 
           driver: N/A interfaces: 1 rev: 1.1 speed: 12 Mb/s chip-ID: 0b97:7772 class-ID: 0b00 
           Device-2: 1-1.5:4 info: Microdia Dell Integrated HD Webcam type: Video 
           driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s power: 500mA 
           chip-ID: 0c45:643f class-ID: 0e02 
           Hub-4: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 speed: 480 Mb/s 
           chip-ID: 1d6b:0002 class-ID: 0900 
           Hub-5: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0 
           speed: 480 Mb/s chip-ID: 8087:0024 class-ID: 0900 
           Hub-6: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 speed: 480 Mb/s 
           chip-ID: 1d6b:0002 class-ID: 0900 
           Hub-7: 4-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.0 speed: 5 Gb/s 
           chip-ID: 1d6b:0003 class-ID: 0900 
Sensors:   System Temperatures: cpu: 63.0 C mobo: 44.0 C sodimm: SODIMM C 
           Fan Speeds (RPM): cpu: 0 
Info:      Processes: 227 Uptime: 6h 44m wakeups: 4 Init: SysVinit v: N/A runlevel: 5 default: 5 
           Compilers: gcc: N/A alt: 10 Packages: note: see --pkg apt: 2336 Shell: Bash v: 5.1.4 
           running-in: xfce4-terminal inxi: 3.3.06 
buck@jasonsmx22:~
$

[Moderator Brian Masinick]

blur13 wrote:

Heres an idea:

Keep a small 20 GB partition with a sid install where you can have the latest version of less frequently used programs, ie Gimp. You can easily access whatever files you create since its on the same HD. In fact, you can edit files directly on your main partition. Want to play the latest version of Wesnoth with improved AI. Boot into your sid install. Want to simply try out the latest version of some program, to see if the new features are worth the hassle of finding a .deb or compiling, then boot into your sid install. I’ve tried this myself and I think its a pretty good concept. I have to admit, I find Sid to be quite stable, I have yet to brick my system.

I can tell you, based on years and years of using various systems and distributions that Sid is not anywhere NEAR the most unstable system, in spite of the name and the wording. The only thing “unstable” about it in my opinion are the packaging dependencies; those are not in 100% of the cases completely correct, but they’re quickly corrected. To get the very latest software and have a “reasonable” chance that it’ll work, Sid is good.

In comparison, using Arch, Gentoo, and a few derivatives of these types of systems over the years, you are FAR MORE LIKELY to destroy your system, maybe ALL of your distributions if you are not watching closely, if you use any of these for a long time and don’t become a true expert and learn every possible nuance; that’s not necessary with Sid. In fact, the ONLY caution I’d give about Sid or Debian in general is that within 1-2 weeks before and after a release, you MIGHT want to hold off on a large number of package changes, because those are the most “risky” time periods – just before release, packaging groups try to get their new work or anything they want to make it into the release packaged. Usually they are OK, but a few incorrect packaging errors are about the only limited risk; stay away then and you reduce that risk to very near zero. Similarly, after code freeze, nothing gets changed, but once the release is complete, there is a great onslaught of changes; again, no super high risk, but sometimes a package goes in and a library might not reach a local repo until later, so there is a package/library mismatch risk when there are large numbers of changes. Again, not a HIGH risk, but in extreme cases you may experience breakage; avoid this window and as mentioned above, “no problem”.

I had around a dozen distributions on a Dell Dimension 4100 desktop ~15 years ago, and I was about ready to reorganize a few distros, their positioning on the disk, and the sizes of the partition, so I was ready to literally BREAK a few of them, so I beat on Sid. I *HAD* to do some absolutely STUPID things to get anything to even malfunction, so eventually I WIPED the system with one of those classic “boo-boo” moves – which is also effective to remove, (though not technically COMPLETELY remove): from root: rm -rf /

That will delete all files and directories. To truly wipe, it’s best to rewrite a disk over and over again with varying combinations of ones and zeros in order to totally obliterate any attempts to recover data or content in any possible way.

Anyway, Sid is a lot more stable than many commercial systems in my opinion. Though I often use antiX, I can (and have, many times), used Debian Sid, sidux, Kanotix, KNOPPIX, or siduction for what I’d consider to be important tasks, and they are more than up to the challenge; the user simply has to pay attention when updating software to make sure that all packages and libraries match the rest of the infrastructure; if they do, they work as well as anything else, and any defects are due to new software that may get an update – such defects are generally fixed promptly too and unless you heavily utilize the features of many apps, you may or may not even spot defects unless you do a deep dive looking for them.

None of this is to suggest that defects are absent; all software is prone to a few defects; they’re just not usually “show stopper” defects.

--
Brian Masinick

[Forum Admin rokytnji]

I keep a rack of old/current antiX, PLOP, Puppy, Hirens, and a bunch others I don’t remember like parted magic,KnoppiX, cd’s and dvd’s in 32 bit and anytime I see some one like exton make a 32 bit iso I grab it.

A lot of my 32 bit gear is gone now but 32 bit iso will boot on 64 bit gear. Plus. I have bunches of blank dvds.
Kinda like a bomb shelter.

My keeper 32 bit hardware is my atom single core touchscreen clamshell netbooks. Retired in laptop bags on the shelf.
I’m a 64 bit user now. At one time. I was the only antiX linux user on the planet running on a Amrel RT 786 EX touchscreen Military grade bullet proof laptop.
The linux users on such gear back then were a rare breed indeed. Not sure about now. 11 pound laptop kinda hard to lug around.

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

[Member punranger]

I would like to add to what Christopher says: First of all, maybe try creating the live USB again, and start from scratch. I would go with antiX 22 full ISO. Next, try to boot up with as little customization as possible. I generally just change the keyboard layout for my language. Stick with the default username and password for now, since the USB by default resets when you reboot.

Now, if you get that working, it might be a good idea to play around with the USB a while before trying an installation. Specifically, it might be a good idea to try to get persistence working on the USB. I don’t know your setup, but I would look in the advanced options menu at boot, try enabling the “text menus” option, and selecting the “persist all” option with the smallest possible persistence file size, and leave everything else at default. This way, you don’t have to start from scratch every time you reboot. A live USB with persistence is a great tool to have at your disposal, it’s like an operating system in your pocket. If you can’t get persistence working, no worries. The USB will in that case reset on reboot.

PS. Check the video in my signature for a walk-through of a standard installation.

EDIT: I see Chris beat me to it – his advice mirrors mine, and he really knows his sh*t!

• This reply was modified 5 months, 2 weeks ago by punranger.

antiX linux: The best way to revive an old computer - https://www.youtube.com/watch?v=JCTaUAP6sSg

Hi everybody,
this is my first try with antix (I’m presently running MX). I downloaded the latest full ISO, put it on a USB stick and booted. The system started, but the X server crashed immediately.
Here is the output:

X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
Build Operating System: linux Debian
Current Operating System: Linux antix1 4.9.0-326-antix.1-amd64-smp #1 SMP PREEMPT Fri Aug 26 21:21:08 EEST 2022 x86_64
Kernel command line: BOOT_IMAGE=/antiX/vmlinuz quiet splasht disable=lxF lang=de_DE kbd=de tz=Europe/Berlin
Build Date: 10 November 2021 11:00:13AM
xorg-server 2:1.20.11-1.0nosystemd1 (https://www.debian.org/support)
Current version of pixman: 0.40.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (–) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: “/home/demo/.local/share/xorg/Xorg.0.log”, Time: Fri Nov 25 14:12:54 2022
(==) Using config directory: “/etc/X11/xorg.conf.d”
(==) Using system config directory “/usr/share/X11/xorg.conf.d”
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
(EE)
Fatal server error:
(EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at “/home/demo/.local/share/xorg/Xorg.0.log” for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Here are what I think are the relevant system informations:

System: Kernel: 5.18.0-4mx-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: Xfce 4.16.0
tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 vt: 7 dm: LightDM 1.26.0
Distro: MX-21.2.1_ahs_x64 Wildflower August 28 2022 base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: <filter>
Mobo: ASUSTeK model: PRIME B450M-A II v: Rev X.0x serial: <filter>
BIOS: American Megatrends v: 3002 date: 03/10/2021
Battery: Message: No system battery data found. Is one present?
Memory: RAM: total: 31.26 GiB used: 1.89 GiB (6.0%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU: Info: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2 rev: 0 cache:
L2: 4 MiB bogomips: 114987
Speed: 2195 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 2195 2: 2195
3: 2195 4: 2195 5: 2194 6: 2196 7: 2196 8: 2196 9: 2196 10: 2195 11: 2196 12: 2155
13: 2479 14: 2193 15: 2196 16: 2196
Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1 bmi2 bpext cat_l3
cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy constant_tsc cpb cpuid cqm cqm_llc
cqm_mbm_local cqm_mbm_total cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists extapic
extd_apicid f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb ibs irperf
lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor movbe msr mtrr mwaitx
nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae pat pausefilter pclmulqdq
pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pni popcnt pse pse36 rapl
rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sev sev_es sha_ni skinit smap smca
smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp succor svm svm_lock syscall tce topoext
tsc tsc_scale umip v_spec_ctrl v_vmsave_vmload vgif vmcb_clean vme vmmcall wbnoinvd wdt
xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
Graphics: Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: ASUSTeK driver: nvidia v: 510.85.02
bus-ID: 09:00.0 chip-ID: 10de:1d01 class-ID: 0300
Display: x11 server: X.Org 1.20.14 compositor: xfwm4 v: 4.16.1 driver: loaded: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv resolution: 1920×1080~60Hz
s-dpi: 96
System: Kernel: 5.18.0-4mx-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: Xfce 4.16.0
tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 vt: 7 dm: LightDM 1.26.0
Distro: MX-21.2.1_ahs_x64 Wildflower August 28 2022 base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: <filter>
Mobo: ASUSTeK model: PRIME B450M-A II v: Rev X.0x serial: <filter>
BIOS: American Megatrends v: 3002 date: 03/10/2021
Battery: Message: No system battery data found. Is one present?
Memory: RAM: total: 31.26 GiB used: 1.89 GiB (6.0%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU: Info: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2 rev: 0 cache:
L2: 4 MiB bogomips: 114987
Speed: 2195 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 2195 2: 2195
3: 2195 4: 2195 5: 2194 6: 2196 7: 2196 8: 2196 9: 2196 10: 2195 11: 2196 12: 2155
13: 2479 14: 2193 15: 2196 16: 2196
Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1 bmi2 bpext cat_l3
cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy constant_tsc cpb cpuid cqm cqm_llc
cqm_mbm_local cqm_mbm_total cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists extapic
extd_apicid f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb ibs irperf
lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor movbe msr mtrr mwaitx
nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae pat pausefilter pclmulqdq
pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pni popcnt pse pse36 rapl
rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sev sev_es sha_ni skinit smap smca
smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp succor svm svm_lock syscall tce topoext
tsc tsc_scale umip v_spec_ctrl v_vmsave_vmload vgif vmcb_clean vme vmmcall wbnoinvd wdt
xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
Graphics: Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: ASUSTeK driver: nvidia v: 510.85.02
bus-ID: 09:00.0 chip-ID: 10de:1d01 class-ID: 0300
Display: x11 server: X.Org 1.20.14 compositor: xfwm4 v: 4.16.1 driver: loaded: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv resolution: 1920×1080~60Hz
s-dpi: 96
OpenGL: renderer: NVIDIA GeForce GT 1030/PCIe/SSE2 v: 4.6.0 NVIDIA 510.85.02
direct render: Yes
OpenGL: renderer: NVIDIA GeForce GT 1030/PCIe/SSE2 v: 4.6.0 NVIDIA 510.85.02
direct render: Yes

I think it has to do with the nvidia options. Any ideas?

– Bernd

I picked up another cheap laptop few days ago, and as I usually do I booted up a few distros from USB stick before deciding which one to install. When I booted antiX 21 (64, Full) it booted ok and the Connman screen appeared almost straight away. Problem is there isn’t any info in it.

The Status tab shows Wifi powered on, tethering off, but nothing in the services box at the bottom.
The Details tab shows a completely blank page.
The Wireless tab – At the top, just below Wireless Services, it shows Wifi Technologies, 1 found, 1 powered. All four of the buttons to the left, Connect, Disconnect, Remove, Rescan, are greyed out. The large box below is empty, no networks are shown.

Now this is where things get weird. If I plug the exact same USB stick into any of my other laptops antiX boots fine and Connman behaves perfectly as expected, and I can connect to internet immediately. Which would suggest there’s nothing wrong with the USB stick or iso.

However, all the other distros I tried on this particular laptop connected to internet without any problems. Which would suggest the laptop/wireless card isn’t at fault either.

I’m currently running MX on it (again, without any issues) and used that to identify the wireless card, which is a Qualcomm Atheros AR9285.

If anyone has any ideas as to what on earth is going on, please fire away, because I’m at a loss.

Thanks

[Member PPC]

Wow – there’s to much going on and not enough info!

First of all, welcome to antiX – and you had bad luck, I never faild to ever “boot” (that’s the correct expression, meaning start your computer running the Operting system from a device, in this case, a USB stick) any linux distro either from a thumbdrive or CD/DVD- with one exception, when I tried to start a 64bits OS on a 32bits only machine…

…but it that was the case, you would probably see an error message about that problem, since it’s a dual core. You may have had a problem either downloading the .iso file or brurning it to the USB stick- I never heard of UUI… I’ll try to find something and get back to you- if possible- post a picture (ex: taken it your phone) of the screen you get when you try to boot antiX, that could be helpfull…

Edit: You wrote another post when I was writing this one – it seems that you get, in fact, antiX’s boot screen, so probably the iso was correctly “burned” to the USB stick…
The motherboard could be incompatible with antiX – there’s an alternative .iso, a forum user created, that runs on old VIA machines- that could run on your’s if that’s the case…

P.

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

[Moderator caprea]

There was a problem with the base version 32bit
https://www.antixforum.com/forums/topic/having-trouble-with-antix-22-386-isos/

You could try the full version.
Also recommended for usb creation on windows are rufus or if rufus doesn’t work unetbootin .

Hello all…

I just last night decided to finally take the plunge and try Linux, and in searching I found antiX to be a very good fit for my intro. In these few short hours, after much reading and downloading, ans then more reading, searching the forums, etc. I have “successfully” ??? mounted the iso for antiX-base 32bit on a USB stick, and am now able to boot into a boot screen… and run into a wall. I have not found a solution to this in the forums, hence this post.

I just get a looping “Automatic boot in… __ seconds” with “Tab to edit” above that. If I do that, I get a string which I assume I can alter, but to what? ALSO, if I press escape I get “boot:” which tells me it can’t find that kernel for anything that I type in.

My system is an old HP Vista (not 7 ffs) laptop, 2core CPU, 1GB RAM, 30 some GBs left of disk space, a 7GB recovery partition I never use, a dead battery (always plugged in, gets really hot, needs air under it else it won’t start at all), and a dodgy power connect (very easy to unplug it). It has a CDRW drive BUT I do not have any disks to burn, and only ONE 7GB USB stick, which I used UUI to put the iso on it with. UUI is the only program I can get to work on this POS.

Please help! Thanks

[Member marcelocripe]

Lighter: smaller full ISO if possible, minimal RAM consumption (I agree with marcelocripe on the subject of old computers with few resources).

Rantanplan, about that, I think you can be carefree. Please read what the anticapitalista wrote about his views and intentions regarding antiX 21 on December 1, 2020. I recommend that you read the entire thread for proper context.

anticapitalista wrote:
We will try to keep CPU and RAM usage at idle down to a minimum. We mainly achieve this through not running unnecessary services on boot.

– – – – –

Lighter: smaller full ISO if possible, minimal RAM consumption (I agree with marcelocripe on the subject of old computers with few resources).

Rantanplan, quanto a isso, eu acho que você pode ficar despreocupado. Por favor, leia o que o anticapitalista escreveu sobre as suas visões e pretenções quanto ao antiX 21 no dia 1 de dezembro de 2020. Eu recomento você ler todo o tópico para ficar contextualizado adequadamente.

anticapitalista wrote:
We will try to keep CPU and RAM usage at idle down to a minimum. We mainly achieve this through not running unnecessary services on boot.

[Member marcelocripe]

Thinking ahead for the next major version release which will be based on Debian 12 (bookworm).

First of all, my big thanks to you, the dev team, the programmers for creating, maintaining and updating antiX Linux.

* It will be free of systemd/libsystemd0 and elogind/libelogind0
* As always, 4 window managers, 2 ‘desktops’
* Ships with 2 kernels on full editions

It’s always great to be free of systemd/libsystemd0 and elogind/libelogind0, to have the various options and combinations of window managers available in antiX, and to be able to boot with two different kernel options for the full ISOs that increase compatibility with different types of computers.

– 4.19 since 4.9 will be unsupported after Jan 2023
– 6 series kernel – rumors have it that 6.1 will have long-term support

This information makes me a little worried about “planned obsolescence” if this series 6 kernel is not compatible with computers that are more than 15 or 20 years old. But, it seems, it is inevitable that our Debian base will always advance in the direction of “planned obsolescence”. I have no idea how you’re going to get around this situation.

* Possible change – default to zzzFM/IceWM rather than Rox-IceWM

I support and want this change from the default Rox-IceWM to become zzzFM-IceWM. This change will be aimed at NEW USERS and does not affect anything for those of us who are familiar with the menus and options available in antiX. Before people complain against , please zzzFM-IceWM being the new standard, I ask you to think about new users when they come across ROX-Filer and don’t know how to handle this excellent file manager and misjudge antiX from hastily because they don’t know the various options that are available in antiX.

* Include a composer out of the box? If so, which one?

I don’t know what is the importance and usefulness of this feature and so I don’t know how to give any kind of opinion on this question.

* New wallpaper and default themes for all window managers?

I like the idea and suggest including the wallpapers from all previous editions of antiX. If this makes the ISO too large, which I find difficult to do due to the size of these images being small, then just the default wallpaper image from each of the previous editions of antiX.

* Others?

My suggestions are mixed with requests, please check the possibility and feasibility of them being implemented or not.

Requests and suggestions:
-Use all the latest translations available from the official Transifex and from the Transifex contribs.

-Use all the latest translations available in Transifex contribs/GitLab for .desktop files, especially .desktop files that are native antiX programs.

-For examples: SearchMonkey translations have been in Transifex contribs since January 2022 and could have already entered the updates. The “recent files” program (antiX recent files dynamic menu) which was reworked by BobC is also available on Transifex contribs since October 2022, the languages ​​that are translated are: fr, fr_BE, de, el, it, pt, pt_BR, ru. Unfortunately, our team of translators is limited to these languages, as it is difficult to find people willing to be volunteer translators.

-Can we translate the antiX updater?

-Use the latest version of the desktop-menu script which is very close to perfection. (Dave was working on getting the desktop-menu completed so we can use all the .desktop files translated by our community in the antiX menus).

-Use Debinstaller as GUI for installing .deb packages in antiX 22. BobC managed to make improvements to the program developed by PPC with regard to translations. I was able to successfully test the pt-BR language translations and see the warning windows working, except for the error windows that I couldn’t simulate to be absolutely sure that everything is working. I have submitted the latest version of Debinstaller reworked by BobC to PPC and I believe it is important to do another second language translation test. if everything works

Suggestions:

-Use in antiX 23 the wallpapers from previous antiX editions, from the first to the 22nd edition.

-FT10 available at full ISO. FT10 appears to be a “14 option window manager with file manager”, user toggles it on or off with just one click on the menu.

-The possibility of using antixscreenshot2.sh which is ready and has been updated by BobC and Robin, because this version has several very interesting features (just learn to speak…).

-The base ISO will still fit on a CD. I just don’t know how this will be possible with the increasing size of programs and controllers.

My main order:

Please create ways for antiX Linux to stay alive, even when we are no longer here. Unfortunately, people will inevitably get sick and die one day, as antiX Linux can live on for generations to come and live on forever.

marcelocripe
(Original text in Brazilian Portuguese language)

– – – – –

Thinking ahead for the next major version release which will be based on Debian 12 (bookworm).

Antes de mais nada, o meu muito obrigado a você, a equipe de desenvolvedores, aos programadores por criarem, manterem e atualizarem o antiX Linux.

* It will be free of systemd/libsystemd0 and elogind/libelogind0
* As always, 4 window managers, 2 ‘desktops’
* Ship with 2 kernels on full editions

É sempre muito bom estarmos livres do systemd/libsystemd0 e do elogind/libelogind0, ter as várias opções e as combinações de gerenciadores de janelas disponíveis no antiX e ainda a possibilidade de inicializar com duas opções de kernels diferentes para as ISOs full que aumentam a compatibilidade com os diversos tipos de computadores.

– 4.19 since 4.9 will be unsupported after Jan 2023
– 6 series kernel – rumours have it that 6.1 will have long-term support

Esta informação me deixa um tanto quanto preocupado com a “obsolescência programada” caso esta série 6 do kernel não tenha compatibilidade para os computadores com mais de 15 ou 20 anos de fabricação. Mas, ao que parece, é inevitável o avanço da nossa base Debian sempre na direção da “obsolescência programada”. Eu não tenho ideia de como você vai conseguir contornar esta situação.

* Possible change – default to zzzFM/IceWM rather than Rox-IceWM

Eu apoio e desejo que esta alteração do padrão Rox-IceWM passe a ser o zzzFM-IceWM. Esta alteração será destinada aos NOVOS USUÁRIOS e não atrapalha em nada para nós que conhecemos os menus e as opções disponíveis no antiX. Antes que as pessoas reclamarem se manifestando contra o , por favor zzzFM-IceWM ser o novo padrão, eu peço para pensarem nos novos usuários quando se deparam com o ROX-Filer e não sabem manusear este excelente gerenciador de arquivos e julgam mal o antiX de forma precipitada por não conhecerem as diversas opções que estão disponíveis no antiX.

* Include a compositor out of the box? If so, which one?

Eu não sei qual é a importância e utilidade deste recurso e por isso eu não sei dar qualquer tipo de opinião sobre esta pergunta.

* New wallpaper and default themes for all window managers?

Eu gosto da ideia e sugiro incluir os papéis de parede de todas as edições anteriores do antiX. Se isso deixar a ISO muito grande, o que eu acho difícil de acontecer devido ao tamanho destas imagens serem pequenos, então apenas a imagem padrão do papel de parede de cada uma das edições anteriores do antiX.

* Others?

As minhas sugestões se misturam com pedidos, por favor, verifique a possibilidade e a viabilidade de serem implementadas ou não.

Pedidos e sugestões:
-Utilizar todas as traduções mais recentes disponíveis no Transifex oficial e do Transifex contribs.

-Utilizar todas as traduções mais recentes disponíveis no Transifex contribs/GitLab para os arquivos .desktop, em especial os arquivos .desktop que são dos programas nativos do antiX.

-Por exemplos: As traduções do SearchMonkey estão no Transifex contribs desde janeiro de 2022 e já poderiam ter entrado nas atualizações. O programa “recent files” (antiX recent files dynamic menu) que foi retrabalhado pelo BobC também está disponível no Transifex contribs desde outubro de 2022, os idiomas que estão traduzidos são: fr, fr_BE, de, el, it, pt, pt_BR, ru. Infelizmente a nossa equipe de tradutores estão limitados a estes idiomas, haja vista que é difícil encontrar pessoas dispostas a serem tradutores voluntários.

-Nós podemos traduzir o atualizador do antiX?

-Utilizar a versão mais recente do script desktop-menu que está muito próximo da perfeição. (O Dave estava trabalhando para que o desktop-menu seja concluído, assim poderemos utilizar todos os arquivos .desktop traduzidos pela nossa comunidade nos menus do antiX).

-Utilizar o Debinstaller como GUI para a instalação de pacotes .deb no antiX 22. O BobC conseguiu fazer as melhorias no programa desenvolvido pelo PPC no que diz respeito às traduções. Eu consegui testar com sucesso as traduções em idioma pt-BR e ver funcionando as janelas de avisos, exceto as janelas de erros que eu não consegui simular para ter certeza absoluta de que tudo está funcionando. Eu enviei para o PPC a versão mais recente do Debinstaller retrabalhado pelo BobC e acredito que seja importante fazer outro teste de tradução de um segundo idioma. Se tudo funcionar

Sugestões:

-Utilizar no antiX 23 os papéis de parede das edições anteriores antiX, desde a primeira até a edição 22.

-O FT10 disponível na ISO full. O FT10 parece ser uma “14 opção de gerenciador de janelas com gerenciador de arquivos”, o usuário ativa ou desativa com apenas um clique no menu.

-A possibilidade de utilizar o antixscreenshot2.sh que está pronto e foi atualizado pelo BobC e o Robin, porque esta versão possui diversas funcionalidades muito interessantes (só falta aprender falar…).

-A ISO base continuar cabendo em um CD. Eu só não sei como isso será possível com o tamanho cada vez maior dos programas e dos controladores.

O meu pedido principal:

Por favor, crie meios do antiX Linux continuar vivo, mesmo quando nós não estivermos mais aqui. Infelizmente, as pessoas inevitavelmente adoecerão e morrerão um dia, já o antiX Linux pode continuar vivo para as próximas gerações e viver eternamente.

marcelocripe
(Texto original em idioma Português do Brasil)

[Forum Admin rokytnji]

Success

harry@scooter:~
$ sudo parted -l
[sudo] password for harry: 
Model: ATA TS32GMTS800 (scsi)
Disk /dev/sda: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system     Flags
 1      1049kB  538MB   537MB   primary  fat32           esp
 3      538MB   30.9GB  30.4GB  primary  ext4            boot
 2      30.9GB  32.0GB  1086MB  primary  linux-swap(v1)

Model: TOSHIBA External USB 3.0 (scsi)
Disk /dev/sdc: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  1000GB  1000GB  primary  ntfs         boot

harry@scooter:~
$ df -h /dev/sdc1
Filesystem      Size  Used Avail Use% Mounted on
/dev/sdc1       932G  281G  652G  31% /media/harry/TOSHIBA EXT

Love it when a plan comes together.

$ inxi -zv8
System:
  Kernel: 5.10.142-antix.2-amd64-smp arch: x86_64 bits: 64
    compiler: gcc v: 10.2.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.142-antix.2-amd64-smp
    root=UUID=ddec6fb9-cec9-4bd7-b2f7-ae23e7048674 ro quiet
  Desktop: IceWM v: 3.0.1 dm: slimski v: 1.5.0
    Distro: antiX-22_x64-full Grup Yorum 18 October 2022
    base: Debian GNU/Linux 11 (bullseye)
Machine:
  Type: Desktop Mobo: Intel model: NUC5i3RYB v: H41000-505
    serial: <superuser required> UEFI-[Legacy]: Intel
    v: RYBDWi35.86A.0361.2016.1202.1005 date: 12/02/2016
Battery:
  Message: No system battery data found. Is one present?
Memory:
  RAM: total: 3.73 GiB used: 1.29 GiB (34.7%)
  RAM Report:
    permissions: Unable to run dmidecode. Root privileges required.
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i3-5010U bits: 64 type: MT MCP
    arch: Broadwell gen: core 5 built: 2015-18 process: Intel 14nm
    family: 6 model-id: 0x3D (61) stepping: 4 microcode: 0x2F
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled
    cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB
    desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 1995 high: 1996 min/max: 500/2000 scaling:
    driver: intel_cpufreq governor: performance cores: 1: 1995
    2: 1996 3: 1996 4: 1996 bogomips: 16760
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_perfmon avx avx2 bmi1 bmi2 bts clflush cmov constant_tsc
    cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts epb ept
    ept_ad erms est f16c flexpriority flush_l1d fma fpu fsgsbase
    fxsr ht ibpb ibrs intel_pt invpcid invpcid_single lahf_lm lm
    mca mce md_clear mmx monitor movbe msr mtrr nonstop_tsc nopl
    nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni
    popcnt pse pse36 pti pts rdrand rdseed rdtscp rep_good sdbg
    sep smap smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp
    syscall tm tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer
    vme vmx vnmi vpid x2apic xsave xsaveopt xtopology xtpr
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache
    flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: retbleed status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass
    disabled via prctl and seccomp
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and
    __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional,
    IBRS_FW, STIBP: conditional, RSB filling, PBRSB-eIBRS: Not
    affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel HD Graphics 5500 driver: i915 v: kernel
    arch: Gen8 process: Intel 14nm built: 2014-15 ports:
    active: HDMI-A-1 empty: DP-1,HDMI-A-2 bus-ID: 00:02.0
    chip-ID: 8086:1616 class-ID: 0300
  Display: server: X.Org v: 1.20.11 driver: X:
    loaded: modesetting unloaded: fbdev,vesa gpu: i915
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1024x768 s-dpi: 96
    s-size: 270x203mm (10.63x7.99") s-diag: 338mm (13.3")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 model-id: NCS 0x2275
    built: 2018 res: 1024x768 hz: 60 dpi: 102 gamma: 1 chroma: red:
    x: 0.620 y: 0.329 green: x: 0.290 y: 0.592 blue: x: 0.137
    y: 0.110 white: x: 0.298 y: 0.329
    size: 256x192mm (10.08x7.56") diag: 378mm (14.9")
    ratio: 4:3, 5:4 modes: 1024x768, 1920x1080, 1280x1024,
    1440x900, 1280x960, 1360x768, 1280x800, 1280x720, 720x480
  OpenGL: renderer: Mesa Intel HD Graphics 5500 (BDW GT2)
    v: 4.6 Mesa 20.3.5 direct render: Yes
Audio:
  Device-1: Intel Broadwell-U Audio driver: snd_hda_intel
    v: kernel bus-ID: 00:03.0 chip-ID: 8086:160c class-ID: 0403
  Device-2: Intel Wildcat Point-LP High Definition Audio
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:9ca0 class-ID: 0403
  Sound Server-1: ALSA v: k5.10.142-antix.2-amd64-smp
    running: yes
Network:
  Device-1: Intel Ethernet I218-V driver: e1000e v: kernel
    port: 2080 bus-ID: 00:19.0 chip-ID: 8086:15a3 class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Intel Wireless 7265 driver: iwlwifi v: kernel
    modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    bus-ID: 02:00.0 chip-ID: 8086:095a class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IP v6: <filter> scope: link
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB
    driver: btusb v: 0.8 bus-ID: 2-7:3 chip-ID: 8087:0a2a
    class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 1 state: up
    address: <filter> bt-v: 2.1 lmp-v: 4.2 sub-v: 1000 hci-v: 4.2
    rev: 1000
  Info: acl-mtu: 1021:5 sco-mtu: 96:6
    link-policy: rswitch hold sniff link-mode: slave accept
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 961.33 GiB used: 284.29 GiB (29.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Transcend
    model: TS32GMTS800 size: 29.82 GiB block-size: physical: 512 B
    logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter>
    rev: 8B scheme: MBR
  ID-2: /dev/sdc maj-min: 8:32 type: USB vendor: Toshiba
    model: External USB 3.0 size: 931.51 GiB block-size:
    physical: 512 B logical: 512 B type: N/A serial: <filter>
    rev: 5438 scheme: MBR
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 28.3 GiB size: 27.69 GiB (97.84%)
    used: 4.26 GiB (15.4%) fs: ext4 dev: /dev/sda3 maj-min: 8:3
    label: rootantiX22 uuid: ddec6fb9-cec9-4bd7-b2f7-ae23e7048674
  ID-2: /media/harry/TOSHIBA EXT raw-size: 931.51 GiB
    size: 931.51 GiB (100.00%) used: 280.03 GiB (30.1%) fs: ntfs
    dev: /dev/sdc1 maj-min: 8:33 label: TOSHIBA EXT
    uuid: 803284B13284ADAA
Swap:
  Kernel: swappiness: 10 (default 60)
    cache-pressure: 50 (default 100)
  ID-1: swap-1 type: partition size: 1.01 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda2 maj-min: 8:2 label: N/A
    uuid: d4674d03-607f-4de9-abd8-a72ea41e4d0a
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 512 MiB fs: vfat label: N/A
    uuid: A025-F394
USB:
  Hub-1: 1-0:1 info: Full speed or root hub ports: 2 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-2: 1-1:2 info: Intel Integrated Hub ports: 8 rev: 2.0
    speed: 480 Mb/s chip-ID: 8087:8001 class-ID: 0900
  Hub-3: 2-0:1 info: Hi-speed hub with single TT ports: 11
    rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-4: 2-4:2 info: Huasheng 4-port hub [Maxxter ACT-HUB2-4P
    HS8836 iSoul ultra-slim]
    ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
    chip-ID: 214b:7000 class-ID: 0900
  Device-1: 2-4.1:9 info: Toshiba America External USB 3.0
    type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.1
    speed: 480 Mb/s power: 500mA chip-ID: 0480:a00c class-ID: 0806
    serial: <filter>
  Device-2: 2-4.2:5 info: Monterey Keyboard type: Keyboard,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1
    speed: 1.5 Mb/s power: 100mA chip-ID: 0566:3107 class-ID: 0300
  Device-3: 2-4.3:6 info: Logitech Optical Wheel Mouse
    type: Mouse driver: hid-generic,usbhid interfaces: 1 rev: 2.0
    speed: 1.5 Mb/s power: 100mA chip-ID: 046d:c016 class-ID: 0301
  Device-4: 2-4.4:7 info: GEMBIRD MicroSD Card Reader/Writer
    type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0
    speed: 480 Mb/s power: 150mA chip-ID: 1908:0226 class-ID: 0806
  Device-5: 2-7:3 info: Intel Bluetooth wireless interface
    type: Bluetooth driver: btusb interfaces: 2 rev: 2.0
    speed: 12 Mb/s power: 100mA chip-ID: 8087:0a2a class-ID: e001
  Hub-5: 3-0:1 info: Super-speed hub ports: 4 rev: 3.0
    speed: 5 Gb/s chip-ID: 1d6b:0003 class-ID: 0900
Sensors:
  System Temperatures: cpu: 41.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: apt: 1569 lib: 741
  Active apt repos in: /etc/apt/sources.list.d/antix.list
    1: deb http://mirrors.rit.edu/mxlinux/mx-packages/antix/bullseye bullseye main nosystemd nonfree
  Active apt repos in: /etc/apt/sources.list.d/bullseye-backports.list
    1: deb http://deb.debian.org/debian bullseye-backports main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://ftp.us.debian.org/debian/ bullseye-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://ftp.us.debian.org/debian/ bullseye main contrib non-free
    2: deb http://security.debian.org/ bullseye-security main contrib non-free
  No active apt repos in: /etc/apt/sources.list.d/various.list
Processes:
  CPU top: 5 of 173
  1: cpu: 17.9% command: firefox-esr pid: 22728
    mem: 545.8 MiB (14.2%)
  2: cpu: 14.8% command: firefox-esr pid: 24611
    mem: 177.7 MiB (4.6%)
  3: cpu: 2.3% command: firefox-esr pid: 22844
    mem: 174.2 MiB (4.5%)
  4: cpu: 1.8% command: xorg pid: 1751 mem: 90.1 MiB (2.3%)
  5: cpu: 1.1% command: firefox-esr pid: 22871
    mem: 126.9 MiB (3.3%)
  Memory top: 5 of 173
  1: mem: 545.8 MiB (14.2%) command: firefox-esr pid: 22728
    cpu: 17.9%
  2: mem: 177.7 MiB (4.6%) command: firefox-esr pid: 24611
    cpu: 14.8%
  3: mem: 174.2 MiB (4.5%) command: firefox-esr pid: 22844
    cpu: 2.3%
  4: mem: 126.9 MiB (3.3%) command: firefox-esr pid: 22871
    cpu: 1.1%
  5: mem: 90.1 MiB (2.3%) command: xorg pid: 1751 cpu: 1.8%
Info:
  Processes: 173 Uptime: 1h 2m wakeups: 1 Init: SysVinit v: 2.96
  runlevel: 5 default: 5 tool: service Compilers: gcc: 10.2.1
  alt: 10 Shell: Bash v: 5.1.4 running-in: roxterm inxi: 3.3.19
harry@scooter:~

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

[Member seaken64]

Okay, I have read through this thread at least three times. It seems to me that the OP was trying to create a Live USB of antiX using a copy of LUM under Mint. Is that correct?

In that case, yes, you can select to create Full Featured Live USB bootable drive, since the iso is an antiX. If the OP was trying to create another bootabel Mint USB drive then they could only choose to use the “dd” mode.

After the Full Featured Live antiX uUSB has been created the OP will have the choice to use ALL the features of the bootable antiX USB drive, including saving changes to the boot settings and Persistence modes for the running live system. From that live running antiX they then have the option to INSTALL the Full system to the hard drive (Assuming that the iso used was fior the Full version of antiX).

The use of the word “installer” was incorrect in the beginning being in reference to the Live USB “MAKER”, not installer. The installer is on the Live USB once the MAKER software is used to create the Live USB.

So, the answer to the now re-phrased question is to use the Live USB Maker (aka LUM), if available to you. If not, then use another suitable live USB “MAKER”, or “burner”, such a unetbootin or Belana Etcher, or Rufus.

[In this case the OP already had LUM in use].

The question in the URL link is still “using-installer-tool” and the answer to that is you don’t use the installer tool from another distro. You use a Live USB or Live DVD to install once created with a Live USB MAKER, or burner.

Seaken64

Bought me a Dell Chromebook with Kali Linux that I played with for awhile.
Decided enough was enough and made up a 64 bit antiX full iso usb.
Hit the escape key when turning this on to pick usb bootup.
Good news. Booted up just fine. Installed just fine. Most hardware worked out of the box
Bad news. No sound. No 2 finger tap. Takes 3 fingers for the 2 finger action.
Tap was easy to fix.
https://www.antixforum.com/forums/topic/acer-c710-chromebook/
Glad I posted earlier.

Sound fix required pulse audio install for my fumbling about in alsa on my lonesome
Took me 2 days to find this page
https://blog.nanax.fr/post/2018-05-01-chromebook-linux/

Now youtube and xmms play noise. Before
speaker-test
button in hardware crashed in antiXcc . Running it terminal would throw errors but no sound.
Now it works in terminal

harry@antix1:~
$ inxi -Fxz
System:
  Kernel: 5.10.153-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc
    v: 10.2.1 Desktop: IceWM v: 3.2.0 Distro: antiX-22_x64-full Grup Yorum 18
    October 2022 base: Debian GNU/Linux 11 (bullseye)
Machine:
  Type: Laptop System: GOOGLE product: Candy v: 1.0
    serial: <superuser required>
  Mobo: GOOGLE model: Candy v: 1.0 serial: <superuser required>
    UEFI: coreboot v: MrChromebox-4.18.1 date: 10/27/2022
Battery:
  ID-1: BAT0 charge: 42.2 Wh (100.0%) condition: 42.2/44.5 Wh (94.9%)
    volts: 12.9 min: 11.4 model: Samsung DELL XK status: full
CPU:
  Info: dual core model: Intel Celeron N2840 bits: 64 type: MCP
    arch: Silvermont rev: 8 cache: L1: 112 KiB L2: 1024 KiB
  Speed (MHz): avg: 2292 high: 2459 min/max: 500/2582 cores: 1: 2459 2: 2125
    bogomips: 8666
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display
    driver: i915 v: kernel bus-ID: 00:02.0
  Device-2: Suyin Integrated_Webcam_HD type: USB driver: uvcvideo
    bus-ID: 1-3:4
  Display: server: X.Org v: 1.20.11 driver: X: loaded: modesetting
    unloaded: fbdev,vesa dri: i965 gpu: i915 resolution: 1366x768~60Hz
  API: OpenGL v: 4.2 Mesa 20.3.5 renderer: Mesa DRI Intel HD Graphics (BYT)
    direct render: Yes
Audio:
  Device-1: Intel Atom Processor Z36xxx/Z37xxx Series High Definition Audio
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
  Sound API: ALSA v: k5.10.153-antix.1-amd64-smp running: yes
  Sound Server-1: PulseAudio v: 14.2 running: no
Network:
  Device-1: Intel Wireless 7260 driver: iwlwifi v: kernel bus-ID: 01:00.0
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
    bus-ID: 1-4:6
  Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: running
    rfk-block: hardware: no software: yes address: <filter>
Drives:
  Local Storage: total: 44.65 GiB used: 20.7 GiB (46.4%)
  ID-1: /dev/mmcblk1 vendor: Hynix model: HAG2e size: 14.68 GiB
  ID-2: /dev/sda type: USB vendor: PNY model: USB 2.0 FD size: 29.97 GiB
Partition:
  ID-1: / size: 13.36 GiB used: 7.09 GiB (53.1%) fs: ext4 dev: /dev/mmcblk1p2
  ID-2: /boot/efi size: 252 MiB used: 274 KiB (0.1%) fs: vfat
    dev: /dev/mmcblk1p1
Swap:
  ID-1: swap-1 type: partition size: 768 MiB used: 0 KiB (0.0%)
    dev: /dev/mmcblk1p3
Sensors:
  System Temperatures: cpu: 41.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 140 Uptime: 22m Memory: 3.75 GiB used: 1.17 GiB (31.3%)
  Init: SysVinit runlevel: 5 Compilers: gcc: 10.2.1 Packages: 1625 Shell: Bash
  v: 5.1.4 inxi: 3.3.23

harry@antix1:~
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: chtmax98090 [chtmax98090], device 0: 3 []
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 1: chtmax98090 [chtmax98090], device 1: Deep-Buffer Audio (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Using that nanax.fr thread. I errored out a bit following the restart commands. Reboot seemed to fix it though cuz I had sound after that.

Hopefully some one > like me > can use this thread. 😀 Tickled pink I got this working. I did not want to go back to Kali where sound and tap worked.

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems