robert i don't have very good mail access right now, because i just lost 2 motherboards (i'm writing this from an ssh session from my girlfriends windows box. however, 2 things:
your question about lockups doesn't really contain enough information. are you running with SCHED_FIFO? are you accessing both playback and capture streams? what else does your code do? about memory allocation: yes, after running fsck, even with 512MB, there is normally/frequently not enough *contiguous* RAM for the hammerfalls. you need to ensure that the memory allocation module (snd-rme9652-mem in the latest alsa) is installed *very* early in your system's startup. how best to do that varies depending on which linux system you have; on my RH-derived systems, i load that module from rc.sysinit, before anything else happens, and then i never get failures. on windows/macos, the driver gets loaded at an equivalently early point; under linux, with modular drivers, its an extra step to make sure the memory allocation happens "early" - this is the tradeoff with modular drivers. if you compile the rme9652 driver (and alsa) into the kernel, this problem would go away, but i don't like building anything but the core drivers into my kernels. oh, and that "defective" hammerfall almost certainly had an M52 EPROM rather than an W52 EPROM, hence the reversed byte-order (its for big endian systems like the macs). my email access will continue to be poor for several days. --p _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
