Bug 78050

Summary:	minicom won't connect to mgetty over nullmodem cable
Product:	[Retired] Red Hat Linux	Reporter:	Wouter Liefting <liefting>
Component:	minicom	Assignee:	Eido Inoue <havill>
Status:	CLOSED WORKSFORME	QA Contact:	Brock Organ <borgan>
Severity:	low	Docs Contact:
Priority:	medium
Version:	8.0
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-01-22 17:36:52 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 Wouter Liefting 2002-11-18 14:52:16 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.75 [en] (Windows NT 5.0; U)

Description of problem:
Minicom won't connect to mgetty over a nullmodem cable. This used to work under 7.3. There are other bugs as well: with LANG=en_US.UTF-8 and LANG=C minicom 
won't always recognise Ctrl-A to get into the menu, and after running minicom, I need to reset my terminal with reset.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install a Red Hat 8.0 with mgetty and run mgetty on the serial port (in /etc/inittab: s1:2345:respawn:/sbin/mgetty -r ttyS0)
2. Install another Red Hat 8.0 and connect both with a (known working) null-modem cable
3. Start minicom. Set serial port options to 38400 8N1, and disable Init and Reset strings.
	

Actual Results:  Should show a login prompt and behave correctly w/ regards to keyboard input

Expected Results:  Does not show a login prompt. Ctrl-A works only occasionally. Afterwards the terminal is in a "echo off" state and needs a "reset" to work 
properly.

Additional info:

I have tried this under LANG=en_US.UTF=8 and LANG=C. No difference.

I have also downgraded to the minicom supplied with Red Hat 7.3. No difference either. I suspect it's got to do with the change of locale from iso<something> to 
UTF-8, 
but can't confirm this.

Comment 1 Mike A. Harris 2002-11-20 16:15:22 UTC

Run minicom with LANG=en_US

Most likely it is not UTF-8 aware

Comment 2 Mike A. Harris 2002-11-20 16:18:25 UTC

Does the above work for you?

Comment 3 Wouter Liefting 2002-11-26 09:52:02 UTC

I couldn't reproduce the exact error. Both with and without LANG=en_US minicom works fine - well, at least it connects properly. I think I did 
something wrong the first time.

In an xterm (GNOME terminal) minicom now works OK, but on a VT, the borders around the menus don't show up. So there *IS* a problem related 
to the terminal, but it is not as severe as I thought.

Running minicom in an xterm is good enough for me. AFAIC, the bug can be closed.

Comment 4 Eido Inoue 2003-01-22 17:36:52 UTC

minicom has some problems regarding drawing boxes with ncurses, which should be
fixed with an ncurses upgrade. I was, however, able to use Ctrl-A and connect.