Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!usenet.ins.cwru.edu!news.csuohio.edu!stever From: stever@csuohio.edu (Steve Ratliff) Subject: Re: FreeBSD & Modem unusable :-( Message-ID: <1994Jun25.182309.3687@news.csuohio.edu> Sender: news@news.csuohio.edu (USENET News System) Organization: Cleveland State University X-Newsreader: TIN [version 1.2 PL2] References: <772309400snz@bstone.demon.co.uk> <1994Jun22.234503.4965@news.csuohio.edu> <772410050snz@bstone.demon.co.uk> <2ud6hg$de6@panix3.panix.com> Date: Sat, 25 Jun 1994 18:23:09 GMT Lines: 26 Bill Paul (wpaul@panix.com) wrote: : Daring to challenge the will of the almighty Leviam00se, : Ian Steel (Ian@bstone.demon.co.uk) had the courage to say: : : In article <1994Jun22.234503.4965@news.csuohio.edu> : : stever@csuohio.edu "Steve Ratliff" writes: : [munch] : : > [deleted] : [munch] : It's supposed to be: comcontrol /dev/tty01 bidir : ^^^^^ : Of course you're getting a 'device not configured' error: you're : trying to turn on a device by accessing a device that isn't turned : on yet. It's a chicken and the egg problem. Use the comcontrol on : /dev/tty01 first, then /dev/cua01 will be accessible. You're the : unfortunate victim of somebody else's temporary memory lapse, I'm afraid. :) : It was definately a memory lapse :) (sheepish grin). That's what happens when you post from memory. If you still get a device not configured when using the correct device tty01 with comcontrol it could also be that you did not do either a make clean or a rm -rf /sys/compile/YOUR_KERNEL_NAME in your kernel make directory. Config doesn't always pick up on "option" changes. Steve