Search Results for 'boot from iso'

[Member xinomilo]

i don’t think it’s kernel/laptop age related, cause i got another hdd with devuan ceres installed and kernels 5.6 (linux-libre) running without issues.
i know 5.5 has/had? issues with intel drivers, cause i had some freezes with 5.5 kernels from linux-libre and antix. (see here : https://dev1galaxy.org/viewtopic.php?id=3361)

also just verified iso md5 checksum, it matches the downloaded iso. and, forgot to say, i got the same issue with booting iso from qemu.

[Member xinomilo]

hey & thanks for providing these isos.

got some time today to try this sid+runit iso..
unfortunately i couldn’t get to login screen *unless* i used option f7 -> ask -> 303 on boot screen (800*600*8 vesa). default option (1024*768) and other options during
boot would show “waiting for dev to be fully populated”, and then nothing, just a black screen, without responding, till a hard poweroff.

it’s an older thinkpad from 2011, but was booting fine every other antix version. also booted and installed antix 19.2 stable without issues.

wanted to try 1600*900 since this is laptop resolution, but then i get “undefined video mode number : 3d4”..

—

another thing, when choosing “toram”, it would start copying-progress, then throw this: “bash: write error: Invalid argument”. then report copying to ram finished succesfully..

—

something minor i’ve seen in other antix versions also, is “nofail” option for encrypted swap partition. i think it’s deprecated even for stable version, maybe it should just go away in the future.. (?)

thanks,

[Forum Admin anticapitalista]

I can’t get it to work either when using any bootloader on live-usb to boot the frugal install on a hard drive.
However, I did find out that it is not due to it being frugal on a ntfs partition.

I can boot frugally with the kernel changes if I have grub installed to hard drive.

Here is my setup.

antiX installed on sda1 (ext4) running grub.
sda2 is ntfs with a frugal install of antiX (in a folder renamed to antiX-test) and, via live-kernel-updater, running a 5.5 antiX kernel.

This is the entry in my sda1 grub

menuentry "antiX-64-buster-runit frugal on ntfs" {
set root='hd0,gpt2'
linux /antiX-test/vmlinuz bdir=antiX-test bdev=sda2 persist quiet nocheckfs nostore disable=lx 
initrd /antiX-test/initrd.gz
}

However, adding the above to the live-usb stick’ grub does not work.

Using fdev=sda2 and fdir=antiX-test cheats, does boot the frugal install via the live-usb, but it uses the vmlinuz and initrd.gz of the live iso and not the one on the frugal install.

The might be a way to get grub, syslinux, isolinux to use the vmlinuz and initrd.gz from the frugal install with clever boot codes, but I couldn’t get it to work.

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

antiX with runit - leaner and meaner.

[Member VW]

The weird thing I found is that while I can’t boot antiX on my intel Atom device, I can boot, and use MX. Both ISOs were made with USB maker.

I confess I am sorely tempted to install MX and then, once Windows is gone, maybe antiX will load.

The error message states:

Limpus Lite boot failed!

• This reply was modified 3 years, 1 month ago by VW. Reason: Added error message

“These are the times that try men's souls" - Thomas Paine

I made a previous post on this subject. But it disappeared after an edit.

After trying a liveUSB of bare Antix19, I decided to upgrade my existing 32 bit Antix 17.4.1 system, by following the steps shown in the post “Upgrading antiX-17 to antiX-19”.

Step 5 is apparently no longer valid with the isos available now (since March 27) according to other posts. This step should be edited, to show that it is only needed with older isos. (This caused confusion, because apt-get complained that libpam-elogind-compat could not be installed, due to a held program, As far as I can see, there is no held program. But until discovering that elogind was no longer an issue, I was stuck.)

Unfortunately, my initial attempt was interrupted, and failed because I accidentally skipped the final step
“apt-get install –reinstall desktop-session-antix”
The system appeared to boot, but the desktop never came to life.

My question, in the post that disappeared, was whether there was a way to recover from my mistake.
When the post disappeared, I decided the quickest cure was to re-install Antix 17 from backup (did so successfully), and to try the upgrade steps again, more carefully.

I did so. Things appeared to progress well. The process completed successfully. But upon reboot,the system behaves just the same… it appears to be booting up, but the desktop never opens.

I was hoping to avoid starting from scratch with a bare system. But maybe that’s all that remains.

Your suggestions will be appreciated.

When running 19.2 core 32-bit iso (both regular & runit) in Virtualbox 6.1.2, the boot hangs just before X starts, at “live-restore-services: restoring service links.”

I gave it a bit of time (a minute or two), pressed enter key, but still nothing. I’m thinking this may be a bug?

• This topic was modified 3 years, 1 month ago by christophe. Reason: marked topic solved

confirmed antiX frugaler, since 2019

Hi Friends!

I rarely use Windows but I always make my laptop a dual boot system. It seems that no matter what I do I can’t install windows 10.

I’ve tried different flash drives to install. Different iso’s. I tried MBR installation when the hdd was still of the MBR partition style. Then I formatted the entire

hdd and converted it from MBR to GPT, and tried GPT installation as well. No success.

It would always be stuck on the windows 10 logo.

Upgrade from a previous windows version is out of the question. Don’t ask why.

My machine, if it matters:

Machine:
Type: Laptop
System: SAMSUNG
product: R439/R478
v: N/A
Mobo: SAMSUNG
model: R439/R478
BIOS: Phoenix
v: 00UN.M001.20100814.LEO
date: 08/14/2010

Is it possible that the motherboard and/or BIOS/UEFI just isn’t compatible with Windows 10?

The BIOS is old style, like navigating and selecting and choosing are done with keyboard only. You can’t use a mouse.

Thank you for your time!

• This topic was modified 3 years, 1 month ago by kaye.
• This topic was modified 3 years, 1 month ago by kaye.

[Member kultex]

I was wrong – the remaster tool does not work with GPT-mode (UEFI-mode). I can boot on the Lattepanda only, when I flash the antiX image with rufus in GPT-mode, because I am not able to turn off uefi mode on the Lattepanda.

anticapitalista – maybe you can provide a iso with 4.19 antix kernel for testing…..

in the meantime, I think, there is a way on the lattepanda, that I can boot it warm – I have to flash the bios back to the original bios….

[Moderator BobC]

Brian, thanks for taking the time to think it through and enter it all.

I am doing Ok adding packages, making minor changes, remastering, making an ISO and running it from flashdrive, but I can’t get it to install normally. It skips the user id/passwords prompt screen on the install.

What I am trying to end up with is an ISO that can be downloaded, burned to a flashdrive, booted, run from flashdrive as demo/root (with or without persistence) and then installed to a hard drive as your own user with your own user and root passwords. That way I can give someone the ISO to install.

I have been doing it as “personal” rather than “general” while on as demo. Maybe that is causing my problems…

[Member kultex]

@PDP-8

I will boot from USB, because my Atom have all 3.0 USB and I want to put /home to the SD-Card. But I am interested, to make an Iso, that boots also from internal eMMC, to get new life for those 1 or 2 GB Windows tablets.

To use internal eMMC for /home is not recommended, because if the eMMC or the device crashes, your data is lost……

So I used my packagecomp and aptik to migrate my tweaks to a fresh flashdrive (really a fast USB SSD), and then used the persistence and remastering to make it into a bootable system which I think will also install, etc. It’s oriented to IceWM, but the other desktops are still available. Here are a few screenshots. I got things like Window driven Helpnotes and my wallpaper modifier working, and only rarely use the menus because the programs I use often are all on the toolbar, which autohides out of the way until you mouse to the bottom of the screen or press a key like Ctrl+Esc to bring up the menu. I only created a 64 bit system at this point. If there is any interest, I’ll figure out how to make an ISO of it and post it. I’m running it from flashdrive only at the moment.

• This topic was modified 3 years, 1 month ago by BobC. Reason: change title
• This topic was modified 3 years, 1 month ago by BobC.

Attachments:

1. 

   antiX19bc1.jpg
   

2. 

   antiX19bc2.jpg
   

3. 

   antix19.1bc_3.jpg
   

Just a question: antiX Snapshot in repos appears to not have been maintained since 2013. Has this been superseded by ISO Snapshot or this is another utility?
My question arises from my search for a perfectly working antiX snapshot utility. ISO Snapshot, otherwise mostly excellent, has a bug that restored system fails during boot on the step to copy existing content of Home, when hope persistence is specified on boot screen…

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

[Member olsztyn]

BobC wrote:

all my configuration changes were lost. My programs installed did remain, the setups were lost.

Pardon my Linux ignorance or lack of understanding of issue… I thought it is the responsibility of ISO Snapshot utility to faithfully ‘snap’ a fully configured system, for the purpose of restoring it on new hardware. Therefore I would appreciate if someone enlightens me why we need to resort to manual porting /etc/skel if such ‘simple’ task is expected to be fulfilled through ISO Snapshot…
In all my apparent misunderstanding of the goal to be accomplished here I brought up: ISO Snapshot in my testing faithfully restored to new environment both all customized software and custom settings if no home persistence was not requested in the new environment. Preserving custom settings only failed when the new environment was booted with creating new homefs with error on copy step. Custom installed programs were carried over to new environment in either case.
So I would appreciate someone explains why need to resort to customizing /etc/skel if carrying over custom settings is already done in ISO Snapshot…

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

[Moderator BobC]

dolphin_oracle wrote:

if you are talking about desktop type settings, you can sync up the configuration files from your user to same location under /etc/skel.

just be aware that if anti pushes any updates to desktop-defaults-*** packages that they might override your changes. On MX its safe to remove the desktop-defaults-mx-xfce-desktop package but I’m not sure what’s germane on antiX.

I put my .icewm changes in /etc/skel before I made the ISO-Snapshot, and made the snapshot for distribution, and then burned the USB, but when I booted to it and then installed it, all my configuration changes were lost. My programs installed did remain, the setups were lost.

The only thing left that I can think of would be to do all my changes without installing, and then remaster?

[Member olsztyn]

BobC wrote:

There is nothing wrong with what the USB it created, as it boots and all the programs and such are there, including what I added, but I am trying to figure out how do I get it to include all the configuration tweaks that I made instead of looking like standard antiX with my added programs?

This is something I attempted recently and after lots of testing determined the following:
– Live USB created from ISO snapshot (using LUM) preserves all the custom settings in the resulting Live USB as long as when booting such Live USB you do not specify Home persistence, just leave all as is.
– If during booting such Live USB any Home persistence is specified (such as for the purpose of changing previous custom settings or retaining data) antiX fails with an error on the step to copy existing Home data to newly created homefs.
This was reported in threads:
https://www.antixforum.com/forums/topic/live-usb-maker-error-creating-live-usb/

https://www.antixforum.com/forums/topic/iso-snapshot-defect-or-limitation/

I do not know if this bug has been fixed yet as I got around this issue by falling back to the older version of Live USB Maker and to cloning Live USB instead of using ISO snapshot.

• This reply was modified 3 years, 1 month ago by olsztyn.

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