|Subject:||Re: UPS USB serial device is not detected properly|
|From:||Greg KH (gr...@kroah.com)|
|Date:||Dec 27, 2008 9:53:39 am|
On Sat, Dec 27, 2008 at 01:14:56PM +0200, Hai Zaar wrote:
On Sat, Dec 27, 2008 at 12:23 AM, Greg KH <gr...@kroah.com> wrote:
On Fri, Dec 26, 2008 at 09:35:09PM +0200, Hai Zaar wrote:
Good day! I have Advice Partner PR650 UPS, that connects to PC using USB. However, /dev/ttyUSB0 is not created. I've tried both on Debian Lenny and Ubuntu Hardy. Here is what dmesg and udevmonitor say (on Debian):
dmesg: usb 2-3: new low speed USB device using ohci_hcd and address 10 usb 2-3: configuration #1
chosen from 1 choice
hiddev96hidraw0: USB HID v1.00 Device [POWERCOM CO., LTD. USB to Serial] on usb-0000:00:0b.0-3 usb 2-3: New USB device found, idVendor=0d9f, idProduct=0002 usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 2-3: Product: USB to Serial usb 2-3: Manufacturer: POWERCOM CO., LTD. usbcore: registered new interface driver usbserial usbserial: USB Serial support registered for generic usbcore: registered new interface driver usbserial_generic usbserial: USB Serial Driver core usbserial: USB Serial support registered for DeLorme Earthmate USB usbserial: USB Serial support registered for HID->COM RS232 Adapter usbserial: USB Serial support registered for Nokia CA-42 V2 Adapter usbcore: registered new interface driver cypress cypress_m8: Cypress USB to Serial Driver v1.09
This is the driver that should bind to this device, but for some reason it isn't. Is it also a HID device? Can you provide the output of /proc/bus/usb/devices with the device plugged in?
Here it is: T: Bus=02 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 10 Spd=1.5 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0d9f ProdID=0002 Rev= 0.00 S: Manufacturer=POWERCOM CO., LTD. S: Product=USB to Serial C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA I:* If#= 0 Alt= 0 #EPs= 2 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=10ms E: Ad=02(O) Atr=03(Int.) MxPS= 8 Ivl=10ms
Ah, the hid driver is binding to the device. You need to add a quirk to it to prevent this from happening, I don't know why no one has reported this before.
If you need help generating such a patch, let us know.