Search Results for 'boot from iso'

[Moderator christophe]

Hi, ThakurMsh,

There is more than one version of the current antiX ISO. You have the bare-bones version without a graphical desktop. I would not recommend this for you.

I see you have a nice modern computer. I recommend you download & install this version:

https://sourceforge.net/projects/antix-linux/files/Final/antiX-19/4.19_kernel/antiX-19.3_x64-full.iso/download

It will give you the full antiX experience. This one is easy to use. Just boot up and try it before you install.

• This reply was modified 2 years, 6 months ago by christophe.

confirmed antiX frugaler, since 2019

My respects to all!

th@deb:~$ lscpu
Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
Address sizes:       39 bits physical, 48 bits virtual
CPU(s):              6
On-line CPU(s) list: 0-5
Thread(s) per core:  1
Core(s) per socket:  6
Socket(s):           1
NUMA node(s):        1
Vendor ID:           GenuineIntel
CPU family:          6
Model:               158
Model name:          Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz
Stepping:            10
CPU MHz:             800.102
CPU max MHz:         4100,0000
CPU min MHz:         800,0000
BogoMIPS:            6000.00
Virtualization:      VT-x
L1d cache:           32K
L1i cache:           32K
L2 cache:            256K
L3 cache:            9216K
NUMA node0 CPU(s):   0-5
th@deb:~$ sudo dmesg | grep DMI:
[    0.000000] DMI: Gigabyte Technology Co., Ltd. B360M-D2V/B360M D2V, BIOS F1 02/13/2018

trying to install
ftp://ftp.debian.ru/mirrors/MX-Linux/MX-ISOs/ANTIX/Final/antiX-19/antiX-19.3_x64-net.iso
the graphical interface is not expanded
I once asked about this on the forum and was told that I need to change the core.
for some reason, the desire disappeared.
I decided to try again.
can you please elaborate a little more?
I understand what you need in Customize Boot (text menu) or Advanced Options do everything ))))

• This topic was modified 2 years, 6 months ago by ThakurMsh.

[Member GeoffC]

Yay! I finally managed to get the 19.14 update installed, then ran ISO Snapshot and Live USB Maker. The snapshot USB boots fine now, so the real problem was that the repositories I was trying to upgrade from, didn’t hold the 19.14 update.

Now I need a crash course in repositories to understand why the update wasn’t available in the ones I was using (and why some of them just don’t seem to be working at all with my system).

[Forum Admin anticapitalista]

You might need to update iso-template before running a snapshot

https://www.antixforum.com/forums/topic/new-iso-snapshots-kernel-panicking-and-not-booting-after-latest-updates/

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

antiX with runit - leaner and meaner.

[Member rayluo]

olsztyn wrote:

So for myself to be clear, for this instance you are running: There is content of rootfs and/or homefs that is not yet merged by remaster into linuxfs and ISO Snapshot you are referring to is a snapshot of running system composed of linuxfs and rootfs?
What if you discard rootfs, does the system start correctly, although perhaps with incomplete app set?
I am just trying to understand underlying conditions…
Thanks and regards…
Edit:
Sorry for my questions that might seem confusing… What I am driving at is that in my understanding linuxfs should be pretty much static unless remaster has been performed, so I am curious what could have caused corruption of linuxfs…
Thanks and regards…

I can understand your questions, and they are all fair and welcome!

* I can see your point of only rootfs and/or homefs would be modified in usual usage, thus more susceptible to accidental dirty write damage. I did not use persistence, so there were no rootfs or homefs in my case. Even if I were using rootfs or homefs, it would be unlikely that I would have a correct copy of them from elsewhere, by their nature.

* Yes, the linuxfs is conceptually readonly during normal antiX liveUSB usage. I’m not sure whether linuxfs is logically readonly in liveUSB implementation. (Is it mounted as a readonly file system, @anticapticalista?). But at least, in my case, now I know it is not physically readonly. To be fair, though, such dirty write happens only once in a life time, at least from my thinkpad X60’s perspective. (More details on that accident: it first halted completely, and then the next reboot results a couple different beeps patterns generates from BIOS, indicating memory malfunction and/or motherboard malfunction. I guess anything could happen in such circumstance. Alas, my rock-solid thinkpad X60 now becomes a solid rock.)

[Member Mynaardt]

Hi Again, anticapitalista and Xecure!

(Xecure, I’ve answered part of your question below:

@ anticapitalista: I seem to have the ethernet connection back, although all I did was shut down the computer for several minutes while doing some studying working on my laptop. (Laptop is running on Linux Mint Xfce 20)…

Here is the copy of the history.log file (I’ve logged in and out and rebooted earlier hoping that make the problem go away):

Start-Date: 2020-10-02  15:20:14
Commandline: synaptic
Requested-By: malcolm (1000)
Install: xarchiver:amd64 (1:0.5.4.14-1)
End-Date: 2020-10-02  15:20:23

Start-Date: 2020-10-04  09:10:42
Commandline: apt-get --assume-yes -V dist-upgrade
Requested-By: malcolm (1000)
Upgrade: virtualbox-guest-utils:amd64 (6.1.6-dfsg-2~mx19+1, 6.1.14-dfsg-2~mx19+1), virtualbox-guest-dkms:amd64 (6.1.6-dfsg-2~mx19+1, 6.1.14-dfsg-2~mx19+1), feh:amd64 (3.4.1-1.0antix1, 3.5-1.0antix1), virtualbox-guest-x11:amd64 (6.1.6-dfsg-2~mx19+1, 6.1.14-dfsg-2~mx19+1)
End-Date: 2020-10-04  09:11:54

Start-Date: 2020-10-06  07:30:44
Commandline: apt-get --assume-yes -V dist-upgrade
Requested-By: malcolm (1000)
Install: python3-pyxattr:amd64 (0.6.1-1, automatic), rtmpdump:amd64 (2.4+20151223.gitfa8646d.1-2, automatic)
Upgrade: youtube-dl:amd64 (2020.09.14-1.0antix1, 2020.09.14-1.0antix2)
End-Date: 2020-10-06  07:30:59

Start-Date: 2020-10-07  06:32:33
Commandline: apt-get --assume-yes -V dist-upgrade
Requested-By: malcolm (1000)
Install: libtspi1:amd64 (0.3.14+fixed1-1, automatic), libbotan-2-9:amd64 (2.9.0-2, automatic)
Upgrade: thunderbird:amd64 (1:68.12.0-1~deb10u1, 1:78.3.1-2~deb10u2), opera-stable:amd64 (71.0.3770.198, 71.0.3770.228)
End-Date: 2020-10-07  06:33:53

Start-Date: 2020-10-08  10:03:10
Commandline: apt-get --assume-yes -V dist-upgrade
Requested-By: malcolm (1000)
Upgrade: desktop-defaults-jwm-antix:amd64 (0.6.0, 0.6.1), desktop-defaults-fluxbox-antix:amd64 (0.4.12, 0.4.13), nano:amd64 (5.2.0-1.0antix1, 5.3.0-1.0antix1), installer-data-antix:amd64 (0.2.0, 0.2.1), cli-shell-utils:amd64 (0.3.31, 0.3.32), iso-snapshot-antix:amd64 (0.3.16, 0.3.17), cli-installer-antix:amd64 (4.6, 4.7), desktop-defaults-icewm-antix:amd64 (0.4.17, 0.4.18), repo-list:amd64 (0.1.17, 0.1.19), antix-goodies:amd64 (0.7.13, 0.7.16), repo-manager:amd64 (0.2.3, 0.2.4), desktop-session-antix:amd64 (0.5.19, 0.5.20)
End-Date: 2020-10-08  10:07:19

Start-Date: 2020-10-10  08:41:32
Commandline: apt-get --assume-yes -V dist-upgrade
Requested-By: malcolm (1000)
Upgrade: advert-block-antix:amd64 (0.2.24, 0.2.25), screenshot-antix:amd64 (0.2.4, 0.2.5), apt-antix:amd64 (0.3.0, 0.3.1), live-usb-maker-gui-antix:amd64 (0.2.12, 0.2.14), ds-mouse-antix:amd64 (0.2.2, 0.2.3), bootrepair-antix:amd64 (17.15, 17.16), set-dpi-antix:amd64 (0.1.15, 0.1.16), antix-libs:amd64 (0.8.2, 0.8.3), remaster-antix:amd64 (0.7.19, 0.7.20), add-desktop-antix:amd64 (0.3.21, 0.3.22), mountbox-antix:amd64 (0.1.11, 0.1.12), cli-aptix:amd64 (0.2.24, 0.2.25), inxi-gui-antix:amd64 (0.3.9, 0.3.11), control-centre-antix:amd64 (0.7.23, 0.7.24), cli-shell-utils:amd64 (0.3.32, 0.3.33), codecs-antix:amd64 (17.4, 17.5), iso-snapshot-antix:amd64 (0.3.17, 0.3.18), console-grid-gui:amd64 (0.2.26, 0.2.27), packageinstaller:amd64 (0.2.3, 0.2.4), formatusb:amd64 (0.1.4, 0.1.5), antix-installer:amd64 (1.3.2, 1.3.3), apt-notifier:amd64 (18.04.10, 18.04.11), iso-template-antix:amd64 (19.10, 19.12), automount-antix:amd64 (0.1.19, 0.1.20), cli-installer-antix:amd64 (4.7, 4.8), wallpaper-antix:amd64 (0.5.3+1, 0.5.4), add-key-antix:amd64 (0.4.2, 0.4.3), antix-goodies:amd64 (0.7.16, 0.7.17), ddm-mx:amd64 (19.11.02+antix1, 19.11.02+antix2), antix-user:amd64 (0.1.9, 0.1.10), repo-manager:amd64 (0.2.4, 0.2.4.1), desktop-session-antix:amd64 (0.5.20, 0.5.21)
End-Date: 2020-10-10  08:42:15

Start-Date: 2020-10-12  09:52:58
Commandline: synaptic
Requested-By: malcolm (1000)
Install: gnustep-common:amd64 (2.7.0-4, automatic), gnustep-back0.27:amd64 (0.27.0-2, automatic), gnustep-gui-runtime:amd64 (0.27.0-5, automatic), gnustep-back0.27-cairo:amd64 (0.27.0-2, automatic), libicns1:amd64 (0.8.1-3.1, automatic), gnustep-back-common:amd64 (0.27.0-2, automatic), libobjc4:amd64 (8.3.0-6, automatic), mknfonts.tool:amd64 (0.5-12+b1, automatic), liblqr-1-0:amd64 (0.4.2-2.1, automatic), gnustep-gui-common:amd64 (0.27.0-5, automatic), charmap.app:amd64 (0.3~rc1-3+b3), libgnustep-base1.26:amd64 (1.26.0-4+deb10u1, automatic), charmap.app-common:amd64 (0.3~rc1-3, automatic), gnustep-base-runtime:amd64 (1.26.0-4+deb10u1, automatic), libmagickcore-6.q16-6:amd64 (8:6.9.10.23+dfsg-2.1+deb10u1, automatic), gnustep-base-common:amd64 (1.26.0-4+deb10u1, automatic), libgc1c2:amd64 (1:7.6.4-0.4, automatic), libgnustep-gui0.27:amd64 (0.27.0-5, automatic), fonts-freefont-ttf:amd64 (20120503-9, automatic), imagemagick-6-common:amd64 (8:6.9.10.23+dfsg-2.1+deb10u1, automatic)
End-Date: 2020-10-12  09:53:32

Start-Date: 2020-10-14  08:33:33
Commandline: apt-get --assume-yes -V dist-upgrade
Requested-By: malcolm (1000)
Upgrade: desktop-defaults-core-antix:amd64 (0.6.6, 0.6.7), libreoffice-math:amd64 (1:7.0.1-1~bpo10+2, 1:7.0.2-1~bpo10+1), firmware-iwlwifi:amd64 (20200817-1.0antix1, 20200918-1.0antix1), firmware-realtek:amd64 (20200817-1.0antix1, 20200918-1.0antix1), uno-libs-private:amd64 (1:7.0.1-1~bpo10+2, 1:7.0.2-1~bpo10+1), desktop-defaults-jwm-antix:amd64 (0.6.1, 0.6.2), libuno-salhelpergcc3-3:amd64 (1:7.0.1-1~bpo10+2, 1:7.0.2-1~bpo10+1), libreoffice-gtk3:amd64 (1:7.0.1-1~bpo10+2, 1:7.0.2-1~bpo10+1), desktop-defaults-fluxbox-antix:amd64 (0.4.13, 0.4.14), libreoffice-core:amd64 (1:7.0.1-1~bpo10+2, 1:7.0.2-1~bpo10+1), firmware-amd-graphics:amd64 (20200817-1.0antix1, 20200918-1.0antix1), remaster-antix:amd64 (0.7.20, 0.7.21), firmware-myricom:amd64 (20200817-1.0antix1, 20200918-1.0antix1), firmware-atheros:amd64 (20200817-1.0antix1, 20200918-1.0antix1), firmware-libertas:amd64 (20200817-1.0antix1, 20200918-1.0antix1), libuno-cppuhelpergcc3-3:amd64 (1:7.0.1-1~bpo10+2, 1:7.0.2-1~bpo10+1), firmware-netxen:amd64 (20200817-1.0antix1, 20200918-1.0antix1), atom:amd64 (1.51.0, 1.52.0), libreoffice-base-core:amd64 (1:7.0.1-1~bpo10+2, 1:7.0.2-1~bpo10+1), iso-snapshot-antix:amd64 (0.3.18, 0.3.19), console-grid-gui:amd64 (0.2.27, 0.2.28), firmware-intelwimax:amd64 (20200817-1.0antix1, 20200918-1.0antix1), libuno-purpenvhelpergcc3-3:amd64 (1:7.0.1-1~bpo10+2, 1:7.0.2-1~bpo10+1), libreoffice-impress:amd64 (1:7.0.1-1~bpo10+2, 1:7.0.2-1~bpo10+1), firmware-linux-nonfree:amd64 (20200817-1.0antix1, 20200918-1.0antix1), firmware-brcm80211:amd64 (20200817-1.0antix1, 20200918-1.0antix1), firmware-intel-sound:amd64 (20200817-1.0antix1, 20200918-1.0antix1), iso-template-antix:amd64 (19.12, 19.13), libreoffice-style-colibre:amd64 (1:7.0.1-1~bpo10+2, 1:7.0.2-1~bpo10+1), firmware-qlogic:amd64 (20200817-1.0antix1, 20200918-1.0antix1), ure:amd64 (1:7.0.1-1~bpo10+2, 1:7.0.2-1~bpo10+1), libreoffice-writer:amd64 (1:7.0.1-1~bpo10+2, 1:7.0.2-1~bpo10+1), libreoffice-common:amd64 (1:7.0.1-1~bpo10+2, 1:7.0.2-1~bpo10+1), desktop-defaults-icewm-antix:amd64 (0.4.18, 0.4.19), firmware-misc-nonfree:amd64 (20200817-1.0antix1, 20200918-1.0antix1), libuno-cppu3:amd64 (1:7.0.1-1~bpo10+2, 1:7.0.2-1~bpo10+1), fonts-opensymbol:amd64 (2:102.11+LibO7.0.1-1~bpo10+2, 2:102.11+LibO7.0.2-1~bpo10+1), firmware-bnx2x:amd64 (20200817-1.0antix1, 20200918-1.0antix1), antix-goodies:amd64 (0.7.17, 0.7.18), broadcom-sta-dkms:amd64 (6.30.223.271-10, 6.30.223.271-15.0antix1), libuno-sal3:amd64 (1:7.0.1-1~bpo10+2, 1:7.0.2-1~bpo10+1), droopy-antix:amd64 (0.1.5, 0.1.6), opera-stable:amd64 (71.0.3770.228, 71.0.3770.271), libreoffice-calc:amd64 (1:7.0.1-1~bpo10+2, 1:7.0.2-1~bpo10+1), packageinstaller-pkglist:amd64 (0.3.22, 0.3.23), firmware-bnx2:amd64 (20200817-1.0antix1, 20200918-1.0antix1), firmware-ipw2x00:amd64 (20200817-1.0antix1, 20200918-1.0antix1), libreoffice-draw:amd64 (1:7.0.1-1~bpo10+2, 1:7.0.2-1~bpo10+1)
End-Date: 2020-10-14  08:38:25

Start-Date: 2020-10-15  09:18:28
Commandline: apt-get --assume-yes -V dist-upgrade
Requested-By: malcolm (1000)
Upgrade: libreoffice-math:amd64 (1:7.0.2-1~bpo10+1, 1:7.0.2-2~bpo10+1), uno-libs-private:amd64 (1:7.0.2-1~bpo10+1, 1:7.0.2-2~bpo10+1), libuno-salhelpergcc3-3:amd64 (1:7.0.2-1~bpo10+1, 1:7.0.2-2~bpo10+1), libreoffice-gtk3:amd64 (1:7.0.2-1~bpo10+1, 1:7.0.2-2~bpo10+1), libreoffice-core:amd64 (1:7.0.2-1~bpo10+1, 1:7.0.2-2~bpo10+1), vivaldi-stable:amd64 (3.3.2022.47-1, 3.4.2066.76-1), libuno-cppuhelpergcc3-3:amd64 (1:7.0.2-1~bpo10+1, 1:7.0.2-2~bpo10+1), libreoffice-base-core:amd64 (1:7.0.2-1~bpo10+1, 1:7.0.2-2~bpo10+1), libuno-purpenvhelpergcc3-3:amd64 (1:7.0.2-1~bpo10+1, 1:7.0.2-2~bpo10+1), libreoffice-impress:amd64 (1:7.0.2-1~bpo10+1, 1:7.0.2-2~bpo10+1), libreoffice-style-colibre:amd64 (1:7.0.2-1~bpo10+1, 1:7.0.2-2~bpo10+1), ure:amd64 (1:7.0.2-1~bpo10+1, 1:7.0.2-2~bpo10+1), libreoffice-writer:amd64 (1:7.0.2-1~bpo10+1, 1:7.0.2-2~bpo10+1), libreoffice-common:amd64 (1:7.0.2-1~bpo10+1, 1:7.0.2-2~bpo10+1), libuno-cppu3:amd64 (1:7.0.2-1~bpo10+1, 1:7.0.2-2~bpo10+1), fonts-opensymbol:amd64 (2:102.11+LibO7.0.2-1~bpo10+1, 2:102.11+LibO7.0.2-2~bpo10+1), libuno-sal3:amd64 (1:7.0.2-1~bpo10+1, 1:7.0.2-2~bpo10+1), libreoffice-calc:amd64 (1:7.0.2-1~bpo10+1, 1:7.0.2-2~bpo10+1), libreoffice-draw:amd64 (1:7.0.2-1~bpo10+1, 1:7.0.2-2~bpo10+1)
End-Date: 2020-10-15  09:20:17

Start-Date: 2020-10-17  10:06:47
Commandline: apt-get --assume-yes -V dist-upgrade
Requested-By: malcolm (1000)
Upgrade: iso-template-antix:amd64 (19.13, 19.14)
End-Date: 2020-10-17  10:06:53

@ Xecure:I’ve not tried that sound file yet, but will in a minute; I’m trying to juggle a few things at the same time.
BUT: there is no master volume button on the Space IceWM session, but it is on the taskbars of both Space Fluxbox and Space JWM.
The regular sound test does application not work in any of the desktops at the moment.

What have the Romans ever done for us?
Apart from: sanitation, medicine, education, wine, public order, irrigation, roads, fresh water, and public health?

Background and Symptom (the solution below would probably only work if you encounter same symptom):

I use antiX on LiveUSB exclusively for a year or two. Most of the time it worked fine, but there was one time that my LiveUSB still booted and largely worked, but some of the icons on Desktop File Manager could not show up, and displayed as a red cross “x” instead. I ended up re-creating a LiveUSB on the same flash drive and it worked well since then.

Yesterday I encountered same symptom, plus the loss of functionality of Archive Manager (i.e. clicking on an .zip archive, the Archive Manager would be invoked but then automatically closed in less than a second). This time, I know it is presumably a side effect of my otherwise rock-solid 14-year-old laptop suddenly halted and then could not turn back on. (RIP 2006-2020)

Solution:

I could choose to (re)create a new LiveUSB on a different flash drive, and then manually copy all my Live-usb-storage content and accumulated states from the old flash drive to new one.

But then I figure that the damaged data on the flash drive would most likely happen at its single biggest file, the 1 GB “/antiX/linuxfs”. Such hypothesis was confirmed by comparing that file’s md5sum. It did not match. So the solution becomes effortlessly simple: just copy the same file from inside the .iso and override the damaged one on flash drive. All my other data on the same flash drive remain valid. Easy piece!

Hope that helps.

[Member Xecure]

non-pae yes (antiX 19.3 i386 base and full come with non-pae kernel).

The problem will be other things probably (enough RAM, compatible graphic card with current xserver-sorg-video drivers, etc.).
antiX 15/16 worked on a Pentium MMX (https://antixlinux.com/forum-archive/antix-v386-base-iso-t5924.html) but it was extremely limited.

If you want to see if it is possible, burn a CD with antiX 17 base i386 first and see if it can boot to graphical environment. Probably you will have to use a 4.4 kernel (in the repos) once you have it installed.
I wouldn’t try antiX 19 yet until you are sure antiX 17 works. I believe 19 will be too much for your computer.

Probably someone with more experience with old machines can give us some more info.

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

[Moderator Brian Masinick]

Brian Masinick wrote:

I chose the image antiX-19.3-runit_x64-full.iso to download…

After trying out a few live logins using Frugal and Live, I installed the full runit X64 instance to a 23 GB partition at the end of my disk.
It’s on partition 12; a previous antiX 19.2.1 runit instance is on partition 8, and a Base instance of the sysinitV scheduler is installed on partition 10. All of them are recognized through GRUB EFI, which is installed on MX Linux 19.2 on partition 3, and the EFI partition containing the /boot/efi directory is on partition 4; this works just as well on the latest instance as on the previous instances.

I’ve been able to “trip” the live login by selecting a persistent or frugal state that conflicts with previously stored instances; that’s probably not “fair” or reasonable. I’ve not had any trouble at all using the system as intended with out feeding it things outside of the designed behavior.
The installation went cleanly with no regressions in the installed functionality detected. My efforts have not been exhaustive, but they do indicate that the software is generally stable and of good quality.

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

--
Brian Masinick

Hi everyone!

I’d like to point out that after the latest updates (19.3 related) all the custom ISO Snapshots that I’ve been making are failing at the boot process.
If I build them with the 4.19 antix kernel, they simply freeze right after the boot menu without any hint; I tried then with the 4.9 antix kernel and it came out that they are kernel panicking. Photo attached.
I burnt them with different programs as well (pure dd too) but it’s the ISO generation to be somehow troublesome.

$ inxi -Fxz
System:
  Host: antiX Kernel: 4.19.143-antix.1-amd64-smp x86_64 bits: 64 
  compiler: gcc v: 8.3.0 Desktop: MATE 1.20.4 
  Distro: antiX-19.2.1-runit_x64-base Hannie Schaft 29 March 2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Laptop System: Hewlett-Packard product: HP EliteBook 8460p 
  v: A0001D02 serial: <filter> 
  Mobo: Hewlett-Packard model: 161C v: KBC Version 97.4E serial: <filter> 
  UEFI: Hewlett-Packard v: 68SCF Ver. F.67 date: 02/13/2018 
Battery:
  ID-1: BAT0 charge: 36.8 Wh condition: 37.4/37.4 Wh (100%) 
  model: Hewlett-Packard Primary status: Charging 
CPU:
  Topology: Quad Core model: Intel Core i7-2720QM bits: 64 type: MT MCP 
  arch: Sandy Bridge rev: 7 L2 cache: 6144 KiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 35123 
  Speed: 1334 MHz min/max: 800/2200 MHz Core speeds (MHz): 1: 1381 2: 992 
  3: 979 4: 925 5: 1215 6: 1059 7: 1237 8: 1308 
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
  vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 
  Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1366x768~60Hz 
  OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.3.6 
  direct render: Yes 
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio 
  vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  Sound Server: ALSA v: k4.19.143-antix.1-amd64-smp 
Network:
  Device-1: Intel 82579LM Gigabit Network vendor: Hewlett-Packard 
  driver: e1000e v: 3.2.6-k port: 2060 bus ID: 00:19.0 
  IF: eth0 state: down mac: <filter> 
  Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi 
  v: kernel port: 2040 bus ID: 03:00.0 
  IF: wlan0 state: up mac: <filter> 
Drives:
  Local Storage: total: 223.57 GiB used: 16.58 GiB (7.4%) 
  ID-1: /dev/sda vendor: OCZ model: ARC100 size: 223.57 GiB 
Partition:
  ID-1: / size: 49.72 GiB used: 16.28 GiB (32.8%) fs: ext4 dev: /dev/dm-0 
  ID-2: /boot size: 975.9 MiB used: 140.8 MiB (14.4%) fs: ext4 
  dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 40.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 253 Uptime: 13m Memory: 11.63 GiB used: 1.93 GiB (16.6%) 
  Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 
  inxi: 3.0.36 

Attachments:

1. 

   photo_2020-10-17_03-21-11.jpg
   

[Member marcelocripe]

No Windows 7:

Conecte na porta USB, apenas o pendrive que será formato e preparado pelo Ventoy, remova com segurança outros pendrives ou cartões de memória que eventualmente estejam conectados no seu computador.

Atenção!

Faça cópia de segurança dos seus dados antes de prosseguir, o Ventoy formatará o seu pendrive e todos os seus dados serão perdidos, excluídos ou apagados.

Acessar o Explorador de Arquivos do Windows (Windows Explorer), também conhecido como Documentos, encontre a pasta Downloads, descompacte o arquivo ventoy-1.0.21-windows.zip, entrar na pasta ventoy-1.0.21, duplo clique sobre Ventoy2Disk.exe, clique em Sim para permitir que o programa faça alterações no computador.

Observe que o pendrive possui a seguinte descrição: Disco removível (G:).

Estando apenas o pendrive que será formatado conectado no computador, será exibido o nome do seu pendrive na lista Device (Dispositivo), caso não seja exibido, clique no ícone que contém duas setas em cor branca e fundo verde, para atualizar a lista.

Clicar em Install (Instalar) para iniciar o processo de preparação do seu pendrive. Será exibido a mensagem “The disk will be formatted and all the data will be lost. Continue?”, traduzindo com o tradutor online: “O disco será formatado e todos os dados serão perdidos. Continuar?”, clique em Sim, outra mensagem será exibida “The disk will be formatted and all the data will be lost. Continue? (Double Check)”, traduzindo com o tradutor online: “O disco será formatado e todos os dados serão perdidos. Continuar? (Verifique duas vezes) ou (Verificação dupla)”, Sim para formatar e preparar o seu pendrive com o Ventoy.

Quando for concluído o processo, será exibido a mensagem “Congratulations! Ventoy has been successfully installed to the device”, traduzindo com o tradutor online: “Parabéns! Ventoy foi instalado com sucesso no dispositivo”, clique em OK e em “X” para fechar ou sair do programa.

Observe que o pendrive possou a ter a seguinte descrição: Ventoy (G:).

No seu computador o pendrive poderá estar identificado por outra letra, atente-se a isso, copie a(s) imagem(s) ISO(s) para a partição chamada Ventoy. Segundo o sr. Alessandro do PCLinux Os Brasil, a imagem ISO não pode possuir espaço em seu nome, remova os espaços ou substitua por underline.

Após a conclusão da cópia, clique no ícone da barra de tarefas para remover o dispositivo USB com segurança.

Agradeço o sr. Brian Masinick que possui vasta experiência e compartilhou a informação sobre este excelente programa para a preparação de pendrive inicializável, pendrive “bootável” ou pendrive de boot.

marcelocripe

Attachments:

1. 

   1-Ventoy_1.0.21.png
   

2. 

   2-Ventoy_1.0.21.png
   

3. 

   3-Ventoy_1.0.21.png
   

4. 

   4-Ventoy_1.0.21.png
   

[Member PPC]

PFO wrote:

Hey Dagws,

Have NERO 6.6.0.3 up and ready to burn antix base – core or full on a
“Multi-border DVD with more than 4.0 GB of Data Not Readable Past First Border”

Seems to be old software unable to interface with new DVD sizes. But if it would load FULL as a bootable that would be optimum!

Your advice?
PFO

I’m not sure if I understood your problem correctly… if Nero is complaining because of the blank dvd-rom you tried to burn “antix full 32 bits” try a new disk, from another brand… I have not burned dvd-roms in a very long time, but I’, not aware the DVD size changed… Can you try to burn the iso to DVD-ROM on another computer?

P.

[Forum Admin rokytnji]

I needed to test this forum function anyway

https://www.antixforum.com/forums/search/boot+from+iso/?gdpos=power-search-request

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

More info:

sda1 (first partition) is the EFI partition. It needs to be at least 20 MBs (what boot and EFI folders take). I set it to about 100MB, for future extra EFI files.
sda2 (main partition) will host your frugal installs. It is recommended to leave it as a ext4 format, but you can change it to something else (for example ntfs for windows access).

About installing EFI when NOT using live USB (from live ISO). The folder /media/demo/LIVE-UEFI (or ANTIX-UEFI) will NOT exist.
The grub.cfg file that Christophe talks about in step 3 is, in fact, the /live/boot-dev/boot/grub/config/efi-grub.cfg file.
So, steps for me were:
1. I boot to my antiX live ISO session.
2. If you don’t like Rox filer, launch SpaceFM as root (open normal SpaceFM, then go to top menu File > Root Window; or terminal gksu spacefm).
3. Copy the EFI folder from the iso (/live/boot-dev/) to your EFI partition (sda1).
3.1. In your EFI (sda1) partition, create a new boot folder and inside it a grub folder
3.2. Go back to the /live/boot-dev/ folder, enter /boot/grub/config/ folder and copy efi-grub.cfg to the grub folder you created in your sda1 efi partition(…/boot/grub/). Rename it to grub.cfg
4. Continue Christophe’s tutorial (in the new grub.cfg file, replace main_uuid=”%UUID%” with the corresponding uuid for sda2, like main_uuid=”6d44c859-e1c4-42d0-b3ea-147b028fc93c”, you can also replace file_id with “/boot/grub/grub.cfg” or create a file in /boot/grub/config/ with a special name and use it instead, or leave as is).

About REGISTERING WITH UEFI, the second step is with sudo:
sudo efibootmgr -c -d /dev/sda -p 1 -l \\EFI\\BOOT\\grubx64.efi -L BootFrugal

I wanted to test this on a virtual machine and all steps worked except for actually booting to the frugal installation. It stops at “cannot find the uuid drive”. I blame the VM as I rechecked everything a thousand times. These kind of errors drain me.

Anyway, good work Christophe. This is a very interesting way of getting things to work without any installation, only with frugals.

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

I have used recently the snapshot tool from the antiX application menu, which worked out very good and looks well overseeable.
At the end I get a message:

MX Snapshot was succesfully done … (I have on German)

isohybrid: Warning: more than 1024 cylinders: 6045
isohybrid: Not all BIOSes will be able to boot this device

Does it mean it works only with an EFI Bios? Which kind of bios is more likely to work ?
My BIOS is :

Vendor: FUJITSU // Phoenix Technologies Ltd.
Version: Version 1.14
Release Date: 08/20/2008

– – –

Just BTW when I log in to antixforum.com I come to:
antixforum.com/wp-admin/index.php ??? is that normal ?