Transcend JetFlash V85
Hi people. Just recently saw the message on STABLE: MFC r210931: Disable sync cache for the Transcend Jetflash V90. This sounds good since I have the same problem with my JetFlash V85: Aug 19 23:33:55 limbo kernel: (da4:umass-sim1:1:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 Aug 19 23:33:55 limbo kernel: (da4:umass-sim1:1:0:0): CAM status: SCSI Status Error Aug 19 23:33:55 limbo kernel: (da4:umass-sim1:1:0:0): SCSI status: Check Condition Aug 19 23:33:55 limbo kernel: (da4:umass-sim1:1:0:0): SCSI sense: ILLEGAL REQUEST asc:26,0 (Invalid field in parameter list) My flash looks like: ugen3.3: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x058f idProduct = 0x6387 bcdDevice = 0x0100 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 bNumConfigurations = 0x0001 Can someone help me understanding how can I a a quirk for my flash drive? -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: Transcend JetFlash V85
20.08.2010 00:38, Hans Petter Selasky wrote: You can use usbconfig to add quirks on the fly. See: usbconfig -h And: man usbconfig Tried that, but it doesn't work for me or I'm messing things up... usbconfig -d 3.3 add_quirk UQ_MSC_NO_SYNC_CACHE And errors continue to show up. The man page also is kinda short on data. -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: Transcend JetFlash V85
21.08.2010 21:29, Hans Petter Selasky wrote: You can use usbconfig to add quirks on the fly. See: usbconfig -h And: man usbconfig Tried that, but it doesn't work for me or I'm messing things up... usbconfig -d 3.3 add_quirk UQ_MSC_NO_SYNC_CACHE And errors continue to show up. The man page also is kinda short on data. After setting the quirk, you need to reset or re-attach the USB device. Not a good behavior for me. What if I need to boot from one? Most FS don't like been pushed off device. But this doesn't work too. usbconfig -d 3.3 add_quirk UQ_MSC_NO_TEST_UNIT_READY usbconfig -d 3.3 reset Gives me: Aug 21 22:46:14 limbo kernel: umass1: at uhub3, port 5, addr 3 (disconnected) Aug 21 22:46:14 limbo kernel: (da4:umass-sim1:1:0:0): lost device Aug 21 22:46:14 limbo kernel: (da4:umass-sim1:1:0:0): removing device entry Aug 21 22:46:15 limbo root: Unknown USB device: vendor 0x058f product 0x6387 bus uhub3 Aug 21 22:46:15 limbo kernel: umass1: class 0/0, rev 2.00/1.00, addr 3> on usbus3 Aug 21 22:46:15 limbo kernel: umass1: SCSI over Bulk-Only; quirks = 0x0100 Here, quirks field doesn't change when I add more quirks. Aug 21 22:46:16 limbo kernel: umass1:2:1:-1: Attached to scbus2 Aug 21 22:46:16 limbo kernel: (probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Aug 21 22:46:16 limbo kernel: (probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error Aug 21 22:46:16 limbo kernel: (probe0:umass-sim1:1:0:0): SCSI status: Check Condition Aug 21 22:46:16 limbo kernel: (probe0:umass-sim1:1:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have changed) Aug 21 22:46:16 limbo kernel: da4 at umass-sim1 bus 1 scbus2 target 0 lun 0 Aug 21 22:46:16 limbo kernel: da4: Removable Direct Access SCSI-2 device Aug 21 22:46:16 limbo kernel: da4: 40.000MB/s transfers Aug 21 22:46:16 limbo kernel: da4: 3900MB (7987200 512 byte sectors: 255H 63S/T 497C) Aug 21 22:46:24 limbo kernel: (da4:umass-sim1:1:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 Aug 21 22:46:24 limbo kernel: (da4:umass-sim1:1:0:0): CAM status: SCSI Status Error Aug 21 22:46:24 limbo kernel: (da4:umass-sim1:1:0:0): SCSI status: Check Condition Aug 21 22:46:24 limbo kernel: (da4:umass-sim1:1:0:0): SCSI sense: ILLEGAL REQUEST asc:26,0 (Invalid field in parameter list) Mentioned patch was looking like: USB_QUIRK(ALCOR, TRANSCEND, 0x0142, 0x0142, UQ_MSC_FORCE_WIRE_BBB, UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN, UQ_MSC_NO_SYNC_CACHE), But I don't understand what should be set for my flash at 3-4 places... They are covering some range but inspecting my flash I don't see something close to the 0x142. -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
software atmel arm serial USB
Hi people. Our technical staff are working with some device that can do serial over USB but they have no controller. This devices implements USB in software (at least they told me so) at atmel arm. usbconfig -d x.x dump_device_desc gives me: ugen4.2: at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x00ef bDeviceSubClass = 0x0002 bDeviceProtocol = 0x0001 bMaxPacketSize0 = 0x0040 idVendor = 0x idProduct = 0x0017 bcdDevice = 0x iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 <023> bNumConfigurations = 0x0001 I have pointed them on idVendor field but they think this value is ok for custom devices. In windows they are using usbser.sys to get access to the device. What can be done one FreeBSD? Can I specify which device driver should be used with this physical device? -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: ranscend JetFlash V85
23.08.2010 22:39, Mykola Dzham wrote: This is bcdDevice range. So, change first 0x0142 to 0x100 for your flash drive or add another quirk (before quirk for all TRANSCEND's) with 3-4 places set to 0x100. Yes, that was the key. I'll file a pr for that. -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
usb/149934: Transcend JetFlash V85 poor performance
>Number: 149934 >Category: usb >Synopsis: Transcend JetFlash V85 poor performance >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Tue Aug 24 11:40:02 UTC 2010 >Closed-Date: >Last-Modified: >Originator: Volodymyr Kostyrko >Release:RELENG_8 >Organization: >Environment: FreeBSD limbo.lan 8.1-STABLE FreeBSD 8.1-STABLE #0 r211717M: Tue Aug 24 12:56:24 EEST 2010 arc...@limbo.lan:/usr/obj/usr/src/sys/MINIMAL_8 i386 >Description: When attaching device kernel reports this: Aug 21 22:46:15 limbo root: Unknown USB device: vendor 0x058f product 0x6387 bus uhub3 Aug 21 22:46:15 limbo kernel: umass1: on usbus3 Aug 21 22:46:15 limbo kernel: umass1: SCSI over Bulk-Only; quirks = 0x0100 Aug 21 22:46:16 limbo kernel: umass1:2:1:-1: Attached to scbus2 Aug 21 22:46:16 limbo kernel: (probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Aug 21 22:46:16 limbo kernel: (probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error Aug 21 22:46:16 limbo kernel: (probe0:umass-sim1:1:0:0): SCSI status: Check Condition Aug 21 22:46:16 limbo kernel: (probe0:umass-sim1:1:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have changed) Aug 21 22:46:16 limbo kernel: da4 at umass-sim1 bus 1 scbus2 target 0 lun 0 Aug 21 22:46:16 limbo kernel: da4: Removable Direct Access SCSI-2 device Aug 21 22:46:16 limbo kernel: da4: 40.000MB/s transfers Aug 21 22:46:16 limbo kernel: da4: 3900MB (7987200 512 byte sectors: 255H 63S/T 497C) Aug 21 22:46:24 limbo kernel: (da4:umass-sim1:1:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 Aug 21 22:46:24 limbo kernel: (da4:umass-sim1:1:0:0): CAM status: SCSI Status Error Aug 21 22:46:24 limbo kernel: (da4:umass-sim1:1:0:0): SCSI status: Check Condition Aug 21 22:46:24 limbo kernel: (da4:umass-sim1:1:0:0): SCSI sense: ILLEGAL REQUEST asc:26,0 (Invalid field in parameter list) After that any time SYNCHRONIZE CACHE command is issued writing to device stops for some time and kernel reports bad command. >How-To-Repeat: Attaching the device and trying to work with it should suffice. >Fix: Apply the following patch. Patch attached with submission follows: Index: sys/dev/usb/quirk/usb_quirk.c === --- sys/dev/usb/quirk/usb_quirk.c (revision 211717) +++ sys/dev/usb/quirk/usb_quirk.c (working copy) @@ -159,6 +159,9 @@ USB_QUIRK(ALCOR, AU6390, 0x, 0x, UQ_MSC_NO_SYNC_CACHE), USB_QUIRK(ALCOR, UMCR_9361, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN), + USB_QUIRK(ALCOR, TRANSCEND, 0x0100, 0x0100, UQ_MSC_FORCE_WIRE_BBB, + UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN, UQ_MSC_NO_SYNC_CACHE, + UQ_MSC_NO_TEST_UNIT_READY), USB_QUIRK(ALCOR, TRANSCEND, 0x0142, 0x0142, UQ_MSC_FORCE_WIRE_BBB, UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN, UQ_MSC_NO_SYNC_CACHE), USB_QUIRK(ALCOR, TRANSCEND, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/149934: Transcend JetFlash V85 poor performance
24.08.2010 18:11, Hans Petter Selasky wrote: Can you test this patch instead: --- sys/dev/usb/quirk/usb_quirk.c 2010-08-10 16:03:19.0 +++ sys/dev/usb/quirk/usb_quirk.c 2010-08-10 16:03:19.0 @@ -160,10 +160,8 @@ USB_QUIRK(ALCOR, AU6390, 0x, 0x, UQ_MSC_NO_SYNC_CACHE), USB_QUIRK(ALCOR, UMCR_9361, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN), - USB_QUIRK(ALCOR, TRANSCEND, 0x0142, 0x0142, UQ_MSC_FORCE_WIRE_BBB, - UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN, UQ_MSC_NO_SYNC_CACHE), - USB_QUIRK(ALCOR, TRANSCEND, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, - UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN), + USB_QUIRK(ALCOR, TRANSCEND, 0x, 0x, UQ_MSC_NO_GETMAXLUN, + UQ_MSC_NO_SYNC_CACHE), USB_QUIRK(APACER, HT202, 0x, 0x, UQ_MSC_NO_TEST_UNIT_READY, UQ_MSC_NO_SYNC_CACHE), USB_QUIRK(ASAHIOPTICAL, OPTIO230, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, Please also dump device and configuration descriptor using usbconfig. --HPS This one results in: Aug 25 00:10:17 limbo root: Unknown USB device: vendor 0x058f product 0x6387 bus uhub3 Aug 25 00:10:17 limbo kernel: ugen3.3: at usbus3 Aug 25 00:10:17 limbo kernel: umass1: class 0/0, rev 2.00/1.00, addr 3> on usbus3 Aug 25 00:10:17 limbo kernel: umass1: SCSI over Bulk-Only; quirks = 0x4100 Aug 25 00:10:18 limbo kernel: umass1:2:1:-1: Attached to scbus2 Aug 25 00:10:18 limbo kernel: (probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Aug 25 00:10:18 limbo kernel: (probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error Aug 25 00:10:18 limbo kernel: (probe0:umass-sim1:1:0:0): SCSI status: Check Condition Aug 25 00:10:18 limbo kernel: (probe0:umass-sim1:1:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have changed) Aug 25 00:10:18 limbo kernel: da4 at umass-sim1 bus 1 scbus2 target 0 lun 0 Aug 25 00:10:18 limbo kernel: da4: Removable Direct Access SCSI-2 device Aug 25 00:10:18 limbo kernel: da4: 40.000MB/s transfers Aug 25 00:10:18 limbo kernel: da4: 3900MB (7987200 512 byte sectors: 255H 63S/T 497C) So how about UQ_MSC_NO_TEST_UNIT_READY? # usbconfig -d 3.3 dump_device_desc ugen3.3: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x058f idProduct = 0x6387 bcdDevice = 0x0100 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 bNumConfigurations = 0x0001 # usbconfig -d 3.3 dump_all_config_desc ugen3.3: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0020 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x bmAttributes = 0x0080 bMaxPower = 0x0032 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x0008 bInterfaceSubClass = 0x0006 bInterfaceProtocol = 0x0050 iInterface = 0x Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0001 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0082 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x bRefresh = 0x bSynchAddress = 0x -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/149934: Transcend JetFlash V85 poor performance
25.08.2010 00:27, Hans Petter Selasky wrote: I've committed my updated patch to USB P4. See change #182862. Please verify that your drive is still working with the new patch. Yes, i've tested my drive exactly with this patch. Say, how about UQ_MSC_NO_TEST_UNIT_READY? You have omitted it on purpose so maybe this one should be added only if without one the device would not work at all? -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/149934: Transcend JetFlash V85 poor performance
The following reply was made to PR usb/149934; it has been noted by GNATS. From: Volodymyr Kostyrko To: Hans Petter Selasky Cc: freebsd-usb@freebsd.org, freebsd-gnats-sub...@freebsd.org Subject: Re: usb/149934: Transcend JetFlash V85 poor performance Date: Wed, 25 Aug 2010 00:43:05 +0300 25.08.2010 00:27, Hans Petter Selasky wrote: > I've committed my updated patch to USB P4. See change #182862. > > Please verify that your drive is still working with the new patch. Yes, i've tested my drive exactly with this patch. Say, how about UQ_MSC_NO_TEST_UNIT_READY? You have omitted it on purpose so maybe this one should be added only if without one the device would not work at all? -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/149934: Transcend JetFlash V85 poor performance
The following reply was made to PR usb/149934; it has been noted by GNATS. From: Volodymyr Kostyrko To: Hans Petter Selasky Cc: freebsd-usb@freebsd.org, freebsd-gnats-sub...@freebsd.org Subject: Re: usb/149934: Transcend JetFlash V85 poor performance Date: Wed, 25 Aug 2010 00:17:25 +0300 24.08.2010 18:11, Hans Petter Selasky wrote: > Can you test this patch instead: > > --- sys/dev/usb/quirk/usb_quirk.c 2010-08-10 16:03:19.0 > +++ sys/dev/usb/quirk/usb_quirk.c 2010-08-10 16:03:19.0 > @@ -160,10 +160,8 @@ > USB_QUIRK(ALCOR, AU6390, 0x, 0x, UQ_MSC_NO_SYNC_CACHE), > USB_QUIRK(ALCOR, UMCR_9361, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, > UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN), > - USB_QUIRK(ALCOR, TRANSCEND, 0x0142, 0x0142, UQ_MSC_FORCE_WIRE_BBB, > - UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN, > UQ_MSC_NO_SYNC_CACHE), > - USB_QUIRK(ALCOR, TRANSCEND, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, > - UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN), > + USB_QUIRK(ALCOR, TRANSCEND, 0x, 0x, UQ_MSC_NO_GETMAXLUN, > + UQ_MSC_NO_SYNC_CACHE), > USB_QUIRK(APACER, HT202, 0x, 0x, UQ_MSC_NO_TEST_UNIT_READY, > UQ_MSC_NO_SYNC_CACHE), > USB_QUIRK(ASAHIOPTICAL, OPTIO230, 0x, 0x, > UQ_MSC_FORCE_WIRE_BBB, > > Please also dump device and configuration descriptor using usbconfig. > > --HPS This one results in: Aug 25 00:10:17 limbo root: Unknown USB device: vendor 0x058f product 0x6387 bus uhub3 Aug 25 00:10:17 limbo kernel: ugen3.3: at usbus3 Aug 25 00:10:17 limbo kernel: umass1: on usbus3 Aug 25 00:10:17 limbo kernel: umass1: SCSI over Bulk-Only; quirks = 0x4100 Aug 25 00:10:18 limbo kernel: umass1:2:1:-1: Attached to scbus2 Aug 25 00:10:18 limbo kernel: (probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Aug 25 00:10:18 limbo kernel: (probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error Aug 25 00:10:18 limbo kernel: (probe0:umass-sim1:1:0:0): SCSI status: Check Condition Aug 25 00:10:18 limbo kernel: (probe0:umass-sim1:1:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have changed) Aug 25 00:10:18 limbo kernel: da4 at umass-sim1 bus 1 scbus2 target 0 lun 0 Aug 25 00:10:18 limbo kernel: da4: Removable Direct Access SCSI-2 device Aug 25 00:10:18 limbo kernel: da4: 40.000MB/s transfers Aug 25 00:10:18 limbo kernel: da4: 3900MB (7987200 512 byte sectors: 255H 63S/T 497C) So how about UQ_MSC_NO_TEST_UNIT_READY? # usbconfig -d 3.3 dump_device_desc ugen3.3: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x058f idProduct = 0x6387 bcdDevice = 0x0100 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 bNumConfigurations = 0x0001 # usbconfig -d 3.3 dump_all_config_desc ugen3.3: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0020 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x bmAttributes = 0x0080 bMaxPower = 0x0032 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x0008 bInterfaceSubClass = 0x0006 bInterfaceProtocol = 0x0050 iInterface = 0x Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0001 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0082 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x bRefresh = 0x bSynchAddress = 0x -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
problem with bluetooth dongle
I have something like: Feb 20 02:43:16 limbo kernel: ugen2.3: at usbus2 Feb 20 02:43:16 limbo kernel: uhub4: 1.10/1.00, addr 3> on usbus2 Feb 20 02:43:16 limbo kernel: uhub4: 3 ports with 0 removable, bus powered Feb 20 02:43:17 limbo kernel: ugen2.4: at usbus2 Feb 20 02:43:17 limbo kernel: ubt0: 224/1, rev 1.10/1.01, addr 4> on usbus2 Feb 20 02:43:17 limbo root: Unknown USB device: vendor 0x0a12 product 0x0001 bus uhub4 Feb 20 02:43:18 limbo root: Unknown USB device: vendor 0x0a5c product 0x3502 bus uhub4 Feb 20 02:43:18 limbo kernel: ugen2.5: at usbus2 Feb 20 02:43:18 limbo kernel: ugen2.6: at usbus2 Feb 20 02:43:18 limbo kernel: ums1: 1.10/1.00, addr 6> on usbus2 Feb 20 02:43:18 limbo kernel: ums1: 3 buttons and [XY] coordinates ID=0 And it almost works. I can register devices with it, but I can't do anything more. Any phone connected shows that this device doesn't provide any services despite sdpd is running. -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: problem with bluetooth dongle
20.02.2011 11:31, Hans Petter Selasky wrote: On Sunday 20 February 2011 01:47:33 Volodymyr Kostyrko wrote: I have something like: Feb 20 02:43:16 limbo kernel: ugen2.3: at usbus2 Feb 20 02:43:16 limbo kernel: uhub4: on usbus2 Feb 20 02:43:16 limbo kernel: uhub4: 3 ports with 0 removable, bus powered Feb 20 02:43:17 limbo kernel: ugen2.4: at usbus2 Feb 20 02:43:17 limbo kernel: ubt0: on usbus2 Feb 20 02:43:17 limbo root: Unknown USB device: vendor 0x0a12 product 0x0001 bus uhub4 Feb 20 02:43:18 limbo root: Unknown USB device: vendor 0x0a5c product 0x3502 bus uhub4 Feb 20 02:43:18 limbo kernel: ugen2.5: at usbus2 Feb 20 02:43:18 limbo kernel: ugen2.6: at usbus2 Feb 20 02:43:18 limbo kernel: ums1: on usbus2 Feb 20 02:43:18 limbo kernel: ums1: 3 buttons and [XY] coordinates ID=0 And it almost works. I can register devices with it, but I can't do anything more. Any phone connected shows that this device doesn't provide any services despite sdpd is running. How did you start the bluetooth daemons? Did you load the required netgraph modules? 1. kldload ng_ubt 2. insert dongle (above output in /var/log/messages) 3. /etc/rc.d/bluetooth start ubt0 /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 (and there's no /dev/ubt0 also) 4. service hcsecd onestart 5. service sdpd onestart After that I can use hccontrol inquiry command, I can configure hcsecd and add this dongle to the list of 'My devices' in my phone. Requesting list of services gives nothing. -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: problem with bluetooth dongle
20.02.2011 13:25, Hans Petter Selasky wrote: On Sunday 20 February 2011 12:01:19 Volodymyr Kostyrko wrote: 3. /etc/rc.d/bluetooth start ubt0 /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 You need to run this twice: 3. /etc/rc.d/bluetooth start ubt0 /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 It just gives no output for the second time. Still nothing though. I'll try to retest this device under Windows somewhere. Maybe I'm trying to chase bugs in broken hardware... -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: problem with bluetooth dongle
20.02.2011 14:06, Volodymyr Kostyrko wrote: 20.02.2011 13:25, Hans Petter Selasky wrote: On Sunday 20 February 2011 12:01:19 Volodymyr Kostyrko wrote: 3. /etc/rc.d/bluetooth start ubt0 /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 You need to run this twice: 3. /etc/rc.d/bluetooth start ubt0 /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 It just gives no output for the second time. Still nothing though. I'll try to retest this device under Windows somewhere. Maybe I'm trying to chase bugs in broken hardware... Same problem under Windows 7. I'll try to retest under WinXP somewhere. Device seem to be very old... -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: problem with bluetooth dongle
20.02.2011 22:04, Gary Palmer wrote: On Sun, Feb 20, 2011 at 01:01:19PM +0200, Volodymyr Kostyrko wrote: Normally there isn't a /dev node for ubt0 (although I'm not sure what version of FreeBSD you're running) as its hooked through netgraph - try running "ngctl list" as root and see if there is a ubt0 node there. I'm on stable: FreeBSD limbo.lan 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #0 r218849: Sat Feb 19 17:18:15 EET 2011 arc...@limbo.lan:/usr/obj/usr/src/sys/MINIMAL_8 i386 Thank you, it's really hooked via netgraph. -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/163328: Hardware
The following reply was made to PR usb/163328; it has been noted by GNATS. From: Volodymyr Kostyrko To: Andrei Cc: freebsd-gnats-sub...@freebsd.org Subject: Re: usb/163328: Hardware Date: Fri, 16 Dec 2011 11:03:05 +0200 16.12.2011 08:11, Andrei wrote: > не Ð¼Ð¾Ð³Ñ Ð¿Ð¾Ð´ÐºÐ»ÑÑиÑÑ TP-LINK 300Mbps Wireless N USB Adapter > TL-WN821N Ð½ÐµÑ Ð´ÑайвеÑов, а во freeBSD данное > обоÑÑдование не поддеÑживаеÑÑÑ. ÐÑÐµÐ½Ñ > Ñ Ð¾ÑелоÑÑ Ð±Ñ Ð¿Ð¾Ð´ÐºÐ»ÑÑиÑÑ Ð´Ð°Ð½Ð½Ñй девайÑ, > поÑÐ¾Ð¼Ñ ÑÑо вÑе ÑоÑеди Ñ Ð¾Ð´ÑÑ Ð² инÑеÑÐ½ÐµÑ > ÑеÑез Ð¼ÐµÐ½Ñ (него)! I'll translate that to English for a start. = I can't connect TP-LINK 300Mbps Wireless N USB Adapter TL-WN821N no drivers, and under FreeBSD this equipment is not supported. I'd love to connect this device, because all the neighbors use this for Internet access! === Now back to the point. Theoretically this should be rum, run, uath, upgt, ural, urtw or zyd. Can you at least post part of log where device attaches? usbconfig dump_device_desc? -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/149934: Transcend JetFlash V85 poor performance
The following reply was made to PR usb/149934; it has been noted by GNATS. From: Volodymyr Kostyrko To: bug-follo...@freebsd.org, freebsd-usb@FreeBSD.org Cc: Subject: Re: usb/149934: Transcend JetFlash V85 poor performance Date: Fri, 30 Dec 2011 15:50:06 +0200 I think this one is MFC'ed into RELENG_8 long time ago. Can we close the PR? -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/149934: Transcend JetFlash V85 poor performance
I think this one is MFC'ed into RELENG_8 long time ago. Can we close the PR? -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
uath fails attaching device
Hello. I just got myself a small plaything for a limited amount of time: Jan 19 15:18:44 faz kernel: Trying to mount root from zfs:faz0 []... Jan 19 15:18:44 faz kernel: uath0: rev 2.00/0.01, addr 2> on usbus6 Jan 19 15:18:44 faz kernel: uath0: uath_cmdeof: invalid WDC msg length 512; msg ignored Jan 19 15:18:45 faz kernel: uath0: timeout waiting for reply to cmd 0x1 (1) Jan 19 15:18:45 faz kernel: uath0: could not initialize adapter Jan 19 15:18:45 faz kernel: device_attach: uath0 attach returned 35 Jan 19 15:18:45 faz kernel: uath0: rev 2.00/0.01, addr 2> on usbus6 Jan 19 15:18:45 faz kernel: uath0: uath_cmdeof: invalid WDC msg length 512; msg ignored Jan 19 15:18:47 faz kernel: WARNING: attempt to domain_add(netgraph) after domainfinalize() Jan 19 15:18:47 faz kernel: uath0: timeout waiting for reply to cmd 0x1 (1) Jan 19 15:18:47 faz kernel: uath0: could not initialize adapter Jan 19 15:18:47 faz kernel: device_attach: uath0 attach returned 35 ugen6.2: at usbus6, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x00ff bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x0cf3 idProduct = 0x0001 bcdDevice = 0x0001 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 <1.0> bNumConfigurations = 0x0001 Device seem to configure properly when reconnected and seem to fail again after time passes. -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: uath fails attaching device
Volodymyr Kostyrko wrote: I just got myself a small plaything for a limited amount of time: And here how it fails: Jan 19 16:30:48 faz kernel: uath0: uath_cmdsend: empty inactive queue Jan 19 16:30:48 faz kernel: uath0: could not flush pipes, error 55 Jan 19 16:30:48 faz kernel: uath0: uath_cmdsend: empty inactive queue Jan 19 16:30:48 faz kernel: uath0: could not reset Tx queues, error 55 Jan 19 16:30:48 faz kernel: uath0: uath_cmdsend: empty inactive queue Jan 19 16:30:48 faz kernel: uath0: could not reset Tx queues, error 55 Jan 19 16:30:49 faz kernel: uath0: uath_cmdsend: empty inactive queue Jan 19 16:30:49 faz kernel: uath0: could not reset Tx queues, error 55 Jan 19 16:30:49 faz kernel: uath0: uath_cmdsend: empty inactive queue Jan 19 16:30:49 faz kernel: uath0: could not reset Tx queues, error 55 Jan 19 16:30:49 faz kernel: uath0: uath_cmdsend: empty inactive queue Jan 19 16:30:49 faz kernel: uath0: could not reset Tx queues, error 55 Jan 19 16:30:49 faz kernel: uath0: uath_cmdsend: empty inactive queue Jan 19 16:30:49 faz kernel: uath0: could not reset Tx queues, error 55 Jan 19 16:30:50 faz kernel: uath0: uath_cmdsend: empty inactive queue Jan 19 16:30:50 faz kernel: uath0: could not set channel, error 55 Jan 19 16:30:50 faz kernel: uath0: uath_cmdsend: empty inactive queue Jan 19 16:30:50 faz kernel: uath0: could not set channel, error 55 Jan 19 16:30:50 faz kernel: uath0: uath_cmdsend: empty inactive queue Jan 19 16:30:50 faz kernel: uath0: could not set channel, error 55 Jan 19 16:30:50 faz kernel: uath0: uath_cmdsend: empty inactive queue Jan 19 16:30:50 faz kernel: uath0: could not set channel, error 55 Jan 19 16:30:50 faz kernel: uath0: uath_cmdsend: empty inactive queue Jan 19 16:30:50 faz kernel: uath0: could not set channel, error 55 Jan 19 16:30:51 faz kernel: uath0: uath_cmdsend: empty inactive queue Jan 19 16:30:51 faz kernel: uath0: could not set channel, error 55 Jan 19 16:30:51 faz kernel: uath0: uath_cmdsend: empty inactive queue Jan 19 16:30:51 faz kernel: uath0: could not set channel, error 55 Jan 19 16:30:51 faz kernel: uath0: uath_cmdsend: empty inactive queue Jan 19 16:30:51 faz kernel: uath0: could not set channel, error 55 Jan 19 16:30:51 faz kernel: uath0: at uhub6, port 2, addr 2 (disconnected) Jan 19 16:30:51 faz kernel: uath0: uath_cmdsend: empty inactive queue Jan 19 16:30:51 faz last message repeated 2 times Jan 19 16:30:53 faz kernel: usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored) Jan 19 16:30:55 faz kernel: uath0: rev 2.00/0.01, addr 2> on usbus6 Jan 19 16:30:55 faz kernel: uath0: uath_cmdeof: invalid WDC msg length 512; msg ignored Jan 19 16:30:57 faz kernel: uath0: timeout waiting for reply to cmd 0x1 (1) Jan 19 16:30:57 faz kernel: uath0: could not initialize adapter Jan 19 16:30:57 faz kernel: device_attach: uath0 attach returned 35 -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
USB devices not autodetecting anymore on stable
Hi all. Maybe I just blow out my installation again but I have two machines on 9_STABLE that for one week refuse to autoload usb device drivers. Before that my Keyboard and mice start automatically. But right now I must explicitly load kernel module for each device. -- Sphinx of black quartz, judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
run(4) needs clarification
Hi all. As per man page run driver supports DWA-140, but I currently obtained one piece that identifies as: # usbconfig -d 0.2 dump_device_desc ugen0.2: <11n Adapter D-Link> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x2001 idProduct = 0x3c15 bcdDevice = 0x0101 iManufacturer = 0x0001 iProduct = 0x0002 <11n Adapter> iSerialNumber = 0x0003 <1.0> bNumConfigurations = 0x0001 After patching kernel to make it detectable I got this: Dec 3 17:15:17 ar1l0u kernel: run0: 2.00/1.01, addr 2> on usbus0 Dec 3 17:15:17 ar1l0u kernel: run0: MAC/BBP RT5392 (rev 0x0222), RF unknown (MIMO 2T2R), address 84:c9:b2:82:8f:ba And chip RT5392 is not supported yet. This one is: H/W Ver.: B3 F/W Ver.: 2.00 Can anyone update man page to explicitly state that only ver. A* is supposed to work? -- Sphinx of black quartz, judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: USB devices not autodetecting anymore on stable
03.12.2012 20:09, Hans Petter Selasky: On Monday 03 December 2012 16:14:56 Volodymyr Kostyrko wrote: Hi all. Maybe I just blow out my installation again but I have two machines on 9_STABLE that for one week refuse to autoload usb device drivers. Before that my Keyboard and mice start automatically. But right now I must explicitly load kernel module for each device. There has been some changes in /etc/ . Make sure you did a mergemaster and that devd is running. I'm missing your point here. Which changes in etc? # svn info Path: . Working Copy Root Path: /usr/src URL: http://svn.freebsd.org/base/stable/9/etc Repository Root: http://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 243808 Node Kind: directory Schedule: normal Last Changed Author: eadler Last Changed Rev: 243757 Last Changed Date: 2012-12-01 18:44:33 +0200 (сб, 01 гру 2012) # find . -mtime -31d . ./rc.subr ./pccard_ether ./disktab ./rc.d ./rc.d/jail ./gettytab ./root ./root/dot.cshrc ./root/dot.login -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: USB devices not autodetecting anymore on stable
03.12.2012 23:25, Hans Petter Selasky: On Monday 03 December 2012 20:04:59 Volodymyr Kostyrko wrote: 03.12.2012 20:09, Hans Petter Selasky: On Monday 03 December 2012 16:14:56 Volodymyr Kostyrko wrote: Hi all. Maybe I just blow out my installation again but I have two machines on 9_STABLE that for one week refuse to autoload usb device drivers. Before that my Keyboard and mice start automatically. But right now I must explicitly load kernel module for each device. There has been some changes in /etc/ . Make sure you did a mergemaster and that devd is running. Hi, I'm missing your point here. Which changes in etc? /etc/devd/usb.conf /etc/dev/devd.conf And you need to rebuild moused. My local files doesn't differ from files in svn. I had rebuilt moused. I have no devd_enable in /etc/rc.conf but according to /etc/defaults/rc.conf it's enabled by default. `service devd restart` does nothing. This covers not just mice but keyboard and wifi usb, however umass works: Dec 4 03:23:34 limbo kernel: ugen0.2: at usbus0 Dec 4 03:23:35 limbo kernel: umass0: 0/0, rev 2.00/1.00, addr 2> on usbus0 Dec 4 03:23:35 limbo kernel: umass0: SCSI over Bulk-Only; quirks = 0x4000 Dec 4 03:23:35 limbo kernel: umass0:5:0:-1: Attached to scbus5 Dec 4 03:23:37 limbo kernel: da0 at umass-sim0 bus 0 scbus5 target 0 lun 0 Dec 4 03:23:37 limbo kernel: da0: Removable Direct Access SCSI-0 device Dec 4 03:23:37 limbo kernel: da0: 40.000MB/s transfers Dec 4 03:23:37 limbo kernel: da0: 7441MB (15240576 512 byte sectors: 255H 63S/T 948C) Maybe just my local glitch though. I'll try to retest tomorrow. -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: USB devices not autodetecting anymore on stable
04.12.2012 09:22, Hans Petter Selasky: Maybe just my local glitch though. I'll try to retest tomorrow. devd must be enabled when you boot the system or plug the device. That was my fault. I tested how libc++ works with world/ports and it seems that devd perfectly compiles with libc++ but works incorrectly. There are no warnings/errors when compiling or running devd. -- Sphinx of black quartz, judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
new usb device probably, needs quirks
Hi all. # usbconfig -d 5.2 dump_device_desc ugen5.2: at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (200mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x0930 idProduct = 0x6544 bcdDevice = 0x0100 iManufacturer = 0x0001 <> iProduct = 0x0002 iSerialNumber = 0x0003 bNumConfigurations = 0x0001 # usbconfig -d 5.2 reset Feb 12 17:44:56 urquan kernel: umass0: at uhub5, port 4, addr 2 (disconnected) Feb 12 17:44:57 urquan kernel: umass0: class 0/0, rev 2.00/1.00, addr 2> on usbus5 Feb 12 17:44:57 urquan kernel: umass0: SCSI over Bulk-Only; quirks = 0x4100 Feb 12 17:44:57 urquan kernel: umass0:1:0:-1: Attached to scbus1 Feb 12 17:44:57 urquan kernel: da7 at umass-sim0 bus 0 scbus1 target 0 lun 0 Feb 12 17:44:57 urquan kernel: da7: < USB Flash Memory 1.00> Removable Direct Access SCSI-0 device Feb 12 17:44:57 urquan kernel: da7: Serial Number E954F90DBA26CC60EDC50A0F Feb 12 17:44:57 urquan kernel: da7: 40.000MB/s transfers Feb 12 17:44:57 urquan kernel: da7: 7397MB (15149056 512 byte sectors: 255H 63S/T 942C) Feb 12 17:44:57 urquan kernel: da7: quirks=0x2 Feb 12 17:44:57 urquan kernel: (da7:umass-sim0:0:0:0): got CAM status 0x50 Feb 12 17:44:57 urquan kernel: (da7:umass-sim0:0:0:0): fatal error, failed to attach to device Feb 12 17:44:57 urquan kernel: da7 at umass-sim0 bus 0 scbus1 target 0 lun 0 Feb 12 17:44:57 urquan kernel: da7: < USB Flash Memory 1.00> s/n E954F90DBA26CC60EDC50A0F detached Feb 12 17:44:57 urquan kernel: (da7:umass-sim0:0:0:0): Periph destroyed # usbconfig -d 5.2 add_quirk UQ_MSC_NO_PREVENT_ALLOW # usbconfig -d 5.2 reset Feb 12 17:47:51 urquan kernel: umass0: at uhub5, port 4, addr 2 (disconnected) Feb 12 17:47:51 urquan kernel: umass0: class 0/0, rev 2.00/1.00, addr 2> on usbus5 Feb 12 17:47:51 urquan kernel: umass0: SCSI over Bulk-Only; quirks = 0xc100 Feb 12 17:47:51 urquan kernel: umass0:1:0:-1: Attached to scbus1 Feb 12 17:47:52 urquan kernel: da7 at umass-sim0 bus 0 scbus1 target 0 lun 0 Feb 12 17:47:52 urquan kernel: da7: < USB Flash Memory 1.00> Removable Direct Access SCSI-0 device Feb 12 17:47:52 urquan kernel: da7: Serial Number E954F90DBA26CC60EDC50A0F Feb 12 17:47:52 urquan kernel: da7: 40.000MB/s transfers Feb 12 17:47:52 urquan kernel: da7: 7397MB (15149056 512 byte sectors: 255H 63S/T 942C) Feb 12 17:47:52 urquan kernel: da7: quirks=0x2 -- Sphinx of black quartz, judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: new usb device probably, needs quirks
14.02.2014 10:20, Hans Petter Selasky wrote: On 02/12/14 16:52, Volodymyr Kostyrko wrote: Hi all. # usbconfig -d 5.2 dump_device_desc ugen5.2: at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (200mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x0930 idProduct = 0x6544 bcdDevice = 0x0100 iManufacturer = 0x0001 <> iProduct = 0x0002 iSerialNumber = 0x0003 bNumConfigurations = 0x0001 Can you send a patch adding this quirk to: sys/dev/usb/quirk/usb_quirk.c And vendor and product IDs to: sys/dev/usb/usbdevs Which you have tested? Thank you, --HPS Probably I wouldn't dare to send patch... The drive is too far from me, something like ~600 km's at some hosting company datacenter. Citing the internet 0930 is "Toshiba Corp." and 6544 is "Kingston DataTraveler 2GB" whereas my hosting provider states that actually flash drive looks exactly like Goodram twister. Been uncertain of drive's origins I'll think I can't claim my solution been perfect. -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: "usbnet" support in FreeBSD?
On 23.08.2014 01:17, Miguel Clara wrote: I know FreeBSD suppots (at least according to the guide) usb tether, but some devices when connected via USB are visible as a network interface and this allows file sharing among other things! I have a Blackberry 10 device and I'm wondering if this is somehow possible or if not how hard would it be? On linux the device is recognize by usbnet driver ( http://www.linux-usb.org/usbnet/) is there anything like this in freebsd? More info about the device detection: dmesg: ugen0.4: at usbus0 umodem0: on usbus0 umodem0: data interface 0, has no CM over data, has no break device_attach: umodem0 attach returned 6 Try setting device to 'Mac compatibility' mode: Settings -> Storage and access -> USB connections : connect to Mac. Also check thath USB tethering is enabled in your phone: Settings -> Network Connections -> Internet tethering, select "Connect using" "USB" and turn it on. kernel: ugen6.2: at usbus6 devd: Executing 'kldload -n if_cdce' kernel: cdce0: 2.00/2.40, addr 1> on usbus6 devd: Executing 'logger Unknown USB device: vendor 0x0fca product 0x8013 bus uhub6' root: Unknown USB device: vendor 0x0fca product 0x8013 bus uhub6 kernel: ue0: on cdce0 kernel: ue0: Ethernet address: 96:eb:cd:2d:05:5d devd: Executing 'logger Unknown USB device: vendor 0x0fca product 0x8013 bus uhub6' limbo root: Unknown USB device: vendor 0x0fca product 0x8013 bus uhub6 devd: Executing '/etc/pccard_ether ue0 start' devd: Executing 'logger Unknown USB device: vendor 0x0fca product 0x8013 bus uhub6' root: Unknown USB device: vendor 0x0fca product 0x8013 bus uhub6 # dhclient ue0 DHCPREQUEST on ue0 to 255.255.255.255 port 67 DHCPNAK from 192.168.0.1 DHCPDISCOVER on ue0 to 255.255.255.255 port 67 interval 4 DHCPOFFER from 192.168.0.1 DHCPREQUEST on ue0 to 255.255.255.255 port 67 DHCPACK from 192.168.0.1 bound to 192.168.0.2 -- renewal in 3600 seconds. I don't know why but setting ifconfig_ue0=DHCP at /etc/rc.conf doesn't works. # route add default 192.168.0.1 # ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: icmp_seq=0 ttl=46 time=588.697 ms 64 bytes from 8.8.8.8: icmp_seq=1 ttl=46 time=284.988 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=46 time=277.634 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=46 time=275.505 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=46 time=252.686 ms ^C --- 8.8.8.8 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 252.686/335.902/588.697/126.859 ms # tcpdump -pni ue0 13:23:09.393751 IP 192.168.0.2 > 8.8.8.8: ICMP echo request, id 18451, seq 0, length 64 13:23:09.982413 IP 8.8.8.8 > 192.168.0.2: ICMP echo reply, id 18451, seq 0, length 64 13:23:10.398790 IP 192.168.0.2 > 8.8.8.8: ICMP echo request, id 18451, seq 1, length 64 13:23:10.683738 IP 8.8.8.8 > 192.168.0.2: ICMP echo reply, id 18451, seq 1, length 64 13:23:11.402911 IP 192.168.0.2 > 8.8.8.8: ICMP echo request, id 18451, seq 2, length 64 13:23:11.680505 IP 8.8.8.8 > 192.168.0.2: ICMP echo reply, id 18451, seq 2, length 64 13:23:12.406746 IP 192.168.0.2 > 8.8.8.8: ICMP echo request, id 18451, seq 3, length 64 13:23:12.682195 IP 8.8.8.8 > 192.168.0.2: ICMP echo reply, id 18451, seq 3, length 64 13:23:13.408292 IP 192.168.0.2 > 8.8.8.8: ICMP echo request, id 18451, seq 4, length 64 13:23:13.660936 IP 8.8.8.8 > 192.168.0.2: ICMP echo reply, id 18451, seq 4, length 64 -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb printer vs cups
On 12.09.2014 20:53, Andriy Gapon wrote: From my experience I think that cupsd executes backend tools with all uids and gids set to cups and no supplementary groups. In the case of USB printers the backends need to access /dev/usbctl and /dev/usb/foobar that corresponds to a printer. That means that the access to those devices must be somehow granted to cups:cups. How do people solve this? What kind of permissions / configuration do you use? devfs P.S. Maybe I over-generalized the issue to all USB printers. My personal experience is with an HP printer handled by hplip / hplip-plugin. Personally I prefer using stock lpd for those, it can be easily integrated with foomatic hpijs. -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
