• Arch Linux Manual Network Setup

In this guide I will show how to get started with Arch Linux using simple steps!

Welcome to arch linux for dummies. I hope this tutorial can help new folks (like me) getting things working. Note: This tutorial is based on. But I will try to make things easier for you dummies. Arch A basic installation with all base packages should take less than 800 MB of disk space. The last arch linux version can be downloaded at (BitTorrent download recommended). The image can be burned to a CD, mounted as an ISO file, or be directly written to a USB stick using a utility like dd ( on Windows).

If arch is been installed in a virtual machine (like ), just create your disc, and start it from the ISO file. The ISO image supports both 32bit and 64bit systems. After booting into the installation media, you will be automatically logged in as the root user and presented with a zsh shell prompt. For modifying or creating configuration files, nano will be used. Fell free to use vim in case you have experience with it.

UEFI mode This tutorial will consider that you have a motherboard with UEFI mode enabled. To verify you are booted in UEFI mode, check that the following directory is populated: # ls /sys/firmware/efi/efivars Note: If arch is been installed in a VM, remember to change the motherboard settings to support UEFI/efivars. Preparation Make sure your internet connection is working (it probably should): # ping google.com If no connection is available, see.

You can also use the wifi-menu command to connect to WiFi. Make sure your system clock is accurate: # timedatectl set-ntp true # timedatectl status Partitioning This section is based on, and. Identify the devices where the new system will be installed: # lsblk!Note: In this section, the 'sd xy' notation will be used, where x represents device and y represents partition (eg. Sd a1, sd a2, sd b1, etc.). Let's start partitioning our device (eg. Sda, sdb, etc.): # parted /dev/sdx If you run a print, you will see the partition label is not defined. Let's set the partition label to gpt: (parted) mklabel gpt If you print again, you will now be able to see an empty partition table.

In this tutorial, we are going to create a basic gpt with 3 partitions (first for boot, second for swap, and third for our data). The boot partition can have a size between 260Mb and 512Mb.

The swap partition needs to have at least your RAM size (it's recomemnded to have 2x RAM size). The remaning space is going to be allocated to your data. Let's format: (parted) mkpart ESP fat32 1MiB 513MiB (parted) set 1 boot on (parted) mkpart primary linux-swap 513M 3G (parted) mkpart primary ext4 3G 100% You can print again to check if your partition table is ok. Exit from parted with: (parted) quit Formatting You need to format each of your partitions, except for swap. All available partitions on device can be listed with the following command: # lsblk /dev/sdx Format the boot partition to fat32: # mkfs.fat -F32 /dev/sdx1 Set up swap partition: # mkswap /dev/sdx2 # swapon /dev/sdx2 Then, format your data partition: # mkfs.ext4 /dev/sdx3 If you want, you can check your partitions with lsblk again.

Contents. The end of the Dual-Boot Era! No more dual-booting baby! I still cannot believe it! I was really looking forward to it and it’s finally here also for me! I really love working under Linux: everything feels smooth, stable, secure and the power of customization is in your hands! Qualities that you cannot find in Windows. Not up until now at least.

Windows are however a necessity: if you are a gamer or your bound to windows-only programs you know what I mean! In this guide I will show you how you can setup -KVM to achieve GPU passthrough and ultimately get rid of dual booting.

This guide will cover the case of using identical GPUs and is a bit different from the most guides out there which go via the pci - stub module. We will directly use the vfio - pci! Drwxr-xr-x 2 root root 0 Feb 28 19:41. Drwxr-xr-x 3 root root 0 Feb 28 19:40. Lrwxrwxrwx 1 root root 0 Feb 28:00:01.0 -././././devices/pci00:00:01.0 lrwxrwxrwx 1 root root 0 Feb 28:00:01.1 -././././devices/pci00:00:01.1 lrwxrwxrwx 1 root root 0 Feb 28:01:00.0 -././././devices/pci00:00:01.0/0000:01:00.0 lrwxrwxrwx 1 root root 0 Feb 28:01:00.1 -././././devices/pci00:00:01.0/0000:01:00.1 lrwxrwxrwx 1 root root 0 Feb 28:02:00.0 -././././devices/pci00:00:01.1/0000:02:00.0 lrwxrwxrwx 1 root root 0 Feb 28:02:00.1 -././././devices/pci00:00:01.1/0000:02:00.1. Reboot Now check again your IOMMU group. The two graphics card should belong to different IOMMU groups.

Arch Linux Manual Network Setup

If yes, you are good to proceed! Step 5: Configure vfio-pci Now this is the part that differs from most guides out there. And most importantly, with the following method we are able to proceed with our setup even if we have two identical graphics cards. The idea is basically to override the NVDIA driver module with the vfio - pci one.

For that, we need to assign as driver the vfio - pci module before the NVIDIA driver module has the chance to take over. Luckily, we can achieve that with the mkinitcpio with two steps:. Create a script that overrides the graphics card driver. Load the vfio - pci before any boot hooks vfio-pci-override script The following script will use the driveroverride feature introduced in kernel v3.16 and make vfio - pci the exclusive driver for that device.