[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]

Re: FTDI Consoles appear down

Marc Franquesa mark@l3jane.net
Sat, 2 Apr 2016 22:07:43 GMT

On vie, 2016-04-01 at 20:16 -0400, John Stoffel wrote:

> Can you share your configuration for your serial ports?  Esp the FTDI
> ones?  I suspect you just need to tweak the settings a bit, but it's
> hard to make suggestions until we see what you're using.

Sure, here is my configuration (with some added comments for

config * {
    primaryport 3109;
    defaultaccess rejected;
    logfile /srv/con-buffer/local-server.log;

default * {
    timestamp 1hab;
    baud 115200;
    parity none;
    logfile /srv/con-buffer/con-&.log;
    logfilemax 2m;
    motd "----- Out-Of-Band Management Console Server
    options unloved;
    rw *;
    master localhost;
    protocol raw;

# This console doesn't work (it shows as down)
console plug {
    aliases ender;    

device /dev/serial/by-id/usb-FTDI_SheevaPlug_JTAGKey_FT2232D_B_FTVB6MLG-if01-port0;
    master localhost;
    type device;

# This one works
console cubie {
    aliases wigan;
    device /dev/serial/by-path/pci-0000:00:1d.7-usb-0:4.3:1.0-port0;
    master localhost;
    type device;

# This is a RaspberryPi, it works
console pi2 {
    aliases mona;
    device /dev/serial/by-path/pci-0000:00:1d.7-usb-0:4.1.4:1.0-port0;
    master localhost;
    type device;

# Router, it doesn't work
console mikrotik {
    aliases ax-ginza;
    baud 115200;
  device /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AI0388XH-if00-port0;
    master localhost;
    type device;

> You can also look in the conserver archives for some hints.  I found
> one that *might* be useful:
> console ttyb {
>         type device;
>         device /dev/term/b;
>         protocol raw;
>         baud 9600;
>         parity odd;
>         options cstopb;
> }

This configuration shouldn't work for me, I need no parity, a 1 stop

As addtiional info (also for the rest of replies which I'm very grateful
for), some facts:

- None of the devices is a 'real/pure' serial (RS232), all are USB
serial devices based on Prolific PL232 or FTDI2232 variants.
- Maybe (not sure of this) this is the reason I have not 'cu' device (in
reference to the reply given by Bryan Stansell
- For the same fact I think they didn't implement any DCD, CTS, or any
other serial feature. I think they simply work as 'null-modem' RxTx

>From my point of view, the most important fact is that with a very basic
(simply configured speed, no parity, 8bit, 1stop) configuration for
minicom and conserver, one works and the other don't, so I think more
about some pre-check conserver is doing that minicom not. 

In reference to the comment by Chris Fowler, I don't know if conserver
is using DCD, didn't found any thing in the configuration neither the

Thanks much for feedback and the quick responses.