AntiX 17.2 64-bit install – Help?

[Member MacRavn]

Just getting started with AntiX. First used on a 13-year old Toshiba as a Live USB (this machine has no HDD – yet still is fully functional with AntiX)

My current project is to us it on:
ASUS E203MA: 4GB/32GBsNMC – basically configured with Win 10-Smode but this will be dumped as soon as I decide I like the machine.
(Specs per inxi attached [inxi run by Xubuntu))

Process: Create USB from the ISO (Rufus or PenDriveLinux Utility). Boot from USB on the ASUS:
The options presented in the initial boot screen do NOT include many items that DO appear in the 32 Bit version I have been using on the old Toshiba.
In Particular: The “Boot Options” text Box, any of the F# menu options.
My options are
antiX 17.2 full
antiX 17.2 full Customie Book (text Menus)
Advanced: Failsafe, Boot Chart, etc.
(These same options appear regardless of if it is FULL, BASE or CORE, and regardless of the states of FastBoot and SecureBoot)

From what I could tell, UEFI makes the “Pop-Up System” available.
I used the text options to set various modes, and successful made it through to the point were one must log in as Root and run cli-installer:
My original intention was to make the USB that I was booting from, be the Live USB. I am not sure how I should have answered the repartitions questions. I chose NO, and chose the sdb for the current USB Drive, and “no” for “Separate Home Partition.”. Subsequently, came an endless list of “cp:error writing… no space on disk”.

I got the same results with the same process but targeting a second, empty USB. This does not surprise me as I do not see how the second USB would end up bootable.

Ideally I would like to make the ISO USB become the Live USB, at least the first one, from which I could make others, and most likely make a proper install of this, likely as the primary OS for this little machine.

What am I doing wrong?

Thanks

• This topic was modified 4 years, 6 months ago by MacRavn.

[Member delix02]

Helpful

Up

0

::

in bothe cases the solution is to answer the repartition questin with YES and thus get the disk/stick reformatted.

The NO answer works only with an empty disk already formatted with a Linux file system.

[Member fatmac]

Helpful

Up

0

::

When you download, you get an .iso image that can be written to CD/DVD or imaged to a USB pendrive.
(Some Windows imaging software doesn’t work properly, so you may have to try a couple.)

When you have imaged your pendrive, you will now have a ‘live’ Linux system, from which you install to other drives.
You can create a ‘persistent’ pendrive system, but I’d start with just installing to another pendrive or disk.

Linux (& BSD) since 1999

[Forum Admin rokytnji]

Helpful

Up

0

::

o run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

xubuntu@xubuntu:~$ inxi -F
System:    Host: xubuntu Kernel: 4.15.0-29-generic x86_64 bits: 64
           Desktop: Xfce 4.12.3 Distro: Ubuntu 18.04.1 LTS
Machine:   Device: laptop System: ASUSTeK product: VivoBook 12_ASUS Laptop E203MAS_E203MA v: 1.0 serial: N/A
           Mobo: ASUSTeK model: E203MAS v: 1.0 serial: N/A
           UEFI: American Megatrends v: E203MAS.302 date: 06/26/2018
Battery    BAT0: charge: 32.5 Wh 95.0% condition: 34.2/38.0 Wh (90%)
CPU:       Dual core Intel Celeron N4000 (-MCP-) cache: 4096 KB
           clock speeds: max: 2600 MHz 1: 1251 MHz 2: 1202 MHz
Graphics:  Card: Intel Device 3185
           Display Server: x11 (X.Org 1.19.6 )
           drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1366x768@60.01hz
           OpenGL: renderer: Mesa DRI Intel UHD Graphics 600 (Geminilake 2x6)
           version: 4.5 Mesa 18.0.5
Audio:     Card Intel Device 3198 driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.15.0-29-generic
Network:   Card: Intel Device 31dc driver: iwlwifi
           IF: wlo1 state: up speed: N/A duplex: N/A mac: 7c:2a:31:ef:ce:37
Drives:    HDD Total Size: 15.5GB (36.9% used)
           ID-1: /dev/mmcblk0 model: N/A size: 31.3GB
           ID-2: USB /dev/sda model: USB_3.0_FD size: 15.5GB
Partition: ID-1: / size: 3.9G used: 312M (9%) fs: overlay dev: N/A
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 36.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 168 Uptime: 5 min Memory: 467.3/3768.5MB
           Client: Shell (bash) inxi: 2.3.56 
xubuntu@xubuntu:~$ 

Just a thought. Saved settings might be on that usb drive you made. Some usb settings are saved even on a non persisent made live usb.
I’d wipe the usb, start over, and just use a virgin live usb session not booted on any other gear.

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

[Forum Admin dolphin_oracle]

Helpful

Up

0

::

I’m confused.

If you are using the full iso, why are you using the cli-installer and/or logging in as root?

[Member MacRavn]

Helpful

Up

0

::

dolphin_oracle wrote:

I’m confused.

If you are using the full iso, why are you using the cli-installer and/or logging in as root?

Good question… I thought this was on account of the UEFI preventing the menu-driven approach according to this: Page

In any event, all paths I tried lead to this instruction to log in a root and run cli-installer.

Anyways, I will follow delix02 advice and see how that goes. Sure appreciate all y’all rushing to the rescue

[Forum Admin anticapitalista]

Helpful

Up

0

::

Are you running core or net versions? – Never mind I see it is full version.

• This reply was modified 4 years, 6 months ago by anticapitalista.

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

antiX with runit - leaner and meaner.

[Member MacRavn]

Helpful

Up

0

::

Back to the Drawing board:

I was unable to find clear documentation about how the partitions should be created, 1 let the live-usb-creator take a stab at this to see what it created:
dev/sdb1 (bootable) 14.4G 83Linus
dev/sdb2 () 50M ef EFI (FAT 12/16/32)

In the hopes this might work, I got rid of sbd1 and recreated a blank version of the same thing and tried to let cli-installer install there using the “choose a root partition” = sdb1. Result: all cp: errorwriting no space on device.

What is not clear to me is: on the 32bit version, it did not need a second usb to install to, the menu-driven installer did its thing and plopped me into my chosen GUI and off we go.

What is clear to me: I am doing something way off base here. I am relatively new to Linux filesystems (you guessed), so I am also a little unclear on what info to post.

[Member fatmac]

Helpful

Up

0

::

I don’t quite remember what I did in the installer, but I’ve just installed 17.2 to a new computer, so presumably EFI, & what I did was to uncheck a box about Windows 10 secure boot in the (equivalent of) BIOS, then I was able to install with the partitioning that I wanted.

Root partition about 7GB, swap partition 4GB (same amount as ram), the rest went to my /home partition.

Hopefully this will give you an idea of how to set up your system.

Linux (& BSD) since 1999

[Member MacRavn]

Helpful

Up

0

::

It is encouraging to know that an install to the primary disk worked, eventually I will do that.

To tune the scope of this thread and my question: Can anyone confirm or deny: Is it in fact possible to run a single complete LIVE USB version in the 64BIT version?

To compare:

32BIT Full ISO to USB (old 2007 Toshiba): presents “Boot Options” textbox with F-menus, etc. Once options chosen, install proceeds to create a self-contained complete system on same USB, with full DE, running etc.

64BIT Full ISO to USB (2018 ASUS machine, UEFI, Secure Boot OFF (or on, no diff)): Presents “Install with Text Menus”. First part of the process allows setting such options through text chain. after this comes “Login as Root and run cli-installer”, with a guided process to install on some other media.

Primary question: Is this the only option? is there not one where it creates a system on the some USB like the 32 Bit version did?

(I’ll leave out the experiences attempting to install it over to a second USB for later – in short, some succeeded in “installing”, but none of these yielded a recoginzable bootable USB. More on that later if needed)

[Member fatmac]

Helpful

Up

0

::

I think you are looking for Persistence(?). I would imagine it would work on an EFI stick, but have no experience, as this was my first computer with it, & I’m still not sure how I would get back into the (equivalent of) BIOS on it. 🙂

I bought several MBR computers when this UEFI came out so that I wouldn’t have to bother with it. 😉
But times have caught up to me…….

Linux (& BSD) since 1999

[Moderator caprea]

Helpful

Up

0

::

If you created a usb-stick with the antix-iso (64bit or 32bit doesn’t matter) and rufus , you created a live-usb-stick.(there is no need for another usb-stick or to modify the stick or something like that)
It should boot you to a desktop.
That worked flawlessly with your toshiba laptop.

The asus-laptop seems to have some problems, it’s a uefi-boot and the boot-menu has a different appearance, but anyway the stick should boot into a working desktop.
you should normally not get to the point were one must log in as Root and run the cli-installer

So the question is, why it doesn’t do so ?
To begin from the start, did you check the md5sum for the downloaded iso ?

You maybe have to play a little more with the boot-options available in the text-based settings.
Which options did you try ?
The problems are maybe related to the relatively modern hardware.

[Member MacRavn]

Helpful

Up

0

::

Thank you all for your suggestions. To finish the story: MD5’s have always checked out OK. I did several attempts, each using a different option from the main list, each lead to the same result – USB operation as a Console/Terminal, but no GUI.

I have ended this particular quest for the time being in favor of other projects:

On the 64-bit ASUS, I ran MX-Linux-64, which has essentially the same Boot process. I used “default” for the main option, and it gave me a live USB first time. Then a very simple install to HDD, and once I added the latest iwlwifi firmware, I had a working machine. So far, working very well indeed as a desktop equipped environment.

AntiX 32 bit Core: Have been using this on the Old Toshiba. I do not need GUI for what I am doing on that.

So thanks for the help.

[Author]

Posts