Slashdot Mirror
Apple/NVidia Driver Bug — Question Deleted
Joe Drago writes "I purchased a Mac Pro within the first week that they were available, and immediately upgraded to 3GB of RAM (knowing that OSX loves memory). When playing 3D games (World of Warcraft mainly), the game would Kernel Panic the machine if I had played it for a few hours, or if I swapped in and out of the game a few times, etc. I eventually found out (from an official Blizzard poster) that NVidia has a bug in their drivers that kernel panics a Mac Pro if any memory past the 2GB boundary is addressed in the driver. After waiting months for a resolution to this, I decided to post on Apple's support site. Here is an image of my post.. Within a few hours, they removed it from the site, placing it under 'Posts Removed by Administration.' What's going on here? Is Apple trying to hide this bug, or is there something more serious going on between Apple and NVidia?"
I eventually found out (from an official Blizzard poster) that NVidia has a bug in their drivers that kernel panics a Mac Pro if any memory past the 2GB boundary is addressed in the driver. After waiting months for a resolution to this, I decided to post on Apple's support site. Here is an image of my post.. Within a few hours, they removed it from the site, placing it under 'Posts Removed by Administration.'
Macs "just work". Everyone knows that. Obviously the "problem" is your fault, and/or you're a troll.
Push Button, Receive Bacon
So don't remove the post! Reply to it saying that and close the topic.
A new Apple icon needs to be added to Slashdot, showing a man gagged by an apple.
I wonder if I use bold in my signature, people will notice my posts.
[This comment has been deleted.]
And the masses cried out, "09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0!"
If so, then they should post a reply to that effect -- not delete the whole thread!
"[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz
Wow, I'm kind of surprised this popped up on slashdot (I figured it would get mentioned in a blog, at most, and forgotten about). I'm one of the admins on that forum, and can confirm that yes, we've been asked to nuke anything regarding nVidia, at least in certain contexts. One recent addition to our arrangement with them (to provide kernel drivers) involves some very restrictive IP deals that upper management has interpreted to mean we shouldn't even acknowledge certain kinds of bugs in a very specific area. It's my understanding that there are some serious showstopper bugs inherent to nvidia's platform independent core code that they really do not want releasing. Most of us think this is utter BS (and management being paranoid), fwiw.
:p
And yes, there are enough forum admins that I'm not too scared about 'leaking' like this. Note that I'm keeping the exact details secret
Apple and nVidia have both said, in public, many times, that in the specific case of Apple NV cards, the drivers are handled by Apple.
Apple Guy: Hi, I'm an Apple.
PC Guy: Hi, I'm a PC.
Apple Guy: *itching crotch*
PC Guy: Got a problem there?
Apple Guy: No, I'm fine. (*cockroaches fall to floor from pant leg*)
PC Guy: Having a little problem with that "Nvidia card"? (chuckles)
Apple Guy: *walks off set*
PC Guy: Don't mind him, he's just trying to support more than 2GB of RAM...
Authority questions you. Return the favor.
Is this what you're looking for?
P.S. I can't believe you got modded troll. Sorry, what I am saying, the world is full of idiots.
This is what I would expect. When I bugged apple about their broken NFS support on servers they told us that engineers would get back to us. They never did. So I started asking on forums and mailing lists to see if I could get an answer and as soon as I brought it up the thread would get killed or the post would be deleted. Then when we had issues with MPICH it as the same dang thing. Eventually they admitted that MPICH2 works much nicer on Mac OS than MPICH 1 due to some network implementations stuff. Every time I brought it up on the forums though the thread would get killed. (For the curious, the problem that we where having was that an Apple server running NFS would always seem to forget about the last file in a directory when it cached the directory contents. so running "mkdir a; cd a; touch 1 2 3 4 5 6 ; cd .. ; rm -rf a" would fail one out of four times when being done over NFS. If you waited a half an hour then ran rm -rf a it would work great. This issue didn't happen when Mac OS systems mounted Linux NFS shares, but happened every time a Linux or Mac OS system mounted a NFS share off of a Mac OS based system. This was still happening to all of our PPC based systems as of last summer when we finally switched them over to PPC Linux, which made the problem go away)
I guess what I am saying is that it is not surprising. Apple has always nuked threads that made them look bad so why not this one?
The video card was standard in his machine. In other words... it was supplied by Apple. The drivers he is using are from Apple. Nvidia doesn't even offer Mac drivers on their site.
Beware of he who would deny you access to information, for in his heart he dreams himself your master.
The article was about a Mac Pro, not a MacBook Pro, which is a laptop. The MacBook Pro has an ATI video card not a NVidia card.
Dell Tech Support is hiring...
How often do people take screen grabs of their posts to a forum? Was their expectation of it being removed?
Apple routinely deletes posts discussing known defects; it's very well known among Apple-using techies. Apple has done it in almost every case where there have been hardware defects of any kind. A classic example would be the iBook motherboard failures. I would imagine they do it to a)keep other owners from finding out and demanding fixes as well, b)keeping the press from finding out, and c)to defend themselves in any lawsuits which can claim "well, people reported it on your forums, so you must have known about it!" So...yes.
Web forums and mailing lists fuck with a classic PR/customer service move: deny all knowledge. I had a problem with speakers in my car, which in some cases had caused smoke or fire in this particular model. We called the car company, and each member of the forum, over a period of several weeks, was told "we have no knowledge of any other reports of problems with this model." They lied straight through their teeth. We later found out that over ten years before, a vehicle had completely burned to the ground because of the same defect, and company reps came out, looked at the car, purchased it back off the owner no questions asked, etc. They knew about the defect for over a decade and a half, and only after lots of bitching to NHSTA, did we get them to do anything about it. Oh, and dealing with NHSTA was another barrel of monkeys. Call their 800 number, and you get an operator who cannot do a single thing except ask for your address and send you the forms to report a problem. Once you do, they completely prevent you from speaking to the investigator at NHSTA to communicate further details et al.
Please help metamoderate.
...hope your Hindi is pretty good!
Reality check:
When the stock car stereo in your new Ford emits magic smoke one week after you drive the car off the dealer's lot, do you contact your the Ford dealer network or Delphi?
Of course you know the answer. Not suprisingly, if you buy a Dell it IS Dell's fault. Dell claims to sell computers, not assembly services for a pile of Intel, Nvidia, and Seagate parts. Dell is even obligated to support the majority of the Microsoft software that it "merely" installs on those computers under the terms of the various licenses and supply agreements that it has negotiated. And we're not even discussing Dell, we're discussing APPLE. The mere suggestion that the end user should have to resolve a bug by contacting an OEM parts supplier, however famous, is laughable.
In fact, the bug was written by an out-sourced company in Taiwan. Did you try contacting them? Obviously Nvidia isn't the right company to contact... No wait, this just in. The bit of code was actually written by Michael Huang, a temp who works for a contracting firm. Please send him a letter describing your problem.
Next week on Slashdot.
I sent Michael Huang a detailed letter describing my problem and he shredded it without responding. Is this any way to treat the customers of your clients customers customer?
Bad drivers, perhaps?
nVidia doesn't do Apple drivers. They may have their engineers help write them, but they don't support or distribute them. Apple is solely responsible for supporting the hardware they ship with their systems because they want it that way. You go to nVidia's site you'll find drivers for Windows of all varieties, Linux 32 and 64-bit, FreeBSD, and even Solaris, but no OS-X. So when you have problems with nVidias on OS-X, it's Apple that you need to talk to.
(Couldn't access the article's screen capture - site's bandwidth exceeded.)
I did some googling around, and it appears that Mac Pro systems have been known to Kernel Panic in a number of cases after a memory upgrade. Have you considered that you might have TWO (intermittent) problems?
According to this http://www.xlr8yourmac.com/systems/Mac_Pro/mac_pro _ram.html upgrade memory should have larger heatsinks than standard heatsinked FB-Dimms. It has links to: memory test utilities, ECC correction reports, and most notably:
Questions:
Hope this helps!
If the Apple PC ever gets serious market share, it will attract serious regulatory attention. Its business model opens it to large monopsony power if it ever gets large, and judging by how they've rolled out Fairplay, they seem like they will become a another textbook example of why we need anti-trust law.
So there's a Token Ring network of evil?
09F91102 no, 455FE104 nope, F190A1E8 uh-uh, 7A5F8A09 that's not it, C87294CE no. Ah! 452F6E403CDF10714E41DFAA257D313F.
Good idea! If it's done properly, it could also be re-used as a GIMP icon.
"I've got more toys than Teruhisa Kitahara."