Re: AWE64 problems

1999-12-09 Thread Frank Nobis
On Thu, Dec 09, 1999 at 12:25:33PM +0900, Seigo Tanimura wrote: > [snipped some part] > >> > > On Tue, 7 Dec 1999 23:00:02 +0100 (MET), > >> > > Thomas Schuerger <[EMAIL PROTECTED]> said: > >> > > > >> > > >> --- sbc.c.orig Mon Dec 6 19:26:31 1999 > >> > > >> +++ sbc.c Tue Dec 7 22:15:

Re: AWE64 problems

1999-12-08 Thread Seigo Tanimura
[snipped some part] >> > > On Tue, 7 Dec 1999 23:00:02 +0100 (MET), >> > > Thomas Schuerger <[EMAIL PROTECTED]> said: >> > > >> > > >> --- sbc.c.origMon Dec 6 19:26:31 1999 >> > > >> +++ sbc.c Tue Dec 7 22:15:25 1999 >> > > >> @@ -110,7 +110,7 @@ >> > > >> if (error) >> > > >> ret

Re: AWE64 problems

1999-12-08 Thread Charles Anderson
So then what is -1 and why does it work when -100 doesn't? (I tried it) -Charlie On Tue, Dec 07, 1999 at 09:13:41PM -0800, Mike Smith wrote: > > I looked for some meaning to the -100, is this documented somewhere? > > It's not, yet. We should move to using some defines for this. > A while back

Re: AWE64 problems

1999-12-07 Thread Mike Smith
> I looked for some meaning to the -100, is this documented somewhere? It's not, yet. We should move to using some defines for this. A while back I proposed something like: #define DEVICE_MATCH_EXACT -100 #define DEVICE_MATCH_CLASS -200 #define DEVICE_MATCH_GENERIC-300 The 'exact

Re: AWE64 problems

1999-12-07 Thread Charles Anderson
I looked for some meaning to the -100, is this documented somewhere? Who calls it? -Charlie On Wed, Dec 08, 1999 at 11:30:46AM +0900, Seigo Tanimura wrote: > On Tue, 7 Dec 1999 23:00:02 +0100 (MET), > Thomas Schuerger <[EMAIL PROTECTED]> said: > > >> --- sbc.c.orig Mon Dec 6 19:26:31 19

Re: AWE64 problems

1999-12-07 Thread Seigo Tanimura
On Tue, 7 Dec 1999 23:00:02 +0100 (MET), Thomas Schuerger <[EMAIL PROTECTED]> said: >> --- sbc.c.orig Mon Dec 6 19:26:31 1999 >> +++ sbc.cTue Dec 7 22:15:25 1999 >> @@ -110,7 +110,7 @@ >> if (error) >> return error; >> else >> -return -100; >> +return -1; >>

Re: AWE64 problems

1999-12-07 Thread Thomas Schuerger
> > I am still having problems getting my AWE64 soundcard to > > work with the newpcm driver (the "old" pcm driver worked > > fine). > > > > Any ideas what I am doing wrong? Are there more people > > having problems with their AWE64? > > I had the same problem with my AWE64. An older kernel > @(

Re: AWE64 problems

1999-12-07 Thread Frank Nobis
On Tue, Dec 07, 1999 at 06:43:55PM +0100, Thomas Schuerger wrote: > Hi! > > I am still having problems getting my AWE64 soundcard to > work with the newpcm driver (the "old" pcm driver worked > fine). > > Any ideas what I am doing wrong? Are there more people > having problems with their AWE64?

Re: AWE64 problems

1999-12-07 Thread Charles Anderson
I hate me too messages, but I'm having problems too. Exact same symptoms. I looked at sbc.c and it has the correct logical id, I spent some time looking at this last night, but was stymied by my lack of understanding of how the pnp system works. I even tried it with PNPBIOS defined, but that di

Re: AWE64 problems

1999-12-07 Thread Kenneth Wayne Culver
Actually, I'm having the same problem with my Soundblaster ViBRA16X. It seems that for some reason the sbc driver is not working right. = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator

AWE64 problems

1999-12-07 Thread Thomas Schuerger
Hi! I am still having problems getting my AWE64 soundcard to work with the newpcm driver (the "old" pcm driver worked fine). I have updated the world last week and am using the kernel as of today. I'm using the "pcm0" and "sbc0" devices in my kernel options. My card is recognized correctly, but n