[Alsa-user] Aplay arecord ecasound - segmentation fault
Hi all, I installed alsa (1.0.17) (lib+plugins+utils). Kernel is 2.6.22.5 and gcc 4.1.2. Installation worked well but now aplay generates a seg fault. [EMAIL PROTECTED] ~]# aplay /usr/share/sounds/alsa/Front_Center.wav Playing WAVE '/usr/share/sounds/alsa/Front_Center.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono Segmentation fault [EMAIL PROTECTED] ~]# Arecord does the same as well as alsaplayer ; and when trying to use ecasound with alsa output, I get this seg fault as well. Verry surprisingly, speech-dispatcher that runs too on this machine works perfectly even if it does use alsa. Has anybody an idea how to investigate this faillure ? I might mention that with 1.0.13 the situation is the same. Regards Pierre - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Aplay arecord ecasound - segmentation fault
Hi Thanks for your answer since it let me at least partially solve the problem : From: stan [EMAIL PROTECTED] Subject: Re: [Alsa-user] Aplay arecord ecasound - segmentation fault Date: Wed, 13 Aug 2008 11:43:56 -0700 Pierre Lorenzon wrote: Hi all, I installed alsa (1.0.17) (lib+plugins+utils). Kernel is 2.6.22.5 and gcc 4.1.2. Installation worked well but now aplay generates a seg fault. [EMAIL PROTECTED] ~]# aplay /usr/share/sounds/alsa/Front_Center.wav Playing WAVE '/usr/share/sounds/alsa/Front_Center.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono Segmentation fault [EMAIL PROTECTED] ~]# Arecord does the same as well as alsaplayer ; and when trying to use ecasound with alsa output, I get this seg fault as well. Are you running a sound server? It can lock up the device, preventing other applications from using it directly. No ! What happens if you use the -vv option to the command? aplay -vv /usr/share/sounds/alsa/Front_Center.wav Verbose but still the seg fault ! aplay -vv -Dhw:0,0 /usr/share/sounds/alsa/Front_Center.wav No seg fault but device is busy ! aplay -vv -Dplughs:0,0 /usr/share/sounds/alsa/Front_Center.wav Same as above ! What does strace show? strace aplay /usr/share/sounds/alsa/Front_Center.wav In particular that the asound.conf and .asoundrc files are not loaded where I thought they were ! Are there any messages in /var/log/messages related to alsa? No aparrently not ! When you installed the library, did you check that everything went in the right place? Some distros move things. The standard location for alsa-lib files is in /usr/share/alsa. Check that those files are the files from the package. Then search in /etc to see if they also exist there. If they do, either link or overwrite them with the latest versions. And ensure that there aren't any old library versions around. libasound usually resides in /usr/lib, but I have seen it in /lib. Is the linked version the version from your compile? Did you run an /sbin/ldconfig after you updated the library? I do not use any distro but simply folow blfs book indications. I tghink that things are at the good place. Verry surprisingly, speech-dispatcher that runs too on this machine works perfectly even if it does use alsa. I wonder if it doesn't use OSS emulation? Or perhaps it is using a sound server via a plugin? I don't think so. Has anybody an idea how to investigate this faillure ? I might mention that with 1.0.13 the situation is the same. Regards Pierre It probably isn't necessary in this case, but could you run a script which provides more information about your sound setup and post the link back here? In fact I simply removed .asoundrc and it works now. I wrote this .asoundrc file following instructions on the alsa-project home page but it was for previous versions of alsa and it is possible that it is no longer compatible. Indeed I felt very convenient to use the dmix plugin and that's why I had this .asoundrc file. Now question is : do you know a good hint to write a correct .asoundrc file ? Regards Pierre - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] First post
Hi, It looks like to me such questions are well answered in the blfs book. I personnaly think that the latter is a very good tool to build his own custom distro. Bests Pierre From: David Henderson dhender...@digital-pipe.com Subject: [Alsa-user] First post Date: Sun, 19 Jun 2011 14:41:08 -0400 Hi everyone! I'm currently expanding my knowledge of GNU/Linux to include building packages from scratch towards an overall goal of a custom distro. So far, I have a nice base for a command line OS, but want to expand into the multimedia aspect. Alsa was my first (only?) choice for the audio portion, but I'm running into problems. The alsa site is somewhat overwhelming to newbies and is easy to get lost. I have a few questions below from which I hope I can find help. All contributions are greatly appreciated. :) Thanks, Dave 1) Currently I have downloaded alsa-driver, alsa-lib, and alsa-utils packages. Is there an order in which these packages need to be compiled and installed? 2) I'm currently running the relatively new Linux kernel 2.6.33 so do I need the alsa-driver package? 3) I've been able to successfully compile the alsa-lib package and install it in the custom distro. When I try to compile the alsa-utils package, I constantly get the error: checking for libasound headers version = 1.0.16... not present. configure: error: Sufficiently new version of libasound not found. I'm actually using an existing Kubuntu installation to build the packages for my custom distro. As a result, after I compiled the newer alsa-lib, I didn't install the package into the Kubuntu OS, but rather a staging directory (/opt/staging/alsa). I'm sure the reason this is failing is because it's probably looking for /usr/lib/... or some other default location. How do I tell the configure script for the alsa-utils to look in the staging directory for the header files it needs? -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] First post
Hi, From: David Henderson dhender...@digital-pipe.com Subject: Re: [Alsa-user] First post Date: Sun, 19 Jun 2011 15:28:48 -0400 Thanks for the reply Pierre. I checked into the blfs book, but it merely says these five chapters will cover alsa and then gives you a basic type configure make. This is obviously not going to answer the questions below. :) Any other thoughts? Dave On 06/19/2011 11:22 PM, Pierre Lorenzon wrote: Hi, It looks like to me such questions are well answered in the blfs book. I personnaly think that the latter is a very good tool to build his own custom distro. Bests Pierre From: David Hendersondhender...@digital-pipe.com Subject: [Alsa-user] First post Date: Sun, 19 Jun 2011 14:41:08 -0400 Hi everyone! I'm currently expanding my knowledge of GNU/Linux to include building packages from scratch towards an overall goal of a custom distro. So far, I have a nice base for a command line OS, but want to expand into the multimedia aspect. Alsa was my first (only?) choice for the audio portion, but I'm running into problems. The alsa site is somewhat overwhelming to newbies and is easy to get lost. I have a few questions below from which I hope I can find help. All contributions are greatly appreciated. :) Thanks, Dave 1) Currently I have downloaded alsa-driver, alsa-lib, and alsa-utils packages. Is there an order in which these packages need to be compiled and installed? This question is answered by the blfs book. First alsa-lib and after alsa-utils. 2) I'm currently running the relatively new Linux kernel 2.6.33 so do I need the alsa-driver package? No ! I am running a 2.6.32 kernel and never installed alsa-driver. Anyway if the sound system is something very exotic it might be necessary ... 3) I've been able to successfully compile the alsa-lib package and install it in the custom distro. When I try to compile the alsa-utils package, I constantly get the error: checking for libasound headers version= 1.0.16... not present. configure: error: Sufficiently new version of libasound not found. I'm actually using an existing Kubuntu installation to build the packages for my custom distro. As a result, after I compiled the newer alsa-lib, I didn't install the package into the Kubuntu OS, but rather a staging directory (/opt/staging/alsa). I'm sure the reason this is failing is because it's probably looking for /usr/lib/... or some other default location. How do I tell the configure script for the alsa-utils to look in the staging directory for the header files it needs? Humm ! I don't really understand this method. In my opinion if you want to have a custom distro you first install a basic systme on a partition or in a directory. Once the basic system is installed (more or less the content of the lfs book) you simply chroot to this new system to install the rest of the stuff. Following this scheme there will be no problem. I did it many times ! It leads me to a more global question : you say you want to build a custom distro but do you have some kind of documentation to do that ? If you plan to do that on your own, it's a big deal ! Anyway I'll suggest you to have a look at the lfs book. It might be that the installation schedule suggested by the lfs team is not suitable for you but in my opinion it is better to check this point before reinventing the weel as we say in french ! Bests Pierre -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] First post
From: James Shatto wwwshad...@gmail.com Subject: Re: [Alsa-user] First post Date: Sun, 19 Jun 2011 15:36:59 -0500 A) If you want to overwrite your existing distro's versions, you probably want the --prefix=/usr option on your ./configure commands. If not, be sure to change your $PATH to look at /usr/local FIRST. B) Compile alsa-lib first, alsa-driver second. Most compile options only need --prefix=/usr if you want to override the default of /usr/local. But alsa-driver requires extra parms depending on what you want. Some packages are only tool sets, so make -f Makefile? And use them from where you made them, or copy/move them to more common $PATH's. C) You might have versioning conflicts depending on what you're trying to mix and match. libc and other things might not work well together unless you're running the latest and greatest of every component. And even that is problematic some of the time. D) unless you have a lot of time to waste, or just need the learning, I'd recommend going with existing distros. There's enough of them that one might suit your current needs. www.distrowatch.com I suggested something intermediary : lfs or gentoo which are easily customizable. Pierre HTH, - James On 6/19/11, David Henderson dhender...@digital-pipe.com wrote: Thanks for the reply Pierre. I checked into the blfs book, but it merely says these five chapters will cover alsa and then gives you a basic type configure make. This is obviously not going to answer the questions below. :) Any other thoughts? Dave On 06/19/2011 11:22 PM, Pierre Lorenzon wrote: Hi, It looks like to me such questions are well answered in the blfs book. I personnaly think that the latter is a very good tool to build his own custom distro. Bests Pierre From: David Hendersondhender...@digital-pipe.com Subject: [Alsa-user] First post Date: Sun, 19 Jun 2011 14:41:08 -0400 Hi everyone! I'm currently expanding my knowledge of GNU/Linux to include building packages from scratch towards an overall goal of a custom distro. So far, I have a nice base for a command line OS, but want to expand into the multimedia aspect. Alsa was my first (only?) choice for the audio portion, but I'm running into problems. The alsa site is somewhat overwhelming to newbies and is easy to get lost. I have a few questions below from which I hope I can find help. All contributions are greatly appreciated. :) Thanks, Dave 1) Currently I have downloaded alsa-driver, alsa-lib, and alsa-utils packages. Is there an order in which these packages need to be compiled and installed? 2) I'm currently running the relatively new Linux kernel 2.6.33 so do I need the alsa-driver package? 3) I've been able to successfully compile the alsa-lib package and install it in the custom distro. When I try to compile the alsa-utils package, I constantly get the error: checking for libasound headers version= 1.0.16... not present. configure: error: Sufficiently new version of libasound not found. I'm actually using an existing Kubuntu installation to build the packages for my custom distro. As a result, after I compiled the newer alsa-lib, I didn't install the package into the Kubuntu OS, but rather a staging directory (/opt/staging/alsa). I'm sure the reason this is failing is because it's probably looking for /usr/lib/... or some other default location. How do I tell the configure script for the alsa-utils to look in the staging directory for the header files it needs? -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https
Re: [Alsa-user] intel hda vs asus xonar STX
Hi Clemens, From: Clemens Ladisch <cladi...@googlemail.com> Subject: Re: [Alsa-user] intel hda vs asus xonar STX Date: Mon, 28 Sep 2015 08:35:24 +0200 > Pierre Lorenzon wrote: >> There are two sound card on the system. A chips on the mother >> board which is driven as far as I know by an hda intel driver >> and a PCI xonar STX card. >> >> On the first one mixing is possible : I mean that if a sound >> process as aplay for instance is running and you start another >> one like mplayer for instance sound is mixed and you might >> listen to the two sources taht are played. >> >> With the xonar STX card it does not seem to be possible. > > Neither hardware supports mixing. OK that's the first significant information ! > > Dmix (or PulseAudio) is enabled by default, but when you're I read taht here and there but did not know really how to activate it ! > using a device name like "hw" or "plughw" to access the other > card, this is bypassed. In theory, "default:X" or "dmix:X" OK I ignored this bypass. > should work for any card. > > Did you redefine the "default" ALSA device? If not, do No I did not redefine anything ! > "aplay -D default:STX something.wav" and > "mplayer -ao alsa:device=default=STX something.mp3" work? Clear it works. Only have now to tell to ecasound to do the same because output description is not exactly the same as in aplay or player but now I precisely know waht have to be done. Thanks and regards Pierre > > > Regards, > Clemens > > -- > ___ > Alsa-user mailing list > Alsa-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/alsa-user -- ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] intel hda vs asus xonar STX
Hi, In fact I expected such an answer but I would like not use jack or pulse if not necessary. If the asus xonar essence stx is able to mix sources there's no need to use more only enable it. Moreover if alsa is able to do the mix softly no need to had anything to the system. In this case you'll tell me simply to read carefully the xonar stx documentation or how to set up dmix for this card. Anyway it would be much more comfortable if someone already has experience with taht whol stuff and can tell me. Regards Pierre From: Ralf MardorfSubject: Re: [Alsa-user] intel hda vs asus xonar STX Date: Sun, 27 Sep 2015 18:19:28 +0200 > Perhaps a sound server defaults to use the integrated sound device? > Pulseaudio nowadays seems to be installed as the default sound server by > most Linux distros that provide an out of the box working > desktop environment and even for other distros it's an annoying > dependency. For my Linux installs empty dummy packages fake to fulfil > the pulseaudio dependency, while I'm using jackd to use several audio > streams. > > -- > ___ > Alsa-user mailing list > Alsa-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/alsa-user -- ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] intel hda vs asus xonar STX
Hi All, My alsa version is 1.0.27 and my kernel version is 3.10.14. There are two sound card on the system. A chips on the mother board which is driven as far as I know by an hda intel driver and a PCI xonar STX card. On the first one mixing is possible : I mean that if a sound process as aplay for instance is running and you start another one like mplayer for instance sound is mixed and you might listen to the two sources taht are played. With the xonar STX card it does not seem to be possible. If an aplay process is running and you try to start a mplayer process for instance it failed with error message indicating taht the device is busy. I don't know where it comes from. Does the asus xonar STX card not have natively ability to mix sound ? Does the driver not implement this feature ? I know that in the past it might be necessarry to activate something like dmix that was no longer needed by newer chips since they have ability to mix without any work of the driver. Is it not the case with the xonar STX card and do I have to setup something like dmix ? Regards Pierre -- ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] intel hda vs asus xonar STX
Hi Vladimir, From: Vladimir Mosgalin <mosga...@vm10124.spb.edu> Subject: Re: [Alsa-user] intel hda vs asus xonar STX Date: Mon, 28 Sep 2015 04:40:28 +0300 > Hi Pierre Lorenzon! > > On 2015.09.27 at 19:13:17 +0200, Pierre Lorenzon wrote next: > >> In fact I expected such an answer but I would like not use jack >> or pulse if not necessary. If the asus xonar essence stx is >> able to mix sources there's no need to use more only enable it. > > Xonar STX ("AV100" chip which is basically the same as C-media 8787) > does not support mixing multiple sources. So you have to either use > pulseaudio or rely on something like dmix. OK that's a very clear answer. In the passt I got dmix functionning for an old sound chipset that did not have mixing ability. In fact I forgot how I did that but I'll try to find it again. Thanks Pierre > > (jack works too but I wouldn't recommend it unless you need low latency > audio in professional audio-related applications, it can be a headache > when used for typical multimedia tasks with random crappy software that > wants to play audio) > > Note that if you have first model of *STX*, not ST or second STX model > (actually I'm not sure about second STX), for quality reasons you'd want > to avoid 44100/88200/176400 audio sample rates, so instead of default > pulse configuration when it tries to pick audio rate to avoid conversion > (e.g. you're playing single stream of 44100 music in your audio player - > it sets card audio rate to 44100 because card supports it), you should > lock the rate to 96000 or 192000 instead, e.g. > > default-sample-format = s24le > default-sample-rate = 96000 > > in pulseaudio's daemon.conf > > Lower audio quality and lower SNR in 44100 and multipies of it is quite > audible. However, this only applies to PCI-E model (STX), PCI model (ST) > has no problems with any rates. > > -- > > Vladimir > > -- > ___ > Alsa-user mailing list > Alsa-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/alsa-user -- ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user