Re: Connecting a USB Zip drive -- whatever am I doing wrong?
epilogue <[EMAIL PROTECTED]> wrote: >### uname -a >FreeBSD 4.10-RELEASE-p1 i386 > >### relevant lines from kernel >device vpo >device scbus >device da >device umass >device uhci# uhci related entries show up in dmesg >device usb >device ugen Do you have 'device pass'? Just a guess, sorry if it doesn't help. -- John. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Connecting a USB Zip drive -- whatever am I doing wrong?
On Sun, 11 Jul 2004 16:04:10 +0100 John Murphy <[EMAIL PROTECTED]> wrote: > epilogue <[EMAIL PROTECTED]> wrote: > > > >### uname -a > >FreeBSD 4.10-RELEASE-p1 i386 > > > >### relevant lines from kernel > >device vpo > >device scbus > >device da > >device umass > >device uhci# uhci related entries show up in dmesg > >device usb > >device ugen > > Do you have 'device pass'? Just a guess, sorry if it doesn't help. regrettably, this did not do the trick. i see precisely the same behaviour as outlined in my earlier messages. sigh. thanks for your suggestion, john. > -- > John. > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Connecting a USB Zip drive -- whatever am I doing wrong?
On Sunday 04 July 2004 07:28 pm, epilogue wrote: > hello all, > > for many moons now, i'll occasionally dedicate a dark day to getting > my USB Zip drive to work. i've been through the handbook, faq, > relevant man pages, mailing lists and across the colossal > googlesphere collecting bits and pieces, none of which seem to get me > the desired result. i'm obviously missing something. > > i'm writing with the hope that, what i have managed to overlook will > be so obvious and straighforward, some kind reader will take 2 > seconds to point it out, so that i may zip off on my merry way. > > ### uname -a > FreeBSD 4.10-RELEASE-p1 i386 > > ### relevant lines from kernel > device vpo > device scbus > device da > device uhci# uhci related entries show up in dmesg > deviceusb > deviceugen > What about device umass # Disks/Mass storage - Requires scbus and da Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Connecting a USB Zip drive -- whatever am I doing wrong?
On Sun, 4 Jul 2004 20:04:06 -0700 Kent Stewart <[EMAIL PROTECTED]> wrote: > On Sunday 04 July 2004 07:28 pm, epilogue wrote: > > hello all, > > > > for many moons now, i'll occasionally dedicate a dark day to getting > > my USB Zip drive to work. i've been through the handbook, faq, > > relevant man pages, mailing lists and across the colossal > > googlesphere collecting bits and pieces, none of which seem to get me > > the desired result. i'm obviously missing something. > > > > i'm writing with the hope that, what i have managed to overlook will > > be so obvious and straighforward, some kind reader will take 2 > > seconds to point it out, so that i may zip off on my merry way. > > > > ### uname -a > > FreeBSD 4.10-RELEASE-p1 i386 > > > > ### relevant lines from kernel > > device vpo > > device scbus > > device da > > device uhci# uhci related entries show up in dmesg > > device usb > > device ugen > > > What about > device umass # Disks/Mass storage - Requires scbus and da hello kent, it's already in there. sigh. i just missed it, when i pasted all this info together. sorry for the oversight. > Kent > > -- > Kent Stewart > Richland, WA > > http://users.owt.com/kstewart/index.html > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Connecting a USB Zip drive -- whatever am I doing wrong?
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. [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. Hope this helps. Phil. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Connecting a USB Zip drive -- whatever am I doing wrong?
On Mon, 05 Jul 2004 13:36:20 +0200 Phil Schulz <[EMAIL PROTECTED]> 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: 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: 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, 0x2000 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. > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
