> I'd suggest installing to a USB drive instead. After booting that, collect > information from sendbug(1) to make a bug report (often simplest done by > running "sendbug -P > /tmp/sendbug.txt" and then sending the file from a > normal email client to [email protected] with a description of what happens - > please run sendbug as root to get more information).
Thank you for the suggestion, Stuart! That was fun, but now the plot gets thicker. I installed 6.3 to a usb stick, but when I reboot into the install, my eMMC is suddenly showing up as 29GB, as it should. Should I try somehow manually installing from my openbsd install on the usb to the eMMC? That seems convoluted but possibly fun. Here are the sdmmc related lines from dmesg in the install environment: sdhc0 at acpi0: SDHD addr 0x90a02000/0x1000 irq 44 sdhc0: SDHC 3.0, 200 MHz base clock sdmmc0 at sdhc0: 8-bit, sd high-speed, mmc high-speed, dma ... sdmmc0: can't re-read EXT_CSD sdmmc0: mem init failed scsibus0 at sdmmc0: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: <SD/MMC, HBG4e\\005, 0000> SCSI2 0/direct removable sd0: 1024MB, 512 bytes/sector, 2097152 sectors And after installing to usb dmesg: sdhc0 at acpi0: SDHD addr 0x90a02000/0x1000 irq 44 sdhc0: SDHC 3.0, 200 MHz base clock sdmmc0 at sdhc0: 8-bit, sd high-speed, mmc high-speed, dma ... sdhc_sdclk_frequency_select: command in progress scsibus1 at sdmmc0: 2 targets, initiator 0 sd0 at scsibus1 targ 1 lun 0: <SD/MMC, HBG4e\\005, 0000> SCSI2 0/direct removable sd0: 29824MB, 512 bytes/sector, 61079552 sectors So I'm not seeing the same error from my usb install of 6.3, and am getting access to the full eMMC. Fdisk could see the whole thing. I probably could have re-partitioned it. Presumably my sendbug PR isn't worth much since the problem wasn't happening in that system? -Nathan
