"Daniel C. Sobral" wrote:
>
> "D. Rock" wrote:
> >
> > options HZ=500
>
> Without this line, do things work?
No, but I finally got an at least partial solution:
I had to configure to use DMA channels 1,0 (it used to be 1,5).
Even 0,1 didn't work. With this setup I was able to play music
Peter Wemm wrote:
> As to why the 1869 isn't working for you, that's anybody's guess. You
> might try posting the 'dmesg' output (not from syslog) and your complete
> config file, as well as any other pertinant information you can think of.
Ok
here is the (hopefully) complete information.
-curr
"D. Rock" wrote:
> "D. Rock" wrote:
> > > > Here my configuration:
> > > > device pcm0at isa? port 0x220 irq 5 drq 1 flags 0x15
> > >
> > > Err, the ESS1868 is a PNP device. You should only have "device pcm0" and
> > > nothing more. You might also try "options PNPBIOS". You are run
"D. Rock" wrote:
> > > Here my configuration:
> > > device pcm0at isa? port 0x220 irq 5 drq 1 flags 0x15
> >
> > Err, the ESS1868 is a PNP device. You should only have "device pcm0" and
> > nothing more. You might also try "options PNPBIOS". You are running
> > -current, right?
> W
Peter Wemm wrote:
>
> "D. Rock" wrote:
> > I read the last mails regarding problems with their ESS 1868 boards.
> > Well, at least it is partially working for them. I didn't have any
> > luck with the driver for some time now. I couldn't get a single tone.
> >
> > With the old voxware driver, sou
> I got the one email that said that there was some trouble with the ESS
> 1868 sound driver under FreeBSD-current. Is there an issue with -current
> and newpcm that is causing the 1868 sound driver to not work? Also, I'd
guys, you should realize that the ESS1868 codecs (and friends)
are extrem
I got the one email that said that there was some trouble with the ESS
1868 sound driver under FreeBSD-current. Is there an issue with -current
and newpcm that is causing the 1868 sound driver to not work? Also, I'd
like to know how to compile the newpcm sound driver as a loadable kernel
module,
"D. Rock" wrote:
> I read the last mails regarding problems with their ESS 1868 boards.
> Well, at least it is partially working for them. I didn't have any
> luck with the driver for some time now. I couldn't get a single tone.
>
> With the old voxware driver, sound worked at least partially
> (
Andrew Atrens writes:
>
> Here's how my card is currently detected -
>
> pcm0: at port
>0x220-0x22f,0x530-0x537,0x388-0x38b,0x330-0x331,0x370-0x371 irq 5 drq 0,1 on isa0
> Yamaha: ver 0x21 DMA config 0x84
> pcm: setmap 3, ff00; 0xc77e9000 -> 3
> pcm: setmap 4, ff00; 0xc77f
I read the last mails regarding problems with their ESS 1868 boards.
Well, at least it is partially working for them. I didn't have any
luck with the driver for some time now. I couldn't get a single tone.
With the old voxware driver, sound worked at least partially
(44.1 kHz, 8 Bit, mono), but w
> Luigi Rizzo <[EMAIL PROTECTED]> writes:
>
> > guys, you should realize that the ESS1868 codecs (and friends)
> > are extremely unfriendly to the programmer, and possibly
> > (according to Sanpei comments) broken in their handling of
> > auto-dma.
>
> ??
>
> I wouldn't say the interface is *pr
All,
I'm having trouble with my old Yamaha OPL based ISA soundcard. It used to
work flawlessly, but now as Don, I get `bursty' sound.
Most pronounced effect is when using `rvplayer'. If I open rvplayer and
click to play a sound clip everything is just peachy until I move the
mouse, causing a wi
On Thu, 4 Nov 1999, Luigi Rizzo wrote:
> guys, you should realize that the ESS1868 codecs (and friends)
> are extremely unfriendly to the programmer, and possibly
> (according to Sanpei comments) broken in their handling of
> auto-dma. As a consequence i cannot believe anyone wants to
> write a d
13 matches
Mail list logo
