RE: sound question
What about modconf in kernel 2.4? It doesn't seem to work because of the
directories the modules are put in.
brendon
-----Original Message-----
From: Allan F. Caetano [mailto:afct@uol.com.br]
Sent: Tuesday, November 21, 2000 5:23 AM
To: Adam C Powell IV
Cc: Daniel Pittman; Andrew Dixon; debian-user@lists.debian.org;
debian-laptop@lists.debian.org
Subject: Re: sound question
>>>>> "Adam" == Adam C Powell IV <hazelsct@mit.edu> writes:
Adam> Daniel Pittman wrote:
>> Andrew Dixon <andrew_dwight_dixon@yahoo.com> writes:
>> >
>> > Hi All, I just recompiled my kernel so that my sound now works. The
>> > only problem is that I have to enter:
>> >
>> > modprobe nm256
>> >
>> > in order to get the module to load into the kernel. Any body know
how
>> > I can automate this or get it to run at startup.
>>
>> Add the name of any modules you want loaded at startup to the file
>> '/etc/modules'.
Adam> The "right way" to do this is to add it using modconf. But AFAIK
this just adds
Adam> it to /etc/modules (along with any arguments the module might
need).
Actually, modconf(8) also modifies /etc/modules.conf, where the
arguments to the modules are defined. But, you're right, using modconf
is the "right way" to go about it.
cheers,
--
Allan F. Caetano
Universo On Line - EngProd - F: (11) 224 4418
ComVc: 479966 ICQ: 68214944
"Who is this peer that keeps resetting my connection?
I have a broken pipe I wanna hit him with!"
--
To UNSUBSCRIBE, email to debian-laptop-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
Reply to: