Date: Mon, 5 Jul 2004 10:02:35 -0400 From: epilogue <epilogue@allstream.net> To: Phil Schulz <ph.schulz@gmx.de> Cc: freebsd-questions@freebsd.org Subject: Re: Connecting a USB Zip drive -- whatever am I doing wrong? Message-ID: <20040705100235.53637dde@localhost> In-Reply-To: <40E93D34.8020208@gmx.de> References: <20040704222857.5e18dfc7@localhost> <40E93D34.8020208@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 05 Jul 2004 13:36:20 +0200 Phil Schulz <ph.schulz@gmx.de> wrote: > epilogue wrote: > > > > ### relevant lines from kernel > > device vpo > > device scbus > > device da > > device uhci # uhci related entries show up in dmesg > > device usb > > device ugen > > > > Don't forget umass. > Try adding sa. My USB HDD comes up as /dev/sa0. Your ZIP drive might > need sa, too. hello phil, actually, i have 'umass' enabled. i simply missed including it, when i cut and pasted all this together. i added 'sa'. the boot time freeze still occurs, but when i unplug, i see a few new messages in dmesg and /var/log/messages. before sa: <snip> umass0: Iomega USB Zip 100, rev 1.00/1.00, addr 2 umass0: Get Max Lun not supported (STALLED) umass0: BBB reset failed, IOERROR with sa: <snip> umass0: Iomega USB Zip 100, rev 1.00/1.00, addr 2 umass0: Get Max Lun not supported (STALLED) umass0: Invalid CSW: status 4 > 2 (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 > [dmesg snipped] > > [various messages snipped] > > > > > ### /var/log/messages > > Jul 4 21:47:04 /kernel: umass0: Iomega USB Zip 100, rev 1.00/1.00, > > addr 2 Jul 4 21:47:04 /kernel: umass0: Get Max Lun not supported > > (STALLED) Jul 4 21:48:09 /kernel: umass0: BBB reset failed, IOERROR > > > > I guess if you posted these to stable@ you might get more attention. > > > ### mounting > > i'm not sure that i 'get' which device the zip maps to nor how to > > determine this. i have tried about 40 different combinations of mount > > (mostly gleaned from my research), but i have yet to hit upon the right > > command. > > > > # mount -t msdos /dev/da* /mnt # * = practically every single one > > msdos: /dev/da0s4: Device not configured > > > > See above. I think USB mass storage devices require sa to work, > therefore you would need sth like > > mount -t msdos /dev/sa* /mnt <-- Don't know what * should be out of my > head now. # cd /dev; sh MAKEDEV all # just to be sure. # ls -al sa* crw-rw---- 4 root operator 14, 0 Jul 5 09:56 sa0 crw-rw---- 4 root operator 14, 0 Jul 5 09:56 sa0.0 crw-rw---- 2 root operator 14, 4 Jul 5 09:56 sa0.1 crw-rw---- 2 root operator 14, 8 Jul 5 09:56 sa0.2 crw-rw---- 2 root operator 14, 12 Jul 5 09:56 sa0.3 crw-rw---- 2 root wheel 14, 0x20000000 Jul 5 09:56 sa0.ctl # mount -t msdos /dev/sa0.0 /mnt msdos: /dev/sa0.0: Device not configured unfortunately, i'm getting the same error for each of these devices. nevertheless, many thanks for your suggestions. epi > Hope this helps. > > Phil. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040705100235.53637dde>