[solved] Somehow quick-init breaks the phonon-xine backend

ChoK · 2010-08-31 23:29:37

Well it has been a long time since I had sound troubles.

So what happened recently :
- The kernel upgrade from 2.6.34 to 2.6.35 broke my sound.
aplay -l gave the following output

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC888 Analog [ALC888 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: ALC888 Digital [ALC888 Digital]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 3: NVIDIA HDMI [NVIDIA HDMI]
Subdevices: 0/1
Subdevice #0: subdevice #0

Nothing fishy here, I always had the same since sound over hdmi was added and everything was unmuted in alsamixer.
I tried to play music in aplay, mplayer, mpd and amarok. None of these gave me the dreaded Device or resource busy but still nothing but silence.
This was solved by putting "options snd-hda-intel model=auto" in /etc/modprobe.d/sound.conf (I didn't have any alsa or sound related config files before).

- Next is quick-init
I installed it today, and it's working fine except that with it phonon-xine doesn't find my analog sound output and my analog sound input
the usual options were for output : analog, spdif, hdmi, esd, jack and for capture : analog.

using jack works fine and non-phonon app were fine. (mplayer and mpd can play a song at the same time, and if I use phonon-xine with jack I can listen to amarok+mpd+mplayer at the same time)
aplay -l output is the same as before so quickinit somehow expose a bug in the way xine or phonon-xine retrieves soundcards/alsa devices.

removing quick-init makes my analog ouput and input devices reappear.
phonon-gstreamer can see my analog output + every other ouput devices but the capture device is not detected (maybe a phonon-gstreamer problem).

This behaviour was on 2.6.34.3 and 2.6.35.4 kernels with phonon phonon-xine and phonon-gstreamer 4.4.2-1 and quickinit 1.10 from aur.

While both problems can be adressed. I'd like to know where they do come from but I have to admit I have no idea. Suggestions?

Last edited by ChoK (2010-09-02 07:29:47)

ChoK · 2010-09-02 07:36:07

I found the source of the missing entries. Somehow with quick-init alsa-oss sequence doesn't exit ( /dev/snd/snq) reloading the module snd_pcm_oss with rmmod and modprobe restores the missing entries like HDAudio ALC888 Analog in phonon-xine and make my capture device entry reappear.

Now to find why when quick init loads snd_pcm_oss, the snd_seq_oss module isn't loaded alongside.

Update : While snd_seq_oss isn't loaded, just adding it in my rc.conf doesn't cut it, I have now Alsa default device, oss default device, jack, and esd listed by phonon xine instead of HDA Intel (ALC888 Analog), HDA Intel (ALC888 Digital SPDIF IEC958) HDA Intel (NVIDIA HDMI), jack and esd. Audio capture device is not back either.
I suspect this has to do with the way qinit load modules, maybe it's because they are loaded before udev. back to some testing.

Update2 : As suspected moving the starting of udev before the module loading is the solution. Looks like modules are configured when loaded only and if udev is not available rules like : /lib/udev/rules.d/60-persistent-alsa.rules will not be applied until module reload. i lose some boot time but well whatever let's go shopping for ssd.

Last edited by ChoK (2010-09-02 10:54:54)

adriano · 2010-09-02 11:54:44

Quick-init it's currently deprecated. I suggested don't use it. Wait for new version soon.

Arch Linux

#1 2010-08-31 23:29:37

[solved] Somehow quick-init breaks the phonon-xine backend

#2 2010-09-02 07:36:07

Re: [solved] Somehow quick-init breaks the phonon-xine backend

#3 2010-09-02 11:54:44

Re: [solved] Somehow quick-init breaks the phonon-xine backend

Board footer