Search Results for 'boot from iso'

[Member ModdIt]

Hi skidoo regarding :
A rootfs occupies “XX blocks” somewhere on the device.
During a remaster operation, it is renamed to rootfs.OLD and still occupies those XX blocks at the point when a new rootfs is created. “Freeing” the blocks occupied by rootfs.OLD is, optionally, performed during a subsequent liveboot session.

Have you browsed “/live/boot-dev/antiX/” to verify/ruleout the possibility that one or more *.OLD files are present, or that some other huge file is occupying a chunk of the available storage capacity (e.g. a forgotten snapshot ISO file)?

Yes well knownto me, on several occasions I have deleted everything I could find which is non essential. While investigating ended up with a non booting stick too :-).
Learning by doing is the game.

The problem is absolutely not antiX, MX or debian related. It is happening because the USB stick memory can not be freed using trim as it is not implimented.
There are some discussions regarding the problem on Buntu, debian and Arch forums.

Normal reformatting has brought capacity back to an expected level in most cases.

I checked again on my 128 GB sti9ck 44 are reported to be free today. I have one old rootfilesys i can remove, that will free up max under 5 GB.

My next boot device will be a fast micro sd card in an adapter, micro sd cards and ssd do not have the same issue as the trim command is effective on those devices..

We have 2 versions for experienced users to try. One using SysVinit, the other runit.

antiX-bullseye-b1-x64-full is a beta quality release for experienced testers of antiX to test and provide feedback.
Do not use this as your main OS.

* 4.9.0-264 and 5.10.27 kernels on the live iso. Please try both in your tests.
* grub/UEFI live boot changes
* no virtualbox-guest packages

The implementation of runit in this edition is closer to how runit works on Void and Artix linux.
Sysvinit has been replaced with various antiX runit scripts and our much smaller sysvinit package.

Please post any feedback at antiX forums and state if you are testing live, frugal, in a virtual machine or on bare metal.

Files here: https://sourceforge.net/projects/antix-linux/files/Testing/

Edit 11 June 2021 – Note the newly uploaded SysVinit version that fixes a bug in the repos.

• This topic was modified 1 year, 11 months ago by anticapitalista. Reason: added more info

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

antiX with runit - leaner and meaner.

[Anonymous]

After many changes and several updates/remasters my 128 GB stick has about half of its capacity unavailable with no
way to free the memory by trimming old data. This does not apply completely to SSD and SD cards which do trim, but
does not overwrite memory cells (to conserve life)

Whoa! Surely the loss of “capacity” is attributable something else, some other factor.
“TRiM” is only relavent at the filesystem level
and
even if “lsblk -D” reports 0 (i.e. discard is unsupported for a device)
(re)formatting is an effect “way” to accomplish a result essentially identical
to that which would have been achieved by a series of incremental TRiM operations.

specific to remastering:
Although a remaster operation does not reformat the partition,
it does initiate the use of new, freshly formatted, rootfs (and/or homefs) Sparse_files

https://www.antixforum.com/forums/topic/async-mount-option-and-datajournal-re-persist-save-and-live-remaseter/
moddit wrote:

[..] the controller is non transparent to the connected device, where things actualy get written to or moved too is manufacturer software controlled. Same goes for wear levelling. So trying to physicaly write data to a new location from the OS is futile.

Again, here in this new topic, I would insist that it is not futile.
A rootfs occupies “XX blocks” somewhere on the device.
During a remaster operation, it is renamed to rootfs.OLD and still occupies those XX blocks at the point when a new rootfs is created. “Freeing” the blocks occupied by rootfs.OLD is, optionally, performed during a subsequent liveboot session.

Have you browsed “/live/boot-dev/antiX/” to verify/ruleout the possibility that one or more *.OLD files are present, or that some other huge file is occupying a chunk of the available storage capacity (e.g. a forgotten snapshot ISO file)?

[Anonymous]

Is it possible to have another kernel to test?

.
Yes —v

https://antixlinux.com/the-most-extensive-live-usb-on-the-planet/

use the live-kernel-updater tool to change which kernel the live systems boots with. You need to first install the new kernel and do a remaster.

.

Tested latest MX Linux ISO file but no changes and no success

FWIW, kernel(s) used in the MX ISO are different from those provided on the antiX -issued ISOs.

As a separate matter, one detail common to both MX and antiX — and probably different from other distros you tried — is use of eudev in place of udev. Although their APIs should be essentially identical, the version of eudev in use by antiX//MX (also Devuan) may not be up-to-date with the version of udev used in the other distros you tried.

Both provided udev parameters seems to have some spelling error. I did not find them in this Antix boot parameters

Right, they are not exclusive-to-antiX boot parameters.

udev.log-priority=
is described in the udevd manpage

UDEVD(8)                           udevd                                  UDEVD(8)

NAME
       udevd - Device event managing daemon

SYNOPSIS
       udevd

       /sbin/udevd [--daemon] [--debug] [--children-max=] [--exec-delay=] [--event-timeout=]
                   [--resolve-names=early|late|never] [--version] [--help]

DESCRIPTION
       udevd listens to kernel uevents. For every event, udevd executes matching instructions specified in udev rules.
       See udev(7).

       The behavior of the daemon can be configured using udev.conf(5), its command-line options, environment
       variables, and on the kernel command-line, or changed dynamically with udevadm control.

OPTIONS
       -d, --daemon
           Detach and run in the background.

       -D, --debug
           Print debug messages to standard error.

       -c, --children-max=
           Limit the number of events executed in parallel.

       -e, --exec-delay=
           Delay the execution of RUN instructions by the given number of seconds. This option might be useful when
           debugging system crashes during coldplug caused by loading non-working kernel modules.

       -t, --event-timeout=
           Set the number of seconds to wait for events to finish. After this time the event will be terminated. The
           default is 30 seconds.

       -N, --resolve-names=
           Specify when udevd should resolve names of users and groups. When set to early (the default), names will be
           resolved when the rules are parsed. When set to late, names will be resolved for every event. When set to
           never, names will never be resolved and all devices will be owned by root.

       -h, --help

KERNEL COMMAND LINE
       Parameters starting with "rd." will be read when udevd is used in an initrd.

       ____________________
       ____________________
       udev.log-priority=, rd.udev.log-priority=
           Set the log level.

       udev.children-max=, rd.udev.children-max=
           Limit the number of events executed in parallel.

       udev.exec-delay=, rd.udev.exec-delay=
           Delay the execution of RUN instructions by the given number of seconds. This option might be useful when
           debugging system crashes during coldplug caused by loading non-working kernel modules.

       udev.event-timeout=, rd.udev.event-timeout=
           Wait for events to finish up to the given number of seconds. This option might be useful if events are
           terminated due to kernel drivers taking too long to initialize.

       net.ifnames=
           Network interfaces are renamed to give them predictable names when possible. It is enabled by default;
           specifying 0 disables it.

SEE ALSO
       udev.conf(5), udev(7), udevadm(8)

[Member frtorres]

Thanks @skidoo for your advice.

I spent some time analyzing this issue.

1. Both provided udev parameters seems to have some spelling error. I did not find them in this Antix boot parameters

2. Tested load=all parameter as it seems was useful in similar situation, no success.

3. It is a “weird” issue because using the same VM configuration (disk layout), I installed other linux distros and FreeBSD with no problems booting. From Linode forum they could not help me as this config works with other distros.

4. At grub command prompt I found squashfs file at (hd0) and it is accessible.

5. At boot time Finally I tested the breakpoint debugging boot parameter with these kernel boot parameters:

load=all bp=3 verb=7

Booted this latest iso (AntiX 19.4 64bit):

The break point and a verbose level=7 showed the attached images. I understand hardware controllers are detected but no partition or disks are reported and detected in order to find:”squashfs” file with the compressed file system, so all ended up with the message:

Fatal Error No block devices found

6. Tested latest MX Linux ISO file (maybe another kernel?) but no changes and no success … it seems it has same base (grub, kernel, etc) for a xfce DE.

I am at this point now, concluding by now, maybe this is a kernel issue / boot parameters. Is it possible to have another kernel to test?.

I want to use Antix, because this VM at linode is US$5/month and has only 1Gb RAM +25Gb disk. I think Antix will fit well and will give me a remote desktop I can use while I travel.

Thanks in advance for Antix community advice, comments or guidance in a proper direction.

Thank you all

Francisco.

Attachments:

1. 

   20210608_102724.jpg
   

2. 

   20210608_102938.jpg
   

3. 

   20210608_103103.jpg
   

4. 

   20210608_103128.jpg
   

[Moderator Brian Masinick]

Brian Masinick wrote:

Xecure wrote:

I remember you finding this on antiX 19.4 testing last month, but then I didn’t have time to help troubleshoot.

The biggest problem you are having is that the i915 kernel driver is not loading properly. I recommend you to
A. Try the antiX 19.4 edition with kernel 4.19 (better intel support) booting NORMALLY (NOT safe Video Mode or Failsafe).
B. Try the current antiX 19.4 Live boot with the parameter
i915.modeset=1 xorg=intel
or just
i915.modeset=1

All packages are included in antiX 19.4 (no need for you to go through the same path you did last month), as I can confirm on my system, but sometimes you need to use one of the very convenient antiX Boot parameters. On one of my devices I need to boot with xorg=intel to boot to graphical interface with intel xorg driver (which they say is deprecated and it is better to use modesetting but it works for me).

This fixed it, provided I booted the USB stick without UEFI. WITH either of the options and UEFI the system would hang within the first 30 seconds after login or less.

After installation it also works, so that indicates that I must have built that one ISO image from a limited graphics mode because my antiX 19.3 and antiX a2 testing images also work.

I’ll mark this solved.

I’ll also correct my erroneous title. I found that the old kernel was unstable on my 64 bit system but other newer kernels have been up several hours, so I’m not going to file any defect. In the past I could run any kernel; that is no longer true. Anyway, the Backlight Brightness works on antiX 19.3, 19.4 and the current test release. SOLVED.

--
Brian Masinick

[Moderator Brian Masinick]

Xecure wrote:

I remember you finding this on antiX 19.4 testing last month, but then I didn’t have time to help troubleshoot.

The biggest problem you are having is that the i915 kernel driver is not loading properly. I recommend you to
A. Try the antiX 19.4 edition with kernel 4.19 (better intel support) booting NORMALLY (NOT safe Video Mode or Failsafe).
B. Try the current antiX 19.4 Live boot with the parameter
i915.modeset=1 xorg=intel
or just
i915.modeset=1

All packages are included in antiX 19.4 (no need for you to go through the same path you did last month), as I can confirm on my system, but sometimes you need to use one of the very convenient antiX Boot parameters. On one of my devices I need to boot with xorg=intel to boot to graphical interface with intel xorg driver (which they say is deprecated and it is better to use modesetting but it works for me).

This fixed it, provided I booted the USB stick without UEFI. WITH either of the options and UEFI the system would hang within the first 30 seconds after login or less.

After installation it also works, so that indicates that I must have built that one ISO image from a limited graphics mode because my antiX 19.3 and antiX a2 testing images also work.

I’ll mark this solved.

--
Brian Masinick

[Member Xecure]

There are many tutorials on the web on how to clone a partition, then edit fstab and update grub on them. You could even chroot into them.

The other option is to use Iso Snapshot tool to create a personal ISO copy of your system and use it (in live USB or booting the ISO from grub) to install your system to the other partition.

Do a bit of research and choose what you like the most or seems the easiest.

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

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

[Member Xecure]

On the antiX core+LXDE (on any computer it boots graphically), see if vesa xorg package is installed
apt policy xserver-xorg-video-vesa
This is what mine looks like:

$ apt policy xserver-xorg-video-vesa
xserver-xorg-video-vesa:
  Installed: 1:2.4.0-1
  Candidate: 1:2.4.0-1

The important part is the Installed: information (it must not be empty).
Two cases here:

If the Installed option shows a version, it means that vesa is installed. When you boot core+LXDE again on the “problematic” computer, select the boot menu option “Safe Video Mode”. This should bring you to a graphical boot.

If you don’t have the vesa driver installed, you will have to install it from the command prompt or install on a separate machine and remake the ISO file (or remaster the USB if on live), and then proceed with the “Safe Video Mode” boot menu option.

Let us know if that works for you.

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

Hi, first post here… A quick gidday and a question about a problem I can’t find a solution to so far.

I’m trying to run AntiX on my laptop and pretty sure it’s booting but still have a black screen. I have tested Ubuntu 20.04 LTS and the 20.10 Groovy Gorilla flavor, and have the same problem but it’s resolved with an edit of the grub at boot with the nomodeset instead of quiet splash on the /vmlinuz line. These distros aren’t very happy on my laptop for some reason, kernel panics and non-responding processes etc, and I like the really lite feel of AntiX and would like to try to get that running. Also systemd could be part of the issue and running AntiX would take that out of the picture for me.

I am having trouble with the the edit of “linux/antiX/vmlinuz quiet splasht disable=1xF menus”.

So far I have tried the following to boot into a live USB so I can install Antix…
linux/antiX/vmlinuz quiet menus
linux/antiX/vmlinuz menus
linux/antiX/vmlinuz nomodeset menus

The laptop is a Dell G5 5505 with an AMD Ryzen7 4800H / Raedon RX 2.9GHz, and using rufus 3.4 to cut my .iso on to the USB.
Does anyone know how AntiX wants to see nomodeset in this line or have another suggestion why I might have a black screen?

[Member PPC]

Last night I used app-select to take a peek at all .desktop files in my antiX 19.3.
I found 19 entries that started with “su-to-root” and tested half a dozen of them, adding them to the icewm toolbar with TIM- they all worked (they were also all GUI applications:

add blocker – tested and works
User management – tested and works
persistance configuration
persistance set up
save persistance changes
iso snaptshot
create live usb
format USB
repo manager- tested and works
one of the Synaptic .desktop files
? menu manager
one of gparted .desktop files
codec installer
package installer
gazelle installer
nvidea driver installer
live remaster
boot repair – tested and works
* rox filer as root – tested and works

I did not do a complete test, but it seems that really Ceni was the single antiX application that fails to be added to the icewm toolbar by TIM…

P.

[Anonymous]

In previous antixforum topics, I’m certain we have discussed howto (what is necessary) to customize. The “automated way” detail was not discussed, just howto assign custom O/S and release name to replace antiX… and whatall needs to be changed, in multiple places (and within the initramfs content) so that the customization will survive across remaster and/or snapshot operations. Any automation would hinge on (stack upon) running a script which, on-demand, performed the customization steps.

From foggy memory, I recall worrying that there was a sticking point related to performing a snapshot from an already installed-to-disk system. Upon installation to disk, several “live” components are removed… and later, if a snapshot is performed, a “installed-to-live()” routine does retrieve a fresh, current version, copy of those live -related files. Nowadays, the snapshot tool has a feature (must edit config file to enable?) which will PAUSE after the work directory has been populated with files, so that you can (??? unpack initramfs content, customize, repack) before iso-snapshot proceeds to generating the ISO file.

I tried “dpkg -S” as root [..] and it returned that they didn’t belong to any package

Also from foggy memory: anticapitalista posted to mention “while snapshot is paused, just edit the working directory copies of lsb-release and os-release.” I’m unsure whether that carries over to the “pretty-name” file which winds up populated along with the dynamically-generated during livesession “initrd.out” file.

/live/config (aka “/etc/live/config”)

$ ls /etc/live/config
boot-device  cmdline2  distro     font        lang         proc-cmdline  virtualbox
cmdline      disabled  dmesg.out  initrd.out  pretty-name  tsplash

[Member mikey777]

Xecure wrote:

<a href=”https://www.antixforum.com/forums/topic/problem-with-sourceforges-antix-19-4_x64-core-iso/#post-59938&#8243;
Is this after installing, after remastering + live-kernel-update or is this a different ISO?

This is the same 19.4-corex64+LXDE setup on the same machine that I mentioned already, the OS being installed onto the laptop’s internal SSD. Following installing and booting to the desktop, using the preinstalled 4.9 kernel, I used cli-aptiX to install two further kernels (4.4.0 and 5.10), just to compare CPU & RAM performance with each kernel. When I booted into 5.10, I selected this kernel from the grubscreen. No problems booting the OS with 4.4.0 and 4.9 – only 5.10 gives the blank screen.

• This reply was modified 1 year, 11 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]

mikey777 wrote:

I notice LTS Kernel version 5.4 is not listed in cli-aptiX – is there a reason for that ?

antiX kernels are built by the main developer. Keeping just 4 main versions is more than enough work, so if a new kernel is required, switch to 5.10. Alternatively, you can use Debian kernels if you need a specific version and they have it available (in repos).

mikey777 wrote:

Could the booting to a blank screen with Kernel 5.10 have anything to do with me deleting the entire “splash line” on the live-USB boot screen ?

Is this after installing, after remastering + live-kernel-update or is this a different ISO?

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

[Member Xecure]

al54 wrote:

Hi i just got the antix 19.4-runit=x64 iso to usb and got this message failed to load ldlinux.c32 boot failed any help tks.

You didn’t explain what software you used to make the live USB. You also don’t mention the edition (base, full, core, net?)

I just tested it on a VM and antix 19.4 runit full x64 boots properly, so your experience may be related to bad download or error with the USB maker.

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