Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!news.maxwell.syr.edu!ais.net!uunet!in1.uu.net!204.157.146.254!news.usaor.net!usenet From: guest@ Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: enabling serial logins Date: Sat, 26 Apr 1997 12:05:02 GMT Organization: USA OnRamp Lines: 58 Message-ID: <3361ee2e.790113@news.usaor.net> References: <5jsgka$1ih$1@news.fas.harvard.edu> NNTP-Posting-Host: 206.148.130.82 X-Newsreader: Forte Free Agent 1.1/32.230 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:39769 On 26 Apr 1997 09:07:22 GMT, Daniel B Giffin <giffin@fas.harvard.edu> wrote: > > I'd like to login to my FBSD box over the serial line. I >believe I compiled the right drivers in to the kernel (actually, which >two are the ones I see on the back of my PC?) ... > >device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr >device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr >device sio2 at isa? port "IO_COM3" tty irq 5 vector siointr >device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr > >... but bootup messages don't seem very encouraging: > >Apr 9 03:35:08 meursault /kernel: sio0 not found at 0x3f8 >Apr 9 03:35:08 meursault /kernel: sio1 not found at 0x2f8 >Apr 9 03:35:08 meursault /kernel: sio2 not found at 0x3e8 >Apr 9 03:35:08 meursault /kernel: sio3 not found at 0x2e8 > >And what was the kernel expecting to find on the serial line? > >Anyway, I went ahead and modified /etc/ttys to allow login over the >serial interfaces: > ># Serial terminals >ttyd0 "/usr/libexec/getty std.9600" unknown on secure >ttyd1 "/usr/libexec/getty std.9600" unknown on secure >ttyd2 "/usr/libexec/getty std.9600" unknown on secure >ttyd3 "/usr/libexec/getty std.9600" unknown on secure > >... and, firing up my terminal emulator from a machine on the other >end of a serial connection (yes, I think I've got the null-modem >hookup right), I get no response. > >Is there something more I need to do? Thanks for any help. > > >daniel > > As long as the sio's aren't seen during boorup you'll never get tot login. Check to see that the two commons com1and com2 are enabled in your systems bios. After the ports are verified then modify the tty file to enable the login. >ttyd0 "/usr/libexec/getty std.9600" dialup on insecure >ttyd1 "/usr/libexec/getty std.9600" dialup on insecure That should do it, you may even want to replace getty with mgetty0.99 a modem aware getty replacement. Good Luck