Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Vinod Koul" <vinod.koul@gmail.com>
To: Tobin Davis <tdavis@dsl-only.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: ALSA Debugging
Date: Mon, 24 Mar 2008 08:52:15 +0530	[thread overview]
Message-ID: <b29ed9aa0803232022j12422d05h3cab9d6fe9734e9f@mail.gmail.com> (raw)
In-Reply-To: <1206116141.4863.127.camel@razman.gruemaster.com>

Thanks Tobin,
Checked snd-intel8x0 is loaded.

Did rmmod and tried to insert with my compiled driver from my sources gives
an error: "error inserting 'snd-intel8x0.ko' : -1 Invalid module format"

Checked from Yast, my sound card is 82801G AC'97, driver snd-intel8x0

-Vinod

On Fri, Mar 21, 2008 at 9:45 PM, Tobin Davis <tdavis@dsl-only.net> wrote:

>  First, verify that you are working with the correct driver.  lsmod will
> tell you which sound drivers are loaded.  If this is a newer system, you're
> probably using the snd-hda-intel driver, which is a whole lot different.
>
> Tobin
>
> On Fri, 2008-03-21 at 20:45 +0530, Vinod Koul wrote:
>
> Hello,I am new to ALSA and Linux. I was trying to understand the ALSAarchitecture.
> I have Linux Box with Intel sound card. with Suse 10.1 on it.I launched the audio player (Real player) and audio plays fine.
> Then, I built the kernel and installed it. I put some printk's in intel8x0.candcontrol.c. (could see the my code was complied)Even though I changed volume muted etc couldn't see any of my printk indmesg. One default printk in intel8x0.c was there, so I have put my printbefore that line as well, but couldn't see anything.
> Apologies If my problem is very basic. I read on forums that best way tolearn is to put printk's.
> Can anyone help me with where I am doing incorrectly, Am I supposed to do itthis way or some other way?
> Thanks in advance-Vinod
> _______________________________________________Alsa-devel mailing listAlsa-devel@alsa-project.orghttp://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
>   -- Tobin Davis
>
> The man on tops walks a lonely street; the "chain" of command is often a noose.
>
>

      reply	other threads:[~2008-03-24  3:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-21 15:15 ALSA Debugging Vinod Koul
2008-03-21 16:15 ` Tobin Davis
2008-03-24  3:22   ` Vinod Koul [this message]

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=b29ed9aa0803232022j12422d05h3cab9d6fe9734e9f@mail.gmail.com \
    --to=vinod.koul@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tdavis@dsl-only.net \
    /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