On Sun, Mar 31, 2013 at 07:15:22PM +0200, Karsten Malcher wrote: > Am 31.03.2013 18:58, schrieb Greg KH: > >On Sun, Mar 31, 2013 at 06:33:24PM +0200, Karsten Malcher wrote: > >>Am 31.03.2013 17:50, schrieb Greg KH: > >>>On Sun, Mar 31, 2013 at 05:20:06PM +0200, Karsten Malcher wrote: > >>>>Hello, > >>>> > >>>>I have a problem with the PL2303HX chip. > >>>> > >>>>Please refer to this bug: > >>>>http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704242 > >>>> > >>>>Where can i address such a bug? > >>>>How can i debug and help to solve the problem? > >>>Please provide the output of the kernel log when using this device on > >>>the 3.8 kernel release. > >>> > >>>thanks, > >>> > >>>greg k-h > >>It seems that the driver is the same i am using in kernel 3.2.0-3. > >>https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/drivers/usb/serial/pl2303.c?id=v3.8.5 > >> > >>So please don't be angry, but it's much effort of installing and compiling for the same result. > >> > >>The main problem is that there is no special output in the kernel messages with this PL-2303 HX chip. > >>Exactly no message or error appears, the driver simply gives no data that arrives. > >Can you provide the output of 'lsusb -v' with the device plugged in? > > > >thanks, > > > >greg k-h > > Of course. > > First the overview over all devices: > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 001 Device 008: ID 058f:6254 Alcor Micro Corp. USB Hub > Bus 003 Device 002: ID 04d9:1503 Holtek Semiconductor, Inc. Shortboard Lefty > Bus 001 Device 009: ID 16c0:05dc VOTI shared ID for use with libusb > Bus 001 Device 017: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port > Bus 001 Device 011: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader > > > The output of lsusb -v for the device: > (Complete output attached as file) > > > Bus 001 Device 017: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 64 Ok, this should be detected as a HX device by the driver. Can you do, as root, unplug the device and type: rmmod pl2303 dmesg -c modprobe pl2303 debug=1 plug the device in, and then send the output of 'dmesg' that gets sent? I really don't know why prolific decided to change their device, yet use the same device id, and not tell us how to talk to the device at all. The fact that this driver even works is pretty amazing at times... thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
