From owner-freebsd-questions@FreeBSD.ORG Sun Jun 20 02:46:04 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D32116A4CE for ; Sun, 20 Jun 2004 02:46:04 +0000 (GMT) Received: from mail.iinet.net.au (mail-06.iinet.net.au [203.59.3.38]) by mx1.FreeBSD.org (Postfix) with SMTP id AC1A643D2D for ; Sun, 20 Jun 2004 02:46:02 +0000 (GMT) (envelope-from waulok@bangrocks.com) Received: (qmail 9967 invoked from network); 20 Jun 2004 02:46:01 -0000 Received: from unknown (HELO smeghead.bangrocks.com) (203.173.18.228) by mail.iinet.net.au with SMTP; 20 Jun 2004 02:46:00 -0000 Message-Id: <6.1.0.6.0.20040620124105.01c4e8a0@mail.bangrocks.com> X-Sender: waulok@bangrocks.com@mail.bangrocks.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6 Date: Sun, 20 Jun 2004 12:45:57 +1000 To: Scott Mitchell From: Jason Oakley In-Reply-To: <20040619153131.GA462@tuatara.fishballoon.org> References: <6.1.0.6.0.20040619191803.01dafa20@mail.bangrocks.com> <200406190745.29010.algould@datawok.com> <20040619153131.GA462@tuatara.fishballoon.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: freebsd-questions@freebsd.org Subject: Re: Mounting a multicard reader (FBSD) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jun 2004 02:46:04 -0000 I set up automount, but that's not working. usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered I also get this after a reboot now: umass0: vendor 0x55aa 8-in-2, rev 1.10/1.01, addr 3 umass0: BBB reset failed, TIMEOUT umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED (da0:umass-sim0:0:0:0): got CAM status 0x4 (da0:umass-sim0:0:0:0): fatal error, failed to attach to device (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry I can't mount by hand now. I don't know if that has to do with the automounter: $ sudo mount -t msdos /dev/da0s1 /mnt/CF Just sits there doing nothing. $ sudo truss mount -t msdos /dev/da0s1 /mnt/CF readlink("/etc/malloc.conf",0xbfbff960,63) ERR#2 'No such file or directory' mmap(0x0,4096,0x3,0x1002,-1,0x0) = 671555584 (0x28072000) break(0x807b000) = 0 (0x0) break(0x807c000) = 0 (0x0) lstat("/mnt",0xbfbfee30) = 0 (0x0) lstat("/mnt/CF",0xbfbfee30) = 0 (0x0) readlink("/mnt/CF","/host/localhost/CF",1023) = 18 (0x12) lstat("/host",0xbfbfee30) = 0 (0x0) lstat("/host/localhost",0xbfbfee30) = 0 (0x0) stalls there More of the same: umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED nfs server pid110@spooty:/host: not responding umass0: BBB reset failed, STALLED umass0: BBB bulk-in clear stall failed, STALLED umass0: BBB bulk-out clear stall failed, STALLED At 01:31 AM 20/06/2004, Scott Mitchell wrote: >What does 'camcontrol devlist' say? Probably it will just list one device >(da0) that - as you've found - corresponds with the CF slot on your card >reader. The other slots are probably mapped to other LUNs (Logical Unit >Numbers) on the same SCSI device number. The CAM framework only probes LUN >0 by default, so you only see the first slot. For example, when my machine >boots, I have: --------------------------------------------------------------------------------- http://www.bangrocks.com/ - http://www.auspug.org/ http://www.ZigZagSoft.com/ - PalmOS Software and "Palm Games Programming" forum