Date: Thu, 2 Sep 1999 23:10:30 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: Maxim Sobolev <sobomax@altavista.net> Cc: Cameron Grant <gandalf@vilnya.demon.co.uk>, freebsd-multimedia@freebsd.org, committers@freebsd.org, freebsd-current@freebsd.org Subject: Re: newpcm Message-ID: <Pine.BSF.4.10.9909022309000.2081-100000@salmon.nlsystems.com> In-Reply-To: <37CEF360.46F7C88D@altavista.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 3 Sep 1999, Maxim Sobolev wrote: > Cameron Grant wrote: > > > newpcm has now been committed in -current, with functional trident 4dwave, > > es1370, sb and mss support. minimal changes to kernel config should be > > required: > > > > pci devices: > > device pcm0 > > > > isa pnp devices: > > controller pnp0 > > device pcm0 > > 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. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9909022309000.2081-100000>