Search Results for 'boot from iso'

[Forum Admin rokytnji]

From my PM answer to your PM to me.

If your rig was mine. I’d insert a class 10 sd card in the slot. Install AntiX on that. Install Grub on MBR of SD card also. Use that cheap built 4 gig internal phison ssd as internal storage formatted as ext3 file system.

Use my ESC key or whatever. Been awhile so I don’t remember if it was F12 or F11 key for playing with bios settings. Set the SD card to boot 1st on the boot order .
That is my poor mans way of operating on a eeepc. I used to be moderator at eeepc forums before they went bust. I lost a lot of good info when that site went down.
My link I gave in your thread points to different ways I ran on eeepcs. I thin the bug was fixed where fstab and legacy grub does not mixed up any more like it did
when I wrote my how tos.

Good Luck.

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

[Member CapitanSgrakkio]

Aok, i downloaded the AntiX17 base version, now i dont find rufus like programs on the live session and if i try to download rufus or unetbooting using synaptic it ask me to put admin psw.. i don t have it.
what can i do?
afterward cli installer is inside the Antix17 base .iso??
Muchas grazias por tu tiempo perdido.

[Forum Admin SamK]

BobC wrote:

Maybe I should do a fresh install of full to see if it works initially? I would probably want IceWM anyway, but can’t run slim.

That test of the audio should be reasonably straightforward to do without installing and while bypassing slim.

The Basic approach is to use antiX in live mode.

Get the antiX-17-Full ISO
Create a bootable DVD or USB stick using the ISO
Boot using the ISO device
At the GRUB boot screen edit the Boot Options field to show
quiet 3
That avoids disabling any services and will bypass slim to produce a CLI environment.
Log-in as demo
Run alsamixer and ensure nothing is muted or set to a low volume level
Close alsamixer
Run the command
speaker-test -c2 -twav -l3

[Anonymous]

can add another browser before making the live cd?
Sure. Prior to running isosnapshot or live-usb-maker (or live-remaster, FWIW), make whatever changes you want. Those customizatons will be present in the resulting copy.

leaves no trace
If you have sufficient RAM, you can add bootline option toram and, post-boot, remove the boot device.
^—- just like Tails Linux
Mentioning this b/c LiveUSB is a much more pleasant experience than sloooooow LiveCD

[Member andfree]

Anonymous wrote:

What tool did you feed the iso to, in order to create the CD?
and
(if you can recall) Did you choose a “slow” burn speed, or default?

I used Xfburn with the default speed. The CD I created this way at the toshiba laptop could not be booted to none of the laptops. The CD I created the same way at the compaq laptop was booted successfully to both laptops. So, I came to the conclusion that the problem has to do with the burning capability of cd-drive of the toshiba laptop.

[Anonymous]

So I’ve narrowed the problem down to the Linux kernel; all the Linux distros that have run well on the IBM run kernels from Linux 3.xx.xx. I installed antiX-17_386.iso to a USB drive, booted it on my main computer, and installed the following packages via Synaptic:

*linux-headers-3.7.10-antix.5-486-smp:i386
*linux-image-3.7.10-antix.5-486-smp:i386

They installed without any errors. I then opened the terminal and ran the following command:

sudo update-grub

The command finished without errors. I powered off the machine, plugged the USB drive into the IBM, and booted from it. When I reached the GRUB menu, I chose “Advanced Options for antiX” and selected kernel 3.7.10. The computer returned the following errors:

(See attatched image)

I’m not sure if I missed a step, or if there’s some configuration file I need to edit (I’m not a coder, so editing files with root privileges makes me a bit nervous). Any ideas?

[Anonymous]

And one more question

Your “one more question” is inspiration toward creating an available antiX kernels FAQ

———————————————
I’m pasting here my WIP draft, inviting corrections and proposed additions
(will later split or repost this into a separate “Documentation” topic)
———————————————

DRAFT : available antiX kernels FAQ

Q. What is special about, or different from, antiX kernels? (compared to linux mainline kernel)
A. (tentative) the antiX kernel includes many extra kernel modules, toward supporting a broader range of hardware devices / firmware (especially older devices, older display adapters/chips)
A. Debian-issued kernels (and not antiX) ship with selinux enabled
A.
A. The wording of this question is probably too broad ~~ begs multiple related answers, some of which might be suited to • bullet-point list format

^——– can we see a list?
^——– are the kernel modules (drivers) in fact “compiled in”, or are just packed into the iso?
^——– /boot/kernelconfig (shows copious detail) need link(s) to suggested refs which explain the nitty-gritty details

.
Q. Whatall kernels can I install? Like, can I install a Liquorix kernel for my antiX system?
A. (tentative) some non-antiX kernels will be unable to support liveboot persistence/remastering features…
(and vice versa ~~ antiX tools cannot setup the “casper” etc persistence used by other distros)
-=-
(?mention the potential absence of an overlayfs/aufs support in alternatively-sourced 3.xx series kernels?)

.
Q. Where can I find a list of available (“currently supported”) antiX kernels?
A. (skidoo’s tentative answer ~~ corrections invited)
http://antixlinux.com/stretch/pool/main/l/ and http://antixlinux.com/stretch/pool/main/l/linux-upstream/
^—– also displayed within synaptic package manager ( availability depends on which repositories are currently selected)

.
Q. What benefit(s) to be gained from installing a newer kernel?
Q. Are there any potential “downsides” to installing a newer kernel?
A.
A. Ultimately, it’s YMMV “try it — on your system, your hardware — and find out”
A. anectodal, machine/model -specific “answers” don’t belong inside the FAQ, are (already, on a an ongoing basis) available
A. ? limit the scope of Q/A here to addressing “…any of the available, currently supported, antiX kernels” ?

.
Q. Howabout benefits/downsides of DOWNgrading the installed kernel?
A.
^—- ? all else aside, how significantly does size does affect (liveboot toram, time until boot completion, …)
v4.10 ~~ 31MB
v4.14 ~~ 39MB
v3.7.10 ~~ 21MB

.
Q. Whaddabout kernel “headers”? Do I need those? When do I need those? How do I know whether I need those?
A.
A.
A.
^—– always needed when proprietary graphics driver is present, yes?

.
Q. So… not all kernels in antiX repo are “supported”, or what?
A.
betatesters (release announcements)…. awaiting a well-tested kernel has delayed distro releases
^——- exist in a separate “testing” repo? YES http://antixlinux.com/testing/pool/main/l/ and http://antixlinux.com/testing/pool/main/l/linux-upstream/
( these are NOT redundant copies, they are alternate, interim versions (probably not widely tested)

.
Q. Instead of downloading a ready-made kernel, how can I compile a kernel?
A. start here: https://mxlinux.org/wiki/system/compiling-and-installing-new-kernel

.
Questions which are beyond the scope of this FAQ:
• What is the kernel, exactly?
• What means LTS (long-term-support) kernel?
• What antiX-issued kernels are condiserd LTS kernels? (belongs in an addendum, or link to release anouncement(s), or…)

So, I’ve been experimenting with Antix-17 on an old laptop, and I think it will be perfect for my old IBM NetVista 225732U. Notably, this machine has:

*1300/100 Mhz Celeron Processor
*256MB RAM
*Intel(R) 8xx Chipset Video BI

I burned the 32-bit antiX-17_386-base.iso image to a CD and booted up the machine. Immediately after loading the kernel, I am hit with this error:

Undefined video mode number: 317
Press <ENTER> to see video modes available, <SPACE> to continue, or wait 30 sec

After multiple reboots I’ve tried all three; none of them seem to make a difference. The machine eventually begins to load antiX, scrolling through colorful lines of text, apparently without incident. However, when it reaches the point where every other machine I’ve tested it on loads the graphical desktop, the IBM freezes on a black screen. I have noticed that the IBM reacts similarly to almost any Debian/Ubuntu-based distro. It boots Q4OS and Slacko Puppy Linux without difficulty. It also used to boot Lucid Puppy, but booting Tahrpup results in the same screen blanking as soon as the machine tries to load the graphical environment.
Is there anything I can do to load antiX properly. Could it be that this machine is just too far behind the times? Any, and I mean any feedback would be appreciated.

It’s not important for me, I’ll try with an older base version, but I thought I should refer it. I downloaded antiX-17_386-base.iso, checked it with md5sum and burned it to a CD. I tried to boot, but:

ISOLINUX 6.03 6.03* ETCD Copyright (C) 1994-2010 H. Peter Anvin et al
Failed to load ldlinux.c32
Boot failed: press a key to retry...

I retried it with the same result.

$ inxi -Fxz
System:    Host: antix1 Kernel: 4.0.5-antix.3-486-smp i686 bits: 32 gcc: 4.9.3
           Desktop: IceWM 1.3.8
           Distro: antiX-15.1_386-full Killah P 18 February 2016
Machine:   Device: laptop System: TOSHIBA product: Satellite 2450 v: PS245E-03TE0-GK serial: N/A
           Mobo: TOSHIBA model: Portable PC v: Version A0 serial: N/A
           BIOS: TOSHIBA v: Version 1.30 date: 03/20/2003
CPU:       Single core Intel Pentium 4 (-UP-) 
           arch: Netburst Willamette rev.7 cache: 512 KB
           flags: (pae sse sse2) bmips: 5586 speed: 2793 MHz (max)
Graphics:  Card: NVIDIA NV17M [GeForce4 420 Go] bus-ID: 01:00.0
           Display Server: X.Org 1.16.4
           drivers: nouveau (unloaded: modesetting,fbdev,vesa)
           Resolution: 1024x768@60.00hz
           OpenGL: renderer: Mesa DRI nv17 x86/MMX/SSE2
           version: 1.2 Mesa 10.3.2 Direct Render: Yes
Audio:     Card Intel 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller
           driver: snd_intel8x0 ports: be00 bdc0 bus-ID: 00:1f.5
           Sound: Advanced Linux Sound Architecture v: k4.0.5-antix.3-486-smp
Network:   Card: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
           driver: 8139too v: 0.9.28 port: ce00 bus-ID: 02:09.0
           IF: eth0 state: unknown speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 100.0GB (63.3% used)
           ID-1: /dev/sda model: TOSHIBA_MK1032GA size: 100.0GB
Partition: ID-1: / size: 90G used: 57G (67%) fs: ext4 dev: /dev/sda1
           ID-2: swap-1 size: 2.17GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
           ID-3: swap-2 size: 0.24GB used: 0.00GB (0%)
           fs: swap dev: /dev/zram0
Sensors:   System Temperatures: cpu: 47.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 98 Uptime: 30 min Memory: 237.4/1005.2MB
           Init: SysVinit runlevel: 5 Gcc sys: 4.9.2
           Client: Shell (bash 4.3.301) inxi: 2.3.53 

• This topic was modified 5 years, 3 months ago by rokytnji.

[Forum Admin SamK]

andfree wrote:

…also noticed that the size of the zram0 partition changes slightly every time I reboot.

That is expected and normal.

The size of the zram swapspace depends on the amount of available RAM at the time the swapspace is created. Because zram swapspace exits only in volatile RAM i.e. while the system is powered up, the zram swapspace is recreated at every boot-up. The zram swapspace creation occurs after other software has begun, or is in the process of loading. During boot-up small variations in the working of the hardware combined with all the software that is loaded in the boot process, means the amount of RAM available for zram may slightly differ from boot-to-boot. This can be seen as a small difference in the size of the zram swapspace.

andfree wrote:

I have already reduced the shared RAM to the lowest value, switched off CUPS, WICD & Bluetooth, I use the min-icewm desktop, I use Palemoon for common browsing, I have set conky off. After all, I have seen a significant improvement in speed & performance. Now, I’m testing with the older kernel & swap issues, but I can’t say yet if these two have improved the performance of the system any more.

It might be the previous tuning you have done has hit the sweet spot for you. Assessing zram in isolation is not the most helpful or revealing way to tweak system performance. It is only one tool is a range of measures you have already tried and seen the benefit of using. As you are discovering, it is the right combination of tweak measures, specific to you and your systems, that produce the worthwhile results.

andfree wrote:

Many thanks for your help.

That is most welcome. You also should share the credit. The quality of your research, testing, and reporting, is a good model for others to emulate.

Off Topic
Some thoughts to close this discussion. You have already begun to discover that breaking free of conventional, restrictive ideas can pay large dividends.

Consider using more lightweight apps and slightly modifying the way you perform your daily tasks. Together they can produce further worthwhile improvements in the performance of your systems. You have already mentioned using the Palemoon web browser. If you use it to watch Youtube videos, try using Streamlight instead. You will find it uses a tiny amount of CPU and RAM compared to any heavyweight web browser.

Streamlight is just one example of a different way of achieving a desired goal (e.g. viewing a streamed video or downloading it). There are plenty of other examples in antiX that perform well while using very few CPU and RAM resources.

The written user guide is available in the antiX FAQ:
Online
http://download.tuxfamily.org/antix/docs-antiX-17/FAQ/streamlight.html
Locally installed
See the Help section of the antiX main menu

The video is available on Youtube
https://www.youtube.com/watch?v=2M5B5aXBDwk

[Forum Admin SamK]

So with my version of the zram script installed you have working zram swapspaces on both the P4 and Celeron when you start the swapspaces manually.

Now you just need to confirm the zram swapspace is automatically available after a reboot i.e. without starting it manually.

Explanation:
The default action of zram is to set up a swapspace per CPU e.g. 4 swapspaces for a quad core, 1 swapspace for a single core, etc.

The version of the zram script shipped in the ISO does not hounour the zram default action. It sets up 1 fewer swapspaces than the number of CPUs i.e. 3 for a quad core. That is a problem when the system has only a single CPU.

My version of the zram script honours the zram default action. It sets up 1 swapspace per CPU for single and multiple CPU systems e.g. 4 swapspaces for a quad core, 1 swapspace for a single core, etc.

[Anonymous]

v— paraphrased instructions found in 2012 oldforums topic

To have zRam start at bootup:

• cp /usr/local/bin/zram /etc/init.d/zram
• ensure owner and group are root:root
• ensure permissions are rwxr-xr-x
• run the command update-rc.d zram defaults
• reboot the system

To check that it has loaded, look at the size of the swap reported by conky (if you use conky). Alternatively, a command such as blkid -o list should list a /dev/zram0 mounted as swap

[Anonymous]

how can I edit files from antiX (presumably) iso? Or, rather: how can I save edited files as iso?

It is much easier to just BOOT the iso, then from within the running session…
edit any files in the live filesystem and/or add/purge packages… and run /usr/bin/isosnapshot

.
.
.
======= ignore what follows (or recognize it as an earlier, rambling, draft =========

Top search result, when I queried “virtualbox iso Fatal Could not read from Boot Medium! System Halted!”
was a video. Check out at 0:26 in the video

Please read about antiX remastering. Manually unpacking/editing/repacking the antiX iso is probably unnecessary nowadays.

v—- hyperlink
antiX docs :: Remastering

The primary purpose of live remastering is to make it as safe, easy, and convenient as possible for users to make their own customized version of antiX. The idea is that you use a LiveUSB or a LiveHD (a frugal install to a hard drive partition) as the development and testing environment. Add or subtract packages and then when you are ready to remaster, use use a simple remaster script or GUI to do the remaster and then reboot. If something goes horribly wrong, simply reboot again with the rollback option and you will boot into the previous environment.

edit:
antiX snapshot (aka iso-snapshot) may be the more appropriate tool for your immediate goal.

The primary purpose of Snapshot is to make it as safe, easy, and convenient as possible for users to make a live bootable iso of their own installed version of antiX. The idea is that you when you are ready to take a snapshot for whatever reason, just use use the iso-snapshot application and once it is finished, you will have an iso file ready for booting.

Menu → Applications → System Tools → iso-snapshot

Hopefully others will chime in to post additional doc/reference links.
I found video: “antixsnapshot – Turn your customized install into an installable ISO!”
and antiX/MX wiki :: Save system to ISO (Snapshot)

another video: “Make a snapshot of an installed system”
(intended for MX Linux audience, demoed on MX… but same tool is available in antiX)

an excerpt from antixlinux.com homepage link, titled “ReadMore”

Live Remaster and snapshot
The live remaster feature provides a slightly more permanent way of saving changes to a live-usb. It creates a new compressed linuxfs file system which contains all of your changes. Typically, someone would use root persistence to store changes on every boot and then after a big upgrade, use live remaster to compress all of those changes into the linuxfs file, letting root persistence start over with a clean slate.

You can now 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.

The snapshot tool works like remaster but it creates an iso file. Unlike remaster, it can also be run on an installed system. Using the live remaster tool is sort of like combining snapshot and live-usb-maker in one step without having to bother creating an intermediary iso file.

Hi guys,

I’m using an AntiX live in a VirtualBox. I have downloaded it from an official page (antiX-17_386-full), mount it in a VirtualBox and everything works but I want to customize it for myself (screen resolution, language etc.). So I’ve unpacked all files, edited what I needed and save everything as *.iso again. After mounting my new custom iso in virtualbox I obtained an error:

>Fatal Could not read from Boot Medium! System Halted!

My first thought: Do I edit wrong files? Or maybe my editor (notepad) change some files encoding? MD5 checksums has been changed?
There can be really many reasons so I just unpacked original iso one more time, and save these unpacked files as iso again (without any changes!). After mounting this “new-but-not-edited” iso, error “Fatal Could not read from Boot Medium! System Halted!” still appear.

So, my question is: how can I edit files from iso? Or, rather: how can I save edited files as iso?

Thanks for any help and tips!

[Member ckhung]

A follow-up note:

I took those same steps in the previous post directly after booting from the installation live cdrom (e.g. before installing to harddisk). Now fcitx did NOT work. The mode-switching key ctrl-space has no effect. When trying to use GUI (right click) to change input mode, there is only one option (keyboard-en(us)) to choose from instead of three. For comparison, attached image is what it looks like when fcitx is working in a normal, installed environment, where there are 3 input modes (keyboard-en(us), chewing, boshiamy) available.

I would appreciate very much if someone familiar with the antix system (and not necessarily with eastern languages or input methods) could please try as far as figuring out how to make the other 2 methods appear in the GUI. Either this may help expose an antix bug that may also have been affecting other input methods, or it may give some good info for reporting bug to fcitx, which is currently the only input method working in antix.

• This reply was modified 5 years, 5 months ago by ckhung. Reason: should be "keyboard-en(us)"

Attachments:

1. 

   1.png