Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!doc.ic.ac.uk!marble.uknet.ac.uk!mcsun!sun4nl!foxim!rvh From: rvh@foxim.nl (Roland van Hout) Newsgroups: comp.os.386bsd.questions Subject: Re: Problem with cgd's driver, no one can login! Keywords: 386bsd, cgd bidirectional rs232 driver Message-ID: <1941@foxim.nl> Date: 31 Mar 93 15:34:21 GMT References: <1940@foxim.nl> Organization: Foxim Software, Capelle a/d IJssel, Netherlands Lines: 83 Subject: Re: Problem with cgd's driver, no one can login! Hello guys, Here is my followup since there some people wanted me to share this information. Sorry this one is in dutch > From: rooij@vangogh.isp.cft.philips.nl (Guido van Rooij) > Hmmm..als de getty de CD niet ziet, zou het modem niet op moeten > hangen, en zou een ps -wlax bij de getty het waitchannel comdcd Yeah the ps shows that getty is on the waitchannel comdcd!! > moeten geven. Is dat zo? En..welke versie van com-beta heb je? My version com-beta is 2.1.1 if i'm not mistaken, it's the newest since the patchkit 0.2 and 0.2.1! Answer Guido at guido@gvr.win.tue.nl The next one: From: Daniel Ortmann <ortmann@plains.NoDak.edu> > Did you update /etc/ttys commenting the "console" entry out and changing > it to "vga"? No I don't have a device called /dev/vga and I don't have a VGA card, it's even worse I DON'T USE X-WINDOWS yet! I cannot see the point in changing this anyway? The next one: > From: dsndata!randy (Randy Terbush) > Share your responses. I have the same symptoms, WITHOUT the new 2.2 > patchkit, and a Telebit T2500. I have a Worldblazer on the second port with a 16550. > INET: randyt@cse.unl.edu The next one: > From: Ernie Elu <root@woody.apana.org.au> > One of the things I noticed is that getty won't behave unless > you set you modem to disable echo and run in quiet mode. > ATQ1E0 You have to put the modem quiet and on no echo with every getty/login on every system I know! Otherwise you have the chance that your getty/login start talking with the modem, this gives strange results! > The second thing is I run my modem at 19200 std.19200 in the gettytab. > And let it do the speed negotiation. The port defaults to 7 data even > parity so that mucks things up as well. I have the following string in > my rc.local. stty -f /dev/tty00 cs8 -parenb clocal. That should get > over your DCD problem as well. There is a patched getty under way that > gets over the termios 7e1 default problem. I think Felix Gaehtgens is > working on it. Anything that uses the old sgtty calls puts the port > back to 7date even parity. > Hope this helps It didnot since I already tried setting the port, but it worked fine with or without the 8 bits no parity without the 0.2.1 patchkit and with the cgd com driver! (the old version) So I'm still where it all started, I run a kernel with the standard rs232 driver and remove the getty every time I want to call out, this works but is not very elegant! But I'll keep on trying getting it to run with cgd's driver if I have the time. If someone else still has ideas I'm still looking and listening. Have fun Roland -- Roland van Hout, software engineer at Foxim Software, Capelle a/d IJssel, Netherlands, tel: 010-4588211, fax: 010-4518690, Internet: rvh@foxim.nl ARPA: ...!uunet!mcsun!sun4nl!foxim!rvh