Forum › Forums › antiX-development › Development › 32 bit antiX-25.a2-full for testers
- This topic has 89 replies, 14 voices, and was last updated Nov 1-2:54 pm by anticapitalista.
-
AuthorPosts
-
September 12, 2025 at 10:17 am #185395
christopheModeratorAfter installing & living with this alpha for a while, the only thing I find that isn’t working for me is lxappearance. The theme isn’t changed in some of the windows, like control centre.
But this is running like a 1.0 release otherwise. Thank you for all your work.antiX on everything, since 2017
September 12, 2025 at 11:59 am #185406
Brian MasinickModeratorThank you, @masinick. There was a mistake in the way I edited the antix.list file. I corrected it and updated without any errors. I edited my previous post to show the correction. But I have a question. In the Bookworm repo, apart from main, nonfree & nosystemd, there is also a “dev” section, which doesn’t exist in the Trixie repo. Should I add this “dev” section or should I let the Trixie repo as it is?
I’d leave it alone for now.
If you want to “experiment”, copy the original to your home directory; you can copy it back if you don’t like the result; I do this from time to time. I helps me “keep track” of my experiments without permanently disrupting the regular workflow.
--
Brian Masinick
Alternate "Search B":
This search pageSeptember 12, 2025 at 12:05 pm #185409andfree
MemberI edited again my #185377 post. I corrected the initial repo and updated without any problems.
I’d leave it alone for now.
If you want to “experiment”, copy the original to your home directory; you can copy it back if you don’t like the result; I do this from time to time. I helps me “keep track” of my experiments without permanently disrupting the regular workflow.
Thanks, again.
antiX utilities for processing PDF files (posted by ChPol)
September 12, 2025 at 12:13 pm #185410
Brian MasinickModerator@andfree glad you got it working. Just remember that it’s OK to alter configurations to experiment; but when you do so, it’s always smart to save both the originals and the changes, so that 1) you can try out other things and 2) you can get back to the original, and also so that you have copies of what you did in the event that some kind of tracking is needed to figure out what all took place.
For me, I liberally use my own directories to store stuff I experiment with. There’s no “magic” to this; you can save to any safe place, online or saved on removable media; it’s just a good idea to somehow be able to retrace your steps; you never know when it may be important to do so.
These are just tips too; there is usually more than one way to get things done; these are merely practical ideas that work for me and are things likely to be helpful when testing.
--
Brian Masinick
Alternate "Search B":
This search pageSeptember 12, 2025 at 5:41 pm #185430Anonymous
I’m getting an error one on of my default repos…. it used to work… http://ftp.cc.uoc.gr/linux/mx
I’d copy and paste exact text but it’s in a qemu VM and that’s not working, plus for some reason I can’t even ssh into it, will try to figure that out later… but screenshot attached.
September 12, 2025 at 11:43 pm #185433andfree
MemberI’m getting an error one on of my default repos…. it used to work… http://ftp.cc.uoc.gr/linux/mx
As I wrote in my #185377 post, you have to edit your antix.list file:
$ sudo geany /etc/apt/sources.list.d/antix.listDoes your repo (the uncommented line) appear exactly like this?
deb [signed-by=/etc/apt/keyrings/antix-archive-keyring.gpg] http://ftp.cc.uoc.gr/mirrors/linux/mx/trixie trixie main nonfree nosystemdIf yes, replace that line with the corrected one:
deb [signed-by=/etc/apt/keyrings/antix-archive-keyring.gpg] http://ftp.cc.uoc.gr/mirrors/linux/mx/antix/trixie/ trixie main nonfree nosystemdI just don’t know if we should add a “dev” section at the end. Till we have an answer, I’ll test it in a frugal.
My conclusion is that http://ftp.cc.uoc.gr updated the repos (and maybe made changes to their structure, I’m not sure). It was red for days in Mirmon, but now it’s green. On the other hand, http://ftp.ntua.gr is now red and you can’t update if you turn your repo to it, as I did for a while.
- This reply was modified 1 year ago by andfree.
antiX utilities for processing PDF files (posted by ChPol)
September 13, 2025 at 2:10 am #185435andfree
MemberBut the issue with Repo Manager still remains.
Not anymore. Today, after update, I can change repos via Repo Manager without problem.
antiX utilities for processing PDF files (posted by ChPol)
October 1, 2025 at 2:08 am #186490andfree
MemberIn the Bookworm repo, apart from main, nonfree & nosystemd, there is also a “dev” section, which doesn’t exist in the Trixie repo. Should I add this “dev” section or should I let the Trixie repo as it is?
After all, there is an answer that the “dev” section shouldn’t be there in the Bookworm repo, too.
- This reply was modified 12 months ago by andfree.
antiX utilities for processing PDF files (posted by ChPol)
October 8, 2025 at 4:43 pm #187114Robin
MemberSorry for being that late with writing here after downloading the ISO initially long ago already. Reason is: I was not able to create a Live USB stick which is accepted by my 32 bit testing device, which has no internal HDD and no CD/DVD drive, so I can only boot from USB.
The USB stick is detected immediately as Boot device by the BIOS by its proper name. But when I select it, the screen goes black after a second or two and shows merely the two words “Boot failure” in the upper left corner, not doing anything else anymore.
I tried different USB stick types, and also different expert settings in the antiX USB maker tool:
1st try. My personal default: GPT, pmbr_boot, additional data partition. vfat for boot partition, ext4 for antiX partition.
2nd try. antiX default: MBR, use 100% of the devivce. vfat for boot partition, ext4 for antix partition.
3rd try. antiX default + EFI partition formatted with ntfs instead of vfatnone of these do work in four different USB sticks of different manufacturers, which are all recognised initially as a valid boot device by the BIOS, but all show the described error.
Now I wanted to change the boot partition format to something more compatible, e.g. fat32 or fat, and found that this is not possible in antiX Live USB Maker: I merely can select
vfat exfat ext4 ntfsfrom the pulldown, neither fat nor non-vfat fat32. This is the partition which is marked with the “boot” flag by the live USB maker, so I guess this is what the BIOS actually accesses. Maybe I’m wrong here, please correct my.
But I believe the BIOS would expect non-vfat, either fat32 or fat format for the boot partition. Is it possible at all to write the stick this way with antiX USB Maker, or wouldn’t that affect the boot at all, I mean, is the additional efi partition accessed for boot from a legacy bios at all?
Next I’ll try to dd the ISO to one of the USB sticks, but then I can’t apply the advanced LIVE features remaster and persistence, which I’d really need due to the lack of an internal HDD.
Ideas? Is it actually possible the vfat format in the antiX-UEFI partition blocks the sticks from booting on a BIOS expecting non-vfat ?
—————————————————
=============================================================================== Starte live-usb-maker 2.41.19-2302 =============================================================================== live-usb-maker 2.41.19-2302 Live Mediengerät /dev/sdb gefunden Gerät /dev/sdc (58,6G Generic Flash Disk) wird als Ziel verwendet Datei /media/sda4/Arbeitsordner/antiX/antiX 25.a2-testing/antiX-25.a2-runit_386-full.iso wird als Quelle verwendet Distro: antiX-25.a2-runit_386-full alpha2 14 August 2025 Grub Konfiguration 2.0 gefunden gesamt benutzt unbelegt Gesamtes Laufwerk 58.6 GiB 58.6 GiB 0 MiB Datenpartition 29.3 GiB 0 MiB 29.3 GiB Hauptpartition 29.2 GiB 2.00 GiB 27.2 GiB UEFI Partition 50 MiB 32 MiB 18 MiB Erzeugung einer führenden ext4 Datenpartition Bereit live-usb auf Gerät sdc ... mit Kopiere Datei /media/sda4/Arbeitsordner/antiX/antiX 25.a2-testing/antiX-25.a2-runit_386-full.iso zu erstellen live-usb-maker 2.41.19-2302: partition-clear >> partition-clear > dd status=none if=/dev/zero of=/dev/sdc bs=512 count=34 > dd status=none if=/dev/zero of=/dev/sdc bs=512 count=34 seek=64 > dd status=none conv=notrunc if=/dev/zero of=/dev/sdc bs=512 count=34 seek=122879966 > partprobe /dev/sdc live-usb-maker 2.41.19-2302: partition-make >> partition-make gpt Partitionierung wird verwendet > parted --script --align optimal /dev/sdc unit MiB mklabel gpt > dd status=none if=/dev/zero of=/dev/sdc seek=1024 bs=1K count=128 > parted --script --align optimal /dev/sdc unit MiB mkpart primary 1 30000 > dd status=none if=/dev/zero of=/dev/sdc seek=30720000 bs=1K count=128 > parted --script --align optimal /dev/sdc unit MiB mkpart primary 30000 59948 > parted --script --align optimal /dev/sdc unit MiB set 2 legacy_boot on > dd status=none if=/dev/zero of=/dev/sdc seek=61386752 bs=1K count=128 > parted --script --align optimal /dev/sdc unit MiB mkpart primary 59948 59997 > parted --script --align optimal /dev/sdc unit MiB set 3 esp on > parted --script --align optimal /dev/sdc unit MiB disk_set pmbr_boot on > partprobe /dev/sdc live-usb-maker 2.41.19-2302: makefs-data >> makefs-data > wait_for_file /dev/sdc1 live-usb-maker 2.41.19-2302: makefs-data >> makefs-data Erzeuge ext4 Dateisystem > mkfs.ext4 -L USB-DATA /dev/sdc1 mke2fs 1.47.0 (5-Feb-2023) Ein Dateisystem mit 7679744 (4k) Blöcken und 1921360 Inodes wird erzeugt. UUID des Dateisystems: f87297f3-037e-4cce-8092-10b466f69801 Superblock-Sicherungskopien gespeichert in den Blöcken: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000 beim Anfordern von Speicher für die Gruppentabellen: 0/235 erledigt Inode-Tabellen werden geschrieben: 0/235 erledigt Das Journal (32768 Blöcke) wird angelegt: erledigt Die Superblöcke und die Informationen über die Dateisystemnutzung werden geschrieben: 0/235 erledigt > partprobe /dev/sdc1 > mount /dev/sdc1 ./data live-usb-maker 2.41.19-2302: set-ownership >> set-ownership Setting data partition ownership to Robin:users > setfacl -m u::rwx,g::rwx,o::r-x ./data/. > setfacl -d -m u::rwx,g::rwx,o::r-x ./data/. > chown Robin:users ./data/. > chmod g+rwx ./data/. > umount ./data > wait_for_file /dev/sdc2 live-usb-maker 2.41.19-2302: makefs-bios >> makefs-bios > mkfs.ext4 -O ^64bit -m0 -i16384 -J size=32 /dev/sdc2 mke2fs 1.47.0 (5-Feb-2023) Die Unterstützung für 64-bittige Dateisysteme wurde nicht aktiviert. Die längeren Felder, die diese Eigenschaft benötigt erlauben die Erstellung der Prüfsumme in voller Stärke. Geben Sie „-O 64bit” an, um dies zu korrigieren. Ein Dateisystem mit 7666688 (4k) Blöcken und 1916928 Inodes wird erzeugt. UUID des Dateisystems: f3ec9e78-5060-4ec0-9924-584086b926ff Superblock-Sicherungskopien gespeichert in den Blöcken: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000 beim Anfordern von Speicher für die Gruppentabellen: 0/234 erledigt Inode-Tabellen werden geschrieben: 0/234 1/234 erledigt Das Journal (8192 Blöcke) wird angelegt: erledigt Die Superblöcke und die Informationen über die Dateisystemnutzung werden geschrieben: 0/234 erledigt > tune2fs -L antiX-Live-usb /dev/sdc2 tune2fs 1.47.0 (5-Feb-2023) > wait_for_file /dev/sdc3 live-usb-maker 2.41.19-2302: makefs-uefi >> makefs-uefi > mkfs.vfat -F 32 -n ANTIX-UEFI /dev/sdc3 mkfs.fat 4.2 (2021-01-31) > partprobe /dev/sdc > wait_for_file /dev/sdc2 > mkdir -p ./main > mount -t ext4 /dev/sdc2 ./main > wait_for_file /dev/sdc3 > mkdir -p ./uefi > mount -t vfat /dev/sdc3 ./uefi > wait_for_file /dev/sdc1 > mkdir -p ./data > mount -t ext4 /dev/sdc1 ./data Dateisystem Typ Größe Benutzt Verf. Verw% Eingehängt auf /dev/sdc1 ext4 29G 24K 28G 1% data /dev/sdc2 ext4 29G 24K 29G 1% main /dev/sdc3 vfat 49M 512 49M 1% uefi live-usb-maker 2.41.19-2302: copy-uefi >> copy-uefi Kopiere von iso auf Partition uefi Dateien [Ee][Ff][Ii] version > cp --no-dereference --preserve=mode,links --recursive ./iso/EFI ./uefi/. > cp --no-dereference --preserve=mode,links --recursive ./iso/version ./uefi/. Dell uefi memtest Bug beheben > cp ./uefi/EFI/BOOT/grubx64.efi ./uefi/EFI/BOOT/fallback.efi live-usb-maker 2.41.19-2302: copy-main >> copy-main > rm -rf ./main/boot.orig Kopiere von iso auf Partition main copy /antiX/vmlinuz > cpio -pdm --quiet ./main/ > e4defrag -v ./antiX/vmlinuz e4defrag 1.47.0 (5-Feb-2023) ext4 defragmentation for ./antiX/vmlinuz [1/1][79;0H[K[1/1]./antiX/vmlinuz: 0%[79;0H[K[1/1]./antiX/vmlinuz: 100% extents: 2 -> 1 [ OK ] Success: [1/1] copy /antiX/initrd.gz > cpio -pdm --quiet ./main/ > e4defrag -v ./antiX/initrd.gz e4defrag 1.47.0 (5-Feb-2023) ext4 defragmentation for ./antiX/initrd.gz [1/1][79;0H[K[1/1]./antiX/initrd.gz: 0%[79;0H[K[1/1]./antiX/initrd.gz: 100% extents: 2 -> 1 [ OK ] Success: [1/1] copy remaining files ... > cpio -pdm --quiet ./main/ > write_file ./main/made-by-live-usb-maker created: Fr 15. Aug 08:59:44 CEST 2025 program: live-usb-maker version: 2.41.19-2302 (Sat, 25 Feb 2023 12:45:10 -0500) > dd status=none if=/dev/urandom of=./main/antiX/random-seed bs=512 count=1 > chmod 600 ./main/antiX/random-seed > rm -rf ./main/.disk live-usb-maker 2.41.19-2302: check-usb-md5 >> check-usb-md5 Überprüfung von md5 für initrd.gz > md5sum -c initrd.gz.md5 initrd.gz: OK Überprüfung von md5 für linuxfs > md5sum -c linuxfs.md5 linuxfs: OK Überprüfung von md5 für vmlinuz > md5sum -c vmlinuz.md5 vmlinuz: OK live-usb-maker 2.41.19-2302: uuids >> uuids Benutze antiX/MX Grub Config 2.0 > mkdir -p ./uefi/boot/grub > cp ./main/boot/grub/config/efi-grub.cfg ./uefi/boot/grub/grub.cfg > touch ./main/boot/grub/config/did-efi-grub > sed -i /^\s*#/! s/%UUID%/f3ec9e78-5060-4ec0-9924-584086b926ff/ ./uefi/boot/grub/grub.cfg > rm -f ./main/boot/grub/config/*.id > touch ./main/boot/grub/config/a36610cf2c1e35db02cc15377e3713b2.id > sed -i /^\s*#/! s|%ID_FILE%|/boot/grub/config/a36610cf2c1e35db02cc15377e3713b2.id| ./uefi/boot/grub/grub.cfg > mkdir -p ./main/antiX > write_file ./main/antiX/data-uuid f87297f3-037e-4cce-8092-10b466f69801 live-usb-maker 2.41.19-2302: install >> Installieren extlinux version 6.04 > dd status=none bs=440 conv=notrunc count=1 if=/usr/lib/syslinux/mbr/gptmbr.bin of=/dev/sdc > rm -f ./main/boot/syslinux/chain.c32 > rm -f ./main/boot/syslinux/gfxboot.c32 > rm -f ./main/boot/syslinux/ldlinux.c32 > rm -f ./main/boot/syslinux/libcom32.c32 > rm -f ./main/boot/syslinux/libmenu.c32 > rm -f ./main/boot/syslinux/libutil.c32 > rm -f ./main/boot/syslinux/menu.c32 > rm -f ./main/boot/syslinux/syslinux.bin > rm -f ./main/boot/syslinux/version > cp /usr/lib/syslinux/modules/bios/chain.c32 ./main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/gfxboot.c32 ./main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/vesamenu.c32 ./main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/ldlinux.c32 ./main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/libcom32.c32 ./main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/libmenu.c32 ./main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/libutil.c32 ./main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/linux.c32 ./main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/menu.c32 ./main/boot/syslinux/ > write_file ./main/boot/syslinux/version 6.04 > extlinux -i ./main/boot/syslinux /run/live-usb-maker/main/boot/syslinux is device /dev/sdc2 Dateisystem Typ Größe Benutzt Verf. Verw% Eingehängt auf /dev/sdc1 ext4 29G 24K 28G 1% data /dev/sdc2 ext4 29G 2,0G 27G 7% main /dev/sdc3 vfat 49M 13M 36M 26% uefi >> Abgeschlossen live-usb-maker took 18 minutes and 39 seconds.=============================================================================== Starte live-usb-maker 2.41.19-2302 =============================================================================== live-usb-maker 2.41.19-2302 Live Mediengerät /dev/sdb gefunden Gerät /dev/sdc (58,6G VendorC ProductCode) wird als Ziel verwendet Datei /media/sda4/Arbeitsordner/antiX/antiX 25.a2-testing/antiX-25.a2-runit_386-full.iso wird als Quelle verwendet Distro: antiX-25.a2-runit_386-full alpha2 14 August 2025 Grub Konfiguration 2.0 gefunden gesamt benutzt unbelegt Gesamtes Laufwerk 58.6 GiB 58.6 GiB 1 MiB Hauptpartition 58.5 GiB 2.00 GiB 56.5 GiB UEFI Partition 50 MiB 32 MiB 18 MiB Bereit live-usb auf Gerät sdc ... mit Kopiere Datei /media/sda4/Arbeitsordner/antiX/antiX 25.a2-testing/antiX-25.a2-runit_386-full.iso zu erstellen live-usb-maker 2.41.19-2302: partition-clear >> partition-clear > dd status=none if=/dev/zero of=/dev/sdc bs=512 count=34 > dd status=none if=/dev/zero of=/dev/sdc bs=512 count=34 seek=64 > dd status=none conv=notrunc if=/dev/zero of=/dev/sdc bs=512 count=34 seek=122879966 > partprobe /dev/sdc live-usb-maker 2.41.19-2302: partition-make >> partition-make msdos Partitionierung wird verwendet > parted --script --align optimal /dev/sdc unit MiB mklabel msdos > dd status=none if=/dev/zero of=/dev/sdc seek=1024 bs=1K count=128 > parted --script --align optimal /dev/sdc unit MiB mkpart primary 1 59949 > parted --script --align optimal /dev/sdc unit MiB set 1 boot on > dd status=none if=/dev/zero of=/dev/sdc seek=61387776 bs=1K count=128 > parted --script --align optimal /dev/sdc unit MiB mkpart primary 59949 59998 > parted --script --align optimal /dev/sdc unit MiB set 2 esp on > partprobe /dev/sdc > wait_for_file /dev/sdc1 live-usb-maker 2.41.19-2302: makefs-bios >> makefs-bios > mkfs.ext4 -O ^64bit -m0 -i16384 -J size=32 /dev/sdc1 mke2fs 1.47.0 (5-Feb-2023) Die Unterstützung für 64-bittige Dateisysteme wurde nicht aktiviert. Die längeren Felder, die diese Eigenschaft benötigt erlauben die Erstellung der Prüfsumme in voller Stärke. Geben Sie „-O 64bit” an, um dies zu korrigieren. Ein Dateisystem mit 15346688 (4k) Blöcken und 3842048 Inodes wird erzeugt. UUID des Dateisystems: 4f1d90ed-aa6d-4761-8b8b-83c996573636 Superblock-Sicherungskopien gespeichert in den Blöcken: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424 beim Anfordern von Speicher für die Gruppentabellen: 0/469 erledigt Inode-Tabellen werden geschrieben: 0/469 1/469 erledigt Das Journal (8192 Blöcke) wird angelegt: erledigt Die Superblöcke und die Informationen über die Dateisystemnutzung werden geschrieben: 0/469 erledigt > tune2fs -L antiX-Live-usb /dev/sdc1 tune2fs 1.47.0 (5-Feb-2023) > wait_for_file /dev/sdc2 live-usb-maker 2.41.19-2302: makefs-uefi >> makefs-uefi > mkfs.vfat -F 32 -n ANTIX-UEFI /dev/sdc2 mkfs.fat 4.2 (2021-01-31) > partprobe /dev/sdc > wait_for_file /dev/sdc1 > mkdir -p ./main > mount -t ext4 /dev/sdc1 ./main > wait_for_file /dev/sdc2 > mkdir -p ./uefi > mount -t vfat /dev/sdc2 ./uefi Dateisystem Typ Größe Benutzt Verf. Verw% Eingehängt auf /dev/sdc1 ext4 58G 24K 58G 1% main /dev/sdc2 vfat 49M 512 49M 1% uefi live-usb-maker 2.41.19-2302: copy-uefi >> copy-uefi Kopiere von iso auf Partition uefi Dateien [Ee][Ff][Ii] version > cp --no-dereference --preserve=mode,links --recursive ./iso/EFI ./uefi/. > cp --no-dereference --preserve=mode,links --recursive ./iso/version ./uefi/. Dell uefi memtest Bug beheben > cp ./uefi/EFI/BOOT/grubx64.efi ./uefi/EFI/BOOT/fallback.efi live-usb-maker 2.41.19-2302: copy-main >> copy-main > rm -rf ./main/boot.orig Kopiere von iso auf Partition main copy /antiX/vmlinuz > cpio -pdm --quiet ./main/ > e4defrag -v ./antiX/vmlinuz e4defrag 1.47.0 (5-Feb-2023) ext4 defragmentation for ./antiX/vmlinuz [1/1][79;0H[K[1/1]./antiX/vmlinuz: 100% extents: 1 -> 1 [ OK ] Success: [1/1] copy /antiX/initrd.gz > cpio -pdm --quiet ./main/ > e4defrag -v ./antiX/initrd.gz e4defrag 1.47.0 (5-Feb-2023) ext4 defragmentation for ./antiX/initrd.gz [1/1][79;0H[K[1/1]./antiX/initrd.gz: 0%[79;0H[K[1/1]./antiX/initrd.gz: 100% extents: 2 -> 1 [ OK ] Success: [1/1] copy remaining files ... > cpio -pdm --quiet ./main/ > write_file ./main/made-by-live-usb-maker created: So 28. Sep 08:19:34 CEST 2025 program: live-usb-maker version: 2.41.19-2302 (Sat, 25 Feb 2023 12:45:10 -0500) > dd status=none if=/dev/urandom of=./main/antiX/random-seed bs=512 count=1 > chmod 600 ./main/antiX/random-seed > rm -rf ./main/.disk live-usb-maker 2.41.19-2302: check-usb-md5 >> check-usb-md5 Überprüfung von md5 für initrd.gz > md5sum -c initrd.gz.md5 initrd.gz: OK Überprüfung von md5 für linuxfs > md5sum -c linuxfs.md5 linuxfs: OK Überprüfung von md5 für vmlinuz > md5sum -c vmlinuz.md5 vmlinuz: OK live-usb-maker 2.41.19-2302: uuids >> uuids Benutze antiX/MX Grub Config 2.0 > mkdir -p ./uefi/boot/grub > cp ./main/boot/grub/config/efi-grub.cfg ./uefi/boot/grub/grub.cfg > touch ./main/boot/grub/config/did-efi-grub > sed -i /^\s*#/! s/%UUID%/4f1d90ed-aa6d-4761-8b8b-83c996573636/ ./uefi/boot/grub/grub.cfg > rm -f ./main/boot/grub/config/*.id > touch ./main/boot/grub/config/c8f80f5c48348ad76adf771d838a31e2.id > sed -i /^\s*#/! s|%ID_FILE%|/boot/grub/config/c8f80f5c48348ad76adf771d838a31e2.id| ./uefi/boot/grub/grub.cfg live-usb-maker 2.41.19-2302: install >> Installieren extlinux version 6.04 > dd status=none bs=440 conv=notrunc count=1 if=/usr/lib/syslinux/mbr/mbr.bin of=/dev/sdc > rm -f ./main/boot/syslinux/chain.c32 > rm -f ./main/boot/syslinux/gfxboot.c32 > rm -f ./main/boot/syslinux/ldlinux.c32 > rm -f ./main/boot/syslinux/libcom32.c32 > rm -f ./main/boot/syslinux/libmenu.c32 > rm -f ./main/boot/syslinux/libutil.c32 > rm -f ./main/boot/syslinux/menu.c32 > rm -f ./main/boot/syslinux/syslinux.bin > rm -f ./main/boot/syslinux/version > cp /usr/lib/syslinux/modules/bios/chain.c32 ./main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/gfxboot.c32 ./main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/vesamenu.c32 ./main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/ldlinux.c32 ./main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/libcom32.c32 ./main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/libmenu.c32 ./main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/libutil.c32 ./main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/linux.c32 ./main/boot/syslinux/ > cp /usr/lib/syslinux/modules/bios/menu.c32 ./main/boot/syslinux/ > write_file ./main/boot/syslinux/version 6.04 > extlinux -i ./main/boot/syslinux /run/live-usb-maker/main/boot/syslinux is device /dev/sdc1 Dateisystem Typ Größe Benutzt Verf. Verw% Eingehängt auf /dev/sdc1 ext4 58G 2,0G 56G 4% main /dev/sdc2 vfat 49M 13M 36M 26% uefi >> Abgeschlossen live-usb-maker took 3 minutes and 51 seconds.Windows is like a submarine. Open a window and serious problems will start.
October 8, 2025 at 5:11 pm #187115j0ta
MemberHi @Robin have you tried make the usb partition msdos ? Not sure if you mean it with the 2 MBR
Gparted > Right top select the usb device > menu Device > Create a partition table > msdos🇳🇴🇸🇾🇸🇹🇪🇲🇩 🇺🇸🇪🇷
🇱🇮🇧🇷🇪🇧🇴🇴🇹 🇺🇸🇪🇷
🇦🇳🇹🇮🇽 🇺🇸🇪🇷
🇱🇮🇧🇷🇪🇼🇴🇱🇫 🇺🇸🇪🇷
Anti A.I userOctober 8, 2025 at 6:17 pm #187121Robin
Memberhave you tried make the usb partition msdos ?
Thanks @j0ta. Even when my first try was with gpt, all other attempts have been done with an MSDOS partition table on the sticks. Now back from testing with the ISO having been written by dd to the stick directly, showing up as Joliet/ISO 9660.
Same result. Boot error before even antiX boot screen is displayed.
Also meanwhile I’ve changed the partition setting from “esp” to “boot” in the UEFI vfat partition in the “fully featured” approach, and additionally changed the “boot” flag to “bls-boot” the antiX ext4 partition in the hope that now grub in the efi partition will be recognized finally. All in vein.
Will try next to replace the EFI vfat partition by a default fat or fat32 partition, and then (re-)install a bootloader (syslinux or grub) into this extra partition on the LIVE USB stick, pointing to the ext4 partition then for actual antiX startup, in the hope that then the PC can finally boot it. But it’s late today already, time for mattress eavesdropping service 🙂 So continuing with trying to bring it up finally only tomorrow evening.
All I know about that device by now is, that it is a MSI desktop PC from 2004, with Celeron 2.8 GHz and plenty of RAM, but I didn’t make it to read out the inxi. Maybe I should download and try an older antiX version first, possibly that could boot so I get at least an initial inxi readout.
Windows is like a submarine. Open a window and serious problems will start.
October 9, 2025 at 10:43 am #187169j0ta
MemberAh ok, misunderstood it
Yes, that’s a good idea try if you can usb boot antiX 22.
If it still refuses to boot
the only alternative I can tell is using a external usb cd/dvd and install it to the usb- This reply was modified 11 months, 3 weeks ago by j0ta.
🇳🇴🇸🇾🇸🇹🇪🇲🇩 🇺🇸🇪🇷
🇱🇮🇧🇷🇪🇧🇴🇴🇹 🇺🇸🇪🇷
🇦🇳🇹🇮🇽 🇺🇸🇪🇷
🇱🇮🇧🇷🇪🇼🇴🇱🇫 🇺🇸🇪🇷
Anti A.I userOctober 21, 2025 at 4:04 am #188028Robin
MemberFinally I made it boot. Alpha2 works really fine on this device. Took some hours of steady try and error until I understood what’s going on with this boot issue.
Luckily I had an old antiX 17.4.1 (remastered) USB-stick-backup 1:1 image which I dd’d to the stick, and immediately the antiX boot screen turned up. (The OS booted fine from this 17.4.1 backup, but that is not what counts here.) The interesting part is: Now I have simply copied over all the content from the antiX folder of a freshly created, non booting 25.a2 stick to the antiX folder of the booting 17.4.1 stick, overwriting/deleting all of the antiX 17.4.1 related files therein. Additionally fixed the entries in boot/syslinux/sylinux.cfg according to the file found on the 25.a2 stick. (And yes, sure I have carefully checked the shasum before creating the a2 sticks from the downloaded ISOs, so not an issue caused by a corrupted download.)That did it. This franken-25a2-USB stick Boots straight away to the default antiX boot screen and then comes up with the antiX 25a2 desktop flawlessly.
I’ll investigate further what causes the recent default stick not to boot as expected.
Major differences are:
– The old stick (in the backup image) has been created with an old Live USB maker version, using syslinux 6.0.3, running on a 32 bit system.
– The failing stick has been created on antiX 23.1 full runit 64bit.
– The old stick has merely a single partition, FAT32 formatted, with the markers “boot, LBA”.
– The failing stick has two partitions, the second one FAT32, marked as “boot”. The first one is ext4, containing the complete boot folder, while the FAT32 partition seems only to contain EFI related stuff for grub boot.The failing stick hangs even when redoing all the extlinux/syslinux or grub setup, either with “boot error” or “Grub” followed by a blinking cursor, which most likely points to the BIOS simply not able to access the ext4 partition for entering the next boot stage after stage 1 from the boot sector.
I have meanwhile added a huge ext4 Data partition to the functioning stick, and it still boots fine. So it is obviously not a problem to have more than a single partition on the stick. But it seems there is an issue with the order possibly: The FAT32 boot partition needs possibly to be the first one, since I already had tried to install the complete bootloader to the existing FAT32 partition of the original 25a2 stick (which I even removed and created new from scratch), there was no sign of entering a next boot stage, no syslinux or grub version message line nor further error messages from execution of next boot stages.
I’ll do some further analysing and testing, so the antiX USB sticks for 32 bit devices can be designed a bit more compatible again for these devices. I guess there is no need for an additional UEFI partition in 32 bit (except for some early 32 bit apple devices using EFI)? Instead it should come with a proper FAT32 boot partition designed for utmost BIOS compatibility in standard PCs.
Fist impressions of the 25a2 version:
1.) Great, really: antiX Acoustic Colours works now even on 32 bit without any stuttering. Pipewire, wireplumber, etc. now system load down to 17% total when processing audio.
Still depending highly on sample rate: 128kbps@48khz is fine, while 320kbps@44khz or 48khz drives CPU up to 70…100%.
Also, having open (and keeping open) pavucontrol causes dropout in audio, driving CPU up to 100% constant.
(Observed in “Analog Stereo Duplex” mode and “Pro Audio” mode both.) Closing pavucontrol restores frecklesfree sound again immediately, and CPU load drops to ~20% even when easyeffects is engaged with antiX Accoustic Colours Cathederal mode (~10% when easyeffects is turned off completely). These are reasonable values already.2.) There is an issue with inxi. Hangs forever when checking the Graphics. Needs to be addressed.
$ sudo inxi -zv8 --za --zv System: Kernel: 5.10.240-antix.1-486-smp arch: i686 bits: 32 compiler: gcc v: 12.2.0 clocksource: tsc avail: hpet,acpi_pm parameters: vga=791 lang=de_DE tz=Europe/Berlin quiet splash=v disable=lx Desktop: IceWM v: 3.8.2 tools: avail: slock,xlock dm: slimski v: 1.5.0 Distro: antiX-25.a2-runit_386-full alpha2 14 August 2025 base: Debian GNU/Linux 13 (trixie) Machine: Type: Desktop Mobo: MICRO-STAR model: MS-7065 v: 100 serial: <filter> BIOS: American Megatrends v: 1.1 on 07.00T date: 10/22/04 Battery: Message: No system battery data found. Is one present? Memory: System RAM: total: 2 GiB available: 1.96 GiB used: 1.42 GiB (72.7%) igpu: 8 MiB Array-1: capacity: 4 GiB slots: 4 modules: 0 EC: None max-module-size: 1024 MiB Device-1: DIMM1 info: double-bank type: DIMM SDRAM detail: N/A size: 1024 MiB speed: N/A volts: N/A width: N/A manufacturer: N/A part-no: N/A serial: N/A Device-2: DIMM2 info: not installed type: N/A size: N/A speed: N/A volts: N/A width: N/A manufacturer: N/A part-no: N/A serial: N/A Device-3: DIMM3 info: double-bank type: DIMM SDRAM detail: N/A size: 1024 MiB speed: N/A volts: N/A width: N/A manufacturer: N/A part-no: N/A serial: N/A Device-4: ROW-3 info: not installed type: N/A size: N/A speed: N/A volts: N/A width: N/A manufacturer: N/A part-no: N/A serial: N/A PCI Slots: Slot: 1 type: PCI status: available length: long volts: 3.3 bus-ID: N/A Slot: 2 type: PCI status: available length: long volts: 3.3 bus-ID: N/A Slot: 3 type: PCI status: unknown length: long volts: 3.3 bus-ID: N/A Slot: 4 type: PCI status: unknown length: long volts: 3.3 bus-ID: N/A Slot: 5 type: PCI status: unknown length: long volts: 3.3 bus-ID: N/A Slot: 4 type: PCI status: unknown length: long volts: 3.3 bus-ID: N/A CPU: Info: model: Intel Celeron socket: 478 (FC-478) note: check bits: 32 arch: Netburst Prescott built: 2004-06 process: Intel 90nm family: 0xF (15) model-id: 4 stepping: 1 microcode: N/A Topology: cpus: 1x dies: 1 cores: 1 smt: <unsupported> cache: L1: 16 KiB desc: d-1x16 KiB L2: 256 KiB desc: 1x256 KiB Speed (MHz): 2812 min/max: N/A base/boost: 2800/4000 volts: 3.3 V ext-clock: 133 MHz core: 1: 2812 bogomips: 5624 Flags: acpi apic bts cid clflush cmov constant_tsc cpuid cx8 de ds_cpl dtes64 dts fpu fxsr ht mca mce mmx monitor msr mtrr pae pat pbe pebs pge pni pse pse36 sep ss sse sse2 tm tsc vme xtpr Vulnerabilities: <filter>(here inxi -G hangs forever, so every verboseability above -v0 also hangs in this place where graphics is processed, inxi must be killed by ctrl+c to recover. I’ll try to replace the script by the most recent version from codeberg, and if this doesn’t fix things already I’ll file a bug report for this over there.)
Workaround: Missing system data, collected by other commands:
$ sudo lspci -vvvgives the following for the graphics:
00:02.0 VGA compatible controller [0300]: Intel Corporation 82865G Integrated Graphics Controller [8086:2572] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Hetis 865GV-E (MS-7065) [1462:7650] Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f0000000 (32-bit, prefetchable) Memory at ffe80000 (32-bit, non-prefetchable) I/O ports at ec00 Expansion ROM at 000c0000 [virtual] [disabled] Capabilities: [d0] Power Management version 1 Kernel driver in use: i915 Kernel modules: i915$ sudo inxi -Aaaa Audio: Device-1: Intel 82801EB/ER AC97 Audio vendor: Micro-Star MSI Hetis 865GV-E driver: snd_intel8x0 v: kernel bus-ID: 00:1f.5 chip-ID: 8086:24d5 class-ID: 0401 API: ALSA v: k5.10.240-antix.1-486-smp status: kernel-api with: apulse type: pulse-emulator tools: alsactl,alsamixer,amixer Server-1: PipeWire v: 1.4.2 status: n/a (root, process) with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin tools: pw-cat,pw-cli,wpctl $ sudo inxi -Nxxxx Network: Device-1: Realtek RTL8169 PCI Gigabit Ethernet vendor: Micro-Star MSI Hetis 865GV-E driver: r8169 v: kernel port: cc00 bus-ID: 01:0b.0 chip-ID: 10ec:8169 class-ID: 0200Windows is like a submarine. Open a window and serious problems will start.
October 22, 2025 at 1:07 am #188115andfree
MemberThere is an issue with inxi. Hangs forever when checking the Graphics.
I have already posted that I face this issue in a laptop with these
Graphics: Device-1: Intel 82852/855GM Integrated Graphics vendor: Toshiba driver: i915 v: kernel arch: Gen-2 bus-ID: 00:02.0 Display: server: X.Org v: 1.21.1.7 driver: X: loaded: intel unloaded: fbdev,modesetting,vesa dri: swrast gpu: i915 resolution: 1024x768~60Hz API: EGL v: 1.4,1.5 drivers: kms_swrast,swrast platforms: active: gbm,x11,surfaceless,device inactive: wayland,device-0 API: OpenGL v: 4.5 vendor: x.org mesa v: 22.3.6 glx-v: 1.4 direct-render: yes renderer: llvmpipe (LLVM 15.0.6 128 bits)- This reply was modified 11 months, 1 week ago by andfree.
antiX utilities for processing PDF files (posted by ChPol)
October 22, 2025 at 6:58 pm #188165Robin
MemberI have already posted that I face this issue in a laptop with these
Hi @andfree Thanks, hadn’t read the whole thread, sorry.
I’ll try to replace the script by the most recent version from codeberg, and if this doesn’t fix things already I’ll file a bug report for this over there.
No need for a bug report. This is already fixed in latest inxi (master branch) at codeberg:
$ inxi --version inxi 3.3.39-00 (2025-08-29)@andfree , can you please confirm 3.3.39-00 works for you also? (It is enough to download the scriptfile from codeberg.org, and place it into the /usr/bin folder, making it executable (chmod/chown), after moving the original inxi script aside.)
@anticapitalista : So this package simply needs an package update in the antiX repos.
Here the full readout from 32 bit antiX 25a2, after live kernel update to 686:
$ sudo inxi -zv8 --za --zv System: Kernel: 5.10.240-antix.1-686-smp-pae arch: i686 bits: 32 compiler: gcc v: 14.2.0 clocksource: tsc avail: hpet,acpi_pm parameters: vga=791 persist_all lang=de_DE tz=Europe/Berlin root=uuid=b04223f7-d60c-4dcb-9f8e-c3f06405aa52 quiet splasht disable=lxF Desktop: IceWM v: 3.9.0 tools: avail: slock,xlock dm: slimski v: 1.5.0 Distro: antiX-25.a2-runit_386-full alpha2 14 August 2025 base: Debian GNU/Linux 13 (trixie) Machine: Type: Desktop Mobo: MICRO-STAR model: MS-7065 v: 100 serial: <filter> BIOS: American Megatrends v: 1.1 on 07.00T date: 10/22/04 Battery: Message: No system battery data found. Is one present? Memory: System RAM: total: 2 GiB available: 1.95 GiB used: 744.9 MiB (37.4%) igpu: 8 MiB Array-1: capacity: 4 GiB slots: 4 modules: 0 EC: None max-module-size: 1024 MiB Device-1: DIMM1 info: double-bank type: DIMM SDRAM detail: N/A size: 1024 MiB speed: N/A volts: N/A width: N/A manufacturer: N/A part-no: N/A serial: N/A Device-2: DIMM2 info: not installed type: N/A size: N/A speed: N/A volts: N/A width: N/A manufacturer: N/A part-no: N/A serial: N/A Device-3: DIMM3 info: double-bank type: DIMM SDRAM detail: N/A size: 1024 MiB speed: N/A volts: N/A width: N/A manufacturer: N/A part-no: N/A serial: N/A Device-4: ROW-3 info: not installed type: N/A size: N/A speed: N/A volts: N/A width: N/A manufacturer: N/A part-no: N/A serial: N/A PCI Slots: Slot: 1 type: PCI status: available length: long volts: 3.3 bus-ID: N/A Slot: 2 type: PCI status: available length: long volts: 3.3 bus-ID: N/A Slot: 3 type: PCI status: unknown length: long volts: 3.3 bus-ID: N/A Slot: 4 type: PCI status: unknown length: long volts: 3.3 bus-ID: N/A Slot: 5 type: PCI status: unknown length: long volts: 3.3 bus-ID: N/A Slot: 4 type: PCI status: unknown length: long volts: 3.3 bus-ID: N/A CPU: Info: model: Intel Celeron socket: 478 (FC-478) note: check bits: 32 arch: Netburst Prescott built: 2004-06 process: Intel 90nm family: 0xF (15) model-id: 4 stepping: 1 microcode: N/A Topology: cpus: 1x dies: 1 cores: 1 smt: <unsupported> cache: L1: 16 KiB desc: d-1x16 KiB L2: 256 KiB desc: 1x256 KiB Speed (MHz): 2812 min/max: N/A base/boost: 2800/4000 volts: 3.3 V ext-clock: 133 MHz core: 1: 2812 bogomips: 5624 Flags: acpi apic bts cid clflush cmov constant_tsc cpuid cx8 de ds_cpl dtes64 dts fpu fxsr ht mca mce mmx monitor msr mtrr pae pat pbe pebs pge pni pse pse36 pti sep ss sse sse2 tm tsc vme xtpr Vulnerabilities: <filter> Graphics: Device-1: Intel 82865G Integrated Graphics vendor: Micro-Star MSI Hetis 865GV-E driver: i915 v: kernel arch: Gen-2 process: Intel 130nm built: 2002-03 ports: active: VGA-1 empty: DVI-I-1 bus-ID: 00:02.0 chip-ID: 8086:2572 class-ID: 0300 Display: server: X.Org v: 21.1.16 driver: X: loaded: intel unloaded: fbdev,modesetting,vesa dri: swrast gpu: i915 display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 1152x864 s-dpi: 97 s-size: 303x227mm (11.93x8.94") s-diag: 379mm (14.91") Monitor-1: VGA-1 mapped: VGA1 model: Belinea/Maxdata 0x1b6c serial: <filter> built: 1998 res: mode: 1152x864 hz: 75 scale: 100% (1) dpi: 91 gamma: 1.83 chroma: red: x: 0.643 y: 0.329 green: x: 0.271 y: 0.604 blue: x: 0.141 y: 0.063 white: x: 0.278 y: 0.310 size: 320x240mm (12.6x9.45") diag: 400mm (15.7") ratio: 4:3 modes: 1280x1024, 1152x864, 1024x768, 800x600, 640x480, 640x400 API: EGL Message: Unreliable API tool+hardware. Override with --egl. API: OpenGL v: 4.5 vendor: mesa v: 25.0.7-2 glx-v: 1.4 es-v: 3.2 direct-render: yes renderer: llvmpipe (LLVM 19.1.7 128 bits) device-ID: ffffffff:ffffffff memory: 1.9 GiB unified: yes Info: Tools: api: eglinfo,glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr Audio: Device-1: Intel 82801EB/ER AC97 Audio vendor: Micro-Star MSI Hetis 865GV-E driver: snd_intel8x0 v: kernel bus-ID: 00:1f.5 chip-ID: 8086:24d5 class-ID: 0401 API: ALSA v: k5.10.240-antix.1-686-smp-pae status: kernel-api with: apulse type: pulse-emulator tools: alsactl,alsamixer,amixer Server-1: PipeWire v: 1.4.2 status: n/a (root, process) with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin tools: pw-cat,pw-cli,wpctl Network: Device-1: Realtek RTL8169 PCI Gigabit Ethernet vendor: Micro-Star MSI Hetis 865GV-E driver: r8169 v: kernel port: cc00 bus-ID: 01:0b.0 chip-ID: 10ec:8169 class-ID: 0200 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> IP v4: <filter> scope: global broadcast: <filter> IP v4: <filter> type: secondary dynamic noprefixroute scope: global broadcast: <filter> IP v6: <filter> type: temporary dynamic scope: global IP v6: <filter> type: dynamic mngtmpaddr noprefixroute scope: global IP v6: <filter> type: temporary dynamic scope: global IP v6: <filter> type: dynamic mngtmpaddr noprefixroute scope: global IP v6: <filter> scope: link Info: services: smbd,wpa_supplicant WAN IP: <filter> Bluetooth: Message: No bluetooth data found. Logical: Message: No logical block device data found. RAID: Message: No RAID data found. Drives: Local Storage: total: 58.59 GiB used: 17.56 GiB (30.0%) ID-1: /dev/sda maj-min: 8:0 model: N/A size: 58.59 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter> fw-rev: 3.00 scheme: MBR SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? Optical-1: /dev/sr0 vendor: MITSUMI model: CD-ROM !B rev: B04 dev-links: cdrom Features: speed: 4 multisession: yes audio: yes dvd: no rw: none state: running Partition: ID-1: /live/boot-dev raw-size: 54.88 GiB size: 53.72 GiB (97.88%) used: 15.87 GiB (29.5%) fs: ext4 block-size: 4096 B dev: /dev/sda2 maj-min: 8:2 label: <filter> uuid: <filter> ID-2: /media/KINGSTON raw-size: 3.7 GiB size: 3.7 GiB (99.89%) used: 1.69 GiB (45.8%) fs: vfat block-size: 512 B dev: /dev/sda1 maj-min: 8:1 label: <filter> uuid: <filter> Swap: Alert: No swap data was found. Unmounted: Message: No unmounted partitions found. USB: Hub-1: 1-0:1 info: full speed or root hub ports: 8 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002 class-ID: 0900 Device-1: 1-1:2 info: USB Disk 20 type: mass storage driver: usb-storage interfaces: 1 rev: 2.1 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA chip-ID: 346d:5678 class-ID: 0806 serial: <filter> Device-2: 1-8:3 info: Carry Eng. 6-in-1 Card Reader type: mass storage driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA chip-ID: 07cc:0301 class-ID: 0806 serial: <filter> Hub-2: 2-0:1 info: full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 1d6b:0001 class-ID: 0900 Hub-3: 3-0:1 info: full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 1d6b:0001 class-ID: 0900 Hub-4: 4-0:1 info: full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 1d6b:0001 class-ID: 0900 Hub-5: 5-0:1 info: full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 1d6b:0001 class-ID: 0900 Sensors: Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or lm-sensors. Repos: Packages: pm: dpkg pkgs: 1824 libs: 891 tools: apt,apt-get,aptitude,synaptic Active apt repos in: /etc/apt/sources.list.d/antix.sources 1: deb http://repo.antixlinux.com/trixie/ trixie main nonfree nosystemd Active apt repos in: /etc/apt/sources.list.d/debian.sources 1: deb deb-src http://ftp.de.debian.org/debian/ trixie main contrib non-free non-free-firmware Processes: CPU top: 5 of 128 1: cpu: 300% command: ps pid: 24250 mem: 2.76 MiB (0.1%) 2: cpu: 5.1% command: Xorg pid: 3809 mem: 72.9 MiB (3.6%) 3: cpu: 2.7% command: sudo pid: 24217 mem: 5.79 MiB (0.2%) 4: cpu: 1.9% command: zzzfm pid: 3978 mem: 35.6 MiB (1.7%) 5: cpu: 0.8% command: conky pid: 7660 mem: 6.78 MiB (0.3%) Memory top: 5 of 128 1: mem: 72.9 MiB (3.6%) command: Xorg pid: 3809 cpu: 5.1% 2: mem: 35.6 MiB (1.7%) command: zzzfm pid: 3978 cpu: 1.9% 3: mem: 27.5 MiB (1.3%) command: roxterm pid: 11102 cpu: 0.3% 4: mem: 22.9 MiB (1.1%) command: icewm pid: 3958 cpu: 0.7% 5: mem: 20.6 MiB (1.0%) command: volumeicon pid: 4256 cpu: 0.0% Info: Processes: 128 Power: uptime: 1h 14m states: freeze,standby,mem,disk suspend: s2idle avail: shallow wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 792.9 MiB Init: runit v: N/A runlevel: 2 tool: service Compilers: gcc: 14.2.0 Shell: Sudo (sudo) v: 1.9.16p2 default: Bash v: 5.2.37 running-in: roxterm inxi: 3.3.39$ sudo ps_mem.py Private + Shared = RAM used Program 88.0 KiB + 26.5 KiB = 114.5 KiB runit 112.0 KiB + 27.5 KiB = 139.5 KiB runsvdir 128.0 KiB + 42.5 KiB = 170.5 KiB seatd 244.0 KiB + 92.5 KiB = 336.5 KiB dbus-launch 180.0 KiB + 227.5 KiB = 407.5 KiB startup 344.0 KiB + 228.5 KiB = 572.5 KiB udevil 284.0 KiB + 414.5 KiB = 698.5 KiB icewm-session 476.0 KiB + 403.0 KiB = 879.0 KiB getty (4) 476.0 KiB + 429.5 KiB = 905.5 KiB dconf-service 564.0 KiB + 343.5 KiB = 907.5 KiB desktop-session 576.0 KiB + 351.5 KiB = 927.5 KiB devmon 732.0 KiB + 339.5 KiB = 1.0 MiB runsv (11) 736.0 KiB + 347.5 KiB = 1.1 MiB gconfd-2 748.0 KiB + 534.5 KiB = 1.3 MiB at-spi-bus-launcher 816.0 KiB + 566.5 KiB = 1.4 MiB at-spi2-registryd 908.0 KiB + 606.5 KiB = 1.5 MiB dbus-daemon (3) 1.4 MiB + 289.5 KiB = 1.7 MiB udevd 1.2 MiB + 699.5 KiB = 1.8 MiB pipewire-pulse 1.6 MiB + 394.5 KiB = 2.0 MiB bash 1.8 MiB + 673.5 KiB = 2.4 MiB conky 924.0 KiB + 1.5 MiB = 2.4 MiB sudo (2) 2.6 MiB + 352.5 KiB = 2.9 MiB wpa_supplicant 2.5 MiB + 441.5 KiB = 2.9 MiB nmbd 2.6 MiB + 530.5 KiB = 3.1 MiB connmand 2.4 MiB + 1.4 MiB = 3.8 MiB slimski 1.9 MiB + 2.1 MiB = 4.0 MiB fbxkb 2.9 MiB + 1.4 MiB = 4.3 MiB dhcpcd (5) 3.7 MiB + 1.2 MiB = 4.8 MiB pipewire 2.3 MiB + 3.6 MiB = 6.0 MiB volumeicon 6.7 MiB + 1.6 MiB = 8.3 MiB wireplumber 6.0 MiB + 4.1 MiB = 10.1 MiB icewm 6.4 MiB + 4.4 MiB = 10.8 MiB smbd (3) 5.4 MiB + 5.7 MiB = 11.0 MiB roxterm 13.8 MiB + 5.9 MiB = 19.7 MiB zzzfm 60.4 MiB + 3.3 MiB = 63.6 MiB Xorg --------------------------------- 177.8 MiB =================================(please note, this is not the ps_mem.py readout from vanilla, there is already a samba server running.)
The boot issue with the default antiX USB stick is still under investigation. Will come up with results once I’ve completed analysis. Meanwhile I made it boot already with linuxfs file moved to the huge ext4 data partition, so no longer limited to the 4GiB restriction causing difficult remaster and kernel update: (Only allowed me xz compression due to file size, which took ~3 hours to complete, unattended, for sure.) Simply adding “root=UUID=….” to the APPEND line in syslinux.cfg did the trick, pointing to the ext4 partition. Before that, in a first step, I had experimented with “puuid=….”, so the root and home persistence could be moved to the ext4 partition, allowing the initial xz compressed remaster finally, needed for a live kernel update to the 686 kernel.
25.a2 looks good so far.
Met a tiny translation and syntax (“%s”) issue in the Live Remaster tool, rarely seen error message. See screenshot. Some more strings in this tool are still untranslated in antiX 25.a2. Needs detailed inspection.
What else works and has been tested meanwhile here?
Shared Folders from antiX Control Centre do work fine still in trixie based antiX 25.a2. Helper tools install flawlessly, account(s) are set up as expected per user request. Allows speedy connection setup to e.g an antiX 23.1 machine.
- This reply was modified 11 months, 1 week ago by Robin. Reason: fixed typo: 25.a1 → 25.a2
Attachments:
Windows is like a submarine. Open a window and serious problems will start.
-
AuthorPosts
- The topic ‘32 bit antiX-25.a2-full for testers’ is closed to new replies.
