From: Arthur Marsh <arthur.marsh@internode.on.net>
Cc: alsa-user@lists.sourceforge.net, alsa-devel@alsa-project.org
Subject: Re: Pc Speaker
Date: Thu, 22 May 2008 21:31:55 +0930 [thread overview]
Message-ID: <483560B3.70204@internode.on.net> (raw)
In-Reply-To: <4829781E.6040909@keyaccess.nl>
Rene Herman wrote, on 2008-05-13 20:44:
> On 13-05-08 12:44, Armin ranjbar wrote:
>
>>> Device Drivers ->
>>> Input device support ->
>>> Miscelaneous devices
>>>
>>> With current mainline, it's:
>>>
>>> General setup ->
>>> Configure standard kernel features (for small systems)
>>> Enable PC-Speaker support
>> Thank you very much for your reply ,
>>
>> but i have to say that i have this options activated , still no pc
>> speaker .
>
> Rechecked. Yes, you need this option, you need the ALSA one disabled (not
> modular, disabled) and then the PC speaker driver option appears in its
> input menu where you want to enable it. Paths as given in last reply.
>
> Yes, that would seem to be amazingly clumsily done. Perhaps there was a
> reason (adding alsa-devel).
>
> Rene.
Thanks for the clues. I attempted to compile a recent snapshot of
alsa-driver from
ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/alsa-driver-hg20080516.tar.bz2
under Debian unstable, by overwriting the unpacked Debian source tarball.
The catch is that the Debian build information set up by
dpkg-reconfigure alsa-source
(which is stored in /etc/alsa/alsa-source.conf)
is out of sync with the Mercurial snapshot and by compiling "all" ALSA
drivers, I get the ALSA pcspkr driver installed, which causes some problems.
I'd probably need to hack /etc/alsa/alsa-source.conf based on the
drivers supported by the Mercurial snapshot *minus* pcspkr to build an
alsa-driver .deb based on the Mercurial snapshot.
Arthur.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-05-22 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080513110322.030a5386.zoup@zoup.org>
[not found] ` <48296CFF.5000207@keyaccess.nl>
[not found] ` <20080513151425.448369e8.zoup@zoup.org>
2008-05-13 11:14 ` [Alsa-user] Pc Speaker Rene Herman
2008-05-13 11:20 ` Takashi Iwai
2008-05-13 11:32 ` Rene Herman
2008-05-13 12:25 ` Rene Herman
2008-05-22 12:01 ` Arthur Marsh [this message]
2008-05-22 20:46 ` Rene Herman
2008-05-22 23:54 ` Arthur Marsh
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=483560B3.70204@internode.on.net \
--to=arthur.marsh@internode.on.net \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-user@lists.sourceforge.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