Replies: 1 comment
|
Omarchy uses iwd for the network stack so that was why you got the error with wifi. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
As of today, the extent the official Omarchy installation process supports dual-booting is referring to the Manual installation page in the Manual, which primarily uses
archinstall. However, dual-booting this way only works by having two separate drives, becausearchinstall's Default Partitioning requires a complete drive for itself. Common workarounds on other guides that involve manually partitioning, thenarchinstall's Pre-mounted partitions option work but are unfortunately incompatible with LUKS encryption for linux on a btrfs partition (as ofarchinstallv4.3), which fails to find the root partition if it's encrypted. Encryption on a daily driver is must-have.The following is a guide to dual-boot Omarchy and Windows, with Omarchy installed on a LUKS encrypted btrfs partition on the same drive as Windows. This is a fully manual installation that completely foregoes
archinstallfor the reasons above, and is designed to replicate what thearchinstallinstallation does, and with the specifics given in the Manual installation page.This worked for me on a Dell G3 laptop with Windows 10.Step 0: Windows and BIOS Preparations
Shrink Windows Partition: Create free unallocated space within Windows using Disk Management.
Disable Secure Boot: In BIOS settings, disable SecureBoot. Else it won't allow you to boot arch iso from a USB.
Storage Controller: If
lsblkdoes not see your drive, reboot and go into BIOS settings and check if Storage Controller Mode is Intel RST, Intel Rapid Storage, RAID, or VMD. Arch often can't see these. This is how you change it to AHCI, which Arch will see.Important: You must set Windows to Safeboot before changing it to AHCI (or it won't use the right storage driver and fail to boot):
i. In Windows, open Command Prompt as Administrator and enter:
bcdedit /set {current} safeboot minimalii. Reboot to BIOS. Change Storage Controller to to AHCI.
iii. Boot to Windows (should automatically boot in Safe Mode). Open Command Prompt as Administrator and enter:
bcdedit /deletevalue {current} safebootiv. Reboot normally. Windows should now work with AHCI as storage controller.
Step 1: Boot into Arch ISO
Flash a standard Arch ISO (not Omarchy ISO) onto your flash drive. I recommend Rufus for this.
Boot from the USB and wait for the
root@archisoprompt.Step 2: Connect to the Internet
If using Wi-Fi:
Bash
If you're plugged in via ethernet, you're already connected.
Step 2.5: (Optional) SSH Access
Recommended to have a clipboard for this, which the archiso terminal does not have.
Bash
From your other computer:
ssh root@192.168.x.xStep 3: Create Partitions
See your drive with
lsblk. You should see your flash drive (will have same size as your USB and typically be called sda), and your main drive (typically nvme0n1 on new computers). Henceforth I will call it nvme0n1. You should also see a bunch of Windows' partitions.Enter the
cfdiskTUI for partitioning withcfdisk /dev/nvme0n1.EFI Partition: Highlight your free space and select 'New'. Type in
1Gas its size, then set its Type asEFI systemRoot Partition: Highlight your free space again, select 'New', and by default should have the remaining free space as its size, so hit Enter. Make Type
btrfs.Write and Quit.
Note: This guide assumes your EFI is
nvme0n1p7and Root isnvme0n1p8.Step 4: Configure Partitions
NOTE: (replace nvme0n1p7 with your EFI partition)
Configure EFI partition:
mkfs.fat -F32 /dev/nvme0n1p7Configure omarchy partition as LUKS container (replace nvme0n1p8 with your main linux partition)
Bash
Format btrfs on top of LUKS:
mkfs.btrfs /dev/mapper/cryptrootMount your partitions (replace nvme0n1p7 with your EFI partition)
Bash
Step 5: Create and Mount Subvolumes
Create btrfs subvolumes
Bash
Mount subvolumes (replace nvme0n1p7 with your EFI partition)
Bash
Step 6: System Provisioning
Install base system
Bash
Generate fstab:
genfstab -U /mnt >> /mnt/etc/fstabStep 7: System Configuration
Chroot in:
arch-chroot /mntSet your timezone (replace America/Dallas with yours)
Bash
Set your hostname (replace archlinux with your desired hostname):
echo "archlinux" > /etc/hostnameSet root password:
passwdSet your locale (replace en_US with yours)
Bash
Create superuser (replace yourusername with your desired one):
useradd -m -G wheel -s /bin/bash yourusernameCreate superuser's password:
passwd yourusernameMake user super (i.e. sudo access):
sed -i 's/# %wheel ALL=(ALL:ALL) ALL/%wheel ALL=(ALL:ALL) ALL/' /etc/sudoersStep 8: Configure Bootloader
i. Hooks line and initcpio:
sed -i 's/^HOOKS=.*/HOOKS=(base udev autodetect microcode modconf block keyboard encrypt filesystems)/' /etc/mkinitcpio.confThen compile it with:
mkinitcpio -Pii. Enable network services:
systemctl enable NetworkManageriii. Limine bootloader (replace nvme0n1 --part7 with your EFI partition)
Bash
iv. See your LUKS partition's UUID (replace nvme0n1p8 with your main linux partition):
blkid -o value -s UUID /dev/nvme0n1p8v. Create /boot/EFI/limine/limine.conf. Replace "Your-UUID-here" with the UUID you got from above.
Bash
vi. Create Pacman hook (keeps Limine updated):
Bash
Step 9: Reboot into Arch Linux
Bash
Right now, Limine will only show Arch Linux. We will add Windows Boot Manager to it later because the Omarchy install overwrites limine.conf. I recommend verifying that you can still boot into Windows from your computer's BIOS menu.
Step 10: Install Omarchy
Install Omarchy with
curl -fsSL https://omarchy.org/install | bashNow when you boot up, if Windows does not show up on your Limine,
sudo limine-scanWhen you boot into Limine it should now be there.
Optional: change Limine listing name of "Windows Boot Manager" to "Windows 10/11" with
sudo nvim /boot/limine.confPost-Install Notes
This install should work just fine for almost everyone but due to the nature of manual install, there may be a few hardware specific things missing specific to your hardware. Only issues I encountered were audio not detecting my sound card (one-liner fix), and DNS not working (two-line fix).
Audio not working because of missing firmware. FIX: install sof-firmware from pacman and reboot.
Could have been prevented by adding sof-firmware in the pacakages named in Step 6. (Didn't include it because not for everyone.)
DNS not working (wifi not working despite saying it's connected and being able to SSH). Basically /etc/resolv.conf was invalid for some reason, so remove, then regenerate it. Still not sure why this happened for me but fix was easy.
Bash
All reactions