20 Apr
2012
20 Apr
'12
2:26 a.m.
Hello,
So, I was getting tired of fighting to keep abreast of the latest
developments in the audio world whilst remaining on Squeeze, which
looked like soon forcing me to maintain half the software myself, so
went ahead and upgraded to Wheezy (while being tired). The upshot is a
rather messy system which I have been wrestling for a couple days
now. One problem seems to be a total lack of sound: opening any audio
device returns a "resource busy" error. I'm wondering whether anyone
else ever encountered this? Also, I'm still running a 2.6.33RT kernel:
is the latest alsa-lib backwards compatible to this?
Cheers,
S.M.
--
20 Apr
20 Apr
7:31 a.m.
2012/4/20 S. Massy <lists(a)wolfdream.ca>
Hello,
So, I was getting tired of fighting to keep abreast of the latest
developments in the audio world whilst remaining on Squeeze, which
looked like soon forcing me to maintain half the software myself, so
went ahead and upgraded to Wheezy (while being tired). The upshot is a
rather messy system which I have been wrestling for a couple days
now. One problem seems to be a total lack of sound: opening any audio
device returns a "resource busy" error. I'm wondering whether anyone
else ever encountered this? Also, I'm still running a 2.6.33RT kernel:
is the latest alsa-lib backwards compatible to this?
Cheers,
S.M.
aptitude purge $(dpkg -l pulse*| grep ^ii | awk '{print $2}')
did you use `aptitude dist-upgrade` for wheey upgrade?
AFAIK 2.6.33.7 RT is one of the stable 2.6* RT kernels ever
-r
--
*L'unica speranza di catarsi, ammesso che ne esista una, resta affidata
all'istinto di ribellione, alla rivolta non isterilita in progetti, alla
protesta violenta e viscerale. (V. Evangelisti)
*
7:39 a.m.
On 20 April 2012 07:31, Raffaele Morelli <raffaele.morelli(a)gmail.com> wrote:
2012/4/20 S. Massy <lists(a)wolfdream.ca>
Hello,
alsa
libs, no problems there.
So, I was getting tired of fighting to keep abreast of the latest
developments in the audio world whilst remaining on Squeeze, which
looked like soon forcing me to maintain half the software myself, so
went ahead and upgraded to Wheezy (while being tired). The upshot is a
rather messy system which I have been wrestling for a couple days
now. One problem seems to be a total lack of sound: opening any audio
device returns a "resource busy" error. I'm wondering whether anyone
else ever encountered this? Also, I'm still running a 2.6.33RT kernel:
is the latest alsa-lib backwards compatible to this?
Cheers,
S.M.
aptitude purge $(dpkg -l pulse*| grep ^ii | awk '{print $2}')
did you use `aptitude dist-upgrade` for wheey upgrade?
AFAIK 2.6.33.7 RT is one of the stable 2.6* RT kernels ever
-r
Yeah, I've been running that for the longest time, including the latest
8:31 a.m.
On Fri, Apr 20, 2012 at 07:31:01AM +0200, Raffaele Morelli wrote:
2012/4/20 S. Massy <lists(a)wolfdream.ca>
Yeah, it looks like the
upgrade did install some stray, unwanted
pulseaudio stuff, god only knows why. So now aplay & co. work fine, but jackd
still doesn't. It says:
Failed to acquire device name : Audio0 error : Invalid argument
Audio device hw:0,0 cannot be acquired...
Jack: ~JackDriver
Cannot initialize driver
This is for my builtin hda-intel card, but the end-result it more or
less the same for hw:1,0, which is my external USB soundcard. All of
this used to work flawlessly before the upgrade and the kernel/drivers
are the same. Any ideas?
Cheers,
S.M.
Hello,
So, I was getting tired of fighting to keep abreast of the latest
developments in the audio world whilst remaining on Squeeze, which
looked like soon forcing me to maintain half the software myself, so
went ahead and upgraded to Wheezy (while being tired). The upshot is a
rather messy system which I have been wrestling for a couple days
now. One problem seems to be a total lack of sound: opening any audio
device returns a "resource busy" error. I'm wondering whether anyone
else ever encountered this? Also, I'm still running a 2.6.33RT kernel:
is the latest alsa-lib backwards compatible to this?
Cheers,
S.M.
aptitude purge $(dpkg -l pulse*| grep ^ii | awk '{print $2}')
did you use `aptitude dist-upgrade` for wheey upgrade?
AFAIK 2.6.33.7 RT is one of the stable 2.6* RT kernels ever
9:16 a.m.
2012/4/20 S. Massy <lists(a)wolfdream.ca>
Yeah, it looks like the upgrade did install some
stray, unwanted
pulseaudio stuff, god only knows why. So now aplay & co. work fine, but
jackd
still doesn't.
command/settings are you running jackd with?
aplay -l && aplay -L ?
cat /proc/asound/cards?
This is for my builtin hda-intel card, but the
end-result it more or
less the same for hw:1,0, which is my external USB soundcard. All of
this used to work flawlessly before the upgrade and the kernel/drivers
are the same. Any ideas?
--
*L'unica speranza di catarsi, ammesso che ne esista una, resta affidata
all'istinto di ribellione, alla rivolta non isterilita in progetti, alla
protesta violenta e viscerale. (V. Evangelisti)
*
6:07 p.m.
On Fri, Apr 20, 2012 at 09:16:32AM +0200, Raffaele Morelli wrote:
2012/4/20 S. Massy <lists(a)wolfdream.ca>
Looks like the problem is with dbus and running without X. May I
recommend considering the opinion expressed in this post?
http://permalink.gmane.org/gmane.comp.audio.jackit/25430
Cheers,
S.M.
Yeah, it looks like the upgrade did install some
stray, unwanted
pulseaudio stuff, god only knows why. So now aplay & co. work fine, but
jackd
still doesn't.
command/settings are you running jackd with?
aplay -l && aplay -L ?
cat /proc/asound/cards?
> This is for my builtin hda-intel card, but the end-result it more or
> less the same for hw:1,0, which is my external USB soundcard. All of
> this used to work flawlessly before the upgrade and the kernel/drivers
> are the same. Any ideas?
> 
2:20 p.m.
On Friday, 20 April 2012 at 2:28, S. Massy wrote:
Yeah, it looks like the upgrade did install some
stray, unwanted
pulseaudio stuff, god only knows why. So now aplay & co. work fine, but jackd
still doesn't. It says:
Failed to acquire device name : Audio0 error : Invalid argument
Audio device hw:0,0 cannot be acquired...
Jack: ~JackDriver
Cannot initialize driver
This is for my builtin hda-intel card, but the end-result it more or
less the same for hw:1,0, which is my external USB soundcard. All of
this used to work flawlessly before the upgrade and the kernel/drivers
are the same. Any ideas?
Possibly the same problem as
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643791; removing
/usr/share/alsa/pulse*.conf helped here.
4604
days inactive
4604
days old
linux-audio-user@lists.linuxaudio.org
6 comments
4 participants
participants (4)
-
Arve Barsnes -
Christian Ohm -
Raffaele Morelli -
S. Massy