Bug 12862 - No headphone control in Sigmatel HDA
Summary: No headphone control in Sigmatel HDA
Status: CLOSED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Sound(ALSA) (show other bugs)
Hardware: All Linux
: P1 high
Assignee: Jaroslav Kysela
URL:
Keywords:
Depends on:
Blocks: 12398
  Show dependency tree
 
Reported: 2009-03-12 12:44 UTC by Martin
Modified: 2009-03-14 11:16 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.29-rc7
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
alsa-info (ran as user) (22.37 KB, text/plain)
2009-03-13 01:30 UTC, Martin
Details

Description Martin 2009-03-12 12:44:30 UTC
Latest working kernel version: 2.6.28
Earliest failing kernel version: 2.6.29-rc7?
Distribution: Ubuntu Jaunty
Hardware Environment: Dell Vostro 1400
Software Environment: Alsa/Audacious
Problem Description: Inserting a headphone does not kill sound on built-in speakers, there is no separate headphone volume/mute control in alsamixer under 2.6.29-rc7

Steps to reproduce: boot 2.6.29-rc7, play audio, plug headphone: still sound from internal speakers (AND sound from headphones). No headphones volume/mute in kmix or alsamixer.
Comment 1 Takashi Iwai 2009-03-12 15:33:13 UTC
Try the very latest Linus git tree.  A couple of fixes for Dell laptops are in after rc7.

If it still doesn't work, try sound git tree (master branch)
    git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git

Anyway, please run alsa-info.sh with --no-upload option and attach the generated file.  This will contain more detailed hardware information.  The script is found at:
    http://www.alsa-project.org/alsa-info.sh
Comment 2 Martin 2009-03-13 01:30:40 UTC
Created attachment 20515 [details]
alsa-info (ran as user)

This is the requested info. I'd prefer to stick with rc's when possible. They're on-the-edge enough for me as I'm running rc7 on a "production" laptop.
Comment 3 Takashi Iwai 2009-03-13 01:35:09 UTC
Then try rc8 released yesterday :)
Comment 4 Martin 2009-03-13 02:51:49 UTC
It's fixed in rc8.
Thx!

Note You need to log in before you can comment on or make changes to this bug.