From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: UPS USB serial device is not detected properly
Date: Sat, 27 Dec 2008 17:53:39 +0000 [thread overview]
Message-ID: <20081227175339.GA26904@kroah.com> (raw)
In-Reply-To: <cfb54190812261135p6ec0a750h2194c784a44424d2@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1252", Size: 2349 bytes --]
On Sat, Dec 27, 2008 at 01:14:56PM +0200, Hai Zaar wrote:
> On Sat, Dec 27, 2008 at 12:23 AM, Greg KH <greg@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
> --
> Zaar
>
>
> 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
9f, idProduct\002
> >> 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\x02 Lev\x01 Prnt\x01 Port\x02 Cnt\x01 Dev#= 10 Spd=1.5 MxCh= 0
> D: Ver= 1.00 Cls\0(>ifc ) Sub\0 Prot\0 MxPS= 8 #Cfgs= 1
> P: Vendor
9f ProdID\002 Rev= 0.00
> S: Manufacturer=POWERCOM CO., LTD.
> S: Product=USB to Serial
> C:* #Ifs= 1 Cfg#= 1 Atr MxPwr\x100mA
> I:* If#= 0 Alt= 0 #EPs= 2 Cls\x03(HID ) Sub\0 Prot\0 Driver=usbhid
> E: Ad(I) Atr\x03(Int.) MxPS= 8 Ivl\x10ms
> E: Ad\x02(O) Atr\x03(Int.) MxPS= 8 Ivl\x10ms
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.
thanks,
greg k-h
next prev parent reply other threads:[~2008-12-27 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 19:35 UPS USB serial device is not detected properly Hai Zaar
2008-12-26 22:23 ` Greg KH
2008-12-27 11:14 ` Hai Zaar
2008-12-27 17:53 ` Greg KH [this message]
2008-12-27 18:03 ` Hai Zaar
2008-12-29 21:48 ` Hai Zaar
2009-01-28 6:16 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081227175339.GA26904@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).