audio devices lottery on each boot

I want to update this bug. Gutsy turned stable and the problem is still there, I even reinstalled the system to be sure, that there are no wrong settings. So right now i'm using

---
$ uname -r
2.6.22-14-generic

$ dpkg -l alsa-base
ii alsa-base 1.0.14-1ubuntu2 ALSA driver configuration files
---

The audio devices still change their order every time i boot my computer. This is pretty annoying. Ususally i'v got no sound over my speakers. I've got to reset the gnome settings. VOIP applications have to be reconfigured every time, etc.

I use the follwoing sound modules

---
$ cat /proc/asound/modules
 0 snd_usb_audio
 1 snd_usb_audio
 2 snd_bt87x
 3 snd_hda_intel
---

When i add something like

---
options snd-hda-intel index=0
---

to my /etc/modprobe.d/alsa-base things turn even worse. Propably every second reboot the Nvidia (snd_hda_intel) device is missing...

Well, hardy is on it's way and despite PulseAudio this problem is still relevant. I can fix this by blacklisting my audio devices inside /etc/modprobe.d/blacklist

blacklist snd_usb_audio
blacklist snd_bt87x
blacklist snd_hda_intel

and loading my devices via /etc/modules

snd-hda-intel
snd-bt87x
snd-usb-audio

and adding

options snd-hda-intel index=0

to my /etc/modprobe.d/alsa-base. But this is quite inconvenient and hard to do for a linux newbie...

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.

 status incomplete
 subscribe

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkit6uMACgkQ06FgkPZwicSsAgCgkI25q3SE59BKf3jQf1mDwFDf
HHcAnA7QXkyZKXWPZM2JNL7bu9Zrincb
=LMeY
-----END PGP SIGNATURE-----

Yes, this is still an issue. My workaround fixes the problem, but without it, the problem is still there. Didn't test intrepid yet.

Hi!

I have exactly the same problem with my newly attached USB keyboard (Enermax Aurora) with integrated audio device.
I use Kubuntu 8.04

Hi is there any progress on this? I have the same problem on 8.10 (and had it on 8.04 too) and have been hoping that someone would find a solution to this.

Still present in Jaunty.

I must admit that this problem is gone since intrepid. I mark this bug as fixed.

It happened today on a clean install of Karmic so fixed might be a bit of an overstatement.
My USB audio started as hw:0 instead of its usual hw:1

Use names instead of the number... Look into /proc/asound/

$ ls -al /proc/asound/
[...]
lrwxrwxrwx 1 root root 5 2009-11-23 21:16 Audigy2 -> card0
lrwxrwxrwx 1 root root 5 2009-11-23 21:16 Bt878 -> card2
[...]
lrwxrwxrwx 1 root root 5 2009-11-23 21:16 CinemaTM -> card1
[...]

and use "hw:CinemaTM,0" if you like "hw:1,0". The names stay static.

QJackCtl does't give me the option to use names. But if I could use the name that would be great.
If I can start Jack from the cmdline using the names then all will be well. I'll give it a try.

Yes that works, thank you very much. I can start jackd from the commandline using names.
That fixed it for me, would be nice if qjackctl would also do this.

PCI audio device enumeration by the kernel has never been deterministic.
Please don't mark this bug fixed (despite it unlikely to be resolved for
10.04 or even in a reasonable timeframe).

On Nov 24, 2009 8:26 AM, "tkoorn" <email address hidden> wrote:

Yes that works, thank you very much. I can start jackd from the commandline
using names.
That fixed it for me, would be nice if qjackctl would also do this.

** Changed in: linux (Ubuntu)
      Status: Confirmed => Fix Released

-- audio devices lottery on each boot
https://bugs.launchpad.net/bugs/130004You received this bug...

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.