Messages in this thread | | | From | Måns Rullgård <> | Subject | Re: [PATCH 001/001] PCI: PCI quirk for Asus A8V and A8V Deluxe motherboards | Date | Sat, 18 Mar 2006 14:23:53 +0000 |
| |
Andras Mantia <amantia@kde.org> writes:
> Måns Rullgård wrote: > >> I didn't do anything else. Check that your chipset has the same PCI >> ID that the patch is for. >> > > Indeed, the problem is here. If I use > DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_VIA, PCI_ANY_ID, > asus_hides_ac97_lpc ); > > (see the PCI_ANY_ID) instead of > DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_8237, > asus_hides_ac97_lpc ); > > (and remove the check "if (likely(!asus_hides_ac97)) return;") > it works. I cannot see the output about enabling the device in "dmesg | grep > PCI", but lspci shows the audio and modem device. > And it works both with the 2.6.13 suse and 2.6.15 vanilla kernel.
That certainly suggests that your chipset has a different PCI ID.
> I managed to hang the machine completely with skype, altough before that a > quick test showed that the device works, as I could hear the music. Maybe > it's the same problem you've experienced.
With the card in the bad slot I only got a few seconds of sound before the machine locked up. Since you have a different board, it could of course still be a similar problem, just less likely to happen.
Which sound card were you using when your machine hung?
> Can you tell me how can I find the real device ID for my chipset? It > *should* be the same one as the original writer of the patch wrote (he also > had an ASUS A8V Deluxe as I understood), but the experience tells it is > not.
lspci -n will list the PCI IDs in hex.
-- Måns Rullgård mru@inprovide.com
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |