Off the top of my head it's mostly these two:
Same experience as me, the device doesn't work with any of the generic drivers ....
Which is what started me down the path of knocking up my own driver to see what was going on.
I'll try and reproduce it later with a fresh one to get the bottom of it, only thing I can think perhaps is the generic drivers try and configure it in some way that it doesn't like.
