Hi,
I noticed that the snd-seq-oss module was giving unresolved symbol
errors when I tried to load it. The following patch fixes the problem.
Cheers,
Chris
--- alsa-driver/kernel/seq/seq.c.orig Fri Oct 19 13:10:15 2001
+++ alsa-driver/kernel/seq/seq.cWed Oct 24 12:38:31 2001
@@
Hi,
This patch fixes a build problem I was having with the latest CVS
version of ALSA and gcc 3.0.2. Specifically, the read_unlock
function, which is really a preprocessor #define, wasn't being
expanded within the snd_runtime_check() macros in mixer_oss.c.
Chris
---
Hi,
A little further study has revealed two additional facts here:
1) this happens with xine,
2) restarting X (logging out and logging back in again) releases the locks .
This would imply that somehow the ALSA devices are staying open, even
though the user-space processes have (apparently)
I'm sure; but I haven't installed a Desktop Environment yet. (It's on
my to-do list.)
There *really*, *really* isn't anything using the audio device.
Chris
On Wed, 10 Oct 2001, James Courtier-Dutton wrote:
I think you will find that X likes to play the odd wave file as you click on
the
Hi,
I've noticed that the ALSA modules have suddenly
gained GPL license tags. Unfortunately I think you
missed one: the snd-hwdep module.
Cheers,
Chris
__
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com
Hi,
My ALSA sound driver uses an MPU401 for MIDI support,
and the OSS emulation module snd-seq-oss works well
with the snd-mpu401-uart module. However, there are no
native ALSA sequencer devices:
[root@wittsend src]# cat /proc/asound/seq/clients
Client info
cur clients : 3
peak clients : 3
Hi,
I saw from the CVS ChangeLog that ALSA is moving away
from the deprecated virt_to_bus() to the new
pci_allocate_consistent() system calls. Unfortunately,
this is causing problems for my ISA DMA sound driver
(CS4231 / MPU401 based). I have currently fixed
things by #undef-ing the
--- pcm_memory.c.orig Sat Feb 16 14:30:29 2002
+++ pcm_memory.cSat Feb 16 15:43:13 2002
@@ -67,7 +67,7 @@
*addrp = isa_virt_to_bus(dma_area);
return dma_area;
}
-static inline void *snd_malloc_isa_pages_fallback(size_t size, dma_addr_t *addrp,
size_t *sizep, unsigned
--- Jaroslav Kysela [EMAIL PROTECTED] wrote:
Using pci_allocate_consistent() for ISA DMA
allocation routines is
definitely a bad idea. I added
snd_malloc_isa_pages() code as you
suggested to snd.o (it seems that it's good to
abstract such bus specific
allocation routines).
Thanks, my
--- Jaroslav Kysela [EMAIL PROTECTED] wrote:
I verified the contents of pci_allocate_consistent()
and I agree that it
should work at least for i386 and alpha
architectures so I reverted back
your code.
Hi,
I have ported my driver to use the new
snd_malloc_isa_pages() call ... and my
--- Jaroslav Kysela [EMAIL PROTECTED] wrote:
I removed dma_flags from isa pages allocation
routines. We use
GFP_ATOMIC|GFP_DMA like pci_allocate_consistent().
Interesting ... my original and working code did the
following:
buf = snd_malloc_pages(size, GFP_KERNEL | GFP_DMA);
and then used
Hi,
I have noticed this deadlock before and had attributed it to having
compiled the ALSA modules with gcc-3.0.4. However, it has just
happened again and I am no longer certain that gcc is responsible. I
was able to rescue the box by killing either the wine or the aplay
process - I'm not sure
Hi,
I just tried to totally rebuild the latest alsa-driver
modules from CVS, and I'm getting this error when I
try to generate the dependencies:
gcc -E -M -DALSA_BUILD -D__KERNEL__ -DMODULE=1
-I/home/chris/Programs/alsa/alsa-driver/include
-I/lib/modules/2.4.18/build/include -O2
Hi,
I am having trouble compiling the OSS-emulation modules for the CVS
ALSA sequencer. Part of the trouble seems to be that the Makefiles
expect CONFIG_SND_SEQUENCER_OSS to be 'y' instead of 'm'; specifically
in
alsa-kernel/core/seq/oss/Makefile
alsa-kernel/synth/emux/Makefile
However, I
Hi,
According to the ALSA web site, the mailing lists are
on alsa-project.org. However, this mailing list is on
lists.sourceforge.net. Could this explain why some of
my posts have never appeared? If so, maybe the website
could be updated?
Cheers,
Chris
Does this mean that the alsa-lib needs to be updated in CVS to be -rc4?
I am trying to compile xine and wine from CVS as well as ALSA, and this
doesn't work because alsa-utils needs the new headers but xine and wine
currently need the old ones. I imagine that the xine and wine people can
--- Jaroslav Kysela [EMAIL PROTECTED] wrote: On Wed,
18 Sep 2002, Chris Rankin wrote:
Note: If
SND_COMPATIBILITY_BUILD_RC3 is defined,
then applications need to fall back to 0.9.0rc3 API
as well.
So maybe we could have a --with-compat-rc3 option for
alsa-utils as well? Regardless of which
--- Jaroslav Kysela [EMAIL PROTECTED] wrote: On Wed,
18 Sep 2002, [iso-8859-1] Chris Rankin
wrote:
It seems, that you're not understand the
compatibility.
That's possible - or maybe the existing
compatibility is woefully inadequate for the scale
of the problem?
The applications that I am
--- Chris Rankin [EMAIL PROTECTED] wrote: ---
Jaroslav Kysela [EMAIL PROTECTED] wrote: On
The possible solutions from my perspective are:
- I install BOTH libraries, each with full headers
(somehow)
Oh yes, and the compatibility version has to go in
/usr because that's where the rest
Hi,
I have installed the brand new libasound.so.2 and
compiled the CVS alsa-utils against it. However, the
new aplay binary just hangs and does not make any
sound. The old aplay works against the new
libasound.so.2 just fine.
Chris
__
Do You
Hi,
[Linux 2.4.19-SMP, SB Live!, alsa-lib CVS, alsa-utils
rc3]
I have just tried to play a WAV file on my machine,
but have triggered these errors instead. The machine
didn't crash, fortunately, but it's very irritating to
have memory problems on a 1 GB machine:
$ aplay
On Friday 20 September 2002 20:18, Chris Rankin wrote:
I have installed the brand new libasound.so.2 and
compiled the CVS alsa-utils against it. However, the
new aplay binary just hangs and does not make any
sound. The old aplay works against the new
libasound.so.2 just fine.
--- Jaroslav
Hi,
With the latest changes to pcm.h and pcm.c, the CVS
version of aplay now works OK, thanks. However, the
CVS alsamixer seems to be displaying its graphics
incorrectly. Some of the columns (with the SB Live!
card) have no numbers underneath them, and the Mic
Select and Mono Output Select
--- Jaroslav Kysela [EMAIL PROTECTED] wrote:
Note that these controls are enumerated (it's a list
of available
options). If you have an idea for better
representation, let us know.
Eh? I am merely pointing out that the alsamixer-CVS
display looks different to the alsamixer-rc3 display.
My
--- Takashi Iwai [EMAIL PROTECTED] wrote:
At Mon, 16 Sep 2002 22:58:34 +0100 (BST),
is yours the vanilla kernel?
Yes, I compiled it myself using vanilla source.
(2.4.19, SMP, HighMem, SB Live!)
i still don't figure out which part of the last
change of pci_alloc_consistent hack affects it.
Hi,
I saw the SoundScape PnP driver appear in CVS today,
along with a number of FIXMEs at the top of the file.
I presume that these FIXMEs are a barrier to fully
integrating the driver, and that's what you mean by
deadlock for alsa-kernel?
Anyway:
- the CONFIG_SND_OSSEMUL dependency was a
--- Takashi Iwai [EMAIL PROTECTED] wrote: At Sun, 22
Sep 2002 20:09:52 +0100 (BST),
i don't think so. more modulalization doesn't mean
to remove the
ability of built-in drivers. (and i heard that
Linus still prefers
built-in drivers to modules :)
I definitely hadn't heard that! I
--- Takashi Iwai [EMAIL PROTECTED] wrote: At Mon, 23
yes, but it should not be the reason to stop
compiling the built-in
driver via ifdef.
Well, it would be more accurate to say that the
built-in code wasn't a priority. I was also hoping
that Linux 2.5+ would make the entire problem go
/driver.h
#include linux/init.h
+#include linux/delay.h
#include linux/isapnp.h
#include linux/spinlock.h
#include asm/dma.h
@@ -42,10 +42,6 @@
#define chip_t cs4231_t
-#ifndef CONFIG_SND_OSSEMUL
-# error Need ALSA configuration!
-#endif
-
EXPORT_NO_SYMBOLS;
MODULE_AUTHOR(Chris Rankin
This quick patch should make the sscape_ctl utility slightly more user-friendly.
Chris
Index: sscape_ctl.c
===
RCS file: /cvsroot/alsa/alsa-tools/sscape_ctl/sscape_ctl.c,v
retrieving revision 1.1
diff -u -u -r1.1 sscape_ctl.c
---
Hi,
I can't dispute this section of Takashi's patch, except to note that
you probably don't want to clobber buf-size if the snd_xxx_fallback()
function sets it properly for you.
Chris
Index: alsa-driver/isa/sscape.c
===
RCS file:
Hi,
I have finally managed to build the alsa-lib and alsa-utils RPMs on my test machine,
having upgraded to
RedHat 7.3. The highlights of this patch are:
- the Versions linker script was not being tarred up
- using $(AMTAR) instead or $(TAR) in the Makefile.am
- using -j instead of -I to
Hi,
I have modified the SoundScape (proto-)driver to use the typesafe Linux min() macro,
defining
the macro if it hasn't been declared already. (This is compatibility for Linux 2.2.)
In fact, it turns
out that both min() and ARRAY_SIZE() are declared in include/linux/kernel.h and so I
suppose
Now that the ARRAY_SIZE macro has been migrated to adriver.h, it can come out of here.
And there's a whitespace diff too.
Chris
Index: alsa-driver/isa/sscape.c
===
RCS file: /cvsroot/alsa/alsa-driver/isa/sscape.c,v
retrieving
--- Jaroslav Kysela [EMAIL PROTECTED] wrote: On Tue,
8
alsa-module-name=snd_this=x,snd_that=y,snd_the_other=z
No, it should be: alsa-module-name=x,y,z . The
prefix for alsa-module-name
is required, because we have collisions with OSS
drivers.
I'm not talking about snd on the
Hi,
I have been hacking on the SoundScape driver again, and have now added support for the
following
module parameters (assuming no snd_ prefix):
index
id
port
irq
mpu_irq
dma
I haven't added the second DMA channel in yet because the driver couldn't do anything
with it
even if I did. Anyway,
limitation?
Chris
--- Takashi Iwai [EMAIL PROTECTED] wrote: Hi,
At Sun, 27 Oct 2002 18:05:41 + (GMT),
Chris Rankin wrote:
Hi,
The 'cannot allocate memory' problem has returned
on
my machine:
(snip)
$ free -t
total used free
shared
--- Takashi Iwai [EMAIL PROTECTED] wrote: At Mon, 28
Oct 2002 13:21:48 + (GMT),
could you try the attached patch?
as mentioned in my previous mail, this is really a
hack, but if it
works...
My box has obviously released some memory overnight
and is working again. I'll try the patch as
Hi,
I downloaded and installed today's CVS ALSA and the
following happened:
- no sound when using aplay
- complete X-server lockup when trying to load OSS
emulation modules. (Machine still pingable, though.)
On reboot, the same thing happened except this time I
received an oops. (Attached.) I
Hi,
Here is what my /proc/asound directory looks like with
the latest ALSA CVS:
$ ls -als /proc/asound/
total 0
0 dr-xr-xr-x7 root root0 Nov 3
15:38 .
0 dr-xr-xr-x 111 root root0 Oct 30
23:08 ..
0 lrwxrwxrwx1 root root0 Nov 3
Hi,
My box has now accumulated almost 3 weeks of uptime,
and so the ALSA memory problem is back again:
$ aplay /usr/lib/sounds/jungle_exit.wav
Playing WAVE '/usr/lib/sounds/jungle_exit.wav' :
Signed 16 bit Little Endian, Rate 22050 Hz, Stereo
ALSA lib pcm_hw.c:297:(snd_pcm_hw_hw_params)
];
va_list args;
Cheers,
Chris
--- Jaroslav Kysela [EMAIL PROTECTED] wrote: On Sat,
23 Nov 2002, [iso-8859-1] Chris Rankin
wrote:
Hi,
I am having problems with the latest ALSA CVS
using
Linux 2.4.19-SMP and devfs. Specifically:
# depmod -ae
depmod: *** Unresolved symbols
Hi,
I am having problems with the latest ALSA CVS using
Linux 2.4.19-SMP and devfs. Specifically:
# depmod -ae
depmod: *** Unresolved symbols in
/lib/modules/2.4.19/kernel/drivers/sound/snd.o
depmod: devfs_remove
Cheers,
Chris
__
Do You
Hi,
Remind me to NEVER try and update two systems at the
same time again! I have compiled Linux 2.4.20 for my
SMP box with very latest ALSA CVS modules. However,
2.4.20 deadlocked when I rebooted it and needed
rescuing by the NMI watchdog.
Unfortunately, I have not tried these ALSA modules
with
--- Jaroslav Kysela [EMAIL PROTECTED] wrote:
Could you try the current CVS? Hopefully, I fixed
the problem.
Just one small spelling mistake ;-)
Index: alsa-kernel/core/control.c
===
RCS file:
Hi,
I was compiling the ALSA CVS drivers this evening when
I saw this compiler warning whizz past. I think that
this lock is a spinlock and not a rwlock.
Cheers,
Chris
Index: alsa-kernel/core/init.c
===
RCS file:
Hi,
I think you missed one ;-) ...
Cheers,
Chris
Index: alsa-kernel/core/init.c
===
RCS file: /cvsroot/alsa/alsa-kernel/core/init.c,v
retrieving revision 1.24
diff -u -u -r1.24 init.c
--- alsa-kernel/core/init.c 8 Dec 2002
Hi,
I have just installed the latest ALSA-CVS and I have
noticed a few oddities:
First, these modules are suddenly being compiled. I
don't know why:
snd-emu8000-synth.o
snd-gus-synth.o
snd-trident-synth.o
This is my /etc/astate/driver_args:
# cat /etc/asound/driver_args
--- Takashi Iwai [EMAIL PROTECTED] wrote:
At Thu, 30 Jan 2003 00:11:00 + (GMT),
does the attached patch have any influence?
Nope, the clicks are still there.
Chris
__
Do You Yahoo!?
Everything you'll ever need on one web page
from News and
--- Takashi Iwai [EMAIL PROTECTED] wrote:
do you know which version (or date) the driver
worked without clicks?
there have been not many changes for emu10k1 or pcm
stuffs recently.
On a hunch, I downloaded the alsa-lib-0.9.0rc6 and
alsa-util-0.9.0rc6 packages and tried those against
the
Speaking as a userspace developer, I expect file
descriptors to be inherited by child processes unless
I explicitly request otherwise. Yes, I usually make
sure that I *DO* request otherwise, but that's not the
point...
Cheers,
Chris
--- Takashi Iwai [EMAIL PROTECTED] wrote: At Wed, 5
Feb 2003
Fair enough, but my point is that I'd expect the
close-on-exec flag NOT to be set unless I explicitly
set it myself. Same as with every other way of getting
a file descriptor.
Chris
--- Paul Davis [EMAIL PROTECTED] wrote:
Speaking as a userspace developer, I expect file
descriptors to be
--- Sebastian Kapfer [EMAIL PROTECTED] wrote:
May I ask what the child process is supposed to to
with a raw ALSA file
descriptor? AFAICT, developers are supposed to use
the alsa-lib API, and
not write to FD's. So the underlying file descriptor
looks to me like a
mere implementation detail
--- Takashi Iwai [EMAIL PROTECTED] wrote:
could you try the latest cvs aplay.c?
That's solved the clicking problem. I'll need to
update the ALSA on my P120 to run further checks.
That's a Friday / weekend job.
Chris
__
Do You Yahoo!?
Everything
--- Sebastian Kapfer [EMAIL PROTECTED] wrote:
I can find a use for stdio FD's
in the new process either. The exec'd process can't
even know which FD corresponds to which file.
I'm assuming from the context of your message that you
meant CAN'T find a use ... either. But the whole
point of a
--- Paul Davis [EMAIL PROTECTED] wrote:
there's a little detail you're forgetting. unless
the hw supports multi-open and the current number of
subunits is below the limit of the number of opens,
then having the descriptor will cause all other
attempts to access the device to block (unless
--- Paul Davis [EMAIL PROTECTED] wrote:
not clearly so. there are very few resources
accessed via a file
descriptor that require this being done.
You think? Try unmounting a filesystem or unloading
the ide-cd kernel module if (say) xscreensaver has
been spawned by (say) xine, but xine has
--- Sebastian Kapfer [EMAIL PROTECTED] wrote:
Setting FD_CLOEXEC automatically doesn't make the
library less powerful.
You can still unset the flag yourself __if you
really need the feature__
of inherited ALSA FD's. But wouldn't FD_CLOEXEC be
the reasonable
default setting, which is
--- Takashi Iwai [EMAIL PROTECTED] wrote:
i don't think it's a bug of the alsa-lib, too.
it's a bug of mplayer. mplayer should be fixed.
period.
Hooray! ;-)
but, the problem is that this kind of bugs can be
rarely found (nor appear).
I found lsof to be a most useful tool.
on the
Hi,
I have just tried loading a sound-font file into my SB
Live! and ended up needing to reboot my machine when
the sfxload program grabbed hold of the CPU and
wouldn't give it back! Fortunately the machine is SMP,
and so I was able to shutdown cleanly using the other
one.
I think the problem
I don't have jack installed either, reran the
cvscompile script in alsa-lib and *still* had a build
failure. Sounds like a bug to me. There's no reason
ALSA should expect to find jack.
Chris
--- Jaakko Prättälä [EMAIL PROTECTED]
wrote: On Friday 07 March 2003 00:10, Martin Langer
wrote:
Hi,
I have just tried to compile the latest alsa-driver
from CVS and was surprised to see lots of
vmalloc_to_page redefined warnings. A quick check
showed that 2.4.20 does define vmalloc_to_page(), but
that ALSA was trying to provide a compatibility
function anyway.
The problem seems to be in
__
Yahoo! Plus
For a better Internet experience
http://www.yahoo.co.uk/btoffer
---
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
Hi,
I understand why you are insisting that people compile the ALSA modules with the same
compiler that they used
to compile the kernel. However, I think that there are still some issues to work out:
checking for GCC version... Kernel compiler: gcc 2.96 2731 (Red Hat Linux 7.3
2.96-112)
Hi,
These breakages have existed for a day or two.
In alsa-driver:
gcc -D__KERNEL__ -DMODULE=1
-I/home/chris/Programs/alsa/alsa-driver/include
-I/home/chris/linux-2.4.21/include -O2
-mpreferred-stack-boundary=2 -march=i686 -D__SMP__
-DCONFIG_SMP -DLINUX -Wall -Wstrict-prototypes
--- Nicola Orru' [EMAIL PROTECTED] wrote:
It looks like a typo. Try and open emufx.c and
replace EMU10K1_GRP_* with EMU10k1_GPR_*.
Yup, a typo. Changing .._GRP_.. to .._GPR_.. fixed it.
Cheers,
Chris
P.S. alsa-lib is still broken, though.
--- Antti Boman [EMAIL PROTECTED] wrote:
Ok, there's a difference compared to my problem. My
computer locks up
within a couple of seconds. So, obviously we're not
talking about the
same problem. Also, I have to install newer ALSA and
JACK to see if the
lock-up is still there.
That's
Hi,
I have just downloaded the latest ALSA from CVS and
suddenly all my WAV files have this loud CLICK! sound
at the end. I'm not entirely sure what is going on but
I have tried downloading various versions of aplay.c
from CVS and the problem doesn't seem to be present
with aplay. 1.170 or 1.171.
Want to chat instantly with your online friends? Get the FREE Yahoo!
Messenger http://mail.messenger.yahoo.co.uk
---
This sf.net email is sponsored by:ThinkGeek
Hi,
I'm not entirely sure why this change was made because the microcode structure was
never being copied
onto the kernel stack. However, there is certainly no need for the magic number of
65536 to be included
everywhere. There was also a compiler warning in the sscape_ctl tool.
Cheers,
Chris
Hi,
I have just installed ALSA CVS on my Linux 2.4.22 box,
and suddenly the PCM playback has gone silent. I know
my speakers are on because I can play CDs, and the OSS
emu10k1 driver still works too so it can't be the
hardware.
Interestingly, the alsa-driver-0.9.7c.tar.bz2 package
is also OK.
--- Takashi Iwai [EMAIL PROTECTED] wrote:
if it's an audigy board, the mixer routing was
rewritten on the cvs version. you'll need to adjust
'Front' in addition to 'Master' and 'PCM'. (and
'Wave'
is gone.)
It isn't an audigy board, it's an SB-Live! (rev. 7). I
still have a 'Wave' device
The alsa-kernel/core/sound.c file references the
linux/device.h header file, but this header does not
exist under Linux 2.4.
Deleting the reference fixes the build.
Cheers,
Chris
Want to chat instantly with your online
Hi,
I've been noticing this for weeks, and it's still
present in 1.0.0-pre1 (fresh from CVS): using
RealPlayer v8 with OSS emulation, the sound is now
several seconds behind the pictures. I haven't touched
my RealPlayer installation, and there is no such delay
if I use the native OSS drivers
Hi,
I have just noticed these errors in my console log
(with the few line immediately before):
Feb 11 20:01:58 twopit kernel: PCI: Setting latency
timer of device :00:1f.5 to 64
Feb 11 20:01:59 twopit kernel:
intel8x0_measure_ac97_clock: measured 49371 usecs
Feb 11 20:01:59 twopit kernel:
[Linux 2.6.3-SMP, single 933 MHz PIII, 1 GB RAM,
devfs, gcc-3.2.3]
Hi,
I have just installed the latest ALSA from CVS and
discovered that it has broken PCM playback. This is
what aplay gives me now:
$ aplay /usr/lib/sounds/jungle_exit.wav
Playing WAVE '/usr/lib/sounds/jungle_exit.wav' :
Signed
--- Jeremy Hall [EMAIL PROTECTED] wrote: Hello,
I just did a cvs update -dP on my CVS because I was
experiencing lockups
when using intel8x0 and my drivers were a bit old.
When I had finished running ./cvscompile in
alsa-driver, alsa-lib, and
alsa-tools along with appropriate make
Hi,
ALSA CVS is still failing to generate all of dependent
modules in my particular config:
--with-kernel=/home/chris/linux-2.6.4
--with-moddir=/lib/modules/2.6.4/kernel/sound
--with-oss=yes
--with-sequencer=yes
--with-cards=intel8x0,emu10k1,dummy
I have managed to hack the (generated)
78 matches
Mail list logo
