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@xxxxxxx> 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 _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
