Re: ALSA USB and motherboard

I have a new Dell PowerEdge T110 workstation to replace the old T105. Both of them lack any proper sound hardware so I've got USB speakers. Some time in the process of replacing the system or the monitor (which is a USB hub and thus changes USB device assignment) sound stopped working in KDE. It seems that the main problem is that there is some sort of sound hardware detected on the motherboard (maybe the built in PC speaker) which causes the real sound hardware to be registered as ALSA device 1. So far the only way I've discovered to make things work is to make the following sym-links to make the USB sound hardware be device 0. # ls -l /dev/snd total 0 drwxr-xr-x. 2 root root 60 Dec 9 20:49 by-id drwxr-xr-x. 2 root root 80 Dec 9 20:49 by-path lrwxrwxrwx. 1 root root 9 Dec 18 00:05 controlC0 -> controlC1 crw-rw---T. 1 root audio 116, 3 Dec 9 20:49 controlC1 crw-rw---T. 1 root audio 116, 5 Dec 9 20:49 hwC0D0 lrwxrwxrwx. 1 root root 8 Dec 18 00:09 pcmC0D0p -> pcmC1D0p crw-rw---T. 1 root audio 116, 4 Dec 9 20:49 pcmC0D3p crw-rw---T. 1 root audio 116, 2 Dec 18 00:09 pcmC1D0p crw-rw---T. 1 root audio 116, 1 Dec 9 20:49 seq crw-rw---T. 1 root audio 116, 33 Dec 9 20:49 timer Is there a way that I can reserve device 0 for the USB device? It needs to be reserved because the motherboard hardware is detected before the USB bus is scanned - if the monitor is even turned on when the system is booted. Is there a way I can make the system just ignore the motherboard device and have only 1 ALSA card? There's only one thing that can ever be useful so it seems best to make it the only recognised card in the system. Thanks -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/ _______________________________________________ luv-main mailing list luv-main(a)luv.asn.au http://lists.luv.asn.au/listinfo/luv-main