[arch-general] Headphone Sound Trouble

[Heiko Becker]

2015-05-10 20:28 GMT+02:00 Ralf Mardorf <ralf.mardorf at rocketmail.com>:

> On Sun, 10 May 2015 20:08:32 +0200, Florian Pelz wrote:
> >Does it occur with all applications? For example, I have crackling
> >sound with headphones in all ALSA applications such as unpatched wine,
> >but not in e.g. a patched wine-staging or VLC or most Linux games
> >because they use Pulseaudio.
>
> For testing purpose the OP could build a package using
>
> pkgname=pulseaudio
> pkgver=2015.05.10
> pkgrel=1
> pkgdesc="Dummy package"
> arch=('any')
> provides=('pulseaudio')
>
> for a PKGBUILD, install the package, to 'definitively disable' PA.
>
> I don't allow PA being installed on my machine.
>
> [rocketmouse at archlinux ~]$ pacman -Qi pulseaudio
> Name           : pulseaudio
> Version        : 2013.08.18-1
> Description    : Dummy package
> Architecture   : any
> URL            : None
> Licenses       : None
> Groups         : None
> Provides       : pulseaudio
> Depends On     : None
> Optional Deps  : None
> Required By    : pulseaudio-alsa  vice
> Optional For   : fluidsynth  phonon-qt4  phonon-qt5  speech-dispatcher
> Conflicts With : dummy
> Replaces       : None
> Installed Size :   4.00 KiB
> Packager       : Unknown Packager
> Build Date     : Sun 18 Aug 2013 06:06:40 PM CEST
> Install Date   : Wed 30 Oct 2013 01:09:38 AM CET
> Install Reason : Explicitly installed
> Install Script : No
> Validated By   : None
>
> Unlikely that ALSA is the culprit, since PA does use ALSA.
>
> Regards,
> Ralf
>

So in fact I do not have Pulseaudio installed, hence it cannot be the
culprit :D
Nevertheless, when trying to test based on the instructions given before
(aplay for the wav files) I was also able to reproduce the issue in awesome
WM too.
But when I boot into Windows 8, sound is crystal clear and nothing cracks.

Related to the driver stuff:
I installed bumblebee some weeks ago and do not remember having used any
audio player since then.
Could it be the case, that bumblebee or something related is the culprit?
Is there an easy way to rule out that it is a hardware bug?

Regards,

-- 
Heiko