linux-kernel - Re: [REGRESSION] 4.1-rc4: Sound muted after boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5hfv6q5zbr.wl-tiwai@suse.de>
Date:	Thu, 21 May 2015 06:28:24 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Martin Steigerwald <martin@...htvoll.de>
Cc:	linux-kernel@...r.kernel.org, alsa-devel@...a-project.org
Subject: Re: [REGRESSION] 4.1-rc4: Sound muted after boot

At Wed, 20 May 2015 16:31:55 +0200,
Martin Steigerwald wrote:
> 
> Hello!
> 
> On ThinkPad T520 (Intel Sandybridge) with 4.14-rc4 + two BTRFS patches and 
> one Intel P-State debug patch I have no sound output on internal Intel HD 
> audio codec.
> 
> According to ThinkPad T520 LED with striked-through speaker the loud speaker 
> is in disabled state. Also KDE´s Phonon says a soundcard is missing. In 
> alsa-mixer I see nothing as MM for muted. If I press the key next to the LED 
> I get a notification on the desktop that loud speaker has been enabled / 
> disabled, but the LED still is on for it being disabled.
> 
> I do not hear anything in Amarok or with aplay. alsa-mixer sound volumes are 
> 100 for master and PCM. I also tried with disabling "Auto-Mute Mod", but 
> still no sound.
>  
> When I reboot and in BIOS or GRUB press the key then the LED toggles state.
> 
> When I reboot into Linux 4.0.1 sound is working fine and loud speaker 
> disabled LED is toggled off, so I bet this is a regression 4.1-rc4 compared 
> to 4.0.1.

Please run alsa-info.sh at both working and non-working cases (with
old and new kernels), and attach the outputs. Run the script with
--no-upload option.

Also, such a problem is rather the device permissions problem.
Check the device permissions of /dev/snd/* files (also check getfacl
/dev/snd/*, too).


Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/