[TOSHIBA NB100, Realtek ALC262, Green Headphone Out, Rear] volume slider problem

[Ярослав Почернин]

I am using Toshiba NB100 Ubuntu Certified netbook. The sound works fine in general but if I plug in a jack it disappears. If I go to alsamixer I can see that the Speaker fader is down, so, if I move it up again, the sound appears in the headphones. But if I unplug the jack and plug it in again, the fader instantly goes down again and the sound disappears. This is a regression that prevents me from using Oneiric full time now. I've shown what happens after I plug in the jack on the attached screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: alsa-base 1.0.24+dfsg-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu3
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 3092 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd0000000 irq 44'
   Mixer name : 'Realtek ALC262'
   Components : 'HDA:10ec0262,1179ff7b,00100302'
   Controls : 17
   Simple ctrls : 9
CasperVersion: 1.285
Date: Mon Oct 10 06:48:52 2011
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20111009)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Internal Audio - HDA Intel
Symptom_Jack: Green Headphone Out, Rear
Symptom_Type: Volume slider, or mixer problems
Title: [TOSHIBA NB100, Realtek ALC262, Green Headphone Out, Rear] volume slider problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/15/2008
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.10
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Insyde
dmi.chassis.version: None
dmi.modalias: dmi:bvnINSYDE:bvr1.10:bd09/15/2008:svnTOSHIBA:pnTOSHIBANB100:pvrPLL10E-00Y00MRU:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnInsyde:ct10:cvrNone:
dmi.product.name: TOSHIBA NB100
dmi.product.version: PLL10E-00Y00MRU
dmi.sys.vendor: TOSHIBA

[David Henningsson (diwic)]

Hi Ярослав!

The problem seems to be that the "Speaker" alsa control affects headphone volume, it should not do that. Can you check if it is fixed upstream by installing the latest sound drivers? See https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS

Thanks in advance!

[Ярослав Почернин (yaroslav-pochernin)]

Well, I did what this wiki says and still I'm getting this bug. The only difference is that I did "sudo /sbin/alsa force-reload" rather than rebooting the system since I'm on live image now.

[David Henningsson (diwic)]

Aha, I now discovered there is an existing quirk in the driver, we could consider removing it. Could you modify
/etc/modprobe.d/alsa-base.conf

And add this line:
options snd-hda-intel model=auto

...then reboot (or alsa force-reload) the system?

And if the above in combination with the DKMS packages still does not work, could you file an alsa-info ( see wiki.ubuntu.com/Audio/AlsaInfo ) with that combination? Thanks!

[Ярослав Почернин (yaroslav-pochernin)]

I've done what you told but it doesn't seem to have changed anything. Here's a link to my alsa-info: http://www.alsa-project.org/db/?f=d7d23c5a36d66450d6d9720d53ae2e2ec985f0de

[David Henningsson (diwic)]

Hmm, I wonder if the modules really reloaded correctly? On successful reload,
cat /sys/module/snd_hda_intel/parameters/model
should say something with "auto", not just "(null)".

[Ярослав Почернин (yaroslav-pochernin)]

Okay, I did a fresh install of Oneiric on my netbook, installed the DKMS packages, added "options snd-hda-intel model=auto" to alsa-base.conf file, rebooted my computer, and the situation is now different: when I plug the input jack, I get the sound in my headphones but when I unplug it, the sound from my netbook built-in speakers is very low, almost imperceptible. So, if I run alsamixer, I can see that there's a Speaker fader muted when a jack is plugged in but when I unplug it, the fader doesn't return to its previous state (full volume) and stays somewhere close to zero. Also, the "cat /sys/module/snd_hda_intel/parameters/model" command says "auto,(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)".

[David Henningsson (diwic)]

Ok, thanks for enduring :-)

So when you unplug, what happens in the "Sound settings" dialog? Is the connector changed (to what)? Is the volume changed?
What if you change the volume (in "Sound settings") while the speaker is active (headphones unplugged), will that be preserved?

[Ярослав Почернин (yaroslav-pochernin)]

When I unplug, the connector (I guess it's called channel in Russian locale of Ubuntu) is changed back to Analog Speakers. THe volume remains unchanged. If I change the volume (even if I make it lower), the speakers immediately start to play at the proper volume.

[David Henningsson (diwic)]

Hi,

Just to let you know,
I've spent today working with the broken volume being set on port change. I've posted two patches upstream for discussion. I'm attaching them here as well for my own reference.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "0001-Fix-deferred-volume-not-being-applied-if-sink-is-clo.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-sponsors please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

[Ярослав Почернин (yaroslav-pochernin)]

Are those of any use to me now? When wllI be able to test it?

[David Henningsson (diwic)]

When this build is finished, you can try it: https://code.launchpad.net/~ubuntu-audio-dev/+archive/alsa-daily/+recipebuild/98117 ( using the https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS instructions)

[Ярослав Почернин (yaroslav-pochernin)]

So, if I add this PPA https://code.launchpad.net/~ubuntu-audio-dev/+archive/alsa-daily and install alsa-hda-dkms from it, the patch should be there with some update, right?

[David Henningsson (diwic)]

Hmm, the above message (comment #15) was written in the wrong bug, sorry. The patches above are for PulseAudio, and I've added one of them to be SRUed but I should probably add the other one as well...

[Mark Fraser (launchpad-mfraz)]

Not sure if it relevant to this bug, but I'm also having problems with not being able to use the built-in microphone. PAUVControl only sees the analogue input doesn't seem to be any way of selecting the microphone.

[Mark Fraser (launchpad-mfraz)]

Also, the sound coming out of the headphones is very quiet unless I select analogue output in PAUVControl, but if I unplug and reconnect the headphones the sound is quiet again.

[Ярослав Почернин (yaroslav-pochernin)]

Is there any chance it's getting fixed soon? I've enabled "Proposed" update channel but still I have the issue.

[Ярослав Почернин (yaroslav-pochernin)]

Got some pulseaudio updates today but still the bug is present here.

[David Henningsson (diwic)]

(Sorry for the late reply, I've been travelling)

@yaroslav,
That's sad to hear that you're still having problems, I was hoping that PulseAudio version 1:1.0-0ubuntu3.1 together with the DKMS alsa modules would resolve the issues. Could we recap a little, what is happening now when you plug and unplug (has anything changed, e g on the alsamixer level), and what would you expect to happen?

[Ярослав Почернин (yaroslav-pochernin)]

I'm sorry, I thought that the bug is fixed in alsa, too (so, I wouldn't need dkms package). Now that I have it installed, everything works fine! Thank you for resolving my issue!

[David Henningsson (diwic)]

Thanks for the feedback! Since this will be fixed in the next version of Ubuntu, I'm setting this to "Fix released".

[mspanc (mspanc)]

I can confirm the problem on ubuntu 12.04 with toshiba nb100.

After fresh install speakers work correctly but sound disappears when headphones are connected. Each volume slider (in the software, PulseAudio, ALSA) are at 100%.

Adding

options snd-hda-intel model=auto

to

/etc/modprobe.d/alsa-base.conf

fixes the issue.

[andi (andi001)]

It's still not completely solved. I am running Mint 13 Maya:

Problem A) as saepia said - one has to manually add "options snd-hda-intel ..." and do some "alsa force-reload" or restart to fix the "1. speaker ->2. headphone insertion ->3. speaker-not-working-anymore" issue

Problem B) but still the "Speaker" volume 0% <= Ss1 <= 100% of 1. is not remembered, but instead it goes to 100% on 3.

Problem C) and the "Speaker" volume (curiously adjusting the headphone volume as well) 0% <= Sh2 <= 100% of 2. is not remembered on "->4. headphone insertion"

=> it seems the logical<->physical relationship between the "Soundcard elements": "Speaker" and "PCM" is not correctly mapped by the driver:

State X) currently:

State Xs) no headphone inserted: "Speaker", "PCM" and "Master" add up to the resulting volume of the notebook speakers VS
      => thus 3. is actually quite bad here since it may significantly increase speaker volume VS3 in opposition to VS1 (=VS3-(1-Ss1))

State Xh) headphone inserted: "Speaker", "PCM" and "Master" add up to the resulting volume of the headphone VH
      => thus 2./4. are actually quite bad here since they may significantly lower the headphone volume VH2/VH4 (VH4=VH2-Sh2)

=>
Solution Y1) driver behaviour should be: B and C "Speaker" volume should not be touched at all on headphone insertion/removal, which would also eliminate the problem of the "remembering of the speaker/headphone volume"

maybe some existing "model=???" other than "auto" may already do Y1 ... if I find time I'll play with this

[andi (andi001)]

additional info that may be of interest:

on headphone insertion (2./4.) the "Speaker" "Mute"

- is automatically set to mute enabled, but
- has no effect (headphones are not muted either way)

and on headphone removal (3.) the "Speaker" "Mute" is enabled again

- another related bug just found: muting the "Speaker" (if headphone is removed) won't make it produce any sound again (even after alsa force-restart) (headphones still work on insertion)
  (somehow the master volume seems to be effected by this as well because it will jump to 0% and muted if one plays with the "Speaker" or "PCM" volumes in Gnome Alsamixer afterwards)

[andi (andi001)]

sorry ... after reboot everything works quite fine although not bug-free ... forget the points B,C,X... and Y1

Z) current state after reboot is:

- additional "Soundcard elements" appeared: "Headphon", "Auto Mute", "Mic Boos"

- volume states before/after headphone insertion are "remembered", but not applied e.g. to the "Speaker" or "Headphon" sliders, but the "Master" volume (e.g. Master:100%, Speaker:80% on 1. may be Master:80%,Speaker:100% on 3.)

- muting "Speaker" or "Headphon" also mutes "Master" and this is not easily undone (using Gnome Alsa Mixer) so you can hear something again (exact behaviour somewhat unclear)
  => solution is to unmute and increase the "System Settings->Sound->Output Volume"