diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-May/015309.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-May/015309.html | 264 |
1 files changed, 264 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-May/015309.html b/zarb-ml/mageia-dev/2012-May/015309.html new file mode 100644 index 000000000..1bf2d976d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-May/015309.html @@ -0,0 +1,264 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] no sound + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20no%20sound&In-Reply-To=%3C4FA51F00.4020105%40colin.guthr.ie%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="015308.html"> + <LINK REL="Next" HREF="015313.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] no sound</H1> + <B>Colin Guthrie</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20no%20sound&In-Reply-To=%3C4FA51F00.4020105%40colin.guthr.ie%3E" + TITLE="[Mageia-dev] no sound">mageia at colin.guthr.ie + </A><BR> + <I>Sat May 5 14:37:20 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="015308.html">[Mageia-dev] no sound (was: Proprietary graphic car...) +</A></li> + <LI>Next message: <A HREF="015313.html">[Mageia-dev] no sound +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#15309">[ date ]</a> + <a href="thread.html#15309">[ thread ]</a> + <a href="subject.html#15309">[ subject ]</a> + <a href="author.html#15309">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>'Twas brillig, and Felix Miata at 05/05/12 11:43 did gyre and gimble: +>><i> Can you clarify "sound does not work"? +</I>><i> +</I>><i> Nothing but background hum coming from connected AV amp connected speakers. +</I>><i> +</I>>><i> Are you referring to HDMI sound +</I>>><i> or regular built in sound? +</I>><i> +</I>><i> Surely there exists no motherboard with NForce2 chipset and AGP slot +</I>><i> filled with rv200 that also has HDMI? +</I> +I have no idea. I'm afraid I don't spend my evenings memorising the +multitude of different hardware in the world so I can automatically know +this stuff. This is why I ask for clarification. + +><i> 00:06.0 Multimedia audio controller: nVidia Corporation NForce2 AC97 +</I>><i> Audio Controler (MCP) (rev a1) +</I>><i> +</I>><i> If so please do attach the output from "pacmd ls" +</I>><i> +</I>><i> No package named pacmd. +</I>><i> # urpmi pulseaudio-utils +</I>><i> ... +</I>><i> # pacmd ls +</I>><i> No PulseAudio daemon running, or not running as session daemon. +</I> +Did you run it as root? If so, run it as a regular user instead. You may +with to run "pactl stat" first if you are in a console as this will +trigger an autospawn of pulseaudio if it's not already running (pacmd +does not trigger autospawn as it's a debugging tool not a regular client). + +><i> # startx +</I> +Is this how you start X always? If so you should know from previous +discussions that this behaviour isn't really officially recommended as +it does not allow for proper user session tracking and thus has various +permissions related issues. It *should* work most of the time, but it is +highly recommended that you use a proper DM to login. + +If this is a simple permissions issue, then you can test by running +"loginctl" before startx and noting if your sessions is listed. If it +is, it should have a number next to it (e.g. 1) and if it is listed you +can do: "loginctl session-status 1" (or whatever the number). This +should confirm that the session is active. When the session is active +your user should be listed in the ACL for the sound device nodes +(getfacl /dev/snd/pcm*). + +After issuing startx, try the same commands and, in particular, make +sure your session is still active. I've tried to ensure that it is kept +active (i.e. there is no VT switch), but this isn't 100% reliable. +startx should print out warnings when things don't work however. + +><i> (KDE menu has no selection to configure computer. Without it there's no +</I>><i> way I know how to manage systemd like I could with sysvinit.) +</I> +I've no idea about this sorry. You should report it as a separate bug tho'. + + +><i> # mcc +</I>><i> bash: mcc: command not found +</I>><i> # chkconfig --list +</I>><i> ... +</I>><i> alsa 0:off 1:off 2:off 3:off 4:off 5:off +</I>><i> 6:off 7:off +</I>><i> ... +</I>><i> numlock 0:off 1:off 2:on 3:on 4:on 5:on +</I>><i> 6:off 7:on +</I>><i> partmon 0:off 1:off 2:off 3:off 4:off 5:off +</I>><i> 6:off 7:off +</I>><i> resolvconf 0:off 1:off 2:off 3:off 4:off 5:off +</I>><i> 6:off 7:off +</I>><i> ... +</I>><i> sound 0:off 1:off 2:on 3:on 4:on 5:on +</I>><i> 6:off 7:off +</I> +In this case, the alsa+sound sysvinit scripts are fully overriden by +systemd so the chkconfig output is not actually relevant (see below for +my comments about the Troubleshooting section's outdated advice) + +><i> # systemctl list-unit-files +</I>><i> alsa-restore.service static +</I>><i> alsa-store.service static +</I>><i> alsa.service masked +</I>><i> ... +</I>><i> sound.service masked +</I>><i> ... +</I>><i> sound.target static +</I>><i> ... +</I>><i> +</I>><i> What to do? +</I> +Yup that looks as expected. + +Try running the commands above to debug user permissions. I suspect this +is where the problem lies but I could be wrong. + +"pacmd ls" output from inside X should work fine as PA will have been +started by then and it won't need to be autospawned. + +>>><i> 2: +</I>>>><i> (Non-PAE, IIRC) P4 2.6GHz CPU +</I>>>><i> Intel 865G pci 0x2572 video& ICH5 chipset +</I>>>><i> KDE bling disabled +</I>>>><i> x11-driver-video-intel-2.19.0-1.mga2 +</I>>>><i> No post-install visual fault found running intel driver +</I>>>><i> Sound does not work +</I>><i> +</I>>><i> AS above +</I>><i> +</I>><i> Nothing but background hum coming from connected AV amp connected speakers. +</I>><i> +</I>><i> Surely there exists no motherboard with 865/ICH5 chipset and empty AGP +</I>><i> slot that also has HDMI? +</I> +Again, I don't know. I don't study this stuff and know all the different +chipsets and motherboard configurations. Sorry if this disappoints you, +but I've got better and more interesting things to spend my time on! + +><i> 00:1f.5 Multimedia audio controller: Inter Corporation 82801EB/ER +</I>><i> (KCH5/ICH5R) AC'97 Ausio Controller (rev 02) +</I>><i> +</I>><i> # pacmd ls +</I>><i> (17.9k attachment) +</I> +There is no attachment I can see for this output... + + + +><i> # mcc +</I>><i> ... +</I>><i> 'Your card currently uses the ALSA "snd_intel8x0" droiver (the default +</I>><i> driver for your card is "snd_intel8x0)' +</I>><i> PulseAudio enabled +</I>><i> Use Glitch-Free mode enabled +</I>><i> (advanced) +</I>><i> Troubleshooting +</I>><i> The classic bug sound tester is to run the following commands: +</I> +Wow, this info is horribly out of date.... + +><i> - "grep sound-slot /etc/modprobe.conf" will tell you what driver it +</I>><i> currently uses +</I> +Not really true. It's all done via udev these days. There should be no +need for any manual configuration in 99.9% of cases. "sound-slot" +arguments are not even read these days. + +><i> - "/sbin/chkconfig --list sound" and "/sbin/chkconfig --list alsa" will +</I>><i> tell you if sound and alsa services are configured to be run on initlevel 3 +</I> +Not really relevant these days. + +><i> - "aumix -q" will tell you if the sound volume is muted or not +</I>><i> - "/sbin/fuser -v /dev/dsp" will tell which program uses the sound card. +</I> +Both these commands are very out of date. They do not deal with ALSA +cards but OSS drivers... that's been old for years :s + + +We need to update these strings (and I think there was a bug about this +somewhere that I've forgotten about :s) but I fear it's too late for +mga2 due to i18n freeze. + + +><i> Logging in from KDM doesn't improve anything. In fact, after the desktop +</I>><i> seems fully populated, there's a long pause before the panel populates +</I>><i> the tray and it's possible to do anything other than look at the screen. +</I>><i> +</I>><i> +</I>><i> Oh, and on all systems <A HREF="https://bugs.kde.org/show_bug.cgi?id=283366">https://bugs.kde.org/show_bug.cgi?id=283366</A> makes +</I>><i> KDE4 virtually useless. +</I> +It's possibly the same issue as the delay itself. + +Col + + +-- + +Colin Guthrie +colin(at)mageia.org +<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A> + +Day Job: + Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A> +Open Source: + Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A> + PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A> + Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A> +</PRE> + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="015308.html">[Mageia-dev] no sound (was: Proprietary graphic car...) +</A></li> + <LI>Next message: <A HREF="015313.html">[Mageia-dev] no sound +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#15309">[ date ]</a> + <a href="thread.html#15309">[ thread ]</a> + <a href="subject.html#15309">[ subject ]</a> + <a href="author.html#15309">[ 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> |