diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-October/008614.html')
-rw-r--r-- | zarb-ml/mageia-dev/2011-October/008614.html | 139 |
1 files changed, 139 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-October/008614.html b/zarb-ml/mageia-dev/2011-October/008614.html new file mode 100644 index 000000000..f9c101b22 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-October/008614.html @@ -0,0 +1,139 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] [changelog] cauldron core/release sound-scripts-0.61-2.mga2 + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Bchangelog%5D%20cauldron%20core/release%0A%09sound-scripts-0.61-2.mga2&In-Reply-To=%3C201110031628.50648.maarten%40rmail.be%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="008611.html"> + <LINK REL="Next" HREF="008612.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] [changelog] cauldron core/release sound-scripts-0.61-2.mga2</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Bchangelog%5D%20cauldron%20core/release%0A%09sound-scripts-0.61-2.mga2&In-Reply-To=%3C201110031628.50648.maarten%40rmail.be%3E" + TITLE="[Mageia-dev] [changelog] cauldron core/release sound-scripts-0.61-2.mga2">maarten at rmail.be + </A><BR> + <I>Mon Oct 3 16:28:50 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="008611.html">[Mageia-dev] [changelog] cauldron core/release sound-scripts-0.61-2.mga2 +</A></li> + <LI>Next message: <A HREF="008612.html">[Mageia-dev] freeglut vs. mesa (devel requires problem) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#8614">[ date ]</a> + <a href="thread.html#8614">[ thread ]</a> + <a href="subject.html#8614">[ subject ]</a> + <a href="author.html#8614">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op maandag 03 oktober 2011 15:38:34 schreef Colin Guthrie: +><i> 'Twas brillig, and Maarten Vanraes at 03/10/11 13:41 did gyre and gimble: +</I>><i> > Op maandag 03 oktober 2011 10:27:02 schreef Colin Guthrie: +</I>><i> >> 'Twas brillig, and Maarten Vanraes at 19/09/11 11:32 did gyre and gimble: +</I>><i> >>>> On 19 September 2011 11:44, Colin Guthrie <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>> +</I>wrote: +><i> >>>>>>> Did you fixed the war against webcam another way? +</I>><i> >>>>>> +</I>><i> >>>>>> Is this a problem of webcam mics not working if they are present +</I>><i> >>>>>> during boot? If not, can you remember the problem better? +</I>><i> >>>>>> +</I>><i> >>>>>> If so, no I've not fixed, but will find an official way that we can +</I>><i> >>>>>> submit upstream. +</I>><i> >>>>> +</I>><i> >>>>> Whoops, it seems this conversation went off list accidentally. +</I>><i> >>>>> +</I>><i> >>>>> TV clarified that the problem the snd-usb-audio modprobe rule solved +</I>><i> >>>>> was that of webcams getting the card0 slot on boot and pushing the +</I>><i> >>>>> normal, built in audio system to card1. +</I>><i> >>>>> +</I>><i> >>>>> As this problem attempts to resolve the underlying limitations of +</I>><i> >>>>> alsa (not preserving the audio device order) in a generic way +</I>><i> >>>>> (specific index= arguments could be added to your own specific +</I>><i> >>>>> hardware to solve it also), and considering that device order really +</I>><i> >>>>> shouldn't matter when PulseAudio is used (it has it's own built in +</I>><i> >>>>> system for determining the "priority" of devices when a first boot +</I>><i> >>>>> with a new user is encountered so that the correct defaults will be +</I>><i> >>>>> picked on first boot and there after it's the user's choice), I'm +</I>><i> >>>>> not really inclined to attempt to fix this "bug". +</I>><i> >>>>> +</I>><i> >>>>> If people feel super strongly about it I can look into it, but I +</I>><i> >>>>> think it's really a matter of "tough love" for the non-PA case if it +</I>><i> >>>>> means we have to put in lots of crazy work arounds like this. +</I>><i> >>>>> +</I>><i> >>>>> Opinions welcome. +</I>><i> >>>> +</I>><i> >>>> Not all people use PA. +</I>><i> >>>> We even have options in draksound in order to disable it... +</I>><i> >>>> Hence we must still support the case were PA isn't around... +</I>><i> >>> +</I>><i> >>> can something be done with udev rules, like it happens with other types +</I>><i> >>> of devices? +</I>><i> >> +</I>><i> >> I'm not sure udev rules will fix this. +</I>><i> >> +</I>><i> >> I guess we could provide some default modprobe rule that just left space +</I>><i> >> for the device 0... +</I>><i> >> +</I>><i> >> <A HREF="http://alsa.opensrc.org/MultipleCards#Reordering_the_driver_for_a_partic">http://alsa.opensrc.org/MultipleCards#Reordering_the_driver_for_a_partic</A> +</I>><i> >> ula r_card +</I>><i> >> +</I>><i> >> options snd slots=,snd-usb-audio +</I>><i> >> +</I>><i> >> +</I>><i> >> These rules could only be used when PA is not used (via sound profile +</I>><i> >> symlinks) +</I>><i> >> +</I>><i> >> That will probably cover most bases and if users want to have more +</I>><i> >> configuration when they do not use PA then they can write their own +</I>><i> >> modprobe rules. I'd say that's an acceptable trade off. +</I>><i> >> +</I>><i> >> WDYT? +</I>><i> >> +</I>><i> >> Col +</I>><i> > +</I>><i> > what i mean is to have some kind of udev rule generator, so that the ones +</I>><i> > you had when you started at first are kept in that order (they still can +</I>><i> > be added or removed, but the existing ones will keep their device name? +</I>><i> +</I>><i> Potentially, tho' I'd much rather avoid complicated rules generators +</I>><i> like that as it'll just lead to problems at some point when it stops +</I>><i> working or syntax changes etc. +</I>><i> +</I>><i> IMO it's just added complexity for questionable gain. +</I>><i> +</I>><i> Col +</I> + +debian uses this system to make sure devices have the same device names and +numbers as long as they are uniquely identifyable. + +perhaps we can take a look at how debian does it? +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="008611.html">[Mageia-dev] [changelog] cauldron core/release sound-scripts-0.61-2.mga2 +</A></li> + <LI>Next message: <A HREF="008612.html">[Mageia-dev] freeglut vs. mesa (devel requires problem) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#8614">[ date ]</a> + <a href="thread.html#8614">[ thread ]</a> + <a href="subject.html#8614">[ subject ]</a> + <a href="author.html#8614">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |