public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Silla Rizzoli <biker@ngi.it>
To: linux-kernel@vger.kernel.org
Subject: No sound from Lenovo 3000 N100
Date: Wed, 6 Jun 2007 17:47:40 +0200	[thread overview]
Message-ID: <200706061747.42559.biker@ngi.it> (raw)

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

I've just tried 2.6.22-rc4 and sound doesn't work. It has never worked before, 
unless I disable ACPI.

dmesg (ALSA debug messages are enabled):
ACPI: PCI interrupt for device 0000:00:1b.0 disabled
ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 21
PCI: Setting latency timer of device 0000:00:1b.0 to 64
ALSA sound/pci/hda/hda_intel.c:695: codec_mask = 0x3
ALSA sound/pci/hda/hda_codec.c:1732: hda_codec: model '3stack' is selected
ALSA sound/pci/hda/patch_si3054.c:245: si3054: cannot initialize. EXT MID = 
0000
ALSA sound/pci/hda/patch_si3054.c:257: Link Frame Detect(FDT) is not ready 
(line status: 0000)


lspci -v:

00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition 
Audio Controller (rev 02)
        Subsystem: Lenovo Unknown device 2066
        Flags: bus master, fast devsel, latency 0, IRQ 21
        Memory at d2400000 (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)

.config attached


Any help is greatly appreciated.

Best regards,
Silla

[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 13033 bytes --]

             reply	other threads:[~2007-06-06 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 15:47 Silla Rizzoli [this message]
2007-06-06 16:09 ` No sound from Lenovo 3000 N100 Chuck Ebbert
2007-06-06 17:33   ` Silla Rizzoli

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=200706061747.42559.biker@ngi.it \
    --to=biker@ngi.it \
    --cc=linux-kernel@vger.kernel.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