Re: [Alsa-user] Soundcard only works every other login
On Fri, 25 Jan 2008 17:27:02 +0100 Ed Porteous <[EMAIL PROTECTED]> wrote: > > Hi, > > An update to this problem... > > The Mia now appears to work every time I boot up, but I only managed to do > this by disabling the built in Intel sound card in the BIOS. Not an ideal > solution. > > When both cards were enabled, the Mia didn't work on alternate boots, and I > found that it wasn't being assigned an interrupt - > interruptslist-installed.txt shows the interrupt list when the Mia is working > and interruptslist-notinstalled.txt when it isn't working. I can't tell why > this is, but lspci always shows Mia in the list. > > Does anyone know why the interrupt would be assigned only every other boot? > Is this an ALSA question or a question for some other group? I don't know, but when the driver can't install the IRQ handler it should write "cannot grab irq\n" in the logs (type dmesg or look in /var/log/???). Please check it out. When something fails the drivers frees all its resources before exitting, so obviously you don't see its name in /proc/interrupts, but it doesn't mean the problem is IRQ related. -- Giuliano. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Soundcard only works every other login
> The Mia now appears to work every time I boot up, > but I only managed to do this by disabling the > built in Intel sound card in the BIOS. Not an > ideal solution. Sound like you might just need to index the alsa modules so they load in a specific order. Automations scripts might be working in strange ways. udev / discover / ... plus mixer restoration. It could just depend on which card get hits first in terms of restoring mixer settings, and/or loading modules. Perhaps something like this in your configuration would help. Modify to use your specific cards. You don't have to disable the card in the bios. At least in a perfect world. /etc/modprobe.d/(whatever yours is called, alsa, alsa-base, alsa_custom) #- START - alias char-major-116 snd alias char-major-14 soundcore options snd major=116 cards_limit=3 # This ensures that my onboard soundcard is card 0, # and therefor the default(unless overridden). options snd-atiixp index=0 # It seems to get assigned in sequence # whether I use it or even want it. options snd-atiixp-modemindex=1 options snd-usb-audio index=2 alias snd-card-0 snd-atiixp alias sound-slot-0snd-card-0 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seqr-oss alias sound-service-0-12 snd-pcm-oss alias snd-card-1 snd-atiixp-modem alias sound-slot-1snd-card-1 alias sound-service-1-0 snd-mixer-oss alias sound-service-1-1 snd-seq-oss alias sound-service-1-3 snd-pcm-oss alias sound-service-1-8 snd-seqr-oss alias sound-service-1-12 snd-pcm-oss alias snd-card-2 snd-usb-audio alias sound-slot-2snd-card-2 alias sound-service-2-0 snd-mixer-oss alias sound-service-2-1 snd-seq-oss alias sound-service-2-3 snd-pcm-oss alias sound-service-2-8 snd-seqr-oss alias sound-service-2-12 snd-pcm-oss #- END - /home/user/.asoundrc #- START - pcm.atiixp { type hw card 0 } ctl.atiixp { type hw card 0 } pcm.atiixp-modem { type hw card 1 } ctl.atiixp-modem { type hw card 1 } pcm.usb_audio { type hw card 2 } ctl.usb_audio { type hw card 2 } # MODIFY this if you don't want card 0 to be your DEFAULT # NOTE: may only work on apps that use alsa natively. defaults.pcm.card 0 # Otherwise you need to modify your indexing # to make your primary card 0, # which doesn't have to be your onboard sound. #- END - HTH, James - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Soundcard only works every other login
> Does anyone know why the interrupt would be assigned only every other > boot? Is this an ALSA question or a question for some other group? That sounds more like a BIOS issue - have you upgraded to the latest BIOS? That issue aside there have been messages posted to this list in the past about cards appearing out of order on every boot - check the archives to find out how to give a specific card a specific order. This would at least stop the Intel card taking over if the other one doesn't work. Cheers, Adam. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Soundcard only works every other login
Hi, An update to this problem... The Mia now appears to work every time I boot up, but I only managed to do this by disabling the built in Intel sound card in the BIOS. Not an ideal solution. When both cards were enabled, the Mia didn't work on alternate boots, and I found that it wasn't being assigned an interrupt - interruptslist-installed.txt shows the interrupt list when the Mia is working and interruptslist-notinstalled.txt when it isn't working. I can't tell why this is, but lspci always shows Mia in the list. Does anyone know why the interrupt would be assigned only every other boot? Is this an ALSA question or a question for some other group? Thanks, Ed. > From: [EMAIL PROTECTED] > To: alsa-user@lists.sourceforge.net > Subject: Soundcard only works every other login > Date: Tue, 22 Jan 2008 02:00:26 +0100 > > > Hi, > > I have an Echo Mia soundcard, and I've managed to get it work, but only every > other time I log in, which is a bit of a pain! The initialization of the card > doesn't show up in /var/log/messages when it doesn't work, and when it does > work, I do see the initialization. I also have a built-in intel sound card, > which it reverts to when the Mia doesn't work. > > I'm using Ubuntu Gutsy, fully patched. > > If anyone would be able to help me, I'd be most grateful. Please let me know > what extra information I can provide. > > Thanks, > Ed. > _ > Express yourself instantly with MSN Messenger! Download today it's FREE! > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ CPU0 0:171 IO-APIC-edge timer 1: 90 IO-APIC-edge i8042 6: 5 IO-APIC-edge floppy 7: 0 IO-APIC-edge parport0 8: 3 IO-APIC-edge rtc 9: 1 IO-APIC-fasteoi acpi 12:279 IO-APIC-edge i8042 14: 8072 IO-APIC-edge libata 15:728 IO-APIC-edge libata 16: 0 IO-APIC-fasteoi uhci_hcd:usb1 17: 50 IO-APIC-fasteoi uhci_hcd:usb2 18: 47 IO-APIC-fasteoi uhci_hcd:usb3, ohci1394, Intel 82801BA-ICH2, eth1 19: 30 IO-APIC-fasteoi uhci_hcd:usb4 20: 29 IO-APIC-fasteoi eth0 21: 183777 IO-APIC-fasteoi ehci_hcd:usb5, Mia 22: 4068 IO-APIC-fasteoi nvidia NMI: 0 LOC: 13633 ERR: 0 MIS: 0 CPU0 0:171 IO-APIC-edge timer 1:263 IO-APIC-edge i8042 6: 5 IO-APIC-edge floppy 7: 0 IO-APIC-edge parport0 8: 3 IO-APIC-edge rtc 9: 1 IO-APIC-fasteoi acpi 12: 1647 IO-APIC-edge i8042 14: 9202 IO-APIC-edge libata 15: 1139 IO-APIC-edge libata 16: 47 IO-APIC-fasteoi eth0 17: 0 IO-APIC-fasteoi uhci_hcd:usb1 18: 50 IO-APIC-fasteoi uhci_hcd:usb2 19:326 IO-APIC-fasteoi uhci_hcd:usb3, ohci1394, Intel 82801BA-ICH2, eth1 20: 22 IO-APIC-fasteoi uhci_hcd:usb4 21: 131865 IO-APIC-fasteoi ehci_hcd:usb5 22: 7052 IO-APIC-fasteoi nvidia NMI: 0 LOC: 16416 ERR: 0 MIS: 0 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] Soundcard only works every other login
Hi, I have an Echo Mia soundcard, and I've managed to get it work, but only every other time I log in, which is a bit of a pain! The initialization of the card doesn't show up in /var/log/messages when it doesn't work, and when it does work, I do see the initialization. I also have a built-in intel sound card, which it reverts to when the Mia doesn't work. I'm using Ubuntu Gutsy, fully patched. If anyone would be able to help me, I'd be most grateful. Please let me know what extra information I can provide. Thanks, Ed. _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user