Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA547 ; Thu, 04 Feb 93 23:00:20 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!uniwa!nodecg.ncc.telecomwa.oz.au!tdwyer From: tdwyer@nodecg.ncc.telecomwa.oz.au (Terry Dwyer 4915161) Subject: Probs with 0.2 com-bidir driver Organization: Regional Network Systems Group, Perth Date: Thu, 4 Feb 1993 10:09:29 GMT Message-ID: <1993Feb4.100929.28069@nodecg.ncc.telecomwa.oz.au> Lines: 51 This is my first posting to the net, so I hope you will excuse me if I am re-stating the obvious. I have recently installed Patchkit-0.2 Since patchkit-0.1, I have never been able to get the outgoing side of Chris Demetriou's com drivers working. Both the Singleport, multiport and now the Bidirectional (Patchkit-0.2) drivers have obstinately refused to allow me to talk to the com ports with tip or cu. I also have as a side issue, probably related, a problem with stty which hangs when I do a stty -a < /dev/tty00. I have installed Chris's com driver patches with some difficulty, .rej files for com.c, termios.h, which I installed by hand. With all of the above patches from Chris, I have the same problem. After doing the install, I can use the incoming side of the com line but have never been able to use the outgoing side. With tip, I get a message: Cannot synchronize with hayes call failed with cu: /dev/cua00: Device not configured Bus error I have been completely frustrated in all my attempts to make these ports call out since my first attempt. At one stage (with patchkit-0.1 and the singleport or the multiport driver), I saw a message: Incorrect file descriptor, or something similar, (don't remember the exact message), so I embedded a few printf's in various places in the tip source: cmds.c hayes.c tip.c cu.c etc. The file descriptor tip tries to use is 3, the lock file tip opens is for the device /dev/cua00, and yes, it does create the lock file. I don't know if any of the above is of any use in diagnosing my problem. I'm probably missing something really simple, and will kick myself for being so thick when the solution is supplied. I've seen a number of people with com port problems post here, but minimal replies posted to the net. I assume that any help these posts elicited were mail replies to the individual. I have refrained from posting in the hope that I would see replies to these earlier posts that would help me, but no luck. I would suggest that since the com ports and slip seem to be of sufficient interest to a number of people that future replies to requests for assistance be posted rather than mailed. Sorry for the epic length of my post, Terry