Re: usb/141467: [uftdi] [patch] RATOC REX-USB60F (usb serial converter) is not working on -current
On Tuesday 15 December 2009 01:51:50 yamam...@freebsd.org, Shigeru wrote:
Number: 141467
Category: usb
Synopsis: [uftdi] [patch] RATOC REX-USB60F (usb serial converter) is
not working on -current Confidential: no
Severity: non-critical
Priority: low
Responsible:freebsd-usb
State: open
Quarter:
Keywords:
Date-Required:
Class: sw-bug
Submitter-Id: current-users
Arrival-Date: Tue Dec 15 01:00:07 UTC 2009
Closed-Date:
Last-Modified:
Originator: YAMAMOTO, Shigeru
Release:FreeBSD 9.0-CURRENT
Organization:
Environment:
FreeBSD 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Wed Dec 2 11:31:13
JST 2009 r...@xxx:/usr/src/sys/amd64/compile/GENERIC amd64
Description:
this problem is same as PR 'usb/115933'.
http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/115933
I modify a patch which is attached to that PR.
I'm currenty using RES-USB60F on my -current environment.
How-To-Repeat:
Fix:
use this patch and recompile uftdi.ko.
Patch attached with submission follows:
Index: sys/dev/usb/usbdevs
===
RCS file: /share/cvsup/FreeBSD/current/usr/src/sys/dev/usb/usbdevs,v
retrieving revision 1.428
diff -u -r1.428 usbdevs
--- sys/dev/usb/usbdevs 11 Dec 2009 02:44:15 - 1.428
+++ sys/dev/usb/usbdevs 11 Dec 2009 06:07:33 -
@@ -2135,6 +2135,7 @@
/* RATOC Systems products */
product RATOC REXUSB60 0xb000 REX-USB60
+product RATOC REXUSB60F 0xb020 REX-USB60F
/* Sagem products */
product SAGEM USBSERIAL 0x0027 USB-Serial Controller
Index: sys/dev/usb/serial/uftdi.c
===
RCS file: /share/cvsup/FreeBSD/current/usr/src/sys/dev/usb/serial/uftdi.c,v
retrieving revision 1.17
diff -u -r1.17 uftdi.c
--- sys/dev/usb/serial/uftdi.c9 Dec 2009 20:28:33 - 1.17
+++ sys/dev/usb/serial/uftdi.c10 Dec 2009 00:15:38 -
@@ -252,6 +252,7 @@
{USB_VPI(USB_VENDOR_BBELECTRONICS, USB_PRODUCT_BBELECTRONICS_USOTL4,
UFTDI_TYPE_8U232AM)}, {USB_VPI(USB_VENDOR_MARVELL,
USB_PRODUCT_MARVELL_SHEEVAPLUG, UFTDI_TYPE_8U232AM)},
{USB_VPI(USB_VENDOR_MELCO, USB_PRODUCT_MELCO_PCOPRS1, UFTDI_TYPE_8U232AM)},
+ {USB_VPI(USB_VENDOR_RATOC, USB_PRODUCT_RATOC_REXUSB60F,
UFTDI_TYPE_8U232AM)}, };
static int
Release-Note:
Audit-Trail:
Unformatted:
Committed to USB P4, ID=171783.
--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: Re-enumerating a device
On Tuesday 15 December 2009 07:17:46 Daniel O'Connor wrote: [ Please CC me as I'm not on list ] Hi, I have an M-Audio MobilePre, it's a USB audio module which works with snd_uadio, however to get it working I need to load the firwmare (via DFU). Unfortunately the only way I can get it to re-enumerate after sending the firmware is to unplug it enough to disconnect the data lines (but not power) and then reconnect. I have tried usbconfig reset, power_off/power_on, set_config and set_alt but to no avail.. [inchoate 16:46] ~/projects/dfu-util-0.1.snap20090212 dfu-util -D ~/ma004103.bin -t 256 dfu-util - (C) 2007-2008 by OpenMoko Inc. This program is Free Software and has ABSOLUTELY NO WARRANTY Opening USB Device 0x:0x... Claiming USB DFU Runtime Interface... Determining device status: state = dfuIDLE, status = 0 WARNING: Runtime device already in DFU state ?!? Found Runtime: [0x0763:0x2804] devnum=0, cfg=0, intf=0, alt=0, name=RAM Claiming USB DFU Interface... Setting Alternate Setting ... Determining device status: state = dfuIDLE, status = 0 dfuIDLE, continuing Transfer Size = 0x0100 bytes_per_hash=120 Starting download: [##] finished! state(7) = dfuMANIFEST, status(0) = No error condition is present state(2) = dfuIDLE, status(0) = No error condition is present Done! From dmesg.. ugen0.2: Unknown at usbus0 # Run dfu-util ugen0.2: Unknown at usbus0 (disconnected) # Cause re-enumeratae ugen0.2: M Audio at usbus0 uaudio0: MobilePre on usbus0 uaudio0: Play: 48000 Hz, 2 ch, 16-bit S-LE PCM format uaudio0: Record: 48000 Hz, 2 ch, 16-bit S-LE PCM format uaudio0: No midi sequencer pcm1: USB audio on uaudio0 Can you show dmesg, when you do: usbconfig -u 0 -a 2 reset --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/141474: [boot] FreeBSD 8.0 can not install from USB CDROM drive
On Tuesday 15 December 2009 08:36:24 lini...@freebsd.org wrote: Old Synopsis: FreeBSD 8.0 can not install from USB CDROM drive New Synopsis: [boot] FreeBSD 8.0 can not install from USB CDROM drive Responsible-Changed-From-To: freebsd-bugs-freebsd-usb Responsible-Changed-By: linimon Responsible-Changed-When: Tue Dec 15 07:35:51 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=141474 ___ 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 Hi, Is the USB CD-ROM detected by the USB stack, and what is the CD-ROM device? Maybe you simply have to reconfigure sysinstall to use another /dev/cdX for the installation. --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
5.1-channel USB sound device on 8.0-RELEASE
Hi.
I tested below device on 8.0-RELEASE with patch.
*1 Kyo-On DIGI(sorry,this page was writtin in Japanese)
http://www.area-powers.jp/product/usb_product/product/kyo-on/u1soundt4.html
This device is 5.1-channel USB sound device.
Without patch, ``No playback!''
ugen0.6: vendor 0x0d8c at usbus0
uaudio1: vendor 0x0d8c product 0x0006, class 0/0, rev 1.10/0.10, addr 6 on
usbus0
uaudio1: No playback!
uaudio1: Record: 48000 Hz, 2 ch, 16-bit S-LE PCM format
uaudio1: No midi sequencer
pcm1: USB audio on uaudio1
With patch:
uaudio1: vendor 0x0d8c product 0x0006, class 0/0, rev 1.10/0.10, addr 6 on usb
us0
uaudio1: Play: 48000 Hz, 8 ch, 16-bit S-LE PCM format
uaudio1: Record: 48000 Hz, 2 ch, 16-bit S-LE PCM format
uaudio1: No midi sequencer
pcm1: USB audio on uaudio1
But I could not play with mpg123, only noise.
How can I use this device on 8.0-RELEASE.
Cheers.
---
MIHIRA, Sanpei Yoshiro
Tokyo, Japan.
http://freebsd.monkey.org/freebsd-usb/200905/msg00090.html
--- sys/dev/sound/usb/uaudio.c.org 2009-12-07 10:29:05.593175070 +0900
+++ sys/dev/sound/usb/uaudio.c 2009-12-07 10:29:51.030304905 +0900
@@ -112,7 +112,8 @@
#defineMAKE_WORD(h,l) (((h) 8) | (l))
#defineBIT_TEST(bm,bno) (((bm)[(bno) / 8] (7 - ((bno) % 8))) 1)
-#defineUAUDIO_MAX_CHAN(x) (x)
+#define UAUDIO_MAX_CHAN(x) (((x) 2) ? (x) : 2)/* XXX fixme later */
+
struct uaudio_mixer_node {
int32_t minval;
___
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 2.5 USB drive
On Fri, Dec 11, 2009 at 6:17 PM, Spil Oss spil@googlemail.com wrote: On Fri, Dec 11, 2009 at 10:37 AM, Hans Petter Selasky hsela...@c2i.net wrote: On Thursday 10 December 2009 17:08:53 Spil Oss wrote: On Thu, Dec 10, 2009 at 10:08 AM, Spil Oss spil@googlemail.com wrote: Hello all, Can't get my 2.5 USB drive to work reliably. The device has a ALI M5642 Chip and connects 2.5 PATA disks. Vendor 0x0402 is USB_VENDOR_ACERLABS /* Acer Labs */ which ALi is afaik. When I connect it: Dec 8 16:11:20 gw root: Unknown USB device: vendor 0x0402 product 0x5642 bus uhub3 Dec 8 16:11:20 gw kernel: ugen3.2: vendor 0x0402 at usbus3 Dec 8 16:11:20 gw kernel: umass0: vendor 0x0402 USB 2.0 Storage Device, class 0/0, rev 2.00/1.00, addr 2 on usbus3 Dec 8 16:11:20 gw kernel: umass0: SCSI over Bulk-Only; quirks = 0x Dec 8 16:11:21 gw kernel: umass0:0:0:-1: Attached to scbus0 Dec 8 16:11:21 gw kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Dec 8 16:11:21 gw kernel: da0: USB 2.0 Storage Device 0100 Fixed Direct Access SCSI-0 device Dec 8 16:11:21 gw kernel: da0: 40.000MB/s transfers Dec 8 16:11:21 gw kernel: da0: 38154MB (78140160 512 byte sectors: 255H 63S/T 4864C) When I try to dd/fdisk/bsdlabel the disk I tend to get Dec 9 12:47:49 gw kernel: (da0:umass-sim0:0:0:0): AutoSense Failed Sometimes the LED on the cage stays red until I reconnect it. When I first `usbconfig -u 3 -a 2 reset` and then reconnect the disk it is recognized again. Tried both on an Intel GM855 and a nVidia nForce4 system. Errors that pop up when transferring data: Dec 8 16:11:21 gw kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 Dec 8 16:11:21 gw kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 Dec 8 16:11:21 gw kernel: (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed Strangely it seems that this device was recognized on a previous version of FreeBSD see http://takaq1.plala.jp/freebsd/usb/index.html (not that I've tried!) Not quite clear what version of FreeBSD that is. Ultimately FreeBSD crashes when I play around too long.. Can anyone assist? Saw on the list that usbconfig dump_device_desc is helpful, problematic device is ugen3.2: ugen0.1: UHCI root HUB Intel at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0100 bDeviceClass = 0x0009 bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x idProduct = 0x bcdDevice = 0x0100 iManufacturer = 0x0001 Intel iProduct = 0x0002 UHCI root HUB iSerialNumber = 0x no string bNumConfigurations = 0x0001 ugen1.1: UHCI root HUB Intel at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0100 bDeviceClass = 0x0009 bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x idProduct = 0x bcdDevice = 0x0100 iManufacturer = 0x0001 Intel iProduct = 0x0002 UHCI root HUB iSerialNumber = 0x no string bNumConfigurations = 0x0001 ugen2.1: UHCI root HUB Intel at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0100 bDeviceClass = 0x0009 bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x idProduct = 0x bcdDevice = 0x0100 iManufacturer = 0x0001 Intel iProduct = 0x0002 UHCI root HUB iSerialNumber = 0x no string bNumConfigurations = 0x0001 ugen3.1: EHCI root HUB Intel at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0009 bDeviceSubClass = 0x bDeviceProtocol = 0x0001 bMaxPacketSize0 = 0x0040 idVendor = 0x idProduct = 0x bcdDevice = 0x0100 iManufacturer = 0x0001 Intel iProduct = 0x0002 EHCI root HUB iSerialNumber = 0x no string bNumConfigurations = 0x0001 ugen3.2: USB 2.0 Storage Device vendor 0x0402 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 = 0x0402 idProduct = 0x5642 bcdDevice = 0x0100 iManufacturer = 0x no string iProduct = 0x0001 USB 2.0 Storage Device iSerialNumber = 0x0002 12345678901234567890 bNumConfigurations = 0x0001 Thanks! Have you tried a 9-current kernel? --HPS Haven't tried a -CURRENT kernel. Guess that a kernel wouldn't be a big change, but world. Have usbdevs.h and/or usbdevs_data.h changed considerably? Hello all, Tried a GENERIC 9.0-CURRENT kernel csup-ped today just about 2 hours ago. Same problem. I seem to have been able to
Re: Problem with 2.5 USB drive
Hello all, Tried a GENERIC 9.0-CURRENT kernel csup-ped today just about 2 hours ago. Same problem. I seem to have been able to fdisk the disk, when bsdlabel-ing I get kernel: (da0:umass-sim0:0:0:0) AutoSense Failed The light on the USB cage stays red until I unplug it. Can anyone assist? Hi, This maybe indicate that your USB hardware dies on a non-supported SCSI command. Have you tried a USB enclosure from another manufacturer? --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: 5.1-channel USB sound device on 8.0-RELEASE
On Tuesday 15 December 2009 15:11:27 MIHIRA Sanpei Yoshiro wrote:
Hi.
I tested below device on 8.0-RELEASE with patch.
*1 Kyo-On DIGI(sorry,this page was writtin in Japanese)
http://www.area-powers.jp/product/usb_product/product/kyo-on/u1soundt4.htm
l
This device is 5.1-channel USB sound device.
Without patch, ``No playback!''
ugen0.6: vendor 0x0d8c at usbus0
uaudio1: vendor 0x0d8c product 0x0006, class 0/0, rev 1.10/0.10, addr 6
on usbus0 uaudio1: No playback!
uaudio1: Record: 48000 Hz, 2 ch, 16-bit S-LE PCM format
uaudio1: No midi sequencer
pcm1: USB audio on uaudio1
With patch:
uaudio1: vendor 0x0d8c product 0x0006, class 0/0, rev 1.10/0.10, addr 6
on usb us0
uaudio1: Play: 48000 Hz, 8 ch, 16-bit S-LE PCM format
uaudio1: Record: 48000 Hz, 2 ch, 16-bit S-LE PCM format
uaudio1: No midi sequencer
pcm1: USB audio on uaudio1
But I could not play with mpg123, only noise.
How can I use this device on 8.0-RELEASE.
Cheers.
---
MIHIRA, Sanpei Yoshiro
Tokyo, Japan.
http://freebsd.monkey.org/freebsd-usb/200905/msg00090.html
--- sys/dev/sound/usb/uaudio.c.org2009-12-07 10:29:05.593175070 +0900
+++ sys/dev/sound/usb/uaudio.c2009-12-07 10:29:51.030304905 +0900
@@ -112,7 +112,8 @@
#define MAKE_WORD(h,l) (((h) 8) | (l))
#define BIT_TEST(bm,bno) (((bm)[(bno) / 8] (7 - ((bno) % 8))) 1)
-#define UAUDIO_MAX_CHAN(x) (x)
+#define UAUDIO_MAX_CHAN(x) (((x) 2) ? (x) : 2)/* XXX fixme later
*/ +
struct uaudio_mixer_node {
int32_t minval;
Hi,
Your audio device does not provide a 2 or 1 channel alternate setting.
Currently the PCM sound system does not support more than 2 channels.
That's why it doesn't work.
Feel free to start working on a more complete patch.
--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: Re-enumerating a device
On Tue, 15 Dec 2009, Hans Petter Selasky wrote: From dmesg.. ugen0.2: Unknown at usbus0 # Run dfu-util ugen0.2: Unknown at usbus0 (disconnected) # Cause re-enumeratae ugen0.2: M Audio at usbus0 uaudio0: MobilePre on usbus0 uaudio0: Play: 48000 Hz, 2 ch, 16-bit S-LE PCM format uaudio0: Record: 48000 Hz, 2 ch, 16-bit S-LE PCM format uaudio0: No midi sequencer pcm1: USB audio on uaudio0 Can you show dmesg, when you do: usbconfig -u 0 -a 2 reset I see nothing appear no matterwhen I run it (before or after the device has been programmed). It takes about a second to run though.. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: usb/141664: Logitech USB microphone failure
Synopsis: Logitech USB microphone failure Responsible-Changed-From-To: freebsd-bugs-freebsd-usb Responsible-Changed-By: linimon Responsible-Changed-When: Wed Dec 16 07:31:20 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=141664 ___ 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
