Hellmo_luciferrari

  • 16 Posts
  • 248 Comments
Joined 9 months ago
cake
Cake day: December 20th, 2023

help-circle



  • I tried using Bazzite since I didn’t want to fuss with Wayland on Nvidia with Arch.

    I had more gripes and more issues with an immutable distro than I ever did with my Arch install.

    Stuck it out with Arch. It has taught me a lot.

    The problem many folks have with Arch is the fact they don’t want to read or learn; well, newsflash, if you read and learn Arch isn’t exactly all that hard to use, setup, or maintain. It has better documentation than Bazzite and other newer distros. In fact, Arch Wiki has saved me hassle for other distros.

    Your mileage may vary. However, I wouldn’t recommend an immutable distribution nec3ssarily to someone coming from Windows unless they want to shift from one paradigm to another.

    Switching from Windows to something with such a vastly different approach in many cases will turn users away from using Linux. Their experience can dictate they switch away because of lack of knowledge and then proced to conflate every distro as just one “Linux” experience and not want to look back at it.

    I still stand by one thing you will always hear me say: use the right tool for the job.









  • Glad to hear another success story of someone who dropped Windows.

    I dropped Windows on all of my machines over a month ago. My 2 desktops and 1 laptop I own are on Arch. I can’t fully escape Windows completely due to music production software I use due to lack of support for the hardware on Linux. (Thanks Line6…) So I run a Windows VM in QEMU with USB passthrough, but with no network access.

    I wrote an alias to count days its been since I switched to Linux full time.

    It wasn’t a difficult switch for me. Even with the learning curve. I actually enjoy the tinkering and learning aspect.





  • I cannot take credit for finding the solution. Someone on a discord chat I found was able to help me. The fix:

    1 Open a terminal:

    Unlock the LUKS partition:

    cryptsetup luksOpen /dev/nvme0n1p2 arch

    2 Mount the BTRFS filesystem: Since BTRFS has subvolumes, you need to mount the correct subvolume:

    mount -o subvol=@ /dev/mapper/arch /mnt

    3 Mount the necessary virtual filesystems:

    
    mount --types proc /proc /mnt/proc
    mount --rbind /sys /mnt/sys
    mount --make-rslave /mnt/sys
    mount --rbind /dev /mnt/dev
    mount --make-rslave /mnt/dev
    

    4 Bind the boot partition (if separate): If you have a separate boot partition, you need to mount it too:

    mount /dev/nvme0n1p1 /mnt/boot

    5 Chroot into your system:

    arch-chroot /mnt

    6 Fix your fstab: Ensure that your /etc/fstab file inside the chroot environment is correctly set up. You might need to generate a new one using genfstab:

    genfstab -U /mnt >> /mnt/etc/fstab

    7 Update GRUB: Reinstall and update GRUB to ensure it is correctly installed:

    grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB
    grub-mkconfig -o /boot/grub/grub.cfg
    

    Exit the chroot environment:

    exit

    Unmount all the filesystems:

    bash

    umount -R /mnt
    cryptsetup luksClose arch
    

    8 Reboot:

    reboot