From owner-freebsd-questions Sat Sep 14 11:03:58 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA28188 for questions-outgoing; Sat, 14 Sep 1996 11:03:58 -0700 (PDT) Received: from alaska.net (root@calvino.alaska.net [206.149.65.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA28182 for ; Sat, 14 Sep 1996 11:03:55 -0700 (PDT) Received: from hmmm.alaska.net by alaska.net (5.x/SMI-SVR4) id AA12232; Sat, 14 Sep 1996 10:03:41 -0800 Message-Id: <3238EAC2.7155@alaska.net> Date: Thu, 12 Sep 1996 22:01:54 -0700 From: hmmm X-Mailer: Mozilla 2.02 (Win16; I) Mime-Version: 1.0 To: dwhite@resnet.uoregon.edu Cc: freebsd-questions Subject: Re: modems References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk 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.