From owner-freebsd-questions  Thu Sep 14  9:58:25 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28])
	by hub.freebsd.org (Postfix) with ESMTP id 293C637B423
	for <freebsd-questions@FreeBSD.ORG>; Thu, 14 Sep 2000 09:58:22 -0700 (PDT)
Received: from tera.com (athena.sea.tera.com [207.224.230.169])
	by gershwin.tera.com (8.9.3/8.9.3) with ESMTP id JAA13755;
	Thu, 14 Sep 2000 09:58:18 -0700 (PDT)
Received: by tera.com (8.8.8+Sun/SMI-SVR4)
	id JAA24303; Thu, 14 Sep 2000 09:58:17 -0700 (PDT)
Date: Thu, 14 Sep 2000 09:58:17 -0700
From: Gary Kline <kline@tera.com>
To: Antoine Beaupre <beaupran@IRO.UMontreal.CA>
Cc: freebsd-questions@FreeBSD.ORG
Subject: Re: PnP modem not recognized at boot, but by pnpinfo(8)
Message-ID: <20000914095817.A24290@athena.sea.tera.com>
References: <Pine.LNX.4.21.0009141151590.1259-100000@blc24.IRO.UMontreal.CA>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95us
In-Reply-To: <Pine.LNX.4.21.0009141151590.1259-100000@blc24.IRO.UMontreal.CA>; from Antoine Beaupre on Thu, Sep 14, 2000 at 12:15:02PM -0400
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Sep 14, 2000 at 12:15:02PM -0400, Antoine Beaupre wrote:
> Hi!
> 
> I've upgraded my machine to FreeBSD 4.1 release recently (clean
> install) and the kernel is not recognizing my modem. (Please note that
> I've read the FAQ, the handbook, searched the mailing lists, read a few
> man pages and hacked some of the kernel source, still no luck. Please read
> on.) I'm thinking of sending this to -hackers, since it's recognized by
> pnpinfo(8) and not on boot (is this normal?).
> 
> Extract from dmesg output:
> 
> sio2: configured irq 5 not in bitmap of probed irqs 0
> [...]
> unknown: <CIRRUS LOGIC PnP V34 MODEM> can't assign resources
> [full dmesg output included at the end of this mail]
> 

	[[ ... ]]

> 
> If I get this to work, I'll submit a PR for the FAQ entry, and the sio.c
> source, but right now, I don't know how to work this out, so a PR will be
> my last resort. There must be something I missed. I fear that the modem
> _might_ just be a winmodem, but then, it would never have worked out in
> FBSD 2/3.x...
> 


	Here is a long-shot suggestion: check your BIOS configuration
	to be certain that it matches with what the probe is looking
	for.  Something very similar happened to me when trying to
	configure my backup FreeBSD-4.0 system with a modem on ``COM2''
	and the problem was an incorrectly set BIOS.

	gary




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message