Bug 250723
Summary: | PL-2303 will not attach to /dev/ttyUSB0, BUT will attach to /dev/ttyUSB when using usbserial module (with arguments, vendor.product) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Shahmat Dahlan <shahmatd> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | f7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-08-03 13:14:23 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Shahmat Dahlan
2007-08-03 08:43:17 UTC
FC5 reached end-of-life for support over a month ago, so this bug will not be fixed in an FC5 kernel update. FWIW, I can say definitively that pl2303 devices do work in the latest fedora kernels, as I've got one myself, running under Fedora 7. I have looked into this and I am certain that pl2303 never supported a vendor 0x0b63. The 0x067b is the correct VID for Prolific. I can see that running both of these modprobe usbserial vendor=0x0b63 product=0x6530 modprobe usbserial vendor=0x067b product=0x6530 will be displayed at the dmesg output that usb 1-1: generic converter now attached to ttyUSB0 But this doesn't seem to be working with this application that we have. Is there anyway I suppose I can test this out I tried testing using minicom, but I couldn't get anything outputs at all and according to the status, its offline and I did configure the serial port settings and all, but couldn't get anything out. Ran these and the following are the outputs, I assume that if you can see the informations stated below, would indicate that it's running ok somehow. [root@FC5 ~]# stty -a -F /dev/ttyUSB0 speed 9600 baud; rows 0; columns 0; line = 0; intr = <undef>; quit = <undef>; erase = <undef>; kill = <undef>; eof = <undef>; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = <undef>; stop = <undef>;susp = <undef>; rprnt = <undef>; werase = <undef>; lnext = <undef>; flush = <undef>; min = 1; time = 0; -parenb -parodd cs8 hupcl -cstopb cread -clocal -crtscts -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ixoff-iuclc -ixany -imaxbel -iutf8 -opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 -isig -icanon iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop -echoprtechoctl echoke Well, duh. Of course a generic won't work if the chip is really a Prolific. I think generic cannot take traffic through an interrupt endpoint. The right course of action is to add the missing IDs to pl2303.c. So, which ID is it? The original report of August 3 says 0x06b3. |