0x103c08b0 needs HP_ONLY ac97 quirk

[Krzysztof Kosinski]

Binary package hint: pulseaudio

I'm running latest Karmic on a HP TC1100. GNOME volume slider works as follows (you can examine it by running alsamixer -c 0 and looking at ALSA mixer levels):
1. When the volume slider is at 0, both PCM and Master are at 0
2. Now when we start increasing the volume, PCM gets increased and Master starts at 0 (but unmuted), until PCM is equal to 71%; this is at about 10% slider volume
3. Then Master is increased from 0 to 100% while PCM is kept at 74%, this happens until about 63% volume
4. Finally, PCM is increased from 74% to 100%

This behavior, apparently implemented in PulseAudio, is perfect (it ensures minimum distortion from cheap audio cards), but I have one problem: phase 3 only increases Master, and ignores Headphones. This means that the volume slider does nothing to headphone volume between approximately 10 and 63%. The GConf setting at /desktop/gnome/sound/default_mixer_tracks that was used to set this doesn't work anymore.

An acceptable workaround would be to tie together Master and Headphone channels at the ALSA level, so that setting one would update the other, but I have no idea how to do this. A proper solution would be to update both Master and Headphones channels in phase 3.

[Krzysztof Kosinski (tweenk)]

Addditional information
:
When I change the connector from the default 'Analog to 'Analog Headphones / Amplifier' in the Output tab, the behavior is slightly different. When increasing the volume slider from 0 to 100%, the following things happen:
1. PCM is increased from 0 to 74%
2. Headphones are increased from 0 to 100%
3. Master is increased fom 0 to 100%
4. PCM is increased from 74 to 100%

This is totally wrong for me, because the Master and Headphone channels are independent. With the volume slider at ~15% I get full volume from the headphones, which makes them unusable. In Jaunty I could set the mixer to control both the Master and Headphone channels simultaneously, but now I can't change anything.

[Krzysztof Kosinski (tweenk)]

Lennart told me that it is a kernel bug for my sound card, and ALSA is supposed to not to expose the Headphone channel. Submitting to kernel bugzilla.

[Krzysztof Kosinski (tweenk)]

http://bugzilla.kernel.org/show_bug.cgi?id=14210

[Jonenst (jon-harper87)]

I have similar problems.
My sound card has a different channel for basses, which is not affected when I change the sound using the sound applet.
In jaunty, I would right click on the applet and select the right channels to modify (eg master and bass).
I agree that removing this step is an improvement on the user interface. However, when none of the "connectors" listed in the sound preferences offer the proper behavior, there still should be a possibiltity to fall back on the previous system.

[Jeremy Foshee (jeremyfoshee)]

Hi Krzysztof,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 429109

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Liam O'Reilly (aliam13-2)]

This is still a problem for me. I have the exact problem described above with a Dell Optiplex GX520 running up-to-date Lucid 64 bit version as of 27 May 2010.

[Liam O'Reilly (aliam13-2)]

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: csliam 1453 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 28
   Simple ctrls : 20
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=a37be7e5-c65c-40c7-bda7-adfc967d7ae7
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Dell Inc. OptiPlex GX520
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=fb642d12-f890-420e-8ae4-472b8cd613d4 ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Regression: Yes
RelatedPackageVersions: linux-firmware 1.34
Reproducible: Yes
RfKill:

Tags: lucid audio regression-release needs-upstream-testing
Uname: Linux 2.6.32-22-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WifiSyslog:

dmi.bios.date: 03/31/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0RJ290
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA07:bd03/31/2006:svnDellInc.:pnOptiPlexGX520:pvr:rvnDellInc.:rn0RJ290:rvr:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex GX520
dmi.sys.vendor: Dell Inc.

[Liam O'Reilly (aliam13-2)]

apport information

[Liam O'Reilly (aliam13-2)]

apport information

[Liam O'Reilly (aliam13-2)]

apport information

[Liam O'Reilly (aliam13-2)]

apport information

[Liam O'Reilly (aliam13-2)]

apport information

[Liam O'Reilly (aliam13-2)]

apport information

[Liam O'Reilly (aliam13-2)]

apport information

[Liam O'Reilly (aliam13-2)]

apport information

[Liam O'Reilly (aliam13-2)]

apport information

[Liam O'Reilly (aliam13-2)]

apport information

[Liam O'Reilly (aliam13-2)]

apport information

[Liam O'Reilly (aliam13-2)]

apport information

[Liam O'Reilly (aliam13-2)]

apport information

[Liam O'Reilly (aliam13-2)]

apport information

[Liam O'Reilly (aliam13-2)]

apport information

[Liam O'Reilly (aliam13-2)]

apport information

[Daniel T Chen (crimsun)]

Do any of the reporter/commenters in this bug report have a physical mute LED associated with the volume control?

[Daniel T Chen (crimsun)]

Also note that there are at least two different pieces of hardware from different reporters in this bug report, which makes it difficult to handle properly when submitting patches and associating them with one specific bug report.

Liam, you need to file a separate bug.

Jonenst, you need to file a separate bug.

[Liam O'Reilly (aliam13-2)]

Thanks Daniel - I will file a separate report later today. could you expand on what you mean by a physical LED associated with the volume control please, I don't understand what you mean.

[Daniel T Chen (crimsun)]

Liam, on some machines there is a mute LED that is toggled when the user presses the mute button (e.g., blue for unmuted, red/orange for muted). This is typically the case for laptops.

[Liam O'Reilly (aliam13-2)]

Thanks Daniel. This is a standard desktop computer that I am using, so it does not have a button of this sort.

[Jonenst (jon-harper87)]

I am not sure if I should file another bug report. I used the modified analog-output-lfe-on-mono.conf from this bug (post #27) : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/441195
The sound applet now controls the correct channels.
I can still file a new bug if you want me to, but what should I call it ?

[Po-Hsu Lin (cypressyew)]

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!