*BSD News Article 39358


Return to BSD News archive

Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!hpg30a.csc.cuhk.hk!news.hk.net!howland.reston.ans.net!spool.mu.edu!sgiblab!cs.uoregon.edu!news.uoregon.edu!netnews.nwnet.net!ns1.nodak.edu!plains.NoDak.edu!ortmann
From: ortmann@plains.NoDak.edu (Daniel Ortmann)
Subject: Modem Woes....Something Drastic???
Summary: that dad-blamed sio.c  :-)
Sender: usenet@ns1.nodak.edu (Usenet login)
Message-ID: <D0oKCt.ntA@ns1.nodak.edu>
Date: Mon, 12 Dec 1994 04:26:53 GMT
Nntp-Posting-Host: plains.nodak.edu
Organization: North Dakota Higher Education Computing Network
Lines: 24

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

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?

What is the current state of the sio driver?

Has anyone been using it to complete satisfaction?  (I assume so or I
would have seen a blizzard of problem reports.)

Anyway, I am frustrated to the point that I am ready to re-install the
earlier FreeBeastie com driver.

Comments?

Am I over-reacting?  It has been 4 days of tough work, many dozens of
configurations/compilations/reboots/manual and book pages.

The strangest thing is that I *did* actually get a full speed
connection at 14.4kpbs on my Gateway2000 TelePath modem.  And then NOTHING!