Search Results for 'boot from iso'

[Member PDP-8]

Try VENTOY (Windows, Linux – gpl3)

https://www.ventoy.net/en/index.html

I had the same issues, and then found Ventoy. Out of the box I was able to multiboot antiX and MXlinux 19.2 on my uefi-only boxes without any problems. Some other distros were hit or miss.

Interesting concept – you “install” Ventoy to the stick. Then all you have to do is put ISO’s on that stick. Ventoy figures out the rest without creating a spaghetti-mess of files on the stick – it’s just booting isos directly.

As such, I treat all multibooters as “live-media” convenience, and either do a frugal install, or do what antiX does best – awesome user-definable persistence.

As with all 3rd party booters, one needs to be careful which way to point fingers if something goes wrong. Not fair to blame the antiX (or other distro) devs for instance if something goes pear-shaped in the process.

I don’t know how many distro devs will want to abide by being “Ventoy compatible” as described in their docs.

I haven’t tested all the corner cases, and only did a quick run with antiX and MXlinux, but so far so good.

• This reply was modified 2 years, 10 months ago by PDP-8.

[Member marcelocripe]

BobC,

5 – With the pendrive ready to boot with antiX-17.4.1_x64-full.iso, after the boot, I selected F2 Language, with the arrow to the right and up, select Portuguese (BR) and Enter, in Boot option:

quiet splash=v disable=lx

I changed it to:

xorg=vesa

Enter

AntiX-17.4.1 64 bit was able to load in graphic mode, the video is slow, better than booting with Safe Video Mode, however it is not yet possible to play a local video or access Youtube.

6 – With the pendrive ready to boot with antiX-17.4.1_x64-full.iso, after the boot, I selected F2 Language, with the right and up arrow, select Portuguese (BR) and Enter, in Boot option:

quiet splash=v disable=lx

I changed it to:

xorg=openchrome

Enter

AntiX-17.4.1 64 bit, failed to load in graphical mode, stopped at the command prompt, I entered the user: demo and the password: demo

demo @ antix: ~
$ startx {Enter}

X.Org X Server 1.19.2
Release date: 2017-03-02
X Protocol Version 11, Revision 0
… Linux 4.19.4-antix2-amd64-smp x86_64 antiX
…
…
…
… (EE) (EE) Server terminated for help (1). Closinglog file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Do the results of these tests help in any way?

marcelocripe

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

—————–

BobC,

5 – Com o pendrive preparado para inicializar com o antiX-17.4.1_x64-full.iso, após o boot, selecionei F2 Language, com a seta para direita e para cima, selecionar Português (BR) e Enter, em Opção de inicialização:

quiet splash=v disable=lx

Alterei para:

xorg=vesa

Enter

O antiX-17.4.1 64 bit conseguiu carregar em modo gráfico, o vídeo está lento, melhor do que inicializando com Safe Video Mode, contudo ainda não é possível tocar um vídeo local ou acessar o Youtube.

6 – Com o pendrive preparado para inicializar com o antiX-17.4.1_x64-full.iso, após o boot, selecionei F2 Language, com a seta para direita e para cima, selecionar Português (BR) e Enter, em Opção de inicialização:

quiet splash=v disable=lx

Alterei para:

xorg=openchrome

Enter

O antiX-17.4.1 64 bit, não conseguiu carregar em modo gráfico, parou no prompt de comando, entrei com o usuário: demo e a senha: demo

demo@antix:~
$ startx {Enter}

X.Org X Server 1.19.2
Release date: 2017-03-02
X Protocol Version 11, Revision 0
… Linux 4.19.4-antix2-amd64-smp x86_64 antiX
…
…
…
… (EE) (EE) Server terminated for help (1) . Closinglog file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Os resultados destes testes ajudam de alguma forma?

marcelocripe

Texto original em idioma português do Brasil, traduzido para o inglês por Google tradutor.

• This reply was modified 2 years, 10 months ago by marcelocripe.
• This reply was modified 2 years, 10 months ago by marcelocripe.

[Member arp]

Regarding the stall at /dev, it happens with MX Linux, antiX base, and antiX full. These were from USB. I will try DVD later today.

I have not tried other ‘boot options,’ but I welcome any suggestions.

I did not check the MDM5dsum because I downloaded the ISOs by torrent, and my understanding is that it self-checks.

Thanks!

[Member seaken64]

Hello – just getting started here.
I have a lot of experience with bigger systems but not a lot with PC hardware. I was a Windows user with some Unix but only as a user.

I have an old Dell Latitude C540 I am trying make useful. 348MB Mem and a 20 GB disk. No Wi-Fi and a single USB-1 port
Bios boot sequence is Floppy, CD, then HD (USB is not an option on the boot list)
I set up two partitions 18GB primary and a 2GB for swap. I thought there was a small partition at the low end but it is gone now.

I have a antiX 19.2.1 386-base LiveCD working and trying installs to hard disk from there but first install attempt failed at the GRUB install
I told install to use all of the disk.
I restarted the system from the CD and used the disk partition to set the boot flag on the primary and asked for an install of grub on the main partition.
– the install runs to the end but when I remove the CD and try to boot I end up with a blank screen and no disk activity.
I am missing something related to the MBR – just have no clue what it might be

Hello prices1950, welcome to antiX.

I think antiX is a good choice for that old computer. I have antiX working on similar equipment. But it may be not straight forward and may require some effort to get the kinks worked out.

If I were you I would try to boot from the USB 1.1 port using a FULL iso. But if that won’t work then the Base CD will work. You may be aware already, sometimes the BIOS uses the “Hard Drive” category to boot from USB. Put the USB drive in the port before turning on then check if the USB drive is on the list of hard drives for booting.

PLOP works for me. I use a PLOP CD and then I set the USB 1.1 port to “Mode 1”. You may have to experiment with your hardware. Once you have it booting from USB you can make your Floppy as mentioned by Roky.

antiX-19 will run in 384M RAM. But if you can you should update the RAM to 1G. That machine supports two SO-DIMM chips of up to 512M each. At the very least get one 256M chip and get to 512M.

You may be having some video card issues. Or, it may be the Grub as you suspect. Try booting into Failsafe mode. Also, you may use gparted to wipe the drive and start fresh. I usually reset the drive to MBR, then reformat to one single EXT4 partition. Then let antiX installer do an auto install and take over the drive. It will repartition and format for you.

Good luck, and have fun.

Seaken64

[Forum Admin rokytnji]

I built me a PLOP floppy disc so I could boot off usb 1.1.

3.1. Floppy
__________________________________________________________________

You create the install floppy with a floppy disk image. A floppy disk
image is a file that contains every sector of the floppy disk. You
cannot copy the image file on a floppy disk like a common file. It’s
required to use a special program that writes sector per sector of the
image file to the floppy disk sectors. There are many programs
available to do this.

Download the current boot manager [94]plpbt-5.0.14.zip. Extract it to
get the floppy disk image. You find the disk image in the install
directory. The name of the file is plpbtin.img

How to create the floppy:

DOS: You can use [95]diskimg.com with diskimg -d a -w plpbtin.img

Windows: Write the disk image with the program [96]rawwritewin to the
floppy disk

Linux: dd if=plpbtin.img of=/dev/fd0

I’d start with base iso. You got to patient. Booting on usb 1.1 can be like watching paint dry. Things will improve after hard drive install takes over.

Keep it simple. Good Luck.

Edit: My quote is my notes on the 3.1 version. PLOP is now in version 5 I think. My instructions are still relevant. Version number naming is the the only difference.

2nd edit: Strike that statement by me about starting with base iso. One can switch over to other window managers using full and it would be better to have all libs and tools for a new user. Ram should not stop boot of full iso either.

• This reply was modified 2 years, 10 months ago by rokytnji.
• This reply was modified 2 years, 10 months ago by rokytnji.

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 marcelocripe]

Hello dear colleagues, how are you?

I apologize for the delay, but time-consuming tests I can only perform on the weekend.

BobC if you can do me a favor and teach me the step by step or tutorial on how to use the cheat codes you suggested, you will be very welcome to me and to everyone who is reviving old computers or with computers that have chip sets of motherboard that antiX 19.2 does not have a compatible driver.

I managed to do more tests on the other computer, it really has a damaged onboard video card and will need to receive the GF MX4000 offboard video card.

Here are the results of the tests using the Via VT8237R Plus onboard video card from the MSI 238318 motherboard brand and model Semp Toshiba Info ES-1513:

1 – I installed Win XP SP3 and installed the video driver and the response was normal without any problem.

2 – I installed SliTaz 5.0-RC4 (image downloaded on 04-07-2020), the video was better on Win XP than on SliTaz, I realized that the answer was slightly slow compared to Win XP. (I hope I won’t be punished for naming other operating systems in this forum).

3 – I prepared the pendrive to boot with antiX-17.4.1_x64-full.iso, after boot, I selected F2 Language, with the right and up arrow, select Portuguese (BR) and Enter, the options menus were displayed in Portuguese, F3 São Paulo Time Zone. I selected antX-17.4.1 x64-full (28 March 2019) I hit Enter and what I didn’t want happened, stopped at the command prompt, I entered the user: demo and password: demo

demo @ antix: ~
$ startx {Enter}

X.Org X Server 1.19.2
release date: 2017-03-02
X Protocol Version 11, Revision 0
… Linux 4.19.4-antix2-amd64-smp x86_64 antiX
…
…
…
… (EE) (EE) Server terminated for help (1). Closinglog file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

4 – I restarted the computer again and selected the second option: Safe Video Mode, the images fail, the response is slow, not as slow as in antiX 19.2.

Obs .: Wow! Since the antiX-17.4.1 menu and taskbar are very beautiful! I found antiX-17.4.1’s menu and taskbar simpler than antiX 19.2’s. It is clearer and easier to read. Another detail is that antiX-17.4.1 consumes about 114MB of RAM, the processing was about 54%.

I was able to complete the installation successfully, after the computer restarted with the boot configured to start via HD, antiX-17.4.1 was started with extreme difficulties in the video responses, similar to Safe Video Mode via pendrive.

Apparently antiX-17.4.1 also does not support this video card, but it behaved better than antiX 19.2, however it is still not feasible to use this computer with antiX until the video controller is resolved, which would be unfortunate not to use antiX due to the video.

If anyone has any more ideas they will be very welcome.

Anyway, I would like to thank everyone who collaborated with their considerations and teachings, certainly this post will be of great use to other colleagues.

marcelocripe

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

————–

Olá caro colegas, tudo bem com vocês?

Peço desculpas pela demora, mas testes demorados eu só conseguo realizar no final de semana.

BobC se você puder me fazer uma gentileza e me ensinar o passo a passo ou tutorial de como usar os códigos de trapaça que você sugeriu, serão muito bem vindos para mim e para todos que estejam revivendo computadores antigos ou com computadores que tenham chip set de placa-mãe que o antiX 19.2 não possui driver compatível.

Eu consegui fazer mais testes no outro computador, realmente está com a placa de vídeo onboard danificada e precisará receber a placa de vídeo offboard GF MX4000.

Seguem os resultados dos testes utilizando a placa de vídeo onboard Via VT8237R Plus da placa mãe MSI 238318 marca e modelo Semp Toshiba Info ES-1513:

1 – Instalei do Win XP SP3 e a instalação do driver de vídeo e a resposta foi normal sem qualquer problema.

2 – Instalei o SliTaz 5.0-RC4 (imagem baixada no dia 04-07-2020), o vídeo foi melhor no Win XP do que no SliTaz, percebi que a reposta apresentava pequena lentidão em relação ao Win XP. (Espero não ser punido por citar nome de outros sistemas operacionais neste fórum).

3 – Preparei o pendrive para inicializar com o antiX-17.4.1_x64-full.iso, após o boot, selecionei F2 Language, com a seta para direita e para cima, selecionar Português (BR) e Enter, os menus de opções foram exibidos em Português, F3 Fuso Horário de São Paulo. Selecionei antX-17.4.1 x64-full (28 March 2019) pressionei Enter e aconteceu o que eu não queria, parou no prompt de comando, entrei com o usuário: demo e a senha: demo

demo@antix:~
$ startx {Enter}

X.Org X Server 1.19.2
release date: 2017-03-02
X Protocol Version 11, Revision 0
… Linux 4.19.4-antix2-amd64-smp x86_64 antiX
…
…
…
… (EE) (EE) Server terminated for help (1) . Closinglog file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

4 – Reiniciei o computador novamente e selecionei a segunda opção: Safe Video Mode, as imagens falham, a resposta é lenta, não tão lenta como no antiX 19.2.

Obs.: Nossa! Como o menu e a barra de tarefas do antiX-17.4.1 são muito bonitos! Eu achei mais bonito o menu e a barra de tarefas mais simples do antiX-17.4.1 do que as do antiX 19.2. É mais claro e mais fácil para a leitura. Outro detalhe é que o antiX-17.4.1 consome cerca de 114MB de memória RAM, o processamento estava em cerca de 54%.

Eu consegui concluir a instalação com sucesso, após o computador reiniciar com o boot configurado para iniciar via HD, o antiX-17.4.1 foi iniciado com extrema dificuldades nas respostas do vídeo, semelhante ao Safe Video Mode via pendrive.

Ao que parece o antiX-17.4.1 também não tem suporte para esta placa de vídeo, mas se comportou melhor que o antiX 19.2, contudo ainda não é viável utilizar este computador com antiX até que se resolva o controlador de vídeo, o que seria lamentável não usar o antiX devido ao vídeo.

Caso alguém tenha mais alguma ideia será muito bem vinda.

De qualquer forma, agradeço a todos que colaboraram com suas considerações e ensinamentos, certamente esta postagem será de grande utilidade para outros colegas.

marcelocripe

Texto original em idioma português do Brasil, traduzido para o inglês por Google tradutor.

[Member Xecure]

For multibooting I have used a windows tool named easy2boot. In their website the have a list of all the distros that work and how to set them up. It is very complicated.
For antiX, the way I started testing it before giving it the full USB was using E2B. I used the tool that lets me create an fat32 image (of 4GB) from the iso and I sued it for persistence until I learnt how things worked. With a whole USB I was able to do many more things that the 4GB limit.

It still works for me on my USB HDD, though I only use it when I don’t want to burn another USB stick. It has worked for me with windows, and all linux distros I tested. The only limitation is that I need windows to use it.
When building the fat32 image files (that later become fat32 partitions), the program always asks to select a syslinux version and syslinux 6 always works for me, so your issues can only be related to multibootusb.

I recently read that YUMi finally has support for UEFI booting, so you could see if you can set persistence with it if you cannot get MultBootUSB to work.

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

I would like to be able to store, boot and run copies of my .iso files, with persistence files for them on a USB mounted Flashdrive, SSD, or Harddrive. I would like for the machine, when booted from the USB, to boot up to a menu, and be able to select or tweak boot codes and boot any of iso’s. This would mostly be for Linux distros’s as I avoid try to avoid using Windows. I was looking for a program to make this easy to do and manage.

I found multibootusb, which looks to be intended to do this for both Windows and Linux. It’s supposed to work for Debian and Ubuntu, and might work for others, and also is supposed to support persistence. I was able to download and install it’s 9.2.0 version from the .deb and ran it under root, and once I ran it correctly and installed a couple of distros, it started to boot up, and the menu came up Ok, but wasn’t able to boot either distro, antiX19.2 net, or pclinuxos kde. I then tried it with DWMX1.0 and Lbuntu19.10. DWMX offered persistence, but wouldn’t boot. Lbuntu offered persistence and actually works!

I found a post saying MX19 works, but didn’t try that.

I found a post saying they were having problems with antiX17, but got it working with antiX17.4

I found a post saying that the 9.3.0 version from git had a lot of bugs fixed, and I got it downloaded, but not installed.

I found a post saying that the version of syslinux included wasn’t up to date (I think it’s 6.03, vs 6.04 in antiX currently)

Maybe someone more technical could look the source to figure out why? The program looks to be done in python3.

http://multibootusb.org

The other programs I found to do this lacked open source, or wanted me to run it from wine, etc.

Debian also worked sometimes. Someone started a page with a list, but it looks like whoever was controlling the git site maintaining it hasn’t been updating anything at all for 8 months now, and was active 2 years ago. There are 14 contributors and 150 forks.

https://github.com/mbusb/multibootusb/wiki/Known-To-Be-Running-Images-List

I will update this post as I get more info and links initially

PS: instead of installing the 9.2.0 .deb package, I tried installing 9.3.0 from git. The install went fine, but I had less success, now getting install_syslinux() failed. I tried it with both the syslinux6 that came from git as well as copying/renaming /usr/bin/syslinux as suggested in a post on git and both led to the same result. I aso noticed that antiX17.4 persistence was not recognized.

Maybe that’s why 9.3.0 has never been released. It looks like the 9.3.0 bug fixes were intended mostly for windows.

PSS: I’ve come to the conclusion that syslinux is not intended for people to use directly. I thought about using the 9.2.0 version to install the iso’s, because it did at least create the menu for the iso’s to boot from, but didn’t find a reasonable way to even get syslinux installed correctly on the USB to be able to try that.

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

[Member PPC]

Brian Masinick wrote:

Is there anyone who agrees, and is there anyone who is able to create a prototype of an antiX Enlightenment desktop from which a potential future effort could be built on?

My only non essential system is my old MX 18,3 – I installed Enlightenment on it and wow… I had some experience with the Moksha Enlightenment derived desktop but most users, used to antiX’s desktops, will not believe their eyes when they see how much functionality Enlightenment packs into a desktop. Let’s just say this: all the good stuff most computer users see in a Windows 10 desktop is available, out of the box in Enlightenment- desktop icons, a bar with a menu, that allow to easily dock quick-launcher, mini previews of running apps, composition (with terminal transparency out of the box, etc), all running in almost the same RAM (some 260 Mb of idle RAM in MX 18.3 case)… If I have the time, over the week end, I can try to do the same in a live antiX and remaster that, if successful. Folks, it’s a bit different from our ordinary desktops, but at the same time to familiar and feature rich. Right clicking an empty space on the desktop calls up the menu, right click calls any application marked as favorite (I added the terminal only)- that does make some sense…
The only con is that the default theme is too dark, even for me that like dark themes and, mainly: the edge of the screen automatically moves the user to the next/previous virtual desktop, which can be quite annoying…

Edit: I had not time, over the week-end to create an iso, but I did manage to install Enlightenment in antiX 19.X. 64 bits… and it’s quite impressive. Iddle RAM, with activated composition, desktop icons, conky and running “free -h” on roxterm was 248Mb (but without a desktop background image)! Quite impressive, but way less difference to what I expected, considering the idle RAM was almost the same on MX…)

Edit2: Hum, after reboot, Ram usage was 206Mb. After setting desktop background and Everything to show on the (i)bar, 216 Mb (with the nvidea proprietary running- so a bit, less than 200Mb without that, I guess).

Comparison: Without desktop icons, my antiX IcewM desktop idles at 176Mb of RAM, so all the bells and whistles cost some 40Mb of RAM. I did not deactivate the composition or desktop icons- hum… I don’t quite have a grip on the desktop.

Pros: The desktop looks very impressive. The best praise I can give it is that it has all the capabilities that IceWM has, plus some that windows 10 desktop has (like showing previews of running apps, and allowing an easy way to dock running icons to the bar). The “everything” launch looks like a cross of our app launcher and drill search app, with plug-ins that make it also work like a calculator, etc. Very nice app! ( I use drill in IceWM to get most of those functions, and skippy-xd to get previews of running apps- so I have about the same functionality in both desktops).
the virtual desktop previewer really shows tiny versions of each desktop! Almost cute…

Cons: not very intuitive at all to configure!
The bar may seem a bit confusing because when you launch apps, you get both an icon (that shows the preview of the app, allows to launch another instance of the same app, and to “dock” the icon to the bar- very nice) but also a taskbar entry with the name of the app – that allows to maximize,minimize and close the application… I don’t understand why not also have those window actions easily available from the ibar (the part that shows only the icons).
The edge of the screen is automatically configured to jump to the next virtual desktop (I don’t use virtual desktops myself, so this is very annoying)

Bug(?): at first run, the log off, restart, etc buttons did not work

Suggestion: once again, I find that using this as the antiX desktop version anti is considering would be very nice- not that mainstream, but very low specs. The system can be configured to have a normal looking bar that looks almost like the default IceWM one, with loads more features, desktop icons and our default desktop background, all that making it much more appealing to the “normal” non geeky user (except for the menu, that is almost like our normal menus) the look and feel of this desktop is almost “Windows 10” like… I’m not sure if that’s good or bad- I’m used to the more spartan IcewM myself- but I can spare 40 Mb more of RAM on my 3 Gig of RAM computer, if I feel like it…

P.

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

[Moderator Brian Masinick]

@AA BB: I am TOTALLY in agreement with you. I have been a longtime Debian Linux user (dating back to 2001). Before that, I used Mandrake and Red Hat (as far back as 1998), and Slackware, (all the way back to November 1995, when I purchased my first home computer). Prior to that, I did use personal computers and workstations, occasionally bringing them home, and I have been using computers at school and work since 1973 (when I had a very nice introduction to computers through a high school Algebra-Trigonometry class – the teacher took us on a field trip to the General Motors Research Laboratories at the Tech. Center in Warren, Michigan, and I instantly figured out what technology center I wanted to work in – computers and software – which I DID from June 1979 until January 2018, a nice career.

As far as systems go, when the first test releases of MEPIS came out in 2003, I was there, and I followed Simply MEPIS and the other releases too, continuing with MX Linux once Warren Woodford abandoned MEPIS for some great jobs (I think it was working with legal and intellectual property, very good professions, no wonder he moved on!) Paul, a.k.a. anticapitalista, appeared about two years after the early MEPIS came around – I’m not sure if our history is out there or not, but anti can confirm the exact time and date. Anyway, my hardware was always a bit older than the latest and greatest stuff. The desktop I had back then, a Dell Dimension 4100, was a good model when new, and it provided me with a very usable lifespan very close to a decade long – ending up being STOLEN just before I was moving – the thieves were local and had a pretty good idea when I was coming and going.

So Debian, MEPIS, MX Linux, and antiX have been a big part of my computing. I used them next with a Gateway 2000 and a Lenovo 3000, both laptops. These were quite a few years old when I finally disposed of them. Like the Dell Dimension, all of them still worked well, but antiX was among the few that still supported their aging 32-bit hardware.

Now I have a nicely aging Dell Inspiron 5558, 64-bit, 8 GB memory, 8 TB disk drive, 4-CPU Intel processors and again it runs antiX and MX Linux, along with Debian very well. As before, the more the unit ages, the more I stick with minimal configurations of one of these three distributions. Note that I definitely support this community – it’s my favorite of all, but I am able to run the SystemD stuff on Debian too, so I exercise BOTH of these choices from time to time, but I spend the majority of my time in either MX Linux or one of TWO instances of antiX (a Full Edition and a runit edition). Yesterday I spent the majority of my time on MX. Today I spent some time with a distro I reinstalled after a few years away, Mageia 7 (former Mandrake/Mandriva derivative). I still have a “soft spot” for it because it was one of the early “friendly” distributions, but I can also tell you that the quality and the repo download speeds can’t begin to compare to what we have – it’s on my TODO list to find FASTER repos, otherwise Mageia won’t last very long for me! Once I killed the software changes, I rebooted to my two antiX instances and I’ve been on them since – using antiX 19.2.1 “runit” now.

Why do I like it? 1) Debian-based packaging; this packaging style has been my favorite since 2001. 2) Tools: both MX Linux and antiX have some of the best tools for installing, configuring, and maintaining systems. They are both effective and efficient, a GREAT combination! 3) Flexibility: not only is this family of software effective to use and maintain, it is EASY to modify appearance, window managers, desktop environments, applications and utilities. 4) Speed: I’ve seen some comparisons on the Phoronix site over the years comparing various distributions. Though it has been a while since I checked them out, I’ve seen Debian-derived systems, even including Ubuntu, beating out the supposedly FAST Arch Linux in certain workloads. I suspect, based on my own informal usage (and some empirical tests (that means “unofficial timings” and visual feel of response) that antiX easily beats Arch Linux, plus it is FAR easier to install. Arch Linux is actually a COOL project, so I don’t want to discourage anyone who is interested in it or totally loves it; all I am saying is that in my experience, to end up with a system that didn’t perform noticeably faster than the other systems I used, yet took considerable time to build unless you grabbed someone’s pre-configured derivative, it just didn’t match my interests – though I WILL say that both Arch Linux and Linux From Scratch are VERY COOL projects if your aim is deep learning of Linux skills. (I learn PLENTY using what we have here, just the same).

Oh yeah, while mentioning learning, I want to thank macondo again for some of his recent sharing, and after this “discourse” I am going to try out a few of the latest ideas recently shared by macondo. Who says that learning stops at a certain age (or after retirement)? Not here; antiX is still a great hobby for me and I still tweak this or that from time to time.

Enjoy! Plenty to learn, try, and use here! 🙂

• This reply was modified 2 years, 10 months ago by Brian Masinick.

--
Brian Masinick

[Member Xecure]

SpaceFM is a better file manager for these kind of things.

Anyway, I found the issue. Luckely I also have a 19.1 base iso around, so I found the issue.

When dist-upgrading, I found that apt-antix, after upgrading, wanted the user to replace the antix.list If a user says no, the result is that the buster entry for the antix repo stays as
.../antix/buster buster main nonfree
intead of being replaced with
.../antix/buster buster main nonfree nosystemd
This means that systemd programs are NOT being blacklisted if the user doesn’t accept the change.
I needed to select No to be able to reproduce the error.

I have just recovered from all the problem.

Here is the solution in case you want to try to fix it.

1. restore apt list
sudo nano /etc/apt/sources.list.d/antix.list
Change the second line (starting with deb). It looks like:
deb http://........./antix/buster buster main nonfree
go to the end of the line and add nosystemd It should look like this:
deb http://........./antix/buster buster main nonfree nosystemd
Control+X to exit (it will ask you to save, say Y and then Enter)

2. Update the package list
sudo apt update

3. Install xorg
sudo apt install xorg

4. Install updates
sudo apt dist-upgrade

reboot.

Edit: Hopefuly this fixes it for you.
Then, after, you can uninstall system-config-printer-udev if you want (it won’t work anyway).

• This reply was modified 2 years, 10 months ago by Xecure.

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

[Moderator BobC]

So far I have 10 machines that the Intel won’t boot on, and 4 that it should. (I didn’t try either of those, yet, and not sure its worth trying).

Thanks for telling me a bout the CPU limitation.

My hope would be that a new antiX DE would be a separate ISO, based on the same foundation as much as possible (ie same up to Xorg if possible), as the current antiX Full and Base ISO’s, or at least based on the same Core system.

To be honest, for me, I don’t plan to run a DE. I’m happy with the WM setup and adding the packages I want.

[Member Xecure]

I think the option you need to select is f_static_root

From https://antixlinux.com/antix-19-isos-available/
p_static_root
Enable static root persistence. Note “persist_static” now requires
both root and home persistence to be enabled. In the past, home
persistence was optional.

f_static_root
Same as above with frugal enabled as well so it means do a
frugal install with static root persistence.
If you selected this, make sure you also changed the boot parameter.

Sorry. Didn’t realize it was antiX 17. Then this is not related. You must have selected frugal_static, so this should work for you.

I will see if I can find something about LIBPAM can only be related to am-elogind-compat. Maybe it updated to libpam-elogind? but I don’t understand what this does or how to fix itknow how to fix this.
Maybe anticapitalista can explain.

• This reply was modified 2 years, 10 months ago by Xecure.
• This reply was modified 2 years, 10 months ago by Xecure.
• This reply was modified 2 years, 10 months ago by Xecure.

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

[Anonymous]

Xecure wrote:

Also, for next frugal install, instead of failsafe try removing the splash boot option and see if it will boot that way.

I tried that and tried safe video mode also.I never had this issue before. All antiX iso’s boot normal.I have tried all 19.2 base,core,sid,runit variations.This particular one (19.2-runit-sid_x64-core) fails to boot normally.

[Member PPC]

Hum, you probably are booting a relatively recent computer that uses UEFI to manage boot. In that case the F keys menu is not used. You’ll probably see, in the antiX boot menu something like “advanced settings”? try clicking there are look for something in the menu that refers to Persistence (and then saving changes).

EDIT:
Check out this instructions:
https://antixlinux.com/forum-archive/solved-want-to-boot-antix-15-v_x64-full-iso-in-uef-t5709.html

P.

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