sasuke
October 5, 2026, 2:16pm
1
System Details
Device : [SASUKE]
OS : [debian]
Firmware Type : [UEFI Full ROM]
Firmware Version : [latest 2609.1 Release ]
Internal storage type : [eMMC]
Summary of the Issue
It seems that this issue is still present. Actually, it may have gotten worse, since the boot delay got even longer than on 2606 or 2603.
opened 01:30PM - 07 Mar 26 UTC
## Device Info
- **Board:** Google Sasuke (Dedede family)
- **CPU:** Intel Celer… on N4500 (Jasper Lake A0)
- **Firmware:** MrChromebox-2512.2 (UEFI Full ROM)
- **OS:** Ubuntu 24.04.4 LTS, kernel 6.17.0-14-generic
- **SD card:** 128GB Samsung FD4Q9 (SDXC, UHS-I SDR104)
## Problem
With a microSD card inserted in the on-board slot (PCI 00:14.5, Intel 8086:4df8), boot takes **2+ minutes** from power-on to GRUB/LUKS prompt. With the SD card removed, the same boot takes **~17 seconds**.
The entire 140+ second delay occurs during the EDK2/UEFI phase — coreboot itself completes in ~1.26 seconds (see cbmem below).
## Reproduction
1. Insert any SDXC card into the on-board microSD slot
2. Power on
3. Observe 2+ minute boot (vs ~17s without card)
The card is not being booted from — it contains a single LUKS-encrypted ext4 partition. The delay is purely from enumeration.
## Kernel dmesg (after EDK2 hands off)
The kernel sees the SD controller early but the card itself doesn't appear until ~230s:
```
[ 0.648] sdhci-pci 0000:00:14.5: SDHCI controller found [8086:4df8] (rev 1)
[ 0.649] mmc0: SDHCI controller on PCI [0000:00:14.5] using ADMA 64-bit
[230.929] mmc0: non-supported SD ext reg layout
[230.929] mmc0: new UHS-I speed SDR104 SDXC card at address 0001
[230.930] mmcblk0: mmc0:0001 FD4Q9 119 GiB
[370.175] mmc0: card 0001 removed
[377.719] mmc0: error -123 whilst initialising SD card
[379.191] mmc0: non-supported SD ext reg layout
[379.191] mmc0: new UHS-I speed SDR104 SDXC card at address 0001
[389.675] mmc0: Timeout waiting for hardware interrupt.
```
The card enumerates, then disconnects/reconnects with errors — suggesting EDK2 leaves the SDHCI controller in an odd state.
## cbmem -t (coreboot timing)
Coreboot completes in 1.26s total:
```
48 entries total:
0:1st timestamp 35,102 (0)
11:start of bootblock 54,404 (19,301)
12:end of bootblock 58,822 (4,417)
1:start of romstage 60,179
951:returning from FspMemoryInit 162,622 (70,813)
955:returning from FspSiliconInit 417,425 (114,198)
70:device setup done 506,433 (82,440)
16:finished LZMA decompress (ignore for x86) 1,259,490 (746,652)
99:selfboot jump 1,260,835 (182)
Total Time: 1,225,710
```
## What I've tried
- **Disabled Intel ME** in Platform Setup Menu → no effect on boot time
- **Cleaned NVRAM / boot entries** → no effect
- **Set boot timeout to 0** → no effect
- **Checked for Fast Boot option** → not available in EDK2 setup menu
- **Different SD cards** → same behavior
## Workaround
Remove SD card before boot, hot-insert after login. I've set up a udev+systemd service to auto-unlock/mount the LUKS partition on insertion.
## Relation to #776
Issue #776 reports that the on-board SD slot isn't recognized in the EDK2 boot menu on Sasuke. My issue is related but distinct: the SD card is never bootable from EDK2, but its presence during boot causes a ~140s delay in the EDK2 phase before handing off to the OS bootloader.
Both issues point to problematic SDHCI controller handling (8086:4df8) in EDK2 on Jasper Lake Dedede boards.
Steps to Reproduce
Insert a SD card into the powered-off device
Start it
Wait about 3 to 4 minutes until the boot screen finally appears.
Expected Behavior
Without the SD card, the startup takes less than 10 seconds.
the issue is still open on github, because it’s a known issue.
sasuke
October 5, 2026, 2:19pm
3
Strangely enough, I remember that 3 main versions ago, the device would start up normally.
3 main versions ago was 3 stable tags (or more) of edk2 ago. possible something changed there.
Do you mean 2512 or 2603?
sasuke
October 5, 2026, 2:31pm
6
It must’ve been the 2603.1 Release I remember that it was present on 2603.0
sasuke
October 5, 2026, 2:46pm
7
Given that this is a “Samsung Galaxy Chromebook Go” with some measly 64GB built-in storage capacity, and no expansion slots whatsoever, the SD card is kind of necessary.
only so many hours in a day, and only so much time I can spend fixing bugs in another project for free