Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!howland.reston.ans.net!wupost!newsfeed.rice.edu!rice!news.Rice.edu!rich From: rich@Rice.edu (Richard Murphey) Subject: Re: [NetBSD] Slattach problems. In-Reply-To: sander@edsi.plexus.COM's message of Tue, 13 Jul 1993 19:11:41 GMT Message-ID: <RICH.93Jul17115350@kappa.Rice.edu> Lines: 17 Sender: news@rice.edu (News) Reply-To: Rich-Murphey@Rice.edu Organization: Department of Electrical and Computer Engineering, Rice University References: <1993Jul13.191141.5981@edsi.plexus.COM> Date: Sat, 17 Jul 1993 17:53:50 GMT >>>>> In article <1993Jul13.191141.5981@edsi.plexus.COM>, sander@edsi.plexus.COM (Scott Anderson) writes: Scott> I have a 486dx33 with 2 com ports. (com0 and com1). Com0 is a mouse. Scott> Com1 is a serial port that can act as a serial terminal just fine (19200 Scott> 7N1 worked just fine) Now when I try to set up a slattach on the port to Scott> set up a slip connection I get a device not configured error. I'm Scott> confused, if the port is working, how can it NOT be configured? The Scott> error message is like innaproprite TIOGCTL (I'm not sure, but this is close) did you put pseudo-device sl 2 in your kernel config file? If not, you don't have the slip driver linked into your kernel and you'll get a 'device not configured' error message. Rich