Search Results for 'boot from iso'

I installed antiX-19.1_386-full.iso to this old laptop (see below). It seemed to work for a brief time period but, after that, no app seemed to could be launched. I could neither open a terminal nor the control-center. No other choice than “PrtSc & reisub” to reboot or press power-button to shutdown. After rebooting, same behavior. I re-installed it twice, but the result was the same. I didn’t have time for more tests, so I installed antiX-17.4.1_386-full.iso and everything is OK. I just inform you about the issue.

$ inxi -Fxz
System:
  Host: puppy Kernel: 4.9.212-antix.1-486-smp i686 bits: 32 compiler: gcc 
  v: 6.3.0 Desktop: IceWM 1.4.2 
  Distro: antiX-17.4.1_386-full Helen Keller 28 March 2019 
  base: Debian GNU/Linux 9 (stretch) 
Machine:
  Type: Laptop System: TOSHIBA product: Satellite L10 v: PSL10E-021011GE 
  serial: <filter> 
  Mobo: TOSHIBA model: Satellite L10 v: Rev 1.0 serial: <filter> 
  BIOS: TOSHIBA v: 2.40 date: 06/22/2005 
Battery:
  ID-1: BAT0 charge: N/A condition: N/A model: N/A status: N/A 
CPU:
  Topology: Single Core model: Intel Pentium M bits: 32 type: MCP 
  arch: M Dothan rev: 6 L2 cache: 2048 KiB 
  flags: sse sse2 bogomips: 2392 
  Speed: 1200 MHz min/max: 600/1700 MHz Core speed (MHz): 1: 1200 
Graphics:
  Device-1: Intel 82852/855GM Integrated Graphics 
  vendor: Toshiba America Info Systems driver: i915 v: kernel 
  bus ID: 00:02.0 
  Display: server: X.Org 1.19.2 driver: intel 
  unloaded: fbdev,modesetting,vesa resolution: 1024x768~60Hz 
  OpenGL: renderer: Mesa DRI Intel 852GM/855GM x86/MMX/SSE2 
  v: 1.3 Mesa 13.0.6 direct render: Yes 
Audio:
  Device-1: Intel 82801DB/DBL/DBM AC97 Audio 
  vendor: Toshiba America Info Systems driver: snd_intel8x0 v: kernel 
  bus ID: 00:1f.5 
  Sound Server: ALSA v: k4.9.212-antix.1-486-smp 
Network:
  Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter 
  vendor: Toshiba America Info Systems driver: 8139too v: 0.9.28 port: 3800 
  bus ID: 02:02.0 
  IF: eth1 state: unknown speed: 100 Mbps duplex: full mac: <filter> 
  Device-2: Intel PRO/Wireless 2200BG [Calexico2] Network driver: ipw2200 
  v: 1.2.2kmprq port: 3800 bus ID: 02:04.0 
  IF: eth0 state: down mac: <filter> 
Drives:
  Local Storage: total: 55.89 GiB used: 11.14 GiB (19.9%) 
  ID-1: /dev/sda vendor: Hitachi model: DK23EA-60 size: 55.89 GiB 
Partition:
  ID-1: / size: 52.76 GiB used: 11.13 GiB (21.1%) fs: ext4 dev: /dev/sda1 
  ID-2: swap-1 size: 2.00 GiB used: 12.0 MiB (0.6%) fs: swap dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 54.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 126 Uptime: 1h 54m Memory: 477.1 MiB used: 254.2 MiB (53.3%) 
  Init: SysVinit runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 
  inxi: 3.0.36

these are shots from 19 core 64-bit final (sysinit) aimed at sid repos and
built up to gdm with gnome DE.

I installed the core with no internet then rebooted.
upon reboot, I changed the repos to point to sid instead of buster. Then
setup ethernet and “apt update …. apt upgrade” I had to use “dpkg -i –force-overwrite”
on the initscripts package.
Installed dialog, xorg, gksu then gnome package.
Latest 5.5 kernel to check it out.
And some apps to have fun. …..
audacious to play cds
spacefm as file manager
palemoon browser to post this.
what fun to use same core isos and build such different systems from
my other is lightdm + mate DE

[Member gerrygk]

@ModdIt:

The installation worked because you only have to click the “Install” icon of the live system desktop. Anyway, there’s currently no chance to handle the menu bar as expected, and handling some opened app windows with the mouse is partially problematic so I have to use the arrow and tab keys instead.

Btw, md5 and sha256 checks of the iso file are positive. I also wrote a media boot twice with the same disappointing result.

Guess I’ll give it one more try, with the fewest hopes. I’ll keep you informed about the results.

[Moderator christophe]

If I understand your situation, you are making an ISO Snapshot of your main antiX system, then making a Live USB from that image, with a data partition on usb.

I just made a Live USB like you outlined, to see if I could get it to work:
1. the first time, I made the live usb, clicking on advanced options, and ticking the “Make separate data partition,” as I see you did.
2. once the live usb was made, I copied a file over to the “USB DATA” partition.
3. Then I reran live usb maker. I “pretended” that I was re-making the live usb with a new ISO Snapshot (but it was the same image).
THIS TIME, under advanced options, tick the box for “Update (only update an existing live usb” (and although I don’t know if this was necessary or not, I also checked the box for “Save the original boot directory when updating a live usb”). ONLY CHECK THOSE 2 OPTIONS. DON’T check “Make separate data partition” as you did the very first time. During operations, I saw that it took the image and copied the main files needed.
4. When Live usb maker finished, I checked — the “USB DATA” partition was still there, as well as the file I copied. Success!

I hope this answers your question. It’s kinda late here as I write this. I hope it’s coherent & applicable… 🙂

• This reply was modified 3 years, 3 months ago by christophe. Reason: clarification

confirmed antiX frugaler, since 2019

I’ve written this tutorial in response to a thread I started at https://www.antixforum.com/forums/topic/difficulty-setting-up-get-iplayer/
That thread concerned difficulties I experienced with setting up get-iplayer in antiX19.1 and they remained unsolved. Finally I was able to
crack the problem and would like to share the following, as it may be useful for other forum members.

Installing get-iplayer
This tutorial will give you the use of get_iplayer on antiX and any Debian-based distro. The command line interface (terminal) is used to download the currently available TV or radio programmes from the BBC. If you live outside the UK, you may experience difficulty with getting this to work. Key material for this tutorial was sourced and adapted from https://github.com/get-iplayer/get_iplayer/wiki/unix

Follow these steps:

1. Install dependencies:

sudo apt-get update
sudo apt-get install libwww-perl liblwp-protocol-https-perl libmojolicious-perl libxml-libxml-perl libcgi-pm-perl atomicparsley ffmpeg

Perl is also a dependency. However, it should be installed by default on your system; check using
sudo dpkg --list If, by chance it isn’t installed, then install it.

2. Download the latest get-iplayer release to the working directory:
sudo wget https://raw.githubusercontent.com/get-iplayer/get_iplayer/master/get_iplayer

3. Install the get_iplayer script
sudo install -m 755 ./get_iplayer /usr/local/bin

At this stage I like to reboot.

4. Get BBC TV or BBC radio listings
For a complete list of BBC programmes available for download, use the following commands:

For TV: get_iplayer “.*”
For Radio: get_iplayer “.*” --type=radio

You can then browse the list by scrolling up or down, using the slider button to the right of the terminal.
You can narrow your search by simply typing the name of the programme or programme-series for either radio or TV. For example, to see what’s available for the Horizon TV-series, type get_iplayer horizon.

The output from terminal shows:

$ get_iplayer horizon
get_iplayer v3.24, Copyright (C) 2008-2010 Phil Lewis
  This program comes with ABSOLUTELY NO WARRANTY; for details use --warranty.
  This is free software, and you are welcome to redistribute it under certain
  conditions; use --conditions for details.

Matches:
3221:	Horizon: 2016 - The Mystery of Dark Energy, BBC Four, b0761llv
3222:	Horizon: 2020 - Addicted to Painkillers? Britain’s Opioid Crisis, BBC Two, m000dbpf
3223:	Horizon: 2020 - Chris Packham: 7.7 Billion People and Counting, BBC Two, m000dl6q
INFO: 3 matching programmes

5. Downloading a chosen radio or TV programme
Let’s suppose, that from the Horizon example above, you wish to download the episode “Addicted to Painkillers”. You will need the programme number (3222) or a keyword from the programme’s title (e.g. painkillers).

So to download the TV programme ‘Horizon’ type the following in terminal:
(i) either use the programme number:
get_iplayer -g 3222
(ii) or, type in a keyword from the title:
get_iplayer -g painkillers
NB. The latter option will download all programme titles containing the keyword “Painkillers”.

For downloading radio programmes, again type the radio programme number or key word, e.g.
get_iplayer -g --type=radio 34067
or
get_iplayer -g --type=radio gardeners

These commands will, by default, download the highest quality of recording available. If you wish to download a lower quality, you can use additional commands with the above command-line. For details of this see https://github.com/get-iplayer/get_iplayer/wiki/modes

The advantage with get_iplayer, is that the downloaded programmes may be stored on your device indefinitely. This is an advantage over downloading programmes directly from the BBC website, where they can only be kept and played for a limited period – I think this is around 30 days.

Hoping this is useful.
Good luck and enjoy 🙂

Problems you may experience & fixes.
1. Not all programmes available are listed in terminal.
For example, only those programmes for programme numbers 7420 to 8306 are listed.
The fix for this is as follows: in the terminal toolbar (I’m using LXTerminal) go to Edit, Preferences, then Display. Go to the second line in the window, entitled Scroll-back lines: change this from 1000 (default) to say 10,000.

2. Not all programmes listed will download.
Sometimes a programme may be listed, but is no longer available. There’s nothing you can do about this.

• This topic was modified 3 years, 3 months ago by mikey777.
• This topic was modified 3 years, 3 months ago by mikey777.
• This topic was modified 3 years, 2 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 lubod]

@Moddit

Thanks for the reply. Yes, that might actually be the cause, or related in some obscure, hard to diagnose way. The BIOS in question is old, but I thought not that old, given it is 64 bit! But maybe it is? One is from circa 2006, the other 2010. I’ve been trying only Base for all versions, maybe I should try Net or Core, they are much smaller.

I haven’t installed on a HD yet (will later). I tried the 32 bit base on the same stick, it worked to save persistence on another 32 bit system. And the next boot, on one of the affected 64 bit BIOSes, also worked, but again only once! So no matter how many times it has booted OK on another system, with or without saving changes to persistent root, every boot after the first on the affected 64 bit BIOSes fails, it would seem.

Unless other steps can work around the problem, the best option is to use LiveUSB to boot once, and immediatelly install to HD. Maybe if I turn off root persistence it might work twice or more? But that makes LiveUSB less configurable and less useful.

ModdIt wrote:

Hallo Lubod, long shots but experienced maximum iso boot size problem on old box when booting from usb.
That is early BIOS Problem.
Also found some USB sticks caused issues like yours. Now only using the aluminium case intenso
Overflashing BIOS might work, but consider unlikely as first boot is consistent.

You might separate board issues from USB troubles by a hdd test install if not done already.

Restore older computers to working order.
Computers everyone else insists are obsolete and useless.

Current recordholder:
Generic Pentium III 600 Mhz with 512Mb RAM and 10Gb HD
Working on Cyrix M2 333 Mhz with 64Mb RAM and OS on IDE to SD card 4Gb

[Member ModdIt]

Hallo Lubod, long shots but experienced maximum iso boot size problem on old box when booting from usb.
That is early BIOS Problem.
Also found some USB sticks caused issues like yours. Now only using the aluminium case intenso
Overflashing BIOS might work, but consider unlikely as first boot is consistent.

You might separate board issues from USB troubles by a hdd test install if not done already.

Bizarre problem on USB boot, on Asrock K8NF6G-VSTA and ECS G41T-r3

So I’ve been trying to set up a LiveUSB of AntiX 19.1 64 bit Base, with all the software I want already installed from the repos, and the indexes and packages entirely up to date. So I can take it wherever, and as long as there is a compatible 64 bit PC that boots USB, I’m ready to go. Easy, Peazy, right? Not so much! 🙁

The following problems occur on two separate desktops, both generic whitebox using legacy BIOS and MBR partitions.
I suspected hardware failure of some rare, corner case variety, but now I don’t know what the cause is 🙁

System specs:

Motherboard:
system 1 – Asrock K8NF6G-VSTA
system 2 – ECS G41T-r3

Support page:
system 1 – https://www.asrock.com/mb/NVIDIA/K8NF6G-VSTA/#BIOS
system 2 – http://www.ecs.com.tw/ECSWebSite/Product/Product_DOWNLOAD/EN/Motherboard/G41T-R3%20-LL-V1-DO-0A-RR-/Socket%20775%20-LL-Intel-RR-

BIOS:
system 1 – 1.70 (already on latest version. Does reflashing a working BIOS with the same version make sense? Not that I’ve heard.)
system 2 – 04/07/2010 (there is only 1. Does reflashing a working BIOS with the same version make sense? Not that I’ve heard.)
Note: Both systems have AMI BIOS, in case it makes a difference.

RAM:
system 1 – 2 Gb, tested OK with Memtest
system 2 – 2 Gb, not yet tested, but has never had a problem after OS boots

Onboard USB 2 on both, tried all possible USB ports, front and back, to rule out one port/controller malfunction

Tried with 2 separate USB flash drives, and one SD card
SD card plugs into an external USB reader for one system, which is known to boot other systems, and with an internal reader on the other system

The problem is as follows: When I write an AntiX ISO (either 17.4 or 19.1 64 bit base, both verified OK by matching MD5SUM) to a known good flash drive or SD card, with Live-USB-Maker in AntiX 17.4 (32 bit, fully updated), the flash drive/SD card works, exactly once.
After I tell it to save the persistent root, which “works” with no errors, and restart or shutdown
every subsequent boot fails, usually with the error “No operating system found” press any key … blah blah
I pressed it once, and up came another error about Grub lacking configuration or some such

After it fails once, nothing other than rewriting the flash/SD with Live-USB-Maker boots, ever again.

Both systems have USB listed as a boot device in BIOS, selecting it there (after it failed the first time) still boots from hard drive, skipping USB or complains “No OS found”
Both systems list the flash drive or SD card reader when boot menu is used via F11, but it also fails that way (after it failed the first time)

I tried booting the “failed” flash on my 32 bit laptop, expecting it to halt and complain the CPU is only 32 bit
No such luck, it also said “No OS found”
Tried boot repair from 32 bit 17.4 on the “failed” flash:

MBR repair on affected device /dev/sdb failed:
Could not set up chroot environment.
Please double-check the selected location.

PBR repair on either main or second partition created by Live-USB-Maker, sdb1 or sdb2, also failed:
Could not set up chroot environment.
Please double-check the selected location.

ESP repair (even though I’m using BIOS only on all systems, but why not!)
Could not find EFI system partition (ESP) on any system disks. Please create an ESP and try again.

Grub repair on either main or second partition, sdb1 or sdb2, also failed:
Could not set up chroot environment.
Please double-check the selected location

The flash always mounts/reads with no errors in the working 32 bit 17.4, even after it is unbootable.
And all the partitions/files it claims it can’t find are exactly where they should be!

I’m thinking saving the persistent root somehow corrupts Grub. Which is why I’ve run memtest, to rule out bad RAM as the cause.

Any diagnostic info you need to narrow it down, I’ll do my best to post it. But I have more access to the
Asrock K8NF6G-VSTA, the ECS G41T-r3 is at another location, so I have to go there to test, and all tests must be done
without restarting, unless I carry 2 or more flash drives, because after 1 restart, no further tests are possible on that flash
drive until it is remastered again.

Any ideas for fixes/workarounds welcome, so long as you don’t suggest something I tried already.

Otherwise consider this a warning, that these motherboards are flaky as hell. I.E. not reliable 🙂

And now that I wrote all that, they worked several times in a row on the ASRock (about 3 or 4), both after shutdown and reboot,
and then failed in a new and exciting way! After the text about retpoline, the text gets garbled, and no other text
or graphics loads, it appears to freeze. Yet I can’t find any hardware problem with either the flash or the computer(s).

Color me confused. And frustrated.

• This topic was modified 3 years, 3 months ago by lubod. Reason: Spellings errors, clean up grammar to clarify meaning
• This topic was modified 3 years, 3 months ago by lubod. Reason: added note that ISOs were verified with MD5SUM
• This topic was modified 3 years, 3 months ago by lubod. Reason: Clean up text

Restore older computers to working order.
Computers everyone else insists are obsolete and useless.

Current recordholder:
Generic Pentium III 600 Mhz with 512Mb RAM and 10Gb HD
Working on Cyrix M2 333 Mhz with 64Mb RAM and OS on IDE to SD card 4Gb

Hello Friends.

I’ve managed to create a liveUSB using:

antiX-19.1_x64-full.iso

As I understand it, I have to press F5 upon booting the liveUSB, so that’s what I did. I then set it to “persistence-all” (I think that’s what it was).

Then I set the rootfs to 5GB and homefs to (I think) the default (around 300+MB).

However I could not get anything to stick. Not the installed applications, not the taskbar modifications, etc. If I reboot, it’s like I did nothing to it at all.

I’ve read the:

http://download.tuxfamily.org/antix/docs-antiX-19/FAQ/persistence.html

but it’s insufficient for my under-developed brain.

There are apps relating to persistence in the menu of the liveUSB but I’m not sure which to use.

By the way, when I used one of those apps that would save my things in home, it said something like, 300+MB available, 900+MB needed.

The flash drive is 8GB, if that matters.

Thank you very much.

• This topic was modified 3 years, 2 months ago by anticapitalista. Reason: solved

[Member ModdIt]

Inspired by thread I got out my Asus EEPC 1215B. Very different beast, It has never given any
sound whatsoever with my Frankenstein AntiX mashup.
@koo, Sound now, with the tiny internal speakers only nuisance value, plug in my Koss Portapro
headphones, plenty good for travel.

@Vincent17 you say I’m using a live flash drive, where kernel changes are tedious.

If your drive is big enough, run live and has full persistence, do all updates then install the new kernel
follow with remaster. System will then boot with new kernel.
One of the reasons I use Antix is remaster or create new iso is made so easy compared to other distros I
have used. Some of those make it more than tedious and extremely time consuming like hours not minutes :-(.

Hope you have sound on your device now.

[Anonymous]

Hi Moddit,
Moditt said: “Did you read about non PAE kernel for MX in old thread. Sorry should not have assumed too much, that is usually chosen
automatically by the installer.”

I burned a DVD with MX-19_386.iso on it. When I booted it on the notebook, the error says:
“WARNING: PAE disabled. User parameter ‘forcepae’ to enable at your own risk. This kernel requires the following features not present on the CPS: pae
Unable to boot – please us a kernel appropriate for your CPU”

I will try using forcepae as a boot option

Thanks again for all your suggestions
: )
G

[Anonymous]

Hi Moddit,
I am not sure if you are addressing me? Sorry. I am a newbie and trying everything people are suggesting. It seems like there might be a few other people who have diffculties with wifi in AntiX 19 as well?

Just in case you are addressing me, wifi worked fine for me in AntiX 17.
I can get wifi to work in AntiX 19 if I attach network wire, install ceni, disconnect network wire, remove connman, add the symlink for resolv.conf. Then, the wireless works. The problem then is that the symlink breaks when I reboot.

If I could retain the symlink over reboots, I would be fine.
As it is, after reboot I’d have to do the symlink again, then reconfigure my wifi in ceni again. That is a hassle. In version 17 it worked just fine.

I am happy to help solve this issue by reinstalling and testing as often as you’d like, with whatever versions of AntiX needed. This is the first time I have had a chance to really help with a distro on an issue that I an experiencing. And I think AntiX is a fabulous disto. I really want to help the devs to continue to grow it.
: )

My notebook is 32-bit and last spring 2019, I came to AntiX from Lubuntu when they announced they are dropping 32-bit. I was so happy that AntiX has non-pae since I have a Pentium M processor. I have 2GB of ram so I think that is too minimal for MX. I do not have a wireless dongle/usb to test with. And according to that command I ran, I do not have broadcom.

Again, I am happy to run any commands and provide any terminal output that may help. Or if you’d like me to do some directory comparisons, I can do that too.
I am a newbie. If you give me the CLI instructions, would debugging logs help? Just tell me the commands and let me help.

I hope this clears things up.
Happy to help
G

[Anonymous]

http://rufus.ie/

For creating an antiX liveUSB under windows, the rufus tool has worked fine when I tested.
Its default settings are fine ~~ no need to change ’em (and doing so can bring an undesirable result).
Browse to select the antiX iso file, then click “Start”. That’s it.

FYI, the “persistence” mentioned in rufus is something other than antiX persistence.
Rufus homepage describes it as experimental, toward supporting deb|ubuntu use of a liveboot persist PARTITION. (In contrast, antiX persist data is stored in a squashfs file, typically {but not necessarily} residing right within the liveboot partition.) IOW, rufus cannot setup antiX persistence in advance. It just creates a fat32 bootable pendrive. During the liveboot session, you will be provided with an opportunity to setup the antiX persistence.

Although reading this linked page in advance isn’t necessary (and doing so will probably raise questions about details you don’t need to fuss over at the outset) it highlights the extra functionality / flexibility available in antiX liveboot compared to the inflexible “persistence” mechanism provided by other linux distros
https://antixlinux.com/the-most-extensive-live-usb-on-the-planet/

[Forum Admin dolphin_oracle]

I think the booted iso and live usb need to match.

Hello,
I have an old 32-bit system that will not boot to usb.

I hear through dolphin oracle videos that the “from=usb” option on the F4 menu of the live boot will allow me to start the boot using the CD/DVD and then hand it off to the USB to finish booting (hybrid boot) (2 part system).

In order to help with testing the new versions of 32-bit AntiX, I would like to have the same CD/DVD boot every time and just update the usb with each new ISO.

Is that possible? Or do I still have to burn a new CD/DVD each time I want to test a new iso?

Loving AntiX (and dolphin’s videos!)

🙂

G