Can't install Arch distros

[Anluz]

Heyo.

I came here asking for some guidance, on diagnosing most likely hardware issues when trying to install Arch distros on an ASUS Expertbook (CV3604CVF) (Intel 1355U + Nvidia 2050).
The screen goes black after selecting the option Arch Linux Install Medium.

Thus far i tried the following:

• Burning the following ISOs (Arch recent and old ones, CachyOS)on:
  • Rufus (MBR, GPT, ISO, DD), BalenaEtcher, Ventoy, USBWrite also tried cat inside ubuntu.
• Tried to chroot install from Ubuntu live with archstrap.
  • While chrooted i tried both manual and archinstall script methods.
• various kernel parameters including nomodeset, i915, nouveau, video=SVIDEO-1:d

Aditional notes:
Firstly tried Ubuntu and Mint to confirm that linux works properly.
I tried 3 different sticks to no avail, all of them worked properly on my desktop (AMD 7800X3D + 4060).
While trying archstrap i managed to "install" it but grub gets stuck on "loading initial ramdisk", i redid the installation again and double checked everything to discard me failing to set up grub properly.
Fast boot and Secure boot are disabled, UEFI only has AHCI.

Im very likely forgetting something, but after a few weeks of reading documentation, the wiki, forums, stackoverflow, reddit, watching videos and mostly trial and error im kinda lost.

 

[Brickwizard]

Welcome to the forums

Tutorial Thread 'Basic checks if Linux fails to install'

Nov 9, 2025

Why Linux fails to load/install direct to HDD, common reasons

1] Corrupt download [check SHA sum]
2] bad burn to installation medium [try again] [if you used Rufus then try Balena Etcher or Ventoy]
2A] if optical drive burn at slow speed [no more than x3]
3] Wind 8.2 and higher quick start/fast boot or secure boot not disabled [after disabling do a full power re-boot not a restart]
3A ] check that boot from USB/Optical drive is enabled in your BIOS?UEFI
4] defective pen-drive/DVD
5] hardware fault,
5A] If old style HDD run integrity check
5B]if SATA SSD check for hidden...

• Brickwizard
• Replies: 2
• Forum: Getting Started

• 

 

[BryantC]

It might actually be the Nvidia 2050 causing the issue. Some laptops with hybrid graphics just drop to a black screen the moment the installer tries to load the default drivers. Try booting with nouveau.modeset=0 and modprobe.blacklist=nouveau. I had a similar problem on another ASUS model — the installer wouldn’t show anything until I completely disabled the nouveau driver.

 

[Trml]

I agree to @BryantC. If the UEFI has an option to turn off the NVIDIA for the time being, that is another option. You can enable it later, after installing nvidia modules.

Also try toggling a BIOS/UEFI CSM mode option, if the machine has it.

edit:
Chrooting the install iso from Ubuntu indeed does not work that easy, as I recall. If no regular booting the ISO works, there is a more cumbersome way to do it via chroot.

 

[Anluz]

Morning.

from what i gathered looking at Ubuntu kernel loads it first tries to load nouveau and fails completly (thats display shows a low resolution while loading the trial) and after a while it starts using i915. I did try to replicate those kernel parameters last night, but didn't work either.

I'm trying to find the option to toggle in the UEFI, will look at it later today, i played a bit with an option that chooses Discrete/Firmware TPM.


I did follow the wiki instructions for chrooting with archstrap, and while i can set up some basic stuff it refuses to load after booting.

 

[Mike-BTU]

Here is an older how-to thread that may help you.

Thread 'Installing ArchLinux 2025 to your computer'

Feb 11, 2025

Degree of Difficulty/Level of Experience - Intermediate to Advanced.

Arch and I have a love/hate relationship. It was my favorite distro for a while, but I don't use it anymore. For one thing it doesn't support EFI, so it won't install on my two newest computers which don't support Legacy BIOS. Which is kind of ironic, because Arch prides itself on being the latest and greatest of everything. But I have rambled enough about EFI these last few days. Some people say Arch is easy to install. We will see if you agree after this article. This article assumes you already have the Arch...

• dos2unix
• Replies: 51
• Forum: Arch and derivatives

• 

He had the same problem as you, but finally figured out how to install Arch on his newer computers.

 

[Mike-BTU]

Here's his solution.

Post in thread 'Installing ArchLinux 2025 to your computer'

Feb 18, 2025

I got Arch Linux to boot in UEFI mode with Qemu. The only thing I had to change was to use a different chiptset for the vm "i144FX" instead of "Q35" and than as firmware "UEFI". When I selected "Q35" with "UEFI" it wouldn't boot in UEFI mode. Try that and see if it works for you as well?

Tah da... it works! I was also able to run it on one of my other Laptops by disabled CSM compatibility mode.
I guess I need to give Arch a clean bill of health.

• dos2unix

• 
• 

I forgot that he was doing this in a VM.

@dos2unix Maybe you have some ideas?

 

[Mike-BTU]

Welcome to the forums

Yes! Welcome!

 

[dos2unix]

We had some issues with the the i44FX chipset, and ended up going back to Q35. But this is only for EFI.

@f33dm3bits found this I think.

 

[f33dm3bits]

@f33dm3bits found this I think.

What did I find?

 

[Trml]

i played a bit with an option that chooses Discrete/Firmware TPM.

TPM does not matter (as long as you don't have fTPM and Win managing it).
Try to turn off the nvidia GPU; Asus UEFI should have that option.

While trying archstrap i managed to "install" it but grub gets stuck on "loading initial ramdisk", i redid the installation again and double checked everything to discard me failing to set up grub properly.

I overread this a little earlier, you got further than I thought. Alternatively, for UEFI the systemd-boot can be used. Or you can paste the grub-install line you used to install it. Likely you needed the kernel parameters that keep the ISO from booting.

 

[dos2unix]

What did I find?

i44FX vx Q35 chipset when installing arch to a VM

 

[Anluz]

Try to turn off the nvidia GPU; Asus UEFI should have that option.

I couldn't find an option on the BIOS for that, it was one of the first things i tried too, that's why i relied more on kernel params.

I overread this a little earlier, you got further than I thought. Alternatively, for UEFI the systemd-boot can be used. Or you can paste the grub-install line you used to install it. Likely you needed the kernel parameters that keep the ISO from booting.

# grub-install --target=x86_64-efi --efi-directory=/efi boot-directory=/boot --bootloader-id=ARCH
I did install nvidia drivers too before rebooting (nvidia-dkms + nvidia-utils).

Keep in mind that for me to be able to reach these steps i was installing via archstrap following the wiki https://wiki.archlinux.org/title/Install_Arch_Linux_from_existing_Linux.

i44FX vx Q35 chipset when installing arch to a VM

I don't know if it applies then, im trying to install it bare metal. If so how could i do it?

 

[Trml]

i was installing via archstrap following the wiki

I don't know that tool. Looking it up, the readme mentions you need to verify environment variables (e.g. /tmp) are correctly set. Did you do that? Was there any output using the tool?

This forum has handy features to upload screenshots. When you work from an installation ISO it is difficult to capture commands/steps you use and corresponding output, to communicate about it here. Using a screenshot is as easy as making a typo, if you see what I mean.

# grub-install --target=x86_64-efi --efi-directory=/efi boot-directory=/boot --bootloader-id=ARCH
I did install nvidia drivers too before rebooting (nvidia-dkms + nvidia-utils).

E.g. that grub misses dashes in front of boot-directory; a typo I assume.
I've had best results with using the --removable option for grub-install; I suggest you add that next time around.

Regarding the dkms, I'm actually not sure how well that works during installation, i.e. if it's supported. The reason being you need to install kernel headers and execute it in chroot, where the installed kernel easily differs from the ISO. How did you check dkms-install of the module was successful? Which mkinitcpio hooks did you use and was the initramfs generation successful (output in terminal)?

I think chances are best, if we stick to the ISO installer for the time being. Where did you set kernel parameters to get rid of the black screen and did you use the exact combo @BryantC suggested?

 

[f33dm3bits]

# grub-install --target=x86_64-efi --efi-directory=/efi boot-directory=/boot --bootloader-id=ARCH
I did install nvidia drivers too before rebooting (nvidia-dkms + nvidia-utils).

It might be useful if you share your partition setup, depending on your setup this command could be different.

lsblk -f

Also something useful for Nvidia is to add the nvidia modules to /etc/mkinitcpio.conf
It looks like this:

MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)

After you add that run the following.

sudo mkinitcpio -P

Then reboot

 

[Anluz]

I don't know that tool. Looking it up, the readme mentions you need to verify environment variables (e.g. /tmp) are correctly set. Did you do that? Was there any output using the tool?

Yes i did.

This forum has handy features to upload screenshots. When you work from an installation ISO it is difficult to capture commands/steps you use and corresponding output, to communicate about it here. Using a screenshot is as easy as making a typo, if you see what I mean.

E.g. that grub misses dashes in front of boot-directory; a typo I assume.
I've had best results with using the --removable option for grub-install; I suggest you add that next time around.

Regarding the dkms, I'm actually not sure how well that works during installation, i.e. if it's supported. The reason being you need to install kernel headers and execute it in chroot, where the installed kernel easily differs from the ISO. How did you check dkms-install of the module was successful? Which mkinitcpio hooks did you use and was the initramfs generation successful (output in terminal)?

Regarding this, ill try once again later tonight, and attach screenshots + commands used too.

I think chances are best, if we stick to the ISO installer for the time being. Where did you set kernel parameters to get rid of the black screen and did you use the exact combo @BryantC suggested?

Yes i did along with parameters trying to force i915.

It might be useful if you share your partition setup, depending on your setup this command could be different.

lsblk -f

Also something useful for Nvidia is to add the nvidia modules to /etc/mkinitcpio.conf
It looks like this:

MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)

After you add that run the following.

sudo mkinitcpio -P

Then reboot

I believe i did not add those params in the mkinitcpio in earlier tries. Will try that too later on.

Thanks for the help thus far.

 

[f33dm3bits]

I believe i did not add those params in the mkinitcpio in earlier tries. Will try that too later on.

The error you are getting after grub tries to load the kernel.

but grub gets stuck on "loading initial ramdisk", i redid the installation again and double checked everything to discard me failing to set up grub properly.

From that I'm understanding you do see grub and when grub then tries to boot the kernel you get that message. I'm getting the impression that might be related to the command you used to install grub.

# grub-install --target=x86_64-efi --efi-directory=/efi boot-directory=/boot --bootloader-id=ARCH

Because you did install Grub, only it seems grub can't load anything? That's why I was asking to share your partition and file-system setup.

It might be useful if you share your partition setup, depending on your setup this command could be different.

lsblk -f

I don't know how you installed Arch Linux, manually or with archinstall? If the latter I would have expected to boot correctly because that error message indicates it can't boot or load your ramdisk. So maybe thinking you need to run a different grub-install command, that's why looking at your partition setup would be useful.

 

[Anluz]

Hello there!

Sorry about the delay, here its the steps that i take to install Arch with archstrap from Ubuntu. While taking screenshots and looking at history i started to realize the amount of mistakes i make.

Here are the steps that i take:

1. First i clone the repo and mount on /tmp

2. Partitioning of the disk.

History of commands before chroot:

3. Commands executed in chroot.

I did add "MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)" inside mkinitcpio.conf

looking at history i realized i almost forgot to set up grub.cfg

Final result:

I think chances are best, if we stick to the ISO installer for the time being. Where did you set kernel parameters to get rid of the black screen and did you use the exact combo @BryantC suggested?

Regarding this, the way i get something out of the ISO installer is with Ventoy >> boot in grub2 mode

 

[Trml]

The screenshots (also from history) are very helpful.

I think we should circle the /boot mount. In the lsblk @f33dm3bits asked for we don't see a partition for /boot. Yet, you specify --boot-directory /boot for the grub-install. Maybe what happens is grub installs to /boot under the root directory, but does not find it at boot.

Looking up history, you skipped the following line from the Arch installation guide:

# mount --mkdir /dev/efi_system_partition /mnt/boot

What this does is mount /boot to the EFI/esp partition (so the path in the guide is /efi/boot).

Have a look at the /etc/fstab of the (half-)installed system, look for an appropriate entry for a /boot partition. There probably is none.

(you don't have to re-do the installation, only mount it via your last method, chroot into it and correct the steps for grub)

Do mount a /boot path explicitly prior to re-executing the grub-install.
Use the --boot-directory option only, if you use a separate partition for /boot. If you don't use a partition, skip it but double check /boot shows under mounts prior to re-executing grub-install.

If it does not work, please add the HOOKS= line of mkinitcpio.conf that is used.

 

[f33dm3bits]

I think we should circle the /boot mount. In the lsblk @f33dm3bits asked for we don't see a partition for /boot. Yet, you specify --boot-directory /boot for the grub-install. Maybe what happens is grub installs to /boot under the root directory, but does not find it at boot.

I have all my boot(kernel and efi) files under /efi and I do still have a /boot under my root file-system but the only thing that resides there is "amd-ucode.img". I don't use Grub but systemd-boot for my setup.

In the pacstrap command history I only see /efi and not a /boot partition. So my first thought since no kernel presets were changed that the kernel files reside under /boot because those are still the default location for the presets to place them unless you change that.

I'd be curious to see the output of this.

ls -l /mnt/boot /mnt/efi

Also it seems like you are dual-booting since you also have an two efi and one ntfs partition, my guess is the first one is for Windows. So my second thought is maybe your Grub is done correctly but when Grub tries to load the efi file it uses the wrong efi partition and that's why it's stuck at loading initramfs. I would also look in that direction. I would think you should be able to use the same efi partition for both Windows and Linux from what I've seen on other forums but can't tell you that since I don't have recent experience with dual-booting with Windows.

Dual boot with Windows - ArchWiki

I'll highlight what you might want to try.

rEFInd and systemd-boot will autodetect Windows Boot Manager (\EFI\Microsoft\Boot\bootmgfw.efi) and show it in their boot menu automatically.

For GRUB follow either GRUB#Windows installed in UEFI/GPT mode to add boot menu entry manually or GRUB#Detecting other operating systems for a generated configuration file.

Also depending on which Windows version you are using you may also need to setup secure-boot on Arch Linux.