..And yes,there's : options saa7134 oss=1 in /etc/modprobe.d/tv, I set it up using YAST...
On Tuesday 04 October 2005 22:42, Stoyan Tzalev wrote: > Hi guys, > just a quick question for the devs/maintainers reading this list... I have > a saa7134 compatible TV tuner card. To get the sound, I pass the oss=1 > option to the kernel module in order to register /dev/dsp1 and use this > little trick : sox -c 2 -sw -r 32050 -t ossdsp /dev/dsp1 -t sw - | aplay -c > 2 -r 32050 -f S16_LE > (it actually "redirects" dsp1 to dsp0). This assumes that the ALSA modules > for OSS compatibility are already loaded successfully. I set the things up > manually an everything worked like a charm,until I was forced to reboot. I > noticed there was no sound,and found this in the logs: > ... > saa7133[0]: registered device dsp0 > saa7133[0]: registered device mixer0 > ... > ALSA sound/core/oss/mixer_oss.c:1274: unable to register OSS mixer device > 0:0 ALSA sound/core/oss/pcm_oss.c:2440: unable to register OSS PCM device > 0:0 > > I have also checked the module order - and,yes, snd_pcm_oss and > snd_mixer_oss were loaded _after_ saa7134. I had to reload the modules in > the right order manually,which is not very convenient... well,I use a > quick&dirty script,but that's not the point :) > You get the picture... my question is - is this a normal behaviour,or > should I report this "feature"? (Or at least,is there a YAST-based > solution/workaround) > > 10x for your attention > > Stoyan > > P.S. openSUSE 10.0 RC1,stock kernel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
