I unfortunately have the shimmer sky bug:


Nvidia 8500GT 512


HP AMD 5000+

Its an 8800GTS 512MB(G92)

Intel core 2 duo 6750

Gigabyte P35 MB

PCI-e 2.0

 

-----signature-----

Thank you for the added information... I'm working on a new spreadhseet atm with newer info added into it...


Fyrie - Lifted form Wikipedia just for you....


"Nvidia does not publish the documentation for its hardware, meaning that programmers cannot write appropriate and effective open-source drivers for Nvidia's products. Instead, Nvidia provides its own binary GeForce graphics drivers for X.Org and a thin open-source library that interfaces with the Linux, FreeBSD or Solaris kernels and the proprietary graphics software."


So its possible the nonbug under WINE is from that, not triggering something thats not "supported" in Linux but is in windows.

 

-----signature-----

Nvidia GEForce 8600 GTS, not sure of the MB properties, lol, but I am running an Intel


DtB

 

-----signature-----

Wubbie - notice that Mawnee indicates having the problem with a 8800GTS 512MB(G92) & PCI-e 2.0 system.

Wubbie,


I'm sick, so I'm a little slow today. My brain is running on half power . I'm not quite understanding what you getting at. There are open source drivers out there, but I haven't tried those. I'm currently using the nVidia binary. It is true that the nVidia linux driver is shrouded in mystery because there is no source for it. In addition to that, I've never seen a document that lists what card features are supported compared to the windows driver. I guess there is no way to know if there is a 1 to 1 feature correlation between the Linux and Windows driver. I'd consider the linux driver a variable, and I also consider WINE's implementation of the direct 3d libraries to be another huge variable. Who knows.. Maybe it's entirely related to WINE and the drivers have nothing to do with it. It's hard to say.


I don't know if I mentioned this earler, but the latest version of wine broke the ac launcher. D'oh!


I've been reading a lot lately about how nVidia and ATI basically don't care about backwards compatibility at this point. That is so sad. I understand that new games drive upgrade adoption, but people want to play games from all eras of pc gaming.

Mawnee - thank you for your information, I apologize for being a bit slow but last night I spent over 2 hours reading and rereading threads updating the list of bugged cards.


Fyrie - I think I was more pointing to the fact that Nvidia has an entirely different driver implementation for *nix and could explain the bug not appearing in WINE.

If you were coding something for *nix would you bother including Windows type calls?

And because Nvidia has decided to be super secret about how it works, even if we could find someone willing to trudge thru the code and find the AHA moment where it all goes boom, we can't. But its very telling that its not maybe a physical defect in the card.


GondorB - You have the oddest card Can I get a couple more favors? Under 5 min total I swear!

1 - Who made your card? PNY, BFG etc...

2 - Whats the BIOS revision on your card? I had to reenable the old style control panel to find this info because the "NEW" better stronger faster Nvidia control panel won't tell you ANYTHING useful about the card. AHA under the help there is a system information option the bios is buried there.


I'mma try to re-find the person who reported your card as bugged in their system and try for the same information for comparison.


If you had a different BIOS/Firmware than the other cards showing the bug I'm not sure what it tells us but I allows us add that detail to the mix. Being able to tell an Nvidia tech "Look 2 "identical" cards the only difference is 1 shows the bug the other doesn't. The ONLY difference is the BIOS revision. This bug shows up on nearly EVERY series 8 card except those with a BIOS higher/lower than x.x.x.xxx.xx.x"


Ugh if only it was that simple...


wubbie - still coughing his lungs out...

 

-----signature-----

I am copy pasting from my thread on Turbine boards cause this is important...


Ok Absoultion and Gondor have both gotten back to me...


Absolution - Bios 62.92.1f.00.01

Gondor - Bios 62.92.12.00.04


As I remember Gondor has a 2.0 rev and Absolution had a 1.XX...

Both of them are using cards bulk packaged with their machines so they do not know the manufacturers easily heck they could be the same.


Fyrie - I don't understand how numbers progress when you add a b c e d f etc to the mix, can you shed some light on it?


Okies, people with the bug... Hit your manufacturer's webpages. The fact that Fyrie found a BIOS offering fixes for some of the cards that SPECIFICALLY talked about PCIe implementation fixes leads me to think that my crackpot idea about a problem with PCIe might go somewhere.


wubbie - did someone sacrifice a turbine staffer to find help and not tell me?

 

-----signature-----

"I don't understand how numbers progress when you add a b c e d f etc to the mix, can you shed some light on it?"


Wubbie - this would indicate the use of hexidicimal numbering, using a base of 16, where 0–9 represents digits zero to nine, plus a-f to represent digits with values ten to fifteen.

Gondor - so you have an earlier bios?


I got a line from Absolution and he used NiBiTor to find out who the manufacturer of his card was, it said it was an EVGA.


Anyone been able to head out and check their makers page for BIOS updates?

 

-----signature-----