Minicom And Ncurses

Home » CentOS » Minicom And Ncurses
CentOS 4 Comments

Hi,

I have to do some maintenance on a CentOS 7 proxy installed on a routerboard without a video card. The only way to access this machine directly is via Minicom and serial port.

I’m using NetworkManager TUI (nmtui) to configure network interfaces, but Ncurses rendering in Minicom works in the sense that chickens fly and horses swim. What you get is a forest of question marks with a few barely recognizable options lost in between.

Is there some magical trick to render Ncurses interfaces correctly in Minicom ?

Cheers,

Niki

Microlinux – Solutions informatiques durables
7, place de l’église – 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info@microlinux.fr Tél. : 04 66 63 10 32
Mob. : 06 51 80 12 12

4 thoughts on - Minicom And Ncurses

  • Maybe “export TERM=vt100” ?

    *Matt Phelps*

    *Information Technology Specialist, Systems Administrator*

    (Computation Facility, Smithsonian Astrophysical Observatory)

    Center for Astrophysics | Harvard & Smithsonian

    60 Garden Street | MS 39 | Cambridge, MA 02138
    email: mphelps@cfa.harvard.edu

    cfa.harvard.edu | Facebook <http://cfa.harvard.edu/facebook> | Twitter
    <http://cfa.harvard.edu/twitter> | YouTube <http://cfa.harvard.edu/youtube>
    | Newsletter <http://cfa.harvard.edu/newsletter>

  • Once upon a time, Nicolas Kovacs said:

    I’d guess the TERM is not set correctly. IIRC Minicom by default emulates a traditional VT102 terminal, while the default Linux TERM
    variable is usually “linux” (which is a superset of VT102). Try setting TERM=vt102 first.

    Alternately, if you have screen installed, it can also be used for serial access… run “screen /dev/ttyS0 9600” (change the device and speed as needed). Screen has its own superset of VT102, so you can set TERM=screen, but it is also possibly close enough to the linux terminal emulation to work directly (they’re both ANSI supersets with similar extensions).