USB HDD needs replugging?
Hi list, I recently bought a Seagate 320 GB portable USB HDD. Works perfectly with Linux and OS X, but in FreeBSD it has to be unplugged and replugged in order to show up in /dev/. Is there a way to make it behave normally? TIA, Indulekha ___ 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 HDD needs replugging?
On Saturday 21 August 2010 14:03:16 Indi wrote: > Hi list, > > I recently bought a Seagate 320 GB portable USB HDD. > Works perfectly with Linux and OS X, but in FreeBSD > it has to be unplugged and replugged in order to show > up in /dev/. > > Is there a way to make it behave normally? Try checking the USB Mass Storaquirks. See: usbconfig -h --HPS ___ 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 HDD needs replugging?
On Sat, Aug 21, 2010 at 03:04:03PM +0200, Hans Petter Selasky wrote: > On Saturday 21 August 2010 14:03:16 Indi wrote: > > Hi list, > > > > I recently bought a Seagate 320 GB portable USB HDD. > > Works perfectly with Linux and OS X, but in FreeBSD > > it has to be unplugged and replugged in order to show > > up in /dev/. > > > > Is there a way to make it behave normally? > > Try checking the USB Mass Storaquirks. See: > > usbconfig -h > Thanks for that. Here's what I found, but I have no idea what to do with it: sudo usbconfig -u 4 -a 5 dump_device_desc ugen4.5: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x0bc2 idProduct = 0x2300 bcdDevice = 0x0130 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 <2GH2P74N> bNumConfigurations = 0x0001 $ sudo usbconfig -u 4 -a 5 dump_device_quirks Dumping current device quirks: VID=0x0b05 PID=0x1726 REVLO=0x REVHI=0x QUIRK=UQ_HID_IGNORE VID=0x1608 PID=0x0001 REVLO=0x0094 REVHI=0x0094 QUIRK=UQ_SWAP_UNICODE VID=0x04fa PID=0x4201 REVLO=0x00a2 REVHI=0x00a2 QUIRK=UQ_BAD_ADC VID=0x04fa PID=0x4201 REVLO=0x00a2 REVHI=0x00a2 QUIRK=UQ_AU_NO_XU VID=0x04d2 PID=0x0070 REVLO=0x0103 REVHI=0x0103 QUIRK=UQ_BAD_ADC VID=0x04d2 PID=0xff05 REVLO=0x REVHI=0x QUIRK=UQ_BAD_AUDIO VID=0x05c7 PID=0x2011 REVLO=0x0110 REVHI=0x0110 QUIRK=UQ_SPUR_BUT_UP VID=0x0566 PID=0x2802 REVLO=0x0001 REVHI=0x0001 QUIRK=UQ_SPUR_BUT_UP VID=0x0711 PID=0x0100 REVLO=0x0102 REVHI=0x0102 QUIRK=UQ_BUS_POWERED VID=0x0711 PID=0x0210 REVLO=0x0102 REVHI=0x0102 QUIRK=UQ_BUS_POWERED VID=0x0451 PID=0x1446 REVLO=0x0110 REVHI=0x0110 QUIRK=UQ_POWER_CLAIM VID=0x0562 PID=0x0001 REVLO=0x0009 REVHI=0x0009 QUIRK=UQ_AU_NO_FRAC VID=0x1527 PID=0x0201 REVLO=0x0100 REVHI=0x0100 QUIRK=UQ_AU_INP_ASYNC VID=0x046d PID=0xc032 REVLO=0x REVHI=0x QUIRK=UQ_NO_STRINGS VID=0x03f0 PID=0x0004 REVLO=0x REVHI=0x QUIRK=UQ_BROKEN_BIDIR VID=0x03f0 PID=0x0104 REVLO=0x REVHI=0x QUIRK=UQ_BROKEN_BIDIR VID=0x03f0 PID=0x0204 REVLO=0x REVHI=0x QUIRK=UQ_BROKEN_BIDIR VID=0x03f0 PID=0x0304 REVLO=0x REVHI=0x QUIRK=UQ_BROKEN_BIDIR VID=0x03f0 PID=0x0404 REVLO=0x REVHI=0x QUIRK=UQ_BROKEN_BIDIR VID=0x03f0 PID=0x0212 REVLO=0x REVHI=0x QUIRK=UQ_BROKEN_BIDIR VID=0x0924 PID=0xffef REVLO=0x REVHI=0x QUIRK=UQ_BROKEN_BIDIR VID=0x051d PID=0x0002 REVLO=0x REVHI=0x QUIRK=UQ_HID_IGNORE VID=0x050d PID=0x0551 REVLO=0x REVHI=0x QUIRK=UQ_HID_IGNORE VID=0x0764 PID=0x0501 REVLO=0x REVHI=0x QUIRK=UQ_HID_IGNORE VID=0x1163 PID=0x0100 REVLO=0x REVHI=0x QUIRK=UQ_HID_IGNORE VID=0x04d8 PID=0x0002 REVLO=0x REVHI=0x QUIRK=UQ_HID_IGNORE VID=0x04d8 PID=0xc001 REVLO=0x REVHI=0x QUIRK=UQ_HID_IGNORE VID=0x0463 PID=0x0001 REVLO=0x REVHI=0x QUIRK=UQ_HID_IGNORE VID=0x0463 PID=0x REVLO=0x REVHI=0x QUIRK=UQ_HID_IGNORE VID=0x05ac PID=0x1290 REVLO=0x REVHI=0x QUIRK=UQ_HID_IGNORE VID=0x05ac PID=0x1292 REVLO=0x REVHI=0x QUIRK=UQ_HID_IGNORE VID=0x04b4 PID=0x0bad REVLO=0x REVHI=0x QUIRK=UQ_KBD_IGNORE VID=0x04b4 PID=0x0bad REVLO=0x REVHI=0x QUIRK=UQ_HID_IGNORE VID=0x1781 PID=0x083e REVLO=0x REVHI=0x QUIRK=UQ_KBD_IGNORE VID=0x1781 PID=0x083e REVLO=0x REVHI=0x QUIRK=UQ_HID_IGNORE VID=0x1130 PID=0xf211 REVLO=0x0101 REVHI=0x0101 QUIRK=UQ_AUDIO_SWAP_LR VID=0x045e PID=0x008c REVLO=0x REVHI=0x QUIRK=UQ_MS_LEADING_BYTE VID=0x1781 PID=0x083f REVLO=0x REVHI=0x QUIRK=UQ_KBD_IGNORE VID=0x1781 PID=0x083f REVLO=0x REVHI=0x QUIRK=UQ_HID_IGNORE ___ 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 HDD needs replugging?
On Sat, 2010-08-21 at 16:37 +0200, Hans Petter Selasky wrote: > There is a command to add quirks. Look at the source code: > > grep UQ_ /sys/dev/usb/storage/umass.c > > and look for UQ_ > Thanks for the suggestion. Unfortunately the string "UQ_" (or even "UQ") does not appear in umass.c. -- Indulekha ___ 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 HDD needs replugging?
On Saturday 21 August 2010 16:54:32 indulekha wrote:
> On Sat, 2010-08-21 at 16:37 +0200, Hans Petter Selasky wrote:
> > There is a command to add quirks. Look at the source code:
> >
> > grep UQ_ /sys/dev/usb/storage/umass.c
> >
> > and look for UQ_
>
> Thanks for the suggestion. Unfortunately the string "UQ_"
> (or even "UQ") does not appear in umass.c.
Then you typed something wrong:
grep UQ_ /sys/dev/usb/storage/umass.c
if (usb_test_quirk(uaa, UQ_MSC_FORCE_WIRE_BBB)) {
} else if (usb_test_quirk(uaa, UQ_MSC_FORCE_WIRE_CBI)) {
} else if (usb_test_quirk(uaa, UQ_MSC_FORCE_WIRE_CBI_I)) {
if (usb_test_quirk(uaa, UQ_MSC_FORCE_PROTO_SCSI)) {
} else if (usb_test_quirk(uaa, UQ_MSC_FORCE_PROTO_ATAPI)) {
} else if (usb_test_quirk(uaa, UQ_MSC_FORCE_PROTO_UFI)) {
} else if (usb_test_quirk(uaa, UQ_MSC_FORCE_PROTO_RBC)) {
if (usb_test_quirk(uaa, UQ_MSC_NO_TEST_UNIT_READY))
if (usb_test_quirk(uaa, UQ_MSC_NO_RS_CLEAR_UA))
if (usb_test_quirk(uaa, UQ_MSC_NO_START_STOP))
if (usb_test_quirk(uaa, UQ_MSC_NO_GETMAXLUN))
if (usb_test_quirk(uaa, UQ_MSC_NO_INQUIRY))
if (usb_test_quirk(uaa, UQ_MSC_NO_INQUIRY_EVPD))
if (usb_test_quirk(uaa, UQ_MSC_NO_SYNC_CACHE))
if (usb_test_quirk(uaa, UQ_MSC_SHUTTLE_INIT))
if (usb_test_quirk(uaa, UQ_MSC_ALT_IFACE_1))
if (usb_test_quirk(uaa, UQ_MSC_FLOPPY_SPEED))
if (usb_test_quirk(uaa, UQ_MSC_IGNORE_RESIDUE))
if (usb_test_quirk(uaa, UQ_MSC_WRONG_CSWSIG))
if (usb_test_quirk(uaa, UQ_MSC_RBC_PAD_TO_12))
if (usb_test_quirk(uaa, UQ_MSC_READ_CAP_OFFBY1))
if (usb_test_quirk(uaa, UQ_MSC_FORCE_SHORT_INQ))
--HPS
___
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 HDD needs replugging?
On Saturday 21 August 2010 16:52:28 Hans Petter Selasky wrote:
> On Saturday 21 August 2010 16:54:32 indulekha wrote:
> > On Sat, 2010-08-21 at 16:37 +0200, Hans Petter Selasky wrote:
> > > There is a command to add quirks. Look at the source code:
> > >
> > > grep UQ_ /sys/dev/usb/storage/umass.c
> > >
> > > and look for UQ_
> >
> > Thanks for the suggestion. Unfortunately the string "UQ_"
> > (or even "UQ") does not appear in umass.c.
>
> Then you typed something wrong:
>
> grep UQ_ /sys/dev/usb/storage/umass.c
> if (usb_test_quirk(uaa, UQ_MSC_FORCE_WIRE_BBB)) {
> } else if (usb_test_quirk(uaa, UQ_MSC_FORCE_WIRE_CBI)) {
> } else if (usb_test_quirk(uaa, UQ_MSC_FORCE_WIRE_CBI_I)) {
> if (usb_test_quirk(uaa, UQ_MSC_FORCE_PROTO_SCSI)) {
> } else if (usb_test_quirk(uaa, UQ_MSC_FORCE_PROTO_ATAPI)) {
> } else if (usb_test_quirk(uaa, UQ_MSC_FORCE_PROTO_UFI)) {
> } else if (usb_test_quirk(uaa, UQ_MSC_FORCE_PROTO_RBC)) {
> if (usb_test_quirk(uaa, UQ_MSC_NO_TEST_UNIT_READY))
> if (usb_test_quirk(uaa, UQ_MSC_NO_RS_CLEAR_UA))
> if (usb_test_quirk(uaa, UQ_MSC_NO_START_STOP))
> if (usb_test_quirk(uaa, UQ_MSC_NO_GETMAXLUN))
> if (usb_test_quirk(uaa, UQ_MSC_NO_INQUIRY))
> if (usb_test_quirk(uaa, UQ_MSC_NO_INQUIRY_EVPD))
> if (usb_test_quirk(uaa, UQ_MSC_NO_SYNC_CACHE))
> if (usb_test_quirk(uaa, UQ_MSC_SHUTTLE_INIT))
> if (usb_test_quirk(uaa, UQ_MSC_ALT_IFACE_1))
> if (usb_test_quirk(uaa, UQ_MSC_FLOPPY_SPEED))
> if (usb_test_quirk(uaa, UQ_MSC_IGNORE_RESIDUE))
> if (usb_test_quirk(uaa, UQ_MSC_WRONG_CSWSIG))
> if (usb_test_quirk(uaa, UQ_MSC_RBC_PAD_TO_12))
> if (usb_test_quirk(uaa, UQ_MSC_READ_CAP_OFFBY1))
> if (usb_test_quirk(uaa, UQ_MSC_FORCE_SHORT_INQ))
>
> --HPS
Hi,
Another suggestion:
Look in the dmesg and see if there are any errors.
--HPS
___
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"
Use extra buttons of Kensington Slimblade Trackball
Hi, While I'm searching how to use the extra buttons in Kensington Slimblade Trackball, I made a patch for myself based on the linux driver. I confirmed it works as intended. However, I have no experience with the FreeBSD kernel and I'm not sure that I modified it in a correct way. -- especially, I don't know should I use usb_quirks? Can somebody check the attached diff file so that I can send problem report? Thanks. ___ 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 HDD needs replugging?
On Saturday 21 August 2010 17:08:44 indulekha wrote: > > --HPS > > Well, see for yourself then: Hi, Ok, I see. I'm using a newer version of the same file :-) Try to enable some of the quirks listed in my previous email using usbconfig. Also check dmesg for errors. --HPS ___ 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 HDD needs replugging?
On Sat, 2010-08-21 at 16:54 +0200, Hans Petter Selasky wrote:
> On Saturday 21 August 2010 16:52:28 Hans Petter Selasky wrote:
> > On Saturday 21 August 2010 16:54:32 indulekha wrote:
> > > On Sat, 2010-08-21 at 16:37 +0200, Hans Petter Selasky wrote:
> > > > There is a command to add quirks. Look at the source code:
> > > >
> > > > grep UQ_ /sys/dev/usb/storage/umass.c
> > > >
> > > > and look for UQ_
> > >
> > > Thanks for the suggestion. Unfortunately the string "UQ_"
> > > (or even "UQ") does not appear in umass.c.
> >
> > Then you typed something wrong:
> >
> > grep UQ_ /sys/dev/usb/storage/umass.c
> > if (usb_test_quirk(uaa, UQ_MSC_FORCE_WIRE_BBB)) {
> > } else if (usb_test_quirk(uaa, UQ_MSC_FORCE_WIRE_CBI)) {
> > } else if (usb_test_quirk(uaa, UQ_MSC_FORCE_WIRE_CBI_I)) {
> > if (usb_test_quirk(uaa, UQ_MSC_FORCE_PROTO_SCSI)) {
> > } else if (usb_test_quirk(uaa, UQ_MSC_FORCE_PROTO_ATAPI)) {
> > } else if (usb_test_quirk(uaa, UQ_MSC_FORCE_PROTO_UFI)) {
> > } else if (usb_test_quirk(uaa, UQ_MSC_FORCE_PROTO_RBC)) {
> > if (usb_test_quirk(uaa, UQ_MSC_NO_TEST_UNIT_READY))
> > if (usb_test_quirk(uaa, UQ_MSC_NO_RS_CLEAR_UA))
> > if (usb_test_quirk(uaa, UQ_MSC_NO_START_STOP))
> > if (usb_test_quirk(uaa, UQ_MSC_NO_GETMAXLUN))
> > if (usb_test_quirk(uaa, UQ_MSC_NO_INQUIRY))
> > if (usb_test_quirk(uaa, UQ_MSC_NO_INQUIRY_EVPD))
> > if (usb_test_quirk(uaa, UQ_MSC_NO_SYNC_CACHE))
> > if (usb_test_quirk(uaa, UQ_MSC_SHUTTLE_INIT))
> > if (usb_test_quirk(uaa, UQ_MSC_ALT_IFACE_1))
> > if (usb_test_quirk(uaa, UQ_MSC_FLOPPY_SPEED))
> > if (usb_test_quirk(uaa, UQ_MSC_IGNORE_RESIDUE))
> > if (usb_test_quirk(uaa, UQ_MSC_WRONG_CSWSIG))
> > if (usb_test_quirk(uaa, UQ_MSC_RBC_PAD_TO_12))
> > if (usb_test_quirk(uaa, UQ_MSC_READ_CAP_OFFBY1))
> > if (usb_test_quirk(uaa, UQ_MSC_FORCE_SHORT_INQ))
> >
> > --HPS
>
> Hi,
>
> Another suggestion:
>
> Look in the dmesg and see if there are any errors.
>
> --HPS
Yes, there is a dmesg error:
ugen4.5: <(null)> at usbus4 (disconnected)
uhub_reattach_port:435: could not allocate new device!
But then just a few lines later, dmesg says:
ugen4.5: at usbus4
umass1: on usbus4
umass1: SCSI over Bulk-Only; quirks = 0x
umass1:3:1:-1: Attached to scbus3
da1 at umass-sim1 bus 1 target 0 lun 0
da1: Fixed Direct Access SCSI-4 device
da1: 40.000MB/s transfers
da1: 305245MB (625142448 512 byte sectors: 255H 63S/T 38913C)
I'm thinking there's some sort of power management scheme in the
Seagate that umass has trouble accommodating.
--
caveat utilitor,
Indi
___
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 HDD needs replugging?
> > Yes, there is a dmesg error: > > ugen4.5: <(null)> at usbus4 (disconnected) > uhub_reattach_port:435: could not allocate new device! > > But then just a few lines later, dmesg says: > > ugen4.5: at usbus4 > umass1: on usbus4 > umass1: SCSI over Bulk-Only; quirks = 0x > umass1:3:1:-1: Attached to scbus3 > da1 at umass-sim1 bus 1 target 0 lun 0 > da1: Fixed Direct Access SCSI-4 device > da1: 40.000MB/s transfers > da1: 305245MB (625142448 512 byte sectors: 255H 63S/T 38913C) > > I'm thinking there's some sort of power management scheme in the > Seagate that umass has trouble accommodating. Does your USB device have a separate power supply? --HPS ___ 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 HDD needs replugging?
On Sat, 2010-08-21 at 17:18 +0200, Hans Petter Selasky wrote: > > > > Yes, there is a dmesg error: > > > > ugen4.5: <(null)> at usbus4 (disconnected) > > uhub_reattach_port:435: could not allocate new device! > > > > But then just a few lines later, dmesg says: > > > > ugen4.5: at usbus4 > > umass1: on usbus4 > > umass1: SCSI over Bulk-Only; quirks = 0x > > umass1:3:1:-1: Attached to scbus3 > > da1 at umass-sim1 bus 1 target 0 lun 0 > > da1: Fixed Direct Access SCSI-4 device > > da1: 40.000MB/s transfers > > da1: 305245MB (625142448 512 byte sectors: 255H 63S/T 38913C) > > > > I'm thinking there's some sort of power management scheme in the > > Seagate that umass has trouble accommodating. > > > Does your USB device have a separate power supply? > > --HPS No, it's one of those pocket-sized HDDs. This one, actually: http://www.amazon.com/gp/product/B001SJZV10/ref=oss_product -- caveat utilitor, Indi ___ 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 HDD needs replugging?
On Saturday 21 August 2010 17:37:18 indulekha wrote: > On Sat, 2010-08-21 at 17:18 +0200, Hans Petter Selasky wrote: > > > Yes, there is a dmesg error: > > > > > > ugen4.5: <(null)> at usbus4 (disconnected) > > > uhub_reattach_port:435: could not allocate new device! > > > > > > But then just a few lines later, dmesg says: > > > > > > ugen4.5: at usbus4 > > > umass1: on usbus4 > > > umass1: SCSI over Bulk-Only; quirks = 0x > > > umass1:3:1:-1: Attached to scbus3 > > > da1 at umass-sim1 bus 1 target 0 lun 0 > > > da1: Fixed Direct Access SCSI-4 device > > > da1: 40.000MB/s transfers > > > da1: 305245MB (625142448 512 byte sectors: 255H 63S/T 38913C) > > > > > > I'm thinking there's some sort of power management scheme in the > > > Seagate that umass has trouble accommodating. > > > > Does your USB device have a separate power supply? > > > > --HPS > > No, it's one of those pocket-sized HDDs. > This one, actually: > http://www.amazon.com/gp/product/B001SJZV10/ref=oss_product Hi, Try to use an external self-powered USB HUB and see if the problem is the same. --PS ___ 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: Use extra buttons of Kensington Slimblade Trackball
On Sat, Aug 21, 2010 at 05:16:31PM +0200, Hans Petter Selasky wrote: > On Saturday 21 August 2010 10:23:06 Lee, Chung-Yeol wrote: > > Hi, > > > > While I'm searching how to use the extra buttons in Kensington Slimblade > > Trackball, I made a patch for myself based on the linux driver. > > > > I confirmed it works as intended. However, I have no experience with the > > FreeBSD kernel and I'm not sure that I modified it in a correct way. -- > > especially, I don't know should I use usb_quirks? > > > > Can somebody check the attached diff file so that I can send problem > > report? > > > > Thanks. > > Hi, > > Can you re-send your patch to me. The listware stripped it off. I think there > is also a similar patch in 9-current. Please check the version history of: > > /sys/dev/usb/input/ums.c > > --HPS diff file is against 8-STABLE. I just looked ums.c in HEAD from Web CVS repository and can't find similar code. C.-Y. Lee ___ 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: Use extra buttons of Kensington Slimblade Trackball
On Saturday 21 August 2010 18:02:56 Lee, Chung-Yeol wrote: > On Sat, Aug 21, 2010 at 05:16:31PM +0200, Hans Petter Selasky wrote: > > On Saturday 21 August 2010 10:23:06 Lee, Chung-Yeol wrote: > > > Hi, > > > > > > While I'm searching how to use the extra buttons in Kensington > > > Slimblade > > > > > > Trackball, I made a patch for myself based on the linux driver. > > > > > > I confirmed it works as intended. However, I have no experience with > > > the FreeBSD kernel and I'm not sure that I modified it in a correct > > > way. -- especially, I don't know should I use usb_quirks? > > > > > > Can somebody check the attached diff file so that I can send problem > > > > > > report? > > > > > > Thanks. > > > > Hi, > > > > Can you re-send your patch to me. The listware stripped it off. I think > > there is also a similar patch in 9-current. Please check the version > > history of: > > > > /sys/dev/usb/input/ums.c > > > > --HPS > > diff file is against 8-STABLE. > I just looked ums.c in HEAD from Web CVS repository and can't find similar > code. > > C.-Y. Lee Hi, Please check and verify this patch: http://p4web.freebsd.org/@@182688?ac=10 Also, could you dump the device, config and HID descriptors of your mouse. See man usbconfig on how to do that. --HPS ___ 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 HDD needs replugging?
On Sat, 2010-08-21 at 17:56 +0200, Hans Petter Selasky wrote: > On Saturday 21 August 2010 17:37:18 indulekha wrote: > > On Sat, 2010-08-21 at 17:18 +0200, Hans Petter Selasky wrote: > > > > Yes, there is a dmesg error: > > > > > > > > ugen4.5: <(null)> at usbus4 (disconnected) > > > > uhub_reattach_port:435: could not allocate new device! > > > > > > > > But then just a few lines later, dmesg says: > > > > > > > > ugen4.5: at usbus4 > > > > umass1: on usbus4 > > > > umass1: SCSI over Bulk-Only; quirks = 0x > > > > umass1:3:1:-1: Attached to scbus3 > > > > da1 at umass-sim1 bus 1 target 0 lun 0 > > > > da1: Fixed Direct Access SCSI-4 device > > > > da1: 40.000MB/s transfers > > > > da1: 305245MB (625142448 512 byte sectors: 255H 63S/T 38913C) > > > > > > > > I'm thinking there's some sort of power management scheme in the > > > > Seagate that umass has trouble accommodating. > > > > > > Does your USB device have a separate power supply? > > > > > > --HPS > > > > No, it's one of those pocket-sized HDDs. > > This one, actually: > > http://www.amazon.com/gp/product/B001SJZV10/ref=oss_product > > Hi, > > Try to use an external self-powered USB HUB and see if the problem is the > same. > > --PS Sorry, don't have one of those. Also, I really haven't been able to find much online about how to enable quirks, whether the quirks listed in the ouput of usbconfig are already in effect or just available for implementation, if there's some formula for creating them, whether any should be avoided, what is the exact command to enable or disable quirks, etc. It's surprising how terribly scarce this knowledge seems to be. All I know is spending Saturday morning screwing around with this was not my plan. :) I'm not trying to become an expert on USB, just thought someone somewhere would see my post and say "oh yeah, just modify line n of file foo to *this* and off you go". Instead this is looking more like an adventure requiring hours and hours of reading I just don't have time for right now. But thanks for taking the time to try to help, I'm just not knowledgeable enough to make use of it yet. :) -- caveat utilitor, Indi ___ 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 HDD needs replugging?
On Saturday 21 August 2010 18:26:21 indulekha wrote: > what is the exact > command to enable or disable quirks, etc. Hi, The format is: usbconfig add_dev_quirk_vplh vid: VendorID pid: ProductID lo_rev: 0 Hi_rev 0x quirk: your quirk UQ_XXX If the driver shows a disconnect message or attach failure, then I think quirks won't help. Instead of replugging your device, it is sometimes possible to make the device available using: usbconfig -u X -a Y reset Where X and Y are the ugenX.Y for your root HUB or your device. You need to be root to execute these commands. --HPS ___ 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 HDD needs replugging?
On Sat, 2010-08-21 at 18:29 +0200, Hans Petter Selasky wrote: > On Saturday 21 August 2010 18:26:21 indulekha wrote: > > what is the exact > > command to enable or disable quirks, etc. > > Hi, > > The format is: > > usbconfig add_dev_quirk_vplh > > vid: VendorID > pid: ProductID > > lo_rev: 0 > Hi_rev 0x > > quirk: your quirk UQ_XXX > > If the driver shows a disconnect message or attach failure, then I think > quirks won't help. > > Instead of replugging your device, it is sometimes possible to make the > device > available using: > > usbconfig -u X -a Y reset > > Where X and Y are the ugenX.Y for your root HUB or your device. > > You need to be root to execute these commands. > > --HPS Thanks very much for that. I'll try the usbconfig reset next time I reboot -- it drops me into single user mode every time due to the unavailable fstab filesystem (my home directory is on that disk, didn't realize there'd be a problem til I rebooted). Fortunately I don't reboot this machine often... -- caveat utilitor, Indi ___ 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 HDD needs replugging?
Hans Petter Selasky wrote: > On Saturday 21 August 2010 17:37:18 indulekha wrote: > > On Sat, 2010-08-21 at 17:18 +0200, Hans Petter Selasky wrote: > > > > Yes, there is a dmesg error: > > > > > > > > ugen4.5: <(null)> at usbus4 (disconnected) > > > > uhub_reattach_port:435: could not allocate new device! > > > > > > > > But then just a few lines later, dmesg says: > > > > > > > > ugen4.5: at usbus4 > > > > umass1: on usbus4 > > > > umass1: SCSI over Bulk-Only; quirks = 0x > > > > umass1:3:1:-1: Attached to scbus3 > > > > da1 at umass-sim1 bus 1 target 0 lun 0 > > > > da1: Fixed Direct Access SCSI-4 device > > > > da1: 40.000MB/s transfers > > > > da1: 305245MB (625142448 512 byte sectors: 255H 63S/T 38913C) > > > > > > > > I'm thinking there's some sort of power management scheme in the > > > > Seagate that umass has trouble accommodating. > > > > > > Does your USB device have a separate power supply? > > > > > > --HPS Joining late, sorry > > No, it's one of those pocket-sized HDDs. > > This one, actually: > > http://www.amazon.com/gp/product/B001SJZV10/ref=oss_product No current rating at http://www.seagate.com/ww/v/index.jsp?name=ST903204EXM101-RK-apac-expansion-portable-usb-320gb-hd&vgnextoid=16816583b2561210VgnVCM101a48090aRCRD&locale=en-US#TabContentSpecifications > Hi, > > Try to use an external self-powered USB HUB and see if the problem is the > same. Yes, PS Ive had so much grief with USB over the years, I cut out some USB sockets off a dead mboard, so I can intercept & meausure voltage & current on USB devices. USB 1 & 2 is spec'd at <= 0.5 Amp, (more on USB3 later) As well as the hub, A power doubler USB Y leads into 2 sockets of the hub may help, also plug both of those in before the disc in the other end. (else voltage droop while disc spins may confuse disc internal logic). PPS HPS Re that suspicion above, I also have a device that used to confuse usbd & prob. still confuses devd, (I guess it was turning itself off after listening to cable, anyway it's free if you or another USB developer wants to play with it, contact me. http://berklix.com/~jhs/txt/clipman/ Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text, Not HTML, quoted-printable & base 64 dumped with spam. Avoid top posting, It cripples itemised cumulative responses. ___ 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 HDD needs replugging?
On Sat, 2010-08-21 at 18:35 +0200, Julian H. Stacey wrote: > Hans Petter Selasky wrote: > > On Saturday 21 August 2010 17:37:18 indulekha wrote: > > > On Sat, 2010-08-21 at 17:18 +0200, Hans Petter Selasky wrote: > > > > > Yes, there is a dmesg error: > > > > > > > > > > ugen4.5: <(null)> at usbus4 (disconnected) > > > > > uhub_reattach_port:435: could not allocate new device! > > > > > > > > > > But then just a few lines later, dmesg says: > > > > > > > > > > ugen4.5: at usbus4 > > > > > umass1: on usbus4 > > > > > umass1: SCSI over Bulk-Only; quirks = 0x > > > > > umass1:3:1:-1: Attached to scbus3 > > > > > da1 at umass-sim1 bus 1 target 0 lun 0 > > > > > da1: Fixed Direct Access SCSI-4 device > > > > > da1: 40.000MB/s transfers > > > > > da1: 305245MB (625142448 512 byte sectors: 255H 63S/T 38913C) > > > > > > > > > > I'm thinking there's some sort of power management scheme in the > > > > > Seagate that umass has trouble accommodating. > > > > > > > > Does your USB device have a separate power supply? > > > > > > > > --HPS > > > Joining late, sorry > > > > No, it's one of those pocket-sized HDDs. > > > This one, actually: > > > http://www.amazon.com/gp/product/B001SJZV10/ref=oss_product > > No current rating at > > http://www.seagate.com/ww/v/index.jsp?name=ST903204EXM101-RK-apac-expansion-portable-usb-320gb-hd&vgnextoid=16816583b2561210VgnVCM101a48090aRCRD&locale=en-US#TabContentSpecifications > > > Hi, > > > > Try to use an external self-powered USB HUB and see if the problem is the > > same. > > Yes, > PS Ive had so much grief with USB over the years, I cut out some > USB sockets off a dead mboard, so I can intercept & meausure voltage > & current on USB devices. > > USB 1 & 2 is spec'd at <= 0.5 Amp, (more on USB3 later) > > As well as the hub, > A power doubler USB Y leads into 2 sockets of the hub may help, > also plug both of those in before the disc in the other end. (else > voltage droop while disc spins may confuse disc internal logic). > > PPS HPS Re that suspicion above, I also have a device that used to > confuse usbd & prob. still confuses devd, (I guess it was turning > itself off after listening to cable, anyway it's free if you or > another USB developer wants to play with it, contact me. > http://berklix.com/~jhs/txt/clipman/ > > Cheers, > Julian Actually, I haven't had any trouble with USB for a long time now but maybe that's just luck. :) Had to jump through some minor hoops to get my Blackberry to mount, otherwise USB has pretty much "just worked" for me the last two years or so. Well, there was one other purchase of a portable USB HDD before this one; it wasn't recognized at all so I just returned it. I'd have returned this one too had I known... -- caveat utilitor, Indi ___ 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: Use extra buttons of Kensington Slimblade Trackball
On Sat, Aug 21, 2010 at 06:18:45PM +0200, Hans Petter Selasky wrote: > On Saturday 21 August 2010 18:02:56 Lee, Chung-Yeol wrote: > > On Sat, Aug 21, 2010 at 05:16:31PM +0200, Hans Petter Selasky wrote: > > > On Saturday 21 August 2010 10:23:06 Lee, Chung-Yeol wrote: > > > > Hi, > > > > > > > > While I'm searching how to use the extra buttons in Kensington > > > > Slimblade > > > > > > > > Trackball, I made a patch for myself based on the linux driver. > > > > > > > > I confirmed it works as intended. However, I have no experience with > > > > the FreeBSD kernel and I'm not sure that I modified it in a correct > > > > way. -- especially, I don't know should I use usb_quirks? > > > > > > > > Can somebody check the attached diff file so that I can send problem > > > > > > > > report? > > > > > > > > Thanks. > > > > > > Hi, > > > > > > Can you re-send your patch to me. The listware stripped it off. I think > > > there is also a similar patch in 9-current. Please check the version > > > history of: > > > > > > /sys/dev/usb/input/ums.c > > > > > > --HPS > > > > diff file is against 8-STABLE. > > I just looked ums.c in HEAD from Web CVS repository and can't find similar > > code. > > > > C.-Y. Lee > > Hi, > > Please check and verify this patch: > > http://p4web.freebsd.org/@@182688?ac=10 > > Also, could you dump the device, config and HID descriptors of your mouse. > See > man usbconfig on how to do that. > > --HPS It seems alright. Here's dump.. # usbconfig -u 0 -a 3 dump_device_desc ugen0.3: at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0008 idVendor = 0x047d idProduct = 0x2041 bcdDevice = 0x0105 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x bNumConfigurations = 0x0001 # usbconfig -u 0 -a 3 dump_curr_config_desc ugen0.3: at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0022 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x bmAttributes = 0x00a0 bMaxPower = 0x0032 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0002 iInterface = 0x Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x10 RAW dump: 0x00 | 0x09, 0x21, 0x10, 0x01, 0x00, 0x01, 0x22, 0x4b, 0x08 | 0x00 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 bmAttributes = 0x0003 wMaxPacketSize = 0x0005 bInterval = 0x000a bRefresh = 0x bSynchAddress = 0x # usbconfig -u 0 -a 3 do_request 0x81 0x06 0x2200 0 0x100 REQUEST = <0x05 0x01 0x09 0x02 0xa1 0x01 0x09 0x01 0xa1 0x00 0x05 0x09 0x19 0x01 0x29 0x02 0x15 0x00 0x25 0x01 0x95 0x02 0x75 0x01 0x81 0x02 0x95 0x01 0x75 0x06 0x81 0x03 0x05 0x01 0x09 0x30 0x09 0x31 0x09 0x38 0x15 0x81 0x25 0x7f 0x75 0x08 0x95 0x03 0x81 0x06 0x06 0x00 0xff 0x19 0x01 0x29 0x02 0x15 0x00 0x25 0x01 0x95 0x02 0x75 0x01 0x81 0x02 0x95 0x01 0x75 0x06 0x81 0x03 0xc0 0xc0><)%uu018%u)%uu> Thanks. C.-Y. Lee. ___ 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
On Saturday 21 August 2010 20:28:55 Volodymyr Kostyrko wrote: > 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. After setting the quirk, you need to reset or re-attach the USB device. --HPS ___ 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: USB HDD needs replugging?
On Sat, 21 Aug 2010, Hans Petter Selasky wrote: On Saturday 21 August 2010 18:26:21 indulekha wrote: what is the exact command to enable or disable quirks, etc. Hi, The format is: usbconfig add_dev_quirk_vplh vid: VendorID pid: ProductID lo_rev: 0 Hi_rev 0x quirk: your quirk UQ_XXX If the driver shows a disconnect message or attach failure, then I think quirks won't help. Instead of replugging your device, it is sometimes possible to make the device available using: usbconfig -u X -a Y reset Where X and Y are the ugenX.Y for your root HUB or your device. You need to be root to execute these commands. A real, working example of this would be an excellent addition to usbconfig(8). If you provide one, and explain what it does, I'll create a patch. ___ 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: software atmel arm serial USB
On Saturday 21 August 2010 22:07:34 Volodymyr Kostyrko wrote: > 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? You can try adding the VID + PID pair to serial/umodem.c . Try loading: kldload umodem.ko First. --HPS ___ 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"
