From owner-freebsd-hackers  Mon Dec  9 11:13:00 1996
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id LAA22702
          for hackers-outgoing; Mon, 9 Dec 1996 11:13:00 -0800 (PST)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA22691
          for <hackers@freebsd.org>; Mon, 9 Dec 1996 11:12:54 -0800 (PST)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA14156; Mon, 9 Dec 1996 11:12:17 -0800 (PST)
Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3)
	id sma014154; Mon Dec  9 11:12:03 1996
Received: (from archie@localhost) by bubba.whistle.com (8.7.5/8.6.12) id LAA08117; Mon, 9 Dec 1996 11:12:03 -0800 (PST)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199612091912.LAA08117@bubba.whistle.com>
Subject: Re: FreeBSD doesn't see my modem
In-Reply-To: <32AC545E.475E@ctron.com> from Alexander Seth Jones at "Dec 9, 96 01:03:11 pm"
To: ajones@ctron.com (Alexander Seth Jones)
Date: Mon, 9 Dec 1996 11:12:02 -0800 (PST)
Cc: mgessner@aristar.com, hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL25 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


>   OK, now I'm confused...
> 
>   (1)  Why do I have to do a UserConfig if I've added the device to my
> config file?
> 
>   (2)  When I did the UserConfig it was already enabled, I booted, and
> FreeBSD didn't see it...
> 
>   (3)  When I did a UserConfig "visual" it was also already enabled, so
> I exited, booted, and FreeBSD saw it...
> 
>   In neither case did I make any changes...
> 
>   What's going on?
> 
> -- 
> Alex Jones              |  ajones@ctron.com
> Cabletron Systems, Inc.
> Durham, NH USA 03824

We have had some trouble in the past getting FreeBSD to recognize
certain modems. Cardinal comes to mind. What kind of modem are you using?

The solution was to increase some of the DELAY() calls in sioprobe().
If you go into user config, and set the flags to 0x80, you'll see which
test the probe is failing at.

If this is the problem, you may need to edit /usr/src/sys/i386/isa/sio.c
Look for the comment /* EXTRA DELAY? */ in the function sioprobe() :-)

This of course may not be your particular situation but it's worth
a try.

-Archie

___________________________________________________________________________
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com