Apologies for posting my question again. I would like to know if anyone else encountered this problem.
With ESS-1878 sound card, es18xx driver. In summary, using 'play' (so I assume native alsa drivers0 I get perfect sound. Addressing OSS directly I get more or less garbage, just white noise with a slight discernable sound. And I get theis noise with Realplayer8 and Realone (realplayer9). Any similar problems or solutions? Thanks Stuart -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 01 August 2002 08:54 To: [EMAIL PROTECTED] Subject: Re: [Alsa-user] problems with snd-ens1371, rewritten... Daniel, If I recall correctly, I have seen a message saying that doing a cat on any of the "devs" will not work. Doing the same on the emulated OSS devices is supported though. I was induced into the same error because of the mini-HOWTO I think this appeared on the developer's list. BTW, this list doesn't seem to have too much traffic, does it? HTH, Hugo Ferreira > > De: "daniel mouritsen" <[EMAIL PROTECTED]> > Data: 31/07/2002 18:39:14 > Para: <[EMAIL PROTECTED]> > Assunto: [Alsa-user] problems with snd-ens1371, rewritten... > > At Tue, 30 Jul 2002 03:33:33 -0700, > daniel mouritsen wrote: > > > > [1 <text/plain; iso-8859-1 (7bit)>] > > > > [2 <text/html (7bit)>] > > > > Hello everybody :) > > > > I have a problem getting my soundblaster 128PCI working, I used this > > card + the snd-ens1371 driver on a gentoo box with out problems. > > > > But after moving the card over into a slackware box, i cant seem to > > get it working. > > > > The wierdest thing though, is that modprobe snd-ens1371 SEEMS to > > work. Meaning: > > > > 1. lsmod shows ALL the nice alsa modules is loaded. > > 2. /proc/asound is created, and looks fine.. > > 3. /dev/snd is created, and looks fine.. (though, it looks like the > > permissions are not the permissions ive setup in devfsd.conf) > > > > But, if i try to access(cat files to them) any of my devices. Like > > /dev/snd/pcmC0D0c , > ^^^^^^^^^^^^^^^^^ > > don't do that. > > the ALSA pcm devices above are not designed to be accessed directly. > you need to use alsa-library to access pcm devices. it's correct > behavior to return these errors. > > you might say that you can do this on OSS: yes. OSS permits it. and > OSS emulation on ALSA supports it, too, but not ALSA native devices. > > > > i get alot of > > differnet errors: > > pcmC0D0c = File descriptor in bad state > > pcmC0D0p = Invalid argument > > midiC0D0 = input/output error > > > > I know i posted this question the other day to, but theres still no > > solution. What wonders me, is that other people seem to have had > > theise errors before(the only reply i got on my first was a guy who > > got the same errors), also on irc did i meet with a few people who > > had the same problems. Nobody had a fix though. > > could you elaborate what is exactly the problem? > otherwise no one can answer. > > > ciao, > > Takashi > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
