Why does the new generic kernel under maverick have no oss?

Asked by Raphael Gradenwitz on 2010-08-18

The generic kernel of maverick seems to be completely without any oss:

me@maverick-host:~$ grep OSS '/boot/config-2.6.35-15-generic':
..
..
# CONFIG_SOUND_OSS_CORE is not set
# CONFIG_SND_MIXER_OSS is not set
# CONFIG_SND_PCM_OSS is not set
# CONFIG_SND_SEQUENCER_OSS is not set

In Lucid OSS was at least available as a module:

me@lucid-host:~$ grep OSS /boot/config-2.6.32-24-generic:
..
..
CONFIG_SOUND_OSS_CORE=y
CONFIG_SOUND_OSS_CORE_PRECLAIM=y
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SOUND_OSS=m

But If there is no oss at all, why are there still the 'oss-compat' package etc..?
A lot of software stil needs oss as sound interface as you can see in bug 605280 and 605536

Raphael Gradenwitz

I have already tried to LD_PRELOAD with libaoss.so, libalsatoss.so and libpulsedsp.so but nothing works (yet).
I use Pulse-Audio myself but tvtime needs /dev/mixer (pased by arguments or config-file) to enable sound volumecontrol from within the program itself.
I do not yet understand why oss is completely removed since bug 579300 is not a bug, its a feature request for developement purpose and the situation now causes a lot of bugs! Those who need oss now have to build their own kernel now instead of the developers build their own! This status quo is unsatisfactory!
Why not leave the modules. You can simply blacklist them.

Regards,
Raphael Gradenwitz

Or let me ask this way:
When OSSp (which if I understood things well should become the successor of OSS) will be released since OSS itself hereby already have been removed?

Since the kernel comes with cuse as module and libfuse meanwhile comes with cuse support out of the box, I only had to build ossp and run:

modprobe cuse
osspd

and syslog shows:

Aug 19 15:12:07 maverickhost osspd: OSS Proxy v1.3.2 (C) 2008-2010 by Tejun Heo <email address hidden>
Aug 19 15:12:07 maverickhost osspd: Creating dsp (14:3), adsp (14:12), mixer (14:0)

.. so far so good.

But unfortunately this does not solve the problem with tvtime which seems to need a native /dev/mixer to work :-(

Greg Beam (ki7mt) said : #5

Hi Raphael,

Although I have no further suggestions than what's be provided already, the Final Kernel Freeze for Maverick is September 16th. If the weekly release on September 24th still yields this problem, then we'd have to ask for the reasoning behind leaving it out, or elevate the awareness to the kernel-dev's.

Additionally, you may find better suited answers from the kernel-dev's themselves in irc.freenode.net #ubuntu-kernel

KE1HA

Can you help with this problem?

Provide an answer of your own, or ask Raphael Gradenwitz for more information if necessary.

To post a message you must log in.