[alsa-devel] HDA Intel IDT 92HD71B7X - HP Pavilion DV7-1299EF - Only the left speaker is working
On Wed, Jul 29, 2009 at 8:55 AM, Takashi Iwai<tiwai at suse.de> wrote:
At Tue, 28 Jul 2009 20:07:29 +0200, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Mon, Jul 27, 2009 at 3:15 PM, Takashi Iwai <tiwai at suse.de> wrote:
At Sat, 25 Jul 2009 21:44:46 +0200, Wael Nasreddine (a.k.a eMxyzptlk) wrote: > > I still got no solution for this problem,
Which problem? It'd be helpful if you give a problem summary and what you've done until now (and don't do top-posting)...
thanks,
Takashi
Hi Takashi,
I'm sorry I didn't notice that the problem wasn't quoted in my last message, anyway the whole topic is included in the forwarded message below, I tried using hda-verb and hda-analyzer, like you suggested in one of your emails, but since I don't even know what I'm looking for nor what to try, I did not got too far!
What else do you suggest? Are you aware of anyone having a similar issue I can query to help me figure it out ?
First off, try the very latest alsa-driver snapshot. ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
The problem is that BIOS sets only one stereo speaker in the pin configuration, so the driver cannot know what to do with another speaker. In short, it's a BIOS bug.
To overcome that, you need to figure out which pin corresponds to the speaker. The rest available (analog) output pins are 0x0f and 0x14. Set these as output pins, and connect to DAC. For example,
# hda-verb /dev/snd/hwC0D0 0x0f SET_PIN_WID 0x40 # hda-verb /dev/snd/hwC0D0 0x0f SET_CONN 0
which enables the output of the pin 0x0f, then connects to the first DAC (= 0x10). Similarly,
# hda-verb /dev/snd/hwC0D0 0x14 SET_PIN_WID 0x40 # hda-verb /dev/snd/hwC0D0 0x15 SET_CONN 0
which enables the output of the pin 0x14, then changes the connection of its mux (0x15) to the first DAC (0x10).
If these don't help, it's possible that some GPIO bits play any role. Play with GPIO bits, which can be also changed via hda-verb.
Takashi
Hey Takashi,
I tried what you have suggested above, and I also tried to upgrade the BIOS (it's F.2C now) but I still have the same problem with my sound, here's an updated alsa-info output
http://www.alsa-project.org/db/?f=2cdfc5aa67bc0baf98d38c13806739afb6f5163f
I also tried to play a bit with GPIO bits but I don't know much about that topic either, I tried
hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x0f hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x0f
and
hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x0f hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x0f
But that did not affect anything, the output is only from one speaker (left one), what do you suggest?
Thanks
-- Wael Nasreddine
Weem Chief-Development Officer - http://www.weem.com
Blog : http://wael.nasreddine.com E-mail : wael.nasreddine@weem.com gTalk : wael.nasreddine@gmail.com Tel : +33.6.32.94.70.13 Skype : eMxyzptlk Twitter : @eMxyzptlk
PGP: 1024D/C8DD18A2 06F6 1622 4BC8 4CEB D724 DE12 5565 3945 C8DD 18A2
.: An infinite number of monkeys typing into GNU emacs, would never make a good program. (L. Torvalds 1995) :.
On Wed, Nov 11, 2009 at 16:22, Wael Nasreddine (a.k.a eMxyzptlk) mla@nasreddine.com wrote:
On Wed, Jul 29, 2009 at 8:55 AM, Takashi Iwai<tiwai at suse.de> wrote:
At Tue, 28 Jul 2009 20:07:29 +0200, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Mon, Jul 27, 2009 at 3:15 PM, Takashi Iwai <tiwai at suse.de> wrote:
At Sat, 25 Jul 2009 21:44:46 +0200, Wael Nasreddine (a.k.a eMxyzptlk) wrote: > > I still got no solution for this problem,
Which problem? It'd be helpful if you give a problem summary and what you've done until now (and don't do top-posting)...
thanks,
Takashi
Hi Takashi,
I'm sorry I didn't notice that the problem wasn't quoted in my last message, anyway the whole topic is included in the forwarded message below, I tried using hda-verb and hda-analyzer, like you suggested in one of your emails, but since I don't even know what I'm looking for nor what to try, I did not got too far!
What else do you suggest? Are you aware of anyone having a similar issue I can query to help me figure it out ?
First off, try the very latest alsa-driver snapshot. ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
The problem is that BIOS sets only one stereo speaker in the pin configuration, so the driver cannot know what to do with another speaker. In short, it's a BIOS bug.
To overcome that, you need to figure out which pin corresponds to the speaker. The rest available (analog) output pins are 0x0f and 0x14. Set these as output pins, and connect to DAC. For example,
# hda-verb /dev/snd/hwC0D0 0x0f SET_PIN_WID 0x40 # hda-verb /dev/snd/hwC0D0 0x0f SET_CONN 0
which enables the output of the pin 0x0f, then connects to the first DAC (= 0x10). Similarly,
# hda-verb /dev/snd/hwC0D0 0x14 SET_PIN_WID 0x40 # hda-verb /dev/snd/hwC0D0 0x15 SET_CONN 0
which enables the output of the pin 0x14, then changes the connection of its mux (0x15) to the first DAC (0x10).
If these don't help, it's possible that some GPIO bits play any role. Play with GPIO bits, which can be also changed via hda-verb.
Takashi
Hey Takashi,
I tried what you have suggested above, and I also tried to upgrade the BIOS (it's F.2C now) but I still have the same problem with my sound, here's an updated alsa-info output
http://www.alsa-project.org/db/?f=2cdfc5aa67bc0baf98d38c13806739afb6f5163f
I also tried to play a bit with GPIO bits but I don't know much about that topic either, I tried
hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x0f hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x0f
and
hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x0f hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x0f
But that did not affect anything, the output is only from one speaker (left one), what do you suggest?
Thanks
-- Wael Nasreddine
Weem Chief-Development Officer - http://www.weem.com
Blog : http://wael.nasreddine.com E-mail : wael.nasreddine@weem.com gTalk : wael.nasreddine@gmail.com Tel : +33.6.32.94.70.13 Skype : eMxyzptlk Twitter : @eMxyzptlk
PGP: 1024D/C8DD18A2 06F6 1622 4BC8 4CEB D724 DE12 5565 3945 C8DD 18A2
.: An infinite number of monkeys typing into GNU emacs, would never make a good program. (L. Torvalds 1995) :.
Someone else has the same PC as mine (HP DV7-1299EF) and it happens that we are running the exact OS and the exact kernel version, I asked him to send me the alsa-info (attached in this mail), The difference I noticed:
Mine: 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xdf000000 irq 33
His: 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xdf000000 irq 34
In the codec section: Mine: Node 0x0a [Pin Complex] wcaps 0x400181: Stereo Pincap 0x0000001c: OUT HP Detect Pin Default 0x0221401f: [Jack] HP Out at Ext Front Conn = 1/8, Color = Green DefAssociation = 0x1, Sequence = 0xf Pin-ctls: 0xc0: OUT HP Unsolicited: tag=01, enabled=1 Connection: 3 0x10 0x11* 0x17 Node 0x10 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out R/L Amp-Out caps: N/A Amp-Out vals: [0x63 0x63] Converter: stream=5, channel=0 Power: setting=D0, actual=D0 Delay: 13 samples Node 0x11 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out R/L Amp-Out caps: N/A Amp-Out vals: [0x63 0x63] Converter: stream=5, channel=0 Power: setting=D0, actual=D0 Delay: 13 samples Node 0x1c [Audio Selector] wcaps 0x30090d: Stereo Amp-Out R/L Amp-Out caps: ofs=0x00, nsteps=0x0f, stepsize=0x05, mute=1 Amp-Out vals: [0x09 0x09] Connection: 4 0x1a* 0x17 0x18 0x19 Node 0x1d [Audio Selector] wcaps 0x30090d: Stereo Amp-Out R/L Amp-Out caps: ofs=0x00, nsteps=0x0f, stepsize=0x05, mute=1 Amp-Out vals: [0x89 0x89] Connection: 4 0x1b* 0x17 0x18 0x19 Node 0x21 [Audio Output] wcaps 0x40211: Stereo Digital Converter: stream=5, channel=0 Digital: Enabled Digital category: 0x0 PCM: rates [0x7e0]: 44100 48000 88200 96000 176400 192000 bits [0xe]: 16 20 24 formats [0x5]: PCM AC3 Delay: 4 samples Node 0x22 [Audio Output] wcaps 0x40211: Stereo Digital Converter: stream=5, channel=0 Digital: Enabled Digital category: 0x0 PCM: rates [0x7e0]: 44100 48000 88200 96000 176400 192000 bits [0xe]: 16 20 24 formats [0x5]: PCM AC3 Delay: 4 samples Node 0x04 [Audio Output] wcaps 0x211: Stereo Digital Converter: stream=0, channel=0 Digital: Enabled Digital category: 0x0 PCM: rates [0xc0]: 48000 88200 bits [0xf]: 8 16 20 24 formats [0x1]: PCM
His: Node 0x0a [Pin Complex] wcaps 0x400181: Stereo Pincap 0x0000001c: OUT HP Detect Pin Default 0x0221401f: [Jack] HP Out at Ext Front Conn = 1/8, Color = Green DefAssociation = 0x1, Sequence = 0xf Pin-ctls: 0x00: Unsolicited: tag=01, enabled=1 Connection: 3 0x10 0x11* 0x17 Node 0x10 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out R/L Amp-Out caps: N/A Amp-Out vals: [0x5f 0x5f] Converter: stream=0, channel=0 Power: setting=D0, actual=D0 Delay: 13 samples Node 0x11 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out R/L Amp-Out caps: N/A Amp-Out vals: [0x5f 0x5f] Converter: stream=0, channel=0 Power: setting=D0, actual=D0 Delay: 13 samples Node 0x1c [Audio Selector] wcaps 0x30090d: Stereo Amp-Out R/L Amp-Out caps: ofs=0x00, nsteps=0x0f, stepsize=0x05, mute=1 Amp-Out vals: [0x8a 0x8a] Connection: 4 0x1a 0x17 0x18* 0x19 Node 0x1d [Audio Selector] wcaps 0x30090d: Stereo Amp-Out R/L Amp-Out caps: ofs=0x00, nsteps=0x0f, stepsize=0x05, mute=1 Amp-Out vals: [0x80 0x80] Connection: 4 0x1b 0x17 0x18* 0x19 Node 0x21 [Audio Output] wcaps 0x40211: Stereo Digital Converter: stream=0, channel=0 Digital: Digital category: 0x0 PCM: rates [0x7e0]: 44100 48000 88200 96000 176400 192000 bits [0xe]: 16 20 24 formats [0x5]: PCM AC3 Delay: 4 samples Node 0x22 [Audio Output] wcaps 0x40211: Stereo Digital Converter: stream=0, channel=0 Digital: Digital category: 0x0 PCM: rates [0x7e0]: 44100 48000 88200 96000 176400 192000 bits [0xe]: 16 20 24 formats [0x5]: PCM AC3 Delay: 4 samples Node 0x04 [Audio Output] wcaps 0x211: Stereo Digital Converter: stream=0, channel=0 Digital: Digital category: 0x0 PCM: rates [0xc0]: 48000 88200 bits [0xf]: 8 16 20 24 formats [0x1]: PCM
The full diff between both info files can be viewed here http://pastebin.com/f314869e
Hopefully someone have an insight on what's going on...
At Wed, 11 Nov 2009 16:22:47 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Wed, Jul 29, 2009 at 8:55 AM, Takashi Iwai<tiwai at suse.de> wrote:
At Tue, 28 Jul 2009 20:07:29 +0200, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Mon, Jul 27, 2009 at 3:15 PM, Takashi Iwai <tiwai at suse.de> wrote:
At Sat, 25 Jul 2009 21:44:46 +0200, Wael Nasreddine (a.k.a eMxyzptlk) wrote: > > I still got no solution for this problem,
Which problem? It'd be helpful if you give a problem summary and what you've done until now (and don't do top-posting)...
thanks,
Takashi
Hi Takashi,
I'm sorry I didn't notice that the problem wasn't quoted in my last message, anyway the whole topic is included in the forwarded message below, I tried using hda-verb and hda-analyzer, like you suggested in one of your emails, but since I don't even know what I'm looking for nor what to try, I did not got too far!
What else do you suggest? Are you aware of anyone having a similar issue I can query to help me figure it out ?
First off, try the very latest alsa-driver snapshot. ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
The problem is that BIOS sets only one stereo speaker in the pin configuration, so the driver cannot know what to do with another speaker. In short, it's a BIOS bug.
To overcome that, you need to figure out which pin corresponds to the speaker. The rest available (analog) output pins are 0x0f and 0x14. Set these as output pins, and connect to DAC. For example,
# hda-verb /dev/snd/hwC0D0 0x0f SET_PIN_WID 0x40 # hda-verb /dev/snd/hwC0D0 0x0f SET_CONN 0
which enables the output of the pin 0x0f, then connects to the first DAC (= 0x10). Similarly,
# hda-verb /dev/snd/hwC0D0 0x14 SET_PIN_WID 0x40 # hda-verb /dev/snd/hwC0D0 0x15 SET_CONN 0
which enables the output of the pin 0x14, then changes the connection of its mux (0x15) to the first DAC (0x10).
If these don't help, it's possible that some GPIO bits play any role. Play with GPIO bits, which can be also changed via hda-verb.
Takashi
Hey Takashi,
I tried what you have suggested above, and I also tried to upgrade the BIOS (it's F.2C now) but I still have the same problem with my sound, here's an updated alsa-info output
http://www.alsa-project.org/db/?f=2cdfc5aa67bc0baf98d38c13806739afb6f5163f
This is obviously from the very old alsa-driver version. Double-check whether the installation was correct.
Also, please attach alsa-info.sh output (run with --no-upload option) instead of uploading to a server.
Anyway, try the very latest snapshot (as of today). A few new fixes for HD laptops are there. And remove all module options for snd-hda-intel once.
HTH,
Takashi
On Wed, Nov 11, 2009 at 18:35, Takashi Iwai tiwai@suse.de wrote:
At Wed, 11 Nov 2009 16:22:47 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Wed, Jul 29, 2009 at 8:55 AM, Takashi Iwai<tiwai at suse.de> wrote:
At Tue, 28 Jul 2009 20:07:29 +0200, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Mon, Jul 27, 2009 at 3:15 PM, Takashi Iwai <tiwai at suse.de> wrote:
At Sat, 25 Jul 2009 21:44:46 +0200, Wael Nasreddine (a.k.a eMxyzptlk) wrote: > > I still got no solution for this problem,
Which problem? It'd be helpful if you give a problem summary and what you've done until now (and don't do top-posting)...
thanks,
Takashi
Hi Takashi,
I'm sorry I didn't notice that the problem wasn't quoted in my last message, anyway the whole topic is included in the forwarded message below, I tried using hda-verb and hda-analyzer, like you suggested in one of your emails, but since I don't even know what I'm looking for nor what to try, I did not got too far!
What else do you suggest? Are you aware of anyone having a similar issue I can query to help me figure it out ?
First off, try the very latest alsa-driver snapshot. ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
The problem is that BIOS sets only one stereo speaker in the pin configuration, so the driver cannot know what to do with another speaker. In short, it's a BIOS bug.
To overcome that, you need to figure out which pin corresponds to the speaker. The rest available (analog) output pins are 0x0f and 0x14. Set these as output pins, and connect to DAC. For example,
# hda-verb /dev/snd/hwC0D0 0x0f SET_PIN_WID 0x40 # hda-verb /dev/snd/hwC0D0 0x0f SET_CONN 0
which enables the output of the pin 0x0f, then connects to the first DAC (= 0x10). Similarly,
# hda-verb /dev/snd/hwC0D0 0x14 SET_PIN_WID 0x40 # hda-verb /dev/snd/hwC0D0 0x15 SET_CONN 0
which enables the output of the pin 0x14, then changes the connection of its mux (0x15) to the first DAC (0x10).
If these don't help, it's possible that some GPIO bits play any role. Play with GPIO bits, which can be also changed via hda-verb.
Takashi
Hey Takashi,
I tried what you have suggested above, and I also tried to upgrade the BIOS (it's F.2C now) but I still have the same problem with my sound, here's an updated alsa-info output
http://www.alsa-project.org/db/?f=2cdfc5aa67bc0baf98d38c13806739afb6f5163f
This is obviously from the very old alsa-driver version. Double-check whether the installation was correct.
Also, please attach alsa-info.sh output (run with --no-upload option) instead of uploading to a server.
Anyway, try the very latest snapshot (as of today). A few new fixes for HD laptops are there. And remove all module options for snd-hda-intel once.
HTH,
Takashi
Hey Takashi,
Here's one from the code in kernel 2.6.31.6 and only with enable_msi=1
I will get a snapshot of the alsa driver and compile install it and I will reply to this topic with the one taken from the snapshot..
Thanks
At Wed, 11 Nov 2009 18:40:48 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Wed, Nov 11, 2009 at 18:35, Takashi Iwai tiwai@suse.de wrote:
At Wed, 11 Nov 2009 16:22:47 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Wed, Jul 29, 2009 at 8:55 AM, Takashi Iwai<tiwai at suse.de> wrote:
At Tue, 28 Jul 2009 20:07:29 +0200, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Mon, Jul 27, 2009 at 3:15 PM, Takashi Iwai <tiwai at suse.de> wrote:
At Sat, 25 Jul 2009 21:44:46 +0200, Wael Nasreddine (a.k.a eMxyzptlk) wrote: > > I still got no solution for this problem,
Which problem? It'd be helpful if you give a problem summary and what you've done until now (and don't do top-posting)...
thanks,
Takashi
Hi Takashi,
I'm sorry I didn't notice that the problem wasn't quoted in my last message, anyway the whole topic is included in the forwarded message below, I tried using hda-verb and hda-analyzer, like you suggested in one of your emails, but since I don't even know what I'm looking for nor what to try, I did not got too far!
What else do you suggest? Are you aware of anyone having a similar issue I can query to help me figure it out ?
First off, try the very latest alsa-driver snapshot. ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
The problem is that BIOS sets only one stereo speaker in the pin configuration, so the driver cannot know what to do with another speaker. In short, it's a BIOS bug.
To overcome that, you need to figure out which pin corresponds to the speaker. The rest available (analog) output pins are 0x0f and 0x14. Set these as output pins, and connect to DAC. For example,
# hda-verb /dev/snd/hwC0D0 0x0f SET_PIN_WID 0x40 # hda-verb /dev/snd/hwC0D0 0x0f SET_CONN 0
which enables the output of the pin 0x0f, then connects to the first DAC (= 0x10). Similarly,
# hda-verb /dev/snd/hwC0D0 0x14 SET_PIN_WID 0x40 # hda-verb /dev/snd/hwC0D0 0x15 SET_CONN 0
which enables the output of the pin 0x14, then changes the connection of its mux (0x15) to the first DAC (0x10).
If these don't help, it's possible that some GPIO bits play any role. Play with GPIO bits, which can be also changed via hda-verb.
Takashi
Hey Takashi,
I tried what you have suggested above, and I also tried to upgrade the BIOS (it's F.2C now) but I still have the same problem with my sound, here's an updated alsa-info output
http://www.alsa-project.org/db/?f=2cdfc5aa67bc0baf98d38c13806739afb6f5163f
This is obviously from the very old alsa-driver version. Double-check whether the installation was correct.
Also, please attach alsa-info.sh output (run with --no-upload option) instead of uploading to a server.
Anyway, try the very latest snapshot (as of today). A few new fixes for HD laptops are there. And remove all module options for snd-hda-intel once.
HTH,
Takashi
Hey Takashi,
Here's one from the code in kernel 2.6.31.6 and only with enable_msi=1
2.6.31.x is also too old to debug :)
I will get a snapshot of the alsa driver and compile install it and I will reply to this topic with the one taken from the snapshot..
Yes, please. That'll be helpful.
With the latest version, you don't need any option (hopefully). Try without options at first.
Takashi
On Wed, Nov 11, 2009 at 18:45, Takashi Iwai tiwai@suse.de wrote:
At Wed, 11 Nov 2009 18:40:48 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Wed, Nov 11, 2009 at 18:35, Takashi Iwai tiwai@suse.de wrote:
At Wed, 11 Nov 2009 16:22:47 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Wed, Jul 29, 2009 at 8:55 AM, Takashi Iwai<tiwai at suse.de> wrote:
At Tue, 28 Jul 2009 20:07:29 +0200, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Mon, Jul 27, 2009 at 3:15 PM, Takashi Iwai <tiwai at suse.de> wrote:
At Sat, 25 Jul 2009 21:44:46 +0200, Wael Nasreddine (a.k.a eMxyzptlk) wrote: > > I still got no solution for this problem,
Which problem? It'd be helpful if you give a problem summary and what you've done until now (and don't do top-posting)...
thanks,
Takashi
Hi Takashi,
I'm sorry I didn't notice that the problem wasn't quoted in my last message, anyway the whole topic is included in the forwarded message below, I tried using hda-verb and hda-analyzer, like you suggested in one of your emails, but since I don't even know what I'm looking for nor what to try, I did not got too far!
What else do you suggest? Are you aware of anyone having a similar issue I can query to help me figure it out ?
First off, try the very latest alsa-driver snapshot. ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
The problem is that BIOS sets only one stereo speaker in the pin configuration, so the driver cannot know what to do with another speaker. In short, it's a BIOS bug.
To overcome that, you need to figure out which pin corresponds to the speaker. The rest available (analog) output pins are 0x0f and 0x14. Set these as output pins, and connect to DAC. For example,
# hda-verb /dev/snd/hwC0D0 0x0f SET_PIN_WID 0x40 # hda-verb /dev/snd/hwC0D0 0x0f SET_CONN 0
which enables the output of the pin 0x0f, then connects to the first DAC (= 0x10). Similarly,
# hda-verb /dev/snd/hwC0D0 0x14 SET_PIN_WID 0x40 # hda-verb /dev/snd/hwC0D0 0x15 SET_CONN 0
which enables the output of the pin 0x14, then changes the connection of its mux (0x15) to the first DAC (0x10).
If these don't help, it's possible that some GPIO bits play any role. Play with GPIO bits, which can be also changed via hda-verb.
Takashi
Hey Takashi,
I tried what you have suggested above, and I also tried to upgrade the BIOS (it's F.2C now) but I still have the same problem with my sound, here's an updated alsa-info output
http://www.alsa-project.org/db/?f=2cdfc5aa67bc0baf98d38c13806739afb6f5163f
This is obviously from the very old alsa-driver version. Double-check whether the installation was correct.
Also, please attach alsa-info.sh output (run with --no-upload option) instead of uploading to a server.
Anyway, try the very latest snapshot (as of today). A few new fixes for HD laptops are there. And remove all module options for snd-hda-intel once.
HTH,
Takashi
Hey Takashi,
Here's one from the code in kernel 2.6.31.6 and only with enable_msi=1
2.6.31.x is also too old to debug :)
I will get a snapshot of the alsa driver and compile install it and I will reply to this topic with the one taken from the snapshot..
Yes, please. That'll be helpful.
With the latest version, you don't need any option (hopefully). Try without options at first.
Takashi
Sadly I get the same result, only the left speaker is working, last month you suggested that I try
# hda-verb /dev/snd/hwC0D0 0x0f SET_PIN_WID 0x40 # hda-verb /dev/snd/hwC0D0 0x0f SET_CONN 0
Or
# hda-verb /dev/snd/hwC0D0 0x14 SET_PIN_WID 0x40 # hda-verb /dev/snd/hwC0D0 0x15 SET_CONN 0
and some GPIO bits, could you specify more GPIO bits that I can try?
Thanks.
At Wed, 11 Nov 2009 18:58:29 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Wed, Nov 11, 2009 at 18:45, Takashi Iwai tiwai@suse.de wrote:
At Wed, 11 Nov 2009 18:40:48 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Wed, Nov 11, 2009 at 18:35, Takashi Iwai tiwai@suse.de wrote:
At Wed, 11 Nov 2009 16:22:47 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Wed, Jul 29, 2009 at 8:55 AM, Takashi Iwai<tiwai at suse.de> wrote:
At Tue, 28 Jul 2009 20:07:29 +0200, Wael Nasreddine (a.k.a eMxyzptlk) wrote: > > On Mon, Jul 27, 2009 at 3:15 PM, Takashi Iwai <tiwai at suse.de> wrote: > > At Sat, 25 Jul 2009 21:44:46 +0200, > Wael Nasreddine (a.k.a eMxyzptlk) wrote: > > > > I still got no solution for this problem, > > Which problem? > It'd be helpful if you give a problem summary and what you've done > until now (and don't do top-posting)... > > thanks, > > Takashi > > Hi Takashi, > > I'm sorry I didn't notice that the problem wasn't quoted in my last message, > anyway the whole topic is included in the forwarded message below, I tried > using hda-verb and hda-analyzer, like you suggested in one of your emails, but > since I don't even know what I'm looking for nor what to try, I did not got > too far! > > What else do you suggest? Are you aware of anyone having a similar issue I can > query to help me figure it out ?
First off, try the very latest alsa-driver snapshot. ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
The problem is that BIOS sets only one stereo speaker in the pin configuration, so the driver cannot know what to do with another speaker. In short, it's a BIOS bug.
To overcome that, you need to figure out which pin corresponds to the speaker. The rest available (analog) output pins are 0x0f and 0x14. Set these as output pins, and connect to DAC. For example,
# hda-verb /dev/snd/hwC0D0 0x0f SET_PIN_WID 0x40 # hda-verb /dev/snd/hwC0D0 0x0f SET_CONN 0
which enables the output of the pin 0x0f, then connects to the first DAC (= 0x10). Similarly,
# hda-verb /dev/snd/hwC0D0 0x14 SET_PIN_WID 0x40 # hda-verb /dev/snd/hwC0D0 0x15 SET_CONN 0
which enables the output of the pin 0x14, then changes the connection of its mux (0x15) to the first DAC (0x10).
If these don't help, it's possible that some GPIO bits play any role. Play with GPIO bits, which can be also changed via hda-verb.
Takashi
Hey Takashi,
I tried what you have suggested above, and I also tried to upgrade the BIOS (it's F.2C now) but I still have the same problem with my sound, here's an updated alsa-info output
http://www.alsa-project.org/db/?f=2cdfc5aa67bc0baf98d38c13806739afb6f5163f
This is obviously from the very old alsa-driver version. Double-check whether the installation was correct.
Also, please attach alsa-info.sh output (run with --no-upload option) instead of uploading to a server.
Anyway, try the very latest snapshot (as of today). A few new fixes for HD laptops are there. And remove all module options for snd-hda-intel once.
HTH,
Takashi
Hey Takashi,
Here's one from the code in kernel 2.6.31.6 and only with enable_msi=1
2.6.31.x is also too old to debug :)
I will get a snapshot of the alsa driver and compile install it and I will reply to this topic with the one taken from the snapshot..
Yes, please. That'll be helpful.
With the latest version, you don't need any option (hopefully). Try without options at first.
Takashi
Sadly I get the same result, only the left speaker is working,
To be sure, did you try the driver from below? ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi
On Wed, Nov 11, 2009 at 20:09, Takashi Iwai tiwai@suse.de wrote:
At Wed, 11 Nov 2009 18:58:29 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Wed, Nov 11, 2009 at 18:45, Takashi Iwai tiwai@suse.de wrote:
At Wed, 11 Nov 2009 18:40:48 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Wed, Nov 11, 2009 at 18:35, Takashi Iwai tiwai@suse.de wrote:
At Wed, 11 Nov 2009 16:22:47 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Wed, Jul 29, 2009 at 8:55 AM, Takashi Iwai<tiwai at suse.de> wrote: > At Tue, 28 Jul 2009 20:07:29 +0200, > Wael Nasreddine (a.k.a eMxyzptlk) wrote: >> >> On Mon, Jul 27, 2009 at 3:15 PM, Takashi Iwai <tiwai at suse.de> wrote: >> >> At Sat, 25 Jul 2009 21:44:46 +0200, >> Wael Nasreddine (a.k.a eMxyzptlk) wrote: >> > >> > I still got no solution for this problem, >> >> Which problem? >> It'd be helpful if you give a problem summary and what you've done >> until now (and don't do top-posting)... >> >> thanks, >> >> Takashi >> >> Hi Takashi, >> >> I'm sorry I didn't notice that the problem wasn't quoted in my last message, >> anyway the whole topic is included in the forwarded message below, I tried >> using hda-verb and hda-analyzer, like you suggested in one of your emails, but >> since I don't even know what I'm looking for nor what to try, I did not got >> too far! >> >> What else do you suggest? Are you aware of anyone having a similar issue I can >> query to help me figure it out ? > > First off, try the very latest alsa-driver snapshot. > ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz > > The problem is that BIOS sets only one stereo speaker in the pin > configuration, so the driver cannot know what to do with another > speaker. In short, it's a BIOS bug. > > To overcome that, you need to figure out which pin corresponds to the > speaker. The rest available (analog) output pins are 0x0f and 0x14. > Set these as output pins, and connect to DAC. For example, > > # hda-verb /dev/snd/hwC0D0 0x0f SET_PIN_WID 0x40 > # hda-verb /dev/snd/hwC0D0 0x0f SET_CONN 0 > > which enables the output of the pin 0x0f, then connects to the first > DAC (= 0x10). Similarly, > > # hda-verb /dev/snd/hwC0D0 0x14 SET_PIN_WID 0x40 > # hda-verb /dev/snd/hwC0D0 0x15 SET_CONN 0 > > which enables the output of the pin 0x14, then changes the connection > of its mux (0x15) to the first DAC (0x10). > > If these don't help, it's possible that some GPIO bits play any role. > Play with GPIO bits, which can be also changed via hda-verb. > > > Takashi >
Hey Takashi,
I tried what you have suggested above, and I also tried to upgrade the BIOS (it's F.2C now) but I still have the same problem with my sound, here's an updated alsa-info output
http://www.alsa-project.org/db/?f=2cdfc5aa67bc0baf98d38c13806739afb6f5163f
This is obviously from the very old alsa-driver version. Double-check whether the installation was correct.
Also, please attach alsa-info.sh output (run with --no-upload option) instead of uploading to a server.
Anyway, try the very latest snapshot (as of today). A few new fixes for HD laptops are there. And remove all module options for snd-hda-intel once.
HTH,
Takashi
Hey Takashi,
Here's one from the code in kernel 2.6.31.6 and only with enable_msi=1
2.6.31.x is also too old to debug :)
I will get a snapshot of the alsa driver and compile install it and I will reply to this topic with the one taken from the snapshot..
Yes, please. That'll be helpful.
With the latest version, you don't need any option (hopefully). Try without options at first.
Takashi
Sadly I get the same result, only the left speaker is working,
To be sure, did you try the driver from below? ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi
Nope I tried this one
http://www.alsa-project.org/snapshot/?package=alsa-driver
I will try this one right now
On Wed, Nov 11, 2009 at 20:15, Wael Nasreddine (a.k.a eMxyzptlk) mla@nasreddine.com wrote:
On Wed, Nov 11, 2009 at 20:09, Takashi Iwai tiwai@suse.de wrote:
At Wed, 11 Nov 2009 18:58:29 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Wed, Nov 11, 2009 at 18:45, Takashi Iwai tiwai@suse.de wrote:
At Wed, 11 Nov 2009 18:40:48 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Wed, Nov 11, 2009 at 18:35, Takashi Iwai tiwai@suse.de wrote:
At Wed, 11 Nov 2009 16:22:47 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote: > > On Wed, Jul 29, 2009 at 8:55 AM, Takashi Iwai<tiwai at suse.de> wrote: > > At Tue, 28 Jul 2009 20:07:29 +0200, > > Wael Nasreddine (a.k.a eMxyzptlk) wrote: > >> > >> On Mon, Jul 27, 2009 at 3:15 PM, Takashi Iwai <tiwai at suse.de> wrote: > >> > >> At Sat, 25 Jul 2009 21:44:46 +0200, > >> Wael Nasreddine (a.k.a eMxyzptlk) wrote: > >> > > >> > I still got no solution for this problem, > >> > >> Which problem? > >> It'd be helpful if you give a problem summary and what you've done > >> until now (and don't do top-posting)... > >> > >> thanks, > >> > >> Takashi > >> > >> Hi Takashi, > >> > >> I'm sorry I didn't notice that the problem wasn't quoted in my last message, > >> anyway the whole topic is included in the forwarded message below, I tried > >> using hda-verb and hda-analyzer, like you suggested in one of your emails, but > >> since I don't even know what I'm looking for nor what to try, I did not got > >> too far! > >> > >> What else do you suggest? Are you aware of anyone having a similar issue I can > >> query to help me figure it out ? > > > > First off, try the very latest alsa-driver snapshot. > > ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz > > > > The problem is that BIOS sets only one stereo speaker in the pin > > configuration, so the driver cannot know what to do with another > > speaker. In short, it's a BIOS bug. > > > > To overcome that, you need to figure out which pin corresponds to the > > speaker. The rest available (analog) output pins are 0x0f and 0x14. > > Set these as output pins, and connect to DAC. For example, > > > > # hda-verb /dev/snd/hwC0D0 0x0f SET_PIN_WID 0x40 > > # hda-verb /dev/snd/hwC0D0 0x0f SET_CONN 0 > > > > which enables the output of the pin 0x0f, then connects to the first > > DAC (= 0x10). Similarly, > > > > # hda-verb /dev/snd/hwC0D0 0x14 SET_PIN_WID 0x40 > > # hda-verb /dev/snd/hwC0D0 0x15 SET_CONN 0 > > > > which enables the output of the pin 0x14, then changes the connection > > of its mux (0x15) to the first DAC (0x10). > > > > If these don't help, it's possible that some GPIO bits play any role. > > Play with GPIO bits, which can be also changed via hda-verb. > > > > > > Takashi > > > > Hey Takashi, > > I tried what you have suggested above, and I also tried to upgrade the > BIOS (it's F.2C now) but I still have the same problem with my sound, > here's an updated alsa-info output > > http://www.alsa-project.org/db/?f=2cdfc5aa67bc0baf98d38c13806739afb6f5163f
This is obviously from the very old alsa-driver version. Double-check whether the installation was correct.
Also, please attach alsa-info.sh output (run with --no-upload option) instead of uploading to a server.
Anyway, try the very latest snapshot (as of today). A few new fixes for HD laptops are there. And remove all module options for snd-hda-intel once.
HTH,
Takashi
Hey Takashi,
Here's one from the code in kernel 2.6.31.6 and only with enable_msi=1
2.6.31.x is also too old to debug :)
I will get a snapshot of the alsa driver and compile install it and I will reply to this topic with the one taken from the snapshot..
Yes, please. That'll be helpful.
With the latest version, you don't need any option (hopefully). Try without options at first.
Takashi
Sadly I get the same result, only the left speaker is working,
To be sure, did you try the driver from below? ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi
Nope I tried this one
http://www.alsa-project.org/snapshot/?package=alsa-driver
I will try this one right now
Still no go :'(
On Wed, Nov 11, 2009 at 20:15, Wael Nasreddine (a.k.a eMxyzptlk) mla@nasreddine.com wrote:
On Wed, Nov 11, 2009 at 20:09, Takashi Iwai tiwai@suse.de wrote:
At Wed, 11 Nov 2009 18:58:29 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Wed, Nov 11, 2009 at 18:45, Takashi Iwai tiwai@suse.de wrote:
At Wed, 11 Nov 2009 18:40:48 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Wed, Nov 11, 2009 at 18:35, Takashi Iwai tiwai@suse.de wrote:
At Wed, 11 Nov 2009 16:22:47 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote: > > On Wed, Jul 29, 2009 at 8:55 AM, Takashi Iwai<tiwai at suse.de> wrote: > > At Tue, 28 Jul 2009 20:07:29 +0200, > > Wael Nasreddine (a.k.a eMxyzptlk) wrote: > >> > >> On Mon, Jul 27, 2009 at 3:15 PM, Takashi Iwai <tiwai at suse.de> wrote: > >> > >> At Sat, 25 Jul 2009 21:44:46 +0200, > >> Wael Nasreddine (a.k.a eMxyzptlk) wrote: > >> > > >> > I still got no solution for this problem, > >> > >> Which problem? > >> It'd be helpful if you give a problem summary and what you've done > >> until now (and don't do top-posting)... > >> > >> thanks, > >> > >> Takashi > >> > >> Hi Takashi, > >> > >> I'm sorry I didn't notice that the problem wasn't quoted in my last message, > >> anyway the whole topic is included in the forwarded message below, I tried > >> using hda-verb and hda-analyzer, like you suggested in one of your emails, but > >> since I don't even know what I'm looking for nor what to try, I did not got > >> too far! > >> > >> What else do you suggest? Are you aware of anyone having a similar issue I can > >> query to help me figure it out ? > > > > First off, try the very latest alsa-driver snapshot. > > ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz > > > > The problem is that BIOS sets only one stereo speaker in the pin > > configuration, so the driver cannot know what to do with another > > speaker. In short, it's a BIOS bug. > > > > To overcome that, you need to figure out which pin corresponds to the > > speaker. The rest available (analog) output pins are 0x0f and 0x14. > > Set these as output pins, and connect to DAC. For example, > > > > # hda-verb /dev/snd/hwC0D0 0x0f SET_PIN_WID 0x40 > > # hda-verb /dev/snd/hwC0D0 0x0f SET_CONN 0 > > > > which enables the output of the pin 0x0f, then connects to the first > > DAC (= 0x10). Similarly, > > > > # hda-verb /dev/snd/hwC0D0 0x14 SET_PIN_WID 0x40 > > # hda-verb /dev/snd/hwC0D0 0x15 SET_CONN 0 > > > > which enables the output of the pin 0x14, then changes the connection > > of its mux (0x15) to the first DAC (0x10). > > > > If these don't help, it's possible that some GPIO bits play any role. > > Play with GPIO bits, which can be also changed via hda-verb. > > > > > > Takashi > > > > Hey Takashi, > > I tried what you have suggested above, and I also tried to upgrade the > BIOS (it's F.2C now) but I still have the same problem with my sound, > here's an updated alsa-info output > > http://www.alsa-project.org/db/?f=2cdfc5aa67bc0baf98d38c13806739afb6f5163f
This is obviously from the very old alsa-driver version. Double-check whether the installation was correct.
Also, please attach alsa-info.sh output (run with --no-upload option) instead of uploading to a server.
Anyway, try the very latest snapshot (as of today). A few new fixes for HD laptops are there. And remove all module options for snd-hda-intel once.
HTH,
Takashi
Hey Takashi,
Here's one from the code in kernel 2.6.31.6 and only with enable_msi=1
2.6.31.x is also too old to debug :)
I will get a snapshot of the alsa driver and compile install it and I will reply to this topic with the one taken from the snapshot..
Yes, please. That'll be helpful.
With the latest version, you don't need any option (hopefully). Try without options at first.
Takashi
Sadly I get the same result, only the left speaker is working,
To be sure, did you try the driver from below? ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi
Nope I tried this one
http://www.alsa-project.org/snapshot/?package=alsa-driver
I will try this one right now
Takashi,
I tried the snapshot from ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz last night with and without options still no go, the options I've tried:
- options snd-hda-intel enable_msi= - options snd-hda-intel enable_msi=1 single_cmd=0 power_save_controller=0 power_save=0 model=hp-dv5
What do you suggest I try next?
alsa-info attached.
-- Wael Nasreddine
Weem Chief-Development Officer - http://www.weem.com
Blog : http://wael.nasreddine.com E-mail : wael.nasreddine@weem.com gTalk : wael.nasreddine@gmail.com Tel : +33.6.32.94.70.13 Skype : eMxyzptlk Twitter : @eMxyzptlk
PGP: 1024D/C8DD18A2 06F6 1622 4BC8 4CEB D724 DE12 5565 3945 C8DD 18A2
.: An infinite number of monkeys typing into GNU emacs, would never make a good program. (L. Torvalds 1995) :.
At Thu, 12 Nov 2009 10:46:24 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
Takashi,
I tried the snapshot from ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz last night with and without options still no go, the options I've tried:
- options snd-hda-intel enable_msi=
- options snd-hda-intel enable_msi=1 single_cmd=0
power_save_controller=0 power_save=0 model=hp-dv5
power_save should be irrelevant. And model=hp-dv5 and enable_msi=1 are already turned on as default in the recent version.
The next would be model=auto to avoid hp-dv5 quirk.
Also, it's helpful if you give a summary of your problems again.
Takashi
On Thu, Nov 12, 2009 at 11:16, Takashi Iwai tiwai@suse.de wrote:
At Thu, 12 Nov 2009 10:46:24 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
Takashi,
I tried the snapshot from ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz last night with and without options still no go, the options I've tried:
- options snd-hda-intel enable_msi=
- options snd-hda-intel enable_msi=1 single_cmd=0
power_save_controller=0 power_save=0 model=hp-dv5
power_save should be irrelevant. And model=hp-dv5 and enable_msi=1 are already turned on as default in the recent version.
The next would be model=auto to avoid hp-dv5 quirk.
Also, it's helpful if you give a summary of your problems again.
Takashi
Takashi,
I just tried 'options snd-hda-intel enable_msi=1 model=auto' Didn't have much effect, the same problem (sound only from left speaker), always the same result with 'speaker-test -c6 -twav' I can only hear 'Front Left'
Summary: =======
I have an HP DV7-1299EF, BIOS Version F.2C, Due to a BIOS BUG, the BIOS report only one speaker as an output so the driver does not know how to use pins in order to have a stereo output ( at least that's what you told me last month when you analysed the alsa-info output)... But this can be confirmed, someone else (Cc'ed by this email) has the same Laptop bought in France as well, using the same OS (Arch Linux 64bit), same Kernel (2.6.31.6) but his BIOS is Version F.23, He does not have this problem, he can hear sound coming out of The left, right and LFE, but in my case only the left works..
First I suspected a hardware problem so 2 days ago I restored Windows, tried the sound it works, and I updated my BIOS (it was version F.2A before) but sadly it has the same BUG.
Attached to this mail, my alsa-info.txt (mine-alsa-info.txt) and his alsa-info.txt (his-alsa-info.txt)
Thank you for helping me!!
Regards, Wael
On Thu, Nov 12, 2009 at 11:16, Takashi Iwai tiwai@suse.de wrote:
At Thu, 12 Nov 2009 10:46:24 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
Takashi,
I tried the snapshot from
ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
last night with and without options still no go, the options I've tried:
- options snd-hda-intel enable_msi=
- options snd-hda-intel enable_msi=1 single_cmd=0
power_save_controller=0 power_save=0 model=hp-dv5
power_save should be irrelevant. And model=hp-dv5 and enable_msi=1 are already turned on as default in the recent version.
The next would be model=auto to avoid hp-dv5 quirk.
Also, it's helpful if you give a summary of your problems again.
Takashi
Takashi,
I just tried 'options snd-hda-intel enable_msi=1 model=auto' Didn't have much effect, the same problem (sound only from left speaker), always the same result with 'speaker-test -c6 -twav' I can only hear 'Front Left'
Summary: =======
I have an HP DV7-1299EF, BIOS (Version F.2C, F.2A and F.23) , Due to a BIOS BUG, the BIOS report only one speaker as an output so the driver does not know how to use pins in order to have a stereo output ( at least that's what you told me last month when you analysed the alsa-info output)... And so one speaker, the left speaker is the only speaker currently working under Linux.
First I suspected a hardware problem so 2 days ago I restored Windows, tried the sound it works, and I updated my BIOS (it was version F.2A before) but sadly it has the same BUG, I also tried reverting back to F.2A and further back to F.23 same result...
Attached to this mail, my alsa-info.txt
Thank you for helping me!!
Regards, Wael
At Sat, 14 Nov 2009 13:46:37 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
[1 <multipart/alternative (7bit)>] [1.1 <text/plain; UTF-8 (7bit)>] On Thu, Nov 12, 2009 at 11:16, Takashi Iwai tiwai@suse.de wrote:
At Thu, 12 Nov 2009 10:46:24 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
Takashi,
I tried the snapshot from
ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
last night with and without options still no go, the options I've tried:
- options snd-hda-intel enable_msi=
- options snd-hda-intel enable_msi=1 single_cmd=0
power_save_controller=0 power_save=0 model=hp-dv5
power_save should be irrelevant. And model=hp-dv5 and enable_msi=1 are already turned on as default in the recent version.
The next would be model=auto to avoid hp-dv5 quirk.
Also, it's helpful if you give a summary of your problems again.
Takashi
Takashi,
I just tried 'options snd-hda-intel enable_msi=1 model=auto' Didn't have much effect, the same problem (sound only from left speaker), always the same result with 'speaker-test -c6 -twav' I can only hear 'Front Left'
OK. But the headphone works, right?
Summary:
I have an HP DV7-1299EF, BIOS (Version F.2C, F.2A and F.23) , Due to a BIOS BUG, the BIOS report only one speaker as an output so the driver does not know how to use pins in order to have a stereo output ( at least that's what you told me last month when you analysed the alsa-info output)... And so one speaker, the left speaker is the only speaker currently working under Linux.
First I suspected a hardware problem so 2 days ago I restored Windows, tried the sound it works, and I updated my BIOS (it was version F.2A before) but sadly it has the same BUG, I also tried reverting back to F.2A and further back to F.23 same result...
Attached to this mail, my alsa-info.txt
The codec registers look OK through a quick look.
You can try GPIO pin up/down for each pin. Also each pin has two directions, so you'll have 8 x 2 x 2 trials. For example, to test GPIO 3, pass 0x08 (= 1 << 3), try the commands below and check aplay at each. (the lines '//' are just my comments)
// dir = 0, data = 1 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x00 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x08
// dir = 0, data = 0 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x00 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x00
// dir = 1, data = 0 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x00
// dir = 1, data = 1 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x08
Repeat these for each GPIO pin, from 0 to 7.
One another possibility is to use the output pin NID 0x0f. For testing this, build with the reconfig feature (usually enabled), then change the pin 0x0f default config, such as
echo 0x0f 0x90171111 > /sys/class/sound/hwC0D0/user_pin_configs
then quit all sound apps and reconfigure
echo 1 > /sys/class/sound/hwC0D0/reconfig
Restore the mixer setup once via alsactl
alsactl restore
Then check the mixer volumes again, try aplay. With this setup, try GPIO procedures above, too.
thanks,
Takashi
On Sat, Nov 14, 2009 at 14:03, Takashi Iwai tiwai@suse.de wrote:
At Sat, 14 Nov 2009 13:46:37 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
[1 <multipart/alternative (7bit)>] [1.1 <text/plain; UTF-8 (7bit)>] On Thu, Nov 12, 2009 at 11:16, Takashi Iwai tiwai@suse.de wrote:
At Thu, 12 Nov 2009 10:46:24 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
Takashi,
I tried the snapshot from
ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
last night with and without options still no go, the options I've tried:
- options snd-hda-intel enable_msi=
- options snd-hda-intel enable_msi=1 single_cmd=0
power_save_controller=0 power_save=0 model=hp-dv5
power_save should be irrelevant. And model=hp-dv5 and enable_msi=1 are already turned on as default in the recent version.
The next would be model=auto to avoid hp-dv5 quirk.
Also, it's helpful if you give a summary of your problems again.
Takashi
Takashi,
I just tried 'options snd-hda-intel enable_msi=1 model=auto' Didn't have much effect, the same problem (sound only from left speaker), always the same result with 'speaker-test -c6 -twav' I can only hear 'Front Left'
OK. But the headphone works, right?
Yes Headphones works, even mics works
Summary:
I have an HP DV7-1299EF, BIOS (Version F.2C, F.2A and F.23) , Due to a BIOS BUG, the BIOS report only one speaker as an output so the driver does not know how to use pins in order to have a stereo output ( at least that's what you told me last month when you analysed the alsa-info output)... And so one speaker, the left speaker is the only speaker currently working under Linux.
First I suspected a hardware problem so 2 days ago I restored Windows, tried the sound it works, and I updated my BIOS (it was version F.2A before) but sadly it has the same BUG, I also tried reverting back to F.2A and further back to F.23 same result...
Attached to this mail, my alsa-info.txt
The codec registers look OK through a quick look.
You can try GPIO pin up/down for each pin. Also each pin has two directions, so you'll have 8 x 2 x 2 trials. For example, to test GPIO 3, pass 0x08 (= 1 << 3), try the commands below and check aplay at each. (the lines '//' are just my comments)
// dir = 0, data = 1 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x00 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x08
// dir = 0, data = 0 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x00 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x00
// dir = 1, data = 0 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x00
// dir = 1, data = 1 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x08
Repeat these for each GPIO pin, from 0 to 7.
One another possibility is to use the output pin NID 0x0f. For testing this, build with the reconfig feature (usually enabled), then change the pin 0x0f default config, such as
echo 0x0f 0x90171111 > /sys/class/sound/hwC0D0/user_pin_configs
then quit all sound apps and reconfigure
echo 1 > /sys/class/sound/hwC0D0/reconfig
Restore the mixer setup once via alsactl
alsactl restore
Then check the mixer volumes again, try aplay. With this setup, try GPIO procedures above, too.
thanks,
Takashi
For the tests I've created a little script (attached for review if I done something wrong), Here's the results
0x01: -------> dir = 0, data = 1 =====> Front Left -------> dir = 0, data = 0 =====> Front Left -------> dir = 1, data = 1 =====> Front Left -------> dir = 1, data = 0 =====> No Sound
0x02: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> No Sound -------> dir = 1, data = 0 =====> No Sound
0x04: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> No Sound -------> dir = 1, data = 0 =====> No Sound
0x16: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> No Sound -------> dir = 1, data = 0 =====> No Sound
0x32: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> LFE -------> dir = 1, data = 0 =====> No Sound
0x64: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> LFE -------> dir = 1, data = 0 =====> No Sound
0x128: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> LFE -------> dir = 1, data = 0 =====> No Sound
I've got the same results with the NID 0x0f
-- Wael Nasreddine
Weem Chief-Development Officer - http://www.weem.com
Blog : http://wael.nasreddine.com E-mail : wael.nasreddine@weem.com gTalk : wael.nasreddine@gmail.com Tel : +33.6.32.94.70.13 Skype : eMxyzptlk Twitter : @eMxyzptlk
PGP: 1024D/C8DD18A2 06F6 1622 4BC8 4CEB D724 DE12 5565 3945 C8DD 18A2
.: An infinite number of monkeys typing into GNU emacs, would never make a good program. (L. Torvalds 1995) :.
On Sat, Nov 14, 2009 at 15:25, Wael Nasreddine (a.k.a eMxyzptlk) < mla@nasreddine.com> wrote:
On Sat, Nov 14, 2009 at 14:03, Takashi Iwai tiwai@suse.de wrote:
At Sat, 14 Nov 2009 13:46:37 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
[1 <multipart/alternative (7bit)>] [1.1 <text/plain; UTF-8 (7bit)>] On Thu, Nov 12, 2009 at 11:16, Takashi Iwai tiwai@suse.de wrote:
At Thu, 12 Nov 2009 10:46:24 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
Takashi,
I tried the snapshot from
ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
last night with and without options still no go, the options I've tried:
- options snd-hda-intel enable_msi=
- options snd-hda-intel enable_msi=1 single_cmd=0
power_save_controller=0 power_save=0 model=hp-dv5
power_save should be irrelevant. And model=hp-dv5 and enable_msi=1 are already turned on as default in the recent version.
The next would be model=auto to avoid hp-dv5 quirk.
Also, it's helpful if you give a summary of your problems again.
Takashi
Takashi,
I just tried 'options snd-hda-intel enable_msi=1 model=auto' Didn't have much effect, the same problem (sound only from left speaker), always the same result with 'speaker-test -c6 -twav' I can only hear 'Front Left'
OK. But the headphone works, right?
Yes Headphones works, even mics works
Summary:
I have an HP DV7-1299EF, BIOS (Version F.2C, F.2A and F.23) , Due to a
BIOS
BUG, the BIOS report only one speaker as an output so the driver does not know how to use pins in order to have a stereo output ( at least that's what you told me last month when you analysed the alsa-info output)...
And
so one speaker, the left speaker is the only speaker currently working
under
Linux.
First I suspected a hardware problem so 2 days ago I restored Windows, tried the sound it works, and I updated my BIOS (it was version F.2A before) but sadly it has the same BUG, I also tried reverting back to
F.2A
and further back to F.23 same result...
Attached to this mail, my alsa-info.txt
The codec registers look OK through a quick look.
You can try GPIO pin up/down for each pin. Also each pin has two directions, so you'll have 8 x 2 x 2 trials. For example, to test GPIO 3, pass 0x08 (= 1 << 3), try the commands below and check aplay at each. (the lines '//' are just my comments)
// dir = 0, data = 1 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x00 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x08 // dir = 0, data = 0 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x00 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x00 // dir = 1, data = 0 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x00 // dir = 1, data = 1 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x08Repeat these for each GPIO pin, from 0 to 7.
One another possibility is to use the output pin NID 0x0f. For testing this, build with the reconfig feature (usually enabled), then change the pin 0x0f default config, such as
echo 0x0f 0x90171111 > /sys/class/sound/hwC0D0/user_pin_configsthen quit all sound apps and reconfigure
echo 1 > /sys/class/sound/hwC0D0/reconfigRestore the mixer setup once via alsactl
alsactl restoreThen check the mixer volumes again, try aplay. With this setup, try GPIO procedures above, too.
thanks,
Takashi
For the tests I've created a little script (attached for review if I done something wrong), Here's the results
0x01: -------> dir = 0, data = 1 =====> Front Left -------> dir = 0, data = 0 =====> Front Left -------> dir = 1, data = 1 =====> Front Left -------> dir = 1, data = 0 =====> No Sound
0x02: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> No Sound -------> dir = 1, data = 0 =====> No Sound
0x04: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> No Sound -------> dir = 1, data = 0 =====> No Sound
0x16: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> No Sound -------> dir = 1, data = 0 =====> No Sound
0x32: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> LFE -------> dir = 1, data = 0 =====> No Sound
0x64: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> LFE -------> dir = 1, data = 0 =====> No Sound
0x128: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> LFE -------> dir = 1, data = 0 =====> No Sound
I've got the same results with the NID 0x0f
Hey Takashi,
I forgot the
0x08: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> No Sound -------> dir = 1, data = 0 =====> No Sound
Looking at the results above, how can I get both the Front Left and LFE to output sound? and hopefully we get the right speaker later to work
Thanks
At Sun, 15 Nov 2009 17:26:00 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Sat, Nov 14, 2009 at 15:25, Wael Nasreddine (a.k.a eMxyzptlk) < mla@nasreddine.com> wrote:
On Sat, Nov 14, 2009 at 14:03, Takashi Iwai tiwai@suse.de wrote:
At Sat, 14 Nov 2009 13:46:37 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
[1 <multipart/alternative (7bit)>] [1.1 <text/plain; UTF-8 (7bit)>] On Thu, Nov 12, 2009 at 11:16, Takashi Iwai tiwai@suse.de wrote:
At Thu, 12 Nov 2009 10:46:24 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
Takashi,
I tried the snapshot from
ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
last night with and without options still no go, the options I've tried:
- options snd-hda-intel enable_msi=
- options snd-hda-intel enable_msi=1 single_cmd=0
power_save_controller=0 power_save=0 model=hp-dv5
power_save should be irrelevant. And model=hp-dv5 and enable_msi=1 are already turned on as default in the recent version.
The next would be model=auto to avoid hp-dv5 quirk.
Also, it's helpful if you give a summary of your problems again.
Takashi
Takashi,
I just tried 'options snd-hda-intel enable_msi=1 model=auto' Didn't have much effect, the same problem (sound only from left speaker), always the same result with 'speaker-test -c6 -twav' I can only hear 'Front Left'
OK. But the headphone works, right?
Yes Headphones works, even mics works
Summary:
I have an HP DV7-1299EF, BIOS (Version F.2C, F.2A and F.23) , Due to a
BIOS
BUG, the BIOS report only one speaker as an output so the driver does not know how to use pins in order to have a stereo output ( at least that's what you told me last month when you analysed the alsa-info output)...
And
so one speaker, the left speaker is the only speaker currently working
under
Linux.
First I suspected a hardware problem so 2 days ago I restored Windows, tried the sound it works, and I updated my BIOS (it was version F.2A before) but sadly it has the same BUG, I also tried reverting back to
F.2A
and further back to F.23 same result...
Attached to this mail, my alsa-info.txt
The codec registers look OK through a quick look.
You can try GPIO pin up/down for each pin. Also each pin has two directions, so you'll have 8 x 2 x 2 trials. For example, to test GPIO 3, pass 0x08 (= 1 << 3), try the commands below and check aplay at each. (the lines '//' are just my comments)
// dir = 0, data = 1 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x00 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x08 // dir = 0, data = 0 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x00 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x00 // dir = 1, data = 0 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x00 // dir = 1, data = 1 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x08Repeat these for each GPIO pin, from 0 to 7.
One another possibility is to use the output pin NID 0x0f. For testing this, build with the reconfig feature (usually enabled), then change the pin 0x0f default config, such as
echo 0x0f 0x90171111 > /sys/class/sound/hwC0D0/user_pin_configsthen quit all sound apps and reconfigure
echo 1 > /sys/class/sound/hwC0D0/reconfigRestore the mixer setup once via alsactl
alsactl restoreThen check the mixer volumes again, try aplay. With this setup, try GPIO procedures above, too.
thanks,
Takashi
For the tests I've created a little script (attached for review if I done something wrong), Here's the results
0x01: -------> dir = 0, data = 1 =====> Front Left -------> dir = 0, data = 0 =====> Front Left -------> dir = 1, data = 1 =====> Front Left -------> dir = 1, data = 0 =====> No Sound
0x02: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> No Sound -------> dir = 1, data = 0 =====> No Sound
0x04: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> No Sound -------> dir = 1, data = 0 =====> No Sound
0x16: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> No Sound -------> dir = 1, data = 0 =====> No Sound
0x32: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> LFE -------> dir = 1, data = 0 =====> No Sound
0x64: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> LFE -------> dir = 1, data = 0 =====> No Sound
0x128: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> LFE -------> dir = 1, data = 0 =====> No Sound
I've got the same results with the NID 0x0f
Hey Takashi,
I forgot the
0x08: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> No Sound -------> dir = 1, data = 0 =====> No Sound
Looking at the results above, how can I get both the Front Left and LFE to output sound? and hopefully we get the right speaker later to work
The LFE could be enabled by the patch below. Give it a try.
Takashi
--- diff --git a/sound/pci/hda/patch_sigmatel.c b/sound/pci/hda/patch_sigmatel.c index 7f76a97..57a561d 100644 --- a/sound/pci/hda/patch_sigmatel.c +++ b/sound/pci/hda/patch_sigmatel.c @@ -5468,6 +5468,18 @@ again: break; }
+ /* enable LFE on HP dv7 if available */ + if (spec->board_config == STAC_HP_DV5) { + unsigned int cap; + cap = snd_hda_param_read(codec, 0x1, AC_PAR_GPIO_CAP); + cap &= AC_GPIO_IO_COUNT; + if (cap >= 6) { + spec->gpio_mask |= 0x20; + spec->gpio_dir |= 0x20; + spec->gpio_data |= 0x20; + } + } + if (hp_bseries_system(codec->subsystem_id)) { pin_cfg = snd_hda_codec_get_pincfg(codec, 0x0f); if (get_defcfg_device(pin_cfg) == AC_JACK_LINE_OUT ||
2009/11/16 Takashi Iwai tiwai@suse.de
At Sun, 15 Nov 2009 17:26:00 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Sat, Nov 14, 2009 at 15:25, Wael Nasreddine (a.k.a eMxyzptlk) < mla@nasreddine.com> wrote:
On Sat, Nov 14, 2009 at 14:03, Takashi Iwai tiwai@suse.de wrote:
At Sat, 14 Nov 2009 13:46:37 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
[1 <multipart/alternative (7bit)>] [1.1 <text/plain; UTF-8 (7bit)>] On Thu, Nov 12, 2009 at 11:16, Takashi Iwai tiwai@suse.de wrote:
At Thu, 12 Nov 2009 10:46:24 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote: > > Takashi, > > I tried the snapshot from >
ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
> last night with and without options still no go, the options
I've
> tried: > > - options snd-hda-intel enable_msi= > - options snd-hda-intel enable_msi=1 single_cmd=0 > power_save_controller=0 power_save=0 model=hp-dv5
power_save should be irrelevant. And model=hp-dv5 and
enable_msi=1
are already turned on as default in the recent version.
The next would be model=auto to avoid hp-dv5 quirk.
Also, it's helpful if you give a summary of your problems again.
Takashi
Takashi,
I just tried 'options snd-hda-intel enable_msi=1 model=auto' Didn't have much effect, the same problem (sound only from left speaker), always the same result with 'speaker-test -c6 -twav' I can only
hear
'Front Left'
OK. But the headphone works, right?
Yes Headphones works, even mics works
Summary:
I have an HP DV7-1299EF, BIOS (Version F.2C, F.2A and F.23) , Due
to a
BIOS
BUG, the BIOS report only one speaker as an output so the driver does not
know
how to use pins in order to have a stereo output ( at least that's what you told me last month when you analysed the alsa-info
output)...
And
so one speaker, the left speaker is the only speaker currently
working
under
Linux.
First I suspected a hardware problem so 2 days ago I restored
Windows,
tried the sound it works, and I updated my BIOS (it was version
F.2A
before) but sadly it has the same BUG, I also tried reverting back
to
F.2A
and further back to F.23 same result...
Attached to this mail, my alsa-info.txt
The codec registers look OK through a quick look.
You can try GPIO pin up/down for each pin. Also each pin has two directions, so you'll have 8 x 2 x 2 trials. For example, to test GPIO 3, pass 0x08 (= 1 << 3), try the commands below and check aplay at each. (the lines '//' are just my comments)
// dir = 0, data = 1 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x00 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x08 // dir = 0, data = 0 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x00 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x00 // dir = 1, data = 0 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x00 // dir = 1, data = 1 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIR 0x08 hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x08Repeat these for each GPIO pin, from 0 to 7.
One another possibility is to use the output pin NID 0x0f. For testing this, build with the reconfig feature (usually enabled), then change the pin 0x0f default config, such as
echo 0x0f 0x90171111 >/sys/class/sound/hwC0D0/user_pin_configs
then quit all sound apps and reconfigure
echo 1 > /sys/class/sound/hwC0D0/reconfigRestore the mixer setup once via alsactl
alsactl restoreThen check the mixer volumes again, try aplay. With this setup, try GPIO procedures above, too.
thanks,
Takashi
For the tests I've created a little script (attached for review if I done something wrong), Here's the results
0x01: -------> dir = 0, data = 1 =====> Front Left -------> dir = 0, data = 0 =====> Front Left -------> dir = 1, data = 1 =====> Front Left -------> dir = 1, data = 0 =====> No Sound
0x02: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> No Sound -------> dir = 1, data = 0 =====> No Sound
0x04: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> No Sound -------> dir = 1, data = 0 =====> No Sound
0x16: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> No Sound -------> dir = 1, data = 0 =====> No Sound
0x32: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> LFE -------> dir = 1, data = 0 =====> No Sound
0x64: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> LFE -------> dir = 1, data = 0 =====> No Sound
0x128: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> LFE -------> dir = 1, data = 0 =====> No Sound
I've got the same results with the NID 0x0f
Hey Takashi,
I forgot the
0x08: -------> dir = 0, data = 1 =====> No Sound -------> dir = 0, data = 0 =====> No Sound -------> dir = 1, data = 1 =====> No Sound -------> dir = 1, data = 0 =====> No Sound
Looking at the results above, how can I get both the Front Left and LFE
to
output sound? and hopefully we get the right speaker later to work
The LFE could be enabled by the patch below. Give it a try.
Takashi
diff --git a/sound/pci/hda/patch_sigmatel.c b/sound/pci/hda/patch_sigmatel.c index 7f76a97..57a561d 100644 --- a/sound/pci/hda/patch_sigmatel.c +++ b/sound/pci/hda/patch_sigmatel.c @@ -5468,6 +5468,18 @@ again: break; }
/* enable LFE on HP dv7 if available */if (spec->board_config == STAC_HP_DV5) {unsigned int cap;cap = snd_hda_param_read(codec, 0x1, AC_PAR_GPIO_CAP);cap &= AC_GPIO_IO_COUNT;if (cap >= 6) {spec->gpio_mask |= 0x20;spec->gpio_dir |= 0x20;spec->gpio_data |= 0x20;}}if (hp_bseries_system(codec->subsystem_id)) { pin_cfg = snd_hda_codec_get_pincfg(codec, 0x0f); if (get_defcfg_device(pin_cfg) == AC_JACK_LINE_OUT ||
Takashi,
Thank you that actually worked, I have now both Front Left and LFE working, but it's very hard to tell coz the LFE is louder than both front speakers I even put my ear directly on the speaker and it still can't be 100% sure, but I think that for now what is working is 'Front Left + LFE', I can't hear anything from the right speaker.. but it's already an improvement to what I had.
Do you have any suggestion on how to enable the right speaker?
Thanks
At Mon, 16 Nov 2009 18:07:40 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
Thank you that actually worked, I have now both Front Left and LFE working, but it's very hard to tell coz the LFE is louder than both front speakers I even put my ear directly on the speaker and it still can't be 100% sure, but I think that for now what is working is 'Front Left + LFE', I can't hear anything from the right speaker.. but it's already an improvement to what I had.
Hm, if it's *so* loud, we should have a mixer control for this, I guess.
Do you have any suggestion on how to enable the right speaker?
No, already out of idea... I wonder whether any other people suffering from the same problem?
thanks,
Takashi
On Mon, Nov 16, 2009 at 18:15, Takashi Iwai tiwai@suse.de wrote:
At Mon, 16 Nov 2009 18:07:40 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
Thank you that actually worked, I have now both Front Left and LFE working, but it's very hard to tell coz the LFE is louder than both front speakers I even put my ear directly on the speaker and it still can't be 100% sure, but I think that for now what is working is 'Front Left + LFE', I can't hear anything from the right speaker.. but it's already an improvement to what I had.
Hm, if it's *so* loud, we should have a mixer control for this, I guess.
It's not *so* loud, but yea I appreciate a mixer for it yes! at least I can tell which speaker is working and also I can listen to Music without bothering someone else because with LFE the base is loud..
Do you have any suggestion on how to enable the right speaker?
No, already out of idea... I wonder whether any other people suffering from the same problem?
Julien has the same PC, same OS, same Kernel, same BIOS Version, but the weird thing is that he is not suffering from this problem, which obviously led me to beleive a hardware defect, but it's working on Windows!
@Julien, could you plz try the patch (attached enable-lfe-on-dv7.patch) against ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz ? and Tell us if it changes anything for you?
thanks,
Takashi
-- Wael Nasreddine
Weem Chief-Development Officer - http://www.weem.com
Blog : http://wael.nasreddine.com E-mail : wael.nasreddine@weem.com gTalk : wael.nasreddine@gmail.com Tel : +33.6.32.94.70.13 Skype : eMxyzptlk Twitter : @eMxyzptlk
PGP: 1024D/C8DD18A2 06F6 1622 4BC8 4CEB D724 DE12 5565 3945 C8DD 18A2
.: An infinite number of monkeys typing into GNU emacs, would never make a good program. (L. Torvalds 1995) :.
At Mon, 16 Nov 2009 18:22:56 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Mon, Nov 16, 2009 at 18:15, Takashi Iwai tiwai@suse.de wrote:
At Mon, 16 Nov 2009 18:07:40 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
Thank you that actually worked, I have now both Front Left and LFE working, but it's very hard to tell coz the LFE is louder than both front speakers I even put my ear directly on the speaker and it still can't be 100% sure, but I think that for now what is working is 'Front Left + LFE', I can't hear anything from the right speaker.. but it's already an improvement to what I had.
Hm, if it's *so* loud, we should have a mixer control for this, I guess.
It's not *so* loud, but yea I appreciate a mixer for it yes! at least I can tell which speaker is working and also I can listen to Music without bothering someone else because with LFE the base is loud..
OK, how about the patch below?
Do you have any suggestion on how to enable the right speaker?
No, already out of idea... I wonder whether any other people suffering from the same problem?
Julien has the same PC, same OS, same Kernel, same BIOS Version, but the weird thing is that he is not suffering from this problem, which obviously led me to beleive a hardware defect, but it's working on Windows!
This is really weird...
Takashi
--- diff --git a/sound/pci/hda/patch_sigmatel.c b/sound/pci/hda/patch_sigmatel.c index 7f76a97..cd3be33 100644 --- a/sound/pci/hda/patch_sigmatel.c +++ b/sound/pci/hda/patch_sigmatel.c @@ -1063,6 +1063,16 @@ static const char *slave_sws[] = { static void stac92xx_free_kctls(struct hda_codec *codec); static int stac92xx_add_jack(struct hda_codec *codec, hda_nid_t nid, int type);
+static void stac_add_mixer(struct sigmatel_spec *spec, + struct snd_kcontrol_new *knew) +{ + if (!knew) + return; + if (snd_BUG_ON(spec->num_mixers >= ARRAY_SIZE(spec->mixers))) + return; + spec->mixers[spec->num_mixers++] = knew; +} + static int stac92xx_build_controls(struct hda_codec *codec) { struct sigmatel_spec *spec = codec->spec; @@ -3825,8 +3835,7 @@ static int stac92xx_parse_auto_config(struct hda_codec *codec, hda_nid_t dig_out if (dig_in && spec->autocfg.dig_in_pin) spec->dig_in_nid = dig_in;
- if (spec->kctls.list) - spec->mixers[spec->num_mixers++] = spec->kctls.list; + stac_add_mixer(spec, spec->kctls.list);
spec->input_mux = &spec->private_imux; if (!spec->dinput_mux) @@ -3935,8 +3944,7 @@ static int stac9200_parse_auto_config(struct hda_codec *codec) if (spec->autocfg.dig_in_pin) spec->dig_in_nid = 0x04;
- if (spec->kctls.list) - spec->mixers[spec->num_mixers++] = spec->kctls.list; + stac_add_mixer(spec, spec->kctls.list);
spec->input_mux = &spec->private_imux; spec->dinput_mux = &spec->private_dimux; @@ -5280,6 +5288,54 @@ static int stac92hd71bxx_connected_smuxes(struct hda_codec *codec, return 0; }
+/* HP dv7 bass volume - GPIO5 */ +#define stac_hp_bass_gpio_info snd_ctl_boolean_mono_info +static int stac_hp_bass_gpio_get(struct snd_kcontrol *kcontrol, + struct snd_ctl_elem_value *ucontrol) +{ + struct hda_codec *codec = snd_kcontrol_chip(kcontrol); + struct sigmatel_spec *spec = codec->spec; + ucontrol->value.integer.value[0] = !!(spec->gpio_data & 0x20); + return 0; +} + +static int stac_hp_bass_gpio_put(struct snd_kcontrol *kcontrol, + struct snd_ctl_elem_value *ucontrol) +{ + struct hda_codec *codec = snd_kcontrol_chip(kcontrol); + struct sigmatel_spec *spec = codec->spec; + unsigned int gpio_data; + + gpio_data = (spec->gpio_data & ~0x20) | + (ucontrol->value.integer.value[0] ? 0x20 : 0); + if (gpio_data == spec->gpio_data) + return 0; + spec->gpio_data = gpio_data; + stac_gpio_set(codec, spec->gpio_mask, spec->gpio_dir, spec->gpio_data); + return 1; +} + +static struct snd_kcontrol_new stac_hp_bass_volume_ctrl[] = { + { + .iface = SNDRV_CTL_ELEM_IFACE_MIXER, + .name = "Bass Speaker Playback Volume", + .info = stac_hp_bass_gpio_info, + .get = stac_hp_bass_gpio_get, + .put = stac_hp_bass_gpio_put, + }, + {} /* terminator */ +}; + +static void stac_add_hp_bass_volume(struct hda_codec *codec) +{ + struct sigmatel_spec *spec = codec->spec; + + spec->gpio_mask |= 0x20; + spec->gpio_dir |= 0x20; + spec->gpio_data |= 0x20; + stac_add_mixer(spec, stac_hp_bass_volume_ctrl); +} + static int patch_stac92hd71bxx(struct hda_codec *codec) { struct sigmatel_spec *spec; @@ -5536,6 +5592,15 @@ again: return err; }
+ /* enable LFE on HP dv7 if available */ + if (spec->board_config == STAC_HP_DV5) { + unsigned int cap; + cap = snd_hda_param_read(codec, 0x1, AC_PAR_GPIO_CAP); + cap &= AC_GPIO_IO_COUNT; + if (cap >= 6) + stac_add_hp_bass_volume(codec); + } + codec->proc_widget_hook = stac92hd7x_proc_hook;
return 0;
On Mon, Nov 16, 2009 at 18:36, Takashi Iwai tiwai@suse.de wrote:
At Mon, 16 Nov 2009 18:22:56 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Mon, Nov 16, 2009 at 18:15, Takashi Iwai tiwai@suse.de wrote:
At Mon, 16 Nov 2009 18:07:40 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
Thank you that actually worked, I have now both Front Left and LFE working, but it's very hard to tell coz the LFE is louder than both front speakers I even put my ear directly on the speaker and it still can't be 100% sure, but I think that for now what is working is 'Front Left + LFE', I can't hear anything from the right speaker.. but it's already an improvement to what I had.
Hm, if it's *so* loud, we should have a mixer control for this, I guess.
It's not *so* loud, but yea I appreciate a mixer for it yes! at least I can tell which speaker is working and also I can listen to Music without bothering someone else because with LFE the base is loud..
OK, how about the patch below?
Do you have any suggestion on how to enable the right speaker?
No, already out of idea... I wonder whether any other people suffering from the same problem?
Julien has the same PC, same OS, same Kernel, same BIOS Version, but the weird thing is that he is not suffering from this problem, which obviously led me to beleive a hardware defect, but it's working on Windows!
This is really weird...
Takashi
Because the patch is not attached, I can't quite copy it correctly from Gmail, so I did it by hand (attached), I applied it but I don't see the mixer anywhere in alsamixer. I double checked the patch though...
-- Wael Nasreddine
Weem Chief-Development Officer - http://www.weem.com
Blog : http://wael.nasreddine.com E-mail : wael.nasreddine@weem.com gTalk : wael.nasreddine@gmail.com Tel : +33.6.32.94.70.13 Skype : eMxyzptlk Twitter : @eMxyzptlk
PGP: 1024D/C8DD18A2 06F6 1622 4BC8 4CEB D724 DE12 5565 3945 C8DD 18A2
.: An infinite number of monkeys typing into GNU emacs, would never make a good program. (L. Torvalds 1995) :.
At Mon, 16 Nov 2009 19:34:45 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
[1 <text/plain; UTF-8 (quoted-printable)>] On Mon, Nov 16, 2009 at 18:36, Takashi Iwai tiwai@suse.de wrote:
At Mon, 16 Nov 2009 18:22:56 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Mon, Nov 16, 2009 at 18:15, Takashi Iwai tiwai@suse.de wrote:
At Mon, 16 Nov 2009 18:07:40 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
Thank you that actually worked, I have now both Front Left and LFE working, but it's very hard to tell coz the LFE is louder than both front speakers I even put my ear directly on the speaker and it still can't be 100% sure, but I think that for now what is working is 'Front Left + LFE', I can't hear anything from the right speaker.. but it's already an improvement to what I had.
Hm, if it's *so* loud, we should have a mixer control for this, I guess.
It's not *so* loud, but yea I appreciate a mixer for it yes! at least I can tell which speaker is working and also I can listen to Music without bothering someone else because with LFE the base is loud..
OK, how about the patch below?
Do you have any suggestion on how to enable the right speaker?
No, already out of idea... I wonder whether any other people suffering from the same problem?
Julien has the same PC, same OS, same Kernel, same BIOS Version, but the weird thing is that he is not suffering from this problem, which obviously led me to beleive a hardware defect, but it's working on Windows!
This is really weird...
Takashi
Because the patch is not attached, I can't quite copy it correctly from Gmail,
You have a pull-down menu at the top-right corner of each mail in gmail. There you can choose "Show original". This will show the raw texts so that you can save it from the browser.
Possibly this menu item appears only in English language mode, though.
so I did it by hand (attached), I applied it but I don't see the mixer anywhere in alsamixer. I double checked the patch though...
I revised the patch. Attached below. Try it instead. You'll have "Bass Speaker" mixer switch, maybe at the most right side.
Takashi --- diff --git a/sound/pci/hda/patch_sigmatel.c b/sound/pci/hda/patch_sigmatel.c index 7f76a97..6a2a501 100644 --- a/sound/pci/hda/patch_sigmatel.c +++ b/sound/pci/hda/patch_sigmatel.c @@ -5280,6 +5280,54 @@ static int stac92hd71bxx_connected_smuxes(struct hda_codec *codec, return 0; }
+/* HP dv7 bass switch - GPIO5 */ +#define stac_hp_bass_gpio_info snd_ctl_boolean_mono_info +static int stac_hp_bass_gpio_get(struct snd_kcontrol *kcontrol, + struct snd_ctl_elem_value *ucontrol) +{ + struct hda_codec *codec = snd_kcontrol_chip(kcontrol); + struct sigmatel_spec *spec = codec->spec; + ucontrol->value.integer.value[0] = !!(spec->gpio_data & 0x20); + return 0; +} + +static int stac_hp_bass_gpio_put(struct snd_kcontrol *kcontrol, + struct snd_ctl_elem_value *ucontrol) +{ + struct hda_codec *codec = snd_kcontrol_chip(kcontrol); + struct sigmatel_spec *spec = codec->spec; + unsigned int gpio_data; + + gpio_data = (spec->gpio_data & ~0x20) | + (ucontrol->value.integer.value[0] ? 0x20 : 0); + if (gpio_data == spec->gpio_data) + return 0; + spec->gpio_data = gpio_data; + stac_gpio_set(codec, spec->gpio_mask, spec->gpio_dir, spec->gpio_data); + return 1; +} + +static struct snd_kcontrol_new stac_hp_bass_sw_ctrl = { + .iface = SNDRV_CTL_ELEM_IFACE_MIXER, + .info = stac_hp_bass_gpio_info, + .get = stac_hp_bass_gpio_get, + .put = stac_hp_bass_gpio_put, +}; + +static int stac_add_hp_bass_switch(struct hda_codec *codec) +{ + struct sigmatel_spec *spec = codec->spec; + + if (!stac_control_new(spec, &stac_hp_bass_sw_ctrl, + "Bass Speaker Playback Switch", 0)) + return -ENOMEM; + + spec->gpio_mask |= 0x20; + spec->gpio_dir |= 0x20; + spec->gpio_data |= 0x20; + return 0; +} + static int patch_stac92hd71bxx(struct hda_codec *codec) { struct sigmatel_spec *spec; @@ -5536,6 +5584,15 @@ again: return err; }
+ /* enable bass on HP dv7 */ + if (spec->board_config == STAC_HP_DV5) { + unsigned int cap; + cap = snd_hda_param_read(codec, 0x1, AC_PAR_GPIO_CAP); + cap &= AC_GPIO_IO_COUNT; + if (cap >= 6) + stac_add_hp_bass_switch(codec); + } + codec->proc_widget_hook = stac92hd7x_proc_hook;
return 0;
On Mon, Nov 16, 2009 at 20:30, Takashi Iwai tiwai@suse.de wrote:
At Mon, 16 Nov 2009 19:34:45 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
[1 <text/plain; UTF-8 (quoted-printable)>] On Mon, Nov 16, 2009 at 18:36, Takashi Iwai tiwai@suse.de wrote:
At Mon, 16 Nov 2009 18:22:56 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Mon, Nov 16, 2009 at 18:15, Takashi Iwai tiwai@suse.de wrote:
At Mon, 16 Nov 2009 18:07:40 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
Thank you that actually worked, I have now both Front Left and
LFE working,
but it's very hard to tell coz the LFE is louder than both front
speakers I
even put my ear directly on the speaker and it still can't be
100% sure, but
I think that for now what is working is 'Front Left + LFE', I
can't hear
anything from the right speaker.. but it's already an improvement
to what I
had.
Hm, if it's *so* loud, we should have a mixer control for this, I guess.
It's not *so* loud, but yea I appreciate a mixer for it yes! at least I can tell which speaker is working and also I can listen to Music without bothering someone else because with LFE the base is loud..
OK, how about the patch below?
Do you have any suggestion on how to enable the right speaker?
No, already out of idea... I wonder whether any other people suffering from the same problem?
Julien has the same PC, same OS, same Kernel, same BIOS Version, but the weird thing is that he is not suffering from this problem, which obviously led me to beleive a hardware defect, but it's working on Windows!
This is really weird...
Takashi
Because the patch is not attached, I can't quite copy it correctly from Gmail,
You have a pull-down menu at the top-right corner of each mail in gmail. There you can choose "Show original". This will show the raw texts so that you can save it from the browser.
Possibly this menu item appears only in English language mode, though.
I have this and that's what I used earlier but it failed on many hunks, now
it only failed on one, the last hunk, so I applied the last one by hand
so I did it by hand (attached), I applied it but I don't see the mixer anywhere in alsamixer. I double checked the patch though...
I revised the patch. Attached below. Try it instead. You'll have "Bass Speaker" mixer switch, maybe at the most right side.
Takashi
Thank you, this patch works indeed, I can enable/disable the LFE as I like now, Thank you so much !!
Why do you think the drivers needed special GPIO settings while another PC, same PC didn't need anything, BIOS BUG or maybe hardware defect?
At Mon, 16 Nov 2009 20:59:22 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
[1 <text/plain; UTF-8 (7bit)>] On Mon, Nov 16, 2009 at 20:30, Takashi Iwai tiwai@suse.de wrote:
At Mon, 16 Nov 2009 19:34:45 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
[1 <text/plain; UTF-8 (quoted-printable)>] On Mon, Nov 16, 2009 at 18:36, Takashi Iwai tiwai@suse.de wrote:
At Mon, 16 Nov 2009 18:22:56 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Mon, Nov 16, 2009 at 18:15, Takashi Iwai tiwai@suse.de wrote:
At Mon, 16 Nov 2009 18:07:40 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote: > > Thank you that actually worked, I have now both Front Left and
LFE working,
> but it's very hard to tell coz the LFE is louder than both front
speakers I
> even put my ear directly on the speaker and it still can't be
100% sure, but
> I think that for now what is working is 'Front Left + LFE', I
can't hear
> anything from the right speaker.. but it's already an improvement
to what I
> had.
Hm, if it's *so* loud, we should have a mixer control for this, I guess.
It's not *so* loud, but yea I appreciate a mixer for it yes! at least I can tell which speaker is working and also I can listen to Music without bothering someone else because with LFE the base is loud..
OK, how about the patch below?
> Do you have any suggestion on how to enable the right speaker?
No, already out of idea... I wonder whether any other people suffering from the same problem?
Julien has the same PC, same OS, same Kernel, same BIOS Version, but the weird thing is that he is not suffering from this problem, which obviously led me to beleive a hardware defect, but it's working on Windows!
This is really weird...
Takashi
Because the patch is not attached, I can't quite copy it correctly from Gmail,
You have a pull-down menu at the top-right corner of each mail in gmail. There you can choose "Show original". This will show the raw texts so that you can save it from the browser.
Possibly this menu item appears only in English language mode, though.
I have this and that's what I used earlier but it failed on many hunks, now
it only failed on one, the last hunk, so I applied the last one by hand
Maybe you aren't using the very latest alsa-driver code?
so I did it by hand (attached), I applied it but I don't see the mixer anywhere in alsamixer. I double checked the patch though...
I revised the patch. Attached below. Try it instead. You'll have "Bass Speaker" mixer switch, maybe at the most right side.
Takashi
Thank you, this patch works indeed, I can enable/disable the LFE as I like now, Thank you so much !!
Why do you think the drivers needed special GPIO settings while another PC, same PC didn't need anything, BIOS BUG or maybe hardware defect?
Well, the question is whether this bass effect wasn't used on any HP dv laptops at all until yet, or it was already enabled as default.
As I have no hardware itself, I really have no idea about it... Can anyone tell whether the bass was enabled already?
thanks,
Takashi
At Tue, 17 Nov 2009 07:37:33 +0100, I wrote:
At Mon, 16 Nov 2009 20:59:22 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
[1 <text/plain; UTF-8 (7bit)>] On Mon, Nov 16, 2009 at 20:30, Takashi Iwai tiwai@suse.de wrote:
At Mon, 16 Nov 2009 19:34:45 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
[1 <text/plain; UTF-8 (quoted-printable)>] On Mon, Nov 16, 2009 at 18:36, Takashi Iwai tiwai@suse.de wrote:
At Mon, 16 Nov 2009 18:22:56 +0100, Wael Nasreddine (a.k.a eMxyzptlk) wrote:
On Mon, Nov 16, 2009 at 18:15, Takashi Iwai tiwai@suse.de wrote: > > At Mon, 16 Nov 2009 18:07:40 +0100, > Wael Nasreddine (a.k.a eMxyzptlk) wrote: > > > > Thank you that actually worked, I have now both Front Left and
LFE working,
> > but it's very hard to tell coz the LFE is louder than both front
speakers I
> > even put my ear directly on the speaker and it still can't be
100% sure, but
> > I think that for now what is working is 'Front Left + LFE', I
can't hear
> > anything from the right speaker.. but it's already an improvement
to what I
> > had. > > Hm, if it's *so* loud, we should have a mixer control for this, I > guess. > It's not *so* loud, but yea I appreciate a mixer for it yes! at least I can tell which speaker is working and also I can listen to Music without bothering someone else because with LFE the base is loud..
OK, how about the patch below?
> > Do you have any suggestion on how to enable the right speaker? > > No, already out of idea... I wonder whether any other people > suffering from the same problem? > Julien has the same PC, same OS, same Kernel, same BIOS Version, but the weird thing is that he is not suffering from this problem, which obviously led me to beleive a hardware defect, but it's working on Windows!
This is really weird...
Takashi
Because the patch is not attached, I can't quite copy it correctly from Gmail,
You have a pull-down menu at the top-right corner of each mail in gmail. There you can choose "Show original". This will show the raw texts so that you can save it from the browser.
Possibly this menu item appears only in English language mode, though.
I have this and that's what I used earlier but it failed on many hunks, now
it only failed on one, the last hunk, so I applied the last one by hand
Maybe you aren't using the very latest alsa-driver code?
so I did it by hand (attached), I applied it but I don't see the mixer anywhere in alsamixer. I double checked the patch though...
I revised the patch. Attached below. Try it instead. You'll have "Bass Speaker" mixer switch, maybe at the most right side.
Takashi
Thank you, this patch works indeed, I can enable/disable the LFE as I like now, Thank you so much !!
Why do you think the drivers needed special GPIO settings while another PC, same PC didn't need anything, BIOS BUG or maybe hardware defect?
Well, the question is whether this bass effect wasn't used on any HP dv laptops at all until yet, or it was already enabled as default.
As I have no hardware itself, I really have no idea about it... Can anyone tell whether the bass was enabled already?
BTW, do you happen to know whether the bass feature is on other HP dv models such as dv5? Isn't it specific to dv7?
We might need to look up PCI SSID or DMI entries to sort this out. Could you give dmidecode output?
thanks,
Takashi
participants (2)
-
Takashi Iwai -
Wael Nasreddine (a.k.a eMxyzptlk)