Hi,
I am new to this list, so I hope I am not asking questions which have
heard many times before. I have tried alsa versions 0.9.0rc4 and rc3 and
in both cases I get the following messages when I try to
modprobe snd-hdsp:
/lib/modules/2.4.18-14/kernel/sound/pci/rme9652/snd-hdsp.o: unresolved
Once upon a time, Takashi wrote :
/usr/bin/ld: .libs/libasound.so.2.0.0: undefined versioned symbol name
[EMAIL PROTECTED]
/usr/bin/ld: failed to set dynamic section sizes: Bad value
please try to configure --with-versioned=no.
which libtool version are you using?
please check the
At Wed, 23 Oct 2002 15:16:08 +0200,
Werner Schweer wrote:
On Wednesday 23 October 2002 11:51, Takashi Iwai wrote:
...
- SB AWE models (ugh, crap!)
- Yamaha YMF7xx/DS-XG (some have reported that these work ok,
but in any case they have a max 3 periods limitation
similar to
At Wed, 23 Oct 2002 13:04:39 +0200,
Matthias Saou wrote:
Once upon a time, Takashi wrote :
/usr/bin/ld: .libs/libasound.so.2.0.0: undefined versioned symbol name
[EMAIL PROTECTED]
/usr/bin/ld: failed to set dynamic section sizes: Bad value
please try to configure
At Wed, 23 Oct 2002 03:44:03 -0700 (PDT),
Shahrokh Yadegari wrote:
Hi,
I am new to this list, so I hope I am not asking questions which have
heard many times before. I have tried alsa versions 0.9.0rc4 and rc3 and
in both cases I get the following messages when I try to
modprobe snd-hdsp:
Once upon a time, Takashi wrote :
I'm getting the exact same problem on Red Hat Linux 8.0 with GNU ld
version 2.13.90.0.2 20020802. Is the --with-versioned=no workaround
considered a clean enough one? Should I wait for a patch to the
configure script instead?
i believe it's not a bug
On Wed, 2002-10-23 at 13:33, Takashi Iwai wrote:
i believe it's not a bug of ld but of libtool.
could you check libtool --version ?
I have exactly the same problem, the libtool (that is included in the
package, so why can't you check for yourself? :-) is version:
ltmain.sh (GNU libtool)
On Wed, 2002-10-23 at 14:04, Mathy Vanvoorden wrote:
Ignore last mail :-) Apparantly make still used the provided libtool. I
replaced it with the libtool I installed (since I can't see a
configure-option to specify that it should use the installed version and
configure doesn't detect it
Completely remove old modules in this directory bytypingrm -rf /lib/modules/(your kernel version)/misc Compile the driver with these options. --with-kernel=(your kernel source dir path)--with-moddir=/lib/modules/(your kernel version)/misc --with-cards=(youur sound card chipset name)type
At 23 Oct 2002 14:04:46 +0200,
Mathy Vanvoorden wrote:
On Wed, 2002-10-23 at 13:33, Takashi Iwai wrote:
i believe it's not a bug of ld but of libtool.
could you check libtool --version ?
I have exactly the same problem, the libtool (that is included in the
package, so why can't you
Hi everybody, I'm setting up a Linux box with a Sb Audigy, so I downloaded the latest
Alsa release but I get the following error while compiling the libraries (driver
compiling went just fine):
gcc -shared conf.lo confmisc.lo input.lo output.lo async.lo error.lo dlmisc.lo
-Wl,--whole-archive
Hi all,
it looks like we have problems on rc4 tarballs.
the reason is the old libtool and generated files by the old auto*
tools included in the tarballs.
so, cvscompile should work, if you have newer libtool.
anyway, we'll release rc5 ASAP.
please be patient for a while now.
Takashi
On Wed, 2002-10-23 at 15:55, Steven Rubenstein wrote:
Read the INSTALL file in alsa-lib.
SJR
I did that... The only thing it states is a bug in libtool when trying
to compile static and shared at the same time. Since I'm using default
configure options, only shared are build. So this has
They are going to release an rc5 to fix this. If you can't wait, try
cvscompile or do it like I did: Install a newer libtool on your
computer, after running the configure script copy it from
/usr/bin/libtool (or wherever it's installed) to your alsa-lib dir,
overwriting the old one, and compile...
I had this problem allready when installing rc3 and they told me to wait
for next release, maybe it would be solved, but it still isn't so again:
Every input/output in my mixer shows up double, only difference is that
behind the second one there is a 1. Why is this and how can I solve it?
:-) Is
Takashi Iwai wrote:
please try to configure --with-versioned=no.
That works! Thanks.
which libtool version are you using?
please check the output of libtool --version.
Actually, I didn't even have libtool installed (relatively new box,
oops, my bad), but after installing it, I still
On 2002.10.23 07:53 Mathy Vanvoorden wrote:
Every input/output in my mixer shows up double, only difference is
that behind the second one there is a 1. Why is this and how can I
solve it? :-)
No, this isn't a bug. The cs46xx driver is undergoing some major
changes, and this simply hasn't
Bill Adam,
Thanks for your responses. This makes sense, and I did get as far last
evening as making sure that rtSynth was seen by kaconnect, but didn't have a
MIDI keyboard handy to see if sound came out. I'll poke into that this
evening.
Thanks again,
Mark
-Original Message-
From:
Hi,
i have a box with a Creative Labs Soundblaster Live,
newest alsa drivers, SuSe 8.0. I can play songs
without problems but i have two big problems:
1. i cannot record sound - when i record something i
just get silence although there's definitively a
signal on line-in.
i.e. arecord -v gives
On Wed, 2002-10-23 at 17:56, Peter Heatwole wrote:
No, this isn't a bug. The cs46xx driver is undergoing some major
changes, and this simply hasn't been rewritten yet. Basically, the
mixer sliders you see with 1 appended to them control the second
AC97 codec on the card. In the future I
On 2002.10.23 10:07 Mathy Vanvoorden wrote:
On Wed, 2002-10-23 at 17:56, Peter Heatwole wrote:
In the future I believe most of these will be merged so that one
slider control's both codecs, then you won't have double's anymore.
Ah, I c, thank you :-) Any idea on when this will be finished? :-)
On 23 Oct 2002, Mathy Vanvoorden wrote:
On Wed, 2002-10-23 at 17:56, Peter Heatwole wrote:
No, this isn't a bug. The cs46xx driver is undergoing some major
changes, and this simply hasn't been rewritten yet. Basically, the
mixer sliders you see with 1 appended to them control the second
Hi
I'm having problems rebuilding the kdemultimedia-3.0.3-4 package to
include alsa support.
Normally I would install the source RPM, edit the kdemultimedia.spec file
and let the build run. Having done that many times so far, and also having
tried just untarring the source tar archive and
Takashi Iwai wrote:
please try to configure --with-versioned=no.
which libtool version are you using?
please check the output of libtool --version.
As I said in my last email, the above worked.
But I found a small bug in the utils tarball.
Namely 'missing' 'mkinstalldirs' and 'install-sh'
Hey all, me again.
The INSTALL file for alsa-drivers 0.9.0rc4 says that the snd_ prefix
was removed from the modules... but this doesn't seem to be the case for
my driver.
In rc3 my driver was called snd_via686
In rc4 my driver is called snd_via82xx
Sligthly different name, but the snd_
Peter Heatwole wrote:
On 2002.10.23 12:52 Phil Dibowitz wrote:
In rc3 my driver was called snd_via686
In rc4 my driver is called snd_via82xx
The snd_ prefix was removed from the module parameters, not the
driver modules themselves (which are prefixed by snd-).
OK... so when I modprobe I
On 2002.10.23 13:15 Phil Dibowitz wrote:
OK... so when I modprobe I still use snd_... but for my modules.conf
file I need to use just via82xx (for example)... and no snd_? Same for
pcm_oss, and the rest of 'em?
Sorry, let me clarify. The module options are the parameters that
you give to
Hello all:
I am attempting to upgrade my system to the latest ALSA release
(0.9.0rc4) and am having issues installing the alsa-lib package. I did
not have any trouble installing and getting the 0.9.0rc4 driver package
running. I am getting an error message during the linking phase of the
make
Peter Heatwole wrote:
Sorry, let me clarify. The module options are the parameters that
you give to the module when you load them, be it through insmod/modprobe
or in modules.conf. The driver in your case would be snd-via82xx, but
the options would no longer have the snd_ prefix.
For
Completely remove old modules in this directory by
typing
rm -rf /lib/modules/(your kernel version)/misc
Compile the driver with these options.
--with-kernel=(your kernel source dir path)
--with-moddir=/lib/modules/(your kernel version)/misc
--with-cards=(your sound card chipset name)
type
I am trying to build Alsa-lib RC5 and it bombs out almost immediately
with:
../../depcomp: No such file or directory
What is depcomp?
---
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java
I don't like to reply on my own post, but I have found what appears to be the
problem.
I wrote:
I'm having problems rebuilding the kdemultimedia-3.0.3-4 package to
include alsa support.
Normally I would install the source RPM, edit the kdemultimedia.spec file
and let the build run. Having
Hello,
I am running RedHat 8.0 with kernel-2.4.18-4 and gcc 3.2 20020903. I am
a Linux newbie and I had questions about configuring alsa to run on my
HP pavilion notebook computer. RedHat detects my card (VIA AC97
VIA82C686) properly, but the test sound, or any sound for that matter,
is played as
At Wed, 23 Oct 2002 00:07:22 +0300 (EEST),
Kai Vehmanen wrote:
On Tue, 22 Oct 2002, Peter L Jones wrote:
I don't want to have to learn about DSPs and stuff to be able to identify a
_good_ sound card. I've currently got a shortlist for my next machine:
* MidiMan Delta Audiophile 2496
34 matches
Mail list logo
