VirtualBox

Ticket #3120 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

Serial ports doesn't work on Solaris hosts => fixed in SVN

Reported by: Tipo874 Owned by:
Priority: major Component: uart
Version: VirtualBox 2.2.2 Keywords:
Cc: Guest type: Windows
Host type: Solaris

Description

I noticed that the Changelog for 2.1.2 says that serial ports are now fixed on solaris hosts. Sadly it appears to be just half true. I have tried with both a win XP client and an OpenSolaris client, and neither of them are able to use the external Edgeport USB-serial dongle that works fine on the host OS.

I have looped all relevant signals so that whatever data is sent on TxD will be received on RxD, and when I run "tip -9600 /dev/cua/1" on the host, whatever I type is echoed to the screen. If I try the same with hyperterm in Win XP or "tip -9600 /dev/cua/a" on the OpenSolaris client, nothing shows up on the screen.

Attachments

VBox.log Download (45.9 KB) - added by Tipo874 5 years ago.

Change History

comment:1 Changed 5 years ago by Tipo874

After installing 2.1.4 I notice that it is getting closer.

Output works, but not input.

If I use stty on the host and disable "iexten" on the port, then input also works, like:

stty -iexten </dev/cua/1

comment:2 Changed 5 years ago by ramshankar

Could you please clarify your loopback setup here? I'm not quite sure what you're doing for the loopback and what speeds you've set up. Are you consistently, explicity using the same speed?

comment:3 Changed 5 years ago by Tipo874

I loop transmit data to receive data, and the relevant status signals (6-8-20, 4-5) so that no matter what speed or handshake mode I select, any data sent out on the port should be received back in on the same port.

I have selected 9600 bps, and I have also tested other speeds, but as the speed affects both receive and transmit, it really shouldn't matter as they are the same.

If I use "tip -9600 /dev/cua/1" on the host, everything I type on the keyboard is echoed back on the screen. If I try the equivalent of this on the client, either win xp (hyperterminal) or opensolaris (tip -9600 /dev/cua/a) nothing comes back in unless I *on the host* issue "stty -iexten </dev/cua/1".

From the stty man page: ---

iexten (-iexten) Enable (disable) special control

characters not currently controlled by icanon, isig, ixon, or ixoff: VEOL, VSWTCH, VREPRINT, VDISCARD, VDSUSP, VWERASE, and VLNEXT.

---

comment:4 follow-up: ↓ 5 Changed 5 years ago by ramshankar

Ok i will try to reproduce the setup here, could you attach the VBox.log file for a VM on which this doesn't work?

Changed 5 years ago by Tipo874

comment:5 in reply to: ↑ 4 Changed 5 years ago by Tipo874

Replying to ramshankar:

Ok i will try to reproduce the setup here, could you attach the VBox.log file for a VM on which this doesn't work?

So how is it going?

I have verified the problem on VB 2.2.2 on an snv_114 host (with the updated vboxkern package) and the behavior is the same.

comment:6 Changed 5 years ago by ramshankar

Could you please try the experimental test build from (remove both SUNWvbox and SUNWvboxkern and reinstall) (link expires in 14 days):  http://virtualbox.org/download/testcase/VirtualBox-rel-SunOS-r47512.tar.gz

Note: this build could be unstable in other parts and it's highly recommended you go back to your 2.2.2 once you have tested what is required.

This contains the Serial port fix required.

comment:7 Changed 5 years ago by Tipo874

Yes, this version seems to work.

comment:8 Changed 5 years ago by frank

  • Version changed from VirtualBox 2.1.2 to VirtualBox 2.2.2
  • Summary changed from Serial ports doesn't work on Solaris hosts, even with 2.1.2 to Serial ports doesn't work on Solaris hosts => fixed in SVN

comment:9 Changed 5 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use