Am 01.04.2013 01:10, schrieb Greg KH:
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?
Results at the end of the mail.
If still needed i can install Ubuntu on an free partition on another PC ?
There is the possibility to upgrade to kernel 3.8.5.
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.
I can't understand why a driver for Mac is provided and not for Linux.
There are so much embedded systems running Linux needing a converter from RS232 to USB.
The fact that this driver even works is pretty amazing at times...
Yes - first i thought the hardware is broken.
There is no error message and sometimes some bytes are received after connection.
I checked the hardware on an PC running windows with the driver from Profilic - it works perfect.
thanks,
greg k-h
Best regards
Karsten
Here the result for PL2303HX:
[ 1626.798549] USB Serial support registered for pl2303
[ 1626.798620] usbcore: registered new interface driver pl2303
[ 1626.798625] pl2303: Prolific PL2303 USB to serial adaptor driver
[ 1666.192803] usb 1-2.3: new full-speed USB device number 8 using ehci_hcd
[ 1666.302378] usb 1-2.3: New USB device found, idVendor=067b, idProduct=2303
[ 1666.302389] usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1666.302396] usb 1-2.3: Product: USB-Serial Controller
[ 1666.302401] usb 1-2.3: Manufacturer: Prolific Technology Inc.
[ 1666.302866] pl2303 1-2.3:1.0: pl2303 converter detected
[ 1666.302881] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: device type: 2
[ 1666.303000] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0xc0:0x1:0x8484:0x0
1 - 2
[ 1666.303121] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0x40:0x1:0x404:0x0 0
[ 1666.303246] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0xc0:0x1:0x8484:0x0
1 - 2
[ 1666.303371] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0xc0:0x1:0x8383:0x0
1 - 0
[ 1666.303496] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0xc0:0x1:0x8484:0x0
1 - 2
[ 1666.303620] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0x40:0x1:0x404:0x1 0
[ 1666.303746] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0xc0:0x1:0x8484:0x0
1 - 2
[ 1666.303996] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0xc0:0x1:0x8383:0x0
1 - 0
[ 1666.304124] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0x40:0x1:0x0:0x1 0
[ 1666.304248] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0x40:0x1:0x1:0x0 0
[ 1666.304373] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0x40:0x1:0x2:0x44 0
[ 1666.304583] usb 1-2.3: pl2303 converter now attached to ttyUSB0
If needed here the result with the old PL2303H:
[ 1847.663884] device-mapper: uevent: version 1.0.3
[ 1847.664722] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-devel@xxxxxxxxxx
[ 1854.074684] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[ 1854.075395] SGI XFS Quota Management subsystem
[ 1854.088576] JFS: nTxBlock = 8192, nTxLock = 65536
[ 1854.149224] NTFS driver 2.1.30 [Flags: R/W MODULE].
[ 1854.201462] QNX4 filesystem 0.2.3 registered.
[ 1854.285428] Btrfs loaded
[ 1863.284587] usb 1-2.3: new full-speed USB device number 9 using ehci_hcd
[ 1863.393057] usb 1-2.3: New USB device found, idVendor=067b, idProduct=2303
[ 1863.393068] usb 1-2.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1863.393590] pl2303 1-2.3:1.0: pl2303 converter detected
[ 1863.393606] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: device type: 1
[ 1863.393797] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0xc0:0x1:0x8484:0x0
1 - 0
[ 1863.393919] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0x40:0x1:0x404:0x0 0
[ 1863.394045] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0xc0:0x1:0x8484:0x0
1 - 0
[ 1863.394169] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0xc0:0x1:0x8383:0x0
1 - 0
[ 1863.394293] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0xc0:0x1:0x8484:0x0
1 - 0
[ 1863.394419] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0x40:0x1:0x404:0x1 0
[ 1863.394544] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0xc0:0x1:0x8484:0x0
1 - 0
[ 1863.394700] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0xc0:0x1:0x8383:0x0
1 - 0
[ 1863.394913] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0x40:0x1:0x0:0x1 0
[ 1863.395038] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0x40:0x1:0x1:0x0 0
[ 1863.395162] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0x40:0x1:0x2:0x24 0
[ 1863.395269] usb 1-2.3: pl2303 converter now attached to ttyUSB0
--
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
