Search Results for 'boot from iso'

[Anonymous]

I just downloaded to try out and noticed that the iso image
name that gets downloaded doesn’t match the name in the md5 file.
also is this going to be a strictly 64-bit thing?

Also @caprea: maybe have to try connman as that’s what 19 uses by default
for connections….to use ceni or wicd had to uninstall connman and reboot
on the official 19 alpha.

[Forum Admin BitJam]

Miguipda wrote:

With Antrix indtalled on USB selecting the persistant_all (and certainly other persistant) option does not allow to select the same USB Drive as destination space to store the persistant data.

The USB has its autogenerated partitions to which de Can not select it as destination.

As I do not want to store it anywhere else could somebody explain how to get it on this Live USB?

I’m sorry you have having so much trouble. It sounds like you created the live-usb with a tool that does not allow you to use all of our live-usb features. We have no control over the various live-usb creation tools. We have tried to be as compatible with them as possible so you can at least boot our system when you use these tools but almost none of them allow you to use all of our extensive live features.

We provide a tool called “live-usb-maker” that will make a full featured live-usb that will allow you to do what you are requesting. Here are 3 different ways you can use it to create a live-usb:

1) If you have a 2nd usb-stick available then boot your current live-usb. After it has booted, plug in the 2nd usb-stick and run live-usb-maker. It will give you an option to “clone this live system”. Select that option and it will make a full featured live-usb on the 2nd live-usb stick. You will be able to enable persistence normally on this new live-usb.

2) If you don’t have a 2nd usb-stick available but you do have some other Linux system then you can download live-usb-maker from my repos. You need to first install the “git” program if it is not already installed. Then run:

git clone https://github.com/BitJam/live-usb-maker
git clone https://github.com/BitJam/cli-shell-utils
cd live-usb-maker
sudo ./live-usb-maker -f $ISO_FILE"

where $ISO_FILE is the iso file you want to make the live-usb from.

3) If neither of these solution are good for you then as a last resort, you could order an antiX live-usb from OSDisc. They use our live-usb-maker tool to make their MX and antiX live-usbs so you will be assured to have all of our live features available.

I hope at least one of these methods work for you.

• This reply was modified 3 years, 11 months ago by BitJam.

Context is worth 80 IQ points -- Alan Kay

[Member orcrist]

Thank you BitJam for the interest. Sorry for my late response – I hadn’t had access to my computer for several days.

I’m afraid that my laptop does not boot UEFI, so the solutions that concern UEFI do not apply…

pan@Lifebook-S761:~
$ sudo efibootmgr 
EFI variables are not supported on this system.
pan@Lifebook-S761:~
$ 

I have nevertheless tried the –gpt solution but to no avail. I have also tried with the stick burned with dd. Same result.
I am always talking about the antiX-17.4.1_x64-full.iso – you are right, 17.1 and 17.3 do work. I have not tried to update my BIOS as I have no idea how to do it (I believe it should be done through Windows) and I am afraid to try, to be honest.

This is not a big problem for me as I can always burn the stick with a 17.3 version of antiX and then update it with the 17.4 version. But I can not be sure that the same will apply to the 19.0 version when it is ready.

• This reply was modified 4 years ago by orcrist.

[Member Xaver]

Thank you for the bugfix.
The iso is booting well now in VirtualBox and from USB stick too.

ISOs created with iso-snapshot-antix 0.3.1 do not boot:
Fatal Error
Neither aufs nor overlayfs is available

In the repo there also is a package iso-snapshot 0.1.4.1
Which one is the better choice?

• This topic was modified 4 years ago by anticapitalista.

[Member koolstofje]

He doesn’t want to boot after an iso snapshot.

Neither aufs nor overlays is available..

[Member dacomboman]

Wish i could understand German!

At present time, i’m dual booting with another Linux distro on Windows 10.
Everything there works just fine.

What i find odd, is that i can boot live mode from usb with any Linux distro (.iso) just as it did with Antix,
but now that Antix is installed on it, it ceases to work (from cold boot with F9 as it is an HP).

I have uploaded an xdelta patch here

To use this patch, you will need the antiX-19.a1_x64.iso and the patch in the same directory.

In a user terminal:

xdelta3 -d -s antiX-19.a1_x64-full.iso antiX-19-a1_a2_x64.xdelta antiX-19.a2_x64-full.iso

md5sum for the patched iso should be:

md5sum antiX-19.a2_x64-full.iso
0c5b0755460875c4119b45901e1b8b5e  antiX-19.a2_x64-full.iso

Please test the following.

* fixed slim ‘double’ login bug
* UEFI boot
* connman wired and wireless. If you want to use ceni, you’ll need to remove connman
* New icon theme available (Papirus) (not default) To make the changes -see below.

antiX-papirus theme:

This is particularly useful for fluxbox users, since the default theme looks awful.

In /home/demo/.fluxbox there should be menu-papirus file.
Rename (after saving the other) to menu.
Use lxappearence to set default icon to papirus-antix
Update Menu
Restart fluxbox

Note – the icon theme is not complete, but you should get some idea of how good/bad the icons look in fluxbox.

You can repeat the above steps for IceWM and JWM as well.

To change the control centre icon theme to match, edit (as root) antixcc.sh in /usr/local/bin
Simply #comment the antix-numix line and uncomment the antix-papirus one.

Do the same to the logout menu by editing /usr/local/lib/desktop-session/desktop-session-exit.py

Note that I realise the control centre icons are not all complete.

My opinion is to use the antix-papirus icon theme rather than the numix-bevel one,
which is one of the reasons for this patch. I will not upload the full a2 iso.

Note: This is still alpha quality, there are lots of bugs and not all the reported issues in the a1 feedback thread have been implemented.

• This topic was modified 4 years ago by anticapitalista.
• This topic was modified 4 years ago by anticapitalista.

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

antiX with runit - leaner and meaner.

[Forum Admin BitJam]

A Google(Could not get fio for li->DeviceHandle: Unsupported) shows other people have this problem on other distros. The first hit was for a Fujitsu Lifebook computer with Ubuntu.

I compared our antiX-17_x64-full.iso with antiX-17.1_x64-full.iso and there were no differences in the Grub bootloaders except in grub.cfg, help.txt and theme.txt. HOWEVER the Grub bootloader did get upgraded in antiX-17.4. So my guess is that 17.1 and 17.3 will also work for you.

If you can legacy boot then try that. otherwise, the only thing I can suggest is to make sure your BIOS/UEFI is up to date. Our dev fehlix may have other ideas. We were forced to upgrade Grub because the signing key of the older version was blacklisted or expired so there were a number of machines it couldn’t boot on even if secure boot was disabled.

There may be a fix in the Google search results but if you can’t boot legacy and you cant’t upgrade the BIOS/UEFI (or the upgrade fails to fix the problem) then I think the only answer might be that you have to downgrade Grub on the live-usb to get it to boot UEFI on your Lifebook. IOW, replace the directories /boot/grub and /EFI on the broken live-usb with the same directories on the working one. This may be confusing because the grub menu will list the wrong version of antiX unless you copy back in the original grub.cfg from the broken live-usb.

Context is worth 80 IQ points -- Alan Kay

This is the message I get when trying to boot from USB:

Could not get fio for li->DeviceHandle: Unsupported
Failed to find fs: Unsupported
Failed to load image \EFI\BOOT\grubx64.efi: Unsupported
start_image() returned Unsupported

My machine specs:

pan@LIFEBOOK-S761:~$ inxi -FG
System:    Host: LIFEBOOK-S761 Kernel: 5.0.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.32.0 
           Distro: Ubuntu 19.04 (Disco Dingo) 
Machine:   Type: Laptop System: FUJITSU product: LIFEBOOK S761 v: 10601115935 serial: <root required> 
           Mobo: FUJITSU model: FJNB225 v: B1 serial: <root required> UEFI [Legacy]: FUJITSU // Phoenix v: Version 1.20 
           date: 04/26/2013 
Battery:   ID-1: CMB1 charge: 2.1 Wh condition: 2.4/62.2 Wh (4%) 
CPU:       Topology: Dual Core model: Intel Core i5-2520M bits: 64 type: MT MCP L2 cache: 3072 KiB 
           Speed: 831 MHz min/max: 800/3200 MHz Core speeds (MHz): 1: 797 2: 797 3: 797 4: 797 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915 v: kernel 
           Display: x11 server: X.Org 1.20.4 driver: i915 resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 19.0.2 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel 
           Sound Server: ALSA v: k5.0.0-13-generic 
Network:   Device-1: Intel 82579LM Gigabit Network driver: e1000e 
           IF: enp0s25 state: down mac: 5c:9a:d8:e0:c8:35 
           Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi 
           IF: wlp2s0 state: up mac: a0:88:b4:28:d5:bc 
           Device-3: Sierra Wireless type: USB driver: qcserial,qmi_wwan 
           IF: wwan0 state: down mac: c2:fb:28:09:c3:46 
Drives:    Local Storage: total: 298.09 GiB used: 155.48 GiB (52.2%) 
           ID-1: /dev/sda vendor: Toshiba model: MK3276GSX size: 298.09 GiB 
Partition: ID-1: / size: 19.23 GiB used: 10.89 GiB (56.6%) fs: ext4 dev: /dev/sda6 
Sensors:   System Temperatures: cpu: 55.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 223 Uptime: 37m Memory: 3.59 GiB used: 1.00 GiB (27.9%) Shell: bash inxi: 3.0.33

The problem occurs when using antix version greater than 17.0, both 32 and 64 bit. The live USB stick is created by using the antix live usb maker from github.
Also when I create the stick from a snapshot of my running antix system installed on HDD.
It boots OK if I first create the stick from antix-17.0 ISO and then update it from e.g. 17.4 ISO, always using the usb maker program from github.

Thanks in advance for any help!

• This topic was modified 3 years ago by orcrist.

[Moderator BobC]

dacomboman, if you go to control centre and go to the maintenance tab, there is a user manager option where you can setup user id’s, assign password, and on the options tab of it you can control autologin and if a password is required. Maybe that will work for you if saved via root and home persistence. I haven’t tried it that way, myself.

What I did was to install everything, change the setups to my liking, then created an iso and made a live usb of it, which I then could insert to boot. I did find that wasn’t perfect, because it did work in a number of machines but not one of them, due to hardware differences.

I ended up creating a process to almost semi-automatically tweak an antiX install to add, remove and configure things to the way I want them from a stock install.

Attachments:

1. 

   screenshot-4.jpg
   

2. 

   screenshot_options.jpg
   

[Anonymous]

The ISO file never lands on the USB drive when using rufus.
Rufus formats the USB drive then copies content extracted from the ISO file and adds a bootloader.

Afterward, the ISO file is not needed, is never looked for.
If, for some reason, you decided to copy the ISO file (or any other file(s)) onto the liveboot pendrive, you can expect that nothing will disturb//overwrite them ~~ they’ll just take up storage space until or unless you manually delete them.

WHERE persistence data is stored

If you attach the liveboot drive to an already running system, when you use a file manager to explore its contents you would see in its toplevel directory an “antiX” subdirectory. The persistence files reside in this subdirectory.

I haven’t used “static” persistence for a while, so I’ll just describe
the persistence files associated with “dynamic” (saved on-demand and/or at shutdown) persistence

The arrowed files are squashfs files. They provide “filesystem within a file” storage.
(to learn more, websearch “squashfs” or from commandline: apropos squashfs)

rootfs {——-
homefs {——-
linuxfs
initrd.gz
vmlinuz
random-seed
initrd.gz.md5
vmlinuz.md5
linuxfs.md5
/state
/state.old

WHERE persistence data is stored

To access that same storage location from a running liveboot session (and you have booted from that device), you can (AsRoot) browse to /live/boot-dev/antiX

If you inspect /etc/fstab
(or at commandline, type: mount)
you can see the mountpoint associated with this storage location, e.g.
/dev/sdb1 on /live/boot-dev

[Member koolstofje]

When I immediately take an iso-snapshot and that usb or dvd boot to ram it fails every time.

Fatal error..
Neither aufs nor overlays is available

p=power off
r=reboot

[Member eugen-b]

Hello guys!
Why I wasn’t my post from tonight published? I posted:
I booted the ISO from disk with Grub on an AMD Jaguar machine.
I took the time to click every application in the menu and in CC.
* In the menu Internet -> Wicd settings don’t start. Since Wicd is gone it should be removed, shouldn’t it?
* In CC -> Hardware -> Alsamixer Equalizer opens a terminal window which close after a short moment. The application starts fine from the main menu.
I didn’t check all the themes and settings, but all wm sessions work.
Regards
eugen-b

[Member eugen-b]

Hi Anti and everybody else, too!
I’ve booted the ISO from disk with Grub, from superficial testing all applications open in the main menu and in Control Centre, apart from two exceptions:
– CC -> Hardware -> Alsamixer Equalizer ~ opens a terminal which then closes immediately. Alsamixer Equalizer opens fine from the main menu in a terminal window.
– Main Menu -> Applications -> Internet -> Wicd Network Manager ~ doesn’t open anything, seems obsolete hence you switched to Connman.

$ inxi -Fxxxz
System:    Host: antix1 Kernel: 4.9.170-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 
           Desktop: IceWM 1.4.3.0~pre-20181030 dm: SLiM 1.3.4 Distro: antiX-19.a1_x64-full Marielle Franco 27 April 2019 
           base: Debian GNU/Linux buster/sid 
Machine:   Type: Desktop System: ASUS product: All Series v: N/A serial: <filter> 
           Mobo: ASUSTeK model: AM1I-A v: Rev X.0x serial: <filter> UEFI: American Megatrends v: 0801 date: 03/10/2016 
CPU:       Topology: Quad Core model: AMD Athlon 5370 APU with Radeon R3 bits: 64 type: MCP arch: Jaguar rev: 1 
           L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 17600 
           Speed: 800 MHz min/max: 800/2200 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Kabini [Radeon HD 8400 / R3 Series] vendor: ASUSTeK driver: radeon 
           v: kernel bus ID: 00:01.0 chip ID: 1002:9830 
           Display: x11 server: X.Org 1.20.3 driver: ati,radeon unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD KABINI (DRM 2.49.0 4.9.170-antix.1-amd64-smp LLVM 7.0.1) v: 4.5 Mesa 18.3.4 
           direct render: Yes 

• This reply was modified 4 years ago by eugen-b.