hello,

for starting an application available on x86 i386; pyilper, using Qt, available in anaconda too; and lifutils available as debian 32bits packages, and making it running on a raspberry pi4, I was thinking about starting antix on my pi4 (antix looks smaller than debian lxde etc.). These applications pyilper and lifutils dont have an ARM version.

Any advice is welcome...

a) what iso with graphic environment to use "antiX-21_386-core.iso" or the base version? (antix is not my daily distro for now)

b) what command parameters in qemu should be used for an antix desktop to run (lightweight; antix will only be used as a nest for pyilper and liftutils; no need for any other applications except the basic functionality of pyilper and liftutils which are communicating with serial drivers and exchanging data with a file in the PC).

If my project is weird and/or a nonsense, let me know (ok if it take 5min to boot; at the end, the pi4 will be used as storage device for an HP41 or HP71 and/or screen extension).

Another idea would be to start Win98 or XP via qemu on the pi4.. but Windows is not my preferred path for now. Example given there https://www.youtube.com/watch?v=2NI7...nnel=RickMakes

Base at least comes with fluxbox and a lot of preinstalled libs.. Core iso. If you prefer dwm. You will have to install it.

Might wanna go with cli installer option also. I am a friend of Brian so I figure his blog should cover stuff.

https://brianmasinick.blogspot.com/2...ntix-core.html

runwiththedolphin on youtube has some videos also. Sorry. I don't handle qemu.

Before I went into my raspberry PI4, I tested in my Debian11 64bits and made following (better/quicker hardware; I will transfer the solution to the pi4 later)

qemu-img create -f qcow2 hpdisk.img 10G
qemu-system-i386 -boot d -cdrom antix.iso -m 2047 -hda hpdisk.img

looks good. it starts (antix.iso = the 386 core version).
But the cli-installer is quite hardcore for me since I have not used it since years. I will try now the 386 full.
A graphical installer is on it: good stuff.

Update 1: a qemu harddrive with 7GB root and 3GB home was not enough (full iso version). Not enough room on the home for anaconda3 install on it. lets install the antix base and 4.2GB root & 4.8GB home. Looks good for now. See the picture.

Update2: antix32bits_base (after install in the qemu environment), starts with

Attached Thumbnails

 

A lot of folks run Base since it comes with Fluxbox only and they can build from there to suit.

Good choice.

Here is a archived thread covering basic differences between Full and Base editions.
https://antixlinux.com/forum-archive...ion-t2168.html

Might wanna try a command I used in MX fluxbox to check on what I had installed so far included with initial installed packages during install process . Can't take credit for it. Borrowed from a thread that a member posted in, in this forum.

Here is hoping base iso has the libs and such to make the above command work
https://pastebin.com/5pzSQuFP

Now the question would be how to pass usb serial ports to qemu (where antix is started)

lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 10000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 2: Dev 2, If 4, Class=Vendor Specific Class, Driver=, 480M
|__ Port 2: Dev 2, If 2, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 2: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 2: Dev 2, If 5, Class=Human Interface Device, Driver=usbhid, 480M
|__ Port 2: Dev 2, If 3, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 2: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 4: Dev 7, If 3, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 4: Dev 7, If 1, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 7, If 2, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 7, If 0, Class=Audio, Driver=snd-usb-audio, 12M
|__ Port 7: Dev 3, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 12M
|__ Port 8: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 8: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 9: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 9: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 14: Dev 6, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 14: Dev 6, If 1, Class=Wireless, Driver=btusb, 12M

UPDATE: DONE. WORKS.

This helped a lot. https://sysadminde.com/questions/872...n-the-guest-os

Now, since antix 32 bits is working in qemu on a 64bits Debian PC (with serial ports activ), lets come back to the previous vision: making antix working on raspberry pi4 via qemu.

I am still hesitating in using the antix base as the 32 bit OS in qemu in a raspberry pi4.
The pi4 boots with raspbian and a 32GB SD.

1. I must have a look if any simulated RAM or qemu window can be simulated into a separated USB storage (I would not like to kill too quick my SD card).

2. I should perhaps give a try again to antix core:
- minimum desktop environment
- automatic login
- serial usb only
- ftp (use of midnight-commander)
- Qt5 application installed via anaconda3
- file manager
- nano editor
- no cpu monitoring etc. because qemu would be nbested in a pi4 rasbian system lxde

Any advice where to find a cli-interface command list for installing (from antix core)
: /dev/sda1 ext4 / 2GB (antix minimum system installed from "core")
: /dev/sbb1 linux-swap 1GB (separated USB drive connected at the pi4)
: /dev/sda2 ext4 /home 5GB (home for storing the anaconda3 Qt application and few files created by it)
are welcome.

Might help or not. Brian is a buddy of mine. Yeah , I know it's old. Brian and I are old also.

https://brianmasinick.blogspot.com/2...ntix-core.html

https://antixlinux.com/forum-archive...sys-t3361.html

https://www.youtube.com/watch?v=njj6geeCOds

Good Luck.

antix32bits starts in qemu on a pi4 (raspbian on it).
I have used the following command
The /media/usb1/ is following https://www.amazon.de/Philips-Black-.../dp/B07YCLM8XT on the usb3 port of the raspberry PI, = USB stick formatted with ext4 in a single partition.
But thats slow. example, in a terminal, the "apt-get update" show at the end "17.7MB in 18min29s".

a) Perhaps I should use another hardware? (looks like 40MB/s read and 18MB/s write is not enough).
Should I give a try to an SSD for approx 40Eur? see examples there https://jamesachambers.com/raspberry...-flash-drives/
I could connect an SSD into the USB3 port instead of that lousy stick.

b) Perhaps is ext4 not the best for reading/writing speed? another format should be used?

c) Using any parameter in qemu for acceleration? the cpu seems to be 100% busy in antix (according the conky cpu monitoring) but the raspbian monitoring show a 30% busy CPU.

Any recommendation is welcome (before I spend more money).

pyilper is written in python, it can run on RPi without VM. lifutils is binary, but I think it can be compiled on arm.
So if possible I wouldn't run qemu at all.
Regarding speed you may want to buy a fast pendrive (like Corsair Voyager GTX)

>Stop here. box86 installed on raspbian was the best alternative to start x86 codes (wine then ilper etc.).