All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Talbut <john@dpets.demon.co.uk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Setup when compiled in 2.6 kernel
Date: Sun, 19 Feb 2006 21:47:45 +0000	[thread overview]
Message-ID: <43F8E781.4030802@dpets.demon.co.uk> (raw)
In-Reply-To: <1140378836.2733.357.camel@mindpipe>

Lee Revell wrote:

>>
>>>This is not how ALSA works, you can't just cat things to the device
>>>file.  The interface to ALSA is through alsa-lib.
>>
>>Can you or anyone explain this, or point to an explanation?
> 
> 
> What's to explain?

Well, some other devices can be checked to see if they are working by 
cat-ing to them.  It seems as if these are different.

>  Userspace apps don't access the device files
> directly.  They should use the alsa-lib API.  Here is the documentation:
> 
> http://www.alsa-project.org/alsa-doc/alsa-lib/

Thanks for that, I guess the answer is there, I will study it more when 
I get a moment.
> 
>>>What happens if you start SIMPLE:
>>>
>>>aplay file.wav
>>
>># aplay /dos/Workspace/Music/originaldedodedo.wav
>>ALSA lib pcm.c:2099:(snd_pcm_open_noupdate) Unknown PCM default
>>aplay: main:544: audio open error: No such file or directory
>>
> 
> 
> 
> Because it defaults to device 0 which is usually a real soundcard, but
> not on your system:
> 
> /proc/asound/cards:
> 
> 0 [Dummy          ]: Dummy - Dummy
>                       Dummy 1
> 1 [VirMIDI        ]: VirMIDI - VirMIDI
>                       Virtual MIDI Card 1
> 2 [AudioPCI       ]: ENS1371 - Ensoniq AudioPCI
>                       Ensoniq AudioPCI ENS1371 at 0xdf00, irq 10
> 
> Try unloading the snd-dummy and snd-virmidi modules, or don't enable
> them when compiling the kernel.

Is there any way of testing whether this is the/a problem before I 
recompile the kernel?  I will have to upgrade it when I recompile (2.6.8 
does not compile with gcc-4.0, which is what I have now.)
> 
> Did you try this first with your distro's default kernel before building your own?

No, I have been using custom compiled kernels for a long time.

John


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

  reply	other threads:[~2006-02-19 21:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-19 17:21 Setup when compiled in 2.6 kernel John Talbut
2006-02-19 19:00 ` Lee Revell
2006-02-19 19:46   ` John Talbut
2006-02-19 19:53     ` Lee Revell
2006-02-19 21:47       ` John Talbut [this message]
2006-02-19 21:52         ` Lee Revell
2006-02-20  7:13           ` John Talbut
2006-02-20  8:01             ` Lee Revell
2006-02-20  8:21     ` Clemens Ladisch

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=43F8E781.4030802@dpets.demon.co.uk \
    --to=john@dpets.demon.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=rlrevell@joe-job.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.