> > [aloew@aloew-lap envytools-master]$ sudo ./nva/nvapeek 10200c 10
> > 0010200c: SS SS SS SS SS SS SS SS SS SS SS SS SS SS SS SS
>
> nvapeek 10200c without the 10. (Not sure what that does.... maybe reads out
> 0x10 regs)
yes - seems to read 10 registers:
[aloew@aloew-lap envytools-master]$ sudo ./nva/nvapeek 10200c
0010200c: SS
> Well, no one's heard of a "missing" PCRYPT before, but it's certainly
> conceivable that certain blocks were omitted. I'd feel better with that
> diagnosis if more people chimed in saying that they had the same issue.
From the screenshots of the corrupted graphics, I definitely think that this is the exact same issue.
But I fully agree that it is a pity that nobody of the folks who had raised this previously and/or commented, do react now that it has probably been tracked down to its root cause.
And something else seems interesting:
All other people who saw the corruption issue (except nemasu with his/her 8800 GTS, who might have seen a different issue indeed from the dmesg output) also were using early G86 chips, particularly 8400M-based, and mostly the "mobile" variants...
Maybe NVidia omitted part of the 8400 functionality in the mobile variants? This would again make up a nice (and easy) question to them...!? ;-)
> > [aloew@aloew-lap envytools-master]$ sudo ./nva/nvapeek 10200c 10
> > 0010200c: SS SS SS SS SS SS SS SS SS SS SS SS SS SS SS SS
>
> nvapeek 10200c without the 10. (Not sure what that does.... maybe reads out
> 0x10 regs)
yes - seems to read 10 registers:
[aloew@aloew-lap envytools-master]$ sudo ./nva/nvapeek 10200c
0010200c: SS
> Well, no one's heard of a "missing" PCRYPT before, but it's certainly
> conceivable that certain blocks were omitted. I'd feel better with that
> diagnosis if more people chimed in saying that they had the same issue.
From the screenshots of the corrupted graphics, I definitely think that this is the exact same issue.
But I fully agree that it is a pity that nobody of the folks who had raised this previously and/or commented, do react now that it has probably been tracked down to its root cause.
And something else seems interesting:
All other people who saw the corruption issue (except nemasu with his/her 8800 GTS, who might have seen a different issue indeed from the dmesg output) also were using early G86 chips, particularly 8400M-based, and mostly the "mobile" variants...
Maybe NVidia omitted part of the 8400 functionality in the mobile variants? This would again make up a nice (and easy) question to them...!? ;-)
Thanks again & BR,
Andreas