Search Results for 'boot from iso'

[Moderator BobC]

No, the program did not check if it had written the usb correctly for an antix iso. It said it was successful, but when i shutdown and rebooted to it, the checkmd5 failed and when I tried again the checkfs crashed the computer.

If the program had an option to check, that would be great. I don’t have any idea how to check an antix iso manually, or I could have done that before shutting down.

I found out I have another bad USB flashdrive. I used live-usb-maker to create it, and everything went ok, but it wouldn’t boot. I did it again 2 more times with similar results. I then used dd to write an iso to the flashdrive and then used a command I found to check to see if it was written correctly. As you can see, you need root authority to run it. The third time I had used a different flashdrive, and on that one the result was valid.

Sorry, not sure how to enter this code as the backticks are messing up the CODE tag and /CODE tag

$ cmp -nstat -c '%s' endeavouros-2020.09.20-x86_64.iso endeavouros-2020.09.20-x86_64.iso /dev/sdd
cmp: /dev/sdd: Permission denied
bobc@xps15-7559:/media/bobc/BIGData/iso
$ sudo cmp -n stat -c '%s' endeavouros-2020.09.20-x86_64.iso endeavouros-2020.09.20-x86_64.iso /dev/sdd
endeavouros-2020.09.20-x86_64.iso /dev/sdd differ: char 17707023, line 67892
bobc@xps15-7559:/media/bobc/BIGData/iso
$ sudo cmp -n stat -c '%s' endeavouros-2020.09.20-x86_64.iso endeavouros-2020.09.20-x86_64.iso /dev/sdd
bobc@xps15-7559:/media/bobc/BIGData/iso

I got the code from this thread: https://unix.stackexchange.com/questions/75483/how-to-check-if-the-iso-was-written-to-my-usb-stick-without-errors

My question is, I know how to check it if its written by dd, but how can I check it if its written by live-usb-maker in non-dd mode? And could these checks either be done optionally or by default automatically by the program at the end as part of the process instead of me trying to figure it out? I do know that antiX has a check function when booting its USB, but it would be much better to know when writing it that it was able to write, but that the flashdrive was not valid.

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

[Member Xecure]

Hi, ArchiMark

In the boot menu, hit F7 and select Console video = default. Remove all boot parameters except for quiet and add the parameter from=cd (to only boot from CD/DVD) and retry=20 to increase by 10 seconds the time limit to try to find the bood device.

The Boot Options bar should look like:

quiet from=cd retry=20

See if at least it gets to find the DVD and load antiX properly.

Hopefully someone with experience with this kind of trouble can recommend other boot parameters.

If you get to boot to it and see you are too limited in RAM, you could see if this experimental iso can free a bit more RAM.

Welcome to antiX!

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

[Forum Admin anticapitalista]

Any official position by the main devs? I think this is a fruitless discussion if we are going to get shut down.

I think this is a very fruitful discussion and well worth continuing.

How I see future antiX (ie the next stable ‘bullseye’ version).

Due to many upstream changes in Debian, python2 and a lot of gtk2 will go.
That includes a few apps that have been ‘standard’ on antiX eg disk-manager, lxkeymap, lxappearance(?), gtkdialog and others.

Our in-house apps also have to be ported from python2/gtk2 as well.
Dave has already started porting them (in testing/sid branch). Most seem to work ok, but there are bugs – testing will be needed.

The live-system (including frugal, remaster, snapshot etc) seems to be working ok. However, the UEFI side probably needs to be improved to cater for more and more frugal/live users booting via UEFI since they have newer hardware.

Documentation certainly needs updating.

All the above will need to be done for the next stable release once Debian11 is out.

Making antiX more usable:

Certainly, IMO, including user written scripts have made antiX more user friendly.
eg the IceWM toolbar script, antiX-wifi switcher, android-device-connect, fast_personal_menu_editor, icewm-menu-recent-files and others, though I personally don’t use any of them. The downside to including these useful scripts is that the menu could be considered to be ‘bloated’.

Having some sort of script/app for hd screens is necessary.
Updating the control centre from gtkdialog to using Xecure’s dialogbox version will probably be needed at some point.
I’m not too keen on the idea of a Welcome app. However, that doesn’t mean that it will not be included if most of us here want it.

What I don’t want is for antiX to be turned into something it is not meant to be.
For example, some in the past basically wanted it to be like a Debian lubuntu. If people want lxde, Xfce etc and ‘bells n whistles’ out of the box, then they really should try another distro.
We will always be systemd-free.
We will keep to IceWM/Rox default
We will ship with/promote our own (less known or even unknown) tools/apps over bigger and better known versions eg droopy, 1-1-voice etc.
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.

Of course, antiX is far from perfect and needs to adapt to changes posed upstream.
We have already done so eg by no longer making the base iso fit on a cd.
Other compromises will no doubt follow at some point in the future.

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

antiX with runit - leaner and meaner.

[Member Xecure]

Probably using these command (only for live system I think) will help. If this problem is related to the latest intel graphics firmware, then not even my iso will boot properly.

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

[Member Keeely]

I had to make another change to install openssh automatically. I needed to wait for the network to come up. In the end I did this, it’s really crude, but it seems to work:

until ping -q -c 1 -W 1 debian.org >/dev/null; do
  echo "Waiting for network to come up, and debian.org to resolve..."
  sleep 2
done

apt update
apt install --assume-yes openssh-server

Also, if you want to try some of this stuff out without creating a virtual machine manually, here’s a VirtualBox script I’m using to test this. The poweroff/unregister will error if you haven’t run it before, but it works for the most part.

#!/bin/bash
VM_NAME=antiX_test
ISO_NAME=new_antix.iso
DISK_NAME=antiXtest.vdi
VBoxManage controlvm $VM_NAME poweroff
VBoxManage unregistervm $VM_NAME --delete
VBoxManage createvm --name $VM_NAME --register
VBoxManage modifyvm $VM_NAME --memory 2048
VBoxManage modifyvm $VM_NAME --audio none
VBoxManage modifyvm $VM_NAME --nic1 nat
VBoxManage modifyvm $VM_NAME --boot1 dvd
VBoxManage modifyvm $VM_NAME --graphicscontroller vmsvga
VBoxManage modifyvm $VM_NAME --natpf1 "guestssh,tcp,,2222,,22"
VBoxManage storagectl $VM_NAME --name IDE --add ide
VBoxManage createmedium disk --filename $DISK_NAME --size 20480
VBoxManage storageattach $VM_NAME --storagectl IDE --port 0 --device 0 --type hdd --medium $DISK_NAME
VBoxManage storageattach $VM_NAME --storagectl IDE --port 1 --device 0 --type dvddrive --medium $ISO_NAME

Then, ssh -p 2222 root@localhost will login, assuming you’ve changed /etc/ssh/sshd_config to allow that. Going to need to write something to do that as well I guess.

• This reply was modified 2 years, 5 months ago by Keeely.

[Member jijojosephk]

Thank you again. I created a xorg.conf file inside /etc/X11. Initially I gave driver as ‘i810’ without any result. But later I’ve given intel and it worked when I use startx command. slim does show the same error and every boot ends up in command line as slim fails still. I’ll have to enter ‘startx’ to have GUI session. How can I see GUI during boot without explicitly entering any commands? I’m yet to try Xecure’s ISO.

[Member olsztyn]

Anonymous wrote:

If the problematic update occurred after you had recently performed a remaster operation,
and your system had been using dynamic root persistence, a fallback recovery is possible

Thank you skidoo for this recovery method. However I do not need to go to that extent as I have multiple copies of perfectly working antiX. This was just to report that today’s full update appears to cause a minor imperfection during boot.
A closer examination and comparing to boot appearance of antiX before update using a backup copy for more detail of this artifact:
– The small VGA size screen appears after fourth step – Start Init and appears to proceed to desktop. Upon shutdown the same small screen in top left appears to show.
– In comparison, booting a copy of antiX version before update results (after Start Init of full size) in screen blanking out for a while, after which the screen ‘Udev Done’ or something to that effect appears and then proceeds to desktop, no interim small screen.
Just to emphasize, it is not critical to me as I have multiple copies of perfectly working antiX, taught by prior experience, so I will try to identify what elements I can update and what to leave at current level, instead of total update.
Thanks again and best regards…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Moderator caprea]

All modern kernels use the modesetting driver instead of the intel-driver. Old intel cards often go better with intel.
If you get an old antiX-version or the iso from Xecure to boot, what you could try is to force the intel driver over the default modesetting on your installed system.

Create this text file on the installed system
/etc/X11/xorg.conf.d/20-intel.conf

with content:

Section "Device"   
   Identifier  "Intel Graphics"
   Driver      "intel"
#  Option      "AccelMethod" "uxa"  #could also use the default "sna"
   Option      "TearFree"     "true"
EndSection

The acceleration method line is might needed or not.

Here’s a link to older versions
https://sourceforge.net/projects/antix-linux/files/old/

antix 13.2 should definitely boot

Edit: I totally missed that, you can get to the command-line. So you can create the file from there with
sudo touch /etc/X11/xorg.conf.d/20-intel.conf

• This reply was modified 2 years, 5 months ago by caprea.

[Member Keeely]

It looks like I have a script that mostly works. My ‘setup.sh’ referred to in the other script. So long as I create the partition first, it’s just an answerfile that’s needed. The only problem is, the cli-installer clearly copies my doctored inittab out of the running root because my install antiX ends up including it. I guess I was hoping that file came from some kind of ‘base-files.deb’ package, but it doesn’t, so I’ll have to do something about that, maybe put aside the original in the root of the ISO. Not rocket science at least.

Here’s the script, with a safety feature of checking the MBR is blank, just in case you’re silly enough to boot this ISO in a machine that you care about this should stop you losing all your data. It doesn’t set timezone or anything. One remaining problem is the prompt for cd-rom removal on poweroff, I have to figure out how to disable that, and just make it power off, then it’s on to installing some extra packages.

EDIT: I’ve added an extra line, to edit live-umount and remove the line ‘read x’ because it includes an ENTER prompt which prevents a clean shutdown.

DEVICE="/dev/sda"

# Dump the mbr somewhere
dd if=$DEVICE of=/tmp/mbr.bin bs=512 count=1
# Dump a file of zeros of the same size
dd if=/dev/zero of=/tmp/zero.bin bs=512 count=1

# Only format if the disk is blank
diff /tmp/mbr.bin /tmp/zero.bin >/dev/null

if [ $? -ne 0 ]
then
    echo "Disk appears to be formatted already, aborting."
    return
fi

# Partition the entire disk with single partition, no swap
echo start=2048 | sfdisk $DEVICE
    
# format it.
mkfs.ext4 ${DEVICE}1

cp /live/boot-dev/inittab_backup /etc/inittab
cp /live/boot-dev/bashrc_backup /root/.bashrc

cli-installer $DEVICE < /live/boot-dev/answers.txt
    
cat <<ENDOFANSWERS | cli-installer
n
sda1
y
n
n
n
y
y
antix1
n
n
n
n
n
n
root
root
root
n

ENDOFANSWERS

# Update live-umount to avoid any prompts for keypress.
sed -i -e 's/^[[:space:]]*read x$//g' /live/bin/live-umount
poweroff

• This reply was modified 2 years, 5 months ago by Keeely.
• This reply was modified 2 years, 5 months ago by Keeely.

[Forum Admin rokytnji]

My Xmass present from the wife. HP 14″ 2-in-1 Touch Teal Chromebook
HPModel: 14a-na0090wm, She paid 179 bucks.

Still learning this one since new < flip screen and touch screen > . It is screaming fast.

My Acer C710 Chromebook is still a dedicated 64bit AntiX Full iso system. Battery is still good and packs on the motorcycle good. Syncs OK with my Samsung Phone.
It is screaming fast also. Been a forum supporter for ages. I don’t plan on retiring it soon.

I don’t dual boot anymore. I have enough hardware to make that mode of operation moot in my use ca-sage. I did a dual boot on the acer c710
https://www.chromium.org/chromium-os/chromiumos-design-docs/disk-format
Till the drive died and I used another scrap ssd drive for antix only and changed the bios from default to .https://johnlewis.ie/custom-chromebook-firmware/rom-download/

Sure simplified the bios choice keys.

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

This ended up being a lot more challenging than I had expected. I used squashfs-tools-ng to convert the squashfs to a tarball, so I could edit it in tar form, however then I found that just as there’s nothing to round-trip decompress->compress a squashfs (and have it recreated the same way) there isn’t really anything to recreate a tarball either.

But if I can get away without changing the size of any files, then I can just update them in-place in the tarball without a re-pack. There is plenty of space in inittab, and also plenty of space in /root/.bashrc, the latter is composed mainly of comments in antiX in case you want to ‘comment-in’ various features, so no problem there, inittab with Christophe’s changes results in a smaller file anyway, so just some whitespace padding needed there.

That’s all very well, but I still need to find out the offset of the files I need to modify in the tarball. I did this with a simple string search of the tarball. I’m making the assumption that the inittab and bashrc content doesn’t somehow appear in more than one place in the tarball, but that’s not unreasonable I feel.

Here is the code to do this, in case someone else needs it.

#!/bin/bash

# Name of the antiX core iso of interest.
ISO_NAME=antiX-19.3_x64-core.iso
# Subdirectory where we'll extract the iso - THIS WILL GET CLOBBERED!!!!
EXTRACT_DIR=iso_content

# A python3 script to figure out the offset in a large file where a small file is found.
offset_script="
import sys
small = open(sys.argv[1], 'rb').read()
blocks = 
base = 0
while True:
    base += len(blocks[0])
    del blocks[0]
    blk = sys.stdin.buffer.read(len(small))
    if not blk:
         sys.exit(0)
    blocks.append(blk)
    offset = b''.join(blocks).find(small)
    if offset != -1:
        print(base + offset)
        sys.exit(0)
"

echo "Removing old extraction directory $EXTRACT_DIR"
rm -Rf $EXTRACT_DIR

echo "Extracting ISO..."
xorriso -osirrox on -indev $ISO_NAME -extract / $EXTRACT_DIR

echo "Updating isolinux.cfg for text mode boot and no delays..."
cat << EOFEOFEOF > $EXTRACT_DIR/boot/isolinux/isolinux.cfg

timeout 10
default safe

MENU TITLE Welcome to antiX-19.3_x64-core (Manolis Glezos)

LABEL safe
MENU LABEL Safe_Video_Mode
KERNEL /antiX/vmlinuz
APPEND disable=lx xorg=safe
INITRD /antiX/initrd.gz
EOFEOFEOF

echo "Converting squashfs to tarball..."
sqfs2tar -r . -s $EXTRACT_DIR/antiX/linuxfs > out.tar

echo "Extracting inittab..."
tar xfO out.tar ./etc/inittab > inittab
echo "Finding offset of inittab..."
OFFSET=$(python3 -c "$offset_script" inittab < out.tar)
echo "initab found at $OFFSET in tarball"

echo "Generating new inittab with auto-login enabled..."
# Note:  these two sed strings, the search and replace must be identical sizes, hence the padding in the 2nd string.
cat inittab | sed "s|1:2345:respawn:/sbin/getty --noclear 38400 tty1|1:2345:respawn:/sbin/getty -a root   38400 tty1|" > inittab2

echo "Re-inserting modified inittab into tarball..."
dd if=inittab2 of=out.tar bs=1 seek=$OFFSET conv=notrunc

echo "Extracting tarball /root/.bashrc to bashrc..."
tar xfO out.tar ./root/.bashrc > bashrc
echo "Finding offset of /root/.bashrc..."
OFFSET=$(python3 -c "$offset_script" bashrc < out.tar)
echo "bashrc found at $OFFSET"

LENGTH=$(wc -c bashrc | awk '{print $1}')
echo "bashrc is $LENGTH bytes long"

echo "Generating new bashrc with automation hooks into ISO image"
cat << EOFBASHRC > bashrc2
. /live/boot-dev/setup.sh
EOFBASHRC

echo "Padding bashrc up to original size with whitespace"
LENGTH2=$(wc -c bashrc2 | awk '{print $1}')
TOPAD=$((LENGTH-LENGTH2))
printf "%${TOPAD}s" >> bashrc2

echo "Re-inserting modified bashrc in tarball..."
dd if=bashrc2 of=out.tar bs=1 seek=$OFFSET conv=notrunc

echo "Recreating squashfs from tarball..."
tar2sqfs -q -s -f $EXTRACT_DIR/antiX/linuxfs < out.tar

echo "Add our new setup.sh in the root of the ISO image..."
cat << EOFSETUP > $EXTRACT_DIR/setup.sh
echo "This is an example of running automated setup..."
EOFSETUP

echo "Recreating ISO image..."
cd $EXTRACT_DIR && xorriso -as mkisofs -D -r -J -joliet-long -l -V \
        "Custom antiX core" -b boot/isolinux/isolinux.bin \
        -c boot/isolinux/boot.cat -iso-level 3 -no-emul-boot \
        -partition_offset 16 -boot-load-size 4 \
        -boot-info-table -o ../new_antix.iso .

[Member Xecure]

Thanks for testing seaken64.
Marcelo wasn’t able too get the antiX 19 to boot with the openchrome driver, and the vesa driver on his machine was very slow. He tested also antiX 17, with openchrome and vesa, and it also performed to slow graphically. The only acceptable result was using an antix 16 release.
As he states in the first page, he has had trouble with the newer xorg version released in Debian buster, and has been trying different linux distros.
We weren’t sure how to get the newer versions of antiX to work on his machines, so I tried with the lowest supported antiX kernel and with the xorg version in antiX 16. This is what lead to me trying to build it using the build-iso tool created by anticapitalista and co.

If your experience is almost the same between normal antiX and this version, then there is hope that there is no need for what I am trying to do and there is a better workaround, which we may find may also work on marcelocripe’s old machines.

seaken64 wrote:

Network:
Device-1: Broadcom Limited BCM4318 [AirForce One 54g] 802.11g Wireless LAN
driver: b43-pci-bridge

My guess is that you used Network Assistant to unblacklist the b43 broadcom drivers on your antiX 19.1 installation, and that is why wifi works on your system. But maybe I have made some mistake and blacklisted drivers that are available on the default antiX 19 version. I experimented with editing many files, but I don’t remember touching modprobe files, but I can entirely be to blame for this. Sorry for that.

If linuxdaddy’s discovery of using the xorg version in Debian Testing/sid for getting SIS video chips to work properly also applies to marcelocripe’s case, then it would be even better. Hopefully Debian is working on keeping and maintaining old hardware working, and I was completely wrong. Debian Bullseye may be a better release compared to buster and bring back life to old systems. Let us hope.

Again, thanks for testing. This has been a learning experience for me. If on the next iso based on testing I send to marcelocripe works on his machines, we can say that these tests were worth it.

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

[Member seaken64]

I’ve been reading this thread with interest. Unfortunately, I don’t think I grasp everything. I understand that Marcelocripe has some old machines that don’t work well with the standard antiX-19 and that Xecure has been trying to provide an alternate iso that may work better on those machines. One approach was to replace the Xorg package with the package from antiX-16, is that correct? I’ve never quite got a handle on how all of this works, but will an older Xorg package continue to work with other programs that may require a dependency on the current Xorg files? Maybe a desktop environment or video editor, or something like that?

For what it is worth, I have one laptop that use the VIA Graphics. So far, I have been able to use this machine in antiX-16, antiX-17, and antiX-19 with no problems. It always uses the OpenChrome driver for Xorg and I am able to use the default screen size of 1280×768. I’ve had no video problems with the apps that I use, such as SMTube or Streamlight, or mpv, or VLC, etc. Apparently marcelocripe has different chips and get different results. I have another system that uses an Intel integrated graphics chip that was not supported and I had to get help from BitJam and others on this forum to set it up with the GUI. So I understand that sometimes the video does not get setup correctly from the standard iso download. But if I recall I only had to force an install of an alternate driver module. Apparently this is not always the case and no driver will solve the problem. In these cases is it a combination of the kernel, Xorg, and drivers? Is it that the driver files have not been maintained to support the newer Xorg and/or kernel?

I also have a keen interest in keeping old computers alive and out of the trash. I hope I can learn how all of these parts of the puzzle fit together so I can contribute to efforts such as those on display here in this forum. If marcelocripe and xecure are successful in getting marcelocripes computers working with antiX-19 it will go a long way toward all of us learning how to massage linux to our own goals. I only have this one laptop that uses the VIA graphics but if my testing will help I will do what I can.

I downloaded the legacy-bet1 iso file that xecure provided and booted it on this Gateway MX3210 laptop, which uses the VIA graphics chipset. It booted to the GUI with no problem and inxi shows the OpenChrome driver for Xorg. But the WiFi does not work. I compared the inxi to the previously installed antiX-19.1 which has been fully upgraded as of today. The graphics driver is the same with the correct resolution for this laptop on both. I’ll paste the inxi output below.

Also, it seems to me that a working WiFi is at least as important as a working graphics. Maybe this beta1 test is only focused on the graphics for now? and the WiFi will be working later?

Thank you all for you hard work. This has always been one of my favorite things about antiX. antiX developers and users appreciate that an old piece of equipment still has some value, even if only to a small handful of the world’s computer users.

Seaken64

Here’s the inxi outputs. The first is the beta1 test on a LiveUSB, the second is my installed and current antiX-19 on the hard drive.

$ inxi -Fxz
System:
  Host: antix1 Kernel: 4.4.240-antix.2-486-smp i686 bits: 32 compiler: gcc 
  v: 8.3.0 Desktop: IceWM 1.9.2 
  Distro: antiX-19-legacy-bet1_386-base Lazarus 23 November 2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Portable System: Gateway product: MX3210 v: 73.03 serial: <filter> 
  Mobo: Gateway model: N/A v: Rev1.73.03 serial: <filter> BIOS: Phoenix 
  v: 73.03 date: 01/06/2006 
Battery:
  ID-1: BAT0 charge: 20.9 Wh condition: 21.1/48.8 Wh (43%) 
  model: Gateway W32044L status: Charging 
CPU:
  Topology: Single Core model: Intel Celeron M bits: 32 type: MCP 
  arch: M Dothan rev: 8 L2 cache: 1024 KiB 
  flags: pae sse sse2 bogomips: 2793 
  Speed: 1397 MHz min/max: N/A Core speed (MHz): 1: 1397 
Graphics:
  Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] 
  vendor: Gateway driver: N/A bus ID: 01:00.0 
  Display: x11 server: X.Org 1.16.4 driver: openchrome 
  unloaded: fbdev,modesetting,vesa resolution: 1280x768~60Hz 
  OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6 
  direct render: Yes 
Audio:
  Device-1: VIA VT8233/A/8235/8237 AC97 Audio vendor: Gateway 
  driver: snd_via82xx v: kernel bus ID: 00:11.5 
  Sound Server: ALSA v: k4.4.240-antix.2-486-smp 
Network:
  Device-1: Broadcom Limited BCM4318 [AirForce One 54g] 802.11g Wireless LAN 
  driver: N/A bus ID: 00:0e.0 
  Device-2: VIA VT6102/VT6103 [Rhine-II] vendor: Gateway driver: via-rhine 
  v: N/A port: 1800 bus ID: 00:12.0 
  IF: eth0 state: down mac: <filter> 
Drives:
  Local Storage: total: 44.72 GiB used: 789.2 MiB (1.7%) 
  ID-1: /dev/sda vendor: Hitachi model: HTS424040M9AT00 size: 37.26 GiB 
  ID-2: /dev/sdb type: USB vendor: Lexar model: USB Flash Drive 
  size: 7.46 GiB 
Partition:
  ID-1: / size: 364.0 MiB used: 2.2 MiB (0.6%) fs: overlay source: ERR-102 
  ID-2: swap-1 size: 896.0 MiB used: 52 KiB (0.0%) fs: swap dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 56.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 114 Uptime: 4m Memory: 479.1 MiB used: 98.2 MiB (20.5%) 
  Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 
  inxi: 3.0.36 

$ inxi -Fxz
System:
  Host: 3210antix19 Kernel: 4.9.200-antix.1-486-smp i686 bits: 32 
  compiler: gcc v: 8.3.0 Desktop: IceWM 1.9.2 
  Distro: antiX-19.1_386-base Marielle Franco 23 December 2019 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Portable System: Gateway product: MX3210 v: 73.03 serial: <filter> 
  Mobo: Gateway model: N/A v: Rev1.73.03 serial: <filter> BIOS: Phoenix 
  v: 73.03 date: 01/06/2006 
Battery:
  ID-1: BAT0 charge: 20.9 Wh condition: 21.1/48.8 Wh (43%) 
  model: Gateway W32044L status: Charging 
CPU:
  Topology: Single Core model: Intel Celeron M bits: 32 type: MCP 
  arch: M Dothan rev: 8 L2 cache: 1024 KiB 
  flags: pae sse sse2 bogomips: 2793 
  Speed: 1397 MHz min/max: N/A Core speed (MHz): 1: 1397 
Graphics:
  Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] 
  vendor: Gateway driver: N/A bus ID: 01:00.0 
  Display: x11 server: X.Org 1.20.4 driver: openchrome 
  unloaded: fbdev,modesetting,vesa resolution: 1280x768~60Hz 
  OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 
  direct render: Yes 
Audio:
  Device-1: VIA VT8233/A/8235/8237 AC97 Audio vendor: Gateway 
  driver: snd_via82xx v: kernel bus ID: 00:11.5 
  Sound Server: ALSA v: k4.9.200-antix.1-486-smp 
Network:
  Device-1: Broadcom Limited BCM4318 [AirForce One 54g] 802.11g Wireless LAN 
  driver: b43-pci-bridge v: N/A bus ID: 00:0e.0 
  Device-2: VIA VT6102/VT6103 [Rhine-II] vendor: Gateway driver: via-rhine 
  v: N/A port: 1800 bus ID: 00:12.0 
  IF: eth0 state: down mac: <filter> 
  IF-ID-1: wlan0 state: up mac: <filter> 
Drives:
  Local Storage: total: 44.72 GiB used: 4.69 GiB (10.5%) 
  ID-1: /dev/sda vendor: Hitachi model: HTS424040M9AT00 size: 37.26 GiB 
  ID-2: /dev/sdb type: USB vendor: Lexar model: USB Flash Drive 
  size: 7.46 GiB 
Partition:
  ID-1: / size: 7.65 GiB used: 3.92 GiB (51.2%) fs: ext4 dev: /dev/sda7 
  ID-2: swap-1 size: 896.0 MiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 51.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 128 Uptime: 2m Memory: 477.3 MiB used: 90.6 MiB (19.0%) 
  Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 
  inxi: 3.0.36 

[Member Xecure]

Anonymous wrote:

did an experiment and
apparently it is a problem only with buster version of xorg. this
is a sid/bullseye core build up and it works in 16 bit and 24 bit
with no icon disappearing problem.

This means that (probably) building an iso for testing with the new xorg version instead of trying to hold the old xorg package from jessie is a better path.
Then this will probably be the last iso I build, as this will become a fruitless endeavor if newer xorg versions fix the issues with SIS and VIA video cards.

It is good news for the future of old machines. Less work for reviving them. This was going to be the next beta2 iso (740MB, autologin, semifix to virtualbox video, removed the firmware, included some of skidoo’s suggestions, added synaptic, could not get a good way to setup xorg.conf automatically that worked, so this will not be included), but I will next try to build an iso with bullseyes repos to see if it will boot for marcelocripe.

Thanks for all the tests, linuxdaddy. It lead to a possible better path than keeping an alternative separate version with low support.

Thank you everyone for participating. This was a learning experience for me.

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