Skip to contentSkip to conversation

ALSA HDA Intel stoped to work in 2.6.16-*

PATCH New Otavio Salvador 6 participants 22 messages Feb 27, 2006 – Mar 11, 2009

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Hello,

I was using 2.6.15 without trouble but wanna try the new 2.6.16 version so I compiled it by myself without much hassle. All worked fine but ALSA.

My sound device is the following:

0000:00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04)

and it stoped to work. Would someone know anything about it? it's a regressions if compared to 2.6.15.

If you wish something more, please let me know.

Thanks in advance,

Signature · 8 lines
        O T A V I O    S A L V A D O R
---------------------------------------------
 E-mail: [email protected]      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
 you the whole house."
#1 lore raw
Quoted 5 lines · Otavio Salvador

Hello,

I was using 2.6.15 without trouble but wanna try the new 2.6.16 version so I compiled it by myself without much hassle. All worked fine but ALSA.

What 2.6.16-rc version did you test, could you try -rc5 if you tried an earlier version?

(also, include dmesg of the non-working version, etc)

#3 lore raw
In reply to Otavio Salvador

At Mon, 27 Feb 2006 10:15:25 -0300,

Quoted 7 lines · Otavio Salvador

Hello,

I was using 2.6.15 without trouble but wanna try the new 2.6.16 version so I compiled it by myself without much hassle. All worked fine but ALSA.

Quoted 5 lines

My sound device is the following:

0000:00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04)

and it stoped to work.

Please elaborate what do you mean "stoped to work"? Only silent output, DMA not working, or what?

Also, more hardware detail is needed - which machine and which codec?

This kind of problem is likely due to a broken BIOS. The current code parses the default pin configuration set up via BIOS while the older version used the fixed pin assignment (depending on the codec chip, though).
In most cases, it can be recovered by specifying a proper model module option. See ALSA-Configuration.txt for details.

Takashi

#2 lore raw
In reply to Diego Calleja
Quoted 12 lines · Diego Calleja
Quoted 5 lines · Otavio Salvador

Hello,

I was using 2.6.15 without trouble but wanna try the new 2.6.16 version so I compiled it by myself without much hassle. All worked fine but ALSA.

What 2.6.16-rc version did you test, could you try -rc5 if you tried an earlier version?

I tried with rc5 and it continue to not work.

Signature · 9 lines
-- 
        O T A V I O    S A L V A D O R
---------------------------------------------
 E-mail: [email protected]      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
 you the whole house."
#4 lore raw
In reply to Takashi Iwai
Quoted 9 lines · Takashi Iwai

At Mon, 27 Feb 2006 10:15:25 -0300,

Quoted 7 lines · Otavio Salvador

Hello,

I was using 2.6.15 without trouble but wanna try the new 2.6.16 version so I compiled it by myself without much hassle. All worked fine but ALSA.

Quoted 8 lines
Quoted 5 lines

My sound device is the following:

0000:00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04)

and it stoped to work.

Please elaborate what do you mean "stoped to work"? Only silent output, DMA not working, or what?

Only silent output.

Quoted 10 lines

Also, more hardware detail is needed - which machine and which codec?

This kind of problem is likely due to a broken BIOS. The current code parses the default pin configuration set up via BIOS while the older version used the fixed pin assignment (depending on the codec chip, though).
In most cases, it can be recovered by specifying a proper model module option. See ALSA-Configuration.txt for details.

I wasn't able to do it. My lspci output for it is the following:

0000:00:1b.0 0403: 8086:2668 (rev 04)
0000:00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04)

0000:00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04)
Subsystem: QUANTA Computer Inc: Unknown device 0729
Flags: fast devsel, IRQ 17
Memory at b0000000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Capabilities: [70] #10 [0091]

I hope it helps.

Signature · 8 lines
        O T A V I O    S A L V A D O R
---------------------------------------------
 E-mail: [email protected]      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
 you the whole house."
#5 lore raw

At Tue, 28 Feb 2006 05:51:26 -0300,

Quoted 9 lines · Otavio Salvador
Quoted 7 lines

This kind of problem is likely due to a broken BIOS. The current code parses the default pin configuration set up via BIOS while the older version used the fixed pin assignment (depending on the codec chip, though).
In most cases, it can be recovered by specifying a proper model module option. See ALSA-Configuration.txt for details.

I wasn't able to do it.

Didn't it worked? Which module parameter did you use?

Quoted 13 lines

My lspci output for it is the following:

0000:00:1b.0 0403: 8086:2668 (rev 04)
0000:00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04)

0000:00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04)
Subsystem: QUANTA Computer Inc: Unknown device 0729
Flags: fast devsel, IRQ 17
Memory at b0000000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Capabilities: [70] #10 [0091]

Quoted 1 line

I hope it helps.

I need more detail of the hardware -- what model of a laptop or a desktop from which vendor.

Takashi

#6 lore raw
Quoted 10 lines · Takashi Iwai

At Tue, 28 Feb 2006 05:51:26 -0300,

Quoted 8 lines · Otavio Salvador
Quoted 7 lines

This kind of problem is likely due to a broken BIOS. The current code parses the default pin configuration set up via BIOS while the older version used the fixed pin assignment (depending on the codec chip, though).
In most cases, it can be recovered by specifying a proper model module option. See ALSA-Configuration.txt for details.

Quoted 3 lines
Quoted 1 line

I wasn't able to do it.

Didn't it worked? Which module parameter did you use?

I tried model=hp, model=fujistsu and priority_fix={1,2}. Neither did it work.

Quoted 4 lines
Quoted 1 line

I hope it helps.

I need more detail of the hardware -- what model of a laptop or a desktop from which vendor.

http://www.ctlnotebooks.com/v2/notebook_spec.aspx?id=21&hdr=Products

Signature · 8 lines
        O T A V I O    S A L V A D O R
---------------------------------------------
 E-mail: [email protected]      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
 you the whole house."
#7 lore raw

At Tue, 28 Feb 2006 17:28:36 -0300,

Quoted 13 lines · Otavio Salvador
Quoted 10 lines · Takashi Iwai

At Tue, 28 Feb 2006 05:51:26 -0300,

Quoted 8 lines · Otavio Salvador
Quoted 7 lines

This kind of problem is likely due to a broken BIOS. The current code parses the default pin configuration set up via BIOS while the older version used the fixed pin assignment (depending on the codec chip, though).
In most cases, it can be recovered by specifying a proper model module option. See ALSA-Configuration.txt for details.

Quoted 6 lines
Quoted 3 lines
Quoted 1 line

I wasn't able to do it.

Didn't it worked? Which module parameter did you use?

I tried model=hp, model=fujistsu and priority_fix={1,2}. Neither did it work.

Try model=basic. It's the old default.
(seems that it's missing in the documentation...)

Takashi

#8 lore raw
Quoted 7 lines · Takashi Iwai
Quoted 4 lines
Quoted 1 line

Didn't it worked? Which module parameter did you use?

I tried model=hp, model=fujistsu and priority_fix={1,2}. Neither did it work.

Try model=basic. It's the old default.
(seems that it's missing in the documentation...)

Yes. Using model=basic it works fine.

I propose the following patch to solve it then:

Do you think it's ok?

sound/pci/hda/patch_realtek.c +2 -2
index b767552..2be4a4c 100644
@@ -2946,8 +2946,8 @@ static int alc260_auto_init(struct hda_c
  */
 static struct hda_board_config alc260_cfg_tbl[] = {
        { .modelname = "basic", .config = ALC260_BASIC },
-       { .pci_subvendor = 0x104d, .pci_subdevice = 0x81bb,
-         .config = ALC260_BASIC }, /* Sony VAIO */
+       { .pci_subvendor = 0x104d, .pci_subdevice = 0x81bb, .config = ALC260_BASIC },
+       { .pci_subvendor = 0x8086, .pci_subdevice = 0x2668, .config = ALC260_BASIC },
        { .modelname = "hp", .config = ALC260_HP },
        { .pci_subvendor = 0x103c, .pci_subdevice = 0x3010, .config = ALC260_HP },
        { .pci_subvendor = 0x103c, .pci_subdevice = 0x3011, .config = ALC260_HP },
Signature · 8 lines
        O T A V I O    S A L V A D O R
---------------------------------------------
 E-mail: [email protected]      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
 you the whole house."
#9 lore raw

At Wed, 01 Mar 2006 23:24:02 -0300,

Quoted 22 lines · Otavio Salvador
Quoted 7 lines · Takashi Iwai
Quoted 4 lines
Quoted 1 line

Didn't it worked? Which module parameter did you use?

I tried model=hp, model=fujistsu and priority_fix={1,2}. Neither did it work.

Try model=basic. It's the old default.
(seems that it's missing in the documentation...)

Yes. Using model=basic it works fine.

I propose the following patch to solve it then:

Do you think it's ok?

sound/pci/hda/patch_realtek.c +0 -0
index b767552..2be4a4c 100644

sound/pci/hda/patch_realtek.c static int alc260_auto_init(struct hda_c · line 2950

Quoted 7 lines
sound/pci/hda/patch_realtek.c +2 -2
@@ -2946,8 +2946,8 @@ static int alc260_auto_init(struct hda_c
  */
 static struct hda_board_config alc260_cfg_tbl[] = {
        { .modelname = "basic", .config = ALC260_BASIC },
-       { .pci_subvendor = 0x104d, .pci_subdevice = 0x81bb,
-         .config = ALC260_BASIC }, /* Sony VAIO */
+       { .pci_subvendor = 0x104d, .pci_subdevice = 0x81bb, .config = ALC260_BASIC },
+       { .pci_subvendor = 0x8086, .pci_subdevice = 0x2668, .config = ALC260_BASIC },

Are you sure that your device has PCI SUB-system id 8086:2668 ?

Takashi

#10 lore raw
Quoted 1 line · Takashi Iwai

Are you sure that your device has PCI SUB-system id 8086:2668 ?

oh no! Sorry!

0000:00:1b.0 0403: 8086:2668 (rev 04)

        Subsystem: 152d:0729
                   ^^^^^^^^^
Signature · 8 lines
        O T A V I O    S A L V A D O R
---------------------------------------------
 E-mail: [email protected]      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
 you the whole house."
#11 lore raw
Quoted 9 lines · Otavio Salvador
Quoted 1 line · Takashi Iwai

Are you sure that your device has PCI SUB-system id 8086:2668 ?

oh no! Sorry!

0000:00:1b.0 0403: 8086:2668 (rev 04)

        Subsystem: 152d:0729
                   ^^^^^^^^^

Can you make a patch with the correct id test whether it fixes your problem (without model=basic)?

TIA
Adrian

Signature · 4 lines
       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed
#21 lore raw

PATCH 1/1 ALSA-Configuration.txt: snd-hda-intel: document model=basic

In reply to Takashi Iwai
Quoted 17 lines · Takashi Iwai

At Tue, 28 Feb 2006 17:28:36 -0300,

Quoted 15 lines · Otavio Salvador
Quoted 12 lines · Takashi Iwai

At Tue, 28 Feb 2006 05:51:26 -0300,

Quoted 9 lines · Otavio Salvador
Quoted 7 lines

This kind of problem is likely due to a broken BIOS. The current code parses the default pin configuration set up via BIOS while the older version used the fixed pin assignment (depending on the codec chip, though).
In most cases, it can be recovered by specifying a proper model module option. See ALSA-Configuration.txt for details.

I wasn't able to do it.

Quoted 7 lines
Quoted 4 lines
Quoted 1 line

Didn't it worked? Which module parameter did you use?

I tried model=hp, model=fujistsu and priority_fix={1,2}. Neither did it work.

Try model=basic. It's the old default.
(seems that it's missing in the documentation...)

What about the patch below for 2.6.16?

Quoted 1 line

Takashi

cu
Adrian

<-- snip -->

Document the model=basic option in the snd-hda-intel driver.

Documentation/sound/alsa/ALSA-Configuration.txt renamed from Documentation/sound/alsa/ALSA-Configuration.txt.old +1 -0
@@ -705,6 +705,7 @@
 			$CONFIG_SND_DEBUG=y
 
 	ALC260
+	  basic		base mode
 	  hp		HP machines
 	  fujitsu	Fujitsu S7020
 

-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

#12 lore raw
In reply to Adrian Bunk

At Sat, 4 Mar 2006 15:51:14 +0100,

Quoted 6 lines · Adrian Bunk
Quoted 4 lines · Otavio Salvador
Quoted 1 line · Takashi Iwai

Are you sure that your device has PCI SUB-system id 8086:2668 ?

Quoted 8 lines
Quoted 5 lines

oh no! Sorry!

0000:00:1b.0 0403: 8086:2668 (rev 04)

        Subsystem: 152d:0729
                   ^^^^^^^^^

Can you make a patch with the correct id test whether it fixes your problem (without model=basic)?

This one should work for his device.

Takashi
===

[PATCH] Add default entry for CTL Travel Master U553W

Added the default entry of ALC880 configuration table for CTL Travel Master U553W.

---

sound/pci/hda/patch_realtek.c +2 -0
index b767552..d5cd3a1 100644
@@ -2948,6 +2948,8 @@ static struct hda_board_config alc260_cf
 	{ .modelname = "basic", .config = ALC260_BASIC },
 	{ .pci_subvendor = 0x104d, .pci_subdevice = 0x81bb,
 	  .config = ALC260_BASIC }, /* Sony VAIO */
+	{ .pci_subvendor = 0x152d, .pci_subdevice = 0x0729,
+	  .config = ALC260_BASIC }, /* CTL Travel Master U553W */
 	{ .modelname = "hp", .config = ALC260_HP },
 	{ .pci_subvendor = 0x103c, .pci_subdevice = 0x3010, .config = ALC260_HP },
 	{ .pci_subvendor = 0x103c, .pci_subdevice = 0x3011, .config = ALC260_HP },
#13 lore raw

At Mon, 6 Mar 2006 15:16:15 +0100,

Quoted 36 lines · Takashi Iwai

At Sat, 4 Mar 2006 15:51:14 +0100,

Quoted 6 lines · Adrian Bunk
Quoted 4 lines · Otavio Salvador
Quoted 1 line · Takashi Iwai

Are you sure that your device has PCI SUB-system id 8086:2668 ?

Quoted 8 lines
Quoted 5 lines

oh no! Sorry!

0000:00:1b.0 0403: 8086:2668 (rev 04)

        Subsystem: 152d:0729
                   ^^^^^^^^^

Can you make a patch with the correct id test whether it fixes your problem (without model=basic)?

This one should work for his device.

Takashi
===

[PATCH] Add default entry for CTL Travel Master U553W

Added the default entry of ALC880 configuration table for CTL Travel Master U553W.

---

sound/pci/hda/patch_realtek.c +0 -0
index b767552..d5cd3a1 100644

sound/pci/hda/patch_realtek.c static struct hda_board_config alc260_cf · line 2955

Quoted 8 lines
sound/pci/hda/patch_realtek.c +2 -0
@@ -2948,6 +2948,8 @@ static struct hda_board_config alc260_cf
      { .modelname = "basic", .config = ALC260_BASIC },
      { .pci_subvendor = 0x104d, .pci_subdevice = 0x81bb,
        .config = ALC260_BASIC }, /* Sony VAIO */
+     { .pci_subvendor = 0x152d, .pci_subdevice = 0x0729,
+       .config = ALC260_BASIC }, /* CTL Travel Master U553W */
      { .modelname = "hp", .config = ALC260_HP },
      { .pci_subvendor = 0x103c, .pci_subdevice = 0x3010, .config = ALC260_HP },
      { .pci_subvendor = 0x103c, .pci_subdevice = 0x3011, .config = ALC260_HP },

It has been three years since the above patch was posted with a request for testing. No testing reply ever appeared, and the patch was committed as submitted. On the relevant hardware, I determined the patch to be incorrect. For the git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
head, the following patch appears to fix it correctly:

sound/pci/hda/patch_realtek.c +1 -1
index 6c26afc..87ec806 100644
@@ -5692,7 +5692,7 @@ static struct snd_pci_quirk alc260_cfg_tbl[] = {
        SND_PCI_QUIRK(0x104d, 0x81cc, "Sony VAIO", ALC260_BASIC),
        SND_PCI_QUIRK(0x104d, 0x81cd, "Sony VAIO", ALC260_BASIC),
        SND_PCI_QUIRK(0x10cf, 0x1326, "Fujitsu S702X", ALC260_FUJITSU_S702X),
-       SND_PCI_QUIRK(0x152d, 0x0729, "CTL U553W", ALC260_BASIC),
+       SND_PCI_QUIRK(0x152d, 0x0729, "CTL U553W", ALC260_WILL),
        SND_PCI_QUIRK(0x161f, 0x2057, "Replacer 672V", ALC260_REPLACER_672V),
        SND_PCI_QUIRK(0x1631, 0xc017, "PB V7900", ALC260_WILL),
        {}
#14 lore raw

(adding CCs).

Usually, sending such things to the LKML alone doesn't really work. Please always send a CC to the relevant subsystem maintainer.

Quoted 72 lines · Daniel Gimpelevich

At Mon, 6 Mar 2006 15:16:15 +0100,

Quoted 36 lines · Takashi Iwai

At Sat, 4 Mar 2006 15:51:14 +0100,

Quoted 6 lines · Adrian Bunk
Quoted 4 lines · Otavio Salvador
Quoted 1 line · Takashi Iwai

Are you sure that your device has PCI SUB-system id 8086:2668 ?

Quoted 8 lines
Quoted 5 lines

oh no! Sorry!

0000:00:1b.0 0403: 8086:2668 (rev 04)

        Subsystem: 152d:0729
                   ^^^^^^^^^

Can you make a patch with the correct id test whether it fixes your problem (without model=basic)?

This one should work for his device.

Takashi
===

[PATCH] Add default entry for CTL Travel Master U553W

Added the default entry of ALC880 configuration table for CTL Travel Master U553W.

---

sound/pci/hda/patch_realtek.c +0 -0
index b767552..d5cd3a1 100644

sound/pci/hda/patch_realtek.c static struct hda_board_config alc260_cf · line 2955

Quoted 8 lines
sound/pci/hda/patch_realtek.c +2 -0
@@ -2948,6 +2948,8 @@ static struct hda_board_config alc260_cf
      { .modelname = "basic", .config = ALC260_BASIC },
      { .pci_subvendor = 0x104d, .pci_subdevice = 0x81bb,
        .config = ALC260_BASIC }, /* Sony VAIO */
+     { .pci_subvendor = 0x152d, .pci_subdevice = 0x0729,
+       .config = ALC260_BASIC }, /* CTL Travel Master U553W */
      { .modelname = "hp", .config = ALC260_HP },
      { .pci_subvendor = 0x103c, .pci_subdevice = 0x3010, .config = ALC260_HP },
      { .pci_subvendor = 0x103c, .pci_subdevice = 0x3011, .config = ALC260_HP },

It has been three years since the above patch was posted with a request for testing. No testing reply ever appeared, and the patch was committed as submitted. On the relevant hardware, I determined the patch to be incorrect. For the git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
head, the following patch appears to fix it correctly:

sound/pci/hda/patch_realtek.c +1 -2
index 6c26afc..87ec806 100644
@@ -5692,7 +5692,7 @@ static struct snd_pci_quirk alc260_cfg_tbl[] = {
        SND_PCI_QUIRK(0x104d, 0x81cc, "Sony VAIO", ALC260_BASIC),
        SND_PCI_QUIRK(0x104d, 0x81cd, "Sony VAIO", ALC260_BASIC),
        SND_PCI_QUIRK(0x10cf, 0x1326, "Fujitsu S702X", ALC260_FUJITSU_S702X),
-       SND_PCI_QUIRK(0x152d, 0x0729, "CTL U553W", ALC260_BASIC),
+       SND_PCI_QUIRK(0x152d, 0x0729, "CTL U553W", ALC260_WILL),
        SND_PCI_QUIRK(0x161f, 0x2057, "Replacer 672V", ALC260_REPLACER_672V),
        SND_PCI_QUIRK(0x1631, 0xc017, "PB V7900", ALC260_WILL),
        {}
 
--
#15 lore raw

At Sat, 7 Mar 2009 19:00:44 +0100,

Quoted 5 lines · Rafael J. Wysocki

(adding CCs).

Usually, sending such things to the LKML alone doesn't really work. Please always send a CC to the relevant subsystem maintainer.

Yep, thanks.

A comment about this change below...

Quoted 44 lines · Daniel Gimpelevich
Quoted 43 lines

At Mon, 6 Mar 2006 15:16:15 +0100,

Quoted 40 lines · Takashi Iwai

At Sat, 4 Mar 2006 15:51:14 +0100,

Quoted 6 lines · Adrian Bunk
Quoted 4 lines · Otavio Salvador
Quoted 1 line · Takashi Iwai

Are you sure that your device has PCI SUB-system id 8086:2668 ?

Quoted 8 lines
Quoted 5 lines

oh no! Sorry!

0000:00:1b.0 0403: 8086:2668 (rev 04)

        Subsystem: 152d:0729
                   ^^^^^^^^^

Can you make a patch with the correct id test whether it fixes your problem (without model=basic)?

This one should work for his device.

Takashi
===

[PATCH] Add default entry for CTL Travel Master U553W

Added the default entry of ALC880 configuration table for CTL Travel Master U553W.

---

sound/pci/hda/patch_realtek.c +1 -0
index b767552..d5cd3a1 100644
@@ -2948,6 +2948,8 @@ static struct hda_board_config alc260_cf
      { .modelname = "basic", .config = ALC260_BASIC },
      { .pci_subvendor = 0x104d, .pci_subdevice = 0x81bb,
        .config = ALC260_BASIC }, /* Sony VAIO */
+     { .pci_subvendor = 0x152d, .pci_subdevice = 0x0729,
Quoted 8 lines
Quoted 8 lines

sound/pci/hda/patch_realtek.c static struct hda_board_config alc260_cf · line 2955

Quoted 4 lines
sound/pci/hda/patch_realtek.c +1 -0
+       .config = ALC260_BASIC }, /* CTL Travel Master U553W */
      { .modelname = "hp", .config = ALC260_HP },
      { .pci_subvendor = 0x103c, .pci_subdevice = 0x3010, .config = ALC260_HP },
      { .pci_subvendor = 0x103c, .pci_subdevice = 0x3011, .config = ALC260_HP },

It has been three years since the above patch was posted with a request for testing. No testing reply ever appeared, and the patch was committed as submitted. On the relevant hardware, I determined the patch to be incorrect.

Daniel, how "incorrect" do you mean exactly?

As you cited, the above patch was added for the request for the specific model, so the patch itself is correct per definition. What wrong could be the choice of the model option by the original poster, which I cannot judge.

Of course I have no objection to fix the model entry at all, but I need a more proper justification.

thanks,

Takashi

#16 lore raw
Quoted 9 lines · Takashi Iwai <tiwai <at> suse.de> writes:

Daniel, how "incorrect" do you mean exactly?

As you cited, the above patch was added for the request for the specific model, so the patch itself is correct per definition. What wrong could be the choice of the model option by the original poster, which I cannot judge.

Of course I have no objection to fix the model entry at all, but I need a more proper justification.

The master volume control appeared to be affecting the wrong control line, and there was no way to turn off IEC958, which appeared to be on by default.

#17 lore raw

At Sun, 8 Mar 2009 23:21:13 +0000 (UTC),

Quoted 10 lines · Daniel Gimpelevich
Quoted 7 lines · Takashi Iwai <tiwai <at> suse.de> writes:

Daniel, how "incorrect" do you mean exactly?

As you cited, the above patch was added for the request for the specific model, so the patch itself is correct per definition. What wrong could be the choice of the model option by the original poster, which I cannot judge.

Quoted 4 lines
Quoted 2 lines

Of course I have no objection to fix the model entry at all, but I need a more proper justification.

The master volume control appeared to be affecting the wrong control line,

Is it so with the latest 2.6.29 kernel?
(Also you aren't accessing pulse plugin, right?)

Quoted 2 lines

and
there was no way to turn off IEC958, which appeared to be on by default.

This should work.

% amixer -Dhw:0 set IEC958 mute

Takashi

#18 lore raw

(Re-adding mistakenly snipped CC's…)

Quoted 12 lines · Takashi Iwai

At Sun, 8 Mar 2009 23:21:13 +0000 (UTC),

Quoted 10 lines · Daniel Gimpelevich
Quoted 7 lines · Takashi Iwai <tiwai <at> suse.de> writes:

Daniel, how "incorrect" do you mean exactly?

As you cited, the above patch was added for the request for the specific model, so the patch itself is correct per definition. What wrong could be the choice of the model option by the original poster, which I cannot judge.

Quoted 7 lines
Quoted 4 lines
Quoted 2 lines

Of course I have no objection to fix the model entry at all, but I need a more proper justification.

The master volume control appeared to be affecting the wrong control line,

Is it so with the latest 2.6.29 kernel?
(Also you aren't accessing pulse plugin, right?)

Was using alsamixer to test, without pulseaudio running. The underlying issue is unchanged in three years of commits.

Quoted 6 lines
Quoted 2 lines

and
there was no way to turn off IEC958, which appeared to be on by default.

This should work.

% amixer -Dhw:0 set IEC958 mute

It does work, but only after the patch I submitted (or by using the equivalent module argument).

#19 lore raw

At Wed, 11 Mar 2009 06:07:20 -0700,

Quoted 19 lines · Daniel Gimpelevich

(Re-adding mistakenly snipped CC's…)

Quoted 15 lines · Takashi Iwai

At Sun, 8 Mar 2009 23:21:13 +0000 (UTC),

Quoted 13 lines · Daniel Gimpelevich
Quoted 9 lines · Takashi Iwai <tiwai <at> suse.de> writes:

Daniel, how "incorrect" do you mean exactly?

As you cited, the above patch was added for the request for the specific model, so the patch itself is correct per definition. What wrong could be the choice of the model option by the original poster, which I cannot judge.

Of course I have no objection to fix the model entry at all, but I need a more proper justification.

Quoted 7 lines
Quoted 4 lines
Quoted 1 line

The master volume control appeared to be affecting the wrong control line,

Is it so with the latest 2.6.29 kernel?
(Also you aren't accessing pulse plugin, right?)

Was using alsamixer to test, without pulseaudio running. The underlying issue is unchanged in three years of commits.

No, the master volume behavior did change recently.

Doesn't it really work with model=basic on 2.6.29?
Its master should change both the widget 0x08 and 0x09, so it should influence on the volume.

Quoted 9 lines
Quoted 6 lines
Quoted 2 lines

and
there was no way to turn off IEC958, which appeared to be on by default.

This should work.

% amixer -Dhw:0 set IEC958 mute

It does work, but only after the patch I submitted (or by using the equivalent module argument).

Ah, you mean there is no IEC958 mixer as is, right? Then yes, there is no control with model=basic.

But, I basically wonder whether model=auto works or not. Choosing an existing model for a device of another vendor is often wrong in small corner cases.

Anyway, it'd be helpful if you attach the output of alsa-info.sh (with --no-upload option) on your device. The script is found at
http://www.alsa-project.org/alsa-info.sh

thanks,

Takashi

#20 lore raw

BTW, Rafael: The reason I originally sent this to the main LKML and not to Takashi through other channels was that I was replying directly to a thread already on only this list. I do acknowledge that this list was not the proper venue for the thread when it was begun, three years ago.

Quoted 26 lines · Takashi Iwai

At Wed, 11 Mar 2009 06:07:20 -0700,

Quoted 24 lines · Daniel Gimpelevich

(Re-adding mistakenly snipped CC's…)

Quoted 19 lines · Takashi Iwai

At Sun, 8 Mar 2009 23:21:13 +0000 (UTC),

Quoted 10 lines · Daniel Gimpelevich
Quoted 7 lines · Takashi Iwai <tiwai <at> suse.de> writes:

Daniel, how "incorrect" do you mean exactly?

As you cited, the above patch was added for the request for the specific model, so the patch itself is correct per definition. What wrong could be the choice of the model option by the original poster, which I cannot judge.

Quoted 4 lines
Quoted 2 lines

Of course I have no objection to fix the model entry at all, but I need a more proper justification.

The master volume control appeared to be affecting the wrong control line,

Is it so with the latest 2.6.29 kernel?
(Also you aren't accessing pulse plugin, right?)

Quoted 8 lines
Quoted 2 lines

Was using alsamixer to test, without pulseaudio running. The underlying issue is unchanged in three years of commits.

No, the master volume behavior did change recently.

Doesn't it really work with model=basic on 2.6.29?
Its master should change both the widget 0x08 and 0x09, so it should influence on the volume.

Perhaps; I was referring only to the issue of model=basic being chosen as a lowest common denominator amidst lack of other info. The newest kernel I have actually tested on that hardware so far is the one on the Fedora 10 LiveCD.

Quoted 10 lines
Quoted 9 lines
Quoted 6 lines
Quoted 2 lines

and
there was no way to turn off IEC958, which appeared to be on by default.

This should work.

% amixer -Dhw:0 set IEC958 mute

It does work, but only after the patch I submitted (or by using the equivalent module argument).

Quoted 6 lines

Ah, you mean there is no IEC958 mixer as is, right? Then yes, there is no control with model=basic.

But, I basically wonder whether model=auto works or not. Choosing an existing model for a device of another vendor is often wrong in small corner cases.

As the OP stated, there is no sound output whatsoever with model=auto. The controls in alsamixer in that case do not exactly match any of the existing models, and I currently intend to attach a three-way comparison of them among model=basic, model=will, and model=auto.

Quoted 3 lines

Anyway, it'd be helpful if you attach the output of alsa-info.sh (with --no-upload option) on your device. The script is found at
http://www.alsa-project.org/alsa-info.sh

Unfortunately, the machine has since suffered a hardware failure, which I will attempt to correct this week. Further testing must wait until then.