Re: [alsa-devel] [Alsa-user] Pc Speaker
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.
At Tue, 13 May 2008 13:14:38 +0200, Rene Herman wrote:
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).
Since snd-pcsp itself provides the input pcspkr functionality, it replaces the input pcspkr driver.
Anyway, the problem of beep on Dell XPS is a different. The PC beep isn't implemented (initialized) in the sound driver side. I have no interest in fixing it as I hate PC beep feature, but am willing to apply patches if provided :)
Takashi
On 13-05-08 13:20, Takashi Iwai wrote:
Yes, that would seem to be amazingly clumsily done. Perhaps there was a reason (adding alsa-devel).
Since snd-pcsp itself provides the input pcspkr functionality, it replaces the input pcspkr driver.
Ah. Yes, then it starts to make sense.
Anyway, the problem of beep on Dell XPS is a different. The PC beep isn't implemented (initialized) in the sound driver side. I have no interest in fixing it as I hate PC beep feature, but am willing to apply patches if provided :)
I suppose his beeper should stil beep through the input driver if he just selects "N" for snd-pcsp?
If not, if it worked before, and if I were him, I'd be throwing up a stink calling it a regression...
Rene.
On 13-05-08 13:32, Rene Herman wrote:
On 13-05-08 13:20, Takashi Iwai wrote:
Anyway, the problem of beep on Dell XPS is a different. The PC beep isn't implemented (initialized) in the sound driver side. I have no interest in fixing it as I hate PC beep feature, but am willing to apply patches if provided :)
I suppose his beeper should stil beep through the input driver if he just selects "N" for snd-pcsp?
If not, if it worked before, and if I were him, I'd be throwing up a stink calling it a regression...
(yes, I get it, not a regression, just jumped to the conclusion it was a changed situation due to the option juggling new to new kernels)
Not having the hardware, I'm not very likely to be useful but if the only problem is someone needing to turn available information into an addition to the driver, you can try me...
Rene.
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.
Rene Herman wrote, on 2008-05-23 06:16:
On 22-05-08 14:01, Arthur Marsh wrote:
under Debian unstable, by overwriting the unpacked Debian source tarball.
I'm afraid you lost me here. I have little clue about Debian.
Rene.
When one installs the "alsa-source" package on Debian and unpacks the resulting /usr/src/alsa-driver.tar.bz2 file, it ends up in a directory under /usr/src/modules.
Normally one would also have the kernel source unpacked into /usr/src/linux, then run:
make-kpkg --initrd linux-image modules-image
to compile a kernel and whatever modules packages were installed (e.g. ALSA)
I unpacked the Mercurial snapshot, then did a cp -r of the snapshot to the directory underneath /usr/src/modules where the alsa drivers were unpacked so that I could still use the Debian build process to compile the Mercurial snapshot of ALSA.
Arthur.
participants (3)
-
Arthur Marsh -
Rene Herman -
Takashi Iwai