Search Results for 'boot from iso'

[Member RickyRaccoon]

Brian Masinick wrote:

I should have posted these comments in the NEWER thread, but since I already posted here, I’ll post another comment regarding the Opera browser here too:
I tried it on Debian and the version reported is Version:79.0.4143.22; this version, for better or for worse, works fine.

I’ll try MX Linux and my two antiX images on this system and see if anything (BETA 2 for BOTH runit and sysvinit images) has resolved the issue; if not, the version cited above could be an alternative.

I’m having trouble with 79.0.4143.22 also. Last update antiX made, to that version, it broke. Doing the same thing, breaking on half the web pages out there. Today I updated to the same version, when booted to Linux Mint 20.2 Cinnamon, through the update manager and it’s running fine under Mint.

Note that this isn’t with the beta ISO- this is with the regular antiX 19.4 release. I have 19.4 on two different machines, and getting the same errors when trying to use Opera in the current version. I haven’t tried MX Linux yet- don’t have it installed atm but on Mint it’s fine.

[Forum Admin dolphin_oracle]

Xecure wrote:

dolphin_oracle wrote:

anyone missing boot menus? On vitualbox legacy boot I only have F1 and F2 menu options.

I cannot say about the 32bits one, but on the 64bits b2 ISO on Legacy boot, the first boot screen for selecting the kernel only has those two (F1, F2) menus on purpose (I think), as its only objective is selecting what kernel to use at boot. After selecting the kernel, you see the well-known legacy menus with all the Fn options. Is it perhaps the 32bits ISO the one with missing menus? (I haven’t tested it yet)

Ah I bet I’m just not familiar with the dual kernel boot menus. I’ll try again and report back.

[Member Xecure]

dolphin_oracle wrote:

anyone missing boot menus? On vitualbox legacy boot I only have F1 and F2 menu options.

I cannot say about the 32bits one, but on the 64bits b2 ISO on Legacy boot, the first boot screen for selecting the kernel only has those two (F1, F2) menus on purpose (I think), as its only objective is selecting what kernel to use at boot. After selecting the kernel, you see the well-known legacy menus with all the Fn options. Is it perhaps the 32bits ISO the one with missing menus? (I haven’t tested it yet)

dolphin_oracle wrote:

On a real live-usb, the UEFI boot menus worked oK but the desktop options apparently don’t match the current offerings. could switch from the icewm window manager menu OK.

My mistake for forgetting to send the changes. I think anticapitalista has fixed this for the next ISO.

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

[Member melodie]

Hi,

then I remove live-boot and live-boot-initramfs-tools. I don’t see any dependency package for them, however. I have searched in Synaptic and couldn’t find any. As for the qt5 packages I am now removing all the ones listed in this screenshot. On the second picture it is the qt5 packages kept.

I’ll rebuild right after and test the new ISO from there, and report back.

Attachments:

1. 

   VirtualBox_bento-antix-i486-sept-2021_14_09_2021_23_24_36.png
   

2. 

   VirtualBox_bento-antix-i486-sept-2021_14_09_2021_23_28_08.png
   

[Member arzarra]

VirtualBox version of VMWare video card in antiX 19.4 works fine as a video acceleration device, glxinfo reports standard VMWare card, glxgears shows high FPS etc. Only the TTY console fails to work properly. In the similar testing minimalist configuration of pure Debian 10 or 11 everything works flawless, TTY console resolution is OK. Therefore, it is antiX that misinterprets some data reported by the module vmwgfx during boot time (IMHO). Moreover, the resolution becomes wrong not after the system report that it has found this module, but during “waiting for /dev to be fully populated”.

If you add “blacklist=vmwgfx” to boot string, antiX live (all editions) boots and works fine, TTY console is OK. Video acceleration works too, glxgears shows similar numbers of FPS, glxinfo reports hardware acceleration to be “yes”. But glxinfo report information is different.
If you install antiX from “net” version of iso without blacklisting vmwgfx (and with corrupted console), and then add “blacklist=vmwgfx” to boot string, antiX works fine.

———————————————————————————————————————
So the FINAL SOLUTION is:
1. During boot of antiX live cd/dvd disks you must add “blacklist=vmwgfx” to boot string.
2. If you forget blacklisting VMWare video card module during boot time, do “setfont default8x16” or simply “setfont“. If after that you decide to install antiX onto hard disk, you must select “VGA” and “8×16” during install process (YES to “Do you want to set up console layout?” etc).
3. If you made mistakes twice (during live boot and during install) you must add “blacklist=vmwgfx” to boot string, boot into antiX, change FONTFACE=”VGA” and FONTSIZE=”8×16″ in /etc/default/console-setup , remove blacklisting from boot string (if you modified the config file, not grub menu field) and reboot.
———————————————————————————————————————-

[Member Robin]

Xecure wrote:

I tried it out on a VM, but it doesn’t work for me. Do I need to remove other boot parameters to work? What kernel versions work with this boot parameter?

Since I have tested 21 beta2 only Live from usb stick by now, without persistence, as I mentioned, the 4.9 kernel as shipped on the ISO is the only one I’ve tested by now. But I remember from setting up antiX 19 long ago that this code works also on a 4.19 kernel. I can confirm this as soon I’ll have once set up persistence and switched to the 686 pae kernel, which will be the 4.19 then.
Maybe the weak performance on my machine compared to the 19 I’ve manually fine tuned for this device already is due to the fact that 21b2 runs on a 486 kernel still. We’ll see.

You simply need to append this bootcode to make things work, in my case it reads
linux=1440x900
right at the end of the existing line. No need to remove any other parameter, at least in my case. Additional I use 1024×768 for terminal, from the f7 menu, but this is not mandatory. It works with and without the resolution setting for the terminal, it is independent from this. Maybe it doesn’t work on installed antiX, or in a virtual environment.
I’ve also tried to add a depth value, as defined for »grub gfxpayload linux« parameter, but this fails here:
linux=1440x900x32 doesn’t work. Moreover I believe any value not valid for or not supported by the graphics device will be ignored silently. At least I noticed that behaviour during my tests. So, if your virtual device driver doesn’t support the resolution you pass with this code, it will not have any visible effect.

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

[Member Xecure]

@calciumsodium I am glad it worked. The package version 019-7 in antiX 21 has an inbuilt check in the post install instructions to see what version should be installed (recent vs original buster version). As I mentioned before, the program that builds the ISO does it in a closed environment, so it will default to the “recent” firmware version. Reinstalling the package on a system that requires the older version should fix the problem (it would be great if you could test the same method described before, but instead of installing the buster version, reinstalling the bullseye version, to see if the script does its job properly and installs the older firmware).

Robin wrote:

In this place I’d like to plead for an additional entry in boot parameter selection:
linux=<width>x<height>
This cheatcode is not wellknown, not even documented

I tried it out on a VM, but it doesn’t work for me. Do I need to remove other boot parameters to work? What kernel versions work with this boot parameter? I am interested in this parameter.

Robin wrote:

Next thing: What does all the dmesg stuff about vulnerabilities mean?

Based on this thread (I cannot find if it is also true on kernel-org kernels compiled by anticapitalista), kernel 4.9 (32 bits) is not receiving latest kernel security patches, but kernel 4.19 (686-pae only) is (but that is for Debian; as I said, I am not sure if it is the same for antiX compiles kernels).

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

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

[Member calciumsodium]

Xecure wrote:

After checking the source code for firmware-b43-installer, if you reinstall it on antiX-21b2 live USB it should install the correct VERSION=”5.100.138″ firmware and then it should no longer be slow on your system.
As the build-iso environment doesn’t present any specific broadcom 43XX chip, it installs the latest version instead of the version for your hardware.

Please try the instructions in my previous post (reinstall firmware-b43-installer, unload and reload the b43-pci-bridge module, restart connman, and check if the connection is no longer slow). This will be a good point to take into account for when another user experiences the same issue and we can redirect at reinstalling this package.

Hi Xecure,

I reinstalled the firmware

sudo apt install –reinstall firmware-b43-installer

then I used antix-wifi-switch to reactivate connman

then I connected to the wifi network.

Network is still very slow.
I tried the centurylink speed test, but the network is just too slow. It did not even register on the centurylink speed test and caused an error. The highest download speed that I could see in conky was 16 Kb/s on this B2 32-bit live usb system.

Then I shutdown down and booted up in the installed antiX 19.1 system. I tried the centurylink speed test and the computer downloaded at a comparatively blazingly fast 17 Mb/s.

I think I will stop on this particular post on this issue. I will just keep this ze4900 system on antiX19.1.

Thank you Xecure for your time.

• This reply was modified 1 year, 8 months ago by calciumsodium.
• This reply was modified 1 year, 8 months ago by calciumsodium. Reason: new testing information

[Member melodie]

anticapitalista wrote:

Not sure if this helps you or not.
I just booted live antiX-19.4 (64 bit) which ships with installer version 1.5.1
Before installing I upgraded the installer to 1.5.4 then ran it.
No issues.

Ok…

1. Can you build/remaster Bento from a later antiX-19 iso?

I would rather avoid, the process takes lots of time as I build manually + aim 700MB max.

2. I just noticed that you are referring to the 32 bit version.
Does your 64 bit one have the same issue?

The 64bits is also up to date (rebuilt the day before I did the 32bits). It works perfectly and can see the storage device fine, as you can see (attaching a screenshot now).

Attachments:

1. 

   amd64-2021-09-13_23-48.png
   

[Forum Admin anticapitalista]

Not sure if this helps you or not.
I just booted live antiX-19.4 (64 bit) which ships with installer version 1.5.1
Before installing I upgraded the installer to 1.5.4 then ran it.
No issues.

Possible suggestions:

1. Can you build/remaster Bento from a later antiX-19 iso?
2. I just noticed that you are referring to the 32 bit version.
Does your 64 bit one have the same issue?

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

antiX with runit - leaner and meaner.

Hello!

I am preparing new ISOS 32 and 64bits with some cosmetic improvements and refined choices. I stared about 10 days ago and was stopped by the installer crashing on my new respins when testing in Virtualbox : the installed DOES NOT SEE the storage unit!

The base I use is antiX 19.

This is what the output of the line in error looks like when I start minstall manually from the console:

SErr #18: “lsblk: unknown column: -bJo\nlsblk: TYPE,NAME,UUID,SIZE,PTTYPE,PARTTYPE,FSTYPE,LABEL,MODEL,PARTFLAGS: not a block device\n”

I have pinpointed when and how : I had first thought it might be caused by me removing some packages that I should not have removed (it had happened before), so I reverted to a previous version I had done which works perfectly, and I restarted rebuilding on it.

Then I decided to do all I wanted in it except one thing : I didn’t update the distro before redoing the snapshot!

And this one works!

So I reused it immediatly, installed, this time I updated, redid a respin and BAM ! This time the installer does not see the virtual disk!

This is why I am now coming here to ask for help.

I have prepared some files, screenshots, outputs of console, logs from the live where the installer fails.

$ su-to-root -X -c minstall
Gkr-Message: 19:13:16.809: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
Gkr-Message: 19:13:21.120: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
Gkr-Message: 19:13:21.122: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
qt5ct: using qt5ct plugin
QFSFileEngine::open: No file name specified
Cannot write to installer log: “/var/log/minstall.log”
Installer version: 1.5.4
+++ void MInstall::startup() +++
check for remastered home demo folder: false
Exec #1: du -sb /live/aufs/boot
Exit #1: 0 QProcess::ExitStatus(NormalExit)
linuxfs file is at : “/live/boot-dev/antiX/linuxfs”
Exec #2: dd if=/live/boot-dev/antiX/linuxfs bs=1 skip=20 count=2 status=none 2>/dev/null | od -An -tdI
Exit #2: 0 QProcess::ExitStatus(NormalExit)
linuxfs compression type is “4” compression factor is 25
Exec #3: df /live/linux –output=used –total |tail -n1
Exit #3: 0 QProcess::ExitStatus(NormalExit)
linuxfs file size is 2756706304 rootfs file size is 0
Minimum space: 268435456 (boot), 3830448128 (root)
Exec #4: uname -m | grep -q i686
Exit #4: 0 QProcess::ExitStatus(NormalExit)
Exec #5: grep -q 64 /sys/firmware/efi/fw_platform_size
SErr #5: “grep: /sys/firmware/efi/fw_platform_size: Aucun fichier ou dossier de ce type\n”
Exit #5: 2 QProcess::ExitStatus(NormalExit)
uefi = false
+++ void MInstall::setupAutoMount(bool) +++
Exec #6: ps -e | grep ‘udisksd’
SOut #6: ” 2590 ? 00:00:00 udisksd\n”
Exit #6: 0 QProcess::ExitStatus(NormalExit)
Exec #7: egrep -l ‘^[^#].*mdadm (-I|–incremental)’ /lib/udev/rules.d
SErr #7: “grep: /lib/udev/rules.d: est un dossier\n”
Exit #7: 2 QProcess::ExitStatus(NormalExit)
MkPath(SUCCESS): “/run/udev/rules.d”
Exec #8: echo ‘SUBSYSTEM==”block”, ENV{UDISKS_IGNORE}=”1″‘ > /run/udev/rules.d/91-mx-udisks-inhibit.rules
Exit #8: 0 QProcess::ExitStatus(NormalExit)
Exec #9: udevadm control –reload
Exit #9: 0 QProcess::ExitStatus(NormalExit)
Exec #10: udevadm trigger –subsystem-match=block
Exit #10: 0 QProcess::ExitStatus(NormalExit)
Exec #11: /bin/ls -1 /home | grep -Ev ‘(lost\+found|demo|snapshot)’ | grep -q [a-zA-Z0-9]
Exit #11: 1 QProcess::ExitStatus(NormalExit)
check for possible snapshot: false
+++ void MInstall::setupkeyboardbutton() +++
Exec #12: find -L /usr/share/zoneinfo/posix -mindepth 2 -type f -printf %P\n
Exit #12: 0 QProcess::ExitStatus(NormalExit)
Exec #13: locale -a | grep -Ev ‘^(C|POSIX)\.?’ | grep -E ‘utf8|UTF-8’
Exit #13: 0 QProcess::ExitStatus(NormalExit)
Exec #14: grub-probe -d /dev/sda2 2>/dev/null | grep hfsplus
Exit #14: 1 QProcess::ExitStatus(NormalExit)
Exec #15: dpkg -s samba | grep ‘^Status.*ok.*’ | sed -e ‘s/.*ok //’
SErr #15: “dpkg-query: le paquet \xC2\xAB\xC2\xA0samba\xC2\xA0\xC2\xBB n’est pas install\xC3\xA9 et aucune information n’est disponible\nUse dpkg –info (= dpkg-deb –info) to examine archive files.\n”
Exit #15: 0 QProcess::ExitStatus(NormalExit)
+++ void MInstall::buildServiceList() +++
+++ void MInstall::updatePartitionWidgets(bool) +++
+++ void BlockDeviceList::build(MProcess&) +++
Exec #16: partprobe -s
SOut #16: “/dev/sda: msdos partitions 1 2\n/dev/sr0: msdos partitions 2\n/dev/zram0: loop partitions 1\n”
SErr #16: “Warning: Unable to open /dev/sr0 read-write (Syst\xC3\xA8me de fichiers accessible en lecture seulement). /dev/sr0 has been opened read-only.\nWarning: Unable to open /dev/sr0 read-write (Syst\xC3\xA8me de fichiers accessible en lecture seulement). /dev/sr0 has been opened read-only.\nWarning: Unable to open /dev/sr0 read-write (Syst\xC3\xA8me de fichiers accessible en lecture seulement). /dev/sr0 has been opened read-only.\n”
Exit #16: 0 QProcess::ExitStatus(NormalExit)
Exec #17: blkid -c /dev/null
SOut #17: “/dev/loop0: TYPE=\”squashfs\”\n/dev/sda1: UUID=\”74321680-92b7-48cb-87af-43cce4a47526\” TYPE=\”swap\” PARTUUID=\”9e343378-01\”\n/dev/sda2: LABEL=\”rootantiX19\” UUID=\”cc346124-ba70-4900-ab3a-8c124b99e21d\” TYPE=\”ext4\” PARTUUID=\”9e343378-02\”\n/dev/sr0: UUID=\”2021-09-13-07-00-58-00\” LABEL=\”antiXLIVE\” TYPE=\”iso9660\” PTUUID=\”5082fcfe\” PTTYPE=\”dos\”\n/dev/zram0: LABEL=\”SWAP_ZRAM0\” UUID=\”32e1350d-9255-48ba-9499-85596e8fccf3\” TYPE=\”swap\”\n”
Exit #17: 0 QProcess::ExitStatus(NormalExit)
Exec #18: lsblk -T -bJo TYPE,NAME,UUID,SIZE,PTTYPE,PARTTYPE,FSTYPE,LABEL,MODEL,PARTFLAGS
SErr #18: “lsblk: unknown column: -bJo\nlsblk: TYPE,NAME,UUID,SIZE,PTTYPE,PARTTYPE,FSTYPE,LABEL,MODEL,PARTFLAGS: not a block device\n”
Exit #18: 32 QProcess::ExitStatus(NormalExit)
Name Size Model FS | isDrive isGPT isBoot isESP isNative isStart isNasty
Exec #19: lsblk -T -bJo TYPE,NAME,UUID,SIZE,FSTYPE,LABEL /dev/mapper/* 2>/dev/null
Exit #19: 32 QProcess::ExitStatus(NormalExit)
Segmentation fault
[demo@antix1:/usr/share/applications/antix]
$

(same result using sudo).

Here is a full zip also including the content from /etc/apt and /var/live : https://nextcloud.orditux.org/s/Lo3qoGg9jf6DBEQ

Thanks for your help! “:-)

Attachments:

1. 

   drive-not-seen-2021-09-13_19-04.png
   

2. 

   drive-not-seen-2-2021-09-13_19-04.png
   

3. 

   minstall-direct-log-2021-09-13_19-24.png
   

1. synaptic-history-last-update-sept-13-before-the-crash.txt

[Anonymous]

look into it, to understand really what is happening.

As an automated step during antiX installation to hard drive, a housekeeping operation “live-to-installed” is performed.
I cannot recall whether the code for “live-to-installed” resides within the installer source code or is a freestanding utility script.
Among other details, the operation removes the no-longer-needed installer package
(would be confusing to still have an “install” icon on the desktop post-install, eh)
Perhaps that operation similarly regards “guest additions” as no-longer-needed, and automatically uninstalls the asssociated package.

> but remastering it it “loses” the Virtual Box Extensions

The term “remastering” may be too generic here.
live-remaster, which can only be performed from within a liveboot session, faithfully preserves the system content (including GuestAdditions packagefiles).

If proceeding from an already installed system, “iso-snapshot” does perform a “installed-to-live” routine (you can grep its source code to review the nitty-gritty details)… but IIRC does NOT automatically (re)inject GuestAdditions (nor does a user-configurable option exist within iso-snapshot to address this detail).

If proceeding from an already installed system, “live-usb-maker” probably does not automatically (re)inject GuestAdditions.
For live-usb-maker to produce a liveUSB in which GuestAdditions are pre-installed, you might:
temporarily install GuestAdditions onto the system prior to launching live-usb-maker and utilize its “clone(ing)” option.

Background:

I would love to have a AntiX Live CD with development tools and Virtual Box Guest additions already installed.
The purpose is to teach C/assembly programming (in Linux) to students who already have a Windows or OSX machine, and don’t want/need/know to install Linux.
The Live CD with Virtual Box allows a fast start, and when the student manages to “corrupt” the Linux machine, all that is needed is a reboot.
The students save their work to a shared folder

Up to now, installing all the required software is easy, the virtualbox-utils package works ok, but when making an ISO from an “Hard disk” installation or remastering a Live USB, the VirtualGuest additions stop working.

I am using AntiX 19.4 64 bits (base) ISO.
Any clues, ideas or debug strategies to follow?

Many thanks for AntiX.
paf

• This topic was modified 1 year, 8 months ago by paf.

[Member seaken64]

32-bit

I installed antix21b2 on a Pentium 4 machine today. It booted fine but I had to un-blacklist the B44 driver to get the ethernet to work. I installed SeaMonkey and Palemoon from the Package Installer with no problem. Then I ran the Snapshot program and made a snapshot iso. It took about 20 minutes. The I used Live USB Maker to create a Live USB. That took about 5 minutes. Then I rebooted and booted to the newly created Live USB. No problems at all.

I moved the Live USB/Snapshot over to one of my Pentium-III machines and booted it up using Plop. It booted with no issues. Ethernet was up. The wallpaper was the same as I had chosen on the P4 and the SeaMonkey and Palemoon browser were ready to go (although they won’t run on this non-SSE2 machine). But everything works good.

Snapshot worked beautifully on my tests.

Seaken64

• This reply was modified 1 year, 8 months ago by seaken64.

[Forum Admin anticapitalista]

I’d like to get some feedback on the following for both 32 and 64 bit versions:

* persistence and remastering both in English and localised running live (frugal or from usb device)
* general localisation of menus, apps (live or installed)
* iso-snapshot in English and localised – does the new snapshot boot (on metal and in a virtual environment)? What about the boot menus?
* is Repo-manager working properly now?
* are there any apps that fail to install via package installer?
* are there any pre-installed apps that fail to open from menus, control centre?
* are there any pre-installed apps that open, but crash don’t seem to work?

Thanks.

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

antiX with runit - leaner and meaner.