From owner-freebsd-current Fri Nov 12 5:24:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from sstar.com (sstar.com [209.102.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 446C614BE5 for ; Fri, 12 Nov 1999 05:24:13 -0800 (PST) (envelope-from king@sstar.com) Received: from MAROON ([134.132.228.8]) by sstar.com with ESMTP (IPAD 2.5s/64) id 4718500; Fri, 12 Nov 1999 07:24:11 -0600 Message-Id: <4.2.0.58.19991112071811.015e8c20@mail.sstar.com> X-Sender: king@mail.sstar.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Fri, 12 Nov 1999 07:24:11 -0600 To: freebsd-current@freebsd.org From: Jim King Subject: Re: pnp and AWE64 In-Reply-To: <4.2.0.58.19991111224704.015fe070@mail.sstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:50 PM 11/11/1999 -0600, Jim King wrote: >I just picked up an AWE64 to use until the Vortex2 driver is working. The >card is detected in Win98, but unfortunately the new PnP code in -current >(cvsup'ed this evening) doesn't seem to find this card at all. Nothing >shows up about it in dmesg; pnpinfo shows my ISA PnP modem, but nothing at >all about the AWE64. One more bit of info: this PC (Dell Dimension R450) has a Phoenix BIOS, which has a setting "Plug-n-Play OS? Yes/No". Changing it from No to Yes made the kernel find the AWE64. Unfortunately changing that setting also made the 3C905B NIC quit working: xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 11 at device 13.0 on pci0 xl0: couldn't map ports/memory device_probe_and_attach: xl0 attach returned 6 Another oddity: Although the AWE64 gets picked up by the pcm driver, pnpinfo still only shows the PnP modem - no mention of the AWE64. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message