Date: Thu, 12 Sep 1996 22:01:54 -0700 From: hmmm <hmmm@alaska.net> To: dwhite@resnet.uoregon.edu Cc: freebsd-questions <freebsd-questions@FreeBSD.org> Subject: Re: modems Message-ID: <3238EAC2.7155@alaska.net> References: <Pine.BSI.3.94.960913220935.615K-100000@gdi.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug White wrote: > > On Fri, 13 Sep 1996, hmmm wrote: > > > i can't wait for a new sio driver! > I didn't know one was in the works.i recently read somewhere that that was the case. > This is not FreeBSD's fault entirely -- apparently your Hayes requires > some sort of initialization and does not properly initialize at reboot. > Internal modems don't appear to work very well with FreeBSD. I've seen > more problems with unresponsive internals than externals.regarding init - it does have standard Hayes/Inet defaults ... it was brand new. > > so i re-enable sio2. sio3 found immediately. > Hm. If you could figure out just what the Hayes is waiting for we could > fix that up. (I have an external Supra that works wonders).how would i test that out when the kernels probes don't find it at boot time? i would imagine certain kernel table entries get marked as "off/inaccessable" when a probe fails - disallowing use of the device by normal methods.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3238EAC2.7155>