Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionThorsten Hesemeyer
2012-09-05 14:40:13 UTC
Description of problem:
USB to serial converters and USB to serial modem devices are detected in a virtual Windows guest and can be used without error messages, but communication does not (fully) work.
Version-Release number of selected component (if applicable):
usbredir-0.4.3-1.el6.x86_64
How reproducible:
Attach a Digitus DA-70146 device or similar.
Steps to Reproduce:
1. Boot RHEL 6.3
2. Start a virtual Windows system
3. Attach an usb to serial converter
4. Enable usbredirection if not done automatically
5. Device is detected by Windows
Status: new device shows up in device manager with yellow esclamation mark
6. install manufacturer windows device drivers
Status: device and COM port are listed in device manager - perfect
7. start a terminal application like "putty", configure to COM port usage
8. attach a modem to the converter for testing
9. in terminal program enter some commands like:
ATE1Q0M1X3
ATDT1234567
STATUS: no local echo from modem - allthough enabled via E1
STATUS: no status messages like "OK" - allthough enabled via Q0
STATUS: modem starts dialing
Actual results:
Communication seems to be working one-way only.
PC -> Serial outbound - works
Serial -> PC inbound - does not work
Expected results:
Communication works both ways (In and out).
Additional info:
export G_MESSAGES_DEBUG=all SPICE_DEBUG=1 remote-viewer spice://localhost:5901
excerpt from pressing and transmitting keys using putty attached.
This is no hardware issue - serial communication works well, using native Linux only.
Hi,
This sound very much like it is a dup of bug 834560, this Fedora package has a fix for that issue:
http://koji.fedoraproject.org/koji/buildinfo?buildID=344919
Can you try upgrading your usbredir package to this build (I know this is for Fedora, but it should work fine on
RHEL too), and see if that fixes things?
Thanks,
Hans
Comment 3Thorsten Hesemeyer
2012-09-19 12:07:21 UTC
Hi,
thank you, tested and issue is solved with the newer usbredir version.
Closeing as duplicate then.
Kind regards,
Thorsten
*** This bug has been marked as a duplicate of bug 834560 ***
Description of problem: USB to serial converters and USB to serial modem devices are detected in a virtual Windows guest and can be used without error messages, but communication does not (fully) work. Version-Release number of selected component (if applicable): usbredir-0.4.3-1.el6.x86_64 How reproducible: Attach a Digitus DA-70146 device or similar. Steps to Reproduce: 1. Boot RHEL 6.3 2. Start a virtual Windows system 3. Attach an usb to serial converter 4. Enable usbredirection if not done automatically 5. Device is detected by Windows Status: new device shows up in device manager with yellow esclamation mark 6. install manufacturer windows device drivers Status: device and COM port are listed in device manager - perfect 7. start a terminal application like "putty", configure to COM port usage 8. attach a modem to the converter for testing 9. in terminal program enter some commands like: ATE1Q0M1X3 ATDT1234567 STATUS: no local echo from modem - allthough enabled via E1 STATUS: no status messages like "OK" - allthough enabled via Q0 STATUS: modem starts dialing Actual results: Communication seems to be working one-way only. PC -> Serial outbound - works Serial -> PC inbound - does not work Expected results: Communication works both ways (In and out). Additional info: export G_MESSAGES_DEBUG=all SPICE_DEBUG=1 remote-viewer spice://localhost:5901 excerpt from pressing and transmitting keys using putty attached. This is no hardware issue - serial communication works well, using native Linux only.