Definitely seconded. snd-maestro3.ko nicely fails for me here, on custom-built 2.6.27+. As probably does lots of other hardware for many other users?
Took ages working through the entire helper hierarchy (including adding printk logging to maestro3.c!!) until I found out that it is completely unable to locate the firmware file (via strace, no less!). Could this bug be turbo-charged? It's already a month old now, and a lot of time wasted locally until the cause was isolated... Thanks, Andreas Mohr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]