Comment 63 for bug 1158689

Hmm...

While my card definitely is not at all defective (it works the exact same way it always has), I indeed also have some issues that make it impossible for me to still use the "blob" even on an attic distro like RHEL6:

The most recent version of the NVidia proprietary driver that worked fine for me was their 285.09 (which can no longer be used even on RHEL6 due to the fact that it relies on an outdated X11 ABI (AFAIK).

Any more recent version of NVidia's driver (and most interestingly, on Linux as well as on Windows 7 x64!) - even though NVidia states that Quadro NVS 130M would still be supported with their latest drivers - has an issue which causes sudden complete hangs every once in a while (between a few seconds to few hours), but completely unpredictably...

Unfortunately, NVidia tech support is unable/unwilling to help with this issue (I tried for several months without any progress...).

I just did some Google research: Do you know that an 8400M (as well as my NVS 130M) does only support VDPAU "feature set A", but most VDPAU software relies on feature sets C or D being implemented by the cards!?

Would it make sense to address the above questions about the feature set implemented by these early G86 cards and how to properly activate these features directly to NVidia (AFAIK, they recently offered some help by answering questions from nouveau developers)?

In order to move forward, I will try to comment out the single line

 { "CRYPT", 0, 0x74c1, nv84_bo_move_exec, nv50_bo_move_init },

in a current 3.12.4 build, and report back on what happens...

Best regards,
Andreas