From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] ALSA don't work
Date: Fri, 05 Oct 2012 20:29:26 +0300 [thread overview]
Message-ID: <506F18F6.5010506@petroprogram.com> (raw)
In-Reply-To: <506EFDEE.5020307@ronetix.at>
5.10.2012 18:34, Martin Peevski kirjoitti:
> On 05/10/12 17:59, Stefan Fr?berg wrote:
>> Have you build your ALSA soundcard drivers as modules ?
>>
>> what does lsmod command give you ?
>>
>> have you checked files in
>> /lib/modules/your_kernel_version_here/kernel/sound ?
>>
>> Best regards:
>> Stefan
>>
>> 5.10.2012 17:42, Martin Peevski kirjoitti:
>>> Hi, I build a Linux system with Buildroot but it don't work -
>>> impossible to start applications. This is theconsole log:
>>>
>>> # aplay -l
>>> aplay: device_list:252: no soundcards found...
>>> [16:11:18] engineerpeevski: # alsactl init
>>> alsactl: init:1743: No soundcards found...
>>> [16:11:30] engineerpeevski: # alsaconf
>>> -sh: alsaconf: not found
>>>
>>> Also when the Kernel boots there is a message that a sound card was
>>> found and with another rootfs it works. I think that it's something in
>>> the config, can you help me, please? I work with AT91SAM9G45 SoC.
>>>
>>> Thanks in advance, Martin!
>>> _______________________________________________
>>> buildroot mailing list
>>> buildroot at busybox.net
>>> http://lists.busybox.net/mailman/listinfo/buildroot
> First must tell you that want to use sound only with WAV files!
>
Irrelevant. Your sound card could care less if you are playing wav, ogg,
mp3 or whatever....
> I built the Kernel with installed in it drivers NOT as modules.
>
> The lsmod command gives me the following:
> # lsmod
> Module Size Used by Not tainted
>
> That's 0 modules I think. Also have not /lib/modules/ ...
> /kernel/sound directory because I haven't modules, I think.
>
Yes.
>
> I search in internet and find the following which claims that I must
> edit the device table in Buildroot configuration:
> http://elasticsheep.com/2011/01/adding-alsa-audio-support-to-a-buildroot-based-system/
>
> but will try it tomorrow. Is it true any way?
>
> Do I need something another special in the config except enabling the
> ALSA and needed tools from it, as alsamixet?
>
>
Well, if you really have built every driver you need in to your kernel
as built-in and not as modules then
you have to do it The Hard Way (tm).
So go ahead and create all those device nodes mentioned in that link.
I use mdev and kernel modules and could care less about having to
manually create every device node needed.
Mdev and kernel will do that automatically for me.
Best regards
Stefan
> Thanks!
>
next prev parent reply other threads:[~2012-10-05 17:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 14:42 [Buildroot] ALSA don't work Martin Peevski
2012-10-05 14:59 ` Stefan Fröberg
2012-10-05 15:34 ` Martin Peevski
2012-10-05 17:29 ` Stefan Fröberg [this message]
[not found] ` <50703E2A.5060702@ronetix.at>
[not found] ` <50704D34.2070002@petroprogram.com>
[not found] ` <50716DA7.4030200@ronetix.at>
[not found] ` <50716F47.1@ronetix.at>
2012-10-07 15:50 ` Stefan Fröberg
2012-10-08 11:44 ` Martin Peevski
2012-10-08 13:49 ` Stefan Fröberg
2012-10-08 14:38 ` Martin Peevski
2012-10-08 14:46 ` Stefan Fröberg
2012-10-09 10:52 ` Martin Peevski
2012-10-09 11:49 ` Stefan Fröberg
2012-10-10 14:52 ` Martin Peevski
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=506F18F6.5010506@petroprogram.com \
--to=stefan.froberg@petroprogram.com \
--cc=buildroot@busybox.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 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.