From owner-freebsd-current@FreeBSD.ORG  Thu Oct 15 19:57:49 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 064B9106566B
	for <current@freebsd.org>; Thu, 15 Oct 2009 19:57:49 +0000 (UTC)
	(envelope-from wblock@wonkity.com)
Received: from wonkity.com (wonkity.com [67.158.26.137])
	by mx1.freebsd.org (Postfix) with ESMTP id BBB0E8FC1D
	for <current@freebsd.org>; Thu, 15 Oct 2009 19:57:48 +0000 (UTC)
Received: from wonkity.com (localhost [127.0.0.1])
	by wonkity.com (8.14.3/8.14.3) with ESMTP id n9FJvjgg079101;
	Thu, 15 Oct 2009 13:57:45 -0600 (MDT)
	(envelope-from wblock@wonkity.com)
Received: from localhost (wblock@localhost)
	by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id n9FJvjVU079098;
	Thu, 15 Oct 2009 13:57:45 -0600 (MDT)
	(envelope-from wblock@wonkity.com)
Date: Thu, 15 Oct 2009 13:57:45 -0600 (MDT)
From: Warren Block <wblock@wonkity.com>
To: Kevin Oberman <oberman@es.net>
In-Reply-To: <20091015043422.6B42D1CC37@ptavv.es.net>
Message-ID: <alpine.BSF.2.00.0910151335530.78975@wonkity.com>
References: <20091015043422.6B42D1CC37@ptavv.es.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2
	(wonkity.com [127.0.0.1]); Thu, 15 Oct 2009 13:57:45 -0600 (MDT)
Cc: current@freebsd.org
Subject: Re: Why does hal think my USB devices are fixed? 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2009 19:57:49 -0000

On Wed, 14 Oct 2009, Kevin Oberman wrote:
>> Date: Wed, 14 Oct 2009 14:38:47 -0600 (MDT)
>> From: Warren Block <wblock@wonkity.com>
>> Then set some options for the card reader:
>>
>> 20-check-media.fdi :
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <deviceinfo version="0.2">
>>    <device>
>>      <!-- check for media changes in card reader -->
>>      <match key="freebsd.driver" string="da">
>>        <merge key="storage.media_check_enabled" type="bool">true</merge>
>>        <merge key="storage.hotpluggable"        type="bool">true</merge>
>>      </match>
>>    </device>
>> </deviceinfo>

My extraneous line removed from the XML above...

>> hal still sometimes doesn't notice new cards being connected, and the
>> card reader's USB cable has to be reconnected.  But at this point, it's
>> at least as good as it was under 7-STABLE.
>
> Doing something to access the device seems to cause it to be "noticed".
> I use 'fsck -p' on the device, but I suspect dd(1) or most anything else
> that touches the device will do it.

This Sandisk reader appears as two devices.  The CompactFlash slot is 
one device (da0) and the SD/MMC/MS/clock radio slot is another (da1). 
Using the alternate slot seems to be when it loses track.  For example, 
use an MMC card (da1s1), works fine.  Load a CF, and /dev still only has 
da0, da1, and da1s1.  No da1s1 appears.  fsck -p /dev/da0 gives 'fsck: 
Could not determine filesystem type', and various other attempts like 
'true > /dev/da0' don't wake it up.

But 'usbconfig -u 3 -a 3 reset' works every time, and is less messy than 
pulling the cable.

-Warren Block * Rapid City, South Dakota USA