From owner-freebsd-current@freebsd.org  Fri Jan 26 16:42:16 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C8ECEDEE46
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Fri, 26 Jan 2018 16:42:16 +0000 (UTC) (envelope-from ian@freebsd.org)
Received: from pmta2.delivery6.ore.mailhop.org
 (pmta2.delivery6.ore.mailhop.org [54.200.129.228])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D88B97A752
 for <freebsd-current@freebsd.org>; Fri, 26 Jan 2018 16:42:15 +0000 (UTC)
 (envelope-from ian@freebsd.org)
X-MHO-User: d70fa45d-02b7-11e8-b951-f99fef315fd9
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 73.78.92.27
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from ilsoft.org (unknown [73.78.92.27])
 by outbound2.ore.mailhop.org (Halon) with ESMTPSA
 id d70fa45d-02b7-11e8-b951-f99fef315fd9;
 Fri, 26 Jan 2018 16:42:04 +0000 (UTC)
Received: from rev (rev [172.22.42.240])
 by ilsoft.org (8.15.2/8.15.2) with ESMTP id w0QGg7D6013961;
 Fri, 26 Jan 2018 09:42:07 -0700 (MST) (envelope-from ian@freebsd.org)
Message-ID: <1516984927.42536.248.camel@freebsd.org>
Subject: Re: microSDXC can't recognized
From: Ian Lepore <ian@freebsd.org>
To: KIRIYAMA Kazuhiko <kiri@kx.openedu.org>, freebsd-current
 <freebsd-current@freebsd.org>
Date: Fri, 26 Jan 2018 09:42:07 -0700
In-Reply-To: <201801261409.w0QE9hR2085651@kx.openedu.org>
References: <201801260731.w0Q7V842079870@kx.openedu.org>
 <201801261409.w0QE9hR2085651@kx.openedu.org>
Content-Type: text/plain; charset="iso-2022-jp"
X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jan 2018 16:42:16 -0000

On Fri, 2018-01-26 at 23:09 +0900, KIRIYAMA Kazuhiko wrote:
> At Fri, 26 Jan 2018 16:31:08 +0900,
> 私 wrote:
> > 
> > 
> > Hi,
> > 
> > Builtin microSDXC card device can't recognized in may
> > machine[1]. Inserted it but nothing happened. Inserted card
> > is SanDisk SDSQAR-128G-GNMA[2]. But in may another machine,
> > it recognized da0:
> > 
> > [...]
> I've rebooted and then recognized by mmcsd1! dmesg shows:
> 
> mmcsd1: 128GB <SDHC SC128 8.0 SN 13C1CB3A MFG 12/2017 by 3 SD> at
> mmc1 50.0MHz/4bit/65535-block
> WARNING: WITNESS option enabled, expect reduced performance.
> 
> [...]
> 
> I supposed SD card to be a pnp device but this embedded
> micro sd port seems to be eMMC device. Actually it is teated
> same as internal eMMC device as HDD. That is micro SD card
> must not be pull out by umount on running isn't it?

You should be able to insert and remove the sdcard whenever you want,
as long as it has no mounted filesystems. Every time you insert or
remove it, you should see a notification on the console and in dmesg.
If that doesn't happen, then somehow the card-detect logic isn't
working right on your hardware.

-- Ian