Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!usenet.ins.cwru.edu!magnus.acs.ohio-state.edu!math.ohio-state.edu!cs.utexas.edu!utnut!torn!nott!cunews!revcan!micor!latour!diana!db From: db@diana.ocunix.on.ca (Dyane Bruce) Subject: NetBSD 0.9/COM driver Message-ID: <1993Nov3.061828.2602@diana.ocunix.on.ca> Organization: db Software Date: Wed, 3 Nov 1993 06:18:28 GMT Lines: 34 Hardware: 486 DX66 + "generic" el cheapo IDE+serial port+Parallel port card 1542C Adapatec SCSI card Software: "Stock" COM driver. (I am going to patch in com-beta-0.2.1 I _need_ bi directionality.) Symptoms: Set up modem for dial in. I dial in, get a string of garbled characters, no login prompt. System doesn't answer the phone anymore. I look at modem, RX+TX leds locked on, but on-hook. Interesting. I double check using local serial connection. ie. no modem. Dropped characters, NetBSD banner does not appear complete... If I do log in, the prompt character does not appear but the shell accepts and prints characters... It appears that the output is dropping characters, not the input. Tried: I tried all combinations of 7 bit 8 bit, 1 stop bit, parity etc. Dropping characters on output, I assume a flow control problem. So, to test that my local terminal wasn't keeping up, (in case flow control wasn't enabled on NetBSD) I dropped the getty down to 2400 bps. Still dropped characters. I find it difficult to believe my local terminal can't keep up to 2400 baud. Anybody else seen this? Anybody have any suggestions? I am going to try dropping the CPU speed down to 16Mhz tmw, just on that off chance it's a buzz loop being used for timing somewhere.... BTW, I know the serial ports aren't great, (A real 16550 card is in the works) but it worked under NeXTSTEP. -- Dyane Bruce db@diana.ocunix.on.ca 29 Vanson Ave. Nepean On, K2E 6A9 Am I the only one who has trouble 613-225-9920 thinking up witty sayings for here?