Search Results for 'boot from iso'

[Member sybok]

Hi,

pragmatic temporary workaround: borrow a USB mouse, if possible.
But most importantly, please, do provide more information about the antiX version and your HW for more skillful forum members.

0) Verify integrity of the ISO download (checksums, e.g. ‘sha256sum <ISO filename>’ and compare with the value available at the download links).
If it differs, your download got corrupted and you need to download and create the live media again.
1) Which ISO do you use (post e.g. the filename)?
2) Which kernel did you boot into (output of ‘uname -a’; antiX contains an older and a newer kernel to cover wide range of HW)?
3) HW info – output of ‘inxi -Fxz’ when running live or at least description of your HW.
You can redirect to a file ‘inxi -Fxz > ~/INXI.txt’ and copy this file.

[Forum Admin anticapitalista]

Thee is no automatic replacement of elogind/libelogind when dist-upgrading antiX-21.
The main reason for this (and why I built a new iso antiX-22) is to avoid any possible breakage.
Some antiX-21 users might be running lxde for example which *needs* elogind (not just libelogind) to be running othewise the lxde logout menu will not have all the features (reboot, halt, suspend) etc.
Now, it is possible to run lxde without any elogind component and use the usual antiX logout scripts, but it is not my choice to force it on users.

The vast majority of antiX-21 users should be able to manually convert to it being elogind-free by following these instructions.

https://www.antixforum.com/forums/topic/removing-libelogind0-testers-needed/

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

antiX with runit - leaner and meaner.

Hello,

I installed the 5.19.0-16.2-liquorix-amd64 kernel on an anti21 system that has the 5.10.142-antix.2-amd64-smp kernel. I have been able to make many bootable iso snapshots in this antiX21 system prior to installing this newer 5.19 kernel.

I searched the forum and found a thread that is similar to this problem, although in that thread @manyroads did not have a kernel change.

https://www.antixforum.com/forums/topic/snapshot-fails-to-boot-a-little-help-needed/

But the error message during boot is the same:

Fatal error

neither aufs nor overlayfs is available:

and it asks to either power off or reboot.

I have iso-snapshot-antix 0.4.14 and iso-template-antix 20.09 installed.

When the liquorix kernel installed, it created these boot codes:

current boot codes: audit=0 intel_pstate=disable hpet=disable rcupdate.rcu_expedite=1 BOOT_image=/antix/vmlinuz quite

This is the first time I am seeing this. I don’t know how to get around this.

Thanks for your help.

• This topic was modified 6 months, 3 weeks ago by calciumsodium.

Hello.
I am not able to boot ‘antiX-21’ from the welcome screen
‘Welcome to antiX-21 (Grup Yorum)!

error: /antiX/vmlinuz has invalid signature
error: you need to load the kernal first

Error occurs with ISO download packages: base, core ,full x64.
created as a live USB using Rufus or MX21 Live USB maker.

For antiX-21_x64-base.iso
I used MX21 ‘Live USB kernal updater’ to check antiX kernal but a new kernal was not found for 4.9.0-279~

I use an HP 250 G6 Notebook, Dual Core model: Intel Core i3-6006U bits: 64 type:
I use MX21 on a live USB on this laptop and want to try AntiX.

Is there anything I can do to get antiX to boot?

I have looked on the forum without success.
Thank you

[Moderator Brian Masinick]

techore wrote:

Helpful

Up

0

:: @olsztyn, I am in a agreement with you and suspect your hypothesis is correct.

In developing both iso-snapshot and live-usb-maker-gui, choices had to be made. Using grub2 and ext4 is consistent with antix-base and it is unreasonable and, probably, impractical to expect my preferences for rEFInd and BTRFS to be supported.

A couple folks expressed interest in an ISO of my antiX-DWM Respin which led me to explore iso-snapshot. I may focus my time and energy with an installation script to simplify installation. Undecided, but this was time well spent.

Thank you!

I applaud your comments and your general attitude.

I think it’s great to be able to do things in whatever way that you want, and that’s exactly why we have the great tools that allow you to image, create, modify, change, and ultimately remaster in whatever way suits your particular interests, so the team definitely does have our interests in mind. At the same time, with such a small team, and also with specific “lean” distribution goals, it isn’t reasonable to offer every possible boot loader, application, etc. etc. for each of us. What IS available are great tools to add things (whatever you want) to the distribution, and if you so choose, also a way to remaster them so that when you boot it, you can use it live, install it, run it Frugal, or any of the other ways – including the creation of your very own methods, applications, tools, and preferences.

I also think you know these things; best wishes with whatever you decide to do with the wonderful flexibility our distribution offers, including the replacement of various apps with whatever you prefer (then you manage and own it 100%).

Best wishes; enjoy the lean defaults plus the great variety possible with antiX!

--
Brian Masinick

[Member Robin]

Please, let us see a screenshot.

Basically: Whether the script shows greyed out entries or not depends whether there exists a nested mount on this drive, which means: A file (e.g. iso or e.g. linuxfs, homfs or rootfs in antiX live) living on this drive is mounted itself to a mountpoint, so the base drive can’t be unmounted as long these nested mount is not unmounted before.
This is one of the many bugfixes present in this version. All the other unplugdrive versions before didn’t care for this issue, allowing the user selecting drives which technically can’t get unmounted for some reason.
So it should not be greyed out for drives other than e.g. the antiX live USB boot medium.

Permissions should be the same as all other files in the /usr/local/bin folder, which is 755. So your command was probably fine. Owner should be root:root, just like all the other files living there.

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

[Member Robin]

In other words: The x64 iso is fine for both of the two your machines you’ve told us about. All isos are prepared to automatically come up on both types of processors, amd and intel. During live boot it will try to configure on its own everything needed, and you can use the very same medium (USB, DVD) on both machines alternatingly. In case it doesn’t come up properly, just post the issue and people here around will try to help you bring it up anyway, there are some methods (including but not restricted to special boot codes for circumventing common problems) which can be applied in this case. So if you ran into such problems, please give as much detailed information along with your concrete question you can make possible, e.g. screenshots or text copies of screen output, along with the console output (if possible) of
sudo inxi -Ffzjrv6 --zl -t cm
and
sudo dmesg
which will be helpful for finding out where’s the rub, and let people know the very moment the startup process stops.

But all this shouldn’t be needed at all, by default the iso should come up fine.
If not, you might try another antiX generation (e.g. 19 instead of 21, or even 17) on some specific hardware. This is due to the fact, that some code needed for specific hardware has been removed either from linux kernel or from some programs antiX relies on or includes, during the last months and year by the program authors or kernel developers. Also the addition of code for new hardware sometimes breaks the functionallity of older hardware unwanted and unnoticed by the devs.

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

[Member Robin]

stevesr0 wrote:

its boot directory including the efi/bootmgfw.exe file is gone.

OK, your posting wasn’t there when I started writing my lengthy advisory above.
And yes, this was my first guess, your windows must have been damaged in some way, otherwise it would have come up via early boot selector menu provided by bios/uefi.

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

[Member Robin]

stevesr0 wrote:

I made the Windows boot manager the initial selection, …

In my understanding this implies: Windows is installed on a second physical drive. Is this assumption correct?

stevesr0 wrote:

…first trying this with F12, then by going into the UEFI Boot menu and altering the order of the boot drives.

Then this implies something is wrong with the windows hdd boot sector itself. (Maybe you’ve managed unintentionally to install a grub there also, overwriting the windows bootsector of this drive) Otherwise using the direct boot to a specific physical medium via selection during startup must boot from the windows drive, whithout seeing the grub on the other hdd at all. Make sure you’ve set BIOS or UEFI to “don’t try other boot devices”. When booting this way it should display something like “no OS found on boot medium found” if it can’t start windows for some reason, instead of automatically booting from the next drive (which contains grub boot loader). You could even try to disable the second hdd completely in BIOS for testing purpose, or plug it off physically for this test. Then Windows must come up, otherwise the Windows installation is damaged and needs to be fixed in the first place. So repair the windows installation.

After you’ve made sure windows can boot when the second hdd is not present, then plug in, add or activate the second hdd containing linux and grub bootmanager again. Check that you can boot into windows still when using the early boot selector provided by BIOS/UEFI. If this works, boot to the second boot medium containing grub and linux the same way.

Now you need to make grub aware of this windows system on the other hdd. For this it is crucial to have this windows and efi drive properly in your fstab, so it can be seen by the grub menu config tools. Try mounting both of them using the ntfs and vfat mount option, e.g. sudo mount -t ntfs … and sudo mount -t vfat … for the efi partition.
Make sure your grub.cfg in use (or /etc/default/grub) contains the string GRUB_DISABLE_OS_PROBER=false. You need to update-grub or grub-mkconfig -o /path/to/grub.cfg to copy the changes to your grub.cfg, it should recognise the windows install on the other hdd and add the respective entry to the grub menu now.

If grub still doesn’t recognise the windows on the other hdd, you can try to add a chainload manually to the grub.cfg

menuentry "Windows" {
insmod part_gpt
insmod chain
set root=(hd0,gpt1)
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}

where the entry behind set root= is to be set to your actual findings, it must point to the efi boot partition, not the windows partition itself. You can get the proper partition and drive naming as grub sees it during boot, when entering grub console while startup and use the ls command in it. Refer to grub manual for details about naming convention.

If no efi partition present, and windows runs plainly on ntfs the entry would look like this:

menuentry "Windows" {
	insmod chain
	insmod ntfs
	set root=(hd0,1)
	chainloader +1
}

Also here you need to modify the values behind set root= to your actual findings. But no idea whether the modern windows versions will accept this way without efi, this is how I did id for Win2000/XP systems long ago. Anyway, it’s worth trying.

Don’t forget update-grub or grub-mkconfig -o /path/to/grub.cfg always after manually editing the grub config to make the effects take place in the boot menu.

Some more knowledge about grub2 configuration you’ll find in this advisory, it doesn’t care it’s from ubuntu, the concept is identically for all debian derivates.

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

[Member ModdIt]

Hi Techore,
in the full antix version there is a tool called ISO snapshot which will
enable you to create a bootable ISO image of your freshly created installed system.
ISO snapshot is a binary not a script and located in /usr/bin. I have not investigated
what it relies on to work, aka depends.

The remaster tool will only do just that, remaster a live system incorporating changes
in to the Live USB and is good after major changes or updates. Keeps the system tidy and
your boot time at optimum. Persistence is way slower.

There is a menu point in the remaster tool for cloning a running system. It has never
worked over last couple of years. Possibly unfinished or overtaken by system changes.

[Moderator christophe]

Hi ozgurilgin,

No new video that I know of. It works the same way since then.
Which software did you use to make the live-usb that you are using?
In addition to that first question, please describe in detail the exact steps you are taking from the bootup onwards, which version of the ISO file is on your live-usb, and how your live system is behaving, and what you are expecting. All in lots of detail, so we can help you.

• This reply was modified 7 months, 3 weeks ago by christophe.

confirmed antiX frugaler, since 2019

I wanted to compare the different iso snapshot compression algorithms in antiX.

For my test system, I am running antiX21 32 bit live from a 650 MB CD on an i3 computer with 4 processors. The iso was originally created using an xz compression method. This iso snapshot, when installed on a hard drive, will take up about 2.2 Gb of space.
For every test, I boot up live and start the iso snapshot compression process. After the test, I determine the iso snapshot size and then reboot live again to start the next test.

This is what I found:

Compression
Method            Time             Iso size          Max CPU %

lz4              5 min 57 sec      1.021 Gb          28 %

lzo              6 min 35 sec      820 Mb            100 %

gzip             6 min 24 sec      748 Mb            100 %

xz               8 min 39 sec      644 Mb            100 % (most of the time was 100%)

zstd  (current kernel doesn't support selected compression algorithm)

The xz method gave the best compression, but it took the most time and the most cpu power.
The lz4 method gave the least compression, but it took the least amount of time and did not use much cpu power.

This is my test system:

$ inxi -b
System:    Host: antix Kernel: 4.9.0-294-antix.1-686-smp-pae i686 bits: 32 Desktop: IceWM 2.9.6 
           Distro: antiX-21_386-base Grup Yorum 31 October 2021 
Machine:   Type: Laptop System: Hewlett-Packard product: HP ProBook 6550b v: N/A serial: <superuser required> 
           Mobo: Hewlett-Packard model: 146D v: KBC Version 73.11 serial: <superuser required> 
           BIOS: Hewlett-Packard v: 68CDE Ver. F.00 date: 04/21/2010 
Battery:   ID-1: BAT0 charge: 9.5 Wh (28.6%) condition: 33.2/55.1 Wh (60.4%) 
CPU:       Info: Dual Core Intel Core i3 M 350 [MT MCP] speed: 933 MHz min/max: 933/2266 MHz 
Graphics:  Device-1: Intel Core Processor Integrated Graphics driver: i915 v: kernel 
           Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.3.5 
Network:   Device-1: Intel 82577LC Gigabit Network driver: e1000e 
           Device-2: Intel Centrino Advanced-N 6200 driver: iwlwifi 
Drives:    Local Storage: total: 0 KiB used: 0 KiB 
Info:      Processes: 160 Uptime: 11m Memory: 7.7 GiB used: 2.44 GiB (31.7%) Shell: Bash inxi: 3.3.06 

• This topic was modified 7 months, 3 weeks ago by calciumsodium.
• This topic was modified 7 months, 3 weeks ago by calciumsodium.
• This topic was modified 7 months, 3 weeks ago by calciumsodium. Reason: Should be 1.021 Gb instead of 1.021 Mb

[Member calciumsodium]

Maybe step (8) make a new iso snapshot of this new system with the elogind free version of piperwire. Then save a copy of that snapshot iso before rebooting or shutting down. Then use the live usb maker to create the live usb of the new iso that contains the elogind free version of pipewire.

• This reply was modified 7 months, 3 weeks ago by calciumsodium.

[Member stevesr0]

UPDATE: I now am listening to music through Pipewire sound server on an antiX Sid live usb WITHOUT elogind.

LIMITS: It is on a particular customized/limited Sid system, that I might have trouble replicating.

How: (1) I cloned my installed Sid system that was successfully running Pipewire WITH elogind using
iso snapshot-cli.

(2) I made a live-usb of this snapshot.iso using live-usb-maker.

(3) I launched the live-usb on my Sid machine.

(4) I removed libelogind0, which removed my pipewire (and wireplumber) packages and elogind and libpam-
elogind.

(5) I downloaded the elogind free version of Pipewire packages that anticapitalista provided on 23 August.

(6) I used dpkg to install the debs.

(7) I started listening to music. (On VLC, the audio devices list Pipewire sound server as the selected
device.)

Caveats: I did not reboot between removing the old Pipewire packages and installing the new ones. I would like to make sure it survives a reboot, but I didn’t see an opportunity in iso snapshot or live usb maker to make persistence. Either I missed it (very likely) or when you launch live usb maker to use a snapshot iso, it doesn’t offer that choice.

I plan to leave my machine on for the rest of the day, hoping for advice from those knowledgeable about saving the changes. At worst, this went so easily, I could repeat it.

So, I hope people read this and ask questions and offer suggestions.

If any are interested in the limitations and “features” of my minimalistic installed system, I will be happy to discuss it. I am sure it can be improved, but it has been a fun toy so far.

stevesr0

[Forum Admin rokytnji]

Base iso is what I* ran eeepc on eeepc 701sd 4 gig drive back when I had a eeepc.

Then later on used a external sd card for the /home partition. Auto mount and used during boot up.

There is no current how to on how to do this.

Since I sold or gave away my eeepc’s.

https://antixlinux.com/forum-archive/how-to-install-antix-onto-a-sd-card-on-a-eee-pc-70-t3757.html

Also. The eeepc.com forum with all it’s useful links is now gone and is history. Lost a lot of good info there.

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