Trending December 2023 # How To Install Arch Linux # Suggested January 2024 # Top 19 Popular

You are reading the article How To Install Arch Linux updated in December 2023 on the website Moimoishop.com. We hope that the information we have shared is helpful to you. If you find the content interesting and meaningful, please share it with your friends and continue to follow and support us for the latest updates. Suggested January 2024 How To Install Arch Linux

Arch Linux, often a barometer of a user’s skill, is one of the most difficult distros to install while still maintaining a level of practicality. With its extremely well-documented Wiki, excellent package manager, and the frontiersman “build it yourself” allure it brings with it, Arch Linux may very well be worth it for you. If you want to attempt to install Arch Linux, this guide can help you to get started!

What Is Arch Linux?

If you ever wanted to custom-build a distro with components you choose and make it as lightweight as possible without losing the features you love, this distro is the one for you.

It comes with a base installation that comes with the bare basics for it to run. You can install your favorite desktop environment and the applications you need.

Arch Linux is also a rolling release distribution, which means you just need to install it once, and it will always update itself to the latest version.

The only real downside to Arch is how unstable it can be due to the “bleeding edge” nature of its packages. Essentially, when a developer releases a new version of their app, Arch will have it within a few hours. In the case of AUR packages, you might even get an alpha release that is still being tested.

Before We Begin

Before you can install Arch Linux, you need to first download the ISO file and burn it to a USB drive or DVD.

Use a tool like balenaEtcher to write to a bootable USB thumb drive from the image you downloaded.

Before booting with the drive, make sure you have configured your motherboard to boot from USB. This can be configured from the BIOS screen.

Installing Arch Linux

Insert the USB drive into your PC and boot it up. You will be greeted with a command prompt.

1. Configure the Disk

Type the following into your prompt:

fdisk

-l

This will show you a list of your drives, partitions inside of them, and the names given to them by Linux. If you have multiple drives, have a look at the size to learn which one you want to install Arch on.

In the case of this image, the installation drive is labeled “/dev/vda,” and it has no partitions yet. The “vda” label only happens when you’re installing in a virtualized environment. When you install any distro of Linux on your hardware, your first drive will be labeled “/dev/sda” – with very few exceptions. To avoid confusion, we’ll use the latter as a convention from now on.

Type the following command to create partitions:

fdisk

Note: if your installation drive isn’t labeled “/dev/sda,” remember to write in the proper name of the drive, or you may risk erasing something you want to keep.

Once you’re in the fdisk utility, type n to create a new partition.

Type p to create a primary partition. It will ask you for a partition number. Don’t worry about that and just press Enter.

We’re making an EFI partition to store your boot record first. To do that, leave the “First sector” part alone and press Enter, then when the disk utility asks you for the last sector, type “+512M” (without the quotes).

This creates a partition that is 512 MB in size and begins on the first available sector.

Type t to change the partition type, then type EF to ensure that your partition is properly recognized as the one that the bootloader will reside in.

Type n again to create a new partition. This time, we are creating a swap partition.

Set it up to be about half the size of the amount of RAM you have installed in your system and set its type code to “82.”

Type n again to create a new partition. This time, we are creating a system partition.

To fill out the rest of your drive with the system partition (i.e., what you want to install Arch Linux on), don’t specify a size for it or use a type code. Fdisk will just allocate the rest of your space for your operating system.

Type w when you’re finished to tell fdisk to write all your changes.

Your disk list (write fdisk -l again to see it) should now look something like this:

If it doesn’t look like this, just delete the partitions you’ve created by opening your device with fdisk again (fdisk /dev/sda) and using d to delete your partitions one by one. Once you’re done, start this section again and carefully read and follow the instructions.

Assuming that you made all three partitions suggested here, and your disk is labeled “/dev/sda,” you need to format each to its proper file system.

Your boot partition needs to be formatted to FAT-32:

Make sure that the swap partition is properly formatted:

Give your system partition an ext4 file system:

Tip: on a regular Linux distribution that is not Arch, you can easily format a partition with GParted that is included in the Installer.

Before you can do anything with your partitions, you have to mount them so that Linux can make sense of how to navigate them.

The commands, in the order I am outlining here, will mount your system drive, mount your boot drive into a subfolder you create in your system drive, then activate the swap partition:

mount

mkdir

-p

mount

Before we get any further into the installation, Arch Linux needs to download the “bootstrapping” applications from the official repositories to make sure all of the packages are up to date. For this, we need to check whether Arch can connect to the Internet:

ping

-c

To connect to a Wi-Fi network, type iwctl. This opens the iNet Wireless Daemon, an extremely simple service that allows you to configure your wireless adapter.

Grab the list of networks with:

Once you’ve found the network you want to connect to, complete the connection with:

'[network]'

Replace [network] with the network name you’re attempting to connect to. If the network name has a space in it, use single quotes around it or this may not work properly.

When you’re done, type exit

Chroot is a command that tells Linux to change the root directory and redirect its running processes. It will detach you from the installation media and start using your newly mounted partitions as a reference point to modify things.

Type the following command to bootstrap Arch:

nano

sudo

If you know the names of any other applications you’d like to have in your distro to assist you in installing it, append them to the command. We are using nano to edit text and sudo to configure an administrative structure into your Arch installation so that it functions just like any other distro you’re accustomed to.

Generate the file system table:

Chroot into your system:

At this point, your system has a kernel, some default system applications, and default configurations for them. To ensure that we get things running properly, we’ll have to change some of these configurations and add a few other applications.

Access your locale generation file:

nano

If you want American English, for example, you need to remove the hash in front of “en_US.UTF-8”.

Generate the locale and set the language environmental variable:

export

LANG

Create a name for your computer. Replace [hostname] with what you want to call your system:

Open the hosts file:

nano

and add the following content:

[

hostname

]

Set the root password for your system:

passwd

Add a user for yourself with the “wheel” group so that you can use sudo:

-G

-m

[

]

Set the user’s password:

passwd

[

]

Open your sudo configuration with nano:

EDITOR

nano

Remove the hash (“#”) symbol from the area that contains the content:

ALL

(

)

Grab the GRUB bootloader and EFI Boot Manager packages:

-S

Install and configure GRUB:

--target

--bootloader-id

--efi-directory

-o

-S

Add and enable a networking service:

-S

enable

This makes it possible for you to access the Internet after you finish the installation.

Set your timezone. You will need to know the Region-City combination your time zone specifically belongs to:

-sf

If you live in Bucharest, for example, the command would be:

-sf

If you’re unsure of your time zone, use:

to list time zone regions, rhen use the ls command again within the full path of the region folder (e.g., /usr/share/zoneinfo/America) to see a list of available cities.

You have finished installing the base of Arch Linux! Boot into your newly-installed system:

exit

When you enter your system for the first time, you’ll be greeted by a terminal login prompt. This may look underwhelming, but we’re about to make this into a full-fledged desktop environment. You may want to learn more about Pacman before you continue.

We are starting by setting NTP up so that the clock has a way to synchronize over the network:

sudo

true

Edit your pacman configuration:

sudo

nano

Install a graphical server. We are using X11 to make things simple, as Wayland still has some compatibility issues with systems running Nvidia cards.

sudo

-S

Install a desktop environment. There are plenty of desktop environments available, and you can install your preferred one here. Some of the common ones are GNOME (gnome), KDE Plasma (plasma-meta and kde-applications-meta), and Cinnamon (install cinnamon, xed, xviewer, xreader, and pix). If you use Intel graphics hardware, remove xf64-video-intel to avoid random freezing events), XFCE (xfce4), etc.

Install the display manager.

Note: Arch Linux’s packages for the KDE desktop environment already come with its own “sddm” display manager, so you don’t have to install it.

sudo

-S

Of course, it goes without saying that If there’s another display manager you personally favor, feel free to install that instead.

Enable gdm:

Once you reboot your system, you should be greeted by a full-fledged graphical login screen that will take you to your desktop!

Good to know: if this tutorial looks complicated to you, then you should check out these Arch-based Linux distributions that are easy to install and use.

Yes, it is up to you to decide if you want a desktop environment or window manager. That is the beauty of Arch Linux. The Arch Wiki lists a variety of window managers, including famous ones, like i3, bspwm, dwm, awesome, spectrum, Qtile, and xmonad.

Wi-Fi doesn’t necessarily “stick” across reboots unless something is controlling the network manager service for you. Since you rebooted to a TTY prompt instead of a full desktop environment, you’re going to have to take manual control of your networking service. You may have also noticed that iwctl is not available, but that’s fine, as you’ll now be using nmcli instead to connect to a Wi-Fi network. Use nmcli device wifi connect password '[your password]' name '[network name]', and in one single line, you’ll get yourself back online!

The first and most common repository for finding stuff you may not find in the official Arch Linux repository is the AUR. Once you get your hands on a helper application, you’ll be able to browse the AUR with just as much ease as the official repository!

Miguel Leiva-Gomez

Miguel has been a business growth and technology expert for more than a decade and has written software for even longer. From his little castle in Romania, he presents cold and analytical perspectives to things that affect the tech world.

Subscribe to our newsletter!

Our latest tutorials delivered straight to your inbox

By signing up, you agree to our Privacy Policy and European users agree to the data transfer policy. We will not share your data and you can unsubscribe at any time.

You're reading How To Install Arch Linux

How To Install Powershell 7 On Linux

If you use PowerShell on Windows 10, but you also require to use a Linux distribution (such as Ubuntu) for work, you can now install the Microsoft command-line shell and scripting language in the most popular flavors of the open source operating system.

At the time of this writing, you can install PowerShell 7, which is built on .NET Core 3.1, but it’s backward compatible with the modules for older releases.

In this guide, you’ll learn the steps to install PowerShell 7 on Ubuntu using graphical user interface (GUI) or command line. (These are the steps to install the tool on Windows 10.)

Search for PowerShell.

Select the powershell option.

Once you complete the steps, you can access the app using the pwsh on the Linux Terminal.

To install PowerShell on Linux using GUI installer, use these steps:

Open PowerShell download page on GitHub.

Quick note: PowerShell is also available for other flavors of Linux, including CentOS, Alpine, Red Hat, and Debian.

Save the file on your device.

Once you complete the steps, PowerShell will install, and you can launch it from the Terminal using the pwsh command.

If you run into dependencies problems, then use the steps below to install PowerShell using command lines.

To update the PowerShell app on Linux, use these steps:

Open Terminal.

Type the following command to install PowerShell and press Enter:

After you complete the steps, you can start the Microsoft scripting tool using the pwsh command in the Terminal.

If you want to uninstall the tool, from the Terminal, type the sudo snap remove powershell command.

To install PowerShell on Linux using Package Repository, use these steps:

Open Terminal.

Type the following command to download the Microsoft repository GPG keys and press Enter:

Type the following command to register the Microsoft repository GPG keys and press Enter:

Type the following command to update the list of products and press Enter:

Type the following command to enable the “universe” repositories and press Enter:

Type the following command to install PowerShell on Linux and press Enter:

After you complete the steps, PowerShell will install on Ubuntu 18.04, and you can start it using the pwsh command.

When you no longer need the command line tool, use the sudo apt-get remove powershell command in the Terminal to uninstall it.

PowerShell builds portable binaries for all Linux distributions. However, Microsoft .NET Core runtime requires several dependencies on different flavors of Linux as well as PowerShell.

For example, on Ubuntu 18.04 and higher, the installation depends on libc6, libgcc1, libgssapi-krb5-2, liblttng-ust0, libstdc++6, libcurl3, libunwind8, libuuid1, zlib1g, libssl1.0.0, and libicu60.

If during the installation process, you come across dependency problems, you’ll have to find and install the components manually.

While preparing this guide, the installation of PowerShell 7 also required liblttng-ust0, libssl1.0.0, and libicu60. If you have the same issues, then you can get these packages with these commands:

Open Terminal.

Type the following command to install liblttng-ust0 and press Enter:

Type the following command to download libicu60 and press Enter:

Type the following command to install libicu60 and press Enter:

Type the following command to download libssl1.0.0 and press Enter:

Type the following command to install libicu60 and press Enter:

Type the following command to install PowerShell and Enter:

Once you complete the steps, PowerShell 7 should install on your Linux device.

In case that you need to download a different version of the dependency packages, you can find them at the Ubuntu package repository.

How To Fix Linux Problems

The goal of this article is simple – I’m going to give you a walk-through explaining how to troubleshoot, fix or otherwise effectively seek help for common Linux problems.

Let’s face it, if you can’t get to a desktop environment, your Linux application usage is going to be pretty limited. This usually comes down to two specific issues: the display server is not playing nicely or perhaps the video driver isn’t doing its job for some reason.

One of the most commonly experienced issues is seeing the splash of a logo then a black screen. It’s understandable how frustrating this can be. Most of the time, this happens when you’re first installing the distro or perhaps it takes place from a “Live” USB boot. In either case, there are some work-a-rounds that will allow you to get past this. Understand however, the first step is to get to the desktop, from there you can explore a better way to make your desktop look right.

Note: Windows users reading this, don’t think this is a Linux only issue. If I had a dollar for every instance where Windows resolution blew out or a video driver update went south, I could buy serious stock in Google. Just want to clear the air on that. Point being, bugs affect all operating systems. Moving on…

Rather than duplicating other video work-around guides, I’m going to link to this guide for fixing the “Black Screen” issue found with some graphic cards. I would also point out that this is less of an issue than it used to be.

Unlike other operating systems where your options are to use an older version of said driver or video settings, Linux affords us solid work-around solutions that have stood the test of time. As Wayland becomes the new display server in the future, it’ll be interesting to see how things progress from there. But for now, the above link will solve 99% of the issues experienced.

To be clear, most people only need to set a boot parameter to get into a graphical interface. From there, the next step below will usually resolve your problems.

Intel – With the exception of dual-graphic environments, I’ve never had a black screen or resolution issue with Intel graphics. If you do, it’s worth trying a system update (from the command line or GUI if you can get to it). If it’s still not working, try doing a Live USB test with a slightly older version of the distro in question (for fixed release distros).

NVIDIA – Once you’re able to get past the black screen issue mentioned above, check and the resolution options under your monitor settings. If you’re experiencing an odd issue with only seeing low resolutions (800*600, or worse), try the following with the command line tool called xrandr and remove the bad settings.

Removing bad configuration:

Reboot and see if your resolution is looking better. If it’s not, then you’re going to need to see what resolutions are available with the existing drivers installed. Let’s run xrandr from the command line and see what resolutions are available.

And on my monitor, this confirms the resolutions available found in my display settings as:

The number x number represents my available resolutions. And the * represents the current resolution being used right now. If you’re stuck at a poor resolution and see greater or ideal resolutions available in the xrandr list, you can try changing it with the following. In my example, I’ll be changing to 1920×1080.

(Note, the dashes need to be right next to each other without a space, but I had to space them for formatting reasons)

Once I hit enter, the screen will flash and it should change the resolution to my new selection. Using xrandr is a fantastic alternative for those instances where using the GUI tools aren’t cooperating due to some odd resolution issues or other monitor out of range headaches.

Truth be told, if the resolution appears in your xrandr output, odds are good that your monitor GUI settings will show the same. But this is a good fall back just in case.

So what should you try if both xrandr and your GUI monitor settings show only limited resolutions? I recommend trying to install the NVIDIA proprietary driver. If you’re running any sort of decent newbie friendly distro, it will come with an installer tool for this. Ubuntu and Mint for example offer this in the Updates tool. Install the “recommended” proprietary video driver and reboot. Then recheck your available resolutions and odds are the problem will be resolved.

Note: For those of you with “hybrid” graphic setups running Intel and NVIDIA, you’re going to want to install the proprietary NVIDIA driver. It will install a package called nvidia-prime. This allows you to effectively choose which video card you wish to use at any given moment. For example, run this in the command line after the proprietary NVIDIA driver are installed:

This will likely output something like nvidia. This means at that moment, this is the video card your hybrid laptop is using. To switch it over to Intel, do the following:

This will switch you back over to your Intel graphics card. You can verify it by using the above verify command. If you prefer to use something automatic instead, you can explore your options with the Bumblebee project. You should be aware it’s degree of success will vary greatly and may not work as smoothly as prime-select.

AMD/ATI – Despite statements claiming AMD video card support has improved over the years for Linux users, I’m still of the mind to just avoid using these cards altogether. That said, if you choose to, follow the same guide as NVIDIA…with one notable exception – you’re looking at open source video drivers only with Ubuntu LTS 16.04. Other distros and future releases may differ here, but I think they have the right idea as AMD drivers are historically, pretty bad.

This means you can still use xrandr or your monitor settings to change resolutions. However if you’re looking to game with an AMD video card, I recommend checking out this guide on getting proprietary AMD video drivers working on Ubuntu. There you will find options such as Optimized Open Graphics Drivers and AMDGPU-PRO based solutions. Personally, I recommend either running Ubuntu 14.04 on the affected system or simply buying a better (NVIDIA) graphics card.

Most Linux based audio issues come from the widespread adoption of the PulseAudio server. At one time, the sound server caused a lot of bugs ranging from crashing to audio just sounding completely wrong at some level. In 2023 however, most issues simply come down to not effectively controlling multiple sound cards.

Enter pavucontrol – the PulseAudio Volume Control tool. This application is usually available from your software repositories and is a must have software title in my opinion. To use it effectively, run pavucontrol and then play some audio. With the sound actively playing, browse to the Playback tab and verify the sound is being sent to the correct device from the pull down menu. This will fix 95% of the issues I see out there.

Another 4% of the sound issues comes down to the audio device in question being muted. Verify you have a command line application called alsamixer installed. Then run it as alsamixer.

The final 1% of issues such as crackling sound, no audio and related can be explored here.

If you’re using a wired connection to a router, odds are you’re not ever going to experience any networking hassles with regard to basic Internet connectivity. If you’re using wireless however, yes, this can be a problem in some rare cases. When dealing with wifi, you’ll be hard pressed to beat my previous article on wifi troubleshooting. It covers everything from diagnosing the issue to finding workable solutions.

The second challenge some users may face with networking is regarding sharing samba directories. As a rule, there are two ways to setup a usable samba share – the secure way or the easy way. The secure samba way is to limit access to a specific user or to a specific group only. That said, samba isn’t that secure to begin with. So if the file sharing is on a LAN that you trust, you could just do samba the easy way.

This last section is a bit of a “catch all” for everything not covered above. Meaning if you have a question not addressed already, you can use the following tips to get the answer you need. Ready? Here we go.

1) Provide useful information about your affected hardware when seeing assistance. For example, which do you think is more useful? “I can’t seem to load any webpages with my Atheros wifi card even though I’m told that the connection is successful.” vs “My wifi isn’t working.” Guess which question is more likely to be solved? The first one, any day of the week.

2) Google for a solution before asking. Look, most of the issues people experience with Linux, Windows or OS X has been examined at length. So use a search engine and try finding a solution before flooding the forums with a redundant question that may have already been answered.

That’s it. If more people would just do those two things, we’d see a lot less frustrated users out there who swear the Linux community is mean. In reality, we just want to see new users make some basic effort and perhaps offer us needed details about their system before asking questions.

How To Install Fortnite On Android

Hit battle royale game Fortnite came to Android well over a year ago now, but playing it hasn’t always been the simplest thing to do, even though the game is now in Chapter 2. You don’t download the game from the Google Play Store (most likely because Epic didn’t want to give Google a cut of its in-app purchases), so you need to sideload the game using the Epic Games App (also unavailable on the Play Store).

But don’t worry. It’s not that complicated, thanks to our quick guide that will show you how to install Fortnite on Android.

Before you start, the first thing you need to know is that Fortnite is quite a demanding game for smartphones. Your phone will need to meet the following technical criteria:

64-bit Android on ARM64 processor,

Android 8.0 or higher,

4GB RAM,

GPU: Adreno 530 or higher, Mali-G71 MP20, Mali-G72 MP12 or higher.

If your phone meets these criteria, then follow the below steps:

First, go to chúng tôi on your Android phone, then tap “Get it on the Epic Games App”.

This will download the Epic Games app through which you can download Fortnite.

Note: You may be asked to give permission to Chrome to download apps from unknown sources. If your phone asks, tap Settings then “Allow from Source” to permanently allow unknown sources to be download from Chrome.

Once you’ve download the Epic Games app APK, install it and open the app. The first thing that appears should be a big picture of Fortnite. Tap it, then tap Install, and you’re away!

Robert Zak

Content Manager at Make Tech Easier. Enjoys Android, Windows, and tinkering with retro console emulation to breaking point.

Subscribe to our newsletter!

Our latest tutorials delivered straight to your inbox

By signing up, you agree to our Privacy Policy and European users agree to the data transfer policy. We will not share your data and you can unsubscribe at any time.

How To Install Msixbundle Using Powershell

The MSIXbundle comes with great benefits over having different MSIX packages for specific architectures. It is a more scalable way to distribute your applications. One way to install MSIXBundle is by using Windows PowerShell. The bundle allows PowerShell to install the resources compatible with and targeted for your PC’s specific system architecture. Once the MSIX packages are bundled together, you only need to specify the location or path of your distribution, and PowerShell will handle the rest.

In this article, we discuss how to install MSIXBundle using Windows PowerShell. Like Appx and AppxPackage, you can use MSIXBundle to sideload or install Windows apps from third-party clouds on your Windows computer. This is quite helpful for some apps not in the Microsoft Store. You can also use MSIXBundle to install Windows apps that show errors or when the servers are not responding.

An MSIXBundle is a Windows app package format used to distribute Universal Windows Platform (UWP) and desktop applications for Windows 11/10. It consists of various MSIX packages bundled together and can support specific architectures in your systems, such as x64, ARM, or x86. For instance, the MSIXBundle format allows users to have one MSIX package for two installer versions, x86, and x64; these are put together in one package called a bundle.

Users can open the MSIXBundle by decompressing the file using a PKZip utility program. Like other MSIX package formats, MSIXBundle is compressed in a PKZip file. Once you decompress the file, the MSIXBundle package resources are replaced by MSIX packages that are put together in a bundle. Let us now see how you can install the MSIX bundle using Windows PowerShell.

If you continuously get errors when you try to install and run MSIXBundle on Windows, or you want to sideload MS Store apps on several computers, you can use PowerShell to run some commands as an administrator. To install MSIXBundle using PowerShell, use the following easy steps:

On the Windows search box, type PowerShell and select Run as administrator.

Copy and paste the following PowerShell command and then hit Enter to initiate app installation: Add-AppxPackage -Path $AppFilePath

Wait until the Windows PowerShell finishes the process, it will indicate the progress.

You can now go to the Start menu and launch the app.

Earlier, we said that you could use the MSIX bundle to install third-party apps that are not in the Microsoft Store. You can follow the steps above, but you must first enable Developer Mode to allow you to install UWP programs from non-MS sites. Follow the steps below to enable the Developer Mode option:

Go to the Windows Settings app and then select Privacy & Security.

Select For Developers and toggle on the button next to Developer Mode.

We hope you can now install the MSIX bundle using Windows PowerShell.

Read: How to install unsigned .Appx app package using PowerShell

If you want to install the MSIX packaging tool, go to the Microsoft Store and then head to the description page, then select Install to start the process. However, ensure that the Microsoft account you are using is the same as the one for the Windows Insider Program. You can also download the MSIX packaging tool in the enterprise for offline use in the Microsoft Store for Business.

Read: The ms-appinstaller protocol has been disabled

To install an MSIX package without the Microsoft Store, you can use third-party sources like GitHub and then use Windows PowerShell to install it using the steps we discussed above. However, unless the app you want to install is completely missing from the store, installing MSIX from the MS Store is the best way to go.

How To Install Android On Virtualbox

Android is a pretty great operating system for phones – it’s versatile, fast and comes with a ton of functions. Of course, if you want to run it on your computer instead of your phone, be it for testing purposes or just for fun, you can do that. All you need to do is to install your chosen version of Android on a normal virtual machine or VM using VirtualBox. Simply follow the steps below and you’ll have Android up and running in no time.

The first step is, of course, installing VirtualBox. To do so, download the software from the official website and follow the simple install process. Once that’s done, you can get started with the real work: Acquiring an android ISO formatted disk image. The most reliable source for this is the Android-x86 project, a team of open source developers that have spent their time porting android code to work on PC hardware.

The next stage is to configure the amount of memory (RAM) that the VM is allocated. The maximum number is based on the system resources of your computer – you can’t use a 16GB machine to give your VM 32GB of RAM! The absolute minimum that you should allocate is 2GB, but somewhere between 6 and 8GB of RAM is recommended. Remember, this VM needs the same sort of resources a physical mobile handset would have, so more is generally better.

Tip: Make sure to leave a minimum of 4GB of RAM free for the rest of your operating system to use, otherwise, you might run into system instability issues.

The next stage of the VM creation process is to make a new virtual hard drive for your virtual machine. Make sure to select the option to “create a virtual hard disk now” and hit next. Any file type will work, the default of VDI is perfectly functional. Again, hit next, and set the file to be a “Fixed Size”. Finally, configure where on your hard drive you want to save your new virtual drive, and how big a hard drive you need. The minimum hard drive size required for the Android-x86 image is 8GB. Depending on what you are planning to do with the virtual machine a hard drive of 16GB should be more than enough and shouldn’t be too much of a drain on your computer’s resources.

In the settings, your first stop is the “Processor” tab under “System”. Here, you can configure the number of CPU cores the VM will have. You should increase this to at least two but preferably more. Just like RAM, this is the same as you wouls see in a physical mobile handset, so more is better.

Tip: The Android-x86 developers warn that only assigning one virtual CPU core to the VM is likely to cause a high chance of system crashes.

The maximum number of CPU cores you can allocate depends on how many cores your computer’s CPU has. Make sure to leave at least two CPU cores to your operating system, although four is better.

Tip: Only physical CPU cores (rather than logical hyperthreaded cores) can be reliably assigned to virtual machines, so don’t go into the red portion of the slider, or you may encounter stability issues.

The next step in the settings is the “Screen” tab under “Display”. Here you want to increase the “Video Memory” available to the VM to 32 or 64MB and ensure that the “Graphics Controller” is set to “VBoxVGA”.

You may be asked to “Select a start-up disk”, if so, select the Android ISO. The next screen will show boot options, to install Android to the VM you need to scroll down and select the “Installation” option.

Tip: The VM might capture your curser (and keyboard), stopping you from moving your mouse out of the window or tabbing out, to free your mouse to control your computer again, you need to press the “Host” key. The “Host” key is shown in the bottom right-hand corner of the VM window, it may default to “Right Ctrl” if you press the Host key, the VM will release your mouse and keyboard back to the operating system.

The next screen is the “Choose Partition” screen. Here you instruct the VM where to install Android on your virtual hard drive. You won’t have any partitions by default, so press the down arrow to highlight “Create/Modify partitions” and press enter. To create a new partition, highlight the “New” option and press enter. You can now configure the properties of the partition, but you can comfortably leave all the values at their suggested default values.

You should, however, apply a name to the partition. Once the partition is created you need to write the change to the disk. To do this move the cursor to the right and select “Write”, you will be asked to verify you want to make this change, type “yes” and press enter to create the partition. Once this is done select “Quit” to back out to the previous “Choose Partition” screen, here you will notice that your new partition is now available for use.

To install Android to your new partition, you first need to select what file system format you want to use, ext4 is likely your best option, though NTFS and FAT32 will also work. When prompted, verify that you want to format the drive. Next, you will be asked if you want to install the “boot loader GRUB”, select yes, GRUB will be used to boot Android. If prompted to convert the disk from GPT to MBR select “yes” as GRUB and GPT are not compatible. The next prompt will ask if you want the “/system” directory to be “read-write”, select yes.

Android is now installing to your virtual hard drive, this process may take time, depending on the system resources you allocated to your VM and your underlying operating system resources. Once installed you’ll be asked if you want to “Launch Android” or to reboot (the VM), select “Launch Android” and your Android VM will come to life.

From here you should configure your Android VM as you would any other Android device. The settings you pick are entirely up to you. When the setup is complete, you can use your Android setup however you would like.

6. Shutting it down

Update the detailed information about How To Install Arch Linux on the Moimoishop.com website. We hope the article's content will meet your needs, and we will regularly update the information to provide you with the fastest and most accurate information. Have a great day!