MicroSD Slot Not Recognized on Intel Compute Stick STCK1A32WFC (Missing SDHCI Controller Support)

[21Development]

Describe the issue you are experiencing

The microSD slot on my Intel Compute Stick STCK1A32WFC is not detected by HaOS, preventing its use for additional storage, such as moving the HA data disk. While the slot functions reliably in Ubuntu 22.04.6 (recognized as mmcblk2 on SDHCI controller 80860F14:02), HaOS fails to detect it—no mmc2 appears in dmesg or /dev/mmcb*, despite the BIOS “SD Card Reader” option being enabled. This seems to stem from HaOS’s kernel missing or inadequately supporting the Bay Trail platform’s SDHCI controller at 80860F14:02

What operating system image do you use?

generic-x86-64 (Generic UEFI capable x86-64 systems)

What version of Home Assistant Operating System is installed?

6.6.73-haos

Did the problem occur after upgrading the Operating System?

Yes

Hardware details

Intel Compute Stick STCK1A32WFC

• Bay Trail
• Atom Z3735F
• 2GB RAM
• 32GB eMMC
• 1 USB port

Steps to reproduce the issue

1. Install HaOS on an Intel Compute Stick STCK1A32WFC (replacing Ubuntu 22.04 or similar).
2. Ensure BIOS “SD Card Reader” is enabled (accessible via 3-second power button hold → BIOS Setup).
3. Insert a microSD card (e.g., 32GB or 128GB) into the slot.
4. Check detection:

• Run dmesg | grep -i mmc—expect only mmc0 (Wi-Fi) and mmc1 (eMMC), no mmc2.
• Run ls /dev/mmcb*—expect only mmcblk1* (eMMC), no mmcblk2.

5. Compare with Ubuntu 22.04.6 live USB:

• Boot Ubuntu, insert card, run dmesg | grep -i mmc—see mmc2 on 80860F14:02.

Expected behavior HaOS should detect the microSD slot as a block device (e.g., mmcblk2) when a card is inserted, matching Ubuntu’s behavior, and make it available in HA’s Storage UI (Settings > System > Storage) for use as a data disk or additional storage.

Anything in the Supervisor logs that might be useful for us?

HaOS
# dmesg | grep -i mmc
mmc0: SDHCI controller on ACPI [INT33BB:00] using ADMA
mmc1: SDHCI controller on ACPI [80860F14:00] using ADMA
mmc0: new high speed SDIO card at address 0001
mmc1: new HS200 MMC card at address 0001
mmcblk1: mmc1:0001 S10032 28.5 GiB

- Note: No mmc2 or 80860F14:02—slot undetected.

Ubuntu 22.04.6:
# dmesg | grep -i mmc
mmc0: SDHCI controller on ACPI [INT33BB:00] using ADMA
mmc1: SDHCI controller on ACPI [80860F14:00] using ADMA
mmc2: SDHCI controller on ACPI [80860F14:02] using ADMA
mmc2: new high speed SDHC card at address 0007
mmcblk2: mmc2:0007 SD32G 29.0 GiB

- Note: Slot detected as mmcblk2

Anything in the Host logs that might be useful for us?

Ubuntu 22.04.6:
# dmesg | grep -i mmc
mmc0: SDHCI controller on ACPI [INT33BB:00] using ADMA
mmc1: SDHCI controller on ACPI [80860F14:00] using ADMA
mmc2: SDHCI controller on ACPI [80860F14:02] using ADMA
mmc2: new high speed SDHC card at address 0007
mmcblk2: mmc2:0007 SD32G 29.0 GiB

- Note: Slot detected as mmcblk2

System information

System Information

version	core-2025.2.5
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.13.1
os_name	Linux
os_version	6.6.73-haos
arch	x86_64
timezone	Europe/London
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	5000
Installed Version	2.0.5
Stage	running
Available Repositories	1554
Downloaded Repositories	29

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 14.2
update_channel	stable
supervisor_version	supervisor-2025.02.1
agent_version	1.6.0
docker_version	27.2.0
disk_total	27.3 GB
disk_used	17.7 GB
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization
board	generic-x86-64
supervisor_api	ok
version_api	ok
installed_addons	Matter Server (7.0.0), Samba share (12.4.0), Duck DNS (1.18.0), Home Assistant Google Drive Backup (0.112.1), Mosquitto broker (6.5.0), File editor (5.8.0), motionEye (0.20.0), Flexget (3.13.23), eBUSd (24.1.1), Asterisk (4.1.2), Plex Media Server (3.6.3), FTP (5.2.1), AdGuard Home (5.2.5), MariaDB (2.7.2), Nginx Proxy Manager (1.0.1), Advanced SSH & Web Terminal (20.0.1)

Dashboards

dashboards	5
resources	13
views	31
mode	storage

Network Configuration

adapters	lo (disabled), enp0s29u1u1 (enabled, default, auto), hassio (disabled), docker0 (disabled), veth1502ee8 (disabled), veth05d763d (disabled), veth7dc2cd0 (disabled), veth2885e10 (disabled), vethc93db8e (disabled), veth26d7470 (disabled), veth920244a (disabled), veth8553f70 (disabled), veth9fa6113 (disabled), vethe846ded (disabled), veth199dc58 (disabled), vethe65bd3a (disabled)
ipv4_addresses	lo (127.0.0.1/8), enp0s29u1u1 (192.168.66.10/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), veth1502ee8 (), veth05d763d (), veth7dc2cd0 (), veth2885e10 (), vethc93db8e (), veth26d7470 (), veth920244a (), veth8553f70 (), veth9fa6113 (), vethe846ded (), veth199dc58 (), vethe65bd3a ()
ipv6_addresses	lo (::1/128), enp0s29u1u1 (fe80::7aed:c757:5af0:65c1/64), hassio (fe80::42:ff:fed3:aff4/64), docker0 (fe80::42:33ff:fe23:c22f/64), veth1502ee8 (fe80::e45e:feff:fe2d:8c6c/64), veth05d763d (fe80::dced:c2ff:fee9:e75a/64), veth7dc2cd0 (fe80::88e8:3fff:fe4a:3444/64), veth2885e10 (fe80::604a:f8ff:feba:c594/64), vethc93db8e (fe80::1015:59ff:fe27:e723/64), veth26d7470 (fe80::24e9:aeff:fe4e:cedb/64), veth920244a (fe80::ec0e:9eff:fe97:987d/64), veth8553f70 (fe80::9006:3cff:fe2d:a1e/64), veth9fa6113 (fe80::859:4aff:fee1:43b1/64), vethe846ded (fe80::868:b2ff:fe74:10fe/64), veth199dc58 (fe80::909e:e9ff:fe43:19a6/64), vethe65bd3a (fe80::3c0d:6ff:fe75:552e/64)
announce_addresses	192.168.66.10, fe80::7aed:c757:5af0:65c1

Recorder

oldest_recorder_run	February 13, 2025 at 11:47 AM
current_recorder_run	February 22, 2025 at 10:45 AM
estimated_db_size	255.04 MiB
database_engine	sqlite
database_version	3.47.1

Additional information

• BIOS: “SD Card Reader” enabled—firmware supports the slot.
• Ubuntu Comparison: Kernel (5.15/6.2) probes 80860F14:02 via sdhci_acpi, loads mmc_block (usage 1), and mounts the card.
• HaOS Issue: Kernel (6.6.73) skips 80860F14:02. GRUB tweak (sdhci_acpi.force_probe=80860F14:02) failed—likely missing CONFIG_MMC_SDHCI_ACPI support or Bay Trail quirks.

Proposed Fix (Custom Kernel Build Steps generated by Grok3 beta):

1. Clone Repo:

• git clone https://github.com/home-assistant/operating-system
• cd operating-system

2. Enter Build Env:

• sudo ./run.sh (requires Docker: sudo apt install docker.io on Ubuntu).

3. Configure Kernel:

• make menuconfig (in buildroot).
• Enable (set to y):
  • CONFIG_MMC_SDHCI_ACPI (Device Drivers > MMC/SD/SDIO > SDHCI ACPI support).
  • CONFIG_MMC_SDHCI (SDHCI core).
  • CONFIG_MMC_BLOCK (MMC block device).
• Search (/): SDHCI, ensure Bay Trail options are enabled.
• Save (updates .config), exit.

4. Build:

• make (~1-2 hours, 20GB disk needed).
• Output: out/haos-ova-*.img.

5. Flash:

• Identify USB: lsblk (e.g., /dev/sdb).
• sudo dd if=out/haos-ova-*.img of=/dev/sdX bs=4M status=progress; sync (replace sdX).

6. Test:

• Boot HaOS from USB, insert microSD, check dmesg | grep -i mmc, ls /dev/mmcb*—expect mmc2 and /dev/mmcblk2.

Request: Add Bay Trail SDHCI support (e.g., 80860F14:02) to default kernel config—could unlock microSD slots on similar devices without custom builds.

Community post with details on troubleshooting steps carried out listed here: https://community.home-assistant.io/t/successfull-installation-on-intel-compute-stick/665051/10

[github-actions[bot]]

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[21Development]

Still the same.

[github-actions[bot]]

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[21Development]

Still not working, seems a simple fix? (As above)