This is a redhat guide:
http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/ch-custom-kernel.html

Possibly more up to date is the Fedora guide:
http://www.mjmwired.net/resources/mjm-kernel-fc4.html

There are many others out there, another approach may be just to grab
a different kernel (such as the fedora one) and give it a go.

On 29/12/06, Zeth Green <[log in to unmask]> wrote:
> My approach would be to download the latest kernel, unpack the archive
> somewhere (such as /usr/src/linux-2.6.19 then go into the directory
> and type "make menuconfig". Then build all the relevant ALSA drivers
> into the kernel (i.e., as * not as M). Then do make && make
> modules_install then copy the image to /boot and finally add an entry
> to your boot loader.
>
> This always works for me (using any distribution) however there should
> hopefully be a less technical way of doing this, I do not have a
> scientific Linux system here (I am away for Christmas) so I cannot
> provide more specific instructions. Perhaps someone else
> could guide you through recompiling your kernel on SL?
>
> On 27/12/06, Francois Colonna <[log in to unmask]> wrote:
> > Troy Dawson wrote:
> > > Francois Colonna wrote:
> > >> Hello
> > >>
> > >> alsaconf detects "hda intel", in fact its seems (from Windows) that
> > >> it is a "Realtek hda" sound card, how to be sure ?
> > >>
> > >> Thanks
> > >> François Colonna
> > >
> > > usually the best way I know of is to do a
> > >   lspci
> > > on the linux side.
> > > Troy
> > Thanks,  I did it.
> >
> > alsamixer gave me the answer : the card is an Intel and the  chipset a
> > Realtek !
> > So both are correct.
> > This does not help for the sound problem anyway.
> > I have read that there may be a bug in the alsa driver, how to check it ?
> >
> > Best,
> > Francois
> >
>