![]() | |||||||||||
Messages in this thread |
Andras Mantia <amantia@kde.org> writes: > Måns Rullgård wrote: >> Hmm, mine crashed when I used the PCI card. Using the onboard sound >> was fine. > > Now it doesn't crash. :-0 That hang was with kernel 2.6.15, but I switeched > back to 2.6.13 as that is what suse provides and I played some music on > both cards and tried Skype on the onboard card (there was the hang) and it > was OK. Just write it off to cosmic rays if it doesn't happen again. >>>>> 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. >>> >>> Thanks. >> >> Care to post the output? > > Sure. I still don't know how to use those numbers in the quircks.c (do I > need to create something like #define PCI_DEVICE_WHATEVER pciIDNumber ?). The device IDs are already #defined in <linux/pci_ids.h>. > The result of lspci -vvvn is attached. > 00:11.0 Class 0601: 1106:3227 > Subsystem: 1043:80ed This is the interesting bit. Curiously enough, it is exactly the same as mine. I can't see any reason why it shouldn't match on your board. Try sticking some printk()s in there and find out what values are actually seen. -- 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/ | ||||||||||
| Last update: 2006-03-19 14:06 [from the cache] ©2003-2008 | |||||||||||