From owner-freebsd-hardware Thu May 16 20:27:24 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA04804 for hardware-outgoing; Thu, 16 May 1996 20:27:24 -0700 (PDT) Received: from xi.dorm.umd.edu (root@xi.dorm.umd.edu [129.2.152.45]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA04799 for ; Thu, 16 May 1996 20:27:18 -0700 (PDT) Received: from localhost (smpatel@localhost [127.0.0.1]) by xi.dorm.umd.edu (8.7.5/8.6.12) with SMTP id XAA23242; Thu, 16 May 1996 23:26:59 -0400 (EDT) Date: Thu, 16 May 1996 23:26:58 -0400 (EDT) From: Sujal Patel X-Sender: smpatel@xi.dorm.umd.edu To: Brandon Gillespie cc: hardware@freebsd.org Subject: Re: PnP Modem: US Robotics In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ Followup to hardware only ] On Thu, 16 May 1996, Brandon Gillespie wrote: > IRQ: 5 > Address: 110 > UART: NS 16550AN > > When FreeBSD boots and probes sio2 it comes up with nothing. Could the > problem lie in the Address? If so, what would be the appropriate > 'port' in the kernel config? Help? :) The PnP bios often has a really tough time trying to figure out where to actually put devices (i.e. it doesn't always get the "conflict free" or "standard" configuration). Win95 also suffers from the same problem. If you grab the Alpha PnP stuff from ftp://freefall.freebsd.org/incoming/ISA_PnP.May5.tar.gz you'll be able to hardcode where you want your modem (probably 3e8, 5). Though this isn't an optimal solution yet, it will get you up and running without much fuss IMO. Sujal