serial comms corruption

Questions about Wine on Linux
Locked
jpyle490
Newbie
Newbie
Posts: 3
Joined: Thu May 28, 2015 12:24 pm

serial comms corruption

Post by jpyle490 »

Hello,

My first adventure in Wine involves the need to access the serial port and I'm having some problems I haven't seen referenced in other posts. This is on Linux Mint 17.1 64-bit on a Dell Latitude D630 laptop with Wine v1.7.38, also reproducible on v1.6.2. 1.7.38 came from the WineHQ Ubuntu PPA, and 1.6.2 came from the standard Ubuntu repo.

My ultimate goal is to run N1MM Logger (or N1MM Logger+), an amateur radio contest logging program. I couldn't make either happy talking to the radio across the serial port so my intermediate goal became to try to get Teraterm to talk to a Cisco router I had laying around. This is where things got interesting.

If I run minicom natively in Linux, all is well. If I run Teraterm through Wine, it almost works but not really. Some keystrokes are echoed back to the terminal, but overall things are laggy and distorted. In short, the whole thing looks corrupt, as if many of the characters coming from the router never make it to the terminal.

This is on a hardware serial port:

Code: Select all

/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
	Baud_base: 115200, close_delay: 50, divisor: 0
	closing_wait: 3000
	Flags: spd_normal skip_test
Having said that, the same thing happens when I test with a Prolific-based USB-to-RS232 adapter instead. Solid on minicom, unusable on Wine+Teraterm.

I started Teraterm with full debugging (WINEDEBUG=warn+all wine ttermpro.exe). The only output I saw relevant to serial communication was this:

Code: Select all

fixme:comm:set_queue_size insize 8192 outsize 2048 unimplemented stub
I've read a handful of howtos for serial communication through Wine and N1MM specifically. None seem to mention this corruption issue. I have seen the registry situation addressed where a program may not "see" a COM port, and that may be relevant for the Logger+ flavor of N1MM, but clearly we have something else more sinister going on.

Advice and direction are most appreciated.


- Jeff
jpyle490
Newbie
Newbie
Posts: 3
Joined: Thu May 28, 2015 12:24 pm

Re: serial comms corruption

Post by jpyle490 »

Additional testing... I compiled 1.7.43 on Mac OS X Mavericks via Macports and created a 32-bit wineprefix just as on the Mint system. No hardware serial port on this one so I used a USB adapter, this time FTDI-based.
User avatar
dimesio
Moderator
Moderator
Posts: 13367
Joined: Tue Mar 25, 2008 10:30 pm

Re: serial comms corruption

Post by dimesio »

File a bug.
jpyle490
Newbie
Newbie
Posts: 3
Joined: Thu May 28, 2015 12:24 pm

Re: serial comms corruption

Post by jpyle490 »

Filed #38690.
Locked