Date: Sun, 25 Dec 2005 10:50:09 +0100 From: Niklas Nielsen <niklas.nielsen@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: umass detected, but da is never created Message-ID: <87e39e8b0512250150w3cc50036ucfa0b4d7efd66e44@mail.gmail.com> In-Reply-To: <43ADD649.1030006@netspace.net.au> References: <200512241148.11674.plcplc@gmail.com> <43ADD649.1030006@netspace.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
I have an iPod shuffle and expirences the same problem - no cabling is envolved, its a kind of USB stick. And I know that the iPod worked in 5.4, so I highly doubt hardware issues. And to Philip - I'll give a beer at the local pub if you post a patch ;) Best regards Niklas Nielsen On 12/25/05, Rowdy <rowdy@netspace.net.au> wrote: > Philip Lykke Carlsen wrote: > > I have this external harddisk kit, and when I plug it in, the system > > correctly recognizes it as a umass.. but afterwards, the da device is > > never created.. > > > > this is what I get from the console: > > > > umass0: vendor 0x05e3 USB TO IDE, rev 2.00/0.33, addr 2 umass0: BBB > > reset failed, TIMEOUT umass0: BBB bulk-in clear stall failed, TIMEOUT > > > > > > Also, the very same thing but the timeouts are happening if I connect > > an Apple iPod.. > > > > And for the record, I had this problem with both the generic and my > > custom kernel.. both with umass,da,ses,pass compiled in.. > > > > Any ideas as for how to solve this? Any guidelines and I'd gladly > > edit the files in question and submit a patch, when I get it > > working.. > > > > PS, Any other usb-drive I've tried has worked without problems.. > > Greetings, > > I have an external USB enclosure into which I can plug either of two IDE > hard drives, each in a separate caddy. One works perfectly, the other > produces something very similar to the above error fairly consistently, > and triggers reboots of the FreeBSD (5.3) box when the enclosure is > plugged in or out with the 'broken' caddy inserted. > > After some experimentation and close examination, it appears that the > cable inside the 'broken' caddy may have been slightly damaged. > Manipulating the cable (squashing it down into the caddy so the sliding > caddy lid does not scrape against it) appears to go some way towards > solving the problem. > > So in my case I would say that it was a hardware (cabling) problem > within the caddy, and thus within the USB enclosure. > > Other USB devices, including the second caddy and a couple of flash > drives, seem to work fine. > > Rowdy > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87e39e8b0512250150w3cc50036ucfa0b4d7efd66e44>