Search Results for 'boot from iso'

[Member Xecure]

rayluo wrote:

I guess I’d have to stick with my otherwise battle-tested 19.2 customized liveUSB for a longer time.

You can always update and remaster and keep using the 19.2 version now fully updated.
Beware of new firmware updates, in case it creates a regression.

About the snapshot issue, I don’t know how to solve (probably anticapitalista’s suggestion), but on the live USB issue, you can simply edit /live/boot-dev/boot/ and replace/edit some of the files there.
I would replace the grub folder with the one on antiX 19.2 iso and add the “switch to Grub bootloader” entry to syslinux/isolinux, copying it from the syslinux/isolinux config (or simply replace the whole boot folder. Justin case, make a backup).

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

[Forum Admin anticapitalista]

You need the latest versions of iso-snapshot-antix and iso-template-antix. See known issues from the release notes: antix-19-3-manolis-glezos-bug-fix-upgrade-isos-available

If you edit /etc/iso-snapshot.conf, and change edit_boot_menu=no to yes, then during the snapshot proedure, a popup appears for user to add the title of the snapshot (plus some other things). Is this broken, skidoo?

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

antiX with runit - leaner and meaner.

[Member rayluo]

Anonymous wrote:

I suggest we not attempt to test and/or troubleshoot using 19.2

> creating an ISO snapshot with or without the custom name,
> would cause that “switch to grub bootloader” menu entry to appear

Testing on 19.3, “switch to grub bootloader” was successfully present on every test variation.

Sure, I’ll pick up antiX 19.3 sooner or later anyway, so, it is fine to do it now. And, 2+ hours later, the test result is – drum rolls – indecisive.

* I download official antiX 19.3 64 bit full and net ISO, and 19.3 32 bit net ISO. And I even managed to find and download the official antiX 19.2 32 bit full and net ISO. When booting, they ALL present that menu entry “Switch to Grub Bootloader”. So, it is not about the antiX version. And it is likely something during my ISO snapshot creation procedure.
* Then I use my same procedure to create a new customized 19.3 ISO snapshot:

rayluo wrote:

1. Download official antiX 19.3 64 bit full ISO, create a pristine antiX 19.3 liveUSB. Use it to reboot my computer.
2. It is probably unnecessary, but I still plug in an ethernet cable, in order to avoid creating-and-leaving some WiFi settings into the new ISO snapshot that I’m going to make.
3. Install the very few tools that I need: Git, Vim, Mosh, Chromium.
4. Create a snapshot immediately. Gives it a filename suffix “gvmc”.
5. Run the liveUSB maker immediately, using the newly created custom ISO snapshot, and create my customized liveUSB.
6. However, the LiveUSB maker would FAIL with FATAL ERROR: Failed to open exclude file "/usr/local/share/excludes/iso-snapshot-exclude.list" because No such file or directory. I never saw this happened before during my 2+ years with antiX liveUSB maker, but I managed to bypass it, by manually copying an existing remaster-snapshot-exclude.list into iso-snapshot-exclude.list and then liveUSB maker becomes happy.
7. Reboot with the new customized liveUSB.

Guess what?
* No “Switch to Grub Bootloader” is displayed. (This is not really a surprise to me now.)
* And then I chose the first menu entry, trying to simply boot the new customized antiX 19.3. Now I see something I do NOT expect:

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
...

and the my computer halts.

Feel free to redo my steps above, to keep me honest.

I guess I’d have to stick with my otherwise battle-tested 19.2 customized liveUSB for a longer time.

[Anonymous]

Skidoo, did you mean

I suggest we not attempt to test and/or troubleshoot using 19.2

> creating an ISO snapshot with or without the custom name,
> would cause that “switch to grub bootloader” menu entry to appear

Testing on 19.3, “switch to grub bootloader” was successfully present on every test variation.

> by “custom name”, did you mean the filename you chose when saving the ISO snapshot?

Yes, by editing YYYYmmddHHMMSS in the entrybox displayed within the iso-snaphot dialog.
Regardless the specified namestring, it is rejected and the resulting bootmenu entry label displays a fallback “antiX” string (without datetime)

[Member rayluo]

Thanks for keeping the momentum on investigating, gentlemen!

Anonymous wrote:

the DATE shown in bootmenu misled me to think that was a pristine 19.2 iso, but it was not. It was a 19.2 iso created via isosnapshot.

Water over the bridge ~~ whatever was what back in 19.2, I retested using fresh 19.3, created a fresh snapshot iso and booted that. Yes, the “switch to grub bootloader” menu entry is displayed, even booting the snapshot iso,

Skidoo, did you mean that, creating an ISO snapshot with or without the custom name, would cause that “switch to grub bootloader” menu entry to appear or disappear? 😮 And, by “custom name”, did you mean the filename you chose when saving the ISO snapshot?

I haven’t used the ISO snapshot tool since last 4+ months, so I am not currently sure, but I believe the default ISO filename contains a YYYYmmddHHMMSS pattern, and then I did change it into a more meaningful (to me) “gvmcf” suffix.

Xecure wrote:

I just tested this out on my laptop, and after making changes in Legacy bootloader and saving (F8), after rebooting I still can see “Switch to Grub Bootloader”.

I think the other possibility is that a previous snapshot version could be to blame. I never realized if there was any problem before as all my remaining computers are UEFI systems.
Maybe rayluo can tell us how he created his live system, and if it comes from a snapshot or from live USB created with Live USB maker or some other tool.

My liveUSB is NOT from the official ISO. It is from my customized snapshot. But my customization process is straightforward, and probably reproducible.

1. When the then-new antiX 19.2 version comes out, I would download its official ISO, and then use the liveUSB tool of my existing antiX (typically the prior version, such as 19.1), to create a pristine antiX 19.2 liveUSB. Use it to reboot my computer.
2. I probably just plug in an ethernet cable, in order to avoid the possibility of creating-and-leaving some WiFi settings into the new ISO snapshot that I’m going to make.
3. Install the very few tools that I need: Git, Vim, Mosh, Chromium, Flash plugin, and tmux.
4. Create a snapshot immediately. Gives it a filename suffix “gvmcf”. (Was that the culprit?)
5. Run the liveUSB maker immediately, using the newly created ISO snapshot. Now, this is the first time and the last time I use the official antiX 19.2 ISO. From now on, I only use those customized liveUSB on my several computers.
6. In my subsequent usage, I would sometimes do F8-Save some settings to the liveUSB.

I’ll attach a picture of my liveUSB’s boot menu.

Attachments:

1. 

   20201107_202318.jpg
   

[Anonymous]

Could this be related to a snapshot? Or maybe when you save the boot parameters, Switch to grub disapears?

As a followup test, I booted the 19.3-from-snapshot ISO, and created another (2nd generation) snapshot iso.
Within the iso-snapshot workflow, I did not choose a custom name this time.
When booting the 2nd-gen ISO, “switch to grub bootloader” is correctly displayed.
The namestring in the default bootmenu entry is (again, still) just “antiX”

> when you save the boot parameters

In virtualbox, can I even test this permutation?
When livebooting in virtualbox, the F8 Save option is absent
(expected to be absent b/c we are emulating a liveCD boot scenario)

[Anonymous]

sorry about omitting text in my earlier post. I was still testing variations and had intended to edit that further before pressing “post”

the DATE shown in bootmenu misled me to think that was a pristine 19.2 iso, but it was not. It was a 19.2 iso created via isosnapshot.

Water over the bridge ~~ whatever was what back in 19.2, I retested using fresh 19.3, created a fresh snapshot iso and booted that. Yes, the “switch to grub bootloader” menu entry is displayed, even booting the snapshot iso,

Today’s testing brings to light a reported 2yrs ago iso-snapshot bug:
User is allowed to select a custom namestring for the snapshot, but that namestring is not transferred ~~ instead, as seen in the screencap, the default bootmenu entry namestring becomes just “antiX” (the default _timedate suffix is lost, and is not replaced by the user-supplied namestring)

[Member Xecure]

From antix 19 Realease notes:

Live grub rescue options (thanks to fehlix). You can now switch between Grub and Syslinux when you boot the live system in “legacy mode”.

ALL my isos have it. I cannot find the links for the original antiX 19 release isos (probably removed at some point in time). So, lets try for antiX 19.1 base 32 and 64 bits:

antiX 19.1 base 32 bits (Iso in VBox) – Legacy Boot

antiX 19.1 base 64 bits (iso in VBox) – Legacy Boot

This is what it looks like after switching to grub menu from syslinux:

You can see that at the botom there is an option “Boot Rescue Menus”

Maybe it is not the iso, but something related to Live USB Maker. I will try booting from legacy mode with my laptop (or from a VM, if possible) and upload some pictures.
EDIT: Photo from my laptop booting live USB of antiX 19.2.1 base x64 from Legacy BIOS boot.

This Live USB was created using the antiX Live USB maker in antiX 19.
My other antiX 19.1 core has a zero second timer at boot, so it was imposible to get the photo on the laptop.

rayluo wrote:

Perhaps, that otherwise very helpful wiki page would need to be modified?

Ok. If you or someone else cannot, I will take some time and edit it so that it says (New since antiX 19)

• This reply was modified 2 years, 6 months ago by Xecure. Reason: Live USB legacy boot photo

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

[Member Xecure]

PFO wrote:

BASIC install of 19.20.1 and it works pretty well! Several programs – Links2, Manage Packages, Package Installer, etc. simply do not work.

This is 64 or 32 bits?
First, when booting from DVD, did you check iso integrity?

Press F4 in the boot screen and checkmd5 or checkfs to see if the DVD is OK.

Then, the second question is, did you check you had internet connection?
ping google.com

none of them (Links2, Manage Packages, Package Installer) will work without internet.

PFO wrote:

A. What is the command that prints out the status on my laptop, to assist bug-fix & optimizing?

How to ask for help

anticapitalista wrote:

When you first get here, we know you are confused and like lost in the woods a bit. To help us help you.
Whenever you 1st join the forums, give us these readouts from a terminal.
Just copy and paste then highlight the text on the page and click on code button.

These readouts will help us to help you.

inxi -zv7

But you can also use

inxi -Fxz

To show us your repositories.

inxi -r

PFO wrote:

B. How do I UPGRADE to FULL install of 19.20.1 OR 19.30 without burning a DVD?

Upgrading the system on the internet is enough to update it to 19.3. For full, you just need to install some extra packages from the package installer (libreoffice latest, synaptic package manager, and little more). Really, antiX base is enough. The rest can be downloaded if really needed.

• This reply was modified 2 years, 6 months ago by Xecure. Reason: Add anticapitalista quote ask for help

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

[Moderator Brian Masinick]

The first couple of references refer to automatic login.

For autologin, if you happen to use LightDM, this *might* be useful:
https://www.addictivetips.com/ubuntu-linux-tips/enable-automatic-login-on-linux/

Another solution is along the lines of what Christophe just suggested:
http://littlesvr.ca/linux-stuff/articles/autologinconsole/autologinconsole.php

I know that Red Hat Linux offers “Kickstart” automated installations. There may be some ideas you can bring into an antiX installation from them as well. Kickstart definitely deals with the installation aspect.

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/installation_guide/sn-automating-installation

This guy talks about using a PXE – The Preboot Execution Environment (PXE) is an industry standard client/server interface that allows networked computers that are not yet loaded with an operating system to be configured and booted remotely by an administrator.

https://www.leifove.com/2016/11/fully-automated-linux-mint-desktop.html

Combining an automated installation and an automatic login may also be potentially useful.

One last reference is a project that contains an ISO image for Fully Automated Installation (FAI):
https://fai-project.org/

This ought to give you a few options to consider. If you need additional background details, please let us know.

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

--
Brian Masinick

Hi everyone,

I’ve looked through the customisation documentation and it seems that there’s nothing to do exactly what I’m wanting, which is an auto-install.

What I’ve done so far is as follows:

1) Starting with core, extracted contents
xorriso -osirrox on -indev antiX-19.3_x64-core.iso -extract / extracted_iso_image

2) Replaced isolinux.cfg with something that will boot immediately into text mode. This seemed to do the job:
timeout 10
default safe

MENU TITLE Welcome to antiX-19.3_x64-core (Manolis Glezos)

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

3) Remastered with
xorriso -as mkisofs -D -r -J -joliet-long -l -V “Custom antiX core” -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat -iso-level 3 -no-emul-boot -partition_offset 16 -boot-load-size 4 -boot-info-table -o ./new_antix.iso ./extracted_iso_image

I appreciate this may not be the way the developers intend me to customise the system, however I need this customisation step to work on a Mac so I was going to use the Brew port of squashfs-tools for the customisation.

So this is a good start, as it takes me immediately into the login prompt, however I’d also like to automate the execution of cli-installer. I’ve been looking through the squashfs and initrd and I’m just wondering where I would run the cli-installer from. Should I put it somewhere in /etc/rc.local? Is there a better place? Should I be trying to run it at run level 1, or level 5?

Thanks for any help!

Hi !

I need to edit grub files in android-x86 in virtualbox, so I use vi .

And I can’t save and quit, because the escape touch (ESC) don’t work.

I need to do like that :

Found the solution!

You have to edit menu.lst file. Here is how:

boot in debug mode (usually the second option in boot menu)
when booting stops (for me it just hangs there with flashing cursor and without any prompt) enter mount -o remount,rw /mnt
enter cd /mnt/grub
enter vi menu.lst
press Shift+a
right under the first boot entry find the line starting with kernel initrd=/in (your line might look different; it depends on Android version; in general just find the line that starts with kernel)
at the end of the line type vga=834 nomodeset xforcevesa
press ESC then :wq – these commands will save the file and quit vi
enter cd /
enter umount /mnt
enter reboot -f

Now the system should reboot in the VESA mode of your choice.

This will enforces to use the VESA driver for X.

You can replace the vga=xxx by any number you want for your screen resolution. Also tested that 832 works fine (gives 800×600 resolution).

You can find all the VESA modes when you use the iso file and pick the boot option to boot in VESA mode – it will show the list with all modes (numbers are in hex and there is also a redundant letter in front of some modes – ignore it) and you can test them there immediately to see if it works and is good to use in this menu.lst fix, but you have to convert it from hex to dec first using any hex->dec converter.

If anyone know how to save and quit in vi , in grub on virtualbox, thank you very much. (I read this too ):

The Escape key is a shortcut to Ctrl+[. If the key is missing (as on a real vt220, for example), or if it doesn’t do what you want (it’s been remapped by VirtualBox, or similar), then try the Ctrl+[ combination instead.

Check your VirtualBox setup. It should not remap Escape by default (at least not on the systems I’ve been using it on).

But don’t work … And Ctrl + C , don’t work, maybe I can mapping this touche in virtualbox, but I don’t found tutorial for that. Sorry.

$ uname -r
4.9.212-antix.1-amd64-smp
Mon retour de inxi -Fxz : https://pastebin.com/kqRMrRZZ
my xmpp : weerbor@jabber.fr

[Member Xecure]

dee64 wrote:

I think this computer has got the hump with me and even though I rarely have the microphone on she has found out I am retiring her.

Hahaha. It like a child demanding for your atention.

I don’t know what is going on with the iso snapshot, so I have no clues as to why it is acting up.

If you want to block all updates and update notifications, purge the apt-updater.

The antiX system already works well with version 19.2, so maybe the only things you need is to install new packages as needed and forget about updates. Firmware and other updates are optional.

If no-one else has any ideas, you could do that and keep the system running the same versions of programs (except maybe update browsers or some kernel updates if after installing they boot properly, for some security patches).

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

[Member marcelocripe]

cherith_reddy wrote:

hey guys
I am using windows XP professional
I had burned a cd with Linux Antix and inserted it in driver
but after restarting with the DVD inside it was not loading linux
but restarting as usual

pls help

@cherith_reddy, did you burn antiX to a CD or DVD? Do you know how to burn an ISO image to DVD? Did you at least use a program similar to ImgBurn or Free DVD ISO Burner for Windows?

The ISO “antiX-19.3_386-full.iso” is 1.16 GB and does not fit on a CD, on a DVD it does. If you are a beginner in antiX Linux, as I am, prefer the full versions, as you already informed us that you have 1 GB of RAM, in the topics https://www.antixforum.com/forums/topic/64- bit-or-32-bit-confusion / e https://www.antixforum.com/forums/topic/need-for-download-guide/, follow the guidelines and recommendations received from colleagues.

Find out with which key on the keyboard you will be able to get to the device boot options menu, as @Xecure said may be the F12 key.

Do the following: Insert the DVD into the player with Windows running, restart the computer, watch the computer lights, when you turn it on again, even if there is no image on the monitor, keep pressing the F12 key or the key that activates the options menu boot device (I found in a search that could be F1), if everything goes right, you can use the keyboard keys up or down to select CDROM option: Model of your player, press Enter. If you can do this and if your player is reading the DVD you burned with antiX correctly, you will certainly see the antiX boot screen.

I found some information that may prevent the device boot options menu from displaying https://support.lenovo.com/en/solutions/sf16-d0035, you will need to translate the website text into your language .

The device boot options menu screen looks like the following image:

marcelocripe
(Original text in Brazilian Portuguese)

———-

@cherith_reddy, você gravou o antiX um CD ou um DVD? Você sabe gravar uma imagem ISO em DVD? Ao menos você usou um programa semelhante ao ImgBurn ou Free DVD ISO Burner para Windows?

A ISO “antiX-19.3_386-full.iso” possui 1,16 GB e não cabe em um CD, em um DVD cabe. Se você é um iniciante no antiX Linux, assim como eu sou, prefira as versões full, como você já nos informou que possui 1 GB de memória RAM, nos tópicos https://www.antixforum.com/forums/topic/64-bit-or-32-bit-confusion/ e https://www.antixforum.com/forums/topic/need-for-download-guide/, siga as orientações e recomendações recebidas dos colegas.

Descubra com qual tecla do teclado você conseguirá chegar até o menu de opções de inicialização de dispositivos, conforme @Xecure disse pode ser que seja a tecla F12.

Faça o seguinte: Insira o DVD no leitor com o Windows funcionando, reinicie o computador, observe as luzes do computador, quando ligar novamente, mesmo que não apareça imagem no monitor, fique pressionando a tecla F12 ou a tecla que acione o menu de opções de inicialização de dispositivos (eu encontrei em uma pesquisa que pode ser F1), se ocorrer tudo certo, você poderá utilizar as teclas do teclado para cima ou para baixo para selecionar opção CDROM: Modelo do seu leitor, pressionar Enter. Se você conseguir fazer isso e se o seu leitor estiver lendo corretamente o DVD que você gravou com o antiX, certamente você verá a tela de inicialização do antiX.

Eu encontrei algumas informações que podem impedir de o menu de opções de inicialização de dispositivos se ser exibido https://support.lenovo.com/pt/pt/solutions/sf16-d0035, você precisará traduzir o texto do site para o seu idioma.

A tela do menu de opções de inicialização de dispositivos assemelha-se a imagem a seguir:

marcelocripe
(Texto original em Português do Brasil)

[Member Xecure]

If your xiaomi phone is very new, you need a kernel upgrade.
See this thread:
https://www.antixforum.com/forums/topic/antix-19-base-iso-android-usb-tethering-wont-work/

Try first upgrading to 4.19 kernel before moving to a 5.X kernel.
Intructions for USB tethering:

Xecure wrote:

As an experiment, I decided to try it out myself on a live USB (no changes, kernel 4.9.212) antiX 19.2.1 base x64.
0. Boot into my antiX 19.2.1 base live USB from my laptop.
1. I made sure connman was running (you should see a corresponding icon in the systemtray). If it isn’t active, Launch it from the COntrol Centre or from App Select (search for connman). Make sure it is running.
2. I connected my phone (Android 9 phone) using a USB cable to the laptop running antiX 19.2.1 base.
3. On my mobile device, I activated “share my connection through USB” (in my language; it probably means “USB Tethering”) in the corresponding section found in “Settings”.
4. After activating it, suddenly my system has internet connection! Success without expecting it at all!

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