Search Results for 'boot from iso'

I just noticed control centre got uninstalled on me, without me doing anything…
I downloaded and tested the latest antiX 19.4 iso on virtualbox, I run antiX-updater, saw it had one update to make, I did not want to install anything at the time, so I selected “no”… continue testing 19.4 – noticed that the “other desktops” menu entry under Menu > Applications > Other Desktops did nothing, tested it in my installed antiX 19.3- I’m using fluxbox, so I selected icewm- it did nothing also… some minutes later, I tried clicking the control centre from the main menu- it did nothing. I tried launching from the terminal- nothing… so I rebooted- nothing.

Solution:
I had to manually reinstall it (sudo apt install antix-cc-full-antix) but I got an older version of the control centre (without the “software” tab, etc)…

How does something like this happen, out of the blue? Also, what’s the right package to install, to get the latest control centre back?

The right command to get Control Center back:
sudo apt install control-centre-antix

P.

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

[Member al54]

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.

[Member frtorres]

Thanks @Xecure.

I Tested using your advised boot options,

Results:

booting the kernel keeps:

waiting for /dev/ to be fully populated.

See attachment.

I was following this howto:

Basically I used a VM 1Gb RAM configuration with a

1- 2GB disk (where I copied Antix ISO File using [dd if= of] )
2- 30GB for HD Installation.

By means of Linode Web Interface, I booted Antix ISO File

ISO used: antiX-19.3_x64-full.iso

I tested this procedure successfully with other debian and slackware distros but I want Antix because this VM with 1Gb RAM and USD5 montly is suitable for Antix and my needs as a remote desktop.

Any hint or advice? (maybe other Antix ISO?)

Thanks again for your kind help.

Francisco

Attachments:

1. 

   Antix-boot-linode.png
   

[Anonymous]

is it really grub?

About the Grub LegacyBIOS boot screen , by choosing the 1) Legacy mode, the kernel 5 was installed automatically on my computer.
I really need an explanation about the first 2 lines of the Grub.

The liveboot .iso file contains 2 kernels.
Choosing the “first line” instructs use of kernel #1 for the current liveboot session.
Choosing the “second line” instructs use of kernel #2 for the current liveboot session.

[Anonymous]

For the persistence+remaster scripts, the gitlab repository contains only .mo files (no .po files). I found no .pot file, so cannot easily check whether the same string is given for “setup” and for “configure”.
https://gitlab.com/antiX-Linux/remaster/-/tree/master/locale/es/LC_MESSAGES

In the context of the program(s), these 2 terms are vague even in English.

setup:
create; establish;
user decides, and and specifies, several parameters
(home-only persist vs home+root)
(dynamic vs static)
(size of persistence savefile)
(operation “mode”: manual vs semi-automatic vs automatic save)

configure:
user may elect to change various previously-speficied parameter values.
For instance, increase the size of the savefile container
or choose a different “operation mode”
___________________________

Even “mode”, in this context, is vague in the English usage.
Mode is the term I have been using, across years, but within the program no formal term (“mode” or otherwise) is given.

    $(gt "Configure root persistence saves to run either:")
1) $_Automatic_[/] ($(gt "at shutdown/reboot, no asking"))
2) $_Semi_Automatic_[/] ($(gt "ask at shutdown/reboot"))
3) $_Manual_[/] ($(gt "you snooze, you lose"))"

Configure-Persistence-french-ellipse.jpg

No, I do not see the same as shown in that screenshot.
Instead, I find this:

I can’t guess how, or why, multiple//redundant menu entries are displayed.
instead of guessing, tracked down the likely cause of the redundant menu entry labels
~~ cited in my followup ppost

Did the reporter browse or grep /usr/share/applications/ (and /usr/share/applications/antix/) to determine whether or not multiple .desktop files containing identical icons (and text string on Name= line) are present?
.
If multiples are present, the following will enlighten us as to which packages provided (installed) the files:
dpkg -L /usr/share/applications/TWIN_1.desktop
dpkg -L /usr/share/applications/TWIN_2.desktop
^— If no matching package is found for a file, that would indicate:
1) either the file was pre-installed (was injected during the pre-release “build-iso” process)
2) you, or your cat, or your grandma… someone using your local machine accidentally created the file

re “browse or grep”:
? Did the reporter also ruleout presence of user-created .desktop files, pathed under ~/.local/

Perhaps, on the reporter’s affected machine, the “Add Menu Item” hickeydoodle was used and TWIN_1.desktop was edited, filename (but not icon and text string on Name= line) was changed, and was savedAs TWIN_2.desktop
^——- This is a potential cause of the reporter’s redundant menu entries

I didn’t reread today all the posts here. Possibly the reporter’s machine was originally antiX 17… and was upgraded to 19… and, along the way, a different name was applied to a .desktop file in the “packageX” (which, in antiX19 release, may also have changed)(the packagename of the package associated with installing one of the twin sibling .desktop files)?

chasingmytailchasingmytailchasing

[Member melodie]

christophe wrote:

Now you might argue that antiX is already light, whatever desktop you choose, which is right, but it’s too large to fit in some of the very old laptops when booted as live, once the squashfs is decompressed it fills all the RAM and the boot process hangs.

When booting live, try persist_static or p_static_root (and definitely not toram) in cases like that. This will not use your RAM for storage.

You see this is not the issue. I have been very much used to these things along the years, and I don’t use toram. I don’t need to. However I have not see a p_static_root in the options.
And it remains that the ISO is too large to be burned on a regular CDROM (as many Linux distros now) whereas some computers have only two options : install from CD, or install from another computer and reinstall the hard drive or SSD afterwards (which is not always quite convenient).

Therefore I still think pursuing the goal of created a spinoff that works out of the box using the best of what antiX provides is still worth pursuing.

[Member melodie]

Xecure wrote:

Search the antiX forums first.

I didn’t search the forum, because it has beeen a _random discovery_ while trying several light GNU/Linux distributions in order to attempt to revive a very old laptop. (18 years old, but very nice looking on the outside).
I had discovered Devuan which I didn’t know of, as well as their snapshot tool, and tried to figure how to have the poweroff reboot etc. working with lightdm instead of slim. Both antiX and Devuan use no systemd with elogind and so on, so I figured I might try the same method on antiX.

Now what you are saying makes me think, I’ll try your way, no additional package else than pm-utils, well at least I’ll try removing both “libpolkit-gobject-elogind-1-0” and “libpolkit-backend-elogind-1-0” (devuan8 packages) and see what happends. I keep both as deb packages in a directory just in case.

But : shouldn’t them packages in the antiX distribution sources be the same version so that installing one will not create a conflict preventing the other to be installed? Shouldn’t it be an issue that should be addressed? (I am not sure how, obviously… )

I enclose a screenshot of Synaptic in antiX 64bits, with emphasis on the two packages and *the versions mis-matching* offered as a *possible update*.

Also : openbox is a window manager with some advanced features, not a desktop manager nor an environment manager so it relies not on itself to manage the desktop, but on the components which are installed along with it. LightDM meaning Light Desktop Manager, the session will require a few things to be working properly as for a full fledged Desktop Environment such as LXDE for instance, but with just some of its components the system will be even lighter.
Now you might argue that antiX is already light, whatever desktop you choose, which is right, but it’s too large to fit in some of the very old laptops when booted as live, once the squashfs is decompressed it fills all the RAM and the boot process hangs.

Also antiX and its Snapshot program is a great tool to have to make your own version. The users targeted for the versions I rebuild are *end users* with *limited needs*, so I make the ISOS as small and simple to use as possible and the users can have it evolved later as they see fit (of course they can ask for help to do that if necessary). You can have a go with the latest 32bits available, here : http://downloads.linuxvillage.org

As soon as a similar 64bits will be ready, I’ll try to write full descriptions with a few screenshots.

Thanks for your help.

• This reply was modified 1 year, 12 months ago by melodie.
• This reply was modified 1 year, 12 months ago by melodie.

Attachments:

1. 

   VirtualBox_antiX-base-64bits.png
   

[Member Xecure]

I have no idea how Linode handles the ISOs. Maybe it requires a network PXE install method on the ISO.

The error seems to be that it cannot find the boot devise. Try using the boot parameter
from=all toram
to see if that helps to initially boot it on the Linode server.

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

Hi all

I have been trying to install Antix-19.3-x64-full *15 October 2020) in a Linode VM 8gb RAM and 160 GB on disk.

I followed this howto>:

install-a-custom-distribution-on-a-linode

ISO file boots ok to grub2 menu but when trying to install I got:

Fatal Error
No usb,cd devices found
p=power off
r=reboot
Select p or r  then press <enter>

I tested other distros and the installer find disks to install and all continues ok.

Any Antix community member with some previous experience installing Antix in a Linode VM?

Maybe another ISO file with a different kernel could help?

Thanks in advance for any hint to make some progress on this.

Francisco

[Member einpoklum]

As requested:

$ cat /etc/fstab 
# Pluggable devices are handled by uDev, they are not in fstab
UUID=2f928b9e-c473-4f34-b086-7e7069021a3d / ext4 defaults,noatime 1 1
UUID=9914d994-8b38-4354-b65f-313e9be87640 /boot ext4 defaults,noatime 1 1
UUID=20cdd61c-5d84-48fc-bfa1-f67b864584c0 swap swap defaults 0 0 
#-> /dev/sda2
UUID=681C84621C842D5E                      /media/681C84621C842D5E                     ntfs-3g    noauto,noexec,uid=1000,gid=users,dmask=002,fmask=113,users  0 0
/dev/cdrom                                 /media/cdrom                                iso9660    noauto,exec,users,ro            0 0
/dev/cdrw                                  /media/cdrw                                 iso9660    noauto,exec,users,rw            0 0
/dev/dvd                                   /media/dvd                                  udf        noauto,exec,users,ro            0 0
/dev/sr0                                   /media/sr0                                  auto       noauto,exec,users,ro            0 0

and also:

# setcd -i /dev/sr0
/dev/sr0:
  Disc found in drive:Unknown status 0

and I assure you – the drive is empty. Using watch, it doesn’t seem to change over a couple of minutes.

• This reply was modified 2 years ago by einpoklum.
• This reply was modified 2 years ago by einpoklum.

[Member einpoklum]

Xecure wrote:

Before you installed antiX, did you boot from CD/DVD or from USB?

USB. Well, ok, actually, not quite: I installed plop on an existing Windows install and booted from USB through that.

Xecure wrote:

If on USB, did this issue also occur during the live-USB experience?

Don’t know, the only thing I did when booting the live USB was start the installation…

Xecure wrote:

Please make sure you have sr0 configuration in /etc/fstab and set to noauto.

Naturally. It’s:
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0

Xecure wrote:

If you can boot from USB, try booting on live-USB and seeing if there is the same issue.

The BIOS doesn’t support USB booting, and unfortunately, it seems grub’s installer doesn’t include the necessary drivers for me to see the USB partition 🙁

Xecure wrote:

If you think this is kernel related, use the package installer to test a different kernel version (be it legacy 4.4.0-XXX or newer 4.19.xxx) o the installed system (and selecting it in grub).

I’ll try that too and report.

• This reply was modified 2 years ago by einpoklum.

[Member Xecure]

Move to an 4.19 kernel instead of a new 5.XX kernel. The jump to kernel version 5.XXX on my laptop also brought super-sensitivity on my touchpat. I now enjoy this high sensitivity (and feel it is dragging in Windows in comparison).

If you are not using kernel 5.XXX (or simply want to keep it but reduce the sensitivity separately), you can do one of 2 things:

A. Use synclient to change synaptics properties on the fly (and add them to startup to make them take effect when the antiX session starts)
See all variables that can be changed with
synclient -l
For example, you can reduce maximum touchpad speed with
synclient MaxSpeed=1
And also reduce the acceleration factor to 0.01
synclient AccelFactor=0.01
You will need to experiment to figure out what values you are comfortable with.
Once you are happy, you can add them to startup or use this information in B

B) Edit with admistrator permissions the file /etc/X11/xorg.conf.d/synaptics.conf
sudo geany /etc/X11/xorg.conf.d/synaptics.conf
and edit the variables mentioned in A) there.
Save the file and reboot. Next time you log in you will see that the touchpad sensitivity will automatically follow the changes you made in the synaptics.conf file.

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

[Member Robin]

I have adressed this problem some time ago, describing a workaround. The more differences to ISO file will come, the bigger gets this problem.

Robin wrote:

Let me append some remarks to the upgrade of Live antiX (persistance). I noticed that meanwhile it is impossible to perform a complete upgrade on a fresh antiX 19.3 full on a computer with 2GB RAM installed. Some of the packages can’t get installed due to lack of free space, and it is impossible to remaster also. I’ve seen you have 3.6 GB RAM if I’m not mistaken, so maybe you ran into the same trap, which corrupted your system possibly. You should carefully watch whether all of the packages do install correctly, allways check the terminal output for this immediately.
In case you also encounter the lack of memory problem on apt upgrade antiX, you’ll have to upgrade some packages in a first run (you need just to keep enough space left in memory for remastering), then save persistence and remaster, then reboot and again upgrade the next packages, save persistence and remaster and reboot again, and so on, until you have anything upgraded. And finally create a fresh backup copy of your upgraded system. This will keep you safe from experiences like what you have to moan about now.

Maybe antiX developers could automatise this process of “chunk updating”, as proposed by seken64 in his original post starting this thread.

Windows is like a submarine. Open a window and serious problems will start.

[Anonymous]

Tested creation of personal snapshot. Boots fine.
Label displayed for the first entry on the legacy bootmenu screen is simply “antix” (noquotes).
Previously, did the use of iso-snapshot with default settings yield a label bearing a YYYYMMDD suffix? Seems different, but maybe the change was intentional, by design.

an observation: slim-themes-extras-antix is not listed as a dependency of slim package, so no warning is issued if that package is purged… but its removal will, per the default configuration, cause slim to fail (cannot find background image, so it pukes/quits).

Just a FWIW note: .desktop (and menu entries) remain if calcurse or luckybackup package is purged

ControlCenter } Hardware } Mouse Configuration
adjusting “cursor size” seemed to have no effect (even after loogut/login)

[Anonymous]

The help texts for the F1 key option in the antiX boot menu

I studied this a while back and did not arrive at a clear understanding.

We can see, and can merge request changes to, the in-English F1 paginated help text(s) here:
https://gitlab.com/antiX-Linux/antiX-Gfxboot/-/blob/master/Help/antiX/en.html

The name (en.html) implies that other, localized, helptexts could be introduced.

Apparently, the “gfxboot” program would be installed on a distro curator’s system.
The curator would place sibling NN.html files in the project directory alongside en.html,
then issue a command ala “gfxboot –add-languages NN OO PP”.
IIRC, the output is a cpio archivefile, to be placed among the set of files which will be bundled within the initrd.gz

To simulate what the result will look like, how it will render, under grub or under isolinux or under syslinux… a curator runs a separate utility program, “gfxtest”.

The “maker” documentation provided for gfxboot is sparse, and the version of gfxboot used in antiX is very old (like, a decade or more, compared to the same-named “gfxboot” version maintained by opensuse). Even if translated NN.html files are submitted, I am not confident that the “old” version provides the necessary font resources to render a wide gamut of font glyphs. To wit: several of the opensuse changecommits across recent years have been toward providing expanded font coverage.

the “press F1 for help” message is fixed and does not translate when we use F2 to select a new language

I was not aware of that, and am quite surprised to read that detail. Now I’m left wondering whether the “gfxboot –add-languages NN OO PP” detail which I had found in the maker docs only merges the .po files.