Search Results for 'boot from iso'

[Member Xecure]

Also, on Legacy Boot, F8 menu (save boot changes) selecting the legacy kernel doesn’t work (at least on my tests). Could anyone else check if this also happens to them?

I see that (on my system) the F8 menu saves the changes to Grub menu, but the syslinux/isolinux doesn’t remember them.

• This reply was modified 1 year, 10 months ago by Xecure.

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

[Member calciumsodium]

Xecure wrote:

Bug Report – all sources list get mangled after update on Live USB with persistence when selecting a timezone before boot.

ISO: antiX bullseye-beta1 (runit)
System: Live USB with persistence – UEFI

Selected Boot parameters (from live grub menus):
Timezone: Europe/Berlin
Kernel:4.9
Persistence: persist_root
Save: grubsave

Issue: /etc/apt/sources.list.d/* files’ content get mangled (it tries to add the same antix mirror to almost all lines)

How to reproduce: Set the previous boot options described above and boot the system. Update all packages and, when asked, replace antix.list and debian.list. Save live changes and reboot. On next boot all sources will get mangled (and on each new reboot they get mangled even more).

Hi @Xecure,
I tried to reproduce this error. But I don’t see it. This is what I get.

demo@antix1:~
$ cat /etc/apt/sources.list.d/debian.list 
# Debian Bullseye/Stable
deb http://ftp.gr.debian.org/debian/ bullseye main contrib non-free
deb http://security.debian.org/ bullseye-security main contrib non-free
#deb http://www.deb-multimedia.org bullseye main non-free

# Debian Testing. 
# Testing enabled for 'rolling' release.
# deb http://ftp.us.debian.org/debian/ testing main contrib non-free
# deb http://security.debian.org testing-security main contrib non-free 
#deb-src http://ftp.gr.debian.org/debian/ testing main contrib non-free

# Multimedia Stable and Testing
# Use to install libdvdcss2 and codecs.
#deb http://www.deb-multimedia.org testing main non-free

###### Debian Unstable/Sid##########
###### Use at your own risk! ########
#deb http://ftp.us.debian.org/debian/ unstable main contrib non-free
#deb http://www.deb-multimedia.org sid main non-free
demo@antix1:~
$ 

Looking at it again. The only thing I didn’t do exactly was set the timezone. I kept it at auto. Would that make a difference?

[Member Xecure]

Bug Report – all sources list get mangled after update on Live USB with persistence when selecting a timezone before boot.

ISO: antiX bullseye-beta1 (runit)
System: Live USB with persistence – UEFI

Selected Boot parameters (from live grub menus):
Timezone: Europe/Berlin
Kernel:4.9
Persistence: persist_root
Save: grubsave

Issue: /etc/apt/sources.list.d/* files’ content get mangled (it tries to add the same antix mirror to almost all lines)

How to reproduce: Set the previous boot options described above and boot the system. Update all packages and, when asked, replace antix.list and debian.list. Save live changes and reboot. On next boot all sources will get mangled (and on each new reboot they get mangled even more).

Example of “mangled” source file:

$ cat /etc/apt/sources.list.d/debian.list 
# Debian Bullseyehttp:http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx//ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/Stable
deb http:http:http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx//ftp.halifax.rwth-aachen.de/mxlinux/packages/antix//ftp.de.debian.org/debian/ bullseye main contrib non-free
deb http:http:http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx//ftp.halifax.rwth-aachen.de/mxlinux/packages/antix//security.debian.org/ bullseye-security main contrib non-free
#deb http:http:http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx//ftp.halifax.rwth-aachen.de/mxlinux/packages/antix//www.deb-multimedia.org bullseye main non-free

# Debian Testing. 
# Testing enabled for 'rolling' release.
# deb http:http:http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx//ftp.halifax.rwth-aachen.de/mxlinux/packages/antix//ftp.de.debian.org/debian/ testing main contrib non-free
# deb http:http:http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx//ftp.halifax.rwth-aachen.de/mxlinux/packages/antix//security.debian.org testing-security main contrib non-free 
#deb-src http:http:http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx//ftp.halifax.rwth-aachen.de/mxlinux/packages/antix//ftp.de.debian.org/debian/ testing main contrib non-free

# Multimedia Stable and Testing
# Use to install libdvdcss2 and codecs.
#deb http:http:http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx//ftp.halifax.rwth-aachen.de/mxlinux/packages/antix//www.deb-multimedia.org testing main non-free

###### Debian Unstablehttp:http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx//ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/Sid##########
###### Use at your own risk! ########
#deb http:http:http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx//ftp.halifax.rwth-aachen.de/mxlinux/packages/antix//ftp.de.debian.org/debian/ unstable main contrib non-free
#deb http:http:http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx//ftp.halifax.rwth-aachen.de/mxlinux/packages/antix//www.deb-multimedia.org sid main non-free

NOTE: It doesn’t occur before the update (on live+persistence without updating the packages)

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

[Member olsztyn]

Xecure wrote:

Maybe I am understanding this wrong, but it makes more sense for me to be able to create easily grub or isolinux/syslinux instruction files with a script (to automate it a bit) and then add the generated instructions to grub/other. This would also include the specific boot parameters you request before running the script.

Understood. Thanks Xecure…
I added some more comments in P.S. section of my prior post.
I will work with what is available at this point.
Regards.

• This reply was modified 1 year, 10 months ago by olsztyn.

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

[Member Xecure]

I think there is no advantage on searching multiple frugal installs when each may require the use of different boot parameters that will have to manually be written anyway before boot. Isn’t it better to manually add the frugal boot entries to the grub bootloader as explained in a different article by christophe (and also a video by dolphin_oracle)? Or add those boot entries to your live-usb boot/grub/grub.cfg (or to the syslinux/isolinus boot config) file as custom entries? It isn’t that common to boot frugal installs on different machines with the same live-USB, so I wouldn’t consider this a pressing issue.

Maybe I am understanding this wrong, but it makes more sense for me to be able to create easily grub or isolinux/syslinux instruction files with a script (to automate it a bit) and then add the generated instructions to grub/other. This would also include the specific boot parameters you request before running the script. We would not need to pressure the devs to add anything new and the few of us who use frugal may benefit more from it that making the live init more complicated and more prone to undesirable errors.

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

(This is a re-posting of a solution in another forum section, placed here into Tip & Tricks, in an effort to make it easier to find in the future.)
.

If you are interested, here’s how to turn your computer’s hard drive into non-removable antiX live USB:
(This is for legacy bios. I haven’t done this on a uefi computer.)

1. Make sure this is what you want to do! (It is reversible, of course, but you erase your data.)

2. Boot with a live-usb. Start the live usb maker from the command line:
sudo live-usb-maker --force=usb
You have to use that parameter, to get the program to “see” your hard drive as a candidate.

3. Live-usb-maker should allow you to pick your hdd as the target. Let the live-usb-maker do its thing. You can clone the live-usb you booted with, or choose an iso file, as usual. (If you clone your current system, I recommend remastering (& rebooting) first, because live-usb-maker won’t (by default) copy over your persistence files for you.) Once it’s done, shut down, remove the live-usb that you were using.

4. Upon boot, the hard drive behaves just like a live-usb, but first you have to adjust one thing: once you get to the splash/options screen, add the boot code:
from=hd
Make sure you “save” (F8).

5. Now it’s a non-removable antiX live-usb!

See also:

For adding more antiX and/or MX frugals into the bootloader (for live-USBs, in general):
https://www.antixforum.com/forums/topic/dual-mx-antix-live-persistent-usb-stick/

For using Syslinux/Extlinux as the bootloader on legacy bios computers (for frugals, & can chainload full-installs):
https://www.antixforum.com/forums/topic/booting-antix-frugal-only-from-hdd-without-any-full-installed-os-with-extlinux/

For a similar bootloader setup for frugal installs on UEFI computers:
https://www.antixforum.com/forums/topic/booting-antix-frugal-only-from-hdd-on-uefi-firmware-with-grub/

• This topic was modified 1 year, 11 months ago by christophe.

Attachments:

1. 

   20210614_072035-1.jpg
   

2. 

   20210614_072153-1.jpg
   

3. 

   20210614_105203-1.jpg
   

confirmed antiX frugaler, since 2019

[Member Xecure]

stevesr0 wrote:

Since this, when I boot into the linux distro on this machine, after log in it just displays a window saying my window manager is not usable. After a few seconds I note that either the fan or the disk is running loudly, so I shut the computer down to avoid possible heat damage.

Could you tell us what distro this was and what window manager or desktop environment was running? When you say “log in”, does this mean you can choose a different WM or DE from the login screen and they also fail to launch?
It is possible that chrooting to the distro with “CHRoot Restue Scan” from an antiX Live system and then reinstalling the Window Manager will solve the problem. The main issue is figuring out if the / (linux root) partition has been replaced by the Debian Live, but I don’t think that has happened (you would realize that the installer was asking for using X or Y partition scheme and exited, it will never install without your input). It is possible that something did get corrupted, and reinstalling it should fix it.
If you can give us more details on the Linux system (GPU, linux edition, Login software, if you can see the linux root partition and see if things have changed, if you are using a separate /home partition, etc.).

With the info provided it is not enough to figure out how to start proceeding, as we are not sure what changes happened with the Debian Live ISO.

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

Hi all,

Because of a problem with my built in wifi and bluetooth card, I have been trying different versions of antix and other distros seeking to find one that the hardware would work with. (It is the subject of another thread.)

Today, I tried to use what I thought was a LIVE Debian 10.9 iso booting from a usb. It didn’t work well – taking an enormous amount of time and ultimately getting to a blinking command hyphen without a prompt.

So, I then tried it on my newest computer.

After it ran a long time, a screen came up and I explored it for a while before trying to shut it down. After choosing logout to shut down, the screen went blank except for two rectangles. After a few minutes, I shut off the power.

Since this, when I boot into the linux distro on this machine, after log in it just displays a window saying my window manager is not usable. After a few seconds I note that either the fan or the disk is running loudly, so I shut the computer down to avoid possible heat damage.

The windows install on a separate hard drive on the same machine is working fine.

I rechecked that iso and found out that it was an installer version NOT a live iso. So I believe that it started installing while it was booting the machine.

When I boot with a live antix 17 distro, I can see that the files still exist on the drive.

I am not sure what was mangled on the ssd with the linux distro and I would appreciate any advice about how I can diagnose this and fix.

I realize this isn’t providing a bunch of useful technical details; be happy to provide them if people suggest what…

Thanks in advance.

stevesr0

P.S. When I boot a live antix 19.4 distro, it comes up to a command line on this machine and I am not able to launch X. This usb does boot to a gui on another machine. A 17 antix usb does boot to a gui.

• This topic was modified 1 year, 11 months ago by stevesr0.
• This topic was modified 1 year, 11 months ago by stevesr0.

[Member Danathar]

christophe wrote:

If you are interested, here’s how to turn your computer’s hard drive into non-removable antiX live USB:
(This is for legacy bios. I haven’t done this on a uefi computer.)

1. Make sure this is what you want to do! (It is reversible, of course.)

2. Boot with a live-usb. Start the live usb maker from the command line:
sudo live-usb-maker --force=usb
You have to use that parameter, to get the program to “see” your hard drive as a candidate.

3. Live-usb-maker should allow you to pick your hdd as the target. Let the live-usb-maker do its thing. You can clone the live-usb you booted with, or choose an iso file, as usual. (If you clone your current system, I recommend remastering (& rebooting) first, because live-usb-maker won’t copy over your persistence files for you.) Once it’s done, shut down, remove the live-usb that you were using.

4. Upon boot, the hard drive behaves just like a live-usb, but first you have to adjust one thing: once you get to the splash/options screen, add the boot code:
from=hd
Make sure you “save” (F8).

5. Now it’s a non-removable antiX live-usb!

Thanks! That’s exactly the instruction I was looking for! I’m assuming encryption should work as expected?

• This reply was modified 1 year, 11 months ago by Danathar.

[Moderator christophe]

If you are interested, here’s how to turn your computer’s hard drive into non-removable antiX live USB:
(This is for legacy bios. I haven’t done this on a uefi computer.)

1. Make sure this is what you want to do! (It is reversible, of course.)

2. Boot with a live-usb. Start the live usb maker from the command line:
sudo live-usb-maker --force=usb
You have to use that parameter, to get the program to “see” your hard drive as a candidate.

3. Live-usb-maker should allow you to pick your hdd as the target. Let the live-usb-maker do its thing. You can clone the live-usb you booted with, or choose an iso file, as usual. (If you clone your current system, I recommend remastering (& rebooting) first, because live-usb-maker won’t copy over your persistence files for you.) Once it’s done, shut down, remove the live-usb that you were using.

4. Upon boot, the hard drive behaves just like a live-usb, but first you have to adjust one thing: once you get to the splash/options screen, add the boot code:
from=hd
Make sure you “save” (F8).

5. Now it’s a non-removable antiX live-usb!

• This reply was modified 1 year, 11 months ago by christophe. Reason: clarification

Attachments:

1. 

   20210614_072035.jpg
   

2. 

   20210614_072153.jpg
   

3. 

   20210614_105203.jpg
   

confirmed antiX frugaler, since 2019

[Member fehlix]

xinomilo wrote:

3) used the same iso in legacy bios with a decade old laptop and everything was working fine in boot menu for live usb.. with uefi live in this laptop, boot menu didn’t work at most options (some tpm error i didn’t write down, something about “TPM unknown error” while trying any options at boot). choosing to boot default entry right after boot was the only thing that worked/booted.

Probably related to the TPM (Trusted Platform Module) enabled chip within UEFI firmware setting, which might be by default enabled (not only for secure boot). So would you mind to disable GRUB’s tpm module this way:
At GRUB menu press ‘c’ to get a GRUB command line
and remove GRUB’S tpm module with this line and press <ENTER>
rmmod tpm
Press <ESC> to go back to the menu.
Removing tpm by default might be one option to consider.
Thanks

• This reply was modified 1 year, 11 months ago by fehlix.

[Member xinomilo]

ok, so i had a serious issue with my main prod laptop with another distro, and thought i’d move permanently/for good to antix. formatted last night with this iso (with uefi/runit/5.10 kernel).

some notes :
– luks partition not mounting problem at boot i had with a1 iso, is fixed in b1! boots normally!
– systemd-timesyncd package shows in “residual configs”, had to : dpkg --purge systemd-timesyncd
– during livecd evaluation, and apt upgrade, i noticed package libpolkit-gobject-elogind-1-0 was marked for autoremoval (probably because it was a version earlier/mirror issue?)… that was fixed in a later upgrade, so just mentioning it.

some issues i’ve been seeing :
1) ps:
runsvdir -P /etc/service log: /run: file does not exist runsv lvm2: fatal: unable to start ./run: file does not exist runsv acpi-support: fatal: unable to start ./run: file does not exist runsv rsync: fatal: unable to start ./run: access denied runsv ofono: fatal: unable to start ./run: access denied runsv sudo: fatal: unable to start ./run: file does not exist ./finish: 4: .: cannot open /etc/default/runit: No such file
any idea how to fix it? maybe /etc/sv/$service/run needs to be executable?
2) backlight setting resetting to 100% after boot
3) used the same iso in legacy bios with a decade old laptop and everything was working fine in boot menu for live usb.. with uefi live in this laptop, boot menu didn’t work at most options (some tpm error i didn’t write down 🙁 , something about “TPM unknown error” while trying any options at boot). choosing to boot default entry right after boot was the only thing that worked/booted.
4) after installation, i’ve seen occasional flickering on screen with i915. will see if that continues, cause i’ve just upgraded everything to sid.. (imho, it’s a nice timing to dist-upgrade to sid, things are more stable during release freeze 🙂 )

some package suggestions/wishlist :
– replace mlocate with plocate, for bullseye and newer… it is much faster.
– replace keepassx with keepassxc in package suggestions (more up to date i think)
– add signal-desktop option to messaging apps. probably telegram-desktop too, but that’s already in debian repos.
– add ungoogled-chromium in browsers.
– i thought clipit was abandoned(?) and even debian has clipit nowadays as a metapackage to install diodon instead. maybe prefer parcellite as an alternative?

Host: LIFEBOOK E746
Kernel: 5.10.27-antix.1-amd64-smp
CPU: Intel i5-6200U (4) @ 2.800GHz
GPU: Intel Skylake GT2 [HD Graphics 520]

thanks 🙂

[Member Xecure]

DynV wrote:

and there’s a window entitled “Boot Loader” with content “/boot/grub/i386-pc/lnxboot.img: file not found” and underneath it there’s another window which the title is almost all covered with content “Loading Linux Kernel”.

This is strange. It is included in the i386 iso.
I don’t have a 32bits machine, but running antiX 19.4 full i386 in a VM does let me access grub menu.
https://youtu.be/Yrrd89pswrY

Does anyone know if some machines cannot get to the grub menus or if this could be related to a corrupted ISO download? (Probably not if the OP already performed a F4 > checkfs or checkmd5).

Any other voices who can give us expert advice are welcome.

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

[Member Xecure]

Wallon wrote:

The installation is only in UEFI mode. Legacy mode is gone.

I didn’t understand, Wallon.
Do you mean that when you boot in UEFI mode the option “Legacy” is not there? The UEFI (grub) menus have the option to select a different kernel in Advanced options, (where you can also select desktop, noautomount, save-grub mode -> to select how you want your selected options to be saved, etc.). NON uefi (isolinux/syslinux) has a different menu system to UEFI mode (grub menus).
Before, in UEFI mode, you could only select option in text menus or directly writing the bootcode inside the “editing” grub mode. Now we can select language/keyboard/timzone in the seconf grub menu option, and also have more advanced menus in the “Advanced Options”, which lets us change kernel, and many other boot parameters.

My am not sure if this answers the question.

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

[Member calciumsodium]

Xecure wrote:

calciumsodium wrote:

b1-runit does NOT boot up in normal boot (quiet splasht disable=lxF) for either the 4.9.0-264 nor the 5.10.27 kernels.

I just read this part. Does it boot properly when using bootcode?
xorg=intel
I had a similar issue on the previous a1, but didn’t see it happen to me again.

Hi @Xecure,

I tried
quiet splasht disable=lxF xorg=intel

and b1-runit still does not boot for me on this old hp 6730b laptop. It just produces a black screen similar to the
quiet splasht disable=lxF
boot option.