Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!darwin.sura.net!howland.reston.ans.net!xlink.net!subnet.sub.net!ppcnet.ppc.sub.org!rumtifsl.ruessel.sub.org!strix.cluster.sub.org!ura From: ura@strix.cluster.sub.org (Ulf Andrick) Subject: Modem problems Organization: Nocturnal Unix System in Kaiserslautern, Germany Message-ID: <CDnv5K.u7@strix.cluster.sub.org> X-Newsreader: TIN [version 1.1 PL8] Date: Mon, 20 Sep 1993 16:29:29 GMT Lines: 57 After all, I got the 0.2.4 patch kit installed. I have two questions now, resp. serial i/o. Question 1: When I configure sio devices and `make depend', I get: sh /usr/bin/mkdep -I. -I../.. -I../../sys -DSTRIX -Di386 -DCOM_BIDIR -DPCFS -DTCP_COMPAT_42 -DCOMPAT_43 -DUCONSOLE -DXSERVER -DNFS -DISOFS -DINET -Di387 -DKERNEL -Di386 -DNPX ../../isofs/isofs_bmap.c ../../isofs/isofs_lookup.c ../../isofs/isofs_node.c ../../isofs/isofs_util.c ../../isofs/isofs_vfsops.c ../../isofs/isofs_vnops.c ../../kern/dead_vnops.c ../../kern/init_main.c ../../kern/init_sysent.c ../../kern/kern__physio.c ../../kern/kern_acct.c ../../kern/kern_clock.c ../../kern/kern_descrip.c ../../kern/kern_execve.c ../../kern/kern_exit.c ../../kern/kern_fork.c ../../kern/kern_kinfo.c ../../kern/kern_ktrace.c ../../kern/kern_malloc.c ../../kern/kern_proc.c ../../kern/kern_prot.c ../../kern/kern_resource.c ../../kern/kern_sig.c ../../kern/kern_subr.c ../../kern/kern_synch.c ../../kern/kern_time.c ../../kern/kern_xxx.c ../../kern/spec_vnops.c ../../kern/subr_log.c ../../kern/subr_prf.c ../../kern/subr_rlist.c ../../kern/subr_xxx.c ../../kern/sys_generic.c ../../kern/sys_process.c ../../kern/sys ../../i386/isa/sio.c:1360: macro or #include recursion too deep mkdep: compile failed. *** Error code 1 Stop. What can I do about that error? Question 2: The real problem is that I can't talk to my modem. There was a time when I could connect to the modem using tip. When I typed `at' then, the modem would answer `OK'. More interesting dialogues also were possible. But now, it seems that I can't transmit any single character to the modem with a shell command. `echo' simply hangs. `cat' exits, but the device is busy afterwards. This problem already appeared when I hadn't installed the patch kit, with cgd's com driver. However, uucico worked fortunately and it would even exit, when the call was successful. With the pk com driver, it hangs at the end of a successful communication and I have to start uuxqt manually and reboot the machine to get rid of the process. I think what I did last with the modem was to configure `at&D3', but I thought, it still worked afterwards. I don't know if I really saved that or whether some other `at&d' configuration prevailed. By the way, it's an internal V32bis modem. So, is there a way to get back control over the modem? I would be grateful for comments or suggestions. -- Ulf Andrick ura@strix.cluster.sub.org