Some interrupt bogons still around.

1999-05-12 Thread Stephen Hocking-Senior Programmer PGS Tensor Perth
An old 486 of mine still cant see its IDE driver with versions of ata-all.c 
later than 1.8, and my soundcard (PAS16) still doesn't seem to generate 
interrupts since the nexus stuff went in.


Stephen
-- 
  The views expressed above are not those of PGS Tensor.

"We've heard that a million monkeys at a million keyboards could produce
 the Complete Works of Shakespeare; now, thanks to the Internet, we know
 this is not true."Robert Wilensky, University of California




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message



Re: Some interrupt bogons still around.

1999-05-12 Thread Alfred Perlstein
On Thu, 13 May 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote:

> An old 486 of mine still cant see its IDE driver with versions of ata-all.c 
> later than 1.8, and my soundcard (PAS16) still doesn't seem to generate 
> interrupts since the nexus stuff went in.

my stock SB16 + freebsd+x11amp hasn't worked right since newbus.

sound skips quite a bit.



-Alfred




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message



Re: Some interrupt bogons still around.

1999-05-13 Thread Jake Burkholder
> 
> my stock SB16 + freebsd+x11amp hasn't worked right since newbus.
> 
> sound skips quite a bit.
> 
> 
> 

I noticed the same thing.  /usr/ports/audio/gqmpeg is a nice player
which uses mpg123 as the backend; it plays fine.  I think it may have 
just have something to do with x11amp, which should probably be considered
a bogon itself.  All other sources of sound work fine, like fxtv.

(I have the same sound card as you; pcm driver.)

Jake
-- 
Linux - Zealotry taken over the Edge




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message



Re: Some interrupt bogons still around.

1999-05-13 Thread Chris Csanady

>> 
>> my stock SB16 + freebsd+x11amp hasn't worked right since newbus.
>> 
>> sound skips quite a bit.
>> 
>> 
>> 
>
>I noticed the same thing.  /usr/ports/audio/gqmpeg is a nice player
>which uses mpg123 as the backend; it plays fine.  I think it may have 
>just have something to do with x11amp, which should probably be considered
>a bogon itself.  All other sources of sound work fine, like fxtv.

Really?  mpg123 and fxtv are broke for me.  Have you tried using fxtv to
capture audio and then play it back?  I haven't tried it in a while, but
they both acted like x11amp with regard to the "skipping."  x11amp still
does not work right for me though..

This is on different audio hardware as well..

Chris




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message



Re: Some interrupt bogons still around.

1999-05-13 Thread Eric L. Hernes
Jake Burkholder writes:
>> 
>> my stock SB16 + freebsd+x11amp hasn't worked right since newbus.

mine either, 'til I switched from pcm back to the voxware stuff.
Then it magically worked ok.

>
>I noticed the same thing.  /usr/ports/audio/gqmpeg is a nice player
>which uses mpg123 as the backend; it plays fine.  I think it may have 
>just have something to do with x11amp, which should probably be considered
>a bogon itself.  All other sources of sound work fine, like fxtv.

A lot of other mp3 decoders worked OK, but x11amp didn't.  I spend some time
looking at x11amp in and out plugins.  The in/out parts of x11amp ain't
exactly textbook threaded code ;-) mostly spinloops and sleeps :(  I
half re-wrote the OSS plugin with real cond-vars and mutexes,
but still skipped... Then I tried the old voxware code, and now it
only skips when the process is CPU starved.  I could prolly fix that
by giving the process a slight rtprio... but it hasn't been irritating
enough yet.

>
>Jake
>-- 
>Linux - Zealotry taken over the Edge
>
>

Eric

-- 
Eric L. Hernes
er...@lodgenet.com





To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message