Doing some more thinking... this is the dmesg output for the 2.6.28-11 kernel grepping for HDA:
myth@Wakko:~$ dmesg | grep -i HDA
[ 9.900622] hda-intel: unable to grab IRQ 0, disabling device
[ 9.900639] HDA Intel: probe of 0000:00:14.2 failed with error -16
[ 9.900655] HDA Intel 0000:01:05.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[ 9.900669] HDA Intel 0000:01:05.1: setting latency timer to 64
In 2.6.27-11 the card has IRQ 16. hda_intel is trying to get IRQ 0 for the card, and sending out error -16... could those be connected? Why is it trying to pull IRQ 0? That should be reserved for the system timer, never even attempted. Seems like this is definitely a kernel issue of some sort, ALSA or something.
Doing some more thinking... this is the dmesg output for the 2.6.28-11 kernel grepping for HDA:
myth@Wakko:~$ dmesg | grep -i HDA
[ 9.900622] hda-intel: unable to grab IRQ 0, disabling device
[ 9.900639] HDA Intel: probe of 0000:00:14.2 failed with error -16
[ 9.900655] HDA Intel 0000:01:05.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[ 9.900669] HDA Intel 0000:01:05.1: setting latency timer to 64
In 2.6.27-11 the card has IRQ 16. hda_intel is trying to get IRQ 0 for the card, and sending out error -16... could those be connected? Why is it trying to pull IRQ 0? That should be reserved for the system timer, never even attempted. Seems like this is definitely a kernel issue of some sort, ALSA or something.
Looks like this guy is having a similar problem with his HP DV4: article. gmane.org/ gmane.linux. alsa.devel/ 62317
http://