On 2017-03-03, Jan Stary <h...@stare.cz> wrote: > This is current/amd64 (dmesg below). I got me this > https://www.alza.cz/EN/axago-pcea-s2-d277216.htm > to have two extra serial ports to connect to my ALIXes. > It shows up in dmesg as > > puc0 at pci2 dev 0 function 0 "NetMos Nm9922" rev 0x00: ports: 1 com > com4 at puc0 port 0 apic 2 int 16: st16650, 32 byte fifo > puc1 at pci2 dev 0 function 1 "NetMos Nm9922" rev 0x00: ports: 1 com > com5 at puc1 port 0 apic 2 int 17: st16650, 32 byte fifo > > The kernel boots, but then the booting sequence hangs with > > setting tty flags > > which apparently is the 'ttyflags -a' in /etc/rc. > So I suppose /etc/ttys needs to be edited accordingly. > I tried turning the getty off, but that didn't help: > > console "/usr/libexec/getty std.9600" vt220 off secure > ttyC0 "/usr/libexec/getty std.9600" vt220 on secure > ttyC1 "/usr/libexec/getty std.9600" vt220 on secure > ttyC2 "/usr/libexec/getty std.9600" vt220 on secure > ttyC3 "/usr/libexec/getty std.9600" vt220 off secure > ttyC4 "/usr/libexec/getty std.9600" vt220 off secure > ttyC5 "/usr/libexec/getty std.9600" vt220 off secure > ttyC6 "/usr/libexec/getty std.9600" vt220 off secure > ttyC7 "/usr/libexec/getty std.9600" vt220 off secure > ttyC8 "/usr/libexec/getty std.9600" vt220 off secure > ttyC9 "/usr/libexec/getty std.9600" vt220 off secure > > Commenting them out works, i.e. the boot sequence finishes: > > console "/usr/libexec/getty std.9600" vt220 off secure > ttyC0 "/usr/libexec/getty std.9600" vt220 on secure > ttyC1 "/usr/libexec/getty std.9600" vt220 on secure > ttyC2 "/usr/libexec/getty std.9600" vt220 on secure > ttyC3 "/usr/libexec/getty std.9600" vt220 on secure > #ttyC4 "/usr/libexec/getty std.9600" vt220 off secure > #ttyC5 "/usr/libexec/getty std.9600" vt220 on secure > #ttyC6 "/usr/libexec/getty std.9600" vt220 off secure > #ttyC7 "/usr/libexec/getty std.9600" vt220 off secure > #ttyC8 "/usr/libexec/getty std.9600" vt220 off secure > #ttyC9 "/usr/libexec/getty std.9600" vt220 off secure > > ttyflags(8) says "device-specific flags for terminals". Does > that mean there is something device specific about this particular > serial port card that ttyflags cannot set (doesn't know how to set) > and hangs on it, presumably because my ttys is wrong? I tried > > ttyC4 none vt220 > ttyC4 none vt220 off > ttyC4 none vt220 off local > > but these all hang too. > > What puzzles me is that now it started hanging again > even with ths ttys emtries commented out. > Am I missing something obvious?
ttyC* are for wscons(4) terminals, i.e. ones on your normal monitor, they're nothing to do with this card. The card is providing tty04/tty05 (and their cua equivalents for outward connections) which are unlikely to be "on" in your /etc/ttys (and you probably don't want them to be - presumably these are for connecting out to consoles on the ALIXes and not for allowing other people to login to this machine?). Commenting-out those entries might get you past boot but then it may hang again later when you try to use them. I think I've sometimes seen similar hangs when the card wanted something from the handshake lines that wasn't being provided. If it's not plugged in yet (with a null modem adapter if needed, note not just a gender-changer) then plugging it in might make it come to life. What I tend to do for consoles on PCs is use a DE9-RJ45 adapter, and in that adapter I loop back DTR-DSR and CTS-RTS (so as soon as the computer raises DTR it sees DSR) and just connect GND/RXD/TXD between the machines which avoids a few headaches..
