Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!paladin.american.edu!howland.reston.ans.net!usenet.ins.cwru.edu!eff!news.kei.com!world!ksr!jfw From: jfw@ksr.com (John F. Woods) Newsgroups: comp.os.386bsd.bugs Subject: Re: Dead com0 in NetBSD Message-ID: <36094@ksr.com> Date: 30 Nov 93 15:26:14 EST References: <CHA4Iu.A5L@rucs2.sunlab.cs.runet.edu> Sender: news@ksr.com Lines: 22 bcolbert@rucs2.sunlab.cs.runet.edu (Brad Colbert) writes: > My com0 is dead! I have tip correctly configured, I can tip com0 and > I can watch the lights on my modem blink, I can even dial out, but > tip doesnt display anything (the modem does have verbose and echo on). > When I try to quit tip (~.) it doesnt return me to my shell, it just > sits there in la-la land, I can type and it shows up on the screen but > no cammands are executed and nothing is sent to the modem (after trying > to quit). On a soft-reboot I selected MS-DOS as the os and tried one > of my communication programs and th same thing happend. Not till I did > a hard-boot did I get moy com port back in DOS. > I have 4 com ports all configured in the standard way (ie IRQs and MEM). > Another problem (if thats what it is), I keep getting a message from > the wd driver... > (looks something like the following) > wdc0: Extra interupt (or something like that) Check the hardware configuration REAL HARD. That sounds a lot like what I saw when I had one of my serial ports misjumpered to interrupt on the wrong IRQ level. With all ports correctly configured (:-), I have been able to make use of all four of my com ports under NetBSD 0.8, 0.9, and -current.