From owner-freebsd-questions  Mon Oct 11 14:49:32 1999
Delivered-To: freebsd-questions@freebsd.org
Received: from gfc-mad-proxy.gflesch.com (gfc-mad-proxy.gflesch.com [208.212.82.194])
	by hub.freebsd.org (Postfix) with ESMTP id BD26715092
	for <freebsd-questions@FreeBSD.ORG>; Mon, 11 Oct 1999 14:49:26 -0700 (PDT)
	(envelope-from kwills@gflesch.com)
Received: from gfc-mad-mail.gflesch.com (gfc-mad-mail.gflesch.int [10.1.1.25])
	by gfc-mad-proxy.gflesch.com (8.9.2/8.9.1) with ESMTP id QAA90252;
	Mon, 11 Oct 1999 16:40:43 -0500 (CDT)
	(envelope-from kwills@gflesch.com)
Received: by gfc-mad-mail.gflesch.int with Internet Mail Service (5.5.2448.0)
	id <S9ZRJJNP>; Mon, 11 Oct 1999 16:48:52 -0500
Message-ID: <058BE165CBA8D111A82E0008C79F9E35024860@gfc-mad-dc.gflesch.int>
From: "Wills, Ken" <kwills@gflesch.com>
To: Bob Giesen <giesen@comm.mot.com>, Gary Kline <kline@tera.com>
Cc: giesen <giesen@inil.com>, freebsd-questions@FreeBSD.ORG
Subject: RE: Plug-n-play modem woes
Date: Mon, 11 Oct 1999 16:48:59 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Bob Giesen
> Sent: Monday, October 11, 1999 4:27 PM
> To: Gary Kline
> Cc: giesen; freebsd-questions@FreeBSD.ORG; giesen@comm.mot.com
> Subject: Re: Plug-n-play modem woes
> 
> One thing I did ask them -- and I'd like to ask anyone who has some
> knowledge -- is, since FreeBSD is consistently finding the 
> modem as sio4 upon
> booting, might an alteration to my kernel configuration be 
> able to pick it up
> and let me access it at cuaa4?  I was thinking along the 
> lines of putting a
> line like, "device sio4 at isa? port ____ tty flags 0x____" 
> in my config file,
> rebuilding the kernel, doing a MAKEDEV cuaa4.......  Might 
> something like that
> work?

I haven't done this in quite a while so excuse me if this is not
relevant.

	(1)  Set "PnP OS = No" in your BIOS.
	(2)  Disable both of your com ports (this always made
		it easier to see what was happening...
	(3)  Make sure your kernel has the following

controller	pnp0

From GENERIC on 3.3-STABLE

# Serial (COM) ports
device          sio0    at isa? port "IO_COM1" flags 0x10 tty irq 4
device          sio1    at isa? port "IO_COM2" tty irq 3
device          sio2    at isa? disable port "IO_COM3" tty irq 5
device          sio3    at isa? disable port "IO_COM4" tty irq 9

Change the last two to :

# Serial (COM) ports
device          sio2    at isa? port "IO_COM3" tty irq 5
device          sio3    at isa? port "IO_COM4" tty irq 9

or possibly even:
device          sio2    at isa? port "IO_COM3" tty irq?
device          sio3    at isa? port "IO_COM4" tty irq?
(I can't remember if this was/is allowed...)

Again, apologies if this is just a rehash of what you already been
doing, but this did work for me on a number of systems and a range
of cheap modems.

Ken
						


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