Search Results for 'boot from iso'

[Member Kjellinux]

Thank you all for your input. I think you overrate my Linux skills though. What I need at this stage is very simple and basic answers to some very basic questions.

Given the equipment described in my original post (Acer Aspire 3100 with 512MB RAM and a 16GB USB stick), what would be the best version of antiX to try first?
Should I burn the .iso file to a CD first and then install to the USB stick, or should I install directly to the USB stick?
If directly to a USB stick, should I format the USB stick in advance, and if so, how?
If directly to a USB stick, which program is best to use on Linux Mint 19.3 Cinnamon and Windows 10 respectively?
What configurations and settings should I do on first boot?
Are there any easy to follow step by step instructions for how to do this?

I will eventually upgrade the test rig with more RAM (1GB, 2GB and 4GB) and an SSD, but for the purpose of my testing, I want to keep the test rig as “crappy” as possible for now. After all, the purpose of my testing is to find out just how old and crappy hardware can be, while still good enough to be given a second life using lightweight Linux distributions. Eventually I will also start installing to hard drive, but for now I want to stick with USBs to get comparable test results.

[Member andyprough]

You can try my Libre-antiX respin for i386 if you like: https://www.antixforum.com/forums/topic/antix-libre-respin/page/2/#post-55939

The ISO is small enough to burn to a regular CD. If I recall correctly, I think it runs with slightly less memory than normal antiX. To be fair, I haven’t fired up my 32-bit desktop in a couple months, so I’m having to go by my own error-prone memory regarding the RAM usage. I think it normally boots up into an Icewm window manager with about 120-130mb of ram (don’t shoot me if I’m wrong on this).

It comes with the Linux-libre kernel (proprietary blobs are stripped out), and with non-free firmware stripped out. It probably won’t work with wifi unless you have a wifi card with a specific Atheros chip.

[Member Xecure]

Note: This is my own speculation and not an official answer.

Hi, Wallon.

TPM 2.0 and modern CPU’s are OK. The problem is

Wallon wrote:

– a Secure Boot,

This is the possibly biggest issue. If Microsoft (and Hardware manufacturers) enforces it, then the current antiX and MX Linux systems will not boot at all.

There are 2 possibilities I see:
– Microsoft recommends but doesn’t enforce Secure Boot (different parties are pressuring Microsoft to not enforce it). So, secure boot can still be disabled and W11 (Windows 11) will work OK (the current W11 ISO can be configured to ignore Secure Boot requirements).
– Microsoft gives MX Linux a special license (because it is so popular) so that MX Linux can Sign their kernels and be able to boot on Secure Boot (and antiX will have to use the MX Linux kernels on the x64 ISOs).

The final possibility is antiX/MX having to hack things with a shim + Debian kernels to be able to boot and install on TPM2 with Secure Boot devices, but that is the second worst case scenario.

The worst case scenario: antiX/MX will not work side-by-side on systems with W11.

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

[Member Xecure]

Thanks for that.
It seems to be an Intel Celeron CPU N3350, as you say with Intel HD Graphics 500 to manage graphics. It seems to use the correct i915 kernel driver and modesetting (kernel managed) for xorg video controller (though it could also use the intel xorg module).

I found some threads for this CPU, and there seems to be better support on kernel version 4.19. If you don’t mind, try this ISO on live USB on your machine just to see if the Font size issue is fixed there. If it does solve the issue, and you have an installed antiX system, you can install the latest antiX 4.19 kernel using the package installer and reboot (which will automatically load the newest 4.19 kernel).

Let me know how it goes.

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

Debian Installer Bullseye RC 3 release

The Debian Installer team[1] is pleased to announce the third
release candidate of the installer for Debian 11 “Bullseye”.

Let’s start with some news regarding firmware support (#989863):
– We don’t want to leave users in the dark if the installed system
doesn’t boot correctly (e.g. black screen, garbled display). We
mentioned that possibility in the installation guide[2], and listed
a few workarounds[3] that might help log in anyway.
– We also documented an isenkram-based procedure[3] which lets users
detect and fix missing firmware on their systems, in an automated
fashion. Of course, one has to weigh the pros and cons of using
that tool since it’s very likely that it will need to install
non-free packages.

In addition to those documentation efforts, the non-free installer
images that include firmware packages[4] have been improved so that
they can anticipate the need for firmware in the installed system
(e.g. firmware for AMD or Nvidia graphics cards, or newer generations
of Intel audio hardware).

Improvements in this release
============================

* cdrom-detect:
– Tell hw-detect not to warn and prompt about missing firmware:
finding and mounting the ISO image happens so early that nothing
could be done about missing firmware at this stage anyway
(#991587).
* hw-detect:
– Add support for installing additional firmware packages if items
in the udev database match some modalias-based patterns, based
on DEP-11 metadata (#989863).
– Make sure to reload the appropriate kernel module after having
injected some firmware: there might be some discrepancy as can
be seen with rtw_8821ce vs. rtw88_8821ce (#973733).
– Improve firmware-related logging by removing obsolete code,
removing duplicates, adjusting format strings.
– Add support for ignoring some particular firmware files that
might be neither actually required, nor packaged; start with
iwl-debug-yoyo.bin, requested by iwlwifi (#969264, #966218).
– Make it possible for callers to disable warning and prompting
about missing firmware.
* debian-cd:
– Add brltty and espeakup to all images from netinst up (#678065).
– Generate firmware metadata from AppStream/DEP-11 metadata, and
use it when building a media tree (#989863).
* debian-installer:
– Bump Linux kernel ABI to 5.10.0-8.
* pcmciautils:
– Update /etc/pcmciautils/ dir to /etc/pcmcia/ in udeb (#980271).
* udpkg:
– Add locking for the status file, avoiding failures on the first
installation step when multiple consoles are involved (#987368).

Hardware support changes
========================

* linux:
– arm64: Add pwm-rockchip to fb-modules udeb.
– arm64: Add fusb302, tcpm and typec to usb-modules udeb.
– armhf: Fix network detection on various i.MX6 boards (#982270).
– armhf: Add mdio-aspeed to nic-modules (#991262).
– s390x: Fix console name to match device (#961056).

Localization status
===================

* 78 languages are supported in this release.
* Full translation for 36 of them.

Known bugs in this release
==========================

* No known major bugs yet.

See the errata[5] for details and a full list of known issues.

Feedback for this release
=========================

We need your help to find bugs and further improve the installer, so
please try it. Installation images, and everything else you will need
are available at our web site[6].

Thanks
======

The Debian Installer team thanks everybody who has contributed to this
release.

1. https://wiki.debian.org/DebianInstaller/Team
2. https://www.debian.org/releases/bullseye/amd64/ch02s02
3. https://www.debian.org/releases/bullseye/amd64/ch06s04#completing-installed-system
4. https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/
5. https://www.debian.org/devel/debian-installer/errata
6. https://www.debian.org/devel/debian-installer

Cheers,
—

Cyril Brulebois (kibi@debian.org) <https://debamax.com/&gt;
D-I release manager — Release team member — Freelance Consultant

--
Brian Masinick

[Member KGHN]

Hi AntiX new friends. I’m installing AntiX for use on a Dell e6400 travel-tasks laptop. I replaced the spinning HDD with a 500GB PNY SSD. I used SysRescueCD 8.03 (on a bootable flash drive)’s GParted to create a DOS partition table and 4 partitions: 4GB linux-swap, 60GB for ext4 linux root/user, 100GB formatted ntfs for a virtual Win7-32 that I need for legacy software, and the rest approx 300GB for ext4 linux home. I downloaded the AntiX 19.4-64 full ISO and checked its MD5, burned a DVD, and booted it. During install I checked for bad HDD sectors. All went well until I got the error message “GRUB installation failed. You can reboot to the live medium and use the GRUB Rescue menu to repair the installation.” The machine would not boot, just danced a restart loop with the BIOS offering <F12> for a boot menu.
Much struggle: I don’t understand what’s the “live medium”? I could not find a GRUB Rescue menu on the AntiX DVD boot. I tried various advice from online without success: mx-boot-repair in terminal was not found. I hunted through antiX-cli-cc and the AntiX desktop menus without finding anything relevant. One post said missing flags (boot, esp) on the boot partition could cause the error, and they were indeed missing. I set them but it didn’t help.
Here’s what worked: brought up GParted again, reformatted the two linux partitions, set flags boot and esp on the root/user partition. Reinstalled from the DVD. Success!
Wish me luck setting up fixed ip internet access, and a virtual Win box. I’m liking AntiX a lot so far. My partner records music (Janis June Respect the Sign is his work), is a big Slackware fan, and hates systemd, and I have a lot of limited-resource hand-me-down machines to configure for fixed-income friends. I figure my upcoming travel is a good chance to really try AntiX in action.

Happy camper, interesting world.

[Member mikey777]

olsztyn wrote:

– Comparison test also should be run on the same hardware. Exactly the same antiX composition (Live or not) has lower memory footprint on lower specs machine than on higher specs one.

I always run OS-comparisons on the same laptop, as a multibooted system.

The same Live antiX run on my Thinkpad X61 shows significantly lower footprint than when run on my Thinkpad T410, which is still lower than run on my Thinkpad T520, although the installed memory size on X61 is the same as on T410 (4GB). Comparison of footprint to T520 in this case might not be fair as T520 has 8GB memory.

Yes, it’s an interesting observation. I’ve found much the same with my hardware – the more powerful the machine the greater the OS footprint. For example, on dual-core CPU machines, I’ve observed that antix19.4core-LXDE idles at 175MB RAM with a 2GHz processor (Asus X71Q), but only 95MB with a 1.4GHz processor (Packard Bell Easynote MX37). I would imagine this relationship between OS-footprint & machine power is a universal one …

• This reply was modified 1 year, 9 months ago by mikey777.
• This reply was modified 1 year, 9 months ago by mikey777.
• This reply was modified 1 year, 9 months ago by mikey777.

▪ 32-bit antix19.4-core+LXDE installed on :
- (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
▪ 64-bit antix21-base+LXDE installed on:
- (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
- (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.

[Member mikey777]

sybok wrote:

Hi,
Debian + XFCE vs. Devuan + XFCE which could be a closest candidate to judge from simple systemd vs. other init without too many other changes.

Yes, I had thought of this but Devuan doesn’t seem to want to install on my multiboot system & don’t understand why. I tried both the USB-stick & CD route for installation, but both failed. Maybe a corrupt iso file. I might try again.

▪ 32-bit antix19.4-core+LXDE installed on :
- (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
▪ 64-bit antix21-base+LXDE installed on:
- (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
- (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.

I’ve copied the iso file for antiX19.4-core-sid onto a USB stick, for installing this edition to my laptop’s internal drive.
The installation did not run as it should as the first reboot, following the cli-installer step, resulted in a blank screen and flashing cursor, instead of the command-line prompt presenting itself to allow installation to continue.

The issue might be the kernel 5.8 which comes prepackaged with the above sid edition, as I’m attempting the install on an old machine (14 years). So, it might be worth trying the install with an older kernel, something that Brian (Masinick) has already suggested elsewhere on the forum. However, the problem is how do I change the kernel on the USB iso file ?

Many thanks for any help with this.

• This topic was modified 1 year, 9 months ago by mikey777.
• This topic was modified 1 year, 9 months ago by mikey777.
• This topic was modified 1 year, 9 months ago by mikey777.

▪ 32-bit antix19.4-core+LXDE installed on :
- (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
▪ 64-bit antix21-base+LXDE installed on:
- (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
- (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.

[Member mikey777]

@Dave @Xecure @anticapitalista

Thanks guys for the feedback.
After downloading the iso file, thanks to you pointing me in the right direction, I started the install of antiX19.3core-sid. Following the initial prompt to reboot (after using the cli-installer), it failed to reboot, just arriving at a black screen with flashing cursor in top left-hand corner (I’ve found the normal antix19.4core doesn’t do this and installs straightforwardly). I notice the default kernel for this antiX edition is 5.8 – maybe my 14 year-old laptop is too old for this kernel …

• This reply was modified 1 year, 9 months ago by mikey777.
• This reply was modified 1 year, 9 months ago by mikey777.

▪ 32-bit antix19.4-core+LXDE installed on :
- (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
▪ 64-bit antix21-base+LXDE installed on:
- (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
- (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.

[Member Xecure]

Anonymous wrote:

I managed to install it only through the automatic creation of homefs and rootfs.
The program created files not on an ext3 partition, but on fat32.
But I need to use the ext3 partition completely.

To change where the location of the persistence files are, you need to use a boot parameter.

https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters#Persistence_Location
On a LiveCD, the default persistence device is whatever device has the disk label antiX-Persist. If you specify a persistence device with one of the three options below, the defaults are ignored.

* persistdev=<dev> or pdev=<dev> will set the name of the <device> that hosts the persistence file.
* persistlabel=<label>, plabel=<label> or plab=<label> will set the <label> of the partition that hosts the persistence file.
* persistuuid=<uuid> or puuid=<uuid> will set The UUID of the persistence device.

All options above will enable persistence even with no persist= boot option.

You can also set the path of the directory that host your persistence files using

* persistdir=<path> or pdir=<path>, where <path> stands for the directory path of the folder that stores the persistence files you want to load.

Examples:
* pdev=sdb2 sets sdb2 as the device which contains the persistence files.
* pdir=Persistence/antiX19 will load your persistence files from that specific path /Persistence/antiX19 (that is the real directory path inside the device).

You can set the UUID of the ext3 partition you mention with puuid=<uuid>, and the directory path pdir=<path-to-persistence-folder>. This is the safest method.
Copy the rootfs and homefs files to your ext3 partiition, for example inside a folder named “antiX”, and thn edit the boot paramaters f the live USB. You can do it live from the same antiX USB; (if grub boot, edit /live/boot-dev/boot/grub/grub.cfg or if syslinux/isolinux legacy boot, edit /live/boot-dev/boot/syslinux/syslinux.cfg file).
To figure out the UUID of your ext3 device, you can run the command
blkid

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

[Member Xecure]

I have been using connman with resolvconf, and been studying how to make it so it works out of the box with antiX 21.

The first thing we need is:
The file /etc/default/connman containing:

CONNMAN_RUNSTATEDIR_RESOLVCONF="no";
DAEMON_OPTS="--nodnsproxy";
OPTS="--nodnsproxy";

For the runit version, we only need to edit /etc/sv/connman/run script and add at the top (below the #!/bin/sh line)
. /etc/default/connman

and that will source the file we created above to use the “nodnsproxy” connman option when starting connman.

For the sysvinit release, we need a patch to connman’s init. I have submitted the fix to Debian, but I don’t expect it to appear until after bullseye’s release, if at all.
Here is the source with the patch already prepared: https://gitlab.com/nXecure/connman/

this will fix the typo in the /etc/init.d/connman file where the CONNMAN_RUNSTATEDIR_RESOLVCONF check is incorrect. It should look like:

...
if [ "$CONNMAN_RUNSTATEDIR_RESOLVCONF" != "no" ] ; then
...

That is it. This will make it much easier to switch between connman and ceni, without having to play with the /etc/resolv.conf symlink each time. This should also help on antiX 19.X.

My tests:
– If running connman, disconnect and remove the saved wireless configuration in cmst, stop connman (or stop wpasupplicant). then run ceni, and save the connection. After rebooting, even if connman is still running, the connection configured with ceni will work properly.
– If my wireless settings was configured with ceni, I launch ceni to remove the wlanX configuration. I then run cmst and disable/re-enable the wifi option/switch. Re-scan and connect to my wireless access point. That is it. On next reboot, connman will auto-connect to my wireless access point.

There is no need anymore for the antix-wifi-switch, at least with these simple tests. Connman and resolvconf can live as brothers, running on the same computer at the same time. Connman will no longer compete to control /etc/resolv.conf and will embrace resolvconf’s configuration.

If someone is extremely happy with connman and also wants to use it to manage resolv dns, then they just need to edit the /etc/default/connman file (or remove it), and connman will again default to managing dns, ignoring what resolvconf tries to do.

anticapitalista has set it so that there is no longer a need for changing the /etc/resolv.conf symlink, but when connman is managing the resolv.conf file, we need to stop connman and restart the resolvconf service, so it again takes control of the resolv.conf file. With the proposed change, connman will NEVER touch resolv.conf except if the user enables such an option.

My proposition is to inject this /etc/default/connman file during the build-iso process, so that it works out of the box in antiX-21 (and the small change in runit connman service run file), and the connman patch or init connman script. I can also compile and build the new version of connman for buster/bullseye 32 and 64 bits if asked to (I just need a bit of time).

Let me know if you think this proposition has value and could be included in antiX-21.

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

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

[Member Xecure]

If normal boot works sometimes, select normal boot, go to tty1 (Control+Alt+F1), log-in as demo, and stop slim
sudo service slim stop
and restart it again
sudo service slim start

If the card is configured as you have shown in the inxi -Gxxx screenshot (it is already properly configured), then maybe the issue is with slim (the login manager). Restarting it will try t start a new xorg server. Hopefully this is an issue only in the live session, and not after installing.

I would check the integrity of the DVD, selecting one of the checkfs or checkmd5 options in the F4 boot menus. Sometimes this happens if the DVD or the ISO have some corrupted part.

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

[Member Xecure]

Hi, maary79

Is that the complete size of the SSD or only a partition?
With such a limited amount of space I recommend you do a frugal install with persistence instead of a “normal” full install.
This will copy all the linux system to a compressed file that will take the same amount of space as the ISO size. With persistence, you can save all of your changes, as if in a real installed system but taking a fraction of the space.

You can also do a frugal install with MX Linux, if that is your preferred system.

To do a frugal install, select frugal (one of the options there) on the live boot menus.
After the frugal installation, you will need a USB device to boot into it if you don’t have a boot manager.

If that is the only SSD, and it only has 7GBs of space, then you may also consider using this method descried by christophe to trick the system in thinking that your SSD is a live USB, so you can have a much easier frugal installation, using the from=hd and persistence options after installing.

If you still prefer a normal installation, try to only use one big 7GBs partition and NOT swap, as it takes extra free space.

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

[Member Xecure]

Hi.

acrobaticpeace wrote:

Model name: AMD Ryzen 7 4700U with Radeon Graphics

Your CPU is very new and was not supported when the 4.9 linux kernel was released (this is the default antiX 19.X kernel, to better support older machines). You need to boot with an antiX edition with at least Linux kernel 5.4 version.

If you don’t mind, could you try booting with the antiX bullseye-b1 ISO, selecting “Modern Kernel 5.10” in the >>>> Advanced Options <<<<? It is interesting to know if the upcoming antiX 21 release will boot properly on modern machines.

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