From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Thomas Meyer <thomas@m3y3r.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Takashi Iwai <tiwai@suse.de>
Subject: Re: hda-intel: no soundcard with current linus' git tree
Date: Thu, 18 Oct 2007 05:36:18 +0200 [thread overview]
Message-ID: <200710180536.18611.maximlevitsky@gmail.com> (raw)
In-Reply-To: <4716C68C.4030504@garzik.org>
On Thursday 18 October 2007 04:35:56 Jeff Garzik wrote:
> Thomas Meyer wrote:
> > $ dmesg
> >
> > [schnipp]
> >
> > ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 21
> > PCI: Enabling bus mastering for device 0000:00:1b.0
> > PCI: Setting latency timer of device 0000:00:1b.0 to 64
> > hda_codec: STAC922x, Apple subsys_id=106b0200
> > ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> > HDA Intel: probe of 0000:00:1b.0 failed with error -16
> >
> > [schnipp]
>
> My sound ability similarly disappeared an upstream kernel <24 hours old
> (includes the ALSA merge).
>
> [jgarzik@core ~]$ lsmod | grep -i snd
> snd_hda_intel 367396 2
> snd_pcm_oss 42080 0
> snd_mixer_oss 16640 2 snd_pcm_oss
> snd_pcm 79624 2 snd_hda_intel,snd_pcm_oss
> snd_page_alloc 9040 2 snd_hda_intel,snd_pcm
>
> [jgarzik@core ~]$ lspci | grep -i audio
> 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High
> Definition Audio Controller (rev 01)
>
> [jgarzik@core ~]$ dmesg | egrep -i 'snd|hda'
> [jgarzik@core ~]$
>
> mplayer says
>
> AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
>
> but no sound is emitted.
>
> Earlier kernels been working fine since hda_intel was introduced.
>
> Jeff
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
What sound codec do you have?
cat /proc/asound/Intel/codec*
You probably have different issue, since your card is probed correctly
Regards,
Maxim Levitsky
next prev parent reply other threads:[~2007-10-18 3:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 22:18 hda-intel: no soundcard with current linus' git tree Thomas Meyer
2007-10-17 2:47 ` Maxim Levitsky
2007-10-17 8:42 ` Takashi Iwai
2007-10-17 18:17 ` Thomas Meyer
2007-10-18 1:51 ` Maxim Levitsky
2007-10-18 1:53 ` Maxim Levitsky
2007-10-18 5:57 ` Takashi Iwai
2007-10-18 14:21 ` Maxim Levitsky
2007-10-18 13:49 ` Takashi Iwai
2007-10-18 15:24 ` Maxim Levitsky
2007-10-18 14:47 ` Takashi Iwai
2007-10-21 15:42 ` Thomas Meyer
2007-10-18 2:35 ` Jeff Garzik
2007-10-18 3:36 ` Maxim Levitsky [this message]
2007-10-18 3:38 ` Jeff Garzik
2007-10-18 4:10 ` Maxim Levitsky
2007-10-18 4:24 ` Jeff Garzik
2007-10-18 6:02 ` Takashi Iwai
2007-10-18 8:49 ` Jan-Simon Möller
2007-10-18 8:11 ` [alsa-devel] " Takashi Iwai
2007-10-18 11:50 ` Jan-Simon Möller
2007-10-18 15:05 ` Jan-Simon Möller
2007-10-18 14:39 ` Takashi Iwai
2007-10-18 16:19 ` Jan-Simon Möller
2007-10-19 5:05 ` Takashi Iwai
2007-10-19 10:46 ` Jan-Simon Möller
2007-10-19 10:02 ` Takashi Iwai
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=200710180536.18611.maximlevitsky@gmail.com \
--to=maximlevitsky@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@m3y3r.de \
--cc=tiwai@suse.de \
/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