Search Results for 'boot from iso'

Is there a way to boot Antix 21 live with grub4dos?

I mounted the .iso, and copied the files to /antix64_21 on a vfat thumb drive which also boots other live distros including Antix 19.3.

The relevant section of the grub4dos menu.lst:

title Antix 21.0 (antix64_21)
find –set-root –ignore-floppies –ignore-cd /antix64_21/antiX/initrd.gz
kernel /antix64_21/antiX/vmlinuz disable=lxF
initrd /antix64_21/antiX/initrd.gz

This method works with Antix 19.3, but not with Antix 21.0.

I get the following message during boot:

Non-Fatal Error
Kernel version mismatch
Kernel version 4.9.0-279-antix.1=amd64-smp
The module directory /live/linux/lib/modules/4.9.0-279-antix.1=amd64-smp is missing
c = continue
p = power off
r – reboot

Selecting c continues the boot with a note about “using Vesa driver.”

Xwin starts but isn’t usable. See attached photo.

Hardware: Thinkpad T400, non-UEFI, using integrated Intel graphics.

Thanks!

• This topic was modified 1 year, 3 months ago by anticapitalista. Reason: solved

Attachments:

1. 

   antix.jpg
   

[Member roland]

I have now noticed that these error messages are sometimes produced during the boot of antiX, and are mixed up with the routine progress and advisory messages coming from the various stages of the boot. Does this perhaps signify that they are being produced by the bios? Maybe it I make selected changes to certain bios settings I can throw more light on things?

[Member marcelocripe]

Hello dear.

Another computer with a Via graphics card (Gigabyte GA-VM900M motherboard) dear was “revived” with the ISO “pseudo-antiX-19-legacy-bet3_x64.iso”. It was necessary to boot into secure video mode.

Thank you very much Xecure.

– – – – –

Olá caros.

Mais um computador com placa de vídeo Via (placa-mãe Gigabyte GA-VM900M) foi “revivido” com a ISO “pseudo-antiX-19-legacy-bet3_x64.iso”. Foi necessário inicializar no modo de vídeo seguro.

Muito obrigado Xecure.

After installing and updating antiX:
Após a instalação e atualização do antiX:

maria@antix:~
$ inxi -Fnz
System:
Kernel: 4.4.0-264-antix.1-amd64-smp x86_64 bits: 64 Desktop: IceWM 2.9.1
Distro: pseudo-antiX-19-legacy-bet3_x64 Lazarus 27 junio 2021
Machine:
Type: Desktop System: Gigabyte product: GA-VM900M v: N/A serial: <filter>
Mobo: Gigabyte model: VM900M serial: <filter> BIOS: Award v: F5
date: 05/02/2007
CPU:
Info: Single Core model: Intel Celeron 420 bits: 64 type: MCP cache:
L2: 512 KiB
Speed: 1608 MHz min/max: N/A Core speed (MHz): 1: 1608
Graphics:
Device-1: VIA CN896/VN896/P4M900 [Chrome 9 HC] driver: N/A
Display: x11 server: X.Org 1.16.4 driver: loaded: vesa
resolution: 1280×1024
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6
Audio:
Device-1: VIA VT8237A/VT8251 HDA driver: snd_hda_intel
Sound Server-1: ALSA v: k4.4.0-264-antix.1-amd64-smp running: yes
Network:
Device-1: VIA VT6102/VT6103 [Rhine-II] driver: via-rhine
IF: eth0 state: unknown speed: 100 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 163.61 GiB used: 14.13 GiB (8.6%)
ID-1: /dev/sda vendor: Samsung model: HD161GJ size: 149.05 GiB
ID-2: /dev/sdb type: USB vendor: Generic model: Flash Disk size: 14.56 GiB
Partition:
ID-1: / size: 39.12 GiB used: 3.74 GiB (9.6%) fs: ext4 dev: /dev/sda1
ID-2: /home size: 102.9 GiB used: 10.39 GiB (10.1%) fs: ext4
dev: /dev/sda2
Swap:
ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) dev: /dev/sda3
Sensors:
System Temperatures: cpu: 49.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 138 Uptime: 24m Memory: 2.2 GiB used: 234.7 MiB (10.4%)
Shell: Bash inxi: 3.3.06
maria@antix:~
$

[Member olsztyn]

Thank you newmant1…
I am starting simple. Partition is MS-DOS.

newmant1 wrote:

You posted a good question that i had in mind, so why is it there when the bootup does not use? for efi configuration? which stated must be Fat32 and was labelled /boot or need to change to /efi-boot when configuring in some other linux distro?

From my experiment, which was to test whether the small 49M Fat32 ANTIX-UEFI partition plays any role, it appears to me that there in antiX world (I would venture to say in Linux world) it does not play any role. I have put the EFI boot files on the main (the only) partition and the resulting antiX live happily boots on my MBR and UEFI laptops.
My conjecture was that perhaps the small Fat32 partition in antiX Live was for some compatibility with Windows UEFI, but on the other hand I really do not see any possibility of Windows being installed on USB stick along with antiX Live, so that seems to be out of picture, so perhaps such partition configuration is some remnant from the past?…
So unless a reason for this small 49M Fat32 partition is found, why not keep it simple and at least to provide an option in Live-USB-Maker and ISO-Snapshot to configure antiX Live as one partition?

• This reply was modified 1 year, 5 months ago by olsztyn.

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

[Member Robin]

Hello all, I’ll be back on this task this evening. Sorry for the delay in answering, first I had to complete the writing of script code for automatic translation of anitX desktop files to the languages we cover, which have no real translators by now, and also I had to check for the unplugdrive woes of antiX 21 version which was heavily modified last minute from 0.91 to 0.93. Xecure did a great job in acceleration of processing performed by unplugdrive, but there was no time left for testing it as extensively as I did while I have written the 0.91 version, on all kinds of devices before it went into the ISO. So we face now the absurd situation we have a well tested 0.91 (slow and sudo) version in the archives, and a mostly untested 0.93 (fast sudo+nonsudo) version in antiX 21 🙂
But back to my antiX Live USB struggles.

May be I still not reached at the bottom of reasons for syslinux not seeing the existing config files at boot time. I copied the files from within true Win2000 to the stick, which should write the correct 8.3 filenames. But still syslinux won’t see the config files.

My next approach was to copy the complete content of ../boot/syslinux subfolder to the root of the USB stick, even if they write in their manual syslinux would check the ../boot/syslinux and ../syslinux folder BEFORE checking the root directory for the config. Surprise: Now syslinux comes up all of a sudden with the antiX 21 boot screen. What the heck? I really don’t see the logical reasoning behind this, since the original config of antiX 17.4.1 was also located in the very subfolder, not in the root. So first (partly) success: I can boot the stick on this PC now and I saw the antiX 21 boot screen the first time. The localised F1 help looks great, @anticapitalista you did a great job with allowing the help menu to be localised now. This makes antiX usable to many more people all over the world. Many thanks for what you do for all of us!

OK, but now back to the LiveUSB. Again the strange “file/folder not found” message hit me, this time /antiX/vmlinuz file is not found while it is actually present in this folder. Slowly but surely I’m fed up to the back teeth by this stupid message. The files ARE present in the directories.

Btw: Doesn’t mean syslinux “sees” the files when they sit in USB root, that all the filenames fine, and merely all new folders are “invisible”?

Just an idea… Since this is a MS-DOS style file system, does syslinux possibly expect the slashes to be written the other way around in its config file now for some strange reason? I mean \ instead of / ? But why does all this work flawlessly in the original 17.4.1 stick then, trouble starting the minute a folder is created new? It must be somehow interdepend on the way how the folder and file names are written to the file system. I have not tried to do this on true old school MS-DOS instead of antiX or Win2000, maybe this would make a difference. Once we have understood WHAT exactly prevents syslinux from seeing the folders at boot time, we can try to treat it while creating the stick from within antiX…

@seaken64 Many thanks for your warnings. But I’m well secured, there is a 1:1 backup hdd, function tested and ready to plug, and in case something unexpected happens to the CAD station, it is a task of 10 minutes max only to make it run again exactly as before. Just switch the cables within the PC case from the hdd in the one slot to the spare hdd in the other slot. Moreover all local user data is stored on external USB drives, internal hdd containing the pure OS and CAD system only. I won’t install antiX on this PC, it is to be run from persistent Live USB stick exclusively, and antiX is meant for allowing external data exchange on this machine, while I wouldn’t never ever let it connect to network or internet when running it on its outdated Windows, Microsoft not providing any security updates anymore and not being able to offer a functioning replacement version of their OS running on this hardware.

Windows is like a submarine. Open a window and serious problems will start.

[Member olsztyn]

Robin wrote:

This is at least the answer to the strange haunting and vanishing of files and directories when moved and renamed using antiX (or any linux) on a vfat file system. The 8.3 filename won’t get written at all to disk, so clear chain of reasoning is syslinux can’t find them on boot. So I’d state the linux vfat kernel driver is considered as broken actually. I’d only like to come to know how the guys from unetbootin have managed this once when I created my very first antiX stick on ubuntu…

I must say this is very interesting, unexpected scenario. I would have never figured this out… So congrats on discovering this…
Very curious how this was correctly created via Unetbootin on Ubuntu. And if Live-USB-Maker created the boot partition (49M) as Fat16 instead of Vfat, whether files would be written out correctly. Or if instead of 64Gb Fat32 partition to compose such antiX21 stick the first partition to contain antiX boot files is set up as Fat16 (4Gb) instead of Vfat. This means whether this would make a difference in behavior of driver.

However you will end up resolving this puzzle, I trust you will find an easier solution than using old MS DOS…
This scenario however brings up an idea to build-in more options into Live-USB-Maker and ISO Snaphot, to be able to specify a file systems and partitioning scheme when creating antiX Live, such as whether to use the Vfat 49Gb ANTIX_UEFI partition or make it a one-partition system, and what file system to use…
I hope antiX team and owner reads these posts and for me personally your experience and discovery of this phenomenon is a great lesson to learn…

• This reply was modified 1 year, 5 months ago by olsztyn.

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

[Member Robin]

@olsztyn per your request:

Original 17.4.1, boots fine:

#--------------------------------------------------------------------
# This is the isolinux.cfg and/or syslinux.cfg file
# It controls the main menu in the bootloader on the live system.
# You can edit it to change the main bootloader menu on a LiveUSB.
# If you are not careful you can break the live system and prevent
# it from booting.
#--------------------------------------------------------------------

UI gfxboot gfx-cpio readme.msg
timeout 3000

default live

MENU TITLE Welcome to antiX-17.4.1_386-full (Helen Keller)

LABEL live
    MENU LABEL antiX-17.4.1_386-full (28 March 2019)
    KERNEL /antiX/vmlinuz
    APPEND quiet splash=v disable=lx
    INITRD /antiX/initrd.gz

LABEL safe
    MENU LABEL Safe_Video_Mode
    KERNEL /antiX/vmlinuz
    APPEND quiet splash=v disable=lx nomodeset xorg=safe
    INITRD /antiX/initrd.gz

LABEL failsafe
    MENU LABEL Failsafe_Boot
    KERNEL /antiX/vmlinuz
    APPEND quiet splash=v disable=lx nomodeset failsafe
    INITRD /antiX/initrd.gz

LABEL harddisk
    MENU LABEL Boot_from_Hard_Disk
    COM32 chain.c32
    APPEND hd1

LABEL memtest
    MENU LABEL Memory_Test
    KERNEL /boot/memtest

Replacement from antiX 21, refuses to work. But as explained in the posting before, this is caused by missing 8.3 filenames when writing these files from within antiX to the fat32 boot medium, not by this file or its content itslf. It also fails when creating a fresh 1:1 copy of the original 17.4.1 syslinux.cfg file as shown above using the same correct file name in the very folder.

#--------------------------------------------------------------------
# This is the isolinux.cfg and/or syslinux.cfg file
# It controls the main menu in the bootloader on the live system.
# You can edit it to change the main bootloader menu on a LiveUSB.
# If you are not careful you can break the live system and prevent
# it from booting.
#--------------------------------------------------------------------

UI gfxboot gfx-cpio readme.msg
timeout 3000

default

MENU TITLE Welcome to antiX-21_386-full (Grup Yorum)

LABEL live
    MENU LABEL antiX-21_386-full (31 October 2021)
    KERNEL /antiX/vmlinuz
    APPEND quiet splasht disable=lxF
    INITRD /antiX/initrd.gz

LABEL safe
    MENU LABEL Safe_Video_Mode
    KERNEL /antiX/vmlinuz
    APPEND quiet splasht disable=lxF xorg=safe
    INITRD /antiX/initrd.gz

LABEL failsafe
    MENU LABEL Failsafe_Boot
    KERNEL /antiX/vmlinuz
    APPEND quiet splasht disable=lxF failsafe
    INITRD /antiX/initrd.gz

LABEL harddisk
    MENU LABEL Boot_from_Hard_Disk
    COM32 chain.c32
    APPEND hd1

LABEL memtest
    MENU LABEL Memory_Test
    KERNEL /boot/memtest

LABEL grub
    MENU LABEL Switch_to_Grub_Bootloader
    KERNEL /boot/grub/i386-pc/lnxboot.img
    INITRD /boot/grub/i386-pc/core.img

olsztyn wrote:

as I am quite confused how exactly it works with separate partitions

From reading this text you’ll probably get an idea how all this works in detail. All syslinux boot stages are described, and how they depend on each other. Also what which file is good for.

Windows is like a submarine. Open a window and serious problems will start.

[Member aluthier]

I know there is a linux compatible driver, because I originally tried live booting Ubuntu but it was horribly slow in comparison to the insanely fast AntiX on this little guy. How do y’all solve missing driver issues?

[Member dirkd]

The edition of runit antix 21 was specified in full — I think?? I did forget to mention the desktop: plain fluxbox.

I didn’t change any setting in antixcc/automount (see attached screenshot). These are the same settings as in Antix17.

I don’t ‘blame’ zzzFM, just saying there’s a connection. And sorry if I’m not exactly aware of the whole chain of processes involved when mounting a DVD or CD. When it ‘works’, in Antix17, I can change CD’s, DVD’s, they are unmounted and mounted in /media/sr0. In Antix21, this folder is not created automatically as happens when mounting a USB stick. If the folder is absent, I get an error message from Mount (2nd attachment). When I make the folder /media/sr0 myself (as root), I can insert a CD, DVD, just once, and it is mounted there correctly. After opening the tray, it won’t stay closed afterwards, so no optical disk can be mounted anymore.

These are the lines in /etc/fstab pertaining to the CD drive (where ‘mount’ ignores the options from):

/dev/cdrom                    /media/cdrom             iso9660    noauto,exec,user,ro            0 0
/dev/sr0                      /media/sr0               iso9660    noauto,exec,user,ro            0 0

The CD-rom drive remains in this state, even after logoff/login. To mount another CD/DVD I need to disconnect it from the USB ports, or reboot. No idea what I could try to remedy this.

• This reply was modified 1 year, 5 months ago by dirkd.
• This reply was modified 1 year, 5 months ago by dirkd.

Attachments:

1. 

   antixcc.jpg
   

2. 

   Mount-message.jpg
   

[Member olsztyn]

christophe wrote:

What about making a legacy-only boot usb using extlinux?

Thanks you brought this methodology up… I remember that following your publishing this I played a lot with your extlinux way and it worked for me very well, although that was on hard disk.
In relation to Robin’s case, I checked my three desktops (all older desktops), which I have not been used for some time as all I do is on laptops now, and all three have the same issues as Robin described… In those times desktops typically provided booting capability from USB in FDD, CDD or HDD emulation but not ‘removable USB media’ mode.
Robin’s post brought back my memories that my failing to make Live antiX boot on those desktops, except flipping boot emulation bit on my old HP (only 4Gb) sticks, made me let those desktops sit in storage useless. All I have been using since are laptops, somewhat newer that those desktops, all booting fine from removable media.
Such deficiency of old desktops (many really old laptops too) is mitigated to some degree by the fact they typically have DVD drive, and considering many antiX users are actually installing to HD not booting Live from USB, this issue has not been widely brought up.
However the interesting (and very valid) point Robin is bringing up is that it is not that such desktop is not capable of booting from USB removable media, as proved by one created with Unetbootin, which boots fine in one of boot emulation mode, but that antiX Live fails to boot in any of those modes.

So the general question was posed – what is the difference between Unetbootin and antiX live boot architecture that makes booting successful for Unetbootin and not so for antiX on such older desktops. And how antiX Live boot can be made successful.
I am very curious myself. Not for the sake of those old desktops sitting in storage, but to make antiX Live boot more capable – more universal, that would boot on more hardware.

Yesterday I was trying to test the suggestion from dolphin_oracle to Live-USB-Make a read only (dd mode) one-partition stick, just for testing if such one-partition antiX Live would boot one my old desktops, but so far Live-USB-Maker fails with an error. Whenever I chose ‘Clone running system’ and select dd mode, the’clone’ blanks out, starts partitioning USB media and then fails with an error.
I will try to do ISO snapshot instead and then attempt dd mode from ISO snapshot. This is just an experiment for me but may shed some light on answer to Robin’s partition question, as the cause of not booting…

• This reply was modified 1 year, 5 months ago by olsztyn.

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

I just learned this week that a new version of AntiX was released. I installed the Antix-21 64-bit Runit version with a 5.10 kernel on my main machine, in parallel with my previous Antix-17.4 environment. I was very impressed, in that (almost) everything I use worked right out of the box. I never managed to get AntiX-19 to work with a 5.10 kernel, which I need to support my relatively new hardware, but this time I was lucky. I was particularly happy to learn that SpaceFM still ships with AntiX, be it in a new incarnation. I would hate to switch to another filemanager after all these years, so thank you, Skidoo!

Some small problems I encountered:

(1) The new login screen doesn’t let you go back to the ‘username’ field after you press enter. That would be nice for fixing the occasional typing error. It doesn’t react to mouse clicks, but maybe this is normal. If everything else is fine, it could use a little esthetic cleaning up. These gargantuan fonts, yech. Again, there may be a reason for that (users with very high resolution screens?). It also mentions the <F1>-key to change session type twice in two different fonts (with and without serifs!). Surely once is enough.

(2) Connman. Worked just fine on the live USB, and I could connect to my network more or less easily. But after installing to the harddisk it messed up the boot process. After the message ‘udev: waiting for being fully populated’ (or something like that) my screen went black and the computer seemed to hang up completely. Enough to scare away a first time user I guess. Luckily I thought about switching to the <F1> console. There I saw an almost endless repeat of the message ‘No protocol specified’ (or something like that). I presumed it was Connman trying to connect to the wifi. After (many!) minutes, if finally gave up, and I could complete the login process. Switching to Ceni for network management solved that problem.

(3) Package manager. This is a known problem, apparently. LaTeX full didn’t install. I used Synaptic instead. After updating I *could* install LaTeX with the package manager, but only after first removing all latex packages I had already added with Synaptic. The interplay between Synaptic and the Package Manager is still somewhat mysterious to me.

(4) Synaptic is absent from the fluxbox menu. Sure, I can start it from the Control Centre, but I’m used to find it under the ‘System’ menu. I *thought* I knew how fluxbox decides which apps it put in the menu (I thought it was decided by the ‘Categories’ entry in the .desktop file), but apparently I’m wrong. So can I get Synaptic back in the menu? And how?

(5) Conky. I use fluxbox as window manager, with a different wallpaper for each desktop. The method I use to switch wallpapers calls for Conky-std in stead of Conky-legacy, which is installed by default. But Conky 1.11 complains about syntax errors in the .conkyrc configuration file. I solved this by installing an older Conky-std 1.10 from my Antix-17 environment. But I would prefer to use the standard version from the repos, if possible.

(6) Fluxbox-minimal session. When choosing a fluxbox-minimal session, fluxbox refuses to use the ‘startup’ configuration file. It makes a new one on its own (and thus makes me loose some customisations I made), and renames the old one to ‘startup.disabled’. Using a normal ‘Fluxbox’ session works fine, so apparently there is nothing wrong with the ‘startup’ file. I tested if Antix-17 has the same problem. To my surprise it refused to start a fluxbox-minimal session! (I forgot the precise error message – ‘Unable to handle startup request’ or something like that), but I *could* switch to ‘fluxbox-minimal’ desktop, after first starting a normal ‘fluxbox’ session.

============================================================================
My hardware:

$ inxi -Fxz
System:
Kernel: 5.10.57-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 10.2.1
Desktop: Fluxbox 1.3.7
Distro: antiX-21-runit_x64-full Grup Yorum 30 October 2021
base: Debian GNU/Linux 11 (bullseye)
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <filter>
Mobo: ASUSTeK model: TUF GAMING B550-PLUS (WI-FI) v: Rev X.0x
serial: <filter> BIOS: American Megatrends v: 1004 date: 08/13/2020
CPU:
Info: 6-Core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2
rev: 0 cache: L2: 3 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 86242
Speed: 3590 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz):
1: 3590 2: 3596 3: 3678 4: 3452 5: 3592 6: 3580 7: 3766 8: 3506 9: 3587
10: 3589 11: 3597 12: 3498
Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] vendor: Gigabyte driver: nouveau
v: kernel bus-ID: 06:00.0
Display: server: X.Org 1.20.11 driver: loaded: modesetting
unloaded: fbdev,vesa resolution: 1280×1024~60Hz
OpenGL: renderer: NV106 v: 4.3 Mesa 20.3.5 direct render: Yes
Audio:
Device-1: NVIDIA GK208 HDMI/DP Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel bus-ID: 06:00.1
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 08:00.4
Sound Server-1: ALSA v: k5.10.57-antix.1-amd64-smp running: yes
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus-ID: 04:00.0
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
port: f000 bus-ID: 05:00.0
IF: eth0 state: down mac: <filter>
Bluetooth:
Device-1: Intel type: USB driver: btusb v: 0.8 bus-ID: 1-5:2
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0
lmp-v: 5.1
Drives:
Local Storage: total: 6.29 TiB used: 1.77 TiB (28.2%)
ID-1: /dev/sda vendor: Samsung model: HD753LJ size: 698.64 GiB
ID-2: /dev/sdb vendor: Seagate model: ST2000VN004-2E4164 size: 1.82 TiB
ID-3: /dev/sdc vendor: Western Digital model: WD20EZRZ-00Z5HB0 size: 1.82 TiB
ID-4: /dev/sdd vendor: Western Digital model: WD20EZRZ-00Z5HB0 size: 1.82 TiB
ID-5: /dev/sde vendor: Intel model: SSDSA2CT040G3 size: 37.27 GiB
ID-6: /dev/sdf vendor: Kingston model: SV300S37A120G size: 111.79 GiB
Partition:
ID-1: / size: 85.96 GiB used: 9.94 GiB (11.6%) fs: ext4 dev: /dev/sdf1
ID-2: /home size: 21.41 GiB used: 4.45 GiB (20.8%) fs: ext4 dev: /dev/sdf3
Swap:
ID-1: swap-1 type: partition size: 2.02 GiB used: 0 KiB (0.0%) dev: /dev/sdf2
Sensors:
System Temperatures: cpu: 43.0 C mobo: N/A gpu: nouveau temp: 41.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 286 Uptime: 1h 37m Memory: 15.58 GiB used: 1.15 GiB (7.4%)
Init: runit runlevel: 2 Compilers: gcc: 10.2.1 Packages: 1869 Shell: Bash
v: 5.1.4 inxi: 3.3.06
=================================================================================

My .conkyrc-file (with some comments removed):

# set to yes if you want Conky to be forked in the background
background yes

short_units yes

cpu_avg_samples 1
net_avg_samples 1

out_to_console no

# X font when Xft is disabled, you can pick one with program xfontsel
#font 7×12
#font 6×10
#font 7×13
font 8×12
#font 7×12
#font *mintsmild.se*
#font -*-*-*-*-*-*-34-*-*-*-*-*-*-*
#font -artwiz-snap-normal-r-normal-*-*-100-*-*-p-*-iso8859-1

# Use Xft?
use_xft yes

# Xft font when Xft is enabled
#xftfont gentium:size=12
#ftfont DejaVu Sans:size=10
xftfont DejaVu Sans:bold:size=9
#xftfont DejaVu Sans:size=9

# Create own window instead of using desktop (required in nautilus, pcmanfm and rox desktops)
own_window no
own_window_transparent yes
own_window_hints undecorated,sticky,skip_taskbar

# Text alpha when using Xft
xftalpha 1.0

#on_bottom no

# mail spool
mail_spool $MAIL

# Update interval in seconds
update_interval 1

# Use double buffering (reduces flicker, may not work for everyone)
double_buffer yes

# Minimum size of text area
minimum_size 5 5
maximum_width 180

# Draw shades?
draw_shades no

# Draw outlines?
draw_outline no

# Draw borders around text
draw_borders no

# Stippled borders?
stippled_borders 0

# border margins
#border_margin 10

# border width
border_width 2

# Default colors and also border colors
default_color white
default_shade_color white
default_outline_color white

color2 ffffff
color3 ff0000
color4 yellow
color8 0044aa
color9 2266cc

# Text alignment, other possible values are commented
alignment top_left
#alignment top_right
#alignment bottom_left
#alignment bottom_right

# Gap between borders of screen and text
gap_x 10
gap_y 30

# Add spaces to keep things from moving about? This only affects certain objects.
use_spacer right

# Subtract file system buffers from used memory?
no_buffers yes

# if_up_strictness link: up | link | address
if_up_strictness address

# set to yes if you want all text to be in uppercase
uppercase no

# boinc (seti) dir
# seti_dir /opt/seti

# Possible variables to be used:
#
# Variable Arguments Description
# acpiacadapter ACPI ac adapter state.
# acpifan ACPI fan state
# acpitemp ACPI temperature.
# adt746xcpu CPU temperature from therm_adt746x
# adt746xfan Fan speed from therm_adt746x
# battery (num) Remaining capasity in ACPI or APM
# battery. ACPI battery number can be
# given as argument (default is BAT0).
# buffers Amount of memory buffered
# cached Amount of memory cached
# color (color) Change drawing color to color
# cpu CPU usage in percents
# cpubar (height) Bar that shows CPU usage, height is
# bar’s height in pixels
# downspeed net Download speed in kilobytes
# downspeedf net Download speed in kilobytes with one
# decimal
# exec shell command Executes a shell command and displays
# the output in torsmo. warning: this
# takes a lot more resources than other
# variables. I’d recommend coding wanted
# behaviour in C and posting a patch :-).
# execi interval, shell Same as exec but with specific interval.
# command Interval can’t be less than
# update_interval in configuration.
# fs_bar (height), (fs) Bar that shows how much space is used on
# a file system. height is the height in
# pixels. fs is any file on that file
# system.
# fs_free (fs) Free space on a file system available
# for users.
# fs_free_perc (fs) Free percentage of space on a file
# system available for users.
# fs_size (fs) File system size
# fs_used (fs) File system used space
# hr (height) Horizontal line, height is the height in
# pixels
# i2c (dev), type, n I2C sensor from sysfs (Linux 2.6). dev
# may be omitted if you have only one I2C
# device. type is either in (or vol)
# meaning voltage, fan meaning fan or temp
# meaning temperature. n is number of the
# sensor. See /sys/bus/i2c/devices/ on
# your local computer.
# kernel Kernel version
# loadavg (1), (2), (3) System load average, 1 is for past 1
# minute, 2 for past 5 minutes and 3 for
# past 15 minutes.
# machine Machine, i686 for example
# mails Mail count in mail spool. You can use
# program like fetchmail to get mails from
# some server using your favourite
# protocol. See also new_mails.
# mem Amount of memory in use
# membar (height) Bar that shows amount of memory in use
# memmax Total amount of memory
# memperc Percentage of memory in use
# new_mails Unread mail count in mail spool.
# nodename Hostname
# outlinecolor (color) Change outline color
# pre_exec shell command Executes a shell command one time before
# torsmo displays anything and puts output
# as text.
# processes Total processes (sleeping and running)
# running_processes Running processes (not sleeping),
# requires Linux 2.6
# shadecolor (color) Change shading color
# stippled_hr (space), Stippled (dashed) horizontal line
# (height)
# swapbar (height) Bar that shows amount of swap in use
# swap Amount of swap in use
# swapmax Total amount of swap
# swapperc Percentage of swap in use
# sysname System name, Linux for example
# time (format) Local time, see man strftime to get more
# information about format
# totaldown net Total download, overflows at 4 GB on
# Linux with 32-bit arch and there doesn’t
# seem to be a way to know how many times
# it has already done that before torsmo
# has started.
# totalup net Total upload, this one too, may overflow
# updates Number of updates (for debugging)
# upspeed net Upload speed in kilobytes
# upspeedf net Upload speed in kilobytes with one
# decimal
# uptime Uptime
# uptime_short Uptime in a shorter format
#
# seti_prog Seti@home current progress
# seti_progbar (height) Seti@home current progress bar
# seti_credit Seti@hoome total user credit

## antiX additives examples. Add below Text##
##Battery examples##
##${color}battery: ${color}$acpiacadapter, ${battery_percent BAT1}%
##${color}battery:${color} ${battery}
#${color}ACPI Battery: ${color}$battery
#${battery_bar 11,0}
##Wireless example##
#${color}Wireless:
#${color}essid: ${wireless_essid wlan0}
#${color}IP:${color} ${addr wlan0}
#${color}speed: ${color} ${wireless_bitrate wlan0}
#${color}link strength: ${color} ${wireless_link_bar 7,50 wlan0}

# stuff after ‘TEXT’ will be formatted on screen

TEXT
${color}${alignc}antiX
${color3}$alignc${font DejaVu Sans:size=12}${time %I:%M} $font
${color3}${alignc}${time %a %d %b}
${color}${alignc}${exec disp=${DISPLAY#:}; disp=${disp%.[0-9]}; cat $HOME/.desktop-session/desktop-code.$disp 2>/dev/null}
${color}${alignc}${execi 60 xdpyinfo | sed -n -r “s/^\s*dimensions:.*\s([0-9]+x[0-9]+).*/\1/p”}
${color}${alignc}$kernel
${color}${alignc}Uptime: $uptime

${color}CPU:${alignr}${color}${cpu}${color}%
${color}Freq:${color}${alignr}${freq}
${color}$alignr${cpugraph cpu0 30, 170 888888 2266cc}
${color}Disk:${alignr}${color}${diskio}
${color}${alignr}${diskiograph 30,170 888888 2266cc}
${if_up eth0}${color}eth0 up: $alignr${color} ${upspeed eth0}
${color}$alignr${upspeedgraph eth0 30,170 888888 2266cc}
${color}eth1 down: $alignr${color3} ${downspeed eth0}
${color2}$alignr${downspeedgraph eth0 30,170 888888 2266cc}${endif}
${if_up wlan0}${color}wlan0 up: $alignr${color} ${upspeed wlan0}
${color2}$alignr${upspeedgraph wlan0 30,170 888888 2266cc}
${color}wlan0 down: $alignr${color} ${downspeed wlan0}
${color}$alignr${downspeedgraph wlan0 30,170 888888 2266cc}${endif}

${color}${alignr}${color3}Used / Total
${color}RAM:${alignr}${color3}$mem ${color3} /${color3} $memmax
${color}Swap:${alignr}${color3}$swap ${color3} /${color3} $swapmax
${color}/ Disk:${alignr}${color3}${fs_used /} ${color3} /${color3} ${fs_size /}
${color3}${alignc}${execi 1000 persist-enabled}
${execi 1000 acpi 2>/dev/null | grep -q . && echo “Batt: “}${execi 10 acpi -b 2>/dev/null | cut -d” ” -f3,4 | sed ‘s/,$//’}

===========================================================================================================================

My fluxbox ‘startup’ file:

# fluxbox startup-script:
#
# Lines starting with a ‘#’ are ignored.

# You can set your favourite wallpaper here if you don’t want
# to do it from your style.
# fbsetbg -l
#
# This sets a black background
# /usr/bin/fbsetroot -solid black

# This shows the fluxbox-splash-screen
# fbsetbg -C /usr/share/fluxbox/splash.jpg

# Other examples. Check man xset for details.
# Turn off beeps:
# xset -b
# Increase the keyboard repeat-rate:
# xset r rate 195 35
# Your own fonts-dir:
# xset +fp ~/.font
#
# Your favourite mouse cursor:
# xsetroot -cursor_name right_ptr
#
# Change your keymap:
# xmodmap ~/.Xmodmap

# Eigen aanvullingen Startup apps
# paneltoggle.sh
rox –top=PANEL
xmodmap -e ‘pointer = 3 2 1’
fbxkb &
volumeicon &

# And last but not least we start fluxbox.
# Because it is the last app you have to run it with ”exec” before it.

# exec /usr/bin/fluxbox
# or if you want to keep a log:
exec /usr/bin/fluxbox -log ~/.fluxbox/log

=========================================================================

[Member Robin]

Hotfix update for the display bug is ready:

You may download it from (interim download link) / (future download link, the first valid only until merge to main branch is completed, the latter only afterwards). Make sure you get version 0.93a, you can easily check the version number by calling the script using its -​-​help option once you’ve copied your download to the /usr/local/bin system folder.

Now the final message should look like this again (see screenshots below). The first screenshot is taken from a test with an USB stick not suffering from the bugs described (btw, it’s a cheap »Alcor Micro Corp. Flash« from discounter), the second screenshot is taken with an USB stick having these two bugs I described some posts above (it’s a »JMTek, LLC. Transcend Flash« from specialised store). As you can see, both are assembled as antiX live USB-sticks, but not used as boot medium here so they are unpluggable. I’ve mounted some additional mountpoints (test_11 … test_14) to check the correct display of multiple line entries.

Sorry for the inconvenience, this really should have worked correctly in the version included in the antiX 21 ISO already…

Many greetings
Robin

Attachments:

1. 

   unmounted_01.jpg
   

2. 

   unmounted_02.jpg
   

Windows is like a submarine. Open a window and serious problems will start.

[Member ModdIt]

Solution 1,
Sould be to reinstall from the backup ISO you created before making repo change to testing. :-).

PLEASE, all users before changing repos from Stable to Testing or Unstable make a Backup, put it
on a stick, boot and confirm it works as expected. It is so easy using antiX tools and can save
you a lot of headeache.

You can reinstall and be back at work in a very short time that way.

Present situation now.
If you do not have a backup of home make one, using a live stick copy your data and .files
for your preferred WM to LiveUSB Storage or a second device. Cou can usually also carry over
claws hidden folders, may not work if claws version changed. You can if you wish copy
all contents of home folder, if username stays same it will probably be ok.

You can reinstall keeping home if it is on a separate partition.

Reinstall your antiX version, copy in your saved files from home.
Reinstall your manually installed options with Packet installer Synaptic console according to
your preference.

When you are finished MAKE A SNAPSHOT ISO, put it on a stick confirm it is ok.
Make a backup of that ISO and put it in a safe place.

I always recommend keeping home separate, if you do a semi automated install the installer has a
lider for allocating space to separate home. I have a huge root, about 24GB rest swap and then home on an ssd.
Very easy install.
More complicated with multiple partitions and/or dual boot, use Gparted then the installer seems easiest.

• This reply was modified 1 year, 5 months ago by ModdIt.

[Member marcelocripe]

Hello IoI_xD,

Welcome to antiX Linux and the forum.

I don’t know how to write in English and I send my texts translated by the internet translator.

Regardless of your level of knowledge about GNU/Linux, I recommend you read these excellent tutorials created by @PPC:

Short essential how-to list for the complete Linux newbie and How-to install applications – 2020 version.

You didn’t tell how you boot the antiX iso, but possibly it would make sense to downgrade the kernel to the 4.4 kernel on the iso before.

As suggested by Caprea, you can try using an ISO with a 4.4.0-264 kernel pseudo-antix-19 legacy bet3 (32 bits) which was built by Xecure. For more information, read the topic page How to use antiX on computers with a motherboard with SIS or VIA chipset. I’ve been reviving old computers with antiX since June 2020, but it’s Pentium 4, Celeron or others from this generation onwards. These computers struggle to surf the internet, even though they have 1 GB of DDR technology RAM or more. So, if you can revive your Pentium 2 with only 128MB of RAM memory with antiX, think of a non-internet use, maybe you can use it to produce text and play MS-DOS games with the available DOSBox emulator in the ISO I mentioned. The Mini-Fluxbox or Mini-JWM desktop may be the better choice due to the low amount of RAM memory available. And finally, try to use application programs that are in text mode or CLI.

The topic antiX the best operating system for my P-III can help you.

When you start any topic or participate with any post, remember to check the option “Notify me of follow-up replies via email”, by checking this option you will receive a message in your email inbox whenever there are replies to the topic in question.

marcelocripe
(Original text in Brazilian Portuguese language)

– – – – –

Olá IoI_xD,

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

Eu não sei escrever em idioma Inglês e envio os meus textos traduzidos pelo tradutor da internet.

Independentemente do seu nível de conhecimento sobre GNU/Linux, eu recomendo você ler estes excelentes tutoriais criados pelo @PPC:

Short essential how-to list for the complete Linux newbie e How-to install applications – 2020 version.

You didn’t tell how you boot the antiX iso, but possibly it would make sense to downgrade the kernel to the 4.4 kernel on the iso before.

Conforme foi sugerido pelo Caprea, você pode tentar utilizar uma ISO com kernel 4.4.0-264 pseudo-antix-19 legacy bet3 (32 bits) que foi construída pelo Xecure. Para você obter mais informações, leia a página do tópico How to use antiX on computers with a motherboard with SIS or VIA chipset. Eu venho revivendo computadores antigos com o antiX desde junho de 2020, mas são Pentium 4, Celeron ou outros a partir desta geração. Estes computadores sofrem para navegar na internet, mesmo possuindo 1 GB de memória RAM de tecnologia DDR ou mais. Então, se você conseguir reviver o seu Pentium 2 com apenas 128 MB de memória RAM com o antiX, pense em um uso que não seja à internet, talvez você possa usar para produzir textos e jogar jogos do MS-DOS com o emulador DOSBox disponível na ISO que eu mencionei. A área de trabalho Mini-Fluxbox ou Mini-JWM podem ser as melhores opções devido a baixa quantidade de memória RAM disponível. E por último, tente utilizar os programas aplicativos que sejam em modo texto ou CLI.

O tópico antiX the best operating system for my P-III poderá te ajudar.

Quando você iniciar algum tópico ou participar com alguma postagem, lembre-se de marcar a opção “Notify me of follow-up replies via email”, marcando esta opção, você receberá uma mensagem na sua caixa de e-mail sempre que houver respostas do tópico em questão.

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

[Moderator caprea]

You didn’t tell how you boot the antiX iso, but possibly it would make sense to downgrade the kernel to the 4.4 kernel on the iso before.