From owner-freebsd-current Thu Sep 2 15:24: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id 83E3F14E9D; Thu, 2 Sep 1999 15:23:52 -0700 (PDT) (envelope-from gandalf@vilnya.demon.co.uk) Received: from vilnya.demon.co.uk ([158.152.19.238]) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 11MfFS-000Ibm-0K; Thu, 2 Sep 1999 22:22:26 +0000 Received: from nenya (nenya.rings [10.2.4.3]) by vilnya.demon.co.uk (8.9.3/8.9.1) with SMTP id XAA12724; Thu, 2 Sep 1999 23:24:33 +0100 (BST) (envelope-from gandalf@vilnya.demon.co.uk) Message-ID: <001301bef592$65b2ce80$0304020a@rings> From: "Cameron Grant" To: "Doug Rabson" , "Maxim Sobolev" Cc: , , References: Subject: Re: newpcm Date: Thu, 2 Sep 1999 23:27:52 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > > Unfortunately I can't get it working on my SB16PNP with previously worked > > flamessly with "oldpcm". I've did as you suggested - as it seems to be pnp card > > I've removed all "at isa0 ....", rebuilded and rebooted. But with the new > > kernel I've observed 2 things: (1) my "pnp 1 0 os enable ..." string is no > > longer recognised; (2) SB is no longer works :-(. Following is relevant pieces > > of my dmesg output for both cases: > > Could you send the output of pnpinfo. We are probably missing an ID in the > driver. The new pnp code doesn't need the "pnp 1 0 ..." stuff as it deals > with resource allocation itself without the need for user intervention. this is the second such report i've had; in the previous case the pnp id was present, so i guess there is a problem elsewhere. - cameron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message