Bug 128777

This feature is not implemented due to lack of hardware information.
Is it a HD-audio volume-control widget, or ACPI-controlled events?

Volume control wheel is hardware piece on the left side of laptop. It has limits (it's just ordinary resistor I suppose). In WinXP I set mixer to max, and control volume with wheel from 0 to max. In suse 10.1 volume can be controlled only with mixer (kmix or alsamixer), wheel is completely ignored. I'm really confused about this. Usially if the wheel is limitless (like jog dial in sony gadgets whith rotate infinitely to any direction), then I'd suppose there's no driver or ACPI support for it. But it HAS limits...

It doesn't matter how XP behaves.  You can set every limit on software as you like :)

My question is how the volume dial implemented on your _hardware_.  Is it implemented as a HD-audio volume-control widget node, or controlled over APCI hot-key events?  Without such a fundamental information, it's impossible to implement the driver feature...

Ok, I agree. But how can I check this?

Update: seems that sound is routed to speaker instead of master and/or pcm outputs. What happens: when I lower "internal speaker" in kmix, sound dissapears completely despite on high settings of PCM and Master. In turn, fiddling with PCM and Master in kmix does nothing to sound at all. I didn't check whether inserting headphones cut sound or not, but will test this evening. I expect it will not cut sound.

I don't know what kmix does.  Please don't use it for debugging.  kmix may have too many bugs.
Use alsamixer for debugging, instead.

It doesn't matter - kmix or alsamixer. They behave exactly the same. Here's what I noticed: actually sound outputs via internal speaker instead of stereo speakers. That's why dial wheel has no effect (it's hardware, I'm sure). So I moght say there's no sound with intel HDA driver.

??  I don't understand the description.  What is "stereo speaker"?  Do you mean the output from line/headphone-out jack?

Internally, the codec chip has no global volume control but only separate volume controls.  So, it's true that one doesn't affect another.  It's a feature.
(I think you don't have "Master" control on alsamixer, no?)
This has nothing to do with the dial volume stuff.

Yes, line-out/headphones or built-in pair of speakers, incl. subwoofer. I think that h/w dial controls "master" volume, that is actually muted by default and there's no {alsa|k}mixer slider for it.

I've managed to get back PCM and Master sliders in kmix/alsamixer after I've added model=3stack-digout to options in /etc/modprobe.d/sound file. Had no chance to test whether sound output is fine, will test this evening. I think yast should offer choice of output ports for intel hda audio driver during setup.

Created attachment 58638 [details]
Output kmix tab

Created attachment 58639 [details]
Input kmix tab

Created attachment 58640 [details]
Third kmix tab (options)

There screenshots are for the following settings in /etc/modprobe.d/sound:
options snd-hda-intel enable=1 position_fix=1 model=5stack-digout
Other models, described in ALSA-Configuration.txt do not work. Even this model (5stack-digout) works not as expected: when there're no headphones, sound goes via 2.1 built-in laptop stereo speakers, but is controlled with slider labeled 'Side'. If I plug in headphones, 2.1 stereo speakers are cut off, BUT now sound loudness is controlled with 'Front' slider. 'PCM' slider affects both when headphones are plugged or unplugged. Slider that appears on single click over kmix tray icon controls 'PC Speaker' volume. Kmix shows and controls exactly the same as alsamixer (see screenshot below).

Created attachment 58641 [details]
Alsamixer controls for 5stack-digout

Addon: hardware volume dial still does not affect any sound with this config (5stack-digout). I suspect that since Intel HDA offers more then stereo, and my laptop has only 2 tweeters and 1 subwoofer built-in, other channels also get routed by driver to these 2 tweeters. Hardware dial affects only front (stereo) circuits, while others (side, center, back, whatever) are routed directly bypassing h/w dial. I think snd-hda-intel just doesn't know about what ports and what channels should go where in case of Amilo laptop. Here's what audio outputs/inputs it has:

o. 2 speakers built-in, left and right. PC Speaker (i.e. beeper) sounds also are played by them.
o. 1 subwoofer on bottom.
o. 1 hardware dial wheel (resistor) that controls speakers volume.
o. 1 microphone built-in on top upder left palm rest.
o. 1 jack for line input combined with external mic input.
o. 1 jack for headphones combined with SPDIF.

Chip used is Realtek ALC880.

I found very similar bug at alsa-project, here's the link:
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1627
It is reported against similar to mine Fujitsu-Siemens laptop model, so I left comment there as well.

Should have been already fixed on beta8.

Nothing changed on beta8 unfortunately.

Hm, then the proper entry for your device is missing in the config table.  Which model option value is most suitable?

For more checking, please attach the contents of /proc/asound/card0/codec#* files and the output of "lspci -nv", too.

Hi there,

just re-installed openSUSE 10.2 factory on this laptop. The closest model is z71v, lspci and codecs are attached. Volume control wheel still doesn't work.

Created attachment 102975 [details]
Contents of /proc/asound/card0/codec#*

Created attachment 102976 [details]
Output of lspci -nv

Any progress on this bug? Still the same on openSUSE 10.2/BETA1+.

Hy! I have the same annoying bug - my system is Fujitsu-Siemens Amilo M3438G. Any progress on this bug?

This should be a problem of the upstream kernel, so the problem persists on openSUSE kernels unless the vanilla kernel gets fixes.

You can check the latest ALSA driver (preferably HG version) from www.alsa-project.org, or the latest 2.6.21-git tree.  The daily snapshot tarball of alsa-driver is found at
    ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/

Resolved to LATER until the openSUSE kernel gets updated.

mass reopening all 10.2 LATER+REMIND bugs.

close all 10.2 LATER/REMIND bugs as WONTFIX. Reopen yourself if you still plan to work on it.