Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!news.mira.net.au!otis.apana.org.au!serval.net.wsu.edu!netnews.nwnet.net!oracle.pnl.gov!osi-east2.es.net!cronkite.nersc.gov!dancer.ca.sandia.gov!overload.lbl.gov!agate!howland.reston.ans.net!spool.mu.edu!caen!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.questions Subject: Re: Modem Woes....Something Drastic??? Date: 13 Dec 1994 04:03:12 GMT Organization: Montana State University, Bozeman Montana Lines: 42 Message-ID: <3cj6e0$79m@pdq.coe.montana.edu> References: <D0oKCt.ntA@ns1.nodak.edu> NNTP-Posting-Host: bsd.coe.montana.edu In article <D0oKCt.ntA@ns1.nodak.edu>, Daniel Ortmann <ortmann@plains.NoDak.edu> wrote: >So far I know of 4 people who have had serious modem problems: > - sio not recognized on startup > - able to dial (and hear the connect) but unable to sustain the connection The cause for the latter in almost 100% of the cases I've been aware of is a IRQ problem. Two devices are trying to use the same interrupt, and in real OS's this won't work. The serial port not recognized on startup is something completely different. >After many days of bleary-eyed configuration and kernel hacking, I've >come to the tentative conclusion that the sio driver is flawed. Some >of the comments lead me to believe that there is serious work >currently being performed on the driver....Is that true? There is always work being done on the driver, but it's fairly stable. >Has anyone been using it to complete satisfaction? (I assume so or I >would have seen a blizzard of problem reports.) It works great on my box, but I wish that stupid modem was better. Using the new Rockwell chip based modem I get tons of serial overflows while my Intel internal modem works like a champ. I don't blame that on the driver, since changing hardware makes it work. >Anyway, I am frustrated to the point that I am ready to re-install the >earlier FreeBeastie com driver. It's almost the same, except for bug-fixes. :-) Nate -- nate@bsd.coe.montana.edu | FreeBSD dude and all around tech. nate@cs.montana.edu | weenie. work #: (406) 994-5980 | Unemployed, looking for permanant work in home #: (406) 586-0579 | CS/EE field.