Re: sound compiled into kernel as opposed to a module
Hi,
my opinion is that it is better to compile drivers as modules. When a
device is messed up, you can rmmod and insmod the driver, and sometimes it
works again.
For info about your driver, read the kernel source documents in
/usr/src/linux/Documents/sound/es1371
Usually there is useful information in there, but not in that document.
Generally you do:
modprobe sound
insmod soundlow
insmod soudcore
insmod sound
insmod es1371
(perhaps just 'modprobe sound' and 'insmod es1371' will work too)
then you should be able to cat to /dev/dsp.
Hope it helps
Sebastiaan
On Tue, 20 Mar 2001, Charles Lewis wrote:
> I have a es1371 card and I've compiled support into the kernel (not as a
> module). How does the install process differ? Before all I had to do was go
> into modconf and select it. Now I'm not sure what to do.
>
> It is detecting the card on bootup. I see it in /proc/devices and
> /proc/interrupts but if I cat something to /dev/dsp, I don't get any sound.
> What else do I need to do to make it work?
>
> --
> Charles Lewis
> lewisc@delta.swau.edu
> 817-556-4720
>
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
Reply to: