First off, using a 2.2.x kernel on Slink was no big deal for me. There was a single error message during boot, but it was just to let me know that /etc/init.d/network didn't need the route -add net lines anymore. 2.2.x automatically configures the parameters for this line on its own.
Personally I never did get the OSS/free in the kernel itself to work. Then again, I didn't try too hard. I invested the $20 in OSS (www.opensound.com) which is a collection of modules providing support for many sound cards -- More than the kernel itself does. Installing OSS is a matter of choosing the platform (Linux 2.2.x glibc UP in my case) and downloading, running the installer, and then the soundon command. Total time to configure is maybe 5-10 minutes. On Sun, 8 Aug 1999, Bill Leach wrote: > This is a case where you most definitely want to read the HOW-TOs! > The normal distribution kernels are compiled without sound support. > The reasons are probably multiple, such as smaller size but in addition > sound hardware is so "non-standard" that it is probably counter productive > to even try to distribute a kernel with sound support compiled in. > > You need to determine the type of sound card that you have. If yours is > a listed card then things will probably go quite smoothly. The generally > big problem that most encounter is that the vast majority of "compatible" > cards are only "compatible" AFTER some sort of DOS based initialization > program has been run. With the old "legacy" cards this _can_ usually be > handled by "cold" booting to DOS followed with a "warm" boot to Linux. > With the PCI and Plug-n-Pray cards I don't think that even that works > (OTOH I think that PCI and PnP are also better supported). > > BE SURE THAT YOU READ THE <kernel-source>/Documentation text files for > sound drivers! > > Install the kernel source (you probably need around 10 Meg free space). > Install the "kernel-package": > (debian/dists/slink/main/binary-all/misc/kernel-package_6.05.deb) > > READ the documentation in /usr/doc/kernel-package/ > Manjo's "README.gz" is an outstanding document and will make kernel > building a pleasure with the added benefit that the package management > system will "know" about your new kernel and if you follow Manjo's > advice then upgrades will not automagically replace your custom kernel. > > Personally, I strongly recommend that you compile the kernel for > "modular" sound support. For many sound cards you HAVE to have the > sound system in modular form (the kernel will fail trying to initialize a > PnP sound card, which it trys to do before PnP is initialized). > AFAIK there are no sound cards (that can be used under Linux) that can > NOT be used as modules so... > > Note that for some sound cards you may HAVE to use a 2.2.x kernel and > that is not a completely trivial upgrade to a slink system. If you do > need to run a 2.2.x kernel be sure that you read the notes on the matter > on debian.org (updates?). > > On Sat, Aug 07, 1999 at 01:50:31PM -0500, Jor-el wrote: > > Hi, > > > > I wasnt too concerned about audio when I installed Slink. Now, > > however, I feel the sudden desire to make my machine talk. The only > > question is how. None of the audio modules required have been installed to > > disk, and 'modconf' doesnt have any audio drivers listed. The install > > guide doesnt make any mention of sound. How the heck do I get started? > > > > TIA, > > Jor-el > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
