On Sat, 5 Oct 2024 12:23:47 +0200 Theo Buehler <t...@theobuehler.org> wrote:
> On Sat, Oct 05, 2024 at 06:14:33PM +0800, Chris Billington wrote: > > > > >Synopsis: O2 Micro PCI SD/MMC Card Reader "sdmmc0: can't enable card" > > >Category: system > > >Environment: > > System : OpenBSD 7.6 > > Details : OpenBSD 7.6-current (GENERIC.MP) #344: Wed Oct 2 > > 12:26:27 MDT 2024 > > > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > > Architecture: OpenBSD.amd64 > > Machine : amd64 > > >Description: > > > > Machine: Panasonic Let's Note CF-SZ6 laptop with O2 Micro PCI-attached > > SD/MMC reader with PCIid: 1217:8520 > > When an SDHC/SDXC card is inserted into the reader, the card is not > > detected and > > /bsd: sdmmc0: can't enable card > > is written to the system log. > > The behaviour is not consistent. > > The first time the card is plugged in, the SD-card access light flashes > > several times and "can't enable card" is logged. > > The second time, the access light does not flash and nothing is logged. > > Third and subsequent attempts go back to the first behaviour: it alternates. > > In both cases the disk is not available (sysctl hw.disknames). > > The symptoms are the same as the ones apparently fixed by hastings in > this diff: > > https://marc.info/?l=openbsd-tech&m=172698492122450&w=2 > > It's probably worth a try. Thanks for the link! I can confirm that applying the diff by Hastings fixes the 'can't enable card' error with this O2 Micro SD-Card reader: With UHS-1 card: Oct 6 12:45:55 emulti8 /bsd: scsibus4 at sdmmc0: 2 targets, initiator 0 Oct 6 12:45:55 emulti8 /bsd: sd1 at scsibus4 targ 1 lun 0: <Apacer, SD64G, 0030> removable Oct 6 12:45:55 emulti8 /bsd: sd1: 59664MB, 512 bytes/sector, 122191872 sectors This boot-time, the reader is detected as '50 Mhz clock': sdhc0: SDHC 4.00, 50 MHz base clock sdmmc0 at sdhc0: 4-bit, sd high-speed, mmc high-speed, ddr52, dma Since I am not subscribed to the tech@ mailing list, I can't reply to the original thread there to notify this as working with this particular chipset, but I will send a new message referencing it. -- Chris Billington
