1 |
Paul Hartman wrote: |
2 |
> On Thu, Nov 5, 2009 at 10:13 AM, Dale <rdalek1967@×××××.com> wrote: |
3 |
> |
4 |
>> Canek Peláez Valdés wrote: |
5 |
>> |
6 |
>>> On Thu, Nov 5, 2009 at 9:25 AM, Grant <emailgrant@×××××.com> wrote: |
7 |
>>> |
8 |
>>> |
9 |
>>>>>>>> But I get the warning about "Module snd_hda_intel not found" which is |
10 |
>>>>>>>> the built-in chip. |
11 |
>>>>>>>> |
12 |
>>>>>>>> |
13 |
>>>>>>> That's because you don't have that module, it's built into the kernel. |
14 |
>>>>>>> This also means the the options lines in alsa.conf will not do anything. |
15 |
>>>>>>> |
16 |
>>>>>>> |
17 |
>>>>>> OK, so I need to build them as modules, or I need to change those |
18 |
>>>>>> lines in alsa.conf? If I can avoid building them as modules I'd like |
19 |
>>>>>> to. How can those lines be written when the drivers are built into |
20 |
>>>>>> the kernel? |
21 |
>>>>>> |
22 |
>>>>>> |
23 |
>>>>> This is from /etc/conf.d/alsasound: |
24 |
>>>>> |
25 |
>>>>> # LOAD_ON_START: |
26 |
>>>>> # Do you want to load sound modules when alsasound starts? |
27 |
>>>>> # Note: The Gentoo ALSA developers encourage you to build your sound |
28 |
>>>>> # drivers into the kernel unless the device is hotpluggable or |
29 |
>>>>> # you need to supply specific options (such as model= to HD-Audio). |
30 |
>>>>> # no - Do not load modules |
31 |
>>>>> # yes - Load modules |
32 |
>>>>> LOAD_ON_START="yes" |
33 |
>>>>> |
34 |
>>>>> I've never had a hot-pluggable sound card, so I can only guess whether |
35 |
>>>>> hald would somehow load that sound module for you. |
36 |
>>>>> |
37 |
>>>>> So say LOAD_ON_START="no", compile the on-board sound driver into the |
38 |
>>>>> kernel and do the other one as a module -- and let us know if it works |
39 |
>>>>> when you plug it in :o) |
40 |
>>>>> |
41 |
>>>>> |
42 |
>>>> Thanks, I will try that right away. Is it necessary for me to keep |
43 |
>>>> the USB sound driver as a module since it could be plugged in or not? |
44 |
>>>> I can't build that one in too? |
45 |
>>>> |
46 |
>>>> |
47 |
>>> Of course you can. If the module is not being used (i.e., the USB card |
48 |
>>> is not connected), it barely uses resources. In my desktop I have the |
49 |
>>> gspca webcam module built-in, even if my webcam is not connected all |
50 |
>>> the time. The same thing with things like USB gamepads. |
51 |
>>> |
52 |
>>> Regards. |
53 |
>>> |
54 |
>>> |
55 |
>> I agree. I have USB stuff and I don't use any modules except the nvidia |
56 |
>> driver. Modules are I think a handy when you need to switch things on |
57 |
>> and off but I have never used a module except to test a driver to see |
58 |
>> which driver I need. Even then I go back and compile it in. |
59 |
>> |
60 |
> |
61 |
> I'm the opposite, I prefer to do everything as a module when possible |
62 |
> (except for a few core drivers required to be built-in for booting). |
63 |
> Trying different models for alsa hda-intel module would have been no |
64 |
> fun if i had to reboot every time. rmmod and modprobe is so much |
65 |
> faster. :) |
66 |
> |
67 |
> |
68 |
|
69 |
That is why I said I have used them to test a driver to see if it works |
70 |
or not. It is easier to test them that way but once you find the right |
71 |
one, you don't need it to be a module unless you have some reason to |
72 |
change them from time to time and don't want to reboot. |
73 |
|
74 |
Either way works tho. |
75 |
|
76 |
Dale |
77 |
|
78 |
:-) :-) |