From owner-freebsd-questions@FreeBSD.ORG Tue Dec 28 00:26:47 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B8D971065673 for ; Tue, 28 Dec 2010 00:26:47 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) by mx1.freebsd.org (Postfix) with ESMTP id 75A738FC29 for ; Tue, 28 Dec 2010 00:26:47 +0000 (UTC) Received: from r55.edvax.de (port-92-195-37-207.dynamic.qsc.de [92.195.37.207]) by mx02.qsc.de (Postfix) with ESMTP id E6EFC1E34E; Tue, 28 Dec 2010 01:26:45 +0100 (CET) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id oBS0Qjh0003458; Tue, 28 Dec 2010 01:26:45 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Tue, 28 Dec 2010 01:26:44 +0100 From: Polytropon To: Adam Vande More Message-Id: <20101228012644.03ded464.freebsd@edvax.de> In-Reply-To: References: <20101227004708.c2d02d15.freebsd@edvax.de> <20101227013359.434b743d.freebsd@edvax.de> <20101227020125.9ab1a07f.freebsd@edvax.de> Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Questions Subject: Re: SD/CF card reader X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2010 00:26:47 -0000 On Sun, 26 Dec 2010 19:35:20 -0600, Adam Vande More wrote: > My understanding is that USB devices can only respond to information > requests, not broadcast changes so that is why nothing is in dmesg > indicating new media has been inserted. Yes, polling instead of interrupt-driven announcements, this is what I understood, too. I did assume some kind of polling mechanism inside the kernel (or *by* the kernel) that would poll the "drive bays" of the SD/CF card reader to see when they contain media. Still the method of issuing something like # true > /dev/da1 looks wrong - even if it works. It looks like: "And now we are overwriting the whole memory card with... erm... with the truth, but at least we're overwriting it." This just gives me a scary impression. There should be something more "correct", such as resetting some bus via camcontrol or re-reading a structure via usbdevs, but no > access to the whole card. > > GEOM: da1: partition 1 does not start on a track boundary. > > GEOM: da1: partition 1 does not end on a track boundary. > > GEOM: da1: partition 1 does not start on a track boundary. > > GEOM: da1: partition 1 does not end on a track boundary. > > > Yeah I don't know about that. I think it's just a warning but maybe trying > using FreeBSD zero out device, partition(slice) and newfs_msdos it. Those messages seem to be uncritical as I've tried to access various media - without any problems. Those cards work well on my v7 system (where those messages aren't shown). I just continue as if those messages haven't been issued. > dd if=/dev/zero of=/dev/da0 bs=512k count=10 > fdisk -i /dev/da0 > newfs_msdos -F32 /dev/da0s1 But that will remove the content of the cards! :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...