On Tue, Jul 13, 1999 at 01:41:01AM -0500, John Foster wrote: > Michael Merten wrote: > > > > On Mon, Jul 12, 1999 at 01:27:15PM -0400, Bob Bernstein wrote: > > > John Foster <jfoster@augustmail.com> wrote: > > > > > > me. The advice, oft given, to see what resources a card uses in Windows, and > > > then try those, was bad advice indeed for me. It threw me WAY off. The main > > > thing I didn't have a clue about was how to edit isapnp.conf after I had > > > created it with pnpdump. That's what sndconfig did for me, so if you use > > > > I've never tried RedHat, and so I'm not familiar with sndconfig, but I've > > always wondered why Debian didn't have a 'isapnpconfig' script that could > > read a pnpdump file and build a menu of options for generating a proper > > isapnp.conf file (something like what pppconfig does for ppp). Hopefully, > > one of those script (or perl) wizards out there will get time to tackle > > this one day. > -------------------------------------- > That is basically what sndconfig does. I think it is GPLed software, so > I wonder why we don't have it as part of Debian? > BTW I did get it to work after some fiddling with the dependencies. It > did not as yet get the sound working on my system. I will try some other > things. I have never fooled around with the sound on this system (didn't > want it). It is now necessary and I am learning about the isapnptools. I > would appreciate any sage advice as the documentation is pretty sparse, > on what is the exact order to do things. My sound card support is > compiled in the kernel, and pnpdump does yield a /etc/isapnp.conf file. > I seems to find all of the pnp cards, sound and 2 modems installed. Don't compile sound into the kernel. Build it as modules. Also, read the kernel documentation for your specific card in /usr/src/linux/Documentation/sound to learn about the arguments to the modules that you will need to specify when you insert them with modconf. HTH -Dano
Attachment:
pgpcIsOzssJbF.pgp
Description: PGP signature