At Fri, 07 Sep 2012 16:28:19 +0200, David Henningsson wrote: > > On 09/07/2012 03:09 PM, Takashi Iwai wrote: > > At Fri, 07 Sep 2012 14:47:16 +0200, > > David Henningsson wrote: > >> > >> On 09/07/2012 02:36 PM, Takashi Iwai wrote: > >>> At Fri, 07 Sep 2012 14:17:58 +0200, > >>> David Henningsson wrote: > >>>> Or is the corner case that ALSA don't give the correct jack detection > >>>> value? If so I prefer it to be fixed in ALSA ;-) > >>> > >>> Well, I can think of different cases: BIOS is broken, my hardware is > >>> broken and the driver is broken. In such a case, an easier test would > >>> be to disable this jack auto-things in PA, rather than fiddling with > >>> the pin config and reconfigure the driver, so I hoped there might be > >>> an intuitive and easy way to do that. > >> > >> Naah, in all those cases it is ALSA's responsibility to give a correct > >> answer up to PA - and as such, also to provide an "intuitive and easy > >> way" to disable jack detection if you feel there is a need. IMO. > > > > Adjusting a user-space things is much safer than adjusting something > > in kernel. The former doesn't need a root privilege (if it's done > > right). Thus for debugging purpose, fiddling with PA at first would > > be more comfortable than digging with the driver code and BIOS > > setups. > > > > Of course, a permanent fix is a different story. I'm talking about > > the debuggability. > > > >> That said, it's not super difficult to comment out a few lines in > >> /usr/share/pulseaudio/alsa-mixer/paths/*.conf, and also, most mixer UIs > >> (e g pavucontrol) still allows you to route audio to an unavailable port. > > > > Yes, but some guidelines would be nice to have somewhere explicitly... > > Also this can be done without being root somehow, right? > > Hmm, I'm afraid it's not so easy to turn off PulseAudio's jack detection > without being root. Maybe it's possible using some .asoundrc magic?
That's bad. asoundrc is equally cryptic like udev rules :) Honestly, can't the whole /usr/share/pulseaudio/* files be specified via an environment variable, or automatically looking at ~/.pulse/alsa-mixer/paths/* or such? > Btw - I've never seen this as a practical problem myself. For debugging > jack sense problems, I typically triage with > 1) "amixer contents" (PulseAudio or kernel space?) > 2) "sudo hda-jack-sense-test" (hardware or driver?) > > Asking people to run a sudo command has never been a problem. (but maybe > that's a problem in itself - i e that people are not security aware...) Indeed. Anyway, it's way offtopic now :) Takashi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/939161 Title: Hardware not showed in Gnome-Control-Center. - [M31EI Series, Realtek ALC861, Green Headphone Out, Rear] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/939161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
