public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Rimas Kudelis <rq@akl.lt>
To: bugtrack@alsa-project.org
Cc: alsa-devel@alsa-project.org
Subject: Re: [ALSA - driver 0001662]: No audio output in a laptop with hda-intel....
Date: Wed, 08 Mar 2006 21:47:52 +0200	[thread overview]
Message-ID: <440F34E8.6010203@akl.lt> (raw)
In-Reply-To: <017f45edbf73ae80c0f9d6fce889fb25@bugtrack.alsa-project.org>

[-- Attachment #1: Type: text/plain, Size: 4370 bytes --]

Takashi, it's now your turn. ;)

Rimas


bugtrack@alsa-project.org wrote:
> A NOTE has been added to this issue.
> ======================================================================
> <https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1662> 
> ======================================================================
> Reported By:                shl
> Assigned To:                tiwai
> ======================================================================
> Project:                    ALSA - driver
> Issue ID:                   1662
> Category:                   PCI - hda-intel
> Reproducibility:            always
> Severity:                   feature
> Priority:                   normal
> Status:                     assigned
> Distribution:               Gentoo Linux
> Kernel Version:             2.6.13.4
> ======================================================================
> Date Submitted:             12-20-2005 11:18 CET
> Last Modified:              03-08-2006 20:44 CET
> ======================================================================
> Summary:                    No audio output in a laptop with hda-intel....
> Description: 
> Hy, I managed to install the hda-intel on my laptop but my big problem is
> :
> The speakers inside the laptop work correctly but everytime I try to plug
> a headset or some external speaker in the output used normally for it, I'd
> the same result : no sound in the laptop'speakers AND no sound at all in
> the external speakers. So after looking a long long time about that
> problem, I didn't find anything. So maybe the function is not yet
> implemented ? If it's the case, is it possible to do it because it'll be
> very usefull for a lot of people ! Thanks for advance and don't hesitate
> to send me a mail if I missed something ...
> 
> 
> ======================================================================
> 
> ----------------------------------------------------------------------
>  er-ku - 03-04-06 10:56 
> ----------------------------------------------------------------------
> Actually, you can help the developers make the module autodetect the card.
> All you have to do is to provide a tiny bit of information they need.
> Here's how:
> 
> 1) go to terminal, and run "lspci -nvd 8086:2668" in it. You should get
> something like this:
> 
> $ lspci -nvd 8086:2668
> 0000:00:1b.0 Class 0403: 8086:2668 (rev 04)
>     Subsystem: 10cf:1326
>     Flags: bus master, fast devsel, latency 0, IRQ 17
>     Memory at b0000000 (64-bit, non-prefetchable) [size=16k]
>     Capabilities: <available only to root>
> 
> 2) paste the output of the command as a comment here, in this bugreport.
> Also, please check if all the controls in  mixer are working as expected,
> and tell if they are.
> 
> After you do this, you may expect the driver to work automagically,
> without tweaking the modules.d/alsa file, in the next version.
> 
> 
> 
> ----------------------------------------------------------------------
>  nutz - 03-08-06 20:44 
> ----------------------------------------------------------------------
> okay here it goes:
> # lspci -vs 00:1b.0
> 00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
> Family) High Definition Audio Controller (rev 04)
>         Subsystem: ASUSTeK Computer Inc. Unknown device 1173
>         Flags: bus master, fast devsel, latency 0, IRQ 11
>         Memory at febf8000 (64-bit, non-prefetchable) [size=16K]
>         Capabilities: [50] Power Management version 2
>         Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0
> Enable-
>         Capabilities: [70] Express Unknown type IRQ 0
>         Capabilities: [100] Virtual Channel
>         Capabilities: [130] Unknown (5)
> 
> 
> # lspci -vns 00:1b.0
> 00:1b.0 0403: 8086:2668 (rev 04)
>         Subsystem: 1043:1173
>         Flags: bus master, fast devsel, latency 0, IRQ 11
>         Memory at febf8000 (64-bit, non-prefetchable) [size=16K]
>         Capabilities: [50] Power Management version 2
>         Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0
> Enable-
>         Capabilities: [70] Express Unknown type IRQ 0
>         Capabilities: [100] Virtual Channel
>         Capabilities: [130] Unknown (5)
> 
> 
> 
> thanks again
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

  reply	other threads:[~2006-03-08 19:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08 19:44 [ALSA - driver 0001662]: No audio output in a laptop with hda-intel bugtrack
2006-03-08 19:47 ` Rimas Kudelis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-21  7:48 bugtrack
2006-03-09 12:09 bugtrack
2006-03-04  9:45 bugtrack
2006-03-04  2:32 bugtrack
2006-01-08 12:54 bugtrack
2005-12-23  1:04 bugtrack
2005-12-20 10:18 bugtrack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=440F34E8.6010203@akl.lt \
    --to=rq@akl.lt \
    --cc=alsa-devel@alsa-project.org \
    --cc=bugtrack@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox