Failure to connect USB Floppy drive

2009-10-28 Thread Yuri
When I plug in my USB floppy drive I get these messages: ugen1.2: NEC at usbus1 umass0: NEC NEC USB UF000x, class 0/0, rev 1.10/1.50, addr 2 on usbus1 umass0: UFI over CBI with CCI; quirks = 0x umass0:4:0:-1: Attached to scbus4 (da0:umass-sim0:0:0:0): got CAM status 0x4

Re: Failure to connect USB Floppy drive

2009-10-28 Thread Adam Vande More
On Wed, Oct 28, 2009 at 2:08 PM, Yuri y...@rawbw.com wrote: When I plug in my USB floppy drive I get these messages: ugen1.2: NEC at usbus1 umass0: NEC NEC USB UF000x, class 0/0, rev 1.10/1.50, addr 2 on usbus1 umass0: UFI over CBI with CCI; quirks = 0x umass0:4:0:-1: Attached to

Re: Failure to connect USB Floppy drive

2009-10-28 Thread Yuri
Adam Vande More wrote: Did you remove devel/libusb It's installed: libusb-0.1.12_4 I enabled debugging and now get an extended dmesg log: ugen1.2: NEC at usbus1 umass0: NEC NEC USB UF000x, class 0/0, rev 1.10/1.50, addr 2 on usbus1 umass0: UFI over CBI with CCI; quirks = 0x

Re: Failure to connect USB Floppy drive

2009-10-28 Thread Adam Vande More
What does this mean? I remember using the same drive in 7.0 without problems. Yuri -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to

Re: Failure to connect USB Floppy drive

2009-10-28 Thread Yuri
Adam Vande More wrote: What does this mean? I remember using the same drive in 7.0 without problems. It used to work in FreeBSD-70 long time ago. Now in FReeBSD-8.0-RC1 it doesn't. Yuri ___ freebsd-questions@freebsd.org mailing list

Re: Failure to connect USB Floppy drive

2009-10-28 Thread Lowell Gilbert
Yuri y...@rawbw.com writes: Adam Vande More wrote: Did you remove devel/libusb It's installed: libusb-0.1.12_4 That's your problem, then. You need to remove it and rebuild the ports that depended on it. This was mentioned in /usr/ports/UPDATING and /usr/src/UPDATING. -- Lowell Gilbert,

Re: Failure to connect USB Floppy drive

2009-10-28 Thread Yuri
Lowell Gilbert wrote: That's your problem, then. You need to remove it and rebuild the ports that depended on it. This was mentioned in /usr/ports/UPDATING and /usr/src/UPDATING. I removed this port but still have this problem. Yuri ___