Siduction Forum

Siduction Forum => Hardware - Support => Topic started by: dlalias2k1 on 2013/05/08, 19:20:19

Title: (solved)No sound 3.9-0.towo.2-siduction-amd64
Post by: dlalias2k1 on 2013/05/08, 19:20:19
lspci | grep Audio
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
02:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1)

After rebooting from the dist-upgade, Phonon tells me it thinks that audio hardware has been removed and gives me the option to remove it, leave it or manage devices.

Testing all the devices for audio output, none of them work now.

Thanks
Title: No sound since dist-upgade to 3.9-0.towo.2-siduction-amd64
Post by: michaa7 on 2013/05/08, 21:28:29
Can you still boot an older kernel? Maybe alsa has changed with newer kernel!


test with live cd, compare output of "lsmod | grep snd" between live cd and installation.
Title: RE: No sound since dist-upgade to 3.9-0.towo.2-siduction-amd
Post by: dibl on 2013/05/09, 03:10:33
Assuming KDE desktop, my experience indicates you should "OK" to remove the audio hardware device, leaving only the pulseaudio server.  Use the "Test" button under systemsettings > multimedia to confirm that your pulseaudio server is working as expected. Also make sure you install pavucontrol -- you will need it.
Title: RE: No sound since dist-upgade to 3.9-0.towo.2-siduction-amd
Post by: spacepenguin on 2013/05/09, 06:01:28
Pulseaudio? This won't be default... will it? :shock:
Title: Re: RE: No sound since dist-upgade to 3.9-0.towo.2-siduction
Post by: piper on 2013/05/09, 07:13:58
Quote from: "spacepenguin"Pulseaudio? This won't be default... will it? :shock:

+1
Title: Re: RE: No sound since dist-upgade to 3.9-0.towo.2-siduction
Post by: dibl on 2013/05/09, 12:53:53
Quote from: "spacepenguin"Pulseaudio? This won't be default... will it? :shock:

I thought it already was default for KDE. Don't you have to deliberately remove it from a KDE default DE?
Title: RE: Re: RE: No sound since dist-upgade to 3.9-0.towo.2-siduc
Post by: towo on 2013/05/09, 12:59:46
Pulseaudio was never default in siduction and even kde does not need this shit.
Title: Re: RE: Re: RE: No sound since dist-upgade to 3.9-0.towo.2-s
Post by: dibl on 2013/05/09, 14:27:57
Quote from: "towo"........ even kde does not need this shit.

Well, OK, I am not one to make an argument online, especially with my favorite kernel engineer.

:D

But, when I read this (http://www.freedesktop.org/wiki/Software/PulseAudio/Desktops/KDE), which I admit is 12 months old, it seems to say that pulseaudio is needed to support phonon and kmix. That is why I think it must be a default element (not a mandatory element) of a standard KDE desktop.
Title: RE: Re: RE: Re: RE: No sound since dist-upgade to 3.9-0.towo
Post by: piper on 2013/05/09, 19:10:20
I have seen pulse do a lot of damage, I, for one am not at fan at all
Title: Re: RE: Re: RE: Re: RE: No sound since dist-upgade to 3.9-0.
Post by: DeepDayze on 2013/05/10, 00:02:00
Quote from: "piper"I have seen pulse do a lot of damage, I, for one am not at fan at all

Pulse is a default of Gnome desktop though...
Title: RE: Re: RE: Re: RE: Re: RE: No sound since dist-upgade to 3.
Post by: dlalias2k1 on 2013/05/10, 00:36:18
So when I boot my previous kernel:
3.8-7.towo-siduction-amd64

Phonon tells me I have seem to have removed devices and if I would like to remove them, like before, however this time it's reporting a different card as removed:
HDA Intel MID, 92HD81B1X5 Analog

and playback does work when I select my output device as:
HDA Intel MID, STAC92xx Analog

When I boot the newer kernel, the cards it thinks are installed are reversed. (i.e. It thinks the STAC92xx is removed and that the 92HD81B1X5 has been installed and none of the enabled devices will succeed in sound playback)

lsmod | grep snd     #from working sound configuration:
snd_hda_codec_hdmi     23879  4
snd_hda_codec_idt      46423  1
snd_hda_intel          26021  7
snd_hda_codec          73891  3 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel
snd_hwdep               5341  1 snd_hda_codec
snd_pcm                61525  4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc          6234  2 snd_pcm,snd_hda_intel
snd_seq                42049  0
snd_seq_device          4649  1 snd_seq
snd_timer              15553  3 snd_pcm,snd_seq
snd                    49920  21 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_idt,snd_pcm,snd_seq,snd_hda_codec,snd_hda_intel,snd_seq_device
soundcore               4402  1 snd
Title: RE: Re: RE: Re: RE: Re: RE: No sound since dist-upgade to 3.
Post by: dlalias2k1 on 2013/05/10, 00:40:10
lsmod | grep snd #from newer kernel
snd_hda_codec_hdmi     24824  4
snd_hda_codec_idt      33731  1
snd_hda_intel          27737  6
snd_hda_codec         106897  3 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel
snd_hwdep               5341  1 snd_hda_codec
snd_pcm                61509  4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc          6170  2 snd_pcm,snd_hda_intel
snd_seq                42049  0
snd_seq_device          4649  1 snd_seq
snd_timer              15553  3 snd_pcm,snd_seq
snd                    49920  19 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_idt,snd_pcm,snd_seq,snd_hda_codec,snd_hda_intel,snd_seq_device
soundcore               4402  1 snd
Title: RE: Re: RE: Re: RE: Re: RE: No sound since dist-upgade to 3.
Post by: michaa7 on 2013/05/10, 01:25:23
I don't know exactly how this problem could be solved. On lkml.org I read that the complete hda_intel stuff got reworked for 3.9 kernel. And the different behavior (different codecs for same hardware, but newone not working) between your 3.8.x and the new 3.9.x kernel seems to demonstrate that there are transition problems.
Only advice I can give so far:

- For the time being stay with the older 3.8.x kernel (if possible).
- Wait some days for new packages to come, maybe new alsa-utils solve this problem.
- File a bugreport to debian (using "reportbug", or maybe to the alsa-user mailing list)

But if *I* would *need to solve* this *now* with the new kernel I would *purge* all the alsa stuff (and if you have a ".asoundrc" in your home, better save it away)c, reboot and reinstall alsa. Without any guarantee.

EDIT://
How do you *know* the new codec / new device is not working? Did you check wheather or not the device is muted in kmix and/or alsamixer?

EDIT2://
Cited from the alsa developer's docs published few days ago:
http://www.mjmwired.net/kernel/Documentation/sound/alsa/HD-Audio.txt

Quote662   Sending a Bug Report
663   ~~~~~~~~~~~~~~~~~~~~
664   If any model or module options don't work for your device, it's time
665   to send a bug report to the developers.  Give the following in your
666   bug report:
667   
668   - Hardware vendor, product and model names
669   - Kernel version (and ALSA-driver version if you built externally)
670   - `alsa-info.sh` output; run with `--no-upload` option.  See the
671     section below about alsa-info
672   
673   If it's a regression, at best, send alsa-info outputs of both working
674   and non-working kernels.  This is really helpful because we can
675   compare the codec registers directly.
676   
677   Send a bug report either the followings:
678   
679   kernel-bugzilla::
680     https://bugzilla.kernel.org/
681   alsa-devel ML::
682     alsa-devel@alsa-project.org
Title: RE: Re: RE: Re: RE: Re: RE: No sound since dist-upgade to 3.
Post by: dlalias2k1 on 2013/05/10, 04:31:23
Yea, I checked kmix and alsmixer, nothing is muted on the "new" device.

Alright, I'll file the bug and run 3.8 and check for fixed releases going forward.

Thanks Michaa7. Seems like I always show up with for help with crazy problems, but I always appreciate the help.
Title: RE: Re: RE: Re: RE: Re: RE: No sound since dist-upgade to 3.
Post by: piper on 2013/05/10, 06:10:15
You might want to try aand rename phonondevicesrc (rename DO NOT delete)
/.kde/share/config/phonondevicesrc and then delete the hardware database
/var/tmp/kdecache-username/libphonon/hardwaredatabase and reboot, yes reboot

Just for shits and giggles, what does apt-cache policy phonon-backend-null say
Title: RE: Re: RE: Re: RE: Re: RE: No sound since dist-upgade to 3.
Post by: michaa7 on 2013/05/10, 13:19:37
Now after reading piper's advice I realize that I possibly was focused on alsa/hda_intel too much. Maybe the culprit is not alsa but kde.

Did you try to play a (.wave-) file with "aplay" directly (or any other player not relying on kde/phonon such as the commandline player "moc"? I think moc is a siduction standard package. So all you have to do is to open a VT, type "mocp" (music_on_commandline_play) and navigate to a song within the moc_ncurses_shell)
Title: RE: Re: RE: Re: RE: Re: RE: No sound since dist-upgade to 3.
Post by: dlalias2k1 on 2013/05/11, 02:39:45
Did as requested, No change in lack of sound on the new kernel.

Phonon is reporting that I have the gstreamer and vlc backends installed. As for your command:

apt-cache policy phonon-backend-null
phonon-backend-null:
 Installed: (none)
 Candidate: 4:4.6.0.0-3
 Version table:
    4:4.6.0.0-3 0
       500 http://http.debian.net/debian/ unstable/main amd64 Packages
       500 ftp://ftp.us.debian.org/debian/ unstable/main amd64 Packages
Title: RE: Re: RE: Re: RE: Re: RE: No sound since dist-upgade to 3.
Post by: piper on 2013/05/11, 02:48:17
Quote
apt-cache policy phonon-backend-null
phonon-backend-null:
Installed: (none)
Candidate: 4:4.6.0.0-3
Version table:
4:4.6.0.0-3 0
500 http://http.debian.net/debian/ unstable/main amd64 Packages
500 ftp://ftp.us.debian.org/debian/ unstable/main amd64 Packages


That's how it should look, thanks.

I am out of options, not sure if kernel related or not
Title: RE: Re: RE: Re: RE: Re: RE: No sound since dist-upgade to 3.
Post by: piper on 2013/05/11, 02:55:06
What I would do is download the latest test iso

http://test.siduction.org/iso/siduction/kde/13_05_10_0704/

that has kernel 3.9-1 and see if sound works in live mode
Title: RE: Re: RE: Re: RE: Re: RE: No sound since dist-upgade to 3.
Post by: dlalias2k1 on 2013/05/11, 04:23:00
I couldn't get the test iso to boot into KDE. It would go to a black screen with regular boot and with Safegfx mode. I could jump to another console, but ctrl-alt-f7 never finished loading the DisplayManager.

But in other news, Messing with audio and mocp, I did discover something. Previously audio was controlled via Master and PCM channels.
Under the new kernel with the non-Stac92xx audio, Sound IS working now.
While the speaker channel wasn't muted it didn't have audible sound (the channel was set at half volume on the slider) With all the sliders maxed, I do have sound, but it's not quite as loud as it was under the earlier kernel for some reason.
Title: Re: RE: Re: RE: Re: RE: Re: RE: No sound since dist-upgade t
Post by: michaa7 on 2013/05/11, 10:40:52
Quote from: "dlalias2k1"...
But in other news, Messing with audio and mocp, I did discover something. Previously audio was controlled via Master and PCM channels.
Under the new kernel with the non-Stac92xx audio, Sound IS working now.
While the speaker channel wasn't muted it didn't have audible sound (the channel was set at half volume on the slider) With all the sliders maxed, I do have sound, but it's not quite as loud as it was under the earlier kernel for some reason.

So your problem seems partly solved (does it work now with KDE?). But if the max volume isn't as satisfying as it was with the older driver it's still worth a bug report with all the details to http://alsa-project.org/main/index.php/Mailing-lists#alsa-devel_at_alsa-project.org (as mentioned above).