### System details

Tronsmart Ara X5 Plus (Atom x5-Z8300 Cherry Trail + 2GB DDR3L + 32GB eMMC)

### What's wrong?

# BUG: Omarchy v4.0.4 does not detect eMMC as an installation drive

### Description

On **Omarchy v4.0.4**, the internal eMMC storage is not detected by the installer on the first boot.

The eMMC is completely functional, but it does not appear as an available installation drive when running the Omarchy installer.

The system is booted from a USB drive, and the affected device is an internal **29.1 GB eMMC**.

### Hardware / Environment

* Omarchy: **v4.032**
* Booting from: USB
* Internal storage: **29.1 GB eMMC**
* eMMC partitions:

  * `mmcblk2p1` — 256 MB
  * `mmcblk2p2` — 28.9 GB

### Symptoms

Initially, `lsblk` only showed the USB/SATA devices and no `/dev/mmcblk*` device.

`dmesg` showed the SDHCI controllers being detected, but the eMMC was not initialized:

```text
mmc1: SDHCI controller on ACPI [80860F14:02] using ADMA
mmc2: SDHCI controller on ACPI [80860F14:00] using ADMA
mmc0: SDHCI controller on ACPI [80860F14:03] using ADMA
mmc2: new HS200 MMC card at address 0001
mmc1: Failed to initialize a non-removable card
```

After manually loading the required kernel modules and triggering udev:

```bash
modprobe mmc_block
modprobe sdhci
modprobe sdhci_acpi
udevadm trigger
udevadm settle
```

the eMMC appeared correctly:

```text
mmcblk2       29.1G
├─mmcblk2p1    256M
└─mmcblk2p2   28.9G
```

At that point, running:

```bash
./automated_script.sh
```

allowed the installer to detect `mmcblk2` as the installation drive.

### Expected behavior

The eMMC should be initialized and detected automatically during the live environment boot, and `mmcblk2` should be available as an installation target without requiring manual `modprobe`/`udevadm` commands.

### Actual behavior

The eMMC is missing from the available installation drives until the following commands are run manually:

```bash
modprobe mmc_block
modprobe sdhci
modprobe sdhci_acpi
udevadm trigger
udevadm settle
```

### Additional information

This appears to be an initialization issue rather than a hardware problem, since the eMMC is detected correctly after manually loading the modules and can then be used by the installer.

I also tested several commands while troubleshooting; screenshots are attached showing the troubleshooting process and the successful detection of the eMMC.

**This would be great to have fixed in a future release so that eMMC devices are detected automatically by the installer.**