Zwane Mwaikambo wrote:
> On Sun, 23 Nov 2003, A E Lawrence wrote:
> 
> 
>>I have a 82C930 based sound card. Under 2.4.22 and earlier kernels, I use
>>the old OSS driver. Having failed to identify any support for this chip
>>under ALSA, I have configured 2.6.0-test9 with a similar OSS configuration.
>>
>>The relevant parts of the .config files are:-
>>
>>2.4.22                  2.6.0-test9
>>------                  -----------
>># Sound                 # CONFIG_SND is not set
>>#                       CONFIG_SOUND_PRIME=m
>>CONFIG_SOUND=m          CONFIG_SOUND_OSS=y
>>                          CONFIG_SOUND_TRACEINIT=y
>>CONFIG_SOUND_MPU401=m   CONFIG_SOUND_MPU401=m
>>CONFIG_SOUND_MAD16=m    CONFIG_SOUND_MAD16=m
>>CONFIG_SOUND_YM3812=m   CONFIG_SOUND_YM3812=m
>>
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>>Under 2.6.0-test9, there are unresolved symbols:-
> 
> 
> Please send your whole .config

Attached.  But:-

I have discovered that changing  CONFIG_SOUND_OSS=y to
CONFIG_SOUND_OSS=m solves the problem.  And that CONFIG_SOUND_OSS=y 
resulted in the modules being built into the kernel despite the "m" values.
I used
    menu xconfig
to build the .config.

It allowed me to make that mistake, and the help does not spell this out 
clearly. So there needs to be a consistency check in the configuration code.


In passing, I have since realized that I overlooked the opti93x module in 
the ALSA, so that might explain why this problem has not been reported before.

Thanks for the replies on and off list.

A E Lawrence