Date: Thu, 2 Sep 1999 23:27:52 +0100 From: "Cameron Grant" <gandalf@vilnya.demon.co.uk> To: "Doug Rabson" <dfr@nlsystems.com>, "Maxim Sobolev" <sobomax@altavista.net> Cc: <freebsd-multimedia@freebsd.org>, <committers@freebsd.org>, <freebsd-current@freebsd.org> Subject: Re: newpcm Message-ID: <001301bef592$65b2ce80$0304020a@rings> References: <Pine.BSF.4.10.9909022309000.2081-100000@salmon.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001301bef592$65b2ce80$0304020a>