Search Results for 'boot from iso'

[Member sybok]

Hi,

some blind questions/suggestions:
1) Does the live-usb-maker provide some more information that the simple “error”?
2) Verify “quality” of the USB – e.g. scan for bad sectors; I had a broken USB once.
3) Verify size of USB and the ISO.
4) Try to write a “dummy” file to the mounted USB to check if the permissions for the USB device are set properly.
5) Did you change any of the default settings of the live-usb-maker?
6) Verify integrity of the downloaded ISO Linux/Windows (checksums, e.g. md5). [Should not be the issue in general but could cause failure of the live media to work properly.]

7) Fallback: You may try to create the live USB using ‘dd’, see e.g. this link at techbit to see if (at least) this (mostly foolproof) method works.
WARNING: ‘dd’ is potentially dangerous (loss of data) if you mess up the target partition in parameter of!

Hope that might point you to the right direction.
Could also be a i386-specific issue which I could not help with since I use 64bit only.

[Moderator Brian Masinick]

PDP-8 wrote: “One of the great things about antiX (and MX too) when it comes to older gear is the fantastic ability to run with persistence on USB.”

I completely agree, though there are MANY great things. I could care less about the fanciest stuff, because I almost always change the appearance to suit my own needs. With EITHER antiX or MX Linux, one of the other things that I really appreciate is that they are made to work. In all the years of MEPIS, antiX, and MX Linux, I think there was only ONE Alpha build (more than a decade ago in MEPIS), that had an issue with the hardware I use; it was one of the first (and only) feature regressions, it was in the first Alpha build, I reported it IMMEDIATELY and I’ve never seen that kind of bug, regardless of Alpha, Beta, or released software. Defects in general are minor and are usually application defects, NOT distribution defects. We’re talking about more than fifteen years of history here too. There are very few distributions that have a record that good. Keep in mind I’m not saying there were zero defects, there just are extremely RARE show stopper defects, highly impressive, especially with small development teams; maybe that, and the commitment to quality, is what makes the difference!

@anti-ewaste: I may be a veteran software user and a long time Linux enthusiast, but it does not mean that I have tried out every possible software combination. I have not ever used the Plop boot manager. I used the original GRUB boot loader, now known as GRUB Legacy for many years and I could chain load distributions and do all kinds of “balancing acts” with GRUB Legacy. I’ve become reasonably adept with the current GRUB 2 boot manager/loader, but I would not quite claim to be an “expert”, just a competent user, capable of making routine modifications and updating it, or reinstalling it when something accidentally is changed or a new distribution “grabs control” of the boot loader.

So I’m interested in your comments on Plop. Is it full of features, really simple, or highly advanced? Is there something you particularly like about it? Also if you have any comparisons with other boot loaders, like the old ones: LILO, syslinux, etc, compared to GRUB, I’d be interested. I may look into it myself, but your impressions are appreciated; thanks!

--
Brian Masinick

[Member Xecure]

melodie wrote:

I would like to remove the choice for these desktops at the start of the live

Are you refering to options in boot under F6 for legacy_BIOS boot? If so, you will have to edit the boot folder in the .iso (/live/boot-dev/boot when mounted).

anticapitalista wrote:

antiX uses syslinux for its live system, but grub2 for installation to a device.

No idea how to change these. I have no experience with isolinux/syslinux. Maybe editing the gfxsave.cfg for isolinux/syslinux. The .c32 module files I have no idea how to edit them (maybe they are binaries, and you need to edit the source files).

Edit: I think https://gitlab.com/antiX-Linux/antiX-Gfxboot is the source code for antiX boot.

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

[Member olsztyn]

Brian Masinick wrote:

How about if each person who wrote in THIS THREAD about improving Linux documentation would personally volunteer to update ONE topic on some aged source?

I would gladly volunteer to contribute. However just to emphasize, I am an average user of antiX so I may not have sufficient knowledge of the details, at least not comparable to seasoned antiX contributors and development team… But I would do my best… Not familiar with MX at all short of trying once in the past.
If you are asking on the topic I would be able to contribute, this could be e.g. Live/Frugal. However there is already an extensive documentation on this and nothing can even come close to the excellent videos produced by d_o.
From my area of modest experience with antiX Live/Frugal I would suggest to update some details highlighting enhancements and capabilities not previously documented to that extent and document a few intricacies, previously not highlighted in existing documentation.
As an example I would suggest specifically to add:
– Using extlinux boot process to boot multiple Frugal installs without the need for OS actually installed – developed by christophe
– Using Grub process to do the same as above – developed recently by christophe
– Highlight easy update of Frugals by replacing linuxfs file – as pointed out recently by anilkage
– Various enhancements brought up recently by Xecure

For clarity of limitations in that area I would raise awareness of a few things:
– Most of errors in Live-USB-Maker process execution result from either not perfect ISO source (as recent thread a few days ago), so not necessarily imperfect LUM code. From my experiece, some erratic LUM errors also may result from laptop being placed in dock. Taken out of dock – works fine with the same stick.
– Awareness that latest update to LUM broke the capability of LUM to clone encrypted antiX, which results in error. The previous version worked fine.
It would be beneficial to highlight this in documentation so users would not be surprised with such error and have at least one un-encrypted backup.

Just an idea what could be added/clarified…

• This reply was modified 2 years, 8 months ago by olsztyn.
• This reply was modified 2 years, 8 months ago by olsztyn.

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

[Member Noman01]

Rebooted the computer and started all over from the beginning, followed the advice given and it worked this time.

Please select the source for the new live-usb
= Copy from an ISO file
Press <Enter> to select the highlighted entry
Use ‘h’ for help, ‘r’ to redraw, ‘q’ to quit
Please enter the filename
(tab completion is enabled)
/home/gerudd/antiX-19.2-runit_386-full.iso
You entered: /home/gerudd/antiX-19.2-runit_386-full.iso
Is this correct?
= yes
> no
Press <Enter> to select the highlighted entry
Use ‘h’ for help, ‘r’ to redraw, ‘q’ to quit
Will use source file /home/gerudd/antiX-19.2-runit_386-full.iso
Distro: antiX-19.2-runit_386-full Hannie Schaft 27 March 2020
Found grub config 2.0

Total Used Extra
entire drive 7.21 GiB 7.21 GiB 1 MiB
main partition 7.16 GiB 1.11 GiB 6.05 GiB
uefi partition 50 MiB 18 MiB 32 MiB

——————————————————————————-
Ready to make live-usb on device sdb
… by copying file /home/gerudd/antiX-19.2-runit_386-full.iso
——————————————————————————-

Shall we begin?
= yes
> no
> pretend mode
Press <Enter> to select the highlighted entry
Use ‘h’ for help, ‘r’ to redraw, ‘q’ to quit
>> partition-clear
>> partition-make
Using msdos partitioning
>> makefs-bios
>> makefs-uefi

Filesystem Type Size Used Avail Use% Mounted on
/dev/sdb1 ext4 7.2G 17M 7.1G 1% main
/dev/sdb2 vfat 49M 512 49M 1% uefi

>> copy-uefi
copy from iso to uefi partition
files [Ee][Ff][Ii] version
Fix Dell uefi memtest bug
>> copy-main
copy from iso to main partition
copy /antiX/vmlinuz
copy /antiX/initrd.gz
copy remaining files …
|=========================================================================>100%
>> check-usb-md5
check md5 for initrd.gz
check md5 for linuxfs
check md5 for vmlinuz
>> uuids
Using antiX/MX grub config 2.0
>> install
extlinux version 6.04

Filesystem Type Size Used Avail Use% Mounted on
/dev/sdb1 ext4 7.2G 1.2G 6.0G 16% main
/dev/sdb2 vfat 49M 4.2M 45M 9% uefi

>> done

live-usb-maker took 4 minutes and 52 seconds.

Thanks for your help.

[Member Xecure]

Noman01 wrote:

Error: Can’t mount /home/gerudd/antiX-19.2-runit_386-full.iso. Mountpoint /run/live-usb-maker/iso is already being used
rmdir: failed to remove ‘/run/live-usb-maker’: Device or resource busy

Reboot the system just in case the live-USB-maker-gui-antix is still running and has “kidnaped” the /run/live-usb-maker/iso mountpoint.
Reboot and try the commands again.

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

I’m trying to make a live usb using antiX 19.2-runit 386, how ever when go to run the program I get an error message error encountered in the live usb creation process. The live usb maker version is 2.41.17.

system info:
System: Host: Kernel: 4.19.120-antix.1-486-smp i686 bits: 32 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.120-antix.1-486-smp
root=UUID=53a47157-cda3-42bc-8112-bf5deac42322 ro quiet
Desktop: Fluxbox 1.3.7 dm: SLiM 1.3.6
Distro: antiX-19.1_386-full Marielle Franco 23 December 2019
base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop System: Apple product: Macmini2,1 v: 1.0 serial: <filter> Chassis:
type: 4 v: Mac-F4208EAA serial: <filter>
Mobo: Apple model: Mac-F4208EAA v: PVT serial: <filter> UEFI: Apple
v: MM21.88Z.009A.B00.0706281359 date: 06/28/07
Memory: RAM: total: 951.4 MiB used: 142.0 MiB (14.9%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
PCI Slots: Permissions: Unable to run dmidecode. Root privileges required.
CPU: Topology: Dual Core model: Intel Core2 T7200 bits: 64 type: MCP arch: Core Merom
family: 6 model-id: F (15) stepping: 6 microcode: D1 L2 cache: 4096 KiB bogomips: 7999
Speed: 1449 MHz min/max: 1000/2000 MHz Core speeds (MHz): 1: 1000 2: 1021
Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc cpuid cx16 cx8
de ds_cpl dtes64 dtherm dts est fpu fxsr ht lahf_lm lm mca mce mmx monitor msr mtrr nx
pae pat pbe pdcm pebs pge pni pse pse36 sep ss sse sse2 ssse3 tm tm2 tpr_shadow tsc vme
vmx xtpr
Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages
Type: l1tf status: Vulnerable
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Type: meltdown status: Vulnerable
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel Mobile 945GM/GMS 943/940GML Express Integrated Graphics driver: i915
v: kernel bus ID: 00:02.0 chip ID: 8086:27a2
Display: x11 server: X.Org 1.20.4 driver: intel unloaded: fbdev,modesetting,vesa
resolution: 1024×768~75Hz
OpenGL: renderer: Mesa DRI Intel 945GM x86/MMX/SSE2 v: 1.4 Mesa 18.3.6
direct render: Yes
Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: SigmaTel STAC9221 Codec
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8
Sound Server: ALSA v: k4.19.120-antix.1-486-smp
Network: Device-1: Marvell 88E8053 PCI-E Gigabit Ethernet driver: sky2 v: 1.30 port: 1000
bus ID: 01:00.0 chip ID: 11ab:4362
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IP v4: <filter> type: dynamic scope: global broadcast: <filter>
IP v4: <filter> virtual: secondary scope: global broadcast: <filter>
IP v6: <filter> scope: global
IP v6: <filter> type: dynamic mngtmpaddr scope: global
IP v6: <filter> scope: link
Device-2: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter
vendor: Apple AirPort Extreme driver: ath5k v: kernel port: 1000 bus ID: 02:00.0
chip ID: 168c:001c
IF: wlan0 state: down mac: <filter>
WAN IP: <filter>
Drives: Local Storage: total: 111.79 GiB used: 36.75 GiB (32.9%)
ID-1: /dev/sda vendor: Hitachi model: HTS541612J9SA00 size: 111.79 GiB block size:
physical: 512 B logical: 512 B speed: 1.5 Gb/s serial: <filter> rev: C7MP scheme: GPT
Optical-1: /dev/sr0 vendor: PIONEER model: DVD-RW DVR-K06 rev: Q614
dev-links: cdrom,cdrw,dvd,dvdrw
Features: speed: 24 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r
state: running
RAID: Message: No RAID data was found.
Partition: ID-1: / raw size: 109.51 GiB size: 107.29 GiB (97.97%) used: 30.74 GiB (28.7%) fs: ext4
dev: /dev/sda2 label: rootantiX19 uuid: 53a47157-cda3-42bc-8112-bf5deac42322
ID-2: /boot/efi raw size: 256.0 MiB size: 252.0 MiB (98.46%) used: 290 KiB (0.1%)
fs: vfat dev: /dev/sda1 label: N/A uuid: 26E1-EBB5
ID-3: /run/live-usb-maker/iso raw size: 8.46 GiB size: <root required>
used: <root required> fs: iso9660 dev: /dev/loop0 label: antiXLIVE
uuid: 2020-07-23-17-38-03-00
ID-4: /run/live-usb-maker/main raw size: N/A size: 14.62 GiB used: 6.00 GiB (41.0%)
fs: ext4 dev: /dev/sdb1 label: N/A uuid: N/A
ID-5: /run/live-usb-maker/uefi raw size: N/A size: 48.2 MiB used: 4.2 MiB (8.7%)
fs: vfat dev: /dev/sdb2 label: N/A uuid: N/A
ID-6: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 10 (default 60)
cache pressure: 50 (default 100) dev: /dev/sda3 label: swapantiX
uuid: 31e6ad28-ae85-451d-9e9e-7ae39f2d2fb0
Unmounted: Message: No unmounted partitions found.
USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 8 rev: 2.0 speed: 480 Mb/s
chip ID: 1d6b:0002
Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 4-2:2 info: Alcor Micro Hub ports: 4 rev: 1.1 speed: 12 Mb/s chip ID: 058f:9254
Hub: 4-2.3:3 info: Apple ports: 3 rev: 2.0 speed: 12 Mb/s chip ID: 05ac:1005
Device-1: 4-2.3.2:4 info: Apple Aluminum Mini Keyboard (ANSI) type: Keyboard,HID
driver: apple,usbhid interfaces: 2 rev: 2.0 speed: 1.5 Mb/s chip ID: 05ac:021d
Device-2: 4-2.3.3:5 info: Apple Mighty Mouse [Mitsumi M1152] type: Mouse
driver: apple,usbhid interfaces: 1 rev: 1.1 speed: 1.5 Mb/s chip ID: 05ac:0304
Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Device-3: 5-1:8 info: Apple Bluetooth HCI type: Bluetooth driver: btusb interfaces: 3
rev: 2.0 speed: 12 Mb/s chip ID: 05ac:8205
Device-4: 5-2:3 info: Apple Built-in IR Receiver type: HID driver: appleir,usbhid
interfaces: 1 rev: 2.0 speed: 12 Mb/s chip ID: 05ac:8240
Sensors: System Temperatures: cpu: 63.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http: //mirrors.rit.edu/mxlinux/mx-packages/antix/buster/ buster main nonfree nosystemd
Active apt repos in: /etc/apt/sources.list.d/buster-backports.list
1: deb http: //deb.debian.org/debian buster-backports main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http: //ftp.us.debian.org/debian/ buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http: //ftp.gr.debian.org/debian/ buster main contrib non-free
2: deb http: //security.debian.org/ buster/updates main contrib non-free
No active apt repos in: /etc/apt/sources.list.d/onion.list
Active apt repos in: /etc/apt/sources.list.d/softmaker.list
1: deb http: //shop.softmaker.com/repo/apt wheezy non-free
No active apt repos in: /etc/apt/sources.list.d/various.list

Any ideas on what is wrong. Thanks in advance.

• This topic was modified 2 years, 8 months ago by Noman01.
• This topic was modified 2 years, 8 months ago by Noman01.

I’m trying to make a live usb using antiX 19.2-runit 386. But I keep getting an error msg “error encountered in the live usb creation process”, the live usb maker is ver is 2.41.17.

Computer info.
System: Host: RuddHome Kernel: 4.19.120-antix.1-486-smp i686 bits: 32 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.120-antix.1-486-smp
root=UUID=53a47157-cda3-42bc-8112-bf5deac42322 ro quiet
Desktop: Fluxbox 1.3.7 dm: SLiM 1.3.6
Distro: antiX-19.1_386-full Marielle Franco 23 December 2019
base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop System: Apple product: Macmini2,1 v: 1.0 serial: <filter> Chassis:
type: 4 v: Mac-F4208EAA serial: <filter>
Mobo: Apple model: Mac-F4208EAA v: PVT serial: <filter> UEFI: Apple
v: MM21.88Z.009A.B00.0706281359 date: 06/28/07
Memory: RAM: total: 951.4 MiB used: 142.0 MiB (14.9%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
PCI Slots: Permissions: Unable to run dmidecode. Root privileges required.
CPU: Topology: Dual Core model: Intel Core2 T7200 bits: 64 type: MCP arch: Core Merom
family: 6 model-id: F (15) stepping: 6 microcode: D1 L2 cache: 4096 KiB bogomips: 7999
Speed: 1449 MHz min/max: 1000/2000 MHz Core speeds (MHz): 1: 1000 2: 1021
Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc cpuid cx16 cx8
de ds_cpl dtes64 dtherm dts est fpu fxsr ht lahf_lm lm mca mce mmx monitor msr mtrr nx
pae pat pbe pdcm pebs pge pni pse pse36 sep ss sse sse2 ssse3 tm tm2 tpr_shadow tsc vme
vmx xtpr
Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages
Type: l1tf status: Vulnerable
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Type: meltdown status: Vulnerable
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel Mobile 945GM/GMS 943/940GML Express Integrated Graphics driver: i915
v: kernel bus ID: 00:02.0 chip ID: 8086:27a2
Display: x11 server: X.Org 1.20.4 driver: intel unloaded: fbdev,modesetting,vesa
resolution: 1024×768~75Hz
OpenGL: renderer: Mesa DRI Intel 945GM x86/MMX/SSE2 v: 1.4 Mesa 18.3.6
direct render: Yes
Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: SigmaTel STAC9221 Codec
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8
Sound Server: ALSA v: k4.19.120-antix.1-486-smp
Network: Device-1: Marvell 88E8053 PCI-E Gigabit Ethernet driver: sky2 v: 1.30 port: 1000
bus ID: 01:00.0 chip ID: 11ab:4362
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IP v4: <filter> type: dynamic scope: global broadcast: <filter>
IP v4: <filter> virtual: secondary scope: global broadcast: <filter>
IP v6: <filter> scope: global
IP v6: <filter> type: dynamic mngtmpaddr scope: global
IP v6: <filter> scope: link
Device-2: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter
vendor: Apple AirPort Extreme driver: ath5k v: kernel port: 1000 bus ID: 02:00.0
chip ID: 168c:001c
IF: wlan0 state: down mac: <filter>
WAN IP: <filter>
Drives: Local Storage: total: 111.79 GiB used: 36.75 GiB (32.9%)
ID-1: /dev/sda vendor: Hitachi model: HTS541612J9SA00 size: 111.79 GiB block size:
physical: 512 B logical: 512 B speed: 1.5 Gb/s serial: <filter> rev: C7MP scheme: GPT
Optical-1: /dev/sr0 vendor: PIONEER model: DVD-RW DVR-K06 rev: Q614
dev-links: cdrom,cdrw,dvd,dvdrw
Features: speed: 24 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r
state: running
RAID: Message: No RAID data was found.
Partition: ID-1: / raw size: 109.51 GiB size: 107.29 GiB (97.97%) used: 30.74 GiB (28.7%) fs: ext4
dev: /dev/sda2 label: rootantiX19 uuid: 53a47157-cda3-42bc-8112-bf5deac42322
ID-2: /boot/efi raw size: 256.0 MiB size: 252.0 MiB (98.46%) used: 290 KiB (0.1%)
fs: vfat dev: /dev/sda1 label: N/A uuid: 26E1-EBB5
ID-3: /run/live-usb-maker/iso raw size: 8.46 GiB size: <root required>
used: <root required> fs: iso9660 dev: /dev/loop0 label: antiXLIVE
uuid: 2020-07-23-17-38-03-00
ID-4: /run/live-usb-maker/main raw size: N/A size: 14.62 GiB used: 6.00 GiB (41.0%)
fs: ext4 dev: /dev/sdb1 label: N/A uuid: N/A
ID-5: /run/live-usb-maker/uefi raw size: N/A size: 48.2 MiB used: 4.2 MiB (8.7%)
fs: vfat dev: /dev/sdb2 label: N/A uuid: N/A
ID-6: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 10 (default 60)
cache pressure: 50 (default 100) dev: /dev/sda3 label: swapantiX
uuid: 31e6ad28-ae85-451d-9e9e-7ae39f2d2fb0
Unmounted: Message: No unmounted partitions found.
USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 8 rev: 2.0 speed: 480 Mb/s
chip ID: 1d6b:0002
Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 4-2:2 info: Alcor Micro Hub ports: 4 rev: 1.1 speed: 12 Mb/s chip ID: 058f:9254
Hub: 4-2.3:3 info: Apple ports: 3 rev: 2.0 speed: 12 Mb/s chip ID: 05ac:1005
Device-1: 4-2.3.2:4 info: Apple Aluminum Mini Keyboard (ANSI) type: Keyboard,HID
driver: apple,usbhid interfaces: 2 rev: 2.0 speed: 1.5 Mb/s chip ID: 05ac:021d
Device-2: 4-2.3.3:5 info: Apple Mighty Mouse [Mitsumi M1152] type: Mouse
driver: apple,usbhid interfaces: 1 rev: 1.1 speed: 1.5 Mb/s chip ID: 05ac:0304
Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Device-3: 5-1:8 info: Apple Bluetooth HCI type: Bluetooth driver: btusb interfaces: 3
rev: 2.0 speed: 12 Mb/s chip ID: 05ac:8205
Device-4: 5-2:3 info: Apple Built-in IR Receiver type: HID driver: appleir,usbhid
interfaces: 1 rev: 2.0 speed: 12 Mb/s chip ID: 05ac:8240
Sensors: System Temperatures: cpu: 63.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http: //mirrors.rit.edu/mxlinux/mx-packages/antix/buster/ buster main nonfree nosystemd
Active apt repos in: /etc/apt/sources.list.d/buster-backports.list
1: deb http: //deb.debian.org/debian buster-backports main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http: //ftp.us.debian.org/debian/ buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http: //ftp.gr.debian.org/debian/ buster main contrib non-free
2: deb http: //security.debian.org/ buster/updates main contrib non-free
No active apt repos in: /etc/apt/sources.list.d/onion.list
Active apt repos in: /etc/apt/sources.list.d/softmaker.list
1: deb http: //shop.softmaker.com/repo/apt wheezy non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Processes: CPU top: 5
1: cpu: 1.5% command: gtkdialog pid: 4456 mem: 23.4 MiB (2.4%)
2: cpu: 0.0% command: init pid: 1 mem: 1.60 MiB (0.1%)
3: cpu: 0.0% command: [kthreadd] pid: 2 mem: 0.00 MiB (0.0%)
4: cpu: 0.0% command: [rcu_gp] pid: 3 mem: 0.00 MiB (0.0%)
5: cpu: 0.0% command: [rcu_par_gp] pid: 4 mem: 0.00 MiB (0.0%)
Memory top: 5
1: mem: 43.9 MiB (4.6%) command: xorg pid: 2388 cpu: 0.0%
2: mem: 23.4 MiB (2.4%) command: gtkdialog pid: 4456 cpu: 1.5%
3: mem: 23.1 MiB (2.4%) command: yad pid: 4569 cpu: 0.0%
4: mem: 14.3 MiB (1.5%) command: tor pid: 2543 cpu: 0.0%
5: mem: 6.81 MiB (0.7%) command: fluxbox pid: 2657 cpu: 0.0%
Info: Processes: 134 Uptime: 2d 4h 05m Init: SysVinit v: 2.93 runlevel: 5 default: 5
Compilers: gcc: 8.3.0 alt: 8 Client: shell wrapper v: 5.0.3-release inxi: 3.0.36

Any help would be welcome.

[Member anilkagi]

The stylisation, has been carried into the programming also. Rightly so, because a name is a name. If the OS has been named as ‘antiX’ with a capital X, then it has to be referred to as such. Thanks @Seaken64, for the analysis.

@Olsztyn, since I first noticed this thread of @Christophe, I had read a bit about extlinux, syslinux and isolinux on the web and was wondering if this method could be repeated with the same results using syslinux too, but didn’t have the knowledge and time to check that. Thanks for sharing your experiment with syslinux.

I had gathered this following info then. Just quoting it here for reference by other interested newbies who come here like I did.

The SYSLINUX Project is a suite of lightweight master boot record (MBR) boot loaders for starting up IBM PC compatible computers with the Linux kernel. EXTLINUX is a new syslinux derivative. EXTLINUX is typically used as a general-purpose bootloader, similar to LILO or GRUB. Since Syslinux 4, EXTLINUX has been merged with SYSLINUX. SYSLINUX is not normally used for booting full Linux installations since Linux is not normally installed on FAT filesystems. Instead, it is often used for boot or rescue floppy disks, live USBs, or other lightweight boot systems. ISOLINUX is generally used by Linux live CDs and bootable install CDs.

[Anonymous]

Xecure wrote:

You could also update/upgrade your live system before installation (as there is a newer minstaller version available). test things first with the newest version (you should always do that first before reporting).

1. I tried installing additional software on live antiX-19.2_x64-full.iso (sysVinit, not runit) but nothing happened (except a glitch?), so I (mis)concluded that antiX live is a still/frozen image by default.
2. I am unfortunate to have internet of worse-than-3G crawling pace, big downloads are an endeavour. I am lucky to have any internet, mind.
3. My RAM is 3 GB, I boot ‘toram’ since there are limitations on keeping boot medium plugged in (-1 GB), so for big updates/upgrades I may run out of memory.
4. I would gladly use piping hot install iso, but 5 months old 2020-03-27 is the most recent date for runit.
Please excuse me my not being on the edge and susceptibility to wrong conclusions.

I have updated live antiX and upgraded antix-installer and cli-installer-antix – no better.

Brian Masinick wrote:

Regarding partitions, if you create separate partitions and mount points you can do it.
Not 100% certain that there is a convenient time to do this but it may be possible to do it as the distribution partitions are selected.

What do you mean by ‘convenient time to do this’?

anticapitalista wrote:

2. What if you choose the root partition first?

The same, as well as for swap: opting sda10/sda11/… for root/home/swap removes sda1 from the list for boot. sda9/sda8/… do not conflict with sda1

anticapitalista wrote:

4. We can fix that – no need for sarcasm. The figures 3.5GB and 5GB refer to base versions that also use the gui installer.

I had no idea that I was being sarcastic. Probably, we interpret smiles differently. Maybe my soul was removed to make room for sarcasm.
Please don’t get hurt.
btw,

Sarcasm is the lowest form of wit. Yet it remains the funniest!

Tact is for people who aren’t witty enough to be sarcastic.

anticapitalista wrote:

Seems strange that you complain that the installer does not offer all the fine tuning re partitions, yet you chose auto-install, which is obviously not going to give you all what you want.

1. This is not a complaint. This is a ‘bugs and questions’ post.
2. I made auto-install to see what it would yield. I have not kept that auto-install – that was a trial start, I am still on live antiX

Trying to install antiX-19.2-runit_x64-full.iso

1. My initial intention was having separate

/tmp
/var
/var/log
/usr

partitions but antiX Linux Installer will not allow for my wish.

I thought that the cli-installer might be flexible enough, but it says from the start:

This installer does NOT offer encryption

Is there a way to fulfill partition separation?

If I install antiX without additional partitions, and after installation manually edit /etc/fstab and put directories’ contents via tar(1) or cpio(1) to additional partitions, for example:

# (cd /var && tar cf - .) | (cd <future-var-temporary-mount> && tar xpf - ) \
&& rm -rf /var \
&& mkdir /var \
&& mount -a   # provided that /ets/fstab is prepared

will it work without breaking the system?
Or am I advised to not tinker arbitrarily, accepting the default install layout?

2. antiX Linux Installer
Custom install on existing partitions
I chose boot location to sda1

then home location to sda10

boot location dropped to root
check drop-down list – sda1 is not displayed

change home location to sda9 – sda1 for boot location is available again



try sda10 for home again – boot drops to root again

I have played with it and it seems that sda9 and below for home do not affect presence of sda1
but sda10 and above for home hide sda1 from drop-down menu

3. bug? in antiXscreenshot:
want to shoot a drop-down list,
Region to capture – Window
set Delay to e.g. 1 (or leave the default 5) counting that it will provide time for drop-down menu to be displayed
press OK in antiXscreenshot
press on drop-down list in the target window – screenshot is taken immediately regardless of delay and drop-down menu is not activated

4. antiX Linux Installer of antiX-19.2-runit_x64-full.iso says:

Installation requires about 3.5 GB of space. 5 GB or more is preferred.

But after auto-installation Gparted reported that 7+ GB are used on / partition.
Send me a screenshot of 7+ GB successfully crammed into 3.5 GB 😉

5. antiX Linux Installer’s auto-install created a 2 GB swap partition whereas my laptop has 3 GB RAM (2 GB + 1 GB). I would expect swap to be 3+ in my case.

6. Samba option present in antiX Linux Installer is grey = unactivatable

[Moderator christophe]

I ran ito this problem a while back, too. https://www.antixforum.com/forums/topic/version-19-2-core-isos-hang-on-first-boot-in-virtualbox/#post-34650

If I remember right, once I installed X, I then installed virtualbox guest X-server — or maybe some x guest addition thing? — from cli-aptiX. (It was a while ago, and the VM is erased now.)

But others don’t have the problem, so maybe it depends on the video hardware?

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

confirmed antiX frugaler, since 2019

[Member anilkagi]

Thank you Xecure for resolving the issue.

The failsafe boot succeeded.

I searched the forum with error terms i.e. “live-restore-services: restoring service links”, and got nill results and then a startpage search yielded this.

There I took Dolphin oracle’s suggestion “this is odd, and may indicate a problem with your media.” and downloaded another ISO. When that too failed I browsed through more startpage search results but couldn’t find any related discussion, so had to post. I did not know what is a failsafe boot till now and I don’t know much of what other options mean on the boot screen, so I had to take the guidance of someone knowledgeable in the matter.

Thanks again for coming and suggesting a solution. I will mark this thread solved, though this is the same issue discussed in the link you provided but the title of this thread is more relevant and close to the issue I suppose and would be easy for others searching for solutions to the same issue.

[Member PDP-8]

I see all the latest FreeBSD’s have been picked up by the latest Ventoy.

But thing is not to get too concerned about the ext2 filesystem, as that is really only meant to be used for Ventoy’s own purpose of storing and launching the iso’s.

The idea is to use Ventoy solely as a distro installation-launcher, where one puts the “real thing” on some other filesystem using that multiboot stick.

If one does desire to use Ventoy as a working environment, then unless your distro fully supports ext2 out of the box, set up persistence on some other physically different filesystem format.

Interesting times.

Hello there,

I am trying to install antix-19.2-x64-core on VBox, but the installation is stuck at;

live-restore-services: restoring service links

I thought the ISO image may have some issue and so I downloaded another ISO file from a different mirror. I have verified the md5sum, sha256sum and the signatures of both the ISO images that I have downloaded. The are fine.

I have not changed any F4 or F5 options. I have done a regular boot.

I have installed antiX-19.2.1-x64-Base on the VB, and it is working fine.

I don’t know what is happening? Please guide.

Thanks & Regards

• This topic was modified 2 years, 9 months ago by anilkagi.