Re: [alsa-devel] Problem with DELL XPS M1530
Hi. I am the mentioned user with this problem. Just thought I'd give you a little more info on this problem.
What wishie described was correct, except it's the internal speakers and the /left/ hp-jack that stopped working, while the right one is still ok. Like he wrote, the reason we started this debugging was to get mic sound on my system. The thing I think is worth mentioning is that with alsa 1.0.14 on an out-of-the box Ubuntu Gutsy, both hp-jacks and the internal speakers worked for me. People in #alsa told me that the module was not loaded correctly, but whatever was loaded _almost_ worked well :-)
- Anders
At Tue, 19 Feb 2008 17:24:04 +0100, Anders Rønningen wrote:
Hi. I am the mentioned user with this problem. Just thought I'd give you a little more info on this problem.
What wishie described was correct, except it's the internal speakers and the /left/ hp-jack that stopped working, while the right one is still ok. Like he wrote, the reason we started this debugging was to get mic sound on my system. The thing I think is worth mentioning is that with alsa 1.0.14 on an out-of-the box Ubuntu Gutsy, both hp-jacks and the internal speakers worked for me. People in #alsa told me that the module was not loaded correctly, but whatever was loaded _almost_ worked well :-)
OK, please build the driver with --with-debug=full option and show the kernel messages such as "autoconfig: ..." and "dac_nids...", etc. This contains the information that the pin configuration parser uses.
Also, unmute and adjust "Surround" volume.
Takashi
Hi Takashi.
Some dmesg output:
[ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:2994: autoconfig: line_outs=1 (0xf/0x0/0x0/0x0/0x0) [ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:2998: speaker_outs=1 (0xd/0x0/0x0/0x0/0x0) [ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3002: hp_outs=1 (0xa/0xf/0x0/0x0/0x0) [ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3003: mono: mono_out=0x0 [ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3011: inputs: mic=0xe, fmic=0x0, line=0x0, fline=0x0, cd=0x0, aux=0x0 [ 14.196000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/../../alsa-kernel/pci/hda/patch_sigmatel.c:2224: dac_nids=2 (0x5/0x4/0x0/0x0/0x0)
Unmuted and adjusted Surround volume, but it made no difference.
- Anders
Takashi Iwai wrote:
At Tue, 19 Feb 2008 17:24:04 +0100, Anders Rønningen wrote:
Hi. I am the mentioned user with this problem. Just thought I'd give you a little more info on this problem.
What wishie described was correct, except it's the internal speakers and the /left/ hp-jack that stopped working, while the right one is still ok. Like he wrote, the reason we started this debugging was to get mic sound on my system. The thing I think is worth mentioning is that with alsa 1.0.14 on an out-of-the box Ubuntu Gutsy, both hp-jacks and the internal speakers worked for me. People in #alsa told me that the module was not loaded correctly, but whatever was loaded _almost_ worked well :-)
OK, please build the driver with --with-debug=full option and show the kernel messages such as "autoconfig: ..." and "dac_nids...", etc. This contains the information that the pin configuration parser uses.
Also, unmute and adjust "Surround" volume.
Takashi
On Wed, 2008-02-20 at 02:25 +0800, Anders Rønningen wrote:
Hi Takashi.
Some dmesg output:
[ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:2994: autoconfig: line_outs=1 (0xf/0x0/0x0/0x0/0x0) [ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:2998: speaker_outs=1 (0xd/0x0/0x0/0x0/0x0) [ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3002: hp_outs=1 (0xa/0xf/0x0/0x0/0x0) [ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3003: mono: mono_out=0x0 [ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3011: inputs: mic=0xe, fmic=0x0, line=0x0, fline=0x0, cd=0x0, aux=0x0 [ 14.196000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/../../alsa-kernel/pci/hda/patch_sigmatel.c:2224: dac_nids=2 (0x5/0x4/0x0/0x0/0x0)
Unmuted and adjusted Surround volume, but it made no difference.
- Anders
It's weird that 0xf is in both the line_outs and hp_outs. And the hp_outs=1 when there are two items.
What is the original configuration of pin 0xf? Please try to get rid of this line from the alsa-kernel/pci/hda/patch_sigmatel.c.
SND_PCI_QUIRK(PCI_VENDOR_ID_DELL, 0x022e, "Dell ", STAC_DELL_BIOS),
Rebuild and install the driver. Please give the output of "cat /proc/asound/card0/codec#0".
Thanks!
Takashi Iwai wrote:
At Tue, 19 Feb 2008 17:24:04 +0100, Anders Rønningen wrote:
Hi. I am the mentioned user with this problem. Just thought I'd
give you
a little more info on this problem.
What wishie described was correct, except it's the internal
speakers and
the /left/ hp-jack that stopped working, while the right one is
still
ok. Like he wrote, the reason we started this debugging was to get
mic
sound on my system. The thing I think is worth mentioning is that
with
alsa 1.0.14 on an out-of-the box Ubuntu Gutsy, both hp-jacks and
the
internal speakers worked for me. People in #alsa told me that the
module
was not loaded correctly, but whatever was loaded _almost_ worked
well :-)
OK, please build the driver with --with-debug=full option and show
the
kernel messages such as "autoconfig: ..." and "dac_nids...", etc. This contains the information that the pin configuration parser
uses.
Also, unmute and adjust "Surround" volume.
Takashi
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
At Wed, 20 Feb 2008 17:49:00 +0800, Jiang zhe wrote:
On Wed, 2008-02-20 at 02:25 +0800, Anders Rønningen wrote:
Hi Takashi.
Some dmesg output:
[ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:2994: autoconfig: line_outs=1 (0xf/0x0/0x0/0x0/0x0) [ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:2998: speaker_outs=1 (0xd/0x0/0x0/0x0/0x0) [ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3002: hp_outs=1 (0xa/0xf/0x0/0x0/0x0) [ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3003: mono: mono_out=0x0 [ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3011: inputs: mic=0xe, fmic=0x0, line=0x0, fline=0x0, cd=0x0, aux=0x0 [ 14.196000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/../../alsa-kernel/pci/hda/patch_sigmatel.c:2224: dac_nids=2 (0x5/0x4/0x0/0x0/0x0)
Unmuted and adjusted Surround volume, but it made no difference.
- Anders
It's weird that 0xf is in both the line_outs and hp_outs. And the hp_outs=1 when there are two items.
It's due to a fix for an ALC268 laptop that has also two HPs but one is actually a line-out. Note that hp_outs=1 in the print above. The 0x0f in hp_outs is simply a garbage. Maybe that patch broke the double HPs with STAC9228...
Takashi
Hi, Takashi:
Maybe we can try handling the ALC268 laptop HP issue in the patch_realtek.c. The patch for the hda_codec.c seems to conflict with the code of patch_sigmatel.c.
The patch_sigmatel.c depends on line_out_type == AUTO_PIN_SPEAKER_OUT and hp_outs > 1 in order to handle the 2 HP jacks issue.
/* If we have no real line-out pin and multiple hp-outs, HPs should * be set up as multi-channel outputs. */ if (spec->autocfg.line_out_type == AUTO_PIN_SPEAKER_OUT && spec->autocfg.hp_outs > 1) { /* Copy hp_outs to line_outs, backup line_outs in * speaker_outs so that the following routines can handle * HP pins as primary outputs. */ memcpy(spec->autocfg.speaker_pins, spec->autocfg.line_out_pins, sizeof(spec->autocfg.line_out_pins)); spec->autocfg.speaker_outs = spec->autocfg.line_outs; memcpy(spec->autocfg.line_out_pins, spec->autocfg.hp_pins, sizeof(spec->autocfg.hp_pins)); spec->autocfg.line_outs = spec->autocfg.hp_outs; hp_speaker_swap = 1; }
Thanks!
It's weird that 0xf is in both the line_outs and hp_outs. And the hp_outs=1 when there are two items.
It's due to a fix for an ALC268 laptop that has also two HPs but one is actually a line-out. Note that hp_outs=1 in the print above. The 0x0f in hp_outs is simply a garbage. Maybe that patch broke the double HPs with STAC9228...
Takashi
At Thu, 21 Feb 2008 11:06:15 +0800, Jiang zhe wrote:
Hi, Takashi:
Maybe we can try handling the ALC268 laptop HP issue in the patch_realtek.c. The patch for the hda_codec.c seems to conflict with the code of patch_sigmatel.c.
Yes, I overlooked this at the time I fixed ALC codec issues. Moving the fix-up to alc-specific part is one solution.
But, I guess this is fixed by the recent patches by Matthew, which I committed to HG tree right now. It fixes the wrong association number of the widget 0x0f -- the headphone jacks should have the association number 0x0f.
If this still doesn't work, let's move the fix-up code from the common place.
thanks,
Takashi
At Tue, 19 Feb 2008 19:25:24 +0100, Anders Rønningen wrote:
Hi Takashi.
Some dmesg output:
[ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:2994: autoconfig: line_outs=1 (0xf/0x0/0x0/0x0/0x0) [ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:2998: speaker_outs=1 (0xd/0x0/0x0/0x0/0x0) [ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3002: hp_outs=1 (0xa/0xf/0x0/0x0/0x0) [ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3003: mono: mono_out=0x0 [ 14.192000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/hda_codec.c:3011: inputs: mic=0xe, fmic=0x0, line=0x0, fline=0x0, cd=0x0, aux=0x0 [ 14.196000] ALSA /mnt/storage/source/alsa/alsa-driver-hg20080217/pci/hda/../../alsa-kernel/pci/hda/patch_sigmatel.c:2224: dac_nids=2 (0x5/0x4/0x0/0x0/0x0)
Unmuted and adjusted Surround volume, but it made no difference.
Please upload the alsa-info.sh output again. No difference in the output but there must be a difference in the codec setting.
Also, just to make the situation clear: the problem is that the speaker and the rear HP don't give sound output even if you *don't* plug in the front HP, right?
Takashi
participants (3)
-
Anders Rønningen -
Jiang zhe -
Takashi Iwai