From: rishi.b.agrawal@gmail.com (Rishi Agrawal)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Sound not coming after compiling new kernel 2.6.36
Date: Tue, 21 Dec 2010 10:11:05 +0530 [thread overview]
Message-ID: <AANLkTik8eYhRxRoc0o2SFmFdQE1G55nXsaKXCLCyo7hT@mail.gmail.com> (raw)
Hi All,
I compiled the kernel 2.6.36 and now the sound is missing. I have pasted the
outputs of lsmod and lspci. I have fedora 12 installed on the system.
Have I done something wrong in the menuconfig stage.
Sound is coming properly with the old Fedora Kernel.
I tried tweaking the alsamixer but it did not work.
[rishi at rishi-desktop ~]$ uname -a
Linux rishi-desktop 2.6.36 #1 SMP Sat Dec 18 21:24:34 IST 2010 i686 i686
i386 GNU/Linux
[rishi at rishi-desktop ~]$ lspci | grep -i audio
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition
Audio Controller (rev 02)
[rishi at rishi-desktop ~]$ lsmod | grep snd
snd_hda_codec_analog 53691 1
snd_hda_intel 20031 1
snd_hda_codec 73253 2 snd_hda_codec_analog,snd_hda_intel
snd_hwdep 4856 1 snd_hda_codec
snd_seq 42695 0
snd_seq_device 4937 1 snd_seq
snd_pcm 62570 2 snd_hda_intel,snd_hda_codec
snd_timer 15387 2 snd_seq,snd_pcm
snd 46823 11
snd_hda_codec_analog,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer,thinkpad_acpi
snd_page_alloc 6077 2 snd_hda_intel,snd_pcm
soundcore 4831 1 snd
--
Regards,
Rishi Agrawal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20101221/9e6aae1a/attachment.html
next reply other threads:[~2010-12-21 4:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 4:41 Rishi Agrawal [this message]
2010-12-21 5:34 ` Sound not coming after compiling new kernel 2.6.36 Rajat Sharma
2010-12-21 18:37 ` Shreyansh Jain
2010-12-22 14:22 ` Mulyadi Santosa
2010-12-22 16:08 ` Bharath H S
2010-12-23 16:06 ` Rishi Agrawal
2010-12-24 6:29 ` Nilesh Tayade
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=AANLkTik8eYhRxRoc0o2SFmFdQE1G55nXsaKXCLCyo7hT@mail.gmail.com \
--to=rishi.b.agrawal@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).