Am Mittwoch, 7. November 2001 22:33 schrieb Anders Torger:
> On Wednesday 07 November 2001 23.18, you wrote:
> >
> > 1.) alsa-oss-0.9.0beta9 fails to compile with:
> > make: *** No rule to make target `aoss.in', needed by `aoss'. Stop.
> > Is aoss.in missing in the tar-ball, or am I doing something wrong? Well,
> > I ignored this for now, since native ALSA apps shouldn't be affected,
> > right?
> >
> > 2.) The card, driver and library seems to be up and running, but I have
> > strange problems with applications:
> >
> > a) aplay and arecord work sometimes, but not always. When failing, aplay
> > ...
> >
> > b) I tried to run the latencytest, but it constantly fails, eighter with
> > test # ./latency -m 8192 -M 8192 -t 1 -p -r 44100
> > ...
> >
> > c) The sine generator and amixer run and work fine.
> >
> > I'm confused. What more info can I give to narrow down the problem?
>
> Hmmm... strange... I use the driver almost every day, and I have not seen
> any problems. I also wrote the driver, but it has been some time since I
> looked at it last, and I don't have an entirely fresh ALSA copy myself.
> Unfortunately I will not be able to look into this until next weekend.
> Perhaps some other user of the card could report on this?
Problem 1) is solved, I took the missing parts from CVS and installed
the oss-layer.
To narrow down problem 2a), I ran alsaconf and selected the onboard
sound (via chipset) instead of the RME. With that, too, I encounter
situations where aplay and/or arecord cannot access the device.
So this seems to be a problem of the library, not the driver?
Or could it be that some other application lock the device? I'm running
nothing special, plain SuSE 7.3 with KDE. I took the dummy-library
libasound.so.1 from ftp.suse.com/pub/people/tiwai/alsa9-packages/ to
stop all alsa-0.5-apps from interfering. Am I missing something?
Concerning problem 2b): Here the RME96-driver seems to make
troubles. Using the via-chipset, I can run "latency" fine. Using the
RME DIGI96, it eigther fails to open the device as described, or dumps
a segmentation fault. gdb gives:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 2932)]
0x4014f111 in chunk_alloc () from /lib/libc.so.6
(gdb) bt
#0 0x4014f111 in chunk_alloc () from /lib/libc.so.6
#1 0x4014ef64 in malloc () from /lib/libc.so.6
#2 0x400d166a in rwlock_add_to_list () from /lib/libpthread.so.0
#3 0x400d17ea in rwlock_have_already () from /lib/libpthread.so.0
#4 0x400d1901 in pthread_rwlock_rdlock () from /lib/libpthread.so.0
#5 0x401045da in __dcigettext () from /lib/libc.so.6
#6 0x401044cd in dcgettext () from /lib/libc.so.6
#7 0x40103a2d in __assert_fail () from /lib/libc.so.6
#8 0x4004615c in snd_pcm_writei (pcm=0x804fbd0, buffer=0x804d8d0, size=8192)
at pcm.c:419
#9 0x0804a644 in writebuf (handle=0x804fbd0, buf=0x804d8d0 "", len=8192,
frames=0xbffff364) at latency.c:363
#10 0x0804b271 in main (argc=4, argv=0xbffff4f4) at latency.c:606
#11 0x400f87ee in __libc_start_main () from /lib/libc.so.6
(gdb) frame 8
#8 0x4004615c in snd_pcm_writei (pcm=0x804fbd0, buffer=0x804d8d0, size=8192)
at pcm.c:419
419 assert(pcm->setup);
Any clues?
Thanks for your patience,
Wolfgang
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
