http://bugzilla.novell.com/show_bug.cgi?id=557403 http://bugzilla.novell.com/show_bug.cgi?id=557403#c2 Endre Gábriel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |endre_gabriel@freemail.hu Info Provider|endre_gabriel@freemail.hu | --- Comment #2 from Endre Gábriel 2009-11-23 21:39:20 UTC --- With the option model=toshiba sound does not work at all (neither sound output nor capture). Output of alsa-info.sh with this option is attached. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=557403 http://bugzilla.novell.com/show_bug.cgi?id=557403#c4 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |endre_gabriel@freemail.hu --- Comment #4 from Takashi Iwai 2009-11-24 15:43:27 UTC --- OK, then we need more investigations with trial-and-error. Install hda-verb package from OBS home:tiwai repo. Load the driver with model=3stack to make speaker working. Then, try to disable each output pin widget one by one, so that you can figure out which pin corresponds to the speaker output. The currently enabled output pin can be found in /proc/asound/card0/codec#1 output. Look for a line '[Pin Complex]'. There are many matching lines, and each one is a pin widget. Then check 'Pin-ctls:' line below each. If the value is either 0x40 or 0xc0, it means the output. If it's 0x2*, it's input. If it's 0, it's disabled. Now, to disable a pin, for example 0x0b, run like below (as root) hda-verb /dev/snd/hwC0D1 0x0b SET_PIN_WID 0x00 Check /proc/asound/card0/codec#1 whether the change was properly applied. Now pin-ctl should be zero. Then run aplay to test the sound output. Repeat this until the speaker (and preferably the headphone, too) output pin is spotted. Once when this is done -- assume the speaker pin is 0x0f, try like below (as root): echo 0x0f 0x90170310 > /sys/class/sound/hwC0D1/user_pin_configs echo 1 > /sys/class/sound/hwC0D1/reconfig Check the mixer status again (preferably via alsamixer), raise/unmute any new mixer elements, then test playbacks. If this still doesn't work, give the alsa-info.sh output at this state. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=557403 http://bugzilla.novell.com/show_bug.cgi?id=557403#c6 --- Comment #6 from Takashi Iwai 2009-11-29 22:57:09 UTC --- The reconfiguration must be done at the state where no program is using the sound device. Kill all processes found via "fuser /dev/snd/*" before doing reconfig. Likely a mixer applet or a sound daemon is running. Try the above without model option. Forget about model=3stack now. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=557403 http://bugzilla.novell.com/show_bug.cgi?id=557403#c8 --- Comment #8 from Takashi Iwai 2009-12-01 11:10:11 UTC --- Good to hear. Then I'll try to fix up the kernel. Note that you can put the command sequence above in /etc/init.d/boot.local or whatever to make it automatically working. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=557403 http://bugzilla.novell.com/show_bug.cgi?id=557403#c10 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:released:11.2:29469 --- Comment #10 from Swamp Workflow Management 2010-01-04 10:53:14 UTC --- Update released for: kernel-debug, kernel-debug-base, kernel-debug-base-debuginfo, kernel-debug-debuginfo, kernel-debug-debugsource, kernel-debug-devel, kernel-debug-devel-debuginfo, kernel-default, kernel-default-base, kernel-default-base-debuginfo, kernel-default-debuginfo, kernel-default-debugsource, kernel-default-devel, kernel-default-devel-debuginfo, kernel-desktop, kernel-desktop-base, kernel-desktop-base-debuginfo, kernel-desktop-debuginfo, kernel-desktop-debugsource, kernel-desktop-devel, kernel-desktop-devel-debuginfo, kernel-pae, kernel-pae-base, kernel-pae-base-debuginfo, kernel-pae-debuginfo, kernel-pae-debugsource, kernel-pae-devel, kernel-pae-devel-debuginfo, kernel-source, kernel-source-vanilla, kernel-syms, kernel-trace, kernel-trace-base, kernel-trace-base-debuginfo, kernel-trace-debuginfo, kernel-trace-debugsource, kernel-trace-devel, kernel-trace-devel-debuginfo, kernel-vanilla, kernel-vanilla-base, kernel-vanilla-base-debuginfo, kernel-vanilla-debuginfo, kernel-vanilla-debugsource, kernel-vanilla-devel, kernel-vanilla-devel-debuginfo, kernel-xen, kernel-xen-base, kernel-xen-base-debuginfo, kernel-xen-debuginfo, kernel-xen-debugsource, kernel-xen-devel, kernel-xen-devel-debuginfo, preload-kmp-default, preload-kmp-desktop Products: openSUSE 11.2 (debug, i586, x86_64) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.