recomended Alsa version for an AWE64?

recomended Alsa version for an AWE64?

[Adam Myrow]

Well, hearing how once people get it working, everybody seems to be quite
pleased with Alsa, I've been trying to get it to compile.  I am using
Slackware Linux with kernel 2.4.19 and trying to build Alsa 0.9.0-RC3.
The drivers aren't compiling and giving a string of errors having to do
with conflicting definitions and such.  I am trying to use a Soundblaster
AWE64.  I know that this card has been around for awhile so I was thinking
that maybe an older version would be more likely to build.  Is there a
particular version that is known to work well with this card?  Otherwise,
I can provide the rather long list of warnings and errors I am getting and
go from there.  I'm doing this so I can use full duplex with Speak Freely.
I had found a hack to sort of get full duplex to work with the kernel
drivers, but it would generate a lot of record overrun errors and lengthy
pauses.  Any ideas welcome.

Re: recomended Alsa version for an AWE64?

[Toby Fisher]

On Tue, 15 Oct 2002, Adam Myrow wrote:

> Well, hearing how once people get it working, everybody seems to be quite
> pleased with Alsa, I've been trying to get it to compile.  I am using
> Slackware Linux with kernel 2.4.19 and trying to build Alsa 0.9.0-RC3.
> The drivers aren't compiling and giving a string of errors having to do
> with conflicting definitions and such.  I am trying to use a Soundblaster
> AWE64.  I know that this card has been around for awhile so I was thinking
> that maybe an older version would be more likely to build.  Is there a
> particular version that is known to work well with this card?  Otherwise,
> I can provide the rather long list of warnings and errors I am getting and
> go from there.  I'm doing this so I can use full duplex with Speak Freely.
> I had found a hack to sort of get full duplex to work with the kernel
> drivers, but it would generate a lot of record overrun errors and lengthy
> pauses.  Any ideas welcome.

Hmmm, I downgraded to 0.9.0b12, find it very stable, though I'm only using
kernel 2.4.5, Slackware 8.0, but that would be my suggestion.  Make sure
you compile the drivers first, then the libs, then the utils.

HTH

-- 
Toby Fisher	Email: toby@gw0ucu.plus.com
Tel.: +44(0)1480 417272	Mobile: +44(0)7974 363239
ICQ: #61744808
   Please avoid sending me Word or PowerPoint attachments.
   See http://www.fsf.org/philosophy/no-word-attachments.html

Re: recomended Alsa version for an AWE64?

[Charles Hallenbeck]

I have also been unable to compile that version of alsa on my
Slackware system with kernel 2.4.18, and have had the same error
messages. I have had success compiling 0.9.0beta11 and am
sticking with it. My card is an sblive though, not an awe64.

On Tue, 15 Oct 2002, Adam Myrow wrote:

> Well, hearing how once people get it working, everybody seems to be quite
> pleased with Alsa, I've been trying to get it to compile.  I am using
> Slackware Linux with kernel 2.4.19 and trying to build Alsa 0.9.0-RC3.
> The drivers aren't compiling and giving a string of errors having to do
> with conflicting definitions and such.  I am trying to use a Soundblaster
> AWE64.  I know that this card has been around for awhile so I was thinking
> that maybe an older version would be more likely to build.  Is there a
> particular version that is known to work well with this card?  Otherwise,
> I can provide the rather long list of warnings and errors I am getting and
> go from there.  I'm doing this so I can use full duplex with Speak Freely.
> I had found a hack to sort of get full duplex to work with the kernel
> drivers, but it would generate a lot of record overrun errors and lengthy
> pauses.  Any ideas welcome.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

-- 
The Moon is Waxing Gibbous (76% of Full)
So visit me at http://www.valstar.net/~hallenbeck

Re: recomended Alsa version for an AWE64?

[Steve Holmes]

I keep hearing so many horrer stories about getting ALSA going that I
hardly find the worth in even trying.  I understand it is supposed to
work better than OSS like recording better and more reliably and to
allow full duplex operation with Speak Freely but...  I wonder why the
compilation procedures for ALSa have been so unpredictable and
apparently flakey.

On Tue, Oct 15, 2002 at 06:54:25PM -0400, Charles Hallenbeck wrote:
> 
> I have also been unable to compile that version of alsa on my
> Slackware system with kernel 2.4.18, and have had the same error
> messages. I have had success compiling 0.9.0beta11 and am
> sticking with it. My card is an sblive though, not an awe64.
> 
> On Tue, 15 Oct 2002, Adam Myrow wrote:
> 
> > Well, hearing how once people get it working, everybody seems to be quite
> > pleased with Alsa, I've been trying to get it to compile.  I am using
> > Slackware Linux with kernel 2.4.19 and trying to build Alsa 0.9.0-RC3.
> > The drivers aren't compiling and giving a string of errors having to do
> > with conflicting definitions and such.  I am trying to use a Soundblaster
> > AWE64.  I know that this card has been around for awhile so I was thinking
> > that maybe an older version would be more likely to build.  Is there a
> > particular version that is known to work well with this card?  Otherwise,
> > I can provide the rather long list of warnings and errors I am getting and
> > go from there.  I'm doing this so I can use full duplex with Speak Freely.
> > I had found a hack to sort of get full duplex to work with the kernel
> > drivers, but it would generate a lot of record overrun errors and lengthy
> > pauses.  Any ideas welcome.
> >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> 
> -- 
> The Moon is Waxing Gibbous (76% of Full)
> So visit me at http://www.valstar.net/~hallenbeck
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
Please avoid sending me Word or PowerPoint attachments.
   See http://www.fsf.org/philosophy/no-word-attachments.html

Re: recomended Alsa version for an AWE64?

[Christopher Moore]

I had a similar dilemma last week.  The solution was in my kernel
configuration.  You need to have soundcore as a module and no other sound
features.  I mistakenly had midi support checked off.  Check your make
config.  You may not need to recompile your kernel, but it might be safer
to do so along with make modules.

Chris
-- 
The Moon is Waxing Gibbous (76% of Full)

Re: recomended Alsa version for an AWE64?

[Adam Myrow]

I got beta 12 to compile and now have it playing sound and am slowly
figuring out how to set volumes and such.  Also, I am trying to figure out
how to make /dev/sequencer work, but at least it came up.  I had left the
standard kernel sound drivers built as modules because I wanted them to
revert back to in case I couldn't get Alsa to work.  However, the problems
with compiling RC3 all revolved around ISAPNP.  I'm going to check out the
Alsa web site for bug reports on this and submit one if I can't find one.
I can't believe that something like this hasn't gone unnoticed yet.

Re: recomended Alsa version for an AWE64?

[jwantz]

Hi,
Well, with the2.4 kernels you aren't supposed to have to use isapnp 
tools.

      Jim Wantz WB0TFK
On Tue, 15 Oct 2002, Adam Myrow wrote:

> I got beta 12 to compile and now have it playing sound and am slowly
> figuring out how to set volumes and such.  Also, I am trying to figure out
> how to make /dev/sequencer work, but at least it came up.  I had left the
> standard kernel sound drivers built as modules because I wanted them to
> revert back to in case I couldn't get Alsa to work.  However, the problems
> with compiling RC3 all revolved around ISAPNP.  I'm going to check out the
> Alsa web site for bug reports on this and submit one if I can't find one.
> I can't believe that something like this hasn't gone unnoticed yet.
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

Re: recommended Alsa version for an AWE64?

[Adam Myrow]

At 09:53 AM 10/16/02 -0400, you wrote:
>Hi,
>Well, with the2.4 kernels you aren't supposed to have to use isapnp
>tools.

I wasn't.  I'm using the native ISAPNP support.  So far, Alsa has given 
extremely mixed results.  As I stated, I had to go back to beta 12.  Some 
sounds sound better than with the stock drivers and some have a loud pop or 
squeal at the end.  Next, the whole thing about muting all channels by 
default is absolutely insane.  I had my /etc/modules.conf set up to 
auto-load Alsa and after a short time, the modules unload and when they 
reload, everything is muted again.  I got around this by manually loading 
the modules in /etc/rc.d/rc.modules so that they stay in memory.  I'll 
probably leave it that way anyway as it's faster.  Anyway, all this has 
been a let down when it comes to Speak Freely.  I've tried both the stock 
7.2 and the CVS version and had very unsatisfying results.  Both versions 
work fine in half duplex, but I may as well use the stock drivers if I have 
to use half duplex.  When trying full duplex, a person reported that I was 
sending dead carrier.  Further testing with an echo-back server reveals 
that what is happening is that I send out a long period of silence then 
audio.  Finally, it is as if the last packet gets held up until I close the 
connection.  When I kill sfspeaker, I will get a burst of sound like the 
last part of a word and then all sounds I play will play about half speed 
with a horrible clicking over the top.  It's like the old APH tape 
recorders that claimed to let you adjust the speed and keep the pitch 
sounding the same.  They produced a very similar sound.  In other words, 
Speak Freely is messing up Alsa.  I've tried every combination from the 
default flags to the -DLINUX_SMALL_BUFFER flag and removing the 
-DAUDIO_BLOCKING flag which produced noise instead.  With the stock driver, 
I could sort of get full duplex with the sflaunch front-end, but after a 
few minutes, incoming audio would start breaking up and get progressively 
worse until becoming unusable.  Sflaunch doesn't seem to work at all with 
Alsa most of the time.  Also, with the stock drivers, I got a log of 
recording overruns even when I wasn't talking.  The bottom line is I've 
never gotten satisfactory performance from the Unix/Linux version of Speak 
Freely.  I thought Alsa would be the solution, but I'm just about to go 
back to the stock driver and live with half duplex.  If anybody has 
actually gotten Speak Freely working with an AW64 in full duplex mode, 
regardless of what drivers they used, I'd like to hear about it!

Re: recommended Alsa version for an AWE64?

[Igor Gueths]

Hi Adam. Did you try rc3? Or any of the 'rc' versions? Also, what modules
did you have loaded Did you have snd-mixer-oss loaded (if using rc3)?

Microsoft dialogue
This company has performed an illegal operation and will be shutdown. If this problem persists, delete Winblows and install Linux. Close button

On Wed, 16 Oct 2002, Adam Myrow wrote:

> At 09:53 AM 10/16/02 -0400, you wrote:
> >Hi,
> >Well, with the2.4 kernels you aren't supposed to have to use isapnp
> >tools.
>
> I wasn't.  I'm using the native ISAPNP support.  So far, Alsa has given
> extremely mixed results.  As I stated, I had to go back to beta 12.  Some
> sounds sound better than with the stock drivers and some have a loud pop or
> squeal at the end.  Next, the whole thing about muting all channels by
> default is absolutely insane.  I had my /etc/modules.conf set up to
> auto-load Alsa and after a short time, the modules unload and when they
> reload, everything is muted again.  I got around this by manually loading
> the modules in /etc/rc.d/rc.modules so that they stay in memory.  I'll
> probably leave it that way anyway as it's faster.  Anyway, all this has
> been a let down when it comes to Speak Freely.  I've tried both the stock
> 7.2 and the CVS version and had very unsatisfying results.  Both versions
> work fine in half duplex, but I may as well use the stock drivers if I have
> to use half duplex.  When trying full duplex, a person reported that I was
> sending dead carrier.  Further testing with an echo-back server reveals
> that what is happening is that I send out a long period of silence then
> audio.  Finally, it is as if the last packet gets held up until I close the
> connection.  When I kill sfspeaker, I will get a burst of sound like the
> last part of a word and then all sounds I play will play about half speed
> with a horrible clicking over the top.  It's like the old APH tape
> recorders that claimed to let you adjust the speed and keep the pitch
> sounding the same.  They produced a very similar sound.  In other words,
> Speak Freely is messing up Alsa.  I've tried every combination from the
> default flags to the -DLINUX_SMALL_BUFFER flag and removing the
> -DAUDIO_BLOCKING flag which produced noise instead.  With the stock driver,
> I could sort of get full duplex with the sflaunch front-end, but after a
> few minutes, incoming audio would start breaking up and get progressively
> worse until becoming unusable.  Sflaunch doesn't seem to work at all with
> Alsa most of the time.  Also, with the stock drivers, I got a log of
> recording overruns even when I wasn't talking.  The bottom line is I've
> never gotten satisfactory performance from the Unix/Linux version of Speak
> Freely.  I thought Alsa would be the solution, but I'm just about to go
> back to the stock driver and live with half duplex.  If anybody has
> actually gotten Speak Freely working with an AW64 in full duplex mode,
> regardless of what drivers they used, I'd like to hear about it!
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Re: recommended Alsa version for an AWE64?

[Adam Myrow]

On Thu, 17 Oct 2002, Igor Gueths wrote:

> Hi Adam. Did you try rc3? Or any of the 'rc' versions? Also, what modules
> did you have loaded Did you have snd-mixer-oss loaded (if using rc3)?

I tried RC3 and it never would compile.  I still have the errors from
attempts to compile it.  If possible, I'd rather use a later version as I
figure that it'll hopefully be less buggy.  Anyhow, here is a sample of
the errors I was getting when trying to build the driver.

About halfway down:

pdplus.c:3032: warning: #warning "This driver need to be ported to new hw_info"
pdplus.c:3082: warning: #warning "This driver need to be ported to new hw_info"
pdplus.c:3107: warning: #warning "This driver need to be ported to new hw_info"
pdplus.c:3136: warning: #warning "The S/PDIF setup code needs to be rewritten."
pdplus.c:3212: warning: #warning "This driver need to be ported to new hw_info"

Some time later:

                 from /usr/src/alsa-driver-0.9.0rc3/include/sound/driver.h:43,
                 from ../alsa-kernel/core/hwdep.c:22,
                 from hwdep.c:1:
/usr/src/alsa-driver-0.9.0rc3/include/linux/isapnp.h:334: warning: `struct
isapnp_card_id' declared inside parameter list
/usr/src/alsa-driver-0.9.0rc3/include/linux/isapnp.h:334: warning: its
scope is only this definition or declaration, which is probably not what
you want.

This last error repeats over and over and finally, the build would bomb
out with:

sound.c:41: `snd_hack_usb_set_interface' undeclared here (not in a
function)
sound.c:41: initializer element is not constant
sound.c:41: (near initialization for
`__ksymtab_snd_hack_usb_set_interface.value')
make[1]: *** [sound.o] Error 1
make[1]: Leaving directory `/usr/src/alsa-driver-0.9.0rc3/acore'
make: *** [compile] Error 1

Looking at this more closely, it may be choking on the fact that I don't
have USB on this machine and thus don't include USB support in my kernel.
any ideas?

Re: recommended Alsa version for an AWE64?

[Igor Gueths]

Hey Adam. Did you remove isapnp.h from the alsa include directory in rc3?
Aparently it was put in by accident. Or check out the latest cvs code.

Microsoft dialogue
This company has performed an illegal operation and will be shutdown. If this problem persists, delete Winblows and install Linux. Close button

On Thu, 17 Oct 2002, Adam Myrow wrote:

> On Thu, 17 Oct 2002, Igor Gueths wrote:
>
> > Hi Adam. Did you try rc3? Or any of the 'rc' versions? Also, what modules
> > did you have loaded Did you have snd-mixer-oss loaded (if using rc3)?
>
> I tried RC3 and it never would compile.  I still have the errors from
> attempts to compile it.  If possible, I'd rather use a later version as I
> figure that it'll hopefully be less buggy.  Anyhow, here is a sample of
> the errors I was getting when trying to build the driver.
>
> About halfway down:
>
> pdplus.c:3032: warning: #warning "This driver need to be ported to new hw_info"
> pdplus.c:3082: warning: #warning "This driver need to be ported to new hw_info"
> pdplus.c:3107: warning: #warning "This driver need to be ported to new hw_info"
> pdplus.c:3136: warning: #warning "The S/PDIF setup code needs to be rewritten."
> pdplus.c:3212: warning: #warning "This driver need to be ported to new hw_info"
>
> Some time later:
>
>                  from /usr/src/alsa-driver-0.9.0rc3/include/sound/driver.h:43,
>                  from ../alsa-kernel/core/hwdep.c:22,
>                  from hwdep.c:1:
> /usr/src/alsa-driver-0.9.0rc3/include/linux/isapnp.h:334: warning: `struct
> isapnp_card_id' declared inside parameter list
> /usr/src/alsa-driver-0.9.0rc3/include/linux/isapnp.h:334: warning: its
> scope is only this definition or declaration, which is probably not what
> you want.
>
> This last error repeats over and over and finally, the build would bomb
> out with:
>
> sound.c:41: `snd_hack_usb_set_interface' undeclared here (not in a
> function)
> sound.c:41: initializer element is not constant
> sound.c:41: (near initialization for
> `__ksymtab_snd_hack_usb_set_interface.value')
> make[1]: *** [sound.o] Error 1
> make[1]: Leaving directory `/usr/src/alsa-driver-0.9.0rc3/acore'
> make: *** [compile] Error 1
>
> Looking at this more closely, it may be choking on the fact that I don't
> have USB on this machine and thus don't include USB support in my kernel.
> any ideas?
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Re: recommended Alsa version for an AWE64?

[Igor Gueths]

Oh one other thing. What did you include as configure cmdline?

Microsoft dialogue
This company has performed an illegal operation and will be shutdown. If this problem persists, delete Winblows and install Linux. Close button

On Thu, 17 Oct 2002, Adam Myrow wrote:

> On Thu, 17 Oct 2002, Igor Gueths wrote:
>
> > Hi Adam. Did you try rc3? Or any of the 'rc' versions? Also, what modules
> > did you have loaded Did you have snd-mixer-oss loaded (if using rc3)?
>
> I tried RC3 and it never would compile.  I still have the errors from
> attempts to compile it.  If possible, I'd rather use a later version as I
> figure that it'll hopefully be less buggy.  Anyhow, here is a sample of
> the errors I was getting when trying to build the driver.
>
> About halfway down:
>
> pdplus.c:3032: warning: #warning "This driver need to be ported to new hw_info"
> pdplus.c:3082: warning: #warning "This driver need to be ported to new hw_info"
> pdplus.c:3107: warning: #warning "This driver need to be ported to new hw_info"
> pdplus.c:3136: warning: #warning "The S/PDIF setup code needs to be rewritten."
> pdplus.c:3212: warning: #warning "This driver need to be ported to new hw_info"
>
> Some time later:
>
>                  from /usr/src/alsa-driver-0.9.0rc3/include/sound/driver.h:43,
>                  from ../alsa-kernel/core/hwdep.c:22,
>                  from hwdep.c:1:
> /usr/src/alsa-driver-0.9.0rc3/include/linux/isapnp.h:334: warning: `struct
> isapnp_card_id' declared inside parameter list
> /usr/src/alsa-driver-0.9.0rc3/include/linux/isapnp.h:334: warning: its
> scope is only this definition or declaration, which is probably not what
> you want.
>
> This last error repeats over and over and finally, the build would bomb
> out with:
>
> sound.c:41: `snd_hack_usb_set_interface' undeclared here (not in a
> function)
> sound.c:41: initializer element is not constant
> sound.c:41: (near initialization for
> `__ksymtab_snd_hack_usb_set_interface.value')
> make[1]: *** [sound.o] Error 1
> make[1]: Leaving directory `/usr/src/alsa-driver-0.9.0rc3/acore'
> make: *** [compile] Error 1
>
> Looking at this more closely, it may be choking on the fact that I don't
> have USB on this machine and thus don't include USB support in my kernel.
> any ideas?
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Re: recommended Alsa version for an AWE64?

[Charles Hallenbeck]

Hi Igor/Adam,

I left isapnp support out of my kernel when compiling it, and
configured the alsa-drivers using --without-isapnp and
--with-oss.

But my sound card is a PCI device, sblive.

Not sure what else I did this time that made it work okay.


On Thu, 17 Oct 2002, Igor Gueths wrote:

> Oh one other thing. What did you include as configure cmdline?
>
> Microsoft dialogue
> This company has performed an illegal operation and will be shutdown. If this problem persists, delete Winblows and install Linux. Close button
>
> On Thu, 17 Oct 2002, Adam Myrow wrote:
>
> > On Thu, 17 Oct 2002, Igor Gueths wrote:
> >
> > > Hi Adam. Did you try rc3? Or any of the 'rc' versions? Also, what modules
> > > did you have loaded Did you have snd-mixer-oss loaded (if using rc3)?
> >
> > I tried RC3 and it never would compile.  I still have the errors from
> > attempts to compile it.  If possible, I'd rather use a later version as I
> > figure that it'll hopefully be less buggy.  Anyhow, here is a sample of
> > the errors I was getting when trying to build the driver.
> >
> > About halfway down:
> >
> > pdplus.c:3032: warning: #warning "This driver need to be ported to new hw_info"
> > pdplus.c:3082: warning: #warning "This driver need to be ported to new hw_info"
> > pdplus.c:3107: warning: #warning "This driver need to be ported to new hw_info"
> > pdplus.c:3136: warning: #warning "The S/PDIF setup code needs to be rewritten."
> > pdplus.c:3212: warning: #warning "This driver need to be ported to new hw_info"
> >
> > Some time later:
> >
> >                  from /usr/src/alsa-driver-0.9.0rc3/include/sound/driver.h:43,
> >                  from ../alsa-kernel/core/hwdep.c:22,
> >                  from hwdep.c:1:
> > /usr/src/alsa-driver-0.9.0rc3/include/linux/isapnp.h:334: warning: `struct
> > isapnp_card_id' declared inside parameter list
> > /usr/src/alsa-driver-0.9.0rc3/include/linux/isapnp.h:334: warning: its
> > scope is only this definition or declaration, which is probably not what
> > you want.
> >
> > This last error repeats over and over and finally, the build would bomb
> > out with:
> >
> > sound.c:41: `snd_hack_usb_set_interface' undeclared here (not in a
> > function)
> > sound.c:41: initializer element is not constant
> > sound.c:41: (near initialization for
> > `__ksymtab_snd_hack_usb_set_interface.value')
> > make[1]: *** [sound.o] Error 1
> > make[1]: Leaving directory `/usr/src/alsa-driver-0.9.0rc3/acore'
> > make: *** [compile] Error 1
> >
> > Looking at this more closely, it may be choking on the fact that I don't
> > have USB on this machine and thus don't include USB support in my kernel.
> > any ideas?
> >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

-- 
The Moon is Waxing Gibbous (91% of Full)
So visit me at http://www.valstar.net/~hallenbeck

Re: recommended Alsa version for an AWE64?

[Adam Myrow]

I think my configure was "./configure --with-sequencer=yes."  I tried
"--with-alsapnp=no" as well and still the same.  I'll try removing the
isapnp.h file and see what happens.  Which directory should I remove it
from?  There is one in support and include/linux.

Re: recommended Alsa version for an AWE64?

[Charles Hallenbeck]

I have no idea. You will not want to do it the way I did -- wipe
out your root partition and reinstall your OS!



-- 
The Moon is Waxing Gibbous (93% of Full)
So visit me at http://www.valstar.net/~hallenbeck

Re: recommended Alsa version for an AWE64?

[Christopher Moore]

Check your kernel .config file.  Look in the
# Sound
section.  The only thing you shold have uncommented is:
CONFIG_SOUND=m

Chris
-- 
The Moon is Waxing Gibbous (94% of Full)

Re: recommended Alsa version for an AWE64?

[Igor Gueths]

Yes its the include/linux directory.

Microsoft dialogue
This company has performed an illegal operation and will be shutdown. If this problem persists, delete Winblows and install Linux. Close button

On Thu, 17 Oct 2002, Adam Myrow wrote:

> I think my configure was "./configure --with-sequencer=yes."  I tried
> "--with-alsapnp=no" as well and still the same.  I'll try removing the
> isapnp.h file and see what happens.  Which directory should I remove it
> from?  There is one in support and include/linux.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Re: recommended Alsa version for an AWE64?

[igueths]

Hi Chuck. As I probably mentioned earlier, remove 
isapnp.h out of $prefix/alsa-0.9.0rc3/include. Then 
reconfigure and remake. 
> Hi Igor/Adam,
> 
> I left isapnp support out of my kernel when compiling it, and
> configured the alsa-drivers using --without-isapnp and
> --with-oss.
> 
> But my sound card is a PCI device, sblive.
> 
> Not sure what else I did this time that made it work okay.
> 
> 
> On Thu, 17 Oct 2002, Igor Gueths wrote:
> 
> > Oh one other thing. What did you include as configure cmdline?
> >
> > Microsoft dialogue
> > This company has performed an illegal operation and will be shutdown. If this 
> problem persists, delete Winblows and install Linux. Close button
> >
> > On Thu, 17 Oct 2002, Adam Myrow wrote:
> >
> > > On Thu, 17 Oct 2002, Igor Gueths wrote:
> > >
> > > > Hi Adam. Did you try rc3? Or any of the 'rc' versions? Also, what modules
> > > > did you have loaded Did you have snd-mixer-oss loaded (if using rc3)?
> > >
> > > I tried RC3 and it never would compile.  I still have the errors from
> > > attempts to compile it.  If possible, I'd rather use a later version as I
> > > figure that it'll hopefully be less buggy.  Anyhow, here is a sample of
> > > the errors I was getting when trying to build the driver.
> > >
> > > About halfway down:
> > >
> > > pdplus.c:3032: warning: #warning "This driver need to be ported to new 
> hw_info"
> > > pdplus.c:3082: warning: #warning "This driver need to be ported to new 
> hw_info"
> > > pdplus.c:3107: warning: #warning "This driver need to be ported to new 
> hw_info"
> > > pdplus.c:3136: warning: #warning "The S/PDIF setup code needs to be 
> rewritten."
> > > pdplus.c:3212: warning: #warning "This driver need to be ported to new 
> hw_info"
> > >
> > > Some time later:
> > >
> > >                  from 
> /usr/src/alsa-driver-0.9.0rc3/include/sound/driver.h:43,
> > >                  from ../alsa-kernel/core/hwdep.c:22,
> > >                  from hwdep.c:1:
> > > /usr/src/alsa-driver-0.9.0rc3/include/linux/isapnp.h:334: warning: `struct
> > > isapnp_card_id' declared inside parameter list
> > > /usr/src/alsa-driver-0.9.0rc3/include/linux/isapnp.h:334: warning: its
> > > scope is only this definition or declaration, which is probably not what
> > > you want.
> > >
> > > This last error repeats over and over and finally, the build would bomb
> > > out with:
> > >
> > > sound.c:41: `snd_hack_usb_set_interface' undeclared here (not in a
> > > function)
> > > sound.c:41: initializer element is not constant
> > > sound.c:41: (near initialization for
> > > `__ksymtab_snd_hack_usb_set_interface.value')
> > > make[1]: *** [sound.o] Error 1
> > > make[1]: Leaving directory `/usr/src/alsa-driver-0.9.0rc3/acore'
> > > make: *** [compile] Error 1
> > >
> > > Looking at this more closely, it may be choking on the fact that I don't
> > > have USB on this machine and thus don't include USB support in my kernel.
> > > any ideas?
> > >
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> 
> -- 
> The Moon is Waxing Gibbous (91% of Full)
> So visit me at http://www.valstar.net/~hallenbeck
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: recommended Alsa version for an AWE64?

[igueths]

Hi Adam. Remove it from $prefix/alsa-0.9.0rc3/include. 
My configure was: ./configure --with-isapnp=yes --with-
moddir=/lib/modules/2.4.18/misc --with-oss=yes. 
> I think my configure was "./configure --with-sequencer=yes."  I tried
> "--with-alsapnp=no" as well and still the same.  I'll try removing the
> isapnp.h file and see what happens.  Which directory should I remove it
> from?  There is one in support and include/linux.
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup