Slashdot Mirror


NVIDIA Responds To Linus Torvalds

jones_supa writes "NVIDIA's PR department has issued a statement following the harsh comments by Linus Torvalds last week where he referred to the graphics company as the single worst company he's ever dealt with, called them out on not supporting Optimus, and other issues. Basically the company replied they're committed to Linux using their proprietary driver that is largely common across platforms, and this allows for same-day Linux support with full OpenGL implementation. They also say that they're active in ARM Linux for Tegra and support a wide range of hardware under Linux. Despite having not made any commitment to better support Optimus under Linux nor providing technical assistance to the Nouveau community, NVIDIA assures us that 'at the end of the day, providing a consistent GPU experience across multiple platforms for all of our customers continues to be one of our key goals.'"

497 comments

  1. I'd agree with them on that.. by Anonymous Coward · · Score: 5, Insightful

    Basically the company replied they're committed to Linux using their proprietary driver that is largely common across platforms, and this allows for same-day Linux support with full OpenGL implementation. They also say that they're active in ARM Linux for Tegra and support a wide range of hardware under Linux. Despite having not made any commitment to better support Optimus under Linux nor providing technical assistance to the Nouveau community, NVIDIA assures us that 'at the end of the day, providing a consistent GPU experience across multiple platforms for all of our customers continues to be one of our key goals.

    Posting anonymously because some people are _incredibly_ opinionated on this subject, but not everybody has the opinion that everything linux related must be open source. Linus Torvalds, while a visionary and certainly one of the most technologically-minded people of our age, disagrees with this, and that's too bad. Just because Linus Torvalds thinks you're doing it wrong doesn't necessarily mean you are.

    Cheers.

    1. Re:I'd agree with them on that.. by kanto · · Score: 3, Insightful

      Posting anonymously because some people are _incredibly_ opinionated on this subject, but not everybody has the opinion that everything linux related must be open source. Linus Torvalds, while a visionary and certainly one of the most technologically-minded people of our age, disagrees with this, and that's too bad. Just because Linus Torvalds thinks you're doing it wrong doesn't necessarily mean you are.

      Cheers.

      Afaik Linus Torvalds has admitted on this topic that proprietary is better than nothing at all so try again, I think he's asking for simple co-operation.

    2. Re:I'd agree with them on that.. by TWX · · Score: 4, Interesting

      I don't need my graphics driver to necessarily be open-source. I need my graphics accelerator to function though, and it's been my experience that proper acceleration support has lagged. Simply bringing up a desktop in X is not the same as being able to navigate a 3d environment at-speed at the quality that the video card manufacturer touts. If they won't support 3d acceleration then I'm better off dusting off my old S3 Virge and buying a much more powerful microprocessor, letting the microprocessor do all of the work.

      If these cards don't do 3d acceleration in my computing environment, what good are they?

      And yes, I had this problem once before, with Matrox and the G450/G550 cards, back in the day. Aggravating as hell. Worse, if you were their corporate customer and asked for 3d accleration drivers they'd release them to you, but as a private consumer you had to justify the need. Apparently nothing that a noncommercial user did was considered justified. It was friggin' compiled! I wasn't even asking for source code!

      --
      Do not look into laser with remaining eye.
    3. Re:I'd agree with them on that.. by MickyTheIdiot · · Score: 2

      I don't have any problems with closed source projects in general; I think there would be a lot of needed software for small industries that wouldn't get written otherwise as open source needs a huge group of knowledgeable users to work. I don't get close-sourced drivers, though. I don't get it just from the side of a open source user OR from the business side. I just underwent another struggle with closed source ATI drivers over the past couple of days in which the regular Ubuntu installer wasn't working right and neither was their downloadable installer, so I am frustrated and a little biased this morning, but I don't see what they have to hide and I don't see how it hurts them to have various people working on their own version of the driver or sending patches in. I think it's shooting their REAL userbase (i.e. the people who recommend certain hardware vendors to people who don't pay attention to such things) in the foot.

    4. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 2, Insightful

      He should start looking at making a stable API for drivers, and draw a line in the sand to firewall GPL compliance.

    5. Re:I'd agree with them on that.. by Penguinisto · · Score: 5, Informative

      As sibling said - I don't think anyone particularly cares if they write closed-source software - just open the effing API and specifications, so the community can write its own drivers for it.

      Also, Nvidia is still not providing any Linux support for the one chipset that seems to be the most commonly used in laptops... go figure.

      --
      Quo usque tandem abutere, Nimbus, patientia nostra?
    6. Re:I'd agree with them on that.. by Yvanhoe · · Score: 5, Informative

      No support of Optimus means that on laptops, nvidia cards are either unsupported or power hungry. NVidia made a statement saying they will never support such a feature in their linux drivers. Nouveau has repeatedly asked for the specification information of this. Note that this information is not critical at all from a strategical point of view. No answer. NVidia's message is clearly "linux users are second zone citizens and we will not help them the slightest".

      Even when not thinking that everything linux should be open source, NVidia does not provide a working linux driver for its optimus cards (that is, 90% of cards sold in laptops today). With no open source solution and no closed source solution, we can simply stare as a fact that their support simply sucks.

      --
      The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
    7. Re:I'd agree with them on that.. by knuthin · · Score: 2

      ...but not everybody has the opinion that everything linux related must be open source...

      You're confusing Linus for RMS.

      If you see the video, you'll notice that he doesn't stress as much on open source drivers than he does about how Nvidia comes in his/developer's way. If Nvidia drivers aren't of such a poor quality, and the company would be so ignorant of the drivers *while depending on his product* in such a large way, he probably wouldn't be so pissed about the whole thing.

      --
      Some apps are WYSIWYG. Some others are WYSIWTF.
    8. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 0

      I have no idea why you're getting modded up for basically another emotional, inflammatory post. This has nothing to do with closed SOURCE versus open SOURCE. The point is that Nvidia's refusal to cooperate is resulting in complete NON-SUPPORT/compromised function of the Nouveau hardware under Linux.

      Think more, feel less.

    9. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 0

      I don't think Nvidia's current model is flawed to the point of being bad. I have had nothing but good luck with them under all OS's. But I think maybe Linus was off on a personal rant about how Nvidia's product could be better, how their business model could improve if they did these things. Not that not doing them is bad. Also that it would be better for the community as a whole. Linus is a techy guy, but maybe he needs to have some critical sit down and think time about his public speeches when it comes to non-kernal space stuff that he does not own, and is not in control over.

      This is a big pitfall all geeks fall into, even the crusty old ones.

    10. Re:I'd agree with them on that.. by gl4ss · · Score: 5, Insightful

      and I suppose this response from nvidia outlines why Linus is frustrated with nvidia.

      the response doesn't have anything to do with the issue he complained about and the response is just about waving hands to make people look the other way, "look, we do provide drivers! we provide the same drivers on the same day!(but please don't ask us about optimus)".

      (also, traditionally one reason for closed source and binary blob graphics drivers has been just plain old bullshitting and lies about what the card does on card with hw. also about selling same products for different clients for wildly different pricing).

      --
      world was created 5 seconds before this post as it is.
    11. Re:I'd agree with them on that.. by peppepz · · Score: 2
      Why should the Linux community take the burden to design, maintain and upgrade a "stable API for drivers" only to bend to the desire of a company that by their own admission doesn't care about Linux? The GPL is a resource for Linux, not a problem to be firewalled. There's plenty of closed source OSes out there which are much easier to use than Linux. The only strength of Linux is its being open source. Making it a closed source OS would mean to saw off the branch on which it's sitting.

      Ati learned the way of open source. Intel learned it even better. Nvidia doesn't want to? It must remain a problem of their own. The community has already responded to them with Nouveau.

    12. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 0

      I'm pretty sure Linus doesn't really care about whether the driver is FOSS or not (he just wants to make sure it's freely available to those who want it), but he is concerned that it doesn't play well with kernel updates, with the result that often updating your kernel will break nvidia's driver, as opposed to 90% of all the other proprietary drivers out there (number pulled from my ass).

    13. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 0

      Why should the Linux community take the burden to design, maintain and upgrade a "stable API for drivers" only to bend to the desire of a company that by their own admission doesn't care about Linux?

      Because this is a problem for ALL drivers and every other OS does the correct way. Why should hardware manufactures take the burden to design, maintain and upgrade drivers only to bend to the whims of the linux community?

    14. Re:I'd agree with them on that.. by Bill_the_Engineer · · Score: 2

      Actually he would make more than proprietary vendors happy. There are some open source drivers that serve a very limited audience that doesn't merit inclusion into the kernel source tree that would benefit from a stable API.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    15. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 1

      I don't need my graphics driver to necessarily be open-source. I need my graphics accelerator to function though

      I don't need my printer driver to necessarily be open-source. I need my printer to function though - oh, I do need open source printer drivers for that...

    16. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 1

      NVIDIA Optimus is supported in Linux, try a search with google, albeit not optimally: http://bumblebee-project.org/ . I for one will not buy another NVIDIA based laptop until it is officially supported, it has been am amazing hassle getting this to work at all.

    17. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 1

      The issue is not just the gpu hardware they sale, which seems to be fairly well supported, but the Tegra implementations several of which have been abandoned by the vendors and languish without opensource drivers. Tell owners of the gtab that Nvidia is "doing it right".

    18. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 1

      He should start looking at making a stable API for drivers, and draw a line in the sand to firewall GPL compliance.

      There is already "a clear line in the sand".
      That line has always been the ISA/PCI/AGP/PCI-E bus. Every other peripheral vendor defines the API to access the hardware. This means that if I build my own hardware I can just add a PCI-E bus and write my own code to use those peripherals, even if I am using an architecture that the vendor havent even heard of.
      The problem here is that NVIDIA is doing something they consider to be "tricky" within the drivers. Perhaps they are offlaoding some of the work to the CPU or covering up some bugs by pre/post processing the data with the CPU or whatever.
      Regardless they want to move the line into the operating system and this creates an artificial inertia in the development process. Basically NVIDIA asks Linus to slow down and/or restrict Linux development so that they can cheat with the peripheral development.

    19. Re:I'd agree with them on that.. by green1 · · Score: 3, Insightful

      Speaking as someone who was gullible enough to think that nvidia had linux compatible hardware, and who bought an nvidia card with the specific intent of running linux. I don't care one bit whether the drivers are open source, or closed source. I just want them to WORK. something that has consistently not been the case. The open source drivers miss hardware acceleration, and various video resolutions/modes on my card, and the closed source ones often don't have the acceleration working right either, and sometimes cause X to crash.

      I've learned my lesson, this is my last computer with an nvidia card in it.

      I don't care how you support linux, but if you claim to offer support, it should be every bit as good as the support you offer to any other operating system you support. If this isn't the case, then it should be noted, clearly, on the same table that brags about that support in the first place. I was sold my current card under false pretenses, based on lies on nvidia's website. I won't make that mistake again.

    20. Re:I'd agree with them on that.. by binarylarry · · Score: 1

      Because the Linux community are their customers and the customer is always right.

      --
      Mod me down, my New Earth Global Warmingist friends!
    21. Re:I'd agree with them on that.. by binarylarry · · Score: 1

      Replied to wrong comment.

      --
      Mod me down, my New Earth Global Warmingist friends!
    22. Re:I'd agree with them on that.. by David+Chappell · · Score: 4, Insightful

      Why should the Linux community take the burden to design, maintain and upgrade a "stable API for drivers" only to bend to the desire of a company that by their own admission doesn't care about Linux?

      Because this is a problem for ALL drivers and every other OS does the correct way. Why should hardware manufactures take the burden to design, maintain and upgrade drivers only to bend to the whims of the linux community?

      By and large the "whim" of the Linux community is "tell us how your card works on the register level and we will write the drivers ourselves." Most manufactures fell in line years ago when they figured out that they were being asked to do less, not more. Nvidia is one of the last holdouts.

      The most likely reason for their unwillingness to release specs is incompence. They have most likely never produced decent documention even for internal use. In other words, their developement process is disorganized. Producing good documentation might mean employing two or three extra persons. But, it would be worth it since not only Linux driver developers would benefit, their own developers would benefit. After all, the binary drivers of which they seem to be so proud do not exactly have a reputation for high quality.

    23. Re:I'd agree with them on that.. by peppepz · · Score: 1
      Because every other OS, even though doing things in what you call "the correct way", is now either defunct or living in a niche. Linux is successful ONLY because it's open source.

      The Linux community has no "whims" - they have even developed a working driver for NVIDIA products with no help whatsoever from them.

    24. Re:I'd agree with them on that.. by David+Chappell · · Score: 1

      He should start looking at making a stable API for drivers, and draw a line in the sand to firewall GPL compliance.

      That would be counter-productive since it would just make it easier for companies to supply junk drivers instead of documentation.

    25. Re:I'd agree with them on that.. by ArsonSmith · · Score: 1

      far from it. Linux doesn't think everything related to Linux should be open source. Just the hardware drivers and systems the interact directly with the kernel. Even at that he's put an exception to the GPL that linking is ok which is what lets nVidia release their derivative works in the first place.

      --
      Paying taxes to buy civilization is like paying a hooker to buy love.
    26. Re:I'd agree with them on that.. by progician · · Score: 1

      That's the thing. They shouldn't. They should just fucking release the how-to for their bloody products. We would do the rest. But what they don't want is that customer made drivers would not have preferences for games against others and other anti-competition deals what they have now.

    27. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 0

      While h4rr4r was harsh, I agree, because: If you think having multiple black boxes (you can't look into) in the same "process" at kernel level is good, you definitely like pain. If there are "drivers serving a very limited audience", then abstract the part that actually needs to be in the kernel (probably very little) and put that into the kernel source tree anyway (see hiddev).

      If it actually needs hooks into the core and is not in the kernel source tree, it's something the kernel developers can't see that's nevertheless there, under their bed, waiting to strike. Bad idea.

    28. Re:I'd agree with them on that.. by Teun · · Score: 1
      I've got a Thinkpad W520 and must say installing Bumblebee and getting it to work was as simple as following the instructions on their git site.

      Due to the nature of the Bumblebee hack it is not as fast as booting straight into the discrete driver but for most 3D programs it works sufficiently.

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    29. Re:I'd agree with them on that.. by Dunbal · · Score: 1

      Why should the Linux community take the burden to design, maintain and upgrade a "stable API for drivers" only to bend to the desire of a company that by their own admission doesn't care about Linux?

      For the same reason that Microsoft did it with DirectX. Maybe you're too young to remember, but I remember back when Windows was pretty shitty and running any 3D app on Windows was a nightmare. DirectX changed all that. Not because DirectX is the perfect solution to anything but Microsoft threw money at the problem and put a team together and marketed it to fledgeling graphics card makers and hey, it turned into something.

      Saying that linux devs shouldn't have to budge at all and that the graphics manufacturers (who really don't need the currently tiny linux market at all) have to do all the work is ridiculous. If you want the reward, you have to put in the work. And apparently until linux gets real graphics support and not the patchwork mish mash currently available through wine, cedega, etc, it will always be a niche and restricted to a tiny, tiny market. In fact some are speculating that it's too late because the PC at home is dying to the tablet and smart phone...

      --
      Seven puppies were harmed during the making of this post.
    30. Re:I'd agree with them on that.. by Dunbal · · Score: 1

      the customer is always right.

      (Points to the sign that says "Management reserves the right to refuse admission")

      Yeah the customer is always right. But we don't serve your kind here. Get out.

      --
      Seven puppies were harmed during the making of this post.
    31. Re:I'd agree with them on that.. by Bill_the_Engineer · · Score: 2

      For example:

      Some of these drivers are from board support packages of PC-104 CPU boards or serial synchronous cards that have extended functions that require direct access to the hardware. They have always ran well as a kernel module and they are pretty much self contained. However if the hardware needs to be included in a system which uses a new kernel and the other hardware contained in that system requires the newer kernel, the user will most likely (and have on many occasions) change constant variable names and kernel call parameters which were only changed to inconvenience the proprietary vendors.

      I hear what you are saying, but your concerns do not apply in this case. I'm not petitioning the Linux kernel developers to stop their practice because after more than a decade that policy will never change despite the fact that a decade has passed and NVIDIA and others still provide binary blobs and make their own wrappers to handle the API changes. Evidently the changes to the API only affect the smaller companies and niche projects.

      I was pointing out that NVIDIA and others would not be the only beneficiaries of a stable API.

      If I wasn't a Linux supporter for all these years and cooperated and was helped by the mainline developers on several occasions, I would have switched to a BSD OS a long time ago...

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    32. Re:I'd agree with them on that.. by Tapewolf · · Score: 1

      The open source drivers miss hardware acceleration, and various video resolutions/modes on my card, and the closed source ones often don't have the acceleration working right either, and sometimes cause X to crash.

      What was the card? I've been using nVidia for years now, because although the closed-source driver is a PITA to set up and occasionally needs care and feeding if the OS updates (e.g. the kernel and when Ubuntu updates X), once it is working it is screams and has been very reliable.

      I've been using the 6200, the 7600 and now the GTX550TI. I forget what before that, but I've only been using nVidia cards for at least a decade because if it won't work well in Linux it's a waste of money and gaming-level cards aren't cheap.

    33. Re:I'd agree with them on that.. by Grishnakh · · Score: 2

      I think this is BS. I don't recall Linux ever saying that "everything linux related must be open source", in fact I think he's pretty pragmatic about the whole thing and has nothing against proprietary software running on top of Linux. You're thinking of RMS, who wants all software to be open source and under the GPL license; Linus and RMS are very different.

      What Linus does think, however, is that all kernel-space drivers in Linux should be part of the kernel. That's a very different issue than proprietary applications, and it makes a lot of technical sense too. Remember, the main reason Microsoft got such a bad rap with Windows being unstable was because of dodgy third-party device drivers; they run in the kernel space, so it's easy for a poorly-written driver to make the system unstable. They finally mostly fixed it with their WHQL program, but that uses an incredible amount of resources, since basically you have to get MS to test out your drivers for you in order to advertise that your device is Windows-compatible. MS has the resources and ability to set up a giant testing program to do this; the Linux kernel people don't (and even if they did set up such a program, very few manufacturers would pay the fees needed for the testing since they don't think it's worth it for Linux's small marketshare; MS has the clout to get the OEMs to pony up big fees for this service). So, the best solution is to make all drivers part of the kernel. This works great with most things, but with GPU drivers it's turning out to be a problem.

    34. Re:I'd agree with them on that.. by LordLimecat · · Score: 2

      The fact that we have a binary blob driver of such high quality (compared to the ATI experience)-- and have for recorded history-- indicates that they DO care about linux.

    35. Re:I'd agree with them on that.. by LordLimecat · · Score: 1

      Perhaps they are offlaoding some of the work to the CPU or covering up some bugs by pre/post processing the data with the CPU or whatever.

      Im pretty sure that would badly hurt performance, not help it. Video cards tend to be orders of magnitude faster at dealing with graphics data than the CPU.

    36. Re:I'd agree with them on that.. by Grishnakh · · Score: 1

      Wrong. Greg K-H has explicitly said he doesn't care if a driver serves an audience of 2, he still wants it in the kernel because of network effects: code in that driver may be useful somewhere else, or may be useful in creating a new subsystem that many small-market drivers use.

      A stable API is not a good thing. Microsoft had that back in the pre-WHQL days, so any vendor could just release drivers willy-nilly, and the result was not good: Windows crashed all the time, MS was blamed for making crappy software, when in reality many of the problems weren't with MS's software, but with poorly-written third-party drivers. Allowing anyone (esp. hardware makers, who seem to almost always do a terrible job writing software for some reason) to release kernel-level device drivers without any quality checking has proven to be a disaster.

    37. Re:I'd agree with them on that.. by Grishnakh · · Score: 1

      This is a good point, but what I think you were getting at is that the binary Nvidia drivers are hard-coded to cheat on many benchmarks. Open-source drivers wouldn't have this, and would show the hardware's true performance instead of taking shortcuts that result in higher numbers on certain benchmarks, and of course, Nvidia wouldn't like that.

    38. Re:I'd agree with them on that.. by Grishnakh · · Score: 1

      They don't have to do any work at all. They only have to release their specs.

    39. Re:I'd agree with them on that.. by Bill_the_Engineer · · Score: 1

      Wrong. Greg K-H has explicitly said he doesn't care if a driver serves an audience of 2, he still wants it in the kernel because of network effects: code in that driver may be useful somewhere else, or may be useful in creating a new subsystem that many small-market drivers use.

      Not exactly wrong. If I'm paid to make the driver work on the current version yet am not paid to maintain the driver for inclusion in the working tree, and no other developer volunteers then said driver is not accepted in the tree. It took a while for LinuxPPS to be incorporated into the tree so I'll use that as an example.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    40. Re:I'd agree with them on that.. by Grishnakh · · Score: 1

      There's something else "tricky" that NVIDIA is doing in their drivers: cheating on certain benchmarks. It's been documented many times.

    41. Re:I'd agree with them on that.. by Andy+Dodd · · Score: 2

      In addition, despite their claims of supporting Linux on ARM, their Tegra open source support is piss-poor compared to TI's OMAP4 support.

      Their mainline cpuidle support is still shit. They also have not published any TRM whatsoever for the chip, unlike TI who provides a comprehensive OMAP4 TRM.

      Hell - they're so diverged from mainline that products running ICS are still running 2.6.39 kernels unlike 3.0.8 which is the official standard for Android devices running ICS.

      --
      retrorocket.o not found, launch anyway?
    42. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 0

      I agree with you. This is the norm in the BSD world. NVIDIA at least provides drivers for FreeBSD, but at the speed the Linux people reinvent the wheel, it will be years before we have graphics support again for any video card at even low speeds. I wish Linus luck, but the Linux community complaining about graphics support is like Microsoft doing it. You guys get some vendor support and it's years ahead of what the rest of us have. You're never happy.

    43. Re:I'd agree with them on that.. by Grishnakh · · Score: 0

      So you want the Kernel developers to do a lot of extra work so some paid developer doesn't have to do as much work to maintain his out-of-tree driver? I'd say that warrants a big "FUCK YOU".

      The kernel devs are right: if you want to maintain a driver out-of-tree, because you're too fucking lazy or stupid to submit it for inclusion upstream, then YOU should be the one jumping through hoops, not them.

    44. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 0

      Did it occur to anyone that optimus (as written) won't work on Linux. Basically you have to have hardware carveout memory shared between the two graphics units (nvidia and intel integrated) and that memory model doesn't mesh with the linux driver memory model (and maybe even the open source intel integrated driver). Also you have to (virually) unplug the graphics which means state-save and state restore which isn't just limited to the graphics, but the PCIe hot-plug driver as well. No doubt nvidia got these working on windows with great effort, but there's no such infrastructure in Linux to fit their driver into, and there's little incentive for nvidia to do this work (so other vendors can just plug into that infrastructure and learn how to do this for windows).

      So if the linux community would just provide the infrastructure for Optimus for the nvidia driver, you might just see that feature pop-up in their closed source driver.

    45. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 0

      I don't know why people call nVidia blobs so "great" their hardware plus software experience on Windows is abysmal. I swear the only people who call nVidia drivers "stable" have only used nVidia. Their crap is the opposite of stable, the Linux experience manages to be even worse.

    46. Re:I'd agree with them on that.. by Cybah · · Score: 1

      There's also the issue of Linux support, not just to developers, but even the end users. As an end user, I've repeatedly been ignored by Nvidia when submitting detailed bug reports about their drivers, both to the support forum and by e-mailing linux-bugs@nvidia.com. Oh, and even on Twitter. Not even a "thanks, but we're not fixing this". Stone-walled. I won't be making the same mistake next time I buy hardware.

    47. Re:I'd agree with them on that.. by jmorris42 · · Score: 2

      > the graphics manufacturers (who really don't need the currently tiny linux market at all)

      Eh? You mean every tablet without a fruit on it and most smartphones? The only platform that isn't fruit based that is growing? That tiny market? We have a different definition of tiny.

      > available through wine, cedega, etc

      Oh, I see your problem. You want to play games released for Windows but for unexplained reasons find dual booting unacceptable. You you have this expectation that until Linux becomes exactly like Windows, while not becoming whatever it is you find unacceptable about it of course, it is simply terrible.

      > the PC at home is dying to the tablet and smart phone...

      Not at all. The market is simply sorting itself out after a long nightmare of Microsoft's monopoly. Most people with a Windows PC should have never had one, they needed a simple game player and media consumption device, but that device was never allowed to be birthed. The people who actually need the power of a PC will still want it, but it will be at most 10-20% of the population.

      --
      Democrat delenda est
    48. Re:I'd agree with them on that.. by peppepz · · Score: 1, Insightful
      We have OpenGL to match MS' DirectX. We share the OpenGL baseline with anything not made by Microsoft (e.g. Android, iOS, OS X) and that's the API exposed by closed drivers, too, so I don't think you can say that *game developers* can't code on Linux because of the lack of a stable API for drivers; they're two completely different problems.

      Saying that linux devs shouldn't have to budge at all and that the graphics manufacturers (who really don't need the currently tiny linux market at all) have to do all the work is ridiculous.

      First, nobody said that graphics manufacturers have to do any work. As you know, linux devs have already done a reverse engineered driver for NVIDIA hardware without any help. Second, the Linux market isn't tiny at all if you consider that most of the Tegra hardware that NVIDIA sells will end up running Linux (for Android).

      The example of AMD and Intel shows that the supposed problems about IP protection were little more than the FUD we all believed them to be.

      In fact some are speculating that it's too late because the PC at home is dying to the tablet and smart phone.

      I have to agree with you on that, and I deeply regret it, as I currently see no alternative to the PC and I'm afraid that we might end up in a world where all commodity hardware is of the "walled garden" kind. Looks like those in the "software is a tool" camp will finally get all the tools they seem to love so much; maybe they'll start to appreciate the value of open source again once they experience life without it.

    49. Re:I'd agree with them on that.. by metamatic · · Score: 1

      So if the linux community would just provide the infrastructure for Optimus for the nvidia driver, you might just see that feature pop-up in their closed source driver.

      So Linux devs should do a bunch of work for free, to help nVidia release closed-source-only drivers? Fuck that.

      If nVidia release the specs for their hardware, then Linux devs will add the necessary infrastructure for Optimus, and nVidia can also use that infrastructure in their closed-source drivers. But it has to be a two-way win-win cooperation. The Linux developers don't exist to serve nVidia's selfish whims.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    50. Re:I'd agree with them on that.. by mdragan · · Score: 1

      Where did you get the impression that this was about open source at all? nVidia had no/crappy Linux support for one of their products. When a group of volunteers started to work on fixing that, nVidia didn't help them at all. That's the problem, they could have fixed it themselves but they didn't, well not in the "same-day" support they are claiming (I understand that after half a year they released something that doesn't work well), and they didn't help volunteers that would do it for them (probably because of the open-source concern).
      So I guess Linus would be happy with any kind of support, open or proprietary, but nVidia refuses both.

    51. Re:I'd agree with them on that.. by morgauxo · · Score: 1

      Sure, people are opinionated but it's not always for abstract OSS moral reasons.

      I would love to see good open drivers for all the common GPUs of all brands. With Nvidia my main reason is I hate upgrading my kernel, rebooting and seeing X blink in and out several times trying to start and having to wait for it to time out. 'Oh, yah, once again I have to rebuild that @#$@ nvidia-drivers wrapper so that it matches my new kernel'. It would be so much nicer if it were just built in like all the 2d drivers!

      Secondly, long term support. Not every use needs the latest and greatest hardware. One nice thing about the OSS community is there are lots of pack rats. If the driver is OSS then it WILL be available tomorrow. I only put this reason second because Nvidia has been surprisingly good about keeping support for old cards around. Few companies support their old hardware so well. Still, that could change at any time and there is nothing the OSS community can do about it because the software is closed. I really hate having to chose between keeping my hardware which is fast enough for my application but being stuck with old OS version that have known bugs and security holes or shelling out $100s to replace 1/2 my hardware because the proprietary drivers haven't been ported to the new OS.

      Third, why does open source have to be a one horse race? It would be nice to see open specs so that maybe some other OS could have native drivers and give Linux some competition. Syllable perhaps? Maybe someday...

      Oh... I almost forgot.. and being able to use Xinerama and RandR (multi-monitor, resolution and rotate settings) from Xorg, not Nvidia's proprietary alternative would be great. My desktop manager (KDE) has seamless support for controlling those built into it's control panel just like one would expect on either of the mainstream proprietary OSs. I'm sure Gnome and others are the same. That would make a much nicer user experience than having those controls not work plus having to either run nvidia-settings or edit xorg.conf by hand to get those effects. This is the kind of thing, I think that makes Linux seem immature as a Desktop OS and the developers really have no control to fix it so long as Nvidia will not cooperate.

      What I don't understand is why GPU manufacturers are so secretive with driver code. It's the instructions on how to use their product, not instructions to duplicate it right? I would think releasing this information just makes their hardware more useful to a wider variety of users and thus more valuable. It must be that they are putting significant portions of their functionality into software rather than hardware. That seems like kind of a ripoff to me. I don' t want my CPU doing graphics, that is what I bought a GPU for.

    52. Re:I'd agree with them on that.. by David+Chappell · · Score: 1

      I'm pretty sure Linus doesn't really care about whether the driver is FOSS or not (he just wants to make sure it's freely available to those who want it), but he is concerned that it doesn't play well with kernel updates, with the result that often updating your kernel will break nvidia's driver, as opposed to 90% of all the other proprietary drivers out there (number pulled from my ass).

      Most drivers don't break between kernel versions because they can be distributed with the kernel and the kernel developers can fix problems with them. The kernel developers dislike the closed-source drivers because they are huge, complicated, and opaque. They would like the hardware manufacturers to answer questions about how the hardware works so that they can write their own lean drivers. They just need to know what all of the 'buttons' do./p.

    53. Re:I'd agree with them on that.. by peppepz · · Score: 1
      High quality, unless you're an Optimus user (Linus' harsh words were the response to an angry Linux user who wasn't satisfied with her Optimus experience).

      They admit themselves that they can't provide a proper Linux driver (as everybody else is doing these days) because they're more interested in reusing the Windows driver than in supporting Linux specifically. Talking about recorded history, do you remember when they didn't release specs for their *ethernet chip* years ago? I don't think there could be precious IP hidden there, or that they were interested in sharing some advanced Ethernet infrastructure between Linux and Windows.

      In summary, I don't read all this love for Linux in their behaviour. If they care for Linux, then they care less than everyone else.

    54. Re:I'd agree with them on that.. by Lisias · · Score: 1

      NVidia is twisting the argument, and you bite it.

      I saw the video. All of it.

      Linus complained for NVIDIA being a pain in the ass by not providing minimally decent support when *their* closed source drivers crashes the kernel.

      Torvalds don't give a shit (literally) if your driver is open or closed sourced - all it cares if that the damned thing works as expected!

      --
      Lisias@Earth.SolarSystem.OrionArm.MilkyWay.Local.Virgo.Universe.org
    55. Re:I'd agree with them on that.. by Bill_the_Engineer · · Score: 1

      So you want the Kernel developers to do a lot of extra work so some paid developer doesn't have to do as much work to maintain his out-of-tree driver?

      In this case the paid developer is only using the driver and doesn't actually own the driver. The hardware vendor has no interest in maintaining their drivers, and the paid developer who merely uses the driver has no time or guaranteed access to the required hardware to maintain it well enough to submit it to the kernel development tree. Since I'm sure no other developer will take up the cause of basically working for a manufacture for free just to have a current driver in the tree, the driver will never be in a shape that allows for its continued presence in the repository.

      You have confused a third-party user of a driver with the first-party developer that a hardware vendor hired to make a single driver a long time ago for the expressed purpose of advertising that their hardware works with Linux.

      I'd say that warrants a big "FUCK YOU".

      Already abused by the hardware vendor there is no need to be abused by a pissant. The rest of your response is invalidated by the fact that you made incorrect assumptions.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    56. Re:I'd agree with them on that.. by sander · · Score: 1

      The parts of Linux community that really are Nvidia customers in a serious way are also dependent on the availablity of a complete, standards compliant openGL implementation, which means they not only depend on the Nvidia driver, but also the libraries, that Nvidia is not likely to support on top of anything except their driver.

      Which in turn makes what Linus, and the rest of not-really-serious nvidia users running Linux thinks about the situation, utterly irrelevant.

    57. Re:I'd agree with them on that.. by chmod+a+x+mojo · · Score: 1

      Funny, I had the opposite.

      Sent in a nice detailed bug report back when they had a "fix" for VDPAU tearing when compositing was enabled in Xorg that didn't work, and interacted directly with some of the driver devs with provided test drivers. The next release of the binary driver had the problems fixed.....

      --
      To err is human; effective mayhem requires the root password!
    58. Re:I'd agree with them on that.. by shaunbr · · Score: 1

      No, he need not cripple himself and developers, but he shouldn't expect vendors to support him, either.

      It's shit like this that guarantees that Linux will never be a mainstream desktop OS. All of you get too hung up on ideology and purity of beliefs, and then wonder why nobody wants to support you.

    59. Re:I'd agree with them on that.. by V!NCENT · · Score: 1

      We're not talking about Linus wanting nVidia to open up their driver. We're talking about something as extremely simple as how to even interface with it. How is Linux as a kernel, even damn able to recognise it, so it can load appropriate drivers? How is Linux able to put it in standby mode and get it out of it?

      We're not talking about OpenGL here; we're talking about some stupid PCI identifier codes and basic register numbers. That's it! Sure there is the basic nVidia's open source display driver, but that's not the damn point for kernel devs.

      Notice how Linus said "work with". nVidia PR just responds like it's a matter of "Please go open source", which is totally besides the damn point.

      --
      Here be signatures
    60. Re:I'd agree with them on that.. by shaunbr · · Score: 1

      Because every other OS vendor does it. Maybe you like broken, half-baked operating systems, but some of us like to get real work done, not tinker with drivers and be forced to use outdated hardware.

    61. Re:I'd agree with them on that.. by shaunbr · · Score: 1

      Windows and MacOS are defunct and living in niches? The amount of delusion here is stunning. Linux is the niche OS, and it's ideological stands like this that are directly to blame.

      Bitch all you want about how proprietary vendors aren't being fair, but understand that the Open Source community has taken a stance, and that stance is largely incompatible with the stance of every major hardware developer in the market. It's not their job to cater to the 2 or 3 percent of PC users that have chosen to use Linux for one reason for another.

    62. Re:I'd agree with them on that.. by shaunbr · · Score: 1

      It's not always as easy as 'release the specs'. Many devices have licensed code and components, and IP agreements prevent information about such code from being released. A good example of this is hardware support for video codec acceleration. Good luck getting Nvidia or AMD to break their contracts just to meet the needs of a small niche of computer users.

    63. Re:I'd agree with them on that.. by shaunbr · · Score: 1

      Why would I want to dual boot to play games when I can stay in one OS (Windows) that does all the useful stuff that Linux can do *and* do things that Linux can't? I'm long past the point where I want to tinker with an OS just for geek cred. I want my computer to work and to do everything I want it to do without having to waste time rebooting between two operating systems.

    64. Re:I'd agree with them on that.. by shaunbr · · Score: 1

      Having used a number of AMD/ATI and Nvidia cards on Windows, Nvidia wins hands down. I've never had a good experience with AMD devices -- more than half the games I own required me to disable the second card of a Crossfire setup (dual 6870s) because AMD had never released a proper compatibility profile. This includes games like Skyrim! There's no excuse for poor Crossfire support in big name, AAA titles, especially when your competitor consistently manages to get it right.

      I've been burned by shitty AMD drivers more than once in the past. Never again.

    65. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 0

      By and large the "whim" of the Linux community is "tell us how your card works on the register level and we will write the drivers ourselves."

      Yea and that's working really great for those ATI drivers.

    66. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 0

      The "Linux Community" is not their customers. Apple, Dell, HP, IBM, Samsung, LG, Motorola, Acer, Lenovo, HTC, etc.. are their customers. So they only need to get a working version for whatever those people are shipping.

    67. Re:I'd agree with them on that.. by fast+turtle · · Score: 1

      I'm a business user and have to wonder what you've been smoking. Simply put, Linux has cedded the market in regards to regulatory compliant software that I must have from a business standpoint. If there was compliant software from a FLOSS vendor, I'd be quite willing to purchase it in a heartbeat but it simply isn't there, thus I have no choice on OS because there's no competition in the application space I need. Sorry but Laws and Regs tend to trump ideology and religion every damn business day.

      --
      Mod me up/Mod me down: I wont frown as I've no crown
    68. Re:I'd agree with them on that.. by ChrisMaple · · Score: 1

      The most likely reason for their unwillingness to release specs is incompence.

      In things like written English?

      Nvidia is one of the last holdouts.

      It's worth noting that Nvidia is the only remaining major independent video hardware manufacturer. I don't like the secrecy, but it's hard to argue with success.

      --
      Contribute to civilization: ari.aynrand.org/donate
    69. Re:I'd agree with them on that.. by jmorris42 · · Score: 1

      Mind telling me where in the wide, wide world of sports that rant fits into this thread of conversation?

      Does it have ANY bearing on the discussion of NVidia's refusal to tell their customers how their product actually works? Does it even impinge in any way on what the fanboy I was taking to task was complaining about?

      Sorry if you are in some field of work where you are stuck with a mandated vertical app, suck it up and either live with it or help fund a replacement. Odds are if it is on Windows it is insecure and sucks, am I right? But that is a topic for another thread so stop hijacking random ones to shill in.

      --
      Democrat delenda est
    70. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 0

      "not everybody has the opinion that everything linux related must be open source."

      Wtf does open source have to do with anything besides the obvious? One stupidly small hardware change made anywhere important means that every binary driver made in the past doesn't work. It's a hostage situation unless you know what works and what's been done before.

      If you don't think that either ATI or NVidia just *not working at all* doesn't matter to people that use linux - you're stupidly and deliberately insane.

      Is it "linux's" fault that supporting unknown binary code that can arbitrarily change without any warning is tough?

      Geez.

    71. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 0

      wtf are you smoking?

    72. Re:I'd agree with them on that.. by peppepz · · Score: 1

      I don't know what you're talking about. Linux doesn't require you to "tinker with drivers". Linux comes with the drivers for all the hardware it supports built-in. There is no tinkering required, the driver is loaded when you attach the hardware and is unloaded when you unplug it. This is a vastly superior model compared to the anarchy of broken, half-baked operating systems that require you to hunt the correct driver for each piece of hardware you own. Especially for people who need to get real work done. In Linux, the "tinkering" is only required if you're the unfortunate owner of a piece of hardware that requires a binary blob, such as an NVIDIA video card. Your complaints are to be directed to the manufacturer of that blob: Linux is not meant to be used that way.

    73. Re:I'd agree with them on that.. by peppepz · · Score: 1
      Mac OS is open source, didn't you know? Its drivers aren't, and in fact Mac OS' driver coverage is very poor. Apple's previous attempt at a closed source OS failed (copland).

      Windows is on its way out, now that more and more people are buying Android-based tablets or smartphones instead of a PC, and it is my opinion that the Metro cure won't do anything to change that. A 60% share of that market is made up of Linux devices. So you think that "it's not NVIDIA's job to cater to the 60% of mobile device users that have chosen to use Linux". Oh well, talk about delusion.

    74. Re:I'd agree with them on that.. by David+Chappell · · Score: 1

      The parts of Linux community that really are Nvidia customers in a serious way are also dependent on the availablity of a complete, standards compliant openGL implementation, which means they not only depend on the Nvidia driver, but also the libraries, that Nvidia is not likely to support on top of anything except their driver.

      Interesting. Perhaps that explains the sharp split I see in this forum between those who insist that only Nvidia makes a card usable on Linux and those who (like me) see the Nvidia drivers as buggy garbage that is not worth installing. The first group must be willing to tolerate the bugs in order to get some features that the average desktop user does not need.

    75. Re:I'd agree with them on that.. by diego.viola · · Score: 1

      If Linus is against of out of tree modules such as the nvidia one, wouldn't it be better if he removes this exception? i.e. forcing nvidia to cooperate.

    76. Re:I'd agree with them on that.. by diego.viola · · Score: 1

      Where can I read this exception?

    77. Re:I'd agree with them on that.. by AvitarX · · Score: 1

      How's that worked for ATI/AMD?

      To get good (choosing the word good, not decent intentionally, I will call at least some of the supported cards decent in the FOSS version) performance, and hardware decoding (this is not the open driver's fault, but lack of documentation), I use the closed driver for my AMD card. AMD still has to maintain their closed one, and give out the info, and if I'm not mistaken additionally helps on the open version. The open community appears to not be able to make full-speed full-featured video drivers, therefore the companies do not get a time/cost savings throwing it to the community.

      Also, I wish Intel's integrated graphics were better, they appear to be the only company that really does FOSS drivers right (gma 500 excluded), especially like their vaapi being for encoding too.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    78. Re:I'd agree with them on that.. by shentino · · Score: 1

      I'd bet that nvidia is hogtied by nondisclosure agreements with other companies.

    79. Re:I'd agree with them on that.. by shutdown+-p+now · · Score: 1

      Because, apparently, the "Linux community" doesn't care about NVidia drivers - enough so for Linus to ask a question about them, and enough for him to publicly say "fuck you".

    80. Re:I'd agree with them on that.. by Grishnakh · · Score: 1

      Um, I think there's some confusion here. I'm not talking about driver users (end users), I'm talking about the paid developer who works for the hardware mfgr, and who's developing a driver to enable the HW's use in Linux. A stable API benefits him because it makes his job much easier if he intends to keep his driver out-of-tree. However, it creates a giant amount of work for the kernel devs to support that. That's why they don't do it, and tell everyone to submit their driver to be in-tree. Microsoft maintains stable APIs because they support the closed-source model, and they can do it because they can afford to hire an army of developers to do nothing but maintain that API (or rather, multiple versions of it to support backwards compatibility). The simple fact is, you're not going to find a bunch of Linux devs willing to volunteer their time to do absolutely nothing productive, and instead spend all their time doing something that will only benefit companies that refuse to submit their drivers for inclusion in the kernel tree.

      If you (any reader, not just the one I'm replying to) think it's sooo important to maintain a stable API, why aren't you volunteering for the job? If you aren't willing to dedicate your free time to the job, then clearly you don't think it's that important. It's interesting how people are so willing to criticize how an open-membership project uses its resources (many of which are unpaid volunteers), but are never willing to step up to volunteer to do it the way they think it should be done.

    81. Re:I'd agree with them on that.. by Grishnakh · · Score: 1

      What "code"? They're only asking for specs to be released, not source code (though that'd be nice too). You don't need source code to access a hardware device, you only need specifications.

    82. Re:I'd agree with them on that.. by LordLimecat · · Score: 1

      I challenge you to find a single forum posting from the last 6 years that recommends an ATI card over an nVidia card on a Linux box.

    83. Re:I'd agree with them on that.. by humanrev · · Score: 1

      NVidia's message is clearly "linux users are second zone citizens and we will not help them the slightest".

      This, right here, is the real reason I think that people ignore Linux on the desktop: No-one likes being treated as a second-class individual. Considering yourself to an operating system/distro that has such few users that you are continually passed over in terms of quality commercial software, fully-functional hardware and all the perks that these two elements provide, then the frustration can be enough to say "fuck it" and move back to Windows or even OS X.

      Experienced, determined and stubborn Linux users are used to it and although frustrating, it's generally not enough to deter them from continuing to use something that very few vendors take seriously on the desktop at least. But most people can't handle that lack of support, and although elated at finding something like Ubuntu, if they start to actually use the system for a while and plug in new devices, look for software to do a particular job and they find it non-existent or substandard in Linux, the novelty will wear thin. And all because of companies like NVidia and others treating Linux users as second-class folks.

      Until this attitude with vendors changes, nothing else will.

      --
      Most people on Slashdot are fucking idiots.
    84. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 0

      They have absolutely terrible linux support for tegra (unless you count android, which is hardly the linux in question). I have been waiting a long time for any kind of linux distribution (arch to xubuntu) for my tegra 2 chip in my tablet. Plasma and ubuntu have touch built in but what is holding them back is graphics acceleration, and that is due to nvidia being closed lips bitches on the finer details. that said there isn't much openess in the soc market samsung is a little better than nvidia, only Texas instruments or intel really give the devs what they want.

    85. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 0

      this man is very very right.

    86. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 0

      not only the gtab, notionink adam, viewsonics tablet, asus transformer, acer Asomthing, the list goes on. There is a lot of people working on opensource stuff for tablets running tegra but with nvidia being a little bitch these people still dont have graphic acceleration. Companies that use tegra beware your going to lose the hardcore market.

    87. Re:I'd agree with them on that.. by peppepz · · Score: 1

      They care enough to write a NVidia driver of their own, NVidia's disinterest notwithstanding. That is, they care more than NVidia themselves, who can't be bothered to write a proper driver beyond a shim around their Windows one, with the result that they provide no solution for their customers having Optimus-capable chips.

    88. Re:I'd agree with them on that.. by David+Chappell · · Score: 1

      I'd bet that nvidia is hogtied by nondisclosure agreements with other companies.

      Possiblly, but I tend to doubt it. First of all, they presumably would have said so if they were. Second, what they are asked to disclose is not potentially secret internal details but basically an API: the commands which must be sent across the PCI bus in order to make their card do things. In my experience, such documentation does not reveal that is not already available from other sources such as: the published higher-level API, product data sheets provided to buyers, and advertising copy.

    89. Re:I'd agree with them on that.. by David+Chappell · · Score: 1

      How's that worked for ATI/AMD?

      To get good (choosing the word good, not decent intentionally, I will call at least some of the supported cards decent in the FOSS version) performance, and hardware decoding (this is not the open driver's fault, but lack of documentation), I use the closed driver for my AMD card. AMD still has to maintain their closed one, and give out the info, and if I'm not mistaken additionally helps on the open version. The open community appears to not be able to make full-speed full-featured video drivers, therefore the companies do not get a time/cost savings throwing it to the community.

      You raise an interesting point which surprises me somewhat. Frankly I have been impressed by the progress made since ATI/AMD started releasing documention in 2007. Before they did, I had to buy Radeon 9200 cards (from 2003) if I wanted hardware accelaration. New cards didn't work at all with opensource drivers. But now it seems that I can take a new computer with a recent ATI card, install Debian or Ubuntu on it, and it just works with full resolution, hardware accelaration, and OpenGL with a high frame rate. It also smoothly runs multiple monitors. I don't know what more I could ask for.

      In my ignorance I have recently concluded that the best solution to problems with the ATI binary driver is to remove it. Other than that the problems go away, nothing changes. I know that the ATI binary driver has higher benchmark numbers, but I know of no real-world scenario in which the opensource driver produces less than 60 frames per second.

      It seems to me that the last 4 1/2 years have been spent getting documentation written and released, implementing drivers, getting those drivers stable, and getting them intergrated into Linux installers. As a developer myself, I know that is a lot of work. I would not expect to have performance parity with the binary drivers by now. I would expect it soon though.

      So, I am very interested and surprised by the idea that there is a long-term need to maintain the binary driver. I think I am a typical user, and as far as I am concerned, they can drop it today. I gather that I am also wrong.

    90. Re:I'd agree with them on that.. by Lisias · · Score: 1

      where I wrote "all it cares if", please read "all it is cared is if".

      (my English is improving! I swear!)

      --
      Lisias@Earth.SolarSystem.OrionArm.MilkyWay.Local.Virgo.Universe.org
    91. Re:I'd agree with them on that.. by Raven17 · · Score: 1

      This needs a +500.

      And a beer.

      Well said!

    92. Re:I'd agree with them on that.. by ArsonSmith · · Score: 1

      it was actually not an exception but a definition of a boundary between derivative work and original work. nVidia is accepted due to the binary blob driver originally coming from windows and the nVidia obfuscated interface to it is open source/GPL.

      --
      Paying taxes to buy civilization is like paying a hooker to buy love.
    93. Re:I'd agree with them on that.. by diego.viola · · Score: 1

      Well, but this definition is not defined in the license or anything right? It was just part of some conversation as I understand it?

      What does the GPLv2 says about this? Woulnd't switching to the GPLv3 force them to cooperate?

      It seems that if they won't cooperate we gotta be tougher in this one.

    94. Re:I'd agree with them on that.. by Bill_the_Engineer · · Score: 1

      If you (any reader, not just the one I'm replying to) think it's sooo important to maintain a stable API, why aren't you volunteering for the job? If you aren't willing to dedicate your free time to the job, then clearly you don't think it's that important. It's interesting how people are so willing to criticize how an open-membership project uses its resources (many of which are unpaid volunteers), but are never willing to step up to volunteer to do it the way they think it should be done.

      It's blatantly obvious that you have no idea what you are talking about.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    95. Re:I'd agree with them on that.. by Grishnakh · · Score: 1

      No, it's blatantly obvious that you're a fucking asshole who wants to tell other people how to spend their free time. Fuck you.

    96. Re:I'd agree with them on that.. by Anonymous Coward · · Score: 0

      [...] Just because Linus Torvalds thinks you're doing it wrong doesn't necessarily mean you are.

      Just because Nvidia Optimus on my laptop doesn't work It means Linus is right :-).

    97. Re:I'd agree with them on that.. by Bill_the_Engineer · · Score: 1

      I think you have it backwards.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    98. Re:I'd agree with them on that.. by AvitarX · · Score: 1

      Or maybe I am, it's been a year since I used it. The video decode is a major feature for me though on my e-350.

      I've not tried games for a awhile, as I've lately been playing Jamestown in all it's 2d glory.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    99. Re:I'd agree with them on that.. by cerberusss · · Score: 1

      That could be re-written as: nVidia has chosen to be hogtied by NDAs with other companies.

      --
      8 of 13 people found this answer helpful. Did you?
  2. Cannot open drivers source by Parker+Lewis · · Score: 3, Interesting

    Most common excuse for don't open the source for drivers is IP. But most part of times, the real reason is users will see there is no difference in hardware between standard and platinum cards.

    1. Re:Cannot open drivers source by Joehonkie · · Score: 2

      I'm not sure what a "platinum" card is, but if you want to pretend the hardware differences between number of shader units and clockspeeds and amount of RAM on different cards will suddenly go away if you use open source drivers, be my guest. Unless you want to talk about overclocking of different cards with the same number of shader units, etc. which is something that people can already easily do.

    2. Re:Cannot open drivers source by Sarten-X · · Score: 1

      My understanding (though I'm not involved with hardware manufacture) is that batches of chips that pass quality control perfectly are labeled as the highest level, and chips with a few minor defects get labeled as inferior, so their driver never tries using that damaged part of the chip. Anybody else looking at the chipsees they're the same, and since it's done in batches it's common for perfect chips to be marketed lower than what they can actually do.

      I say this only as passing on what I've heard. Perhaps someone more in-the-know can confirm or deny?

      --
      You do not have a moral or legal right to do absolutely anything you want.
    3. Re:Cannot open drivers source by am+2k · · Score: 4, Interesting

      Most common excuse for don't open the source for drivers is IP. But most part of times, the real reason is users will see there is no difference in hardware between standard and platinum cards.

      Well, there's one that's not visible in software: The RAM is tested to be less error-prone. If one pixel in a game isn't correct for 1/60 of a second, it doesn't matter. However, it does matter (potentially literally making the difference between life and death) when your CUDA calculation returns incorrect values.

    4. Re:Cannot open drivers source by Anonymous Coward · · Score: 0

      You do realize that the whatsit where the defect is doesn't actually work, right? So that there are, in fact, fewer whatsits than on a die with no defects?

    5. Re:Cannot open drivers source by bruce_the_loon · · Score: 5, Informative

      I think he means that there is no real difference between a Quadro GPU and the consumer GeForce GPU, only a PCI ID and some limits in the firmware.

      --
      Trying to become famous by taking photos. Visit my homepage please.
    6. Re:Cannot open drivers source by shadowrat · · Score: 1

      You mean someone could make a driver that makes my Quadro actually approach the performance of a GeForce in games?

    7. Re:Cannot open drivers source by seanzig · · Score: 2

      I think people are more skeptical of NVidia's IP reasoning than they have a right to be. Yes, I'd love more open drivers like Nouveau that actually performed well, and I'd like to not have to run NVidia's special installer every time I upgrade the kernel. Yet, I can easily conceive of situations where seeing driver source code might reveal something about the underlying hardware. It's probably a moot point in 6 months after a new card is released, when the cat is out of the bag on the hardware tweaks and everyone else has adopted it also or came up with an alternative solution. But this is a competitive industry, and I can understand how NVidia would be extra protective of their latest designs for the very short time that they are novel and superior. NVidia has some sharp people - I've known at least a couple of them. They know what open source is, what the advantages would be (free help, for one), and they consistently choose closed source.

      Most people (at least in the hardware sales business) already know that there isn't a difference between their standard and platinum cards, except the support. The platinum cards are intended for server systems. NVidia is charging for the need to replace cards if they overheat from having batches of them installed in some rack. Sure, they don't say that outright, probably so some unknowing gamers will buy them anyway, but most people can find this out by doing some basic research online.

    8. Re:Cannot open drivers source by shadowrat · · Score: 1

      Yeah, you can pay 50 bucks for the low end chip. You can mess around with overclocking and poking other parts of it. You might get lucky and have something that works. That's fine and all if your goal is to tinker and gamble. Personally, I'm buying a video card to render stuff according to my needs. I fail to see the logic in risking my $50 and time to potentially get a card that doesn't fit my needs when i could just spend $200 and be up and running.

    9. Re:Cannot open drivers source by Anonymous Coward · · Score: 0

      It's hard to say. It's probable that Nvidia uses some sort of code signing, and the only someone who can do that is Nvidia (or someone with the full specs and keys.) But yeah, your Quadro could easily be the same as a GeForce.

    10. Re:Cannot open drivers source by Anonymous Coward · · Score: 0

      That's true, but it's also true that some companies sell identical hardware with identical QA and disable features in software.

      Often in the case you're talking about they'll actually burn the features that didn't pass QA off the chip so that it is physically different.

    11. Re:Cannot open drivers source by progician · · Score: 1

      Yet, I can easily conceive of situations where seeing driver source code might reveal something about the underlying hardware.

      That is still this stupid IP argument. If for instance the AMD can see how the underlying hardware works, then what? If there are people who are ready to reverse engineer software and make high resolution microscopic images of the chips, I would say that is an other chip manufacturer, like AMD anyway. So what if they see?

      There's no excuse for keeping secrets no matter what you say. For people of the world the only beneficial way to run an economy where everybody is honest and do not hold back information. It is possible to make profit without keeping secrets, which means that secrecy is a criminal way to gain profits. Pure and simple.

    12. Re:Cannot open drivers source by Andy+Dodd · · Score: 1

      Approach a similarly-priced GeForce? No - since the Quadro was sold with a massive price premium.

      However, as I understand it, some of the features in Quadros make them unsuitable for gaming. Google "SoftQuadro" (which is ancient, NV has provided significantly more lockdown in newer models) - it was known for being detrimental to gaming performance.

      --
      retrorocket.o not found, launch anyway?
    13. Re:Cannot open drivers source by guruevi · · Score: 1

      There are quite some differences in the firmware though. You're right, same chipset, same card layout, Quadro may have more memory but deep down, the Quadro is optimized (and tested) for certain workstation applications (scientific, CAD etc.) while GeForce is optimized (and certainly not well tested) for games. And that is prevalent in a lot of features the Quadro has over the GeForce (ECC memory, multi-window rendering).

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    14. Re:Cannot open drivers source by TheGratefulNet · · Score: 1

      There's no excuse for keeping secrets no matter what you say

      disc: I am a linux user and have been since the 1.2.x kernel days back in the mid 90's.

      let me inform you of something that is a reality in the big wide world out there. you can get sued for using 'someone elses' algorithm or code. even if you write it 100% yourself and dreamed it up yourself, YOU ARE STILL LIABLE if found out.

      this cannot be argued; this legal fact. its nasty, its ugly and its unethical but its REAL WORLD and company people who run things do know this.

      in fact, it also puts you and I at risk whe WE write code. some company can look at our code (note: this is the key issue, here, even if you don't agree) and declare us as 'thieves' and then come after us. they usually don't if you are not a money making (suable) enterprise but if you ARE one, well, there's threatening to do, son!

      once someone clued me into this, a light went on in my head. I suddenly knew what the issue was. self defense.

      this is not often mentioned but its a reality and unles you can stop A from suing B due to 'software' then this will continue.

      hell, I'd worry about releasing some of my own code on my own hardware projects simply because the chances are VERY HIGH that I did something someone else did and if they have lawyers on the payroll, I could be toast...

      hope this gives some insight. its not mentioned much and its not technical but its the MAIN reason why code does not get released or shared.

      change the legal system and we could see change here. no change in legal? no change will EVER come here on companies that know this lawsuit bullshit stuff. and believe me, the big ones know about this all too well.

      --

      --
      "It is now safe to switch off your computer."
    15. Re:Cannot open drivers source by Anonymous Coward · · Score: 0

      Yet, I can easily conceive of situations where seeing driver source code might reveal something about the underlying hardware.

      That is still this stupid IP argument. If for instance the AMD can see how the underlying hardware works, then what? If there are people who are ready to reverse engineer software and make high resolution microscopic images of the chips, I would say that is an other chip manufacturer, like AMD anyway. So what if they see?

      How sure do you think nvidia can be that their hardware and software does not contain any patent violation?

      Maybe ATI does examine NVidia chips using an electron microscope to reverse-engineer the technology - but that's not a problem as nvidia and ati do probably have extensive cross-licensing agreements already. But publishing specs (or code) would make it much more convenient for a vast number of other competitors (and lawyers) to go hunting for patent violations..

    16. Re:Cannot open drivers source by Nimey · · Score: 1

      The "features", IIRC, amount to valuing correct image rendering above anything else. This makes sense for things like AutoCAD and Solidworks.

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    17. Re:Cannot open drivers source by David+Chappell · · Score: 1

      Most common excuse for don't open the source for drivers is IP. But most part of times, the real reason is users will see there is no difference in hardware between standard and platinum cards.

      Yes, that is a common excuse. It is a sort of a boogy-man. It probably isn't true, but it is scary. Remember, two of the three video card makers have already released the requested information.

    18. Re:Cannot open drivers source by gman003 · · Score: 0

      Since /. is likely interested in a few more details:

      There is no fundamental hardware difference between "gaming cards" (GeForce, Radeon) and "professional cards" (Quadro, FireGL/FirePro). Historically the pro cards had more memory, but even that is now not universal.

      The difference is, and almost always has been, in the drivers. Gaming drivers prioritize "get the frame rendered on time", while pro drivers prioritize "get the frame rendered perfectly".

      The best way to demonstrate this is this: how does each draw a line? The gaming drivers use an algorithm that is crazy-fast, using all-integer math. It gives ugly results, which are normally cleaned up either by anti-aliasing, or (more recently) by running every frame through a selective blur filter. The pro drivers use a slightly different algorithm that gives near-perfect results, but is much slower because it uses all-floating-point math.

      That's hardly the only difference, but it's the most easily explained. The pro drivers do all kinds of things to make the results as accurate as possible, while the gaming drivers do all kinds of things to render as quickly as possible.

      Another difference, at least for Windows, is OpenGL. Most games tend to use Direct3D, so that code path is much better tested and optimized than OpenGL on the gaming drivers. But OpenGL is *the* API used by pro-grade programs, so that's much more functional in the pro drivers.

      Back in the day, it was possible to make the drivers for either work on either - you could run the pro drivers on your gaming card and get a cheap professional card (although this was when the extra 128MB of VRAM would have justified at least half the price increase), or you could even run the gaming drivers on a pro card and get the fastest system around.

      Nowadays there's too much stuff restricting you from doing that. Which is kind of sad, actually, because every so often on gaming forums you'll find a guy with more $$ than IQ who bought "the most expensive card on the market" and is wondering why he's getting only 15FPS in Battlefield when a card costing a tenth as much runs ten times as fast. At least if the drivers were unlocked we could tell them to use the GeForce drivers instead of the Quadro drivers...

    19. Re:Cannot open drivers source by Anonymous Coward · · Score: 0

      No. In truth, the only difference is a fuse. That's it- just a single fuse between a GeForce and a Quadro.

    20. Re:Cannot open drivers source by Anonymous Coward · · Score: 0

      You mean someone could make a driver that makes my Quadro actually approach the performance of a GeForce in games?

      Yes.

      I don't know about your particular card, but sometimes, this is exactly the case.

    21. Re:Cannot open drivers source by Anonymous Coward · · Score: 0

      Yes, just look at how many competitors sued AMD after they released their GPU register specs...

    22. Re:Cannot open drivers source by WuphonsReach · · Score: 1

      So what IP in involved with APC UPS's new "Microlink" communication protocol that it uses over USB ports on the newer UPS units? Why won't APC release this information to the apcupsd developers?

      NVIDIA is not the only company being stupid about this. We've bought APC Smart-UPS units for about 15 years now based on their reputation. Now we buy Tripp-Lite, because they play nicer with our Linux based servers.

      --
      Wolde you bothe eate your cake, and have your cake?
    23. Re:Cannot open drivers source by Anonymous Coward · · Score: 0

      Yes, yes they could. And make my GeForce approach (but probably not reach) the accuracy of your Quadro when running CAD software. There are a few small hardware differences, or at least there used to be. With the GF2/Quadro2 the difference was the placement of a couple of resistors.

  3. At least open the specs. by Picass0 · · Score: 5, Insightful

    I think Torvalds less critical of closed source drivers and more critical of closed specs. Nouveau would be improved greatly if Nvidia provided more transparency on the hardware.

    1. Re:At least open the specs. by 0100010001010011 · · Score: 4, Funny

      I'm sure AMDs offerings would be greatly improved too if Nvidia released more specs on the hardware.

    2. Re:At least open the specs. by DigiShaman · · Score: 5, Insightful

      With Intel and AMD as their competition, why risk tipping your hat for what arguably could be called a niche market. Keeping secrets about low level hardware optimizations is a competitive market advantage.

      --
      Life is not for the lazy.
    3. Re:At least open the specs. by higuita · · Score: 1

      what makes you believe that reverse engineering isn't possible and not done by all companies? yes, its harder than reading the source, but the open source drivers arent also based on the closed one, so the open source ones will not give you that information, at very least you would need to look at the firmware (closed source and that you can also extract from the closed source driver)

      --
      Higuita
    4. Re:At least open the specs. by Anonymous Coward · · Score: 1

      Who said they need to release the driver as source? Giving the specs for all instructions the hardware can carry out would be enough. If the open source community provides a better optimization maybe nVidia can take a hint. If it performs worse it might still be worth to use it with unsopported OSs or deliberatly unsupported nVidia hardware.

    5. Re:At least open the specs. by KingMotley · · Score: 5, Insightful

      What makes you think that your bank account PIN can't be guessed? Please post it.

    6. Re:At least open the specs. by DrXym · · Score: 5, Insightful
      They could keep their low level optimizations and simply release the technical specs to their hardware. Then the nouveau people can program the driver without even seeing NVidia do or do not do in their own code.

      Keeping the source closed might mean they have some secret tricks but at what cost? At the end of the day updating a binary driver is a pain in the arse. Every time the kernel changes, the video driver must be updated. The natural inclination for Linux users is to favour AMD or Intel products and forget about NVidia completely. And yet NVidia is stuck with testing and develop a driver that runs across an eclectic range of kernels and distributions. If they opened the source, or assisted nouveau by releasing the tech specs they could turn over a lot of support and maintenance to the distributions themselves.

      They could even implement some reasonable and sane end of life policy where once a GPU is more than 2 years old they turn over the specs or some reference driver so the hardware can be community supported. It would gain them a lot of kudos and alleviate them from a lot of the hassle of maintaining drivers.

    7. Re:At least open the specs. by Anonymous Coward · · Score: 2, Funny

      My bank account PIN is 12345. It's the same as my luggage just so I won't forget it.

    8. Re:At least open the specs. by Anonymous Coward · · Score: 0

      psst. Nobody talks about fight club.

    9. Re:At least open the specs. by DrDitto · · Score: 2

      nVidia device drivers have the complexity of an entire operating system (yes, seriously). Much of the functionality and competitive advantage comes from the software drivers.

    10. Re:At least open the specs. by Anonymous Coward · · Score: 0

      9299

      WHAT NOW, BITCHES?

    11. Re:At least open the specs. by Anonymous Coward · · Score: 1

      Based on what happened after ATI released their specs, I don't think nVidia has to worry about getting shown up by the community.

    12. Re:At least open the specs. by Anonymous Coward · · Score: 1, Insightful

      Just like it was enough for ATI? Right now you have a choice between drivers that don't crash and drivers with features. Pick the open source drivers and you get fast 2D that doesn't crash. If you want 3D that can do more than ppracer you get the crash happy Catalyst drivers. If you want a full featured driver you're fucked on AMD/ATI hardware.

      It's been what 5~6 years since ATI specs were released and the enthusiastic user base promised that the "community" would push out amazing drivers? When is that going to happen?

      At least with NVIDIA you can have a choice. If you don't need the full feature set the Nouveau can work. If you do need the full feature set the blob works at some small inconvenience (usually absorbed by the distribution) when installing new kernels. If NVIDIAs blob was crash happy crap like Catalyst, then yeah I'd say "fuck you" NVIDIA. But despite the hate and FUD the blob remains the _only_ driver that is not gimped or unstable.

      When we get full featured functional open source ATI drivers, then and only then, you can say "see!!? Open source drivers work if you release the specs ten years ago." I'll ditch the blob and buy an ATI. Until I see "release the specs" actually working (AMD/ATI), I'm not going to get all excited about NVIDIA not doing it.

    13. Re:At least open the specs. by sqldr · · Score: 5, Informative

      I've read the specs for AMD. It's mostly just a list of registers and what numbers to dump into them to control it. It's hardly giving away how it works.

      As an offtopic, there's over 500 of the bloody things. I sort of glazed over when I saw it. The people writing drivers with no support are doing a grand (but probably quite fun) job.

      --
      I wrote my first program at the age of six, and I still can't work out how this website works.
    14. Re:At least open the specs. by gorzek · · Score: 1

      Just because you know it's possible for your competitors to reverse-engineer your hardware doesn't mean you should make it easy for them, or basically hand them the keys to it. Make them do the work themselves--while you continue plowing forward with a better product.

    15. Re:At least open the specs. by Bert64 · · Score: 1

      Just because you publish details, doesn't mean its legal to copy them into your own work...
      In fact, if the details are out in the public it becomes much easier to prove that someone has created a derivative work without complying with the distribution terms.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    16. Re:At least open the specs. by ciderbrew · · Score: 2

      Same as mine?! ! no way..

    17. Re:At least open the specs. by buchner.johannes · · Score: 2

      My NVIDIA experience has vastly improved when Nouveau started supporting my chipset. Thank you Nouveau guys!

      Finally, Flash does not crash any more (apparently 2 closed-source apps are too many).

      --
      NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
    18. Re:At least open the specs. by Anonymous Coward · · Score: 1

      You are assuming that Nvidia (or any other company) has externally consumable "specs" for their hardware. Many companies only have internally consumable specs for their hardware (e.g., delta specs from old chips, specs filled with internal jargon, combination of msword docs, text files, power-point presentations, etc.)

      Also, almost all complicated chips these days (like a graphics chip or a wireless chip) are released with lists of bugs in the 1000's which sometimes have complicated driver work arounds. There's almost no benefit for the company to release these skeletons as they ususally:

      1. suggest performance "pot-holes" that can be exploited by the competition (assuming the chip is performance rated)
      2. suggest compatibility issues that can be exploited by the competition (assuming the chip is compatibility rated)
      3. some features are "software-only" on some models of the chip and can be just lifted and copied by the competion.

      Releasing the documents (assuming the company wants to spend the time to clean them up) w/o the bug list would probably mean that the documents would be insufficient to write a fully performant driver (in the best case), and/or a fully functional driver (in the worst case).

    19. Re:At least open the specs. by Anonymous Coward · · Score: 0

      I forget the name of the book offhand, but it basically states "all corp. secrets last at most 3 years"

      Also... it is VERY easy for other manufactures of silicon chips to reverse engineer other company's chips, most hire that out to "contractors" so as to remove potential legal issues... but that is besides the point. Once you start getting REALLY low level... things start to become more of "what is their caching scheme" rather than the actual layout of the chip, that makes more of an impact.

    20. Re:At least open the specs. by Andy+Dodd · · Score: 1

      Same thing with TI's OMAP TRMs - They provide DETAILED technical documentation without giving away any major secrets about how their stuff actually works.

      --
      retrorocket.o not found, launch anyway?
    21. Re:At least open the specs. by cwebster · · Score: 1

      At the end of the day updating a binary driver is a pain in the arse. Every time the kernel changes, the video driver must be updated. The natural inclination for Linux users is to favour AMD or Intel products and forget about NVidia completely.

      If you are compiling the kernel and whatever modules you compiled, how hard is it to compile one more module external to the kernel sources?

      Chances are if you are using a distro that provides per-built generic kernels for you to use, they also provide a package for the nvidia driver package that takes care of things for you. If you are building the kernel yourself, it really is no pain to use tools like 'cd' and 'make' to build the nvidia driver.

    22. Re:At least open the specs. by Mystra_x64 · · Score: 1

      The natural inclination for Linux users is to favour AMD or Intel products and forget about NVidia completely.

      One of us might be from Mars because it's opposite of what actually happens here. Also, dkms works wonders.

      --
      Quick way to get 30% Funny 70% Troll: defend Opera browser on /.
    23. Re:At least open the specs. by drinkypoo · · Score: 1

      nVidia has seen what has happened with ATI and OSS. ATI releases specs, community says "now release more specs", oh and the driver still sucks balls (sure, it works kind of OK for some cars) which doesn't make ATI look good. nVidia wants no piece of that. They're not shiting on Nouveau but they're not going to lend it a hand either so they don't take responsibility of any kind, and there's no issues of what they can and can't release if they release nothing. Even releasing specs might compromise their licensing in cases where they don't own all the tech.

      I'd like to see nVidia come around on this, but I admit I can't see any reason why they would.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    24. Re:At least open the specs. by DrXym · · Score: 3, Interesting

      Most people don't compile the kernel. The system tells them their kernel has an update and they click the update button. Then it turns their desktop to crap because it won't even start because the graphics configuration is bolloxed and they end up spending half an hour screwing around reinstalling the graphics driver or hunting the NVidia site for a replacement. Some distributions might help reinstall the driver but it might not necessarily integrated into their package management system.

    25. Re:At least open the specs. by toejam13 · · Score: 5, Insightful

      Every time the kernel changes, the video driver must be updated.

      I see that as a problem with the kernel developers, not the video driver developers.

      I've read elsewhere that developers from Nvidia are frustrated over the volatility of the Linux kernel interface to the graphics subsystem. It changes frequently and often with little advanced notification. You don't hear that complaint about Windows, MacOS or FreeBSD.

      Perhaps your ire is aimed at the wrong group.

    26. Re:At least open the specs. by Anonymous Coward · · Score: 0

      Every time the kernel changes, the video driver must be updated.

      It does? Seriously? And the Linux developers thought this was perfectly fine?
      No wonder it gets shafted, that is a terrible implementation choice.
      I just lost a little bit more respect for Linux.

    27. Re:At least open the specs. by Henour · · Score: 2

      Everyone I know that wanted 3D Performance under Linux went with Nvidia. I don't know were you get your natural inclination from.

      If you don't need 3D Performance that might be different, but for 2D even the nvidia OSS Driver is probably good enough :D

    28. Re:At least open the specs. by Anonymous Coward · · Score: 0

      The natural inclination for Linux users is to favour AMD or Intel products and forget about NVidia completely.

      One of us might be from Mars because it's opposite of what actually happens here. Also, dkms works wonders.

      I'm with Mystra here - in my experience linux support for ATI graphics has improved markedly since I had to use (terrible) fglrx drivers on my Radeon 9000 but if you want to do any gaming on linux NVidia closed-source drivers are still the superior choice and trying to run games via Wine on ATI is just one huge exercise in frustration.

      Intel drivers are said to be nice (no personal experience except for a GMA 950 which worked fine under Linux) but the graphics chips are just not competitive.

      (my most recent experiences with ATi drivers under linux/wine are a HD 4850 and 6770)

    29. Re:At least open the specs. by DCFusor · · Score: 2, Informative
      You must not be much of a reverse engineer. That tells you just what can be controlled in hardware - which jobs are hardware and which software, and that tradeoff, as well as the division of labour between the GPU and system CPU is the big deal.

      Plus, with all this closed stuff, who knows, or can know, what software/hardware patents might be getting cheated? What stuff that's just trade secrets (but good stuff) needs to be kept secret?

      Yes, it would sure be nice if NVidia could give us more support - I'm all for that one, as there's a lotta cool things you could do with their cards. Like CUDA? Last I checked they were pretty open with that one. All my linux boxen run NVidia cards as they're the best for the money, and "just work" for me all the time.

      --
      Why guess when you can know? Measure!
    30. Re:At least open the specs. by multi+io · · Score: 2

      I think Torvalds less critical of closed source drivers and more critical of closed specs. Nouveau would be improved greatly if Nvidia provided more transparency on the hardware.

      The way they probably see it, the hardware-independent graphics API layer (DirectX/OpenGL) is the "spec", and the stack that they offer, including the hardware, hardware-software interface, and the driver, is their "implementation" of that spec. So the hardware-software interface (which Linus wants them to publish) is sort of an implementation detail, which they may want to change without notice.

    31. Re:At least open the specs. by chmod+a+x+mojo · · Score: 3, Informative

      1:Put module source in the DKMS tree
      2: reboot into the new kernel so the module automatically gets rebuilt
      3:????
      4: profit

      Is it really that hard nowadays?

      --
      To err is human; effective mayhem requires the root password!
    32. Re:At least open the specs. by Anonymous Coward · · Score: 0

      It's a trap!

    33. Re:At least open the specs. by Anonymous Coward · · Score: 0

      You are assuming that AMD doen't have the resources ou expertise to reverse engineerer nvidia's driver and hardware.

    34. Re:At least open the specs. by SolitaryMan · · Score: 1

      I've read the specs for AMD. It's mostly just a list of registers and what numbers to dump into them to control it. It's hardly giving away how it works.

      Just like any other data sheet for any other chip out there. From tiniest to the largest.

      I'm just going to assume that their architecture is so crappy, that they just plain ashamed of releasing a data sheet.

      --
      May Peace Prevail On Earth
    35. Re:At least open the specs. by Anonymous Coward · · Score: 0

      Well, he's free to create an open video card as capable as nvidia's and publish the specs...

    36. Re:At least open the specs. by SolitaryMan · · Score: 1

      You must not be much of a reverse engineer. That tells you just what can be controlled in hardware - which jobs are hardware and which software, and that tradeoff, as well as the division of labour between the GPU and system CPU is the big deal.

      In all respects this is exactly the same as if somebody releases the library as binary and refuses to release any documentation for the API. In this particular case, people need this API to make NVidia's crap work with Linux.

      Anyway, I'm pretty sure that this is a political issue for them.

      --
      May Peace Prevail On Earth
    37. Re:At least open the specs. by hairyfeet · · Score: 5, Insightful

      This would be an argument IF Nvidia and AMD were doing things even closely to the same way, but they are not and haven't been for several years now. Nvidia has always used the classical "Build a big ass bad ass chip, then cut it down for the mainstream and budget markets" while AMD is using the "Build a mainstream chip and then add more chips to ramp UP to the high end" which is a completely different approach and one knowing how the other did X or Y frankly i doubt would help much as their designs are just too different. hell just look at the specs of any two roughly equal Nvidia and AMD chips, Nvidia has fewer but much more powerful cores while AMD has hundreds of weaker cores working in concert.

      so I really don't see how knowing how one does X or Y really is gonna do shit. After all they could always reverse engineer the hardware or write a custom kernel to look at what is going on if they were THAT curious and it certainly didn't seem to bother AMD to open up THEIR specs, most likely because as i said their designs and Nvidia's are just too radically different for one to be copying the other. I mean how long as AMD been using the X2s for the high end now? 5 years? 6? it wouldn't make any sense to suddenly change their designs just because Nvidia opened their specs, not to mention it would mean basically tossing their designs and roadmap, it just wouldn't make sense.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    38. Re:At least open the specs. by DerPflanz · · Score: 2

      I once met a man that could remember all PIN codes. Amazing guy.

      --
      -- The Internet is a too slow way of doing things, you'd never do without it.
    39. Re:At least open the specs. by steveg · · Score: 1

      Even so Nouveau has gotten *much* better, and nVidia has gotten much worse. I've been using the proprietary drivers for years now and have been reasonably satisfied with them. At least until recently.

      For a couple of months my work PC has had the graphics lock up several times a day as the graphics card has "fallen off the bus." I'd have to ssh in from another machine and reboot. Anything even that even slightly stressed the graphics could bring it on (like a Youtube video) or even just a fast scroll through a page.

      I switched over to Nouveau and the problem has gone away. Uptime is currently 16 days, where I was lucky to make 4 hours using the nVidia drivers. Nouveau soes everything I want it to, other than a little tearing in some very old-school X programs like nedit.

      So yes, it would be really nice if nVidia would make their specs available, but the Nouveau people have done a really good job, right now better than nVidia have. It would be really nice if I could use my Optimus graphics on my laptop as well.

      --
      Ignorance killed the cat. Curiosity was framed.
    40. Re:At least open the specs. by houghi · · Score: 2

      At the end of the day updating a binary driver is a pain in the arse. Every time the kernel changes, the video driver must be updated.

      True for many distro's. Not so for openSUSE. I just add the NVidia repo and be done with it.

      --
      Don't fight for your country, if your country does not fight for you.
    41. Re:At least open the specs. by LateArthurDent · · Score: 0, Troll

      Every time the kernel changes, the video driver must be updated.

      I see that as a problem with the kernel developers, not the video driver developers.

      I've read elsewhere that developers from Nvidia are frustrated over the volatility of the Linux kernel interface to the graphics subsystem. It changes frequently and often with little advanced notification. You don't hear that complaint about Windows, MacOS or FreeBSD.

      Perhaps your ire is aimed at the wrong group.

      As far as I'm concerned, that's a feature not a bug. Anything that makes closed-source anything harder to work on linux than an open-source alternative is fantastic.

    42. Re:At least open the specs. by Anonymous Coward · · Score: 0

      I believe it would be a good policy to document your API - so that others can benefit from using your hardware. This would also ensure MORE sales.

      You don't have to reveal any tech (the 'how it works') when doing this - but some reference to how to interface with it, and what are the various advantages and disadvantages of various interfaces would make that very desireable to developers - and again, would increase your overall sales.

      Being over protective will only lead to more such responses, and depending on the environment, could have a significant negative impact on your business in the long run.

    43. Re:At least open the specs. by sqldr · · Score: 1

      You must not be much of a reverse engineer.

      It wasn't *just* that. the specs are online. The software isn't embedded in the chips - you upload compiled code to it via the driver.

      as they're the best for the money, and "just work" for me all the time.

      You must not be much of a reverse engineer.

      --
      I wrote my first program at the age of six, and I still can't work out how this website works.
    44. Re:At least open the specs. by c0d3g33k · · Score: 0

      At the end of the day updating a binary driver is a pain in the arse. Every time the kernel changes, the video driver must be updated.

      True for many distro's. Not so for openSUSE. I just add the NVidia repo and be done with it.

      You've missed the point entirely with a lack of understanding that approaches perfection.

      The statements you quoted were referring to the changing ABI of the Linux kernel, which requires the developers of the video driver (a kernel module) to update it every time the kernel ABI changes (which is often). That requires coding, debugging, recompiling,testing on the part of the video driver developers, which apart from being real work has the potential to introduce bugs that have to be fixed. This is NOT about relying on your package manager to update your video driver for you when your distribution updates the kernel. In order for that to happen for you, not only do the video driver developers have to update the driver to match the new kernel ABI, the packagers for your distribution (openSUSE) have to download, build, package and test the new driver. That's quite a lot of work that has to be done to allow you to smugly declare that updating your video driver when the kernel changes is simple. I hope you appreciate the work that goes into making your magic computing box do your bidding with minimum effort on your part.

      Read the following: http://en.wikipedia.org/wiki/Loadable_kernel_module
      Skip down to the "Binary compatability" section if you're pressed for time.

    45. Re:At least open the specs. by sjames · · Score: 1

      Reverse engineering that is trivial for a company that will use that information in a multi-million dollar product (such as any notable competitor), not so easy for someone writing a free driver. So publishing that information is very helpful to people who want to expand the user base for your product (free of charge no less) but not so amazingly helpful to the competition.

      In general, manufacturers vastly over-estimate just how special that sort of information is. That was the situation for a while with ethernet cards, but when the reverse-engineering started in earnest it turned out that practically all of the cards used a minor variation on one of two themes for their register level access. The difference between the best and worst of them really was in the actual hardware.

      The most common reason for hiding that sort of information is actually sweeping the ugliness under the rug and hiding the fact that the amazing 'feature x' is actually implemented in the driver. It's a fine way to hide that you're cheating on benchmarks. I generally assume that when register level info isn't freely available, there's plenty of that going on.

    46. Re:At least open the specs. by cwebster · · Score: 1

      If most people don't compile the kernel then I doubt they have the problems you claim. I can't speak for rpm based distros (and perhaps this is why I doubt you, who knows) but I've never had this issue with a debian based distro or gentoo. In debian (i'm a bit out of date here) there was a package you could install (and apt-get update kept it updated) that you would just have to rebuild when you built/installed a new kernel. With gentoo I have a package installed that manages my external modules so I just need to do a 'module-rebuild' and it updates everything to the kernel linked in /usr/src/linux. Perhaps there are more issues for people using distro-built packages, but I can't speak for them either (the only distro-built kernels I've ever used are the ones bundled in installers to get enough of a system installed to build my own kernel). I do recall having some issues 10 or so years ago, but since then, and especially recently, I have had no problems.

      The biggest inconvenience I can see is when your binary driver gets upgraded/rebuilt while using X, as then apps trying to use GLX fail with a kernel driver version mismatch, but a quick logout / stop xdm, rmmod nvidia, modprobe nvidia, start xdm, login, fixes that (or just reboot if that is too hard).

    47. Re:At least open the specs. by ChrisMaple · · Score: 1

      Would you care to repeat that anything making closed-source anything harder ... is fantastic, when all video cards won't work with anything but a VESA text driver?

      --
      Contribute to civilization: ari.aynrand.org/donate
    48. Re:At least open the specs. by s.petry · · Score: 1

      I like you use nVidia on Linux since ATI simply fails to release working drivers most of the time. I can't say I envy the NVidia position. Giving away to much could harm them, but giving away nothing harms Linux.

      Both of the big players in GPU do the same thing, but at least I can get the NVidia gear working.

      --

      -The wise argue that there are few absolutes, the fool argues that there are no probabilities.

    49. Re:At least open the specs. by Darinbob · · Score: 1

      Specs on the interface give away almost no trade secrets.

    50. Re:At least open the specs. by Anonymous Coward · · Score: 0

      All 10,000 of them? Wow!

      I, personally always had problems remembering 1057. Oh, I just remembered it! Today, my memory must be excellent!

      </sarcasm>

    51. Re:At least open the specs. by toejam13 · · Score: 1

      Then you can bathe in your self-righteousness with Nouveau on Linux while I enjoy Nvidia's latest binary blob over on FreeBSD.

    52. Re:At least open the specs. by LateArthurDent · · Score: 1

      Would you care to repeat that anything making closed-source anything harder ... is fantastic, when all video cards won't work with anything but a VESA text driver?

      First, is that hypothetical scenario based on reality at all? Because the way I see it, AMD and Intel open-source drivers work great.

      Second, even assuming your comment was true, the answer would be yes. If you're going to use an open source operating system, then you believe in open source. What's stopping you from using Windows or Mac OS X if all you care about is that things work?

    53. Re:At least open the specs. by LateArthurDent · · Score: 1

      Then you can bathe in your self-righteousness with Nouveau on Linux while I enjoy Nvidia's latest binary blob over on FreeBSD.

      No, thanks. I bathe in my self-righteousness by buying AMD and running the open source drivers created as a result of them releasing the specs.

    54. Re:At least open the specs. by hairyfeet · · Score: 0

      I hate to break the news to ya AC but the ONLY ones complaining are Linux users, which is less than 3% of the market and who frankly don't buy that many GPUs anyway. In the Windows world AMD has owned a pretty good chunk of the crucial under $200 market and their high end cards trade blows with Nvidia all the time while often being a good c-note or more cheaper.

      In the end FOSS users have no right at all to complain because AMD did EXACTLY what you told them to. How many times did we hear from the devs and even on this very forum "Just open up the specs and we'll do the support"? Well guess what sparky, FOSS devs are finding out the hard way that writing good GPU drivers is INSANELY difficult. you asked for it, you got it. Either accept the fact you are not capable of the task and demand a hardware ABI so that the people that actually BUILD the hardware can support it without having to keep an entire dev team just to make drivers for old shit, or STFU and make the drivers already.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    55. Re:At least open the specs. by diego.viola · · Score: 1

      I use nouveau too and it's a lot better than the blob in many different ways, I would suggest also that you stop using the Flash blob (for practical reasons) and instead use HTML5 or simply stream down the flash into VLC or mplayer (with scripts like youtube-dl), you'll thank me later.

    56. Re:At least open the specs. by higuita · · Score: 1

      To make things equivalent, here is the source for my open source Bluetooth pin reminder:

      echo "0000"

      you can now extract the pin from the source.
      the bank account is still closed source, sorry, you will have to guess it!

      --
      Higuita
    57. Re:At least open the specs. by Amtrak · · Score: 1

      What!? Darth Helmet, change my luggage code immediately!

    58. Re:At least open the specs. by Anonymous Coward · · Score: 0

      Every time the kernel changes, the video driver must be updated.

      I see that as a problem with the kernel developers, not the video driver developers.

      I've read elsewhere that developers from Nvidia are frustrated over the volatility of the Linux kernel interface to the graphics subsystem. It changes frequently and often with little advanced notification. You don't hear that complaint about Windows, MacOS or FreeBSD.

      Perhaps your ire is aimed at the wrong group.

      So wrong. There were never a promise of a stable kernel ABI, so why do NVIDIA complain? (Just as I can't complain that their cards aren't cheaper - they never promised me a cheaper card...)

      Every time the kernel changes, lots of drivers must be updated. And a kernel guy who make such changes, is normally required to update all drivers as part of the change. Driver writers don't need notification, because the changes doesn't really impact them that much. Except of course, anyone who insist on keeping a closed driver outside the kernel. Their impractical choice,their problem entirely. Get the driver into the kernel - loose that problem!

      The situation is actually much worse with windows. They don't change stuff every month, but they change everything on a new version. Try to use a windows ME display driver on windows 7 - won't work. Write the driver again! But they don't complain because that is how windows is - and if they want to sell they go with the program. They think they can complain about linux because the market is smaller, that is all.

    59. Re:At least open the specs. by Anonymous Coward · · Score: 0

      The natural inclination for Linux users is to favour AMD or Intel products and forget about NVidia completely.

      Which makes you wonder why exactly they bother. As you say, Linux users are more interested in updating for the sake of updating than they are about high performance and stability, both things Nvidia strives to bring to the table with their binary drivers.

      It makes little sense, they should give up their competitive advantage because you like to update for the sake of updating knowing full well it will break things. The sad thing is that this also shines light on one of the more pronounced problems with Linux's development model. There's no (good) reason for drivers, even binary ones, to break between updates, especially between point-releases. Intentionally keeping the ABI in flux for the sake of attempting to coerce vendors into the releasing their source code is NOT a good reason to not have a stable ABI.

      Linux and whine and moan all day about how Nvidia doesn't cooperate to his liking, the fact remains that by intentionally keeping the ABI in flux, the kernel team refuses to cooperate as well, in fact, it's a commitment to, in a sense, punishing anyone who cares to support Linux.

      Yeah, yeah, minus one troll, even though you all know it's true.

    60. Re:At least open the specs. by Anonymous Coward · · Score: 0

      Open drivers + wine handles at least the max payne game fine here, thank you very much. I'm sure it could do more if I asked it too, but I quit gaming years ago. how about you just go fuck yourself together with your useless nvidia-wanking chums?

    61. Re:At least open the specs. by Anonymous Coward · · Score: 0

      No, if the details of somebody else's derivative work are out in public, then it becomes much easier to prove that it is a derivative work. For hardware, it is much more difficult to prove that somebody didn't comply with your distribution terms because you have to go through a chip and reverse engineer every signal trace - a time and money consuming process. AMD and Intel are likely to never publicly document their hardware if they do try to copy nVidia's designs, so it would not be easier for nVidia to prove that Intel or AMD did not comply with the distribution terms (read: created a derivative work).

      It does not benefit nVidia to publicly document their hardware. It does benefit them to have a very good closed-source driver that they make and that supports multiple OSes, and it benefits them a little to have people try to reverse engineer their hardware to create better drivers for more niche OSes (read: native Linux and BSD drivers, as in Nouveau), but it does not benefit them at all to commit engineering resources to creating, reviewing, and releasing public documentation for their hardware, and it could benefit Intel or AMD if they start to try to copy nVidia's designs.

      TL;DR: Your argument is fallacious, it is in nVidia's best interest to keep their hardware documentation private and release a closed-source driver for Linux and BSD instead of supporting open source drivers, and that's exactly what they're doing.

    62. Re:At least open the specs. by Anonymous Coward · · Score: 0

      It changes frequently and often with little advanced notification.

      This is by design. Not committing to a stable in-kernel interface places the maintenance burden on people who insist on developing their drivers out of tree, instead of the people working on improving the kernel.

    63. Re:At least open the specs. by Anonymous Coward · · Score: 0

      I've been using Linux for seven years. Never compiled a kernel.

      'Some distributions might help reinstall the driver but it might not necessarily integrated into their package management system.

      Those are immature distros. Anyone can throw a distro together, but the major ones all have that and have had that for the whole time I've used Linux. It's part of being a major distro. If you're using an immature distro, then you're in an even smaller minority that's looking for adventure.

      Context: yup, I started late and I'm not much of a Linux geek. I just use it on all my computers. Started playing with this home computers in '78 but waited till Linux got easy because fighting with the stuff had lost some shine by then.

    64. Re:At least open the specs. by crAckZ · · Score: 1

      WOW, that is the same pin they used in "Spaceballs" to protect the air lock for their world. what a coincidence.

    65. Re:At least open the specs. by Anonymous Coward · · Score: 0

      The PIN is ****

      Now you can share yours to make it even.

    66. Re:At least open the specs. by Anonymous Coward · · Score: 0

      If you're going to use an open source operating system, then you believe in open source.

      I use open source software because it's free (as in beer) and it gets the job done, in some cases better than the proprietary alternatives. Access to source code is pretty much a non-issue for my purposes.

      What's stopping you from using Windows or Mac OS X if all you care about is that things work?

      The main thing stopping me from using OS X is that it's tied to Apple hardware. I do use Windows on a couple of my machines, I just don't see any reason to pay for a Windows license to set up a file server, refurbish an old desktop, etc.

      Contrary to popular belief, you actually can use both Windows and Linux without spontaneously combusting. OS choice doesn't have to be a religion.

    67. Re:At least open the specs. by Anonymous Coward · · Score: 0

      There were never a promise of a stable kernel ABI, so why do NVIDIA complain?

      Nvidia never promised continued up to date driver support for linux so why do Linus, You and the Linux community complain?

    68. Re:At least open the specs. by toejam13 · · Score: 3, Insightful

      At a minimum, it places an extra burden on other kernel developers, unless those changes are being made in common header files that propagate out with each new build. At most, you're playing a game of chicken with a major partner who could dump all support of your kernel and back a competing free Unix-like OS.

    69. Re:At least open the specs. by uslurper · · Score: 1

      "Keeping the source closed might mean they have some secret tricks"

      -More likely its just plain ugly and they are ashamed of it.

      --
      oldhack: "Security is a waste of money until shit hits the fan. 5 minutes later, it becomes waste of money again. "
    70. Re:At least open the specs. by toejam13 · · Score: 2

      They don't change stuff every month, but they change everything on a new version.

      False. Not every bump of a Windows kernel version eliminates backwards compatibility with an older video driver. Generally speaking, neighboring versions of the same series can utilize the older OS video driver on the newer OS. I can personally confirm getting Win95 drivers to work on Win98, Windows NT4 drivers to work on Win2K (NT5) and Vista (NT6) drivers to work on Win7 (NT6.1).

      Try to use a windows ME display driver on windows 7

      WinME was part of the 9x series. Win7 is part of the NT6 series. NT and 9x never shared a common kernel interface for anything. They were two completely different operating systems that shared a common API (Win32/WinAPI).

      But they don't complain because that is how windows is

      They don't complain because the 9x series was phased out over a decade ago. The only major change to the kernel driver interface since then came with Vista. And when that change was proposed, they worked with partners far in advance.

      Can I take a video driver for kernel 2.0.37 and get it to build easily with kernel 3.2.18?

    71. Re:At least open the specs. by smash · · Score: 1

      Expecting companies to bend over backwards to support Linux, when Linux can't even provide a stable driver ABI is a bit rich. By not providing this, Linux is giving a big "fuck you" to hardware OEMs.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    72. Re:At least open the specs. by smash · · Score: 1

      If Linux were to have a stable driver ABI, Nvidia/AMD could simply release a binary that you could link and have work. Like on every other sane OS on the planet.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    73. Re:At least open the specs. by Anonymous Coward · · Score: 0

      fuck nvidia and there complaints. linux is more activly developed and that is why.

    74. Re:At least open the specs. by ToasterMonkey · · Score: 1

      Every time the kernel changes, the video driver must be updated.

      How does every other OS get by then?

      I wish NVidia would just post some hardware specs and say have fun, I truly wish it.

    75. Re:At least open the specs. by DrXym · · Score: 1
      Maintaining an ABI is incredibly difficult. The question in an open source setup is why bother at all as 99% of the drivers are source code. If the kernel changes, the modules will change and recompile with it. Therefore why should kernel developers who want to spend their time developing be concerned for the likes of NVidia who only release binaries? Look at how much change went into the 2.6.x kernel during its lifetime. Imagine an ABI over all that and the effort involved in supporting it.

      That is not to say an ABI is a bad idea. It's a good idea, at least if you're not a kernel developer. I just believe users would be better served if it is was maintained separately to the kernel with all the necessary shims were done in userland as much as possible or thin kernel modules. It also makes more sense that the maintainers for this ABI would be NVidia, AMD and distributors like Ubuntu and Red Hat since they would be the ones who benefit most from it.

    76. Re:At least open the specs. by DrXym · · Score: 1

      My natural inclination is for an OS that works and continues to work as I install updates to it. I couldn't care less or not if the graphics driver was a binary or not. Really I couldn't and I'm not advocating an open source driver because I'm some kind of GPL Nazi. I just know from bitter experience that 3rd party drivers are fragile and if the choice is between an OS that works after an update applies and one that flips a coin and dumps me in the console to fix this shit then I'd prefer the former over the latter.

    77. Re:At least open the specs. by DrXym · · Score: 1

      I update because the distribution tells me to update and invariably updates occur to fix security, stability and performance. It's good practice to update.

    78. Re:At least open the specs. by epyT-R · · Score: 1

      or if the driver was available as source, it could be compiled as needed, like every other sane linux driver.

    79. Re:At least open the specs. by Anonymous Coward · · Score: 0

      Funny because I use linux for like.. 12 years and I am more than inclined.. almost mandatorily bound by sanity to FORGET about AMD and Intel CRAP DRIVERS and use an NVIDIA hardware that gives me an INCREDIBLE final result.

      I find far more important to be able to use the resources of the card I spent a Lot on than updating the kernel every fricking minor release is made (that usually changes NOTHING on my system).

    80. Re:At least open the specs. by socceroos · · Score: 2

      The way I see it is that it would be far better for Nvidia to at least use the current provided infrastructure in Gnu/Linux than roll their own broken infrastructure. Not sure how many of you have used the latest Ubuntu, Fedora, etc, but if you have you'll have noticed that the open source drivers work like a dream in terms of integration with the OS and the latest stack - but the minute you install a binary blob from Nvidia you suddenly have to work with their broken and buggy way of doing things. Suddenly the smooth experience you had with the open driver is replaced by great 3D graphics but introduced bugs and issues with your OS experience.

    81. Re:At least open the specs. by petermgreen · · Score: 1

      What used to happen with debian is that the resident geek (aka me) would set a system up then the system's owner/user would install updates that introduced a new "abi version" of the kernel and on teh next reboot X would fail to load rendering the system unsable for them. Yeah it wasn't exactly difficult to fix if you knew what you were doing (just re-run module-assistant auto-install nvidia)but it was a PITA if you were setting up systems for other people.

      Nowadays there is dkms which provided you get things setup right in the first place (e.g. make sure you install the kernel headers metapackage so the new kernel headers get pulled in when the new kernel does) mostly mitigates this issue but that is a fairly recent development.

      There are also some miguided souls who use NVIDIA's installer to install the driver rather than the debian packages. That WILL end badly when a kernel update comes down.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    82. Re:At least open the specs. by Erpo · · Score: 1

      Then it turns their desktop to crap because it won't even start because the graphics configuration is bolloxed and they end up spending half an hour screwing around reinstalling the graphics driver or hunting the NVidia site for a replacement.

      Half an hour... How things change. Before cell phones could access the Internet and I had multiple computers in my house, an X failure meant trying to remember how to connect to the Internet from the console and then searching for a solution using lynx. That was not a half hour process by any stretch of the imagination.

      Reading your comment, I got a feeling like I did when a kid asked me why the drive letters in Windows start with C: instead of A:.

      What do you call that feeling? It's not quite nostalgia; I'm glad the days of editing XFree86Config with ed and storing data on floppies are gone for good. Thanks, I guess, for reminding me how far we've come?

    83. Re:At least open the specs. by crutchy · · Score: 1

      when you reverse things come at you from behind

      just stop that dog dribblin on my seats

    84. Re:At least open the specs. by lsatenstein · · Score: 1

      One way to get more pertinent responses is for the Linux community to support a competitor to NVIDIA, and to publicize it with reasons why the community is so doing.
      And make certain the hardware lists reflect the same as well. Long before sales drop to zero for Linux, we should expect better cooperation. I like Intel and AMD hardware for Linux graphics.

      --
      Leslie Satenstein Montreal Quebec Canada
    85. Re:At least open the specs. by Anonymous Coward · · Score: 0

      Look at it this way, Intel and AMD are both large chip makers. AMD may have separated their fab business from the design division but both, of necessity, are likely to be some of the best in the industry at disassembling chips and figuring out exactly what's going on in them.

    86. Re:At least open the specs. by hobarrera · · Score: 1

      So you congratulate Ubuntu for integrating the OS driver so neatly, but critize nvidia for not integrating their own so well?
      Shouldn't the Ubuntu devs be the ones integrating the binary blob, if you expect so nice an integration?

    87. Re:At least open the specs. by socceroos · · Score: 1

      No, you've misunderstood.

    88. Re:At least open the specs. by Anonymous Coward · · Score: 0

      You defeated yourself with your first sentence. The very fact that Nvidia and AMD do things very differently is testament to the fact that either would seriously gain from the knowledge of the other, because AMD shines at Anisotropy and Nvida has superior Anti-Aliasing for example. Also your chip analogy is wrong on two points. Nvidia don't build a 'big badass chip' they build each Unified Shader to work standalone, whereas from what I've read AMD's chips are more like FGPAs in the sense they are meant to be used in grids and thus several combine to make a unit like a single NVidia chip, making them far more adaptable and programmable, but adding significant overhead software wise.

      Now you have no idea why AMD did this, maybe they simply couldn't make a chip like Nvidia. Having a card spec would allow them to sit there and probe all the pinouts with a multimeter to work out exactly how the shaders work. They would then be able to reverse engineer the Nvidia circuit.

      Your idea of reverse engineering a graphics card with millions of transistors and hardware levels when you have no idea what's under the hood, is three words. Stupid and impossible.

      Lest we not forget, AMD have released the spec for the 2D side of its drivers, but there is still no 3D support for a very important reason. 3D mode is not in OSS drivers because AMD is pretending to be an OSS ally of the good PR. We haven't had a AMD 3D level whitepaper since 2008, and all graphics cards have a large complexity and power gap between 2D and 3D acceleration.

      So finally, I would like to thank Nvidia. Sure you didn't release whitepapers for you hardware, but you instea provided us with a 3D driver that supports 3D acceleration and a plethora of things that we wouldn't have under OSS due to copyright, like CUDA (as this would be easy enough for AMD to emulate/translate in software).

      Best of all you made it simple and effective. You spent money on programmers just for us and provided us with stable solid and reliable drivers. Anyone who doesn't think that that's a good thing needs to take a long hard look at themselves and come to terms with the fact that they live in a world where sometimes, you have to pay attention to the needs of the hand that feeds you.... and his requirement that people don't steal his hardware secrets.

  4. Diplomatic response by Anonymous Coward · · Score: 2, Interesting

    They should have blasted him for not having a consistent set of APIs and changing things, often for little benefit, which break binary compatibility and make supporting Linux in all it's variants a mighty task.

    Sure, Linus made Linux and uses it to push his agenda (i.e. that of FOSS), but when Commercial software houses struggle to keep up with the changes, I don't think he should be blaming them. Instead he should look more at what Linux can do to help non-FOSS software exist on the platform without needing a full time 10 man team just to keep up with the ports.

    1. Re:Diplomatic response by Hatta · · Score: 5, Insightful

      Sure, Linus made Linux and uses it to push his agenda (i.e. that of FOSS)

      No, Linus uses FOSS to push Linux, not the other way around.

      --
      Give me Classic Slashdot or give me death!
    2. Re:Diplomatic response by Anonymous Coward · · Score: 0

      How?

    3. Re:Diplomatic response by higuita · · Score: 5, Informative

      Apps have a stable API, so non-FOSS software can work fine with linux...

      now DRIVERS have to comply with the kernel API, that might not be stable over time and can change... hardware builders should integrate their drivers in the kernel tree or suffer the pain of outside development. Its their choice, having to work together with the community and have the pain for legal process and code cleanup (not all trash is accepted in the kernel) is harder in the beginning, but will pay off for everyone (users, developers and company) on the long run... or play dumb and keep the closed driver and keep updating it when things change.

      Releasing the hardware papers will allow the community to develop their drivers without the company have to work much, so between open source drivers, papers or close source drivers, the company have a lot to choose.

      Most companies choose the first or at every least, release some papers or demo driver. They are seen as heros.
      Nvidia is one of the few that choose closed sources drivers and so earns the hate of many users and the kernel developers.

      Again, its their choice. Also, its the user choice to buy their cards or not.
      i personally prefer open drivers and stability over better performance and locked in over on my own machine. other might have other opinions.

      finally Linus dont have a hidden agenda, he cares only about the kernel and closed source drivers make very hard to almost impossible to debug problems. He choose GPL as a license as it protect his work from being abused by others. Linus didnt even wanted to migrate to GPL V3, so is clearly dont have a hidden agenda.
      Again, if NVIDIA dont like the kernel license, they can choose to work only with *BSD kernels.

      --
      Higuita
    4. Re:Diplomatic response by Anonymous Coward · · Score: 0

      > Apps have a stable API, so non-FOSS software can work fine with linux...

      That is a lie. Distro to distro API's change in subtle and difficult ways, each needing their own workarounds to build software, even when it is all 'GNU/Linux'.

      Some API's like netfilter and nfqueue may or may not be even provided, or may be in decrepit forms with deprecated warnings flying everywhere. Others libs like libcrypto have differing version numbers and patch levels across the board and don't play well either. Package names are never the same and often not even similar, making tracking these things down a PITA.

      > Releasing the hardware papers will allow the community to develop their drivers without the company have to work much

      Dream on. And even with the docs, you won't be able to do a better job than Nvidia themselves as they have all the experts.

      > Nvidia is one of the few that choose closed sources drivers

      Probably because they have the most to lose. If they opened it up, I'm sure the clone market would be really happy. Is that worth letting some amateur hackers have a go at making a potentially buggy driver that just pisses of some of their market share? Seems unlikely.

      > finally Linus dont have a hidden agenda,

      No it's not hidden at all - he wears his agenda on his sleeves.

      > He cares only about the kernel and closed source drivers make very hard to almost impossible to debug problems.

      Perhaps if Linux made a stable and consistent API for drivers, one which didn't constantly churn, a greater number of proprietary drivers would be able to settle and become stable, and the worthless effort of keeping up with the latest API changes and tweaks could be put to genuinely fixing and improving things. You could even start to add monitoring hooks to a well defined interface and compare the actions against a model for correctness, or run the driver in test harnesses to start to test its properties. Maybe something as far fetched as WHQL could be made and you could even provide test kits to closed source vendors to help them do a good job of their shit?

      Sadly while the interface is poorly defined and a moving target, no one is going to put the effort into things like this unless they have massive resource and a lot of motivation.

      Anyway, it is Nvidia's choice to keep the specs they developed to themselves. At the same time it is Linus's choice to make things more difficult for closed software.

      For him to swear so publicly against Nvidia is both unfair and immature. Nvidia could very easily drop all support for desktop Linux if they wanted, but they don't and Linus should be thankful they bother to play his petty games.

      At the same time, Linus being an asshole sets a poor example to everyone else in the community and looks bad to those outside it.

    5. Re:Diplomatic response by Anonymous Coward · · Score: 0

      It's not just better performance. It's a much more complete feature set than what is provided any other manufacture out there. NVIDIA drivers are always first to have the new GL stuff. Always. And not by a few days or months but by fucking years, man! If you want to target Linux for you apps you have to pick a GL spec from 10 years ago because everyone but NVIDIA is lagging behind by at least that much.

      People like to say that modern GL is competitive with Direct3D but that's really only true if you use NVIDIA's blob (the only driver that lives on GL 3.3). People like to say that GL is cross platform but that's only true if you take a spec from a decade ago -or- use NVIDIA's blob.

      Despite ATI's open specs they have yet to deliver a driver that is competitive with NVIDIA.

      As to the stability, the only thing that I've had a problem with over the last ~8 years I've been using Linux has been due to a bad RAM module and the move to KDE4 (which is fine now but sucked back then). The rest of the time Linux has been rock solid using the NVIDIA blob (although it hasn't always been convenient).

    6. Re:Diplomatic response by Anonymous Coward · · Score: 1

      > Apps have a stable API, so non-FOSS software can work fine with linux...

      That is one of the greatest fallacies of Linux. Getting something to compile between different distros is no walk in the park, let me assure you.

      Not only are package names wildly different and inconsistent on each linux platform, but library features, header locations and even library names are all subtly different. All this means wasted time for developers and nasty workarounds in the code base when trying to compile for more than one Linux distro.

      Sure, ideally you'd get a packager to help you out, but finding and developing relationships with guys to do this takes time, and should really be needed at all.

    7. Re:Diplomatic response by chmod+a+x+mojo · · Score: 1

      This.

      Not saying Linus needs to make a stable video interface that doesn't change for the next 10 years, but at least make the interface stable for major revision numbers. E.G. Designing a driver for 3.1 shouldn't need anything changed from 3.1.0 all the way to 3.1.99999. If you do find you absolutely need to change the video interface on the kernel for some god awful (read: good reason, not just because you can) reason send out notices before your next release and move up the revision. There is no need to just randomly change the interface between 3.1.21 and 3.1.22 and let everybody scramble to get everything working again. This would even help the FOSS drivers since they could concentrate on adding new code instead of adapting the old code to the next random revision of the interface ( less kernel code to change, less bugs introduced)

      --
      To err is human; effective mayhem requires the root password!
    8. Re:Diplomatic response by higuita · · Score: 1

      sorry, but that is not a kernel problem, its a package management and version problem. no where i said that supporting various distros is easy.

      both open source and close source program have this problem, totally different from the kernel internal api changing. the kernel user is stable, even between distros and kernel versions.

      --
      Higuita
    9. Re:Diplomatic response by higuita · · Score: 1

      i agree with the features, open source one are still lacking.
      Both intel and amd open the drivers too late and are still catching up. Mesa had little support for many years and XFree86 lock down didnt help. Is not easy to fast forward to current GL specifications. More developers are needed to increase the rate of this recovery.
      Without MESA support for newer GL versions, drivers cant also develop their support, its need to be developed on both ends, debugged and optimized. all this makes the all cacth up story slower

      --
      Higuita
    10. Re:Diplomatic response by Ash-Fox · · Score: 1

      Not only are package names wildly different and inconsistent on each linux platform, but library features, header locations and even library names are all subtly different. All this means wasted time for developers and nasty workarounds in the code base when trying to compile for more than one Linux distro.

      Sir, you talk rubbish. The common Linux distributions don't change what features libraries support in a given version. Library names are rarely renamed (only cases I know of are due to package conflicts). Location of header files, library locations - These are all for autoconfig to figure out when compiling a library - The developer doesn't need to do any 'nasty workarounds'.

      Getting something to compile between different distros is no walk in the park, let me assure you.

      So.. What's your contact info? I want to collect on your assurance policy.

      --
      Change is certain; progress is not obligatory.
    11. Re:Diplomatic response by higuita · · Score: 1

      kernel developers dont change internal APIs randomly just because they like it. they change the kernel and those changes meed different interfaces. having a stable internal API requires emulations of old interfaces, so wasting kernel developers time and resources to keep something that doesnt want to work together with the kernel. why bother then?! Drivers that are in the kernel have the kernel developers help to update to the new interfaces, outside drivers must support the themselves that and pay for that decision.

      If NVIDIA pays someone to keep a stable internal API in the kernel, hey, maybe it was accepted, but people wont have lot of works to help nvidia and getting nothing back (no money, no drivers, no specifications)

      --
      Higuita
    12. Re:Diplomatic response by higuita · · Score: 1

      >Some API's like netfilter and nfqueue may or may not be even provided, or may be in decrepit forms with deprecated warnings flying everywhere.

      Recompile the kernel to have a stable api you want, linux isnt "one size fits all", different distros have different kernel options. but usually related distros have close kernel options (routers distros have close configs, as desktop distos also have closed configs). What mainline distro dont have netfilter support?
      also, new features is different, dont expect that older kernels magically support new features. some distros may backport, but its rare.

      > Others libs like libcrypto have (...)
      that is not a kernel API

      >Dream on. And even with the docs, you won't be able to do a better job than Nvidia themselves as they have all the experts.

      hey, right, there are no more people in the world, nvidia have then all.
      look at the nouveau developers have made a amazing job, without any docs.
      look at the radeon driver, in several places is already equivalent to the fglrx (both windows and linux) (sadly other are lagging a lot), so there are other experts out there, all its needed is time.

      >Probably because they have the most to lose. If they opened it up, I'm sure the clone market would be really happy.

      yep, right, we are full of intel and ati clones out there!!
      not only building hardware is a lot different than software, but also open how a hardware works with the software makes almost no difference for whatever want to clone the hardware. everyone knows how a x86 works... do you see any clone, other than those that registered in the very start (via and amd)?

      >Perhaps if Linux made a stable and consistent API for drivers, one which didn't constantly churn, a greater number of proprietary drivers would be able to settle and become stable,

        yep, that helped the windows drivers being stable
      Windows drivers only start to improve the quality when MS start to certificate drivers and ship with many generic and certificated drivers

      >Nvidia could very easily drop all support for desktop Linux if they wanted,

      right, dream on, they would lose a huge market for they professional cards and probably higher for for CUDA/GPU processing.
      for me, i wouldnt care much if nvidia dropped linux, many developers that are happy with nvidia blob would start to think about helping improving the open source ones and NVIDIA would have to help the open sources one or lose the linux market.

      >Linus should be thankful they bother to play his petty games.
      you are totally out of the linux reality ... Linus dont play games

      --
      Higuita
  5. Summary by backslashdot · · Score: 0, Flamebait

    1. We are not going make any changes.
    2. Fuck Linux, fuck being open.

    1. Re:Summary by Bongoots · · Score: 1

      3. PROFIT!

    2. Re:Summary by Matje · · Score: 2, Informative

      what!? Did you even read their statement?

      3) We are a very active participant in the ARM Linux kernel. For the latest 3.4 ARM kernel – the next-gen kernel to be used on future Linux, Android, and Chrome distributions – NVIDIA ranks second in terms of total lines changed and fourth in terms of number of changesets for all employers or organizations.

      (emphasis mine)

      Unless you yourself are even more active in Linux then they are, it would be more appropriate for them to say to you ... Fuck You.

    3. Re:Summary by LWATCDR · · Score: 1

      1. is correct.
      2. Is not. nVidia is spending time and money to write Linux drivers. They actually work pretty well. If they where going to say Fuck Linux then they wouldn't provide drivers.

      Let's be honest about what the FOSS community wants. They want nVidia to keep writing the drivers and make them open source. But hey if you still want to stick with the party line of "If you provide the documentation the community will write the drivers for you" then buy AMD/ATI video cards and stop complaining about nVidia. Vote with your wallet.
      AKA
      2. We will do things the way we think is best if you do not like it then go somewhere else.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    4. Re:Summary by peppepz · · Score: 5, Insightful

      Yeah, you're right, who's this Linux Torvalds to judge who contributes to the Linux kernel and who doesn't.

    5. Re:Summary by peppepz · · Score: 1

      Whoops, s/Linux/Linus

    6. Re:Summary by Andy+Dodd · · Score: 4, Informative

      There's what they say... And then there's the code.

      If they're really contributing as much as they claim, then why is the mainline cpuidle support for Tegra in 3.4 so piss-poor compared to that of their own forked 2.6.36 branch? Where's the documentation on their CPU's idle/power management capabilities? Why is the Tegra code so badly branched that devices running Android 4.0 on Tegra are running 2.6.39 instead of the officially recommended 3.0.8?

      --
      retrorocket.o not found, launch anyway?
    7. Re:Summary by Anonymous Coward · · Score: 0

      Lines changed doesn't mean all that much. I could just as easily say "look how incompetent they are! They keep having to fix everything!"

    8. Re:Summary by Anonymous Coward · · Score: 0

      2. Fuck Linux, fuck being open.

      Nvidia aside, I think more people need to say this. "Fuck Linux", and more importantly, "Fuck Linux Zealots!" Fuck their lies, fuck their attitude, fuck their hypocrisy, and fuck their philosophies. They LIE about the what Linux is, how it works, what advantages or disadvantages it has, how much market share it has, who likes it, who wants it, and what it will be in the future. Lie, lie, lie... FUCK YOU!

    9. Re:Summary by phantomfive · · Score: 1

      NVIDIA ranks second in terms of total lines changed and fourth in terms of number of changesets for all employers or organizations.

      This doesn't mean they are second in total lines changed, it means they are second in one particular branch of the kernel, and of all the Android graphics drivers, Tegra is also second to the Qualcomm chipset in giving me the most trouble. So their 'second number of changes' is probably just a bunch of bug fixes.

      --
      "First they came for the slanderers and i said nothing."
    10. Re:Summary by Anonymous Coward · · Score: 0

      Yea seriously, who is this Linux Torvalds guy?!?!?! Now Linus Torvalds, he might have a dog in that fight...

    11. Re:Summary by Anonymous Coward · · Score: 0

      He was directing it to blackslashdot, but cool karma whoring bro. Being a virgin is tough I hear, so I can't fault you too much.

    12. Re:Summary by sander · · Score: 1

      The reason NVIDIA originally started supporting Linux, and why the continue to do so, is simple, it does so to sell graphics cards to large 3d graphics, animations, video effects and similar studios. They are also happy to sell Tesla cards to the same for backend render farms. Nvidia contributed immensely to the use of Linux in DCC, something that it does not usually get any credit for.

      This is the core segment of business in Linux for Nvidia, and why the drivers exist at all. Without DCC, Nvidia would not bother to consider Linux at all. On the other side of the coin, the people doing DCC need more than a driver - they need a full OpenGL implementation. One that is as fast and complete as as on other platforms. So how this really is step-by step (for NVIDIA) is:

      1. Make OpenGL driver + library that runs on Linux and is as good as competition, but runs on cheaper hardware
      2. Kill off Unix Workstations
      3. Sell people more of your cards
      4. Profit!
      5. Sell people the next generation of your cards, making sure the driver + libraries combination is at least as good as any other platform provides
      6. Profit!
      7. Keep doing it and getting profit

      But this only works if you have both the library and the driver. If you buy the card, you also buy the right to run software that ... makes rather expensive software you buy from Autodesk work. The fact that you can download the driver + library from the web and use it on a system that doesn't run any real 3d design software is simply Nvidia being nice.

      Unfortunately, Slashdot seems to have degenerated to the point where few posters have a clear idea what they are posting about, never mind seeing the bigger picture.

    13. Re:Summary by sapphire+wyvern · · Score: 1

      Huh. Didn't know that Linus had written a Linus kernel as well as the Linux kernel.

      Gotta be careful with those regexes! :)

    14. Re:Summary by peppepz · · Score: 1

      There was no /g ;)

  6. This story starts more than a decade ago by Anonymous Coward · · Score: 0

    This story starts more than a decade ago. There was a hugely popular software vendor concerned that maybe one day people might choose to not use their software. They had vast sums of money and controlled access to the immediate future for software and hardware vendors alike. Foreseeing a potential difficult future they chose to defend themselves in a particular way. They formed subsidiaries they controlled and gave them patents, and filled them with developers skilled in the finer (and secret) nuances of how to interact with their software, and they kept them informed with advance knowledge of how it would work in the future. These subsidiaries approached hardware designers with a simple message: they would accept the patented technologies and use them; they would let the subsidiaries write the drivers that had special hooks into the software; they would do this under non-disclosure and never tell - or they wouldn't. If they accepted they would not be able to publish open specifications about how their own hardware worked because that would be exclusively cross-licensed with the subsidiaries in exchange for access to the patents. The hardware makers who wouldn't play along wouldn't get as good compatibility with the big company's software, nor inclusion in their distribution CD and OEM images. The refusers would be plagued with difficult installation, buggy drivers and unhappy customers and fail in the market. The software would change in ways the refusers could not predict, but the accepters could. Some accepted, and some refused. Those who accepted survived, those who refused mostly died. This has continued to the present day and as the hardware has evolved the agreements persist in ways that are now not removable. Nobody involved in Linux wants hardware manufacturers to write the device drivers for them. They only want open and clear specifications for how the hardware works so they can make their own drivers. They aren't going to get that from NVidia, nor ATI, nor any others whose technology is intertwined with this compromise from yesteryear. This boon is now beyond their ability to grant without starting again from the beginning. Source

    1. Re:This story starts more than a decade ago by Anonymous Coward · · Score: 1

      One must be mindful that these offers were all carrot and no stick. The developers came with a plausible story: we have experience and insight into the big company's software, as many of us came from there. We know how to pass validation. We have the inside track to getting on the CD, and can speed your way to market. We can use our secret ways to optimize it because we have special insight we can't share even with you. All we ask (other than pay) is that the interfaces become private between us. We will help you develop your hardware so that the hardware interfaces presented are optimal for interfacing with the software, and we don't want to share that work with others for no pay, which is fair, right? They had good stuff to offer too: the benefits of some deep research into compositing that the hardware vendors couln't get some other way - but it always came with this catch. And it seemed like such a little catch at the time since there were no credible challengers to the big company's ware. And it seemed quite reasonable to work together and not share with outsiders. But the devil is in the details.

      Only rarely would the stick come out, in reference to some other company: "oh, that seems to be a smart way to think. So-and-so thought so." So-and-so being a dead company who failed to come around to the "right" way of thinking. The threat implied was never stated outright.

      Later, when hardware vendors want more, they get more committed. Implement that new hardware feature in the OS game engine rendering interface? Sure.. but there's more cost than just money. Want the standard user interface to leverage high-end blurring, transparency and shadow features... sure.. but how that works has to remain private between us. That requires a specially committed level of partnership. Along the way there were more patents to incorporate and license, and a stronger bond to build until the hardware manufacturer is committed to the big vendor's software and none other - in a way they can't be free of even if they want to be. These aren't just patents and copyrights: they're trade secrets too, and those are immortal. Each is as much to blame as the other, as they used each other to mutual advantage. There's enough dirt in there to get mud all over everybody and nobody wants that.

      Every now and then some PFY trying to implement a feature for X will call up the hardware vendor hoping for some help. "So I've got some app in the debugger, and I can see it load a texture in the buffer and trigger the interrupt that submits it to your hardware. But there are mode-setting things in here that have been deserialized and I can't see which one goes first, or the right grammar for the call so when it doesn't crash it looks like crap. Throw me a bone. Feed me just a tiny little hint please, I'm dying here." These calls used to be fielded by actual developers who might be conflicted and want to say the easy truth but would instead give the same bored answer every time: "sorry, but that's a trade secret." And never would they say the big secret: "and it's not our trade secret so we'll never be able to answer these questions." Now it's probably handled by some flunky in Bangalore who couldn't give the right answer if he wanted to. It might as well be a recording - but they still want to pretend that they care.

      This is all in the desktop and laptop arena of course. Servers are different. The big software company didn't have tyranny over server vendors like they did over desktops. Servers had to support Unix at first, and then Novell, and then Linux - to the point where no server company could survive or even be taken seriously with servers that could only run the big company's software - though they did try, notably with Broadcom network chipsets. The special features of the software/hardware interface just weren't as important in servers. Now in servers we have virtualization and the danger is pretty much passed. For some years when people wanted to run desktop software that was not based on the big company's ware they bought

  7. This is a tough call... by Anonymous Coward · · Score: 0

    This is a tough call. We want/need this hardware, and the software is tightly coupled with it.
    I've installed nVidia's driver on many Linux architectures and haven't had any problem with their
    certified drivers. I think nVidia will benefit by open-sourcing their driver, and eventually they will,
    but they've no complaints from me.

    I can understand how releasing the source could expose them at the hardware level and be copied by somebody.
    But, their properitary driver works very well and I'm not sure with just the source, I could improve on it.

  8. "consistent" experience? by DdJ · · Score: 4, Interesting

    They're saying "providing a consistent GPU experience across multiple platforms for all of our customers continues to be one of our key goals".

    So, my interpretation of that is:

    "If we released the drivers as open source, then people might figure out how to optimize and tune the Linux drivers. This could result in a better GPU experience on Linux than under Windows. That would embarrass us. To ensure a consistent experience across platforms, we therefore must prevent others from tinkering with the drivers, which mandates closed source."

    Does anyone else read it that way?

    1. Re:"consistent" experience? by Anonymous Coward · · Score: 5, Insightful

      No the "Consistent Experience" statement is just PR bullshit.

      If providing a "consistent experience" was a true goal of the company they would be implementing Optimus on Linux.

    2. Re:"consistent" experience? by TheRealMindChild · · Score: 1

      I did not, however, it makes sense. They also don't want to show you all of the software voodoo they have in the driver that runs on your CPU, but should be running on your video card

      --

      "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
    3. Re:"consistent" experience? by _xeno_ · · Score: 1

      Considering that the NVidia drivers consistently hard-freeze the machine and force either a remote "ssh sudo reboot" (if you're lucky) or a complete reset - I'm not sure I really want their "consistent experience."

      Seriously, it's been my experience that more often than not the Linux NVidia drivers crash after running for a day or so, leaving you with a completely non-responsive desktop. I had to revert to Nouveau, which gives me a functional machine with no pretty graphics.

      This has been my experience with the Linux NVidia driver for years across multiple machines and cards, for probably the past decade or so.

      So, no, I'm not sure they're worried about Linux speed exceeding Windows speed. I'd say they're more worried about people making Linux drivers that actually fucking work when they've proven themselves completely incapable of doing so.

      --
      You are in a maze of twisty little relative jumps, all alike.
    4. Re:"consistent" experience? by Anonymous Coward · · Score: 0

      Does anyone else read it that way?

      I read it as, "People will find out about all the shit we throw into our drivers to cheat in benchmarks. Also, nyah nyah, what are you going to to, go and buy an AMD card about it? Please."

    5. Re:"consistent" experience? by BeansBaxter · · Score: 1

      Interesting. It just sounded to me like they said go buy AMD Video cards. Solved my problems with Nvidia drivers.

    6. Re:"consistent" experience? by Anonymous Coward · · Score: 0

      > This could result in a better GPU experience on Linux than under Windows. That would embarrass us.

      The problem is interoperability with games. Windows drivers contain a huge number of game specific optimizations and fixes to actually make them work with newer drivers. I don't see open source community pulling that off, since there are no native AAA quality 3D games for Linux.

    7. Re:"consistent" experience? by TheGratefulNet · · Score: 1

      counterpoint: my mythtv client runs on an asus fanless atom with the ION1 gpu. it needs nvidias binary driver.

      I can watch HD video (mostly; the only time things get bad is when myth puts up its bargraph play position overlay on; but when it fades off, the video is nearly flawless.)

      I can do desktop things. stuff works fine and I've had no need to reboot. currently:

      % uname -a
      Linux myth 2.6.35-32-generic #67-Ubuntu SMP Mon Mar 5 19:35:26 UTC 2012 i686 GNU/Linux

      % uptime
        09:10:38 up 67 days, 10:40, 5 users, load average: 0.08, 0.03, 0.05

      % lspci ...
      03:00.0 VGA compatible controller: NVIDIA Corporation ION VGA (rev b1)

      I'd say that more than 2 months of uptime is enough to prove that the video drives don't always fark up. its a PITA to do the dkms crap due to NV binary drivers but since running this board for the last 2 year (almost) and only rebooting when I need to get to win7 (rare these days) I have only minor grumbles about NV. building new kernels is a pain but if I can live with the kernel I have, its stable and the video has not cause a crash.

      if anything, myth-tv is the piece-of-shit software! that thing falls over if you look at it the wrong way. its crap the way its written and has been for years. but, if I avoid touching it, lock it down so that things don't get upgraded, stuff generally will work. the NV driver is the least of my worries, actually.

      --

      --
      "It is now safe to switch off your computer."
    8. Re:"consistent" experience? by David+Chappell · · Score: 1

      I did not, however, it makes sense. They also don't want to show you all of the software voodoo they have in the driver that runs on your CPU, but should be running on your video card

      No one ask has asked them to. They have been asked to explain the boring bit twiddling which a competing driver (likely without the voodoo and hence of slightly lower performance) would need to do.

    9. Re:"consistent" experience? by sander · · Score: 1

      No. What they mean is that using their driver + libraries, OpenGL programs will conistently give you the same results regardless if you used these on Linux, MacOSX or Windows. If you work on 3d design, animation or even shaders, this really matters. Same for Quadro using CAD users. And these are the people that make Nvidia money.

    10. Re:"consistent" experience? by David+Chappell · · Score: 1

      They're saying "providing a consistent GPU experience across multiple platforms for all of our customers continues to be one of our key goals".

      So, my interpretation of that is:

      "If we released the drivers as open source, then people might figure out how to optimize and tune the Linux drivers. This could result in a better GPU experience on Linux than under Windows. That would embarrass us. To ensure a consistent experience across platforms, we therefore must prevent others from tinkering with the drivers, which mandates closed source."

      Does anyone else read it that way?

      No, they are saying that as long as Nvidia releases a driver for Linux, customers don't need to know how to program the card themselves and should stop complaining. Very patronizing. Those who are complaining don't want Nvidia to open-source its driver. They want the information they need to write a completely new driver.

    11. Re:"consistent" experience? by jittles · · Score: 1

      Uh can you tell me exactly where I can get Laptop drivers from NVidia for my Dell laptop? I mean Windows drivers. Or an HP laptop? Or even an Apple laptop? Oh wait you can't! Why? Because the OEM manufacturers want to push their own drivers. If you have a problem with this, complain to the OEMs. Then you'll get your Linux driver from NVidia.

  9. It Is Positive by assertation · · Score: 5, Insightful

    It is positive sign that they care enough about the Linux community to bother to have their PR department give the usual empty corporate zero content response.

    1. Re:It Is Positive by Anonymous Coward · · Score: 0

      We only have support because the vfx industry is centered around linux. That's fine and I don't think anyone is ungrateful but NVidia could still do more. I have a couple of aging workstations running integrated intel graphics having decided open source drivers are important... I'd much sooner buy CUDA supporting cards with my upgrade but I'm not swallowing "the blob".

      There's no sense of entitlement with me, individuals and companies are free to make their own deals with the world.

    2. Re:It Is Positive by Anonymous Coward · · Score: 0

      Next time I buy a notebook it will be . . . one without Nvidea graphic card ... or a Mac (have to look up what's in there) . . .

    3. Re:It Is Positive by Anonymous Coward · · Score: 0

      So is it positive because is zero? I guess I'm math outdated.

    4. Re:It Is Positive by Anonymous Coward · · Score: 0

      AFAIK Mac's use Nvidia GPU's, so simple choice for you then :P

    5. Re:It Is Positive by h4rr4r · · Score: 1

      The macbook air in front of me has an intel GPU.

    6. Re:It Is Positive by Robert+Zenz · · Score: 1

      Yes it is...many implementations are containing a positive and a negative zero.

    7. Re:It Is Positive by Anonymous Coward · · Score: 0

      they care enough about the Linux community to bother to have their PR department...

      What 'they' care about is bad press, especially if it come from someone with credibility. If it were commonly acknowledged that ANY laptops w/ Nvideous hardware wer less desirable because you'd NEVER be able to duel boot to Linux well (thus relieving the consumer of future choice or resale value) it might cause people to look elsewhere.

      PR response doesn't necessarily imply importance in the manner you've presented it.

    8. Re:It Is Positive by mrjimorg · · Score: 1

      Same here- that's why it has such poor 3d performance. Can't even run Civ5 very well

  10. Linus missed the point by Anonymous Coward · · Score: 0

    Linus should be sending Nvidia chocolates and flowers on the anniversary of Nvidia first Linux driver release. 3D / hardware acceleration on Linux was in a terrible state for a very long time. Open source drivers were going almost nowhere, and there was a very small number of cards on the market with "proper" support. Even if Nvidia opened up their full design so people could design open soruce drivers, those drivers would still be way behind where Nvidia is. Nvidia closed source drivers are certainly much easier to use and far more effective than the alternative for people that *gasp* want to use their PC and not make a statement about open source issues. I know a few people who only switched over to Linux (for good) after they got an Nvidia card and would be properly supported.

    1. Re:Linus missed the point by David+Chappell · · Score: 1

      Linus should be sending Nvidia chocolates and flowers on the anniversary of Nvidia first Linux driver release. 3D / hardware acceleration on Linux was in a terrible state for a very long time. Open source drivers were going almost nowhere, and there was a very small number of cards on the market with "proper" support. Even if Nvidia opened up their full design so people could design open soruce drivers, those drivers would still be way behind where Nvidia is. Nvidia closed source drivers are certainly much easier to use and far more effective than the alternative for people that *gasp* want to use their PC and not make a statement about open source issues. I know a few people who only switched over to Linux (for good) after they got an Nvidia card and would be properly supported.

      Or we could look to the present when the open source ATI drivers are more than good enough for most users.

  11. Linus summed it up best by Anonymous Coward · · Score: 0

    "@#%& you NVIDIA!"

  12. I'd settle for a checkbox during setup by Picass0 · · Score: 1

    "Nvidia compatible hardware accelerator detected. Enable Nouveau?" Yes No

  13. Nvidia has said this all along.. by Severus+Snape · · Score: 2, Informative

    90% of the code used in the Linux driver is shared with the Windows driver, that was a claim made by one of their developers on their forums I read a year or so ago. Open sourcing the code is out of the question as all of that code isn't just from internal employees, as getting everyone who has written lines of code to agree to their code being available under a open source licence would be a huge task. Documentation would be great, there's the issue of IP though there. To be fair to Nvidia, they actively support Linux, I've used their cards for years and have never had much of an issue, in the old days, it was just a matter of shutting X11 and running their installer, it built the kernel module and you were good to go. Nowadays every distro I've used has the packages ready out of the box. I think Linus pain comes simply from running pre release kernels and expecting them to be supported before their even released! Nvidia normally provide patches in these situations anyway so I don't understand what Linus really wants them to do.

    1. Re:Nvidia has said this all along.. by gl4ss · · Score: 2

      nope.. this is particularly about optimus for which they're not giving specs(switching between using integrated and a discrete gpu).

      also the nvidia answer dodges that _totally_.

      --
      world was created 5 seconds before this post as it is.
    2. Re:Nvidia has said this all along.. by Joehonkie · · Score: 5, Informative

      He wants working Optimus on laptops. He was kinda clear about that.

    3. Re:Nvidia has said this all along.. by Anonymous Coward · · Score: 0

      He wants open specs not their source code. So there might be an optimus driver for linux (and other systems). There is a difference between the hardware specs and the open sourcing the existing driver.

    4. Re:Nvidia has said this all along.. by rrohbeck · · Score: 0

      Replying to undo moderation mouso...

    5. Re:Nvidia has said this all along.. by Anonymous Coward · · Score: 0

      They could write their drivers in such a way that they aren't version-locked. Plenty of other companies do it, so why not Nvidia?

    6. Re:Nvidia has said this all along.. by Anonymous Coward · · Score: 0

      90% of the code used in the Linux driver is shared with the Windows driver, that was a claim made by one of their developers on their forums I read a year or so ago. Open sourcing the code is out of the question as all of that code isn't just from internal employees, as getting everyone who has written lines of code to agree to their code being available under a open source licence would be a huge task.

      What? Are you telling me that nVidia doesn't own the copyright to their own driver?

    7. Re:Nvidia has said this all along.. by Anonymous Coward · · Score: 0

      Do you think the IP situation is really all that different for Intel, AMD, or anyone else who has already opened their code? You think Nvidia is the only hardware developer in the entire PC industry who hasn't collaborated with third parties to get their drivers working on every configuration of hardware and software?

      The IP excuse is bullshit. The most that can be said is that Nvidia has been consistent in using this as a cop-out.

    8. Re:Nvidia has said this all along.. by Anonymous Coward · · Score: 0

      I just got a job doing remote computer repair and had to sign an agreement granting any and all patent and copyright for anything I create invent or imagine during my employment to my employer, whether it was done at work or on my personal time, no matter what industry it was in.

      Surely nVidia has a similar agreement that it owns all the code in its drivers.

    9. Re:Nvidia has said this all along.. by Kidbro · · Score: 1

      Open sourcing the code is out of the question as all of that code isn't just from internal employees, as getting everyone who has written lines of code to agree to their code being available under a open source licence would be a huge task.

      I call bullshit on this. No way did their contract say "I relinquish my rights to the code I produce to Nvidida, under the condition that they do not open source it". That would be the stupidest contract I've ever seen, and the liars^H^H^H^Hawyers wouldn't even have the knowledge to produce such a contract.

    10. Re:Nvidia has said this all along.. by mathfeel · · Score: 1

      90% of the code used in the Linux driver is shared with the Windows driver, that was a claim made by one of their developers on their forums I read a year or so ago. Open sourcing the code is out of the question as all of that code isn't just from internal employees, as getting everyone who has written lines of code to agree to their code being available under a open source licence would be a huge task. Documentation would be great, there's the issue of IP though there. To be fair to Nvidia, they actively support Linux, I've used their cards for years and have never had much of an issue, in the old days, it was just a matter of shutting X11 and running their installer, it built the kernel module and you were good to go. Nowadays every distro I've used has the packages ready out of the box. I think Linus pain comes simply from running pre release kernels and expecting them to be supported before their even released! Nvidia normally provide patches in these situations anyway so I don't understand what Linus really wants them to do.

      Until one day, they decided that your card is too old to support. By that point, nouveau would probably have decent support for basic 3D primitive, but by no mean optimized. For really old card that neither driver support, the user is screwed.

      --
      The only possible interpretation of any research whatever in the 'social sciences' is: some do, some don't
  14. Open Source community lacks professionalism by Anonymous Coward · · Score: 0, Interesting

    This is why Linux will never be taken seriously.... The open source community as a whole lacks professionalism. The rant, which basically says that nVidia driver support was a pain and in the end result the drivers are not to par with Windows AND they are BLOBS. It is a childish rant coming from an old man in a professional environment.

    People only buy nVidia GPUs to play games on them and it just so happens that 99% of the PC games are run off Windows, hence nVidia would happily support that platform. As for Linux... gaming on it is still in its infancy. nVidia has to spend real money (because time = money) to develop those drivers, of course they are going to release them as BLOBs, which is the root of the rant is coming from.

    Hence the linux community lacks professionalism. Obviously nVidia and Linux developers can coordinate, but it's like having a down syndrom kid work with someone with aspergers - problems in communication will be abound.

    1. Re:Open Source community lacks professionalism by Adaeniel · · Score: 1

      People only buy nVidia GPUs to play games on them

      That's not true at all.

    2. Re:Open Source community lacks professionalism by Anonymous Coward · · Score: 0

      I would say that the majority of nVidia GPU purchases are for gaming purposes...

    3. Re:Open Source community lacks professionalism by Anonymous Coward · · Score: 0

      The one thing I hate about modern society is this "act professionally" bullshit. It's essentially a translation for completely lack of humor and transparency. Why should everyone conform to some standard of behavior that is not backed up by any real argument except that corporate drones just expect you to behave in a certain way? Luckily, it's not as important in the academic world.

    4. Re:Open Source community lacks professionalism by progician · · Score: 1

      And what do you just think, why is Linux gaming in its infancy still? Think about it while you re-read your own post.

      I remember when NVIDIA came to our gaming studio, trying to sell their shit, with the promise that they make our game work better with driver updates. Of course, for some money. That means anti-competition behaviour that is tolerated in the name of IP.

    5. Re:Open Source community lacks professionalism by Tarlus · · Score: 2

      It makes the Linux and open source communities look bad when the man who has essentially become the face of it all is publicly throwing childish profanities at a major company for not offering software to Linux users in the way that he thinks they should. If we want help from other hardware manufacturers down the road then we should at least appear somewhat civilized. I enjoy using Linux but don't appreciate that this is how my best interests are being represented.

      It's enough of a miracle that nVidia has thrown a bone to Linux users at all. I have always appreciated that they have taken the time and effort to make Windows alternatives more viable. I would really rather not bite that hand...

      --
      /* No Comment */
    6. Re:Open Source community lacks professionalism by Teun · · Score: 1
      You are clearly not informed about what Linus said.

      Linus has repeatedly said he prefers FOSS but is OK with blobs when they do their task.
      In this particular interview he was complaining about nVidia's refusal to cooperate on an Optimus solution, something nVidia conveniently omitted from their 'reply'.

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    7. Re:Open Source community lacks professionalism by Anonymous Coward · · Score: 0

      Google "steve ballmer chair throw" and "steve ballmer monkey dance" and then lecture us about professionalism. Google "steve ballmer cancer" and lecture us about professionalism. I could go on for some time...

      BTW the nvidia driver shares most most of the code between Linux and Windows drivers (obviously excluding DirectX). The Linux drivers are at feature and performance parity with their Windows counterpart. The only other manufacture that has the same parity between the Linux and Windows drivers is Intel (although their GPUs are weak and mostly suck regardless of platform).

    8. Re:Open Source community lacks professionalism by ifiwereasculptor · · Score: 1

      Linus didn't take the perfect poilitical road. Nvidia, in their statement, did. The thing is Linus was complaining about some very real problems, while Nvidia's statement was void of any substance on the matter. And I'll take childish profanities over neglect, suspicion and condescension any day.

    9. Re:Open Source community lacks professionalism by Anonymous Coward · · Score: 0

      Fuck you.

  15. Disappointing response by peppepz · · Score: 5, Interesting

    Basically they're confirming Linus' words, not denying them. Linus never said that they don't make good drivers. He said that they suck at doing open source, which is an objective truth. Their response is that they do that because they don't want to invest resources to specifically support Linux. Which is exactly what Linus was upset about.

  16. Re:Ha ha ha! That crazy guy Ballmer... by Picass0 · · Score: 0

    Let's take a user interface designed for music players and cell phones and inflict it on Desktop and Tablet users!

  17. It is about Tegra by Anonymous Coward · · Score: 0

    The reason why you don't see a lot of android devices is that driver updates from nvidia is really bad. A lot of andriod phones are stuck at 2.2/2.3 because the old drivers won't run on the new kernel. Nvidia isn't really interested in releasing updated drivers for these old chips. If you want ICS drivers, get tegra3.

  18. Wayland by Anonymous Coward · · Score: 0

    If Nvidia wants their drivers to work with Wayland, they'll have to cooperate, since Wayland requires KMS to work. If Nvidia choose not to support Wayland, they'll lose customers.

    1. Re:Wayland by peppepz · · Score: 1

      Or the could sneak some ABI into the Linux kenel allowing them to continue using blobs as they do today.

    2. Re:Wayland by Anonymous Coward · · Score: 0

      Fuck Wayland.

      I've been saying this for ages, but I feel that now I must offer some background to avoid the impression that I am simply parroting Linus. Wayland offers no performance or security increases over X, simply because applications written for X will not work with Wayland, resulting in the incredible situation that Wayland will wrap itself around X. Why should I add another layer to my graphics stack? If I wanted to use a system that required me to half-assedly start X every time I wanted to use my favorite terminal emulator, I'd be using OS X.

    3. Re:Wayland by spitzak · · Score: 1

      X applications are already running on Wayland now. It's an X server called xwayland.

    4. Re:Wayland by Anonymous Coward · · Score: 0

      X is perfectly fine for terminal emulators, true. There's a lot of us that want modern, accelerated, tear-free, high performance graphics though. The only reason X even comes close to achieving that task is layers and layers of hacks that, while it's commendable that people have managed to twist X enough to manage that much, unfortunately just isn't good enough.

      By the by, X on Wayland doesn't add another layer of abstraction that isn't already there with a compositing window manager. It actually removes a layer.

    5. Re:Wayland by Anonymous Coward · · Score: 0

      Go fuck yourself, Wayland is a real need for our community, and it will take off you want it or not.

  19. lol.. consistency by sl4shd0rk · · Score: 5, Insightful

    I haven't had an NVIDIA driver work the same in Linux as it does in windows. Ever. Random screen blanking (nouveau driver), weird X errors (poly request too large or internal Xlib length error) and re-compiles every time there is a system kernel update. In comparison, all you need to do in Windows to get the NVIDIA driver working is hold down the enter key with a stapler while it's installing. Accept all the defaults. reboot. it's working.

    At "the end of the day" this is not consistency, it's crapsistency.

    --
    Join the Slashcott! Feb 10 thru Feb 17!
    1. Re:lol.. consistency by Bert64 · · Score: 1

      I have an XP box that would beg to differ, if i install the nvidia drivers on it the box won't boot anymore unless i go into safe mode and remove the drivers.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    2. Re:lol.. consistency by Anonymous Coward · · Score: 0

      What is this "reboot" after installing video drivers you refer to? Oh, perhaps you're referring to really, really old versions of Windows?

    3. Re:lol.. consistency by Anonymous Coward · · Score: 1

      Random screen blanking (nouveau driver).

      To be fair, nouveau is a project that receives no support or documentation from nVidia. While nVidia's lack of help contributes to the bugs in nouveau, it is somewhat unfair to blame nVidia for it.

    4. Re:lol.. consistency by Anonymous Coward · · Score: 0

      You are aware that the Nouveau driver is NOT developed by nVidia, correct? The binary nVidia driver in Arch is cake easy to install and I haven't had an issue with it, in Arch and in FreeBSD, in over 5 years. It just works. ATI / AMD makes decent / good hardware, but their drivers suck. Optimus would be nice, but I'll just run intel graphics on laptops. nVidia's loss.

    5. Re:lol.. consistency by spongman · · Score: 1

      now there's an express install. also, reboot is no longer required.

    6. Re:lol.. consistency by Anonymous Coward · · Score: 0

      What about not using nouveau and using the driver NVIDIA is rerefering to?

    7. Re:lol.. consistency by diego.viola · · Score: 1

      File a bug report to the nouveau project if you find any issues.

    8. Re:lol.. consistency by humanrev · · Score: 1

      Take a fresh install of Windows 7, install the NVIDIA drivers and let it finish. You'll be asked to reboot before they'll work.

      Take an existing install of Windows 7 with the NVIDIA drivers already installed, install a newer set of drivers and let it finish. You'll be able to use the new drivers without a reboot.

      In other words, stop being a fucking smart-ass - you don't know everything.

      --
      Most people on Slashdot are fucking idiots.
  20. I used to agree by h4rr4r · · Score: 3, Insightful

    These days I have a GTX460 and I get tearing all the damn time. I have turned off compositing, I have turned it on, I have switched to xfce I have tried gnome3.

    I hear the Open driver would fix this. If you can't even stop the tearing, then let someone else write your drivers.

    1. Re:I used to agree by Anonymous Coward · · Score: 0

      This is because the Nvidia driver supplies bogus refresh rate values to xrandr. The only way I've found to fix it completely is to disable compositing, and enable vsync and page flipping in nvidia-settings. XFCE works great, but it has its own compositor you must disable.

    2. Re:I used to agree by h4rr4r · · Score: 1

      I have disabled compositing and enabled vsync. I will check to see if I have page flipping enabled.

      How in 2012 you have a driver that does not work with xrandr and you claim it works I cannot understand.

    3. Re:I used to agree by Anonymous Coward · · Score: 0

      Agreed. Disabling compositing isn't a very good workaround either, since you miss out of some nice eye candy (wobbly windows can go to hell, but I like transparency, some slight shadows around windows, etc), and since the desktop itself isn't synced without compositing you get tearing on youtube etc. I have high hopes for Wayland fixing all this with its "every frame is perfect" philosophy, but of course given Nvidia's stance they're not very likely to support Wayland at all, specially since it requires KMS. Ever since Nvidia released their first GeForce I've never bought anything else, but it seems more and more likely that my next graphics card will be an AMD.

    4. Re:I used to agree by Anonymous Coward · · Score: 0

      Are you sure you have vsync activated?? No tearing at all here in games or videos for that case.
      I can even force vsync using NVIDIA control panel for games that does not support that feature.

    5. Re:I used to agree by h4rr4r · · Score: 1

      I have vsync turned on. I just looked at nvidia-settings.

    6. Re:I used to agree by Anonymous Coward · · Score: 0

      Except that the closed-source nvidia driver now supports RandR 1.2/1.3 (since May 2012 actually).
      http://www.phoronix.com/scan.php?page=news_item&px=MTA5NTY

    7. Re:I used to agree by h4rr4r · · Score: 1

      I saw that article and will be trying that. I prefer to just use the in distribution drivers.

    8. Re:I used to agree by Anonymous Coward · · Score: 0

      XFCE will always tear because they use the X11 Compositor instead of OpenGL. This is the main reason I do not use it. Not only does XFCE tear, but it tears *badly*.

      Gnome3, on the other hand, does not, provided you set things up correctly in nvidia-settings.

    9. Re:I used to agree by h4rr4r · · Score: 1

      I have compositing turned off and it still tears.

      If Nvidia is supposedly providing a working driver, it should work with X11 compositing.

    10. Re:I used to agree by chmod+a+x+mojo · · Score: 1

      So, you use old outdated drivers and complain when they don't work right? Makes sense.

      They release newer drivers for a good reason, not only to add support for newer cards but also to fix issues that came up in real world situations. And in this case even if the drivers had been FOSS it wouldn't have made a difference.... the fix is in a newer driver version that you aren't running. You can't even argue that it would have been easier to upgrade the FOSS driver since there is no guarantee that your distro would have included the update.

      --
      To err is human; effective mayhem requires the root password!
    11. Re:I used to agree by h4rr4r · · Score: 1

      So you think it is fine that for the past 8 months this hardware has had this issue?

      Even if I installed the lastest driver when NVIDIA sent them out I would still have tons of tearing for months.

      I bet they still don't work with compositing on.

    12. Re:I used to agree by Anonymous Coward · · Score: 0

      That's a beta driver.

  21. Sigh by Anonymous Coward · · Score: 0

    Nvidia has surely wronged here, the angry hippie want's them to give THEIR source code for FREE. Nothing wrong with that eh?

    I don't get it. It's their code, let them do whatever they wish with it, they paid money for making it.

    Vote with your wallet and go by Amd chips, stop griefing over stupid things.

    1. Re:Sigh by David+Chappell · · Score: 1

      Nvidia has surely wronged here, the angry hippie want's them to give THEIR source code for FREE. Nothing wrong with that eh?

      I don't get it. It's their code, let them do whatever they wish with it, they paid money for making it.

      Nobody wants their code. We want specs. Some of us think that if we buy a video card, we should be told how to operate it with a program we write. This was the industry norm in the MS-DOS days.

      Vote with your wallet and go by Amd chips, stop griefing over stupid things.

      I agree.

  22. Open source drivers are good for some things... by Alwin+Henseler · · Score: 4, Insightful

    Open source software in general has (among others) some practical advantages:

    1. You can keep using it as long as people are interested in doing so, even if underlying hardware or software platforms change.
    2. Any feature / improvement can be put in, when someone feels like putting in the effort.

    With a closed source driver, those 2 options are thrown in the trash. This is especially important for hardware drivers, if there's no way to patch drivers to work with newer versions of an OS (or another OS), then no further driver releases basically means: "throw away your graphics card".

    The net result may work fine for many people, but it tells me NVIDIA puts their roadmap before their user's roadmap(s). I read that as marketing, not user support.

  23. nVidia are not the worst by Anonymous Coward · · Score: 0

    ATI/AMD are the pathetic ones with the perpetually broken drivers, nVidia, with it's common platform and easy update (1 ring to rule them all) are not the worst by any means. Support nVidia.

    1. Re:nVidia are not the worst by BeansBaxter · · Score: 2

      As a former NVIDIA buy and a long time AMD owner I must respond to your ignorance AC. AMD over the last 2 years have release drivers as stable as I've ever had. Even better than NVIDIA's. Oh and they have community support for Linux with specs that they are willing to share. But go on with your ignorant bashing of a quality company with very strong cost effective products.

    2. Re:nVidia are not the worst by Anonymous Coward · · Score: 0

      Until you try a game... In my experience ati drivers works okay until you actually try to play a game with them.
      I also was unable to get my laptop working a year or two ago even though the driver officially supported my chip.

    3. Re:nVidia are not the worst by chmod+a+x+mojo · · Score: 1

      Ummm, yeah. ATI binary blob quite often kills suspend-to-RAM ( won't wake up properly - this HAS gotten better in the last years but isn't 100% yet), often ( in my experience ) hangs on logout - requiring you to set the option to kill and restart Xorg in the KDM / GDM config file, multi monitor ( plug and play ) on laptops is hit or miss... when it works it works, when it doesn't it is quite ugly. Not to mention ATI / AMD _could_ have just gone and used the VDPAU interface for shader decoding, but that is "EWWW NVidia supported" so lets go re-invent the wheel by adapting some obscure X extension ( making VA-API) instead of using the stable tested working API extensions that are already there...

      The FOSS radeon driver is much improved I will admit. Not suitable for gaming quite yet, but it is generally stable and has enough oomph to run light to midweight 3D acceleration. I use it on my ATI carded laptops over the blob driver just because it has better sleep support.

      --
      To err is human; effective mayhem requires the root password!
  24. Right to Repair bill in Massachusetts by Latent+Heat · · Score: 5, Interesting
    The Commonwealth of Massuchesetts is going to have a ballot question on whether auto companies have to reveal all of their "codes" so that independent repair shops (and I guess do-it-yourself people) would have access to diagnostics on cars. Some assembly member is attempting legislation to preempt the referendum question, telling the auto companies, "We can do this the easy way, or we can do this the hard way . . ."

    So, maybe we could get Bay State voters interested in open other things?

    1. Re:Right to Repair bill in Massachusetts by DigiShaman · · Score: 3, Interesting

      Federal law trumps state law. The auto manufactures could encrypt the computers and any attempt to crack it would be grounds for violating the DMCA (anti-circumvention portion).

      --
      Life is not for the lazy.
    2. Re:Right to Repair bill in Massachusetts by Belial6 · · Score: 2

      and I guess do-it-yourself people

      I am not a do-it-yourselfer when it comes to repairing cars. I am however aware of just how many mechanics will rip you off, and on more than one occasion caught a mechanic breaking things so that they can later fix it. I want access to my error codes so that when I can know that the engine light came on because the gas cap is loose or a fuse blew out before I get to the mechanic who tells me that the on board computer needs replacing at $1000.

    3. Re:Right to Repair bill in Massachusetts by rraylion · · Score: 1

      Encrypt the hard drive all you wish, all they are asking for are the expected input and output specs. This does not have to change with an encrypted source.

    4. Re:Right to Repair bill in Massachusetts by Lonewolf666 · · Score: 5, Interesting

      Getting a bit off topic, but I don't see the conflict between Federal law and state law.

      By not providing the codes (including decryption codes for encrypted onboard electronics) the auto manufactures would be violating state law. Instead of trying to crack the encryption, auto mechanics could sue them. No DMCA violation necessary there.

      --
      C - the footgun of programming languages
    5. Re:Right to Repair bill in Massachusetts by MarkGriz · · Score: 4, Insightful

      Good luck selling your cars in a state where you don't comply with state law.

      Do you think car manufacturers don't have to meet California's tougher emissions standards because Federal law trumps state law?

      --
      Beauty is in the eye of the beerholder.
    6. Re:Right to Repair bill in Massachusetts by DigiShaman · · Score: 1

      Federal EPA standard are such that individual states must meet or exceed the Federal standards. The way in which the law was codified gives states the provision to do this.

      Again. Federal Law trumps state law! Unless not codified.

      --
      Life is not for the lazy.
    7. Re:Right to Repair bill in Massachusetts by MimeticLie · · Score: 1

      The DMCA is irrelevant in this case. The state law doesn't say you have the right to circumvent diagnostic code encryption, it says that auto manufacturers have to make their diagnostic codes public. The car companies could legally encrypt the codes, they just wouldn't be able to sell their cars in Massachusetts.

    8. Re:Right to Repair bill in Massachusetts by cwebster · · Score: 1

      Go to an O'reilleys auto part store, they'll pull your engine codes for free for you. Some small oil change places will do it also in my experience. Fuses? Just look at them, or buy a cheap tester to probe them.

    9. Re:Right to Repair bill in Massachusetts by DigiShaman · · Score: 1

      While I'm sure they would be in direct violation of Massachusetts law, the whole argument would be rendered moot should the industry take it to the federal court. Massachusetts most likely would lose. I say "most likely" because there has and will forever be legal battles of state law vs federal law. Even to this day, Texas battling EPA provisions. An entire STATE. So ya, entirely possible Auto Industry vs. Massachusetts could happen in court.

      --
      Life is not for the lazy.
    10. Re:Right to Repair bill in Massachusetts by drinkypoo · · Score: 2

      Do you think car manufacturers don't have to meet California's tougher emissions standards because Federal law trumps state law?

      Yes, in cases where there is a California model and a Federal model, the federal model meets different emissions standards. You can't sell them new in California, you can sell them used. Nothing prohibits you buying a car in another state and smogging it in California, and California does not expect your vehicle to have California-specific equipment swapped in so that you can meet the California-model tailpipe numbers or equipment requirements.

      So, you're wrong, this falls under interstate commerce. Hell, The People of California voted to increase emissions restrictions (i.e. decrease allowable tailpipe emissions) and the federal government told us we couldn't, and remember, this applies only to new cars sold within California.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    11. Re:Right to Repair bill in Massachusetts by Spamalope · · Score: 1

      Go to an O'reilleys auto part store, they'll pull your engine codes for free for you. Some small oil change places will do it also in my experience.

      They can pull the basic, very limited OBD information. The really useful information that gives the dealer a huge advantage in repairing your car is restricted to protect the high dealer repair prices.

    12. Re:Right to Repair bill in Massachusetts by mk1004 · · Score: 1

      IIRC, federal law requires that automakers use common codes for certain diagnostics but manufacturer-specific codes do not have to be disclosed. Remember a few years back with the Toyota uncommanded-acceleration issue? There was something of a stink about how only someone from the factory could read out the crash data that Toyota, along with many other car manufacturers, record.

      In your case, having the codes doesn't necessarily help, other than obvious "we replaced your ABS controller because the codes said you had a MAF lean code" stuff. But sometimes the actual problem isn't readily apparent from the codes that are thrown.

      More on topic, the law generally isn't going to get involved unless there's some issue with restricted competition. For cars, it's dealers versus independent auto mechanics that are driving the laws regarding diagnostic codes. For graphic cards, I don't see how that could apply. No one has been making money providing third-party graphics drivers and are now in jeopardy because of nVidia's closed systems.

      --
      I can mend the break of day, heal a broken heart, and provide temporary relief to nymphomaniacs.
    13. Re:Right to Repair bill in Massachusetts by Anonymous Coward · · Score: 0

      It depends if the court sees it in a similar light as Lexmark and their toner cartridges.

      http://en.wikipedia.org/wiki/Lexmark_Int'l_v._Static_Control_Components

    14. Re:Right to Repair bill in Massachusetts by morgauxo · · Score: 1

      I don't think Mass is going to do anything like that. They could just not allow those cars to be sold in Mass. It works for California, they require stricter environmental controls and all US cars get them because that is easier than making a special California version and that market is too big to lose.

    15. Re:Right to Repair bill in Massachusetts by Anonymous Coward · · Score: 0

      Federal law trumps state law. The auto manufactures could encrypt the computers and any attempt to crack it would be grounds for violating the DMCA (anti-circumvention portion).

      You're already violating the DMCA by hacking their ROT26 encryption. Send this man to prison!

    16. Re:Right to Repair bill in Massachusetts by Anonymous Coward · · Score: 0

      Good luck running your state if you make it impossible to sell cars there. And good luck dealing with people who let their out of state family buy them a car that remains registered in the family name.

      Your solution will only work if a significant number of states participated. One is not enough.

      Massachusetts is a horrible place for drivers, anyways. I can't even use their tunnels, because, apparently, Massachusetts can't build them properly (propane is banned from them, my car runs on it). Of course, NY and PA don't seem to have such an issue engineering their tunnels properly. Even Massachusetts seems to have at least figure out how to engineer them for NG (which is lighter than air, and that might be a valid argument, if it weren't for the fact that gasoline cars are still permitted in the tunnels).

      Why did I care? I went to PAX. What a pain in the arse it is to drive around Boston without using a tunnel. I found at least two intersections where there was only one way I could drive, and the H/C logos can't be seen until you're making your turn. Ugh.

    17. Re:Right to Repair bill in Massachusetts by Anonymous Coward · · Score: 0

      California is a special case: "The state of California has special dispensation to promulgate more stringent vehicle emissions standards, and other states may choose to follow either the national or California standards."

      http://en.wikipedia.org/wiki/Emission_standard#USA

    18. Re:Right to Repair bill in Massachusetts by Anonymous Coward · · Score: 0

      You obviously do not understand this at all.
      Thats ok, I can lead you to water.

      Fed gov says: You may encrypt and no one can break your encryptions.
      Auto CEO says awesome, encrypt away.
      Mass Gov says thats cool but you have to give us the keys.

      The mass gov hasn't forced anyone to break the encryption, they just forced the keys to be public in that state. Since the keys are public, then anyone can legally decrypt.

      Do you get it now?

      Those are very different things.

    19. Re:Right to Repair bill in Massachusetts by cwebster · · Score: 1

      Didn't know that. The newest car I've owned is a '97 and barely speaks OBD II.

    20. Re:Right to Repair bill in Massachusetts by spire3661 · · Score: 1

      Federal law does not always trump state law. The Federal government might want you to think that, but its simply not true.

      --
      Good-bye
    21. Re:Right to Repair bill in Massachusetts by sjames · · Score: 1

      State law (for example): Publish codes in usable form or it's $1000 per car.

      Auto makers: here it is but it's encrypted. ('70s dancing "It's fun to rape you with Deeee Emmmmm Seeeeeee Ayyyyyy).

      State: Cool, that'll be $500 million dollars or we can confiscate these cars and auction them off.

    22. Re:Right to Repair bill in Massachusetts by CompMD · · Score: 1

      Unfortunately, Volkswagen plays a similar game on a daily basis. Their TDI models specifically require #2 diesel fuel, with no more than 5% biodiesel content. Any different fuel will void the warranty and (they claim) may damage components in the fuel delivery and exhaust systems. In Illinois, "#2 diesel" can contain up to 20% biodiesel, and you aren't guaranteed a specific percentage. Essentially, VW is selling cars in a state where you cannot fuel them.

    23. Re:Right to Repair bill in Massachusetts by David+Chappell · · Score: 1

      Federal law trumps state law.

      Not necessarily. The constitution defines certain areas in which the federal goverment can make laws. If a matter is clearly in that area, the federal law trumps. If it is clearly not in that area, the federal law can be struck down outright as unconstitutional. There are numberous grey areas which create controversy.

      The auto manufactures could encrypt the computers and any attempt to crack it would be grounds for violating the DMCA (anti-circumvention portion).

      If this is information that they are legally required to disclose, this trick would not work. If things worked that way, I could encrypt my tax return and tell the IRS, "I have filed as required. Sorry you can't read it, but we have the DMCA, you know."

    24. Re:Right to Repair bill in Massachusetts by Anonymous Coward · · Score: 0

      California is allowed to have their own emissions regulations because their EPA predates federal EPA and has been kind of grandfathered in. No other state has been allowed to have their own emission regulations.

    25. Re:Right to Repair bill in Massachusetts by David+Chappell · · Score: 1

      While I'm sure they would be in direct violation of Massachusetts law, the whole argument would be rendered moot should the industry take it to the federal court. Massachusetts most likely would lose.

      I would expect the case against Massachusetts to be dismissed quickly. There would be no conflict whatsoever between the laws. By publishing the information encrypted form the auto manufacturer would be engaging in a straightforward violation of the state law. The DMCA does not grant anyone special authority to encrypt anything and certainly not as a way to evade legally required disclosure.

    26. Re:Right to Repair bill in Massachusetts by David+Chappell · · Score: 2

      Good luck running your state if you make it impossible to sell cars there.

      This would not make it impossible to sell cars there. The auto manufacturers are already providing these service manuals to their dealers. This law would require them to sell them to anyone who wants to buy them. This doesn't make it even difficult for them to sell cars there.

    27. Re:Right to Repair bill in Massachusetts by Anonymous Coward · · Score: 0

      Not true. The codes coming out of the computer are just numbers. A table listing codes and what they mean does not circumvent any technological measure. So P0120 is a throttle position sensor malfunction (I drive a Chevy so I have many of these codes memorized from seeing them so often). Keeping the codes secret is more along the lines of the police department not letting you know what a code 454 is. But DMCA would not apply.

    28. Re:Right to Repair bill in Massachusetts by hey! · · Score: 1

      Federal law trumps state law. The auto manufactures could encrypt the computers and any attempt to crack it would be grounds for violating the DMCA (anti-circumvention portion).

      Saying the have to *reveal* their diagnostic codes is entirely consistent with rules against circumvention. In fact, THAT'S THE POINT: allow users to repair their property without circumventing anything.

      So there is no issue of Federal preemption here. It preempts private companies from doing certain things which would entice their customers to break Federal law.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    29. Re:Right to Repair bill in Massachusetts by Anonymous Coward · · Score: 0

      no it doesn't.

    30. Re:Right to Repair bill in Massachusetts by Anonymous Coward · · Score: 0

      Not Really. That's why there are states, to trump Federal "law".

    31. Re:Right to Repair bill in Massachusetts by MrResistor · · Score: 1

      Nothing prohibits you buying a car in another state and smogging it in California, and California does not expect your vehicle to have California-specific equipment swapped in so that you can meet the California-model tailpipe numbers or equipment requirements.

      You can buy it, sure. But in order to register it, and thus legally operate it on public roads, it still has to meet the same emissions standards as the California model (and by law the seller is responsible if it doesn't).

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    32. Re:Right to Repair bill in Massachusetts by drinkypoo · · Score: 1

      You can buy it, sure. But in order to register it, and thus legally operate it on public roads, it still has to meet the same emissions standards as the California model (and by law the seller is responsible if it doesn't).

      Nope. The car has to have been sold to you in another state, at which point you can register it here in California, under its normal federal emissions standard, which is how Californians were getting TDIs for a while; they simply weren't sold in California at all. California placed an additional tax on out-of-state vehicles for a while, and eventually had to refund it because it was unconstitutional.

      However, this is all basically irrelevant now because the federal standard is the standard, and California does all it can to remove older vehicles from the road including encouraging and defending illegal tows and so on. (I had my 1960 Dodge Dart red-tagged on one street, so I moved it to another street entirely, from which it was towed...) The California and Federal models alike have EGR or DPF or what have you, and if there is any difference it lies in programming.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    33. Re:Right to Repair bill in Massachusetts by Anonymous Coward · · Score: 0

      Most error codes are already available, at least in the category you describe.

      Buy a good scanner, not the cheapies. I got an EQUUS 3140, that model specifically because it works on many cars older than 1996. I Live in Mexico and there are a lot of older cars.

      This model and its EQUUS siblings let me watch live data as the car warms up, also watch the sensors in operation.

      I realize there are some special things on some luxury cars. My son even told me there is a car which requires a special scanner/controller to change the &^%$# oil.

      But, all cars must comply with the current OBDII requirements, which are open information.

  25. OP here.. by Anonymous Coward · · Score: 1, Insightful

    Openly bashing NVIDIA for doing things their way is wrong, because it's their product, and, therefore, their decision.

    I'd really love to see NVIDIA open their specs, but if they don't want to, they're not going to because they don't need to.

    And I completely agree with this from a business perspective. It's easy to rant or cheer from the sidelines when you don't have a business to run. NVIDIA produces some of the best GPU architectures on the market, arguably the best in their industry, and I can understand that they would like to do everything they can to not lose their trade secrets. Especially with AMD not doing so great against Intel in the CPU market..

    1. Re:OP here.. by David+Chappell · · Score: 5, Insightful

      Openly bashing NVIDIA for doing things their way is wrong, because it's their product, and, therefore, their decision.

      The right to make a decision does not include the right not to be criticised for the descision one make.

    2. Re:OP here.. by Anonymous Coward · · Score: 0

      > Openly bashing NVIDIA for doing things their way is wrong, because it's their product, and, therefore, their decision.

      And we're the customers, on whom NVIDIA depends for their livelihood. So it seems we have something to say about what kind of product they should offer.

    3. Re:OP here.. by progician · · Score: 4, Insightful

      because it's their product, and, therefore, their decision.

      As long as they don't sell it. Once they sold their products to millions of user, they are also responsible for that what they are selling has no built-in secrets what so ever.

      NVIDIA sells hardware. That's one market. NVIDIA distribute software. That's an other. Not releasing the information about their hardware creates a situation where NVIDIA (an the rest of the hardware market virtually) is abusing its market leading position on one market, to sniffle the other. All this because of contracts all around between Microsoft, the gaming industry and so on. For fuck sake, that's my fucking video card, I'd like to know how to use it. I didn't by with a computer, and I could use it in a completely different architecture. No, they narrow the market choices, to control not the product, but the customers, so they can get juicy extra money through anti-competition deals from software companies.

    4. Re:OP here.. by Omnifarious · · Score: 3, Insightful

      No, I'm happy to openly bash them repeatedly for making a choice that sucks. Yes, it's their choice to make. If I didn't think that, I would be advocating they be sued to force them to make a different choice. Otherwise, I'm expressing my opinion of their awful and stupid choice. And I should be perfectly free to do that. It's not like freedom is a one-way street here.

    5. Re:OP here.. by wisty · · Score: 5, Insightful

      I wouldn't call Linus's off-the-cuff speech "bashing". While his exact words were "Fuck you, nVidia" it was in a jovial sort of way. Americans might not understand, but for most English speakers (especially Brits and non-natives) "Fuck you" is not always incredibly harsh.

      His main criticism was, they were making a lot of money off Linux (selling chips to run Android), and were being difficult to work with.

      Also, it was an off-the-cuff remark. He's not a Presidential candidate or CEO, he's a programmer. Some people talk in a way that PR flacks don't, and if they are well known it causes a bit of a PR shitstorm. The media reports their "rant", instead of the 49 other minutes before it, in which they were speaking quite insightfully.

      Seriously, everyone knows about the Tanenbaum–Torvalds "flame war", in which Linus came up with such withering remarks as "linux still beats the
      pants of minix in almost all areas", and Andrew shot back with things like "You would not get a high grade for such a design :-)", and sprouted fanatical anti-free-software rhetoric like "For the true hacker, not having source code is fatal, but for people who just want a UNIX system, there are many alternatives (albeit not free)".

      Strong stuff.

      I guess people are more interested in shit-slinging (or even pretending that there was shit-slinging) than the technical points these guys raise.

      I've heard Linus is a bit mean at times (rejecting patches? refusing to mentor new contributors?), but the idea that he's an angry angry man seems to be more myth than anything.

    6. Re:OP here.. by Weatherlawyer · · Score: 0

      Openly bashing NVIDIA for doing things their way is wrong, because it's their product, and, therefore, their decision.

      You are right they shouldn't ever be told that they are making a mistake.

      How long have you been employed by AMD?

      I'd really love to see NVIDIA open their specs, but if they don't want to, they're not going to because they don't need to.

      Absolutely

      And I completely agree with this from a business perspective. It's easy to rant or cheer from the sidelines when you don't have a culture to run.

      Ah, hang on. I can remember when the railways were de-nationalised in this country. The morons who got the control suddenly decided that people who used bicycles were going to have to pay for their tickets and their bike's space on the train.

      So the people who had bikes had a choice, use the bike or use the car.

      NVIDIA produces some of the best GPU architectures on the market, arguably the best in their industry, and I can understand that they would like to do everything they can to not lose their trade secrets.

      And that means their architecture will be the best?

      How does that work when the people who need to know can't couple their expertise with their expertise?

    7. Re:OP here.. by UnknowingFool · · Score: 1

      Yeah and Linus' comment was an answer to a question that someone asked to him specifically on the subject. It wasn't a tangent. The disagreement between Tenebaum and Torvalds was strictly about theory. I agree with Tenebaum that microkernel provides many advantages over the kernel design of Linux but only in theory. As the Hurd project has shown, the reality of designing a microkernel for practical usage is harder than it seems.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    8. Re:OP here.. by Anonymous Coward · · Score: 1

      Not to mention that, as there are exactly two major graphics providers left, they both have obligations not to abuse their duopoly. If they couldn't get away with it if they had more real competition, they should (at least) be criticized if they do it now.

    9. Re:OP here.. by mk1004 · · Score: 2

      Ah, hang on. I can remember when the railways were de-nationalised in this country. The morons who got the control suddenly decided that people who used bicycles were going to have to pay for their tickets and their bike's space on the train.

      So the people who had bikes had a choice, use the bike or use the car.

      Uh, so the bikes take up space that could otherwise be used by paying passengers, but you don't think you should pay more? So if someone rides the train but doesn't take a bike with them, they should subsidize those who do by paying the same?

      You're either using a poor analogy to make your point or you don't seem willing to acknowledge the concept of paying for what you use. Unlike the railroads, nVidia is in competition and is trying to keep a competitive edge. We may disagree with them on how they are doing that, and we are free to criticize them. They are free to ignore us, and we are free to take our business elsewhere.

      --
      I can mend the break of day, heal a broken heart, and provide temporary relief to nymphomaniacs.
    10. Re:OP here.. by Anonymous Coward · · Score: 0

      Once they sold their products to millions of user, they are also responsible for that what they are selling has no built-in secrets what so ever.

      Uh sorry, but no. They have no responsibility whatsoever to not include "built-in secrets." The only requirement they have is to provide the support that they advertised it to support.

      For example, say you worked for a radio-controlled helicopter company and, as an engineer, you spent a year of your time developing a stabilization technique in hardware and software that was far better than any other manufacturer could produce. Should you be required to just hand over the details of all the hard work you put into it, just so all the other companies can duplicate it without any effort at all? No, you're going to burn the copy protection fuse on your microcontroller and grind off the part numbers to make it as hard as possible to recreate so you can get monetarily compensated for your work.

      Now, if you have a personal problem with that, you are free to purchase a different, inferior product until another manufacturer decides to spend the time to figure out what you did.

      For another example, you could ask the manufacturer of the CDMA chip in your Android phone for interface details or firmware source code, and you will be directed to a brick wall. Releasing that information could cause instability of the cell networks for many users when hacker Joe releases a "new and improved" firmware that does not adhere to the CDMA specs.

      tl;dr If you don't like nVidia's practices, you have the freedom to buy ATi. We all know how well those drivers work under Linux.

    11. Re:OP here.. by Anonymous Coward · · Score: 0

      No - he specifically mentioned that he thought it was better to speak his mind regarding bad code/ideas even though he thought it may be harsh. Frankly, that's the only way to get through with some earnest and very well meaning people that just don't understand how things work.

      He explicitly said that he came to that conclusion after people had put major work on ideas that he didn't support because he was trying to be nice about letting them down.

      I'd rather tell someone to fuck off and get lost (my expression here!) than try to be nice and unintentionally see them continue years of work only to eventually have to make a decision that the inclusion of such work wouldn't happen - and then for them to be genuinely suicidal.

      Amazingly, context matters.

    12. Re:OP here.. by Anonymous Coward · · Score: 0

      because it's their product, and, therefore, their decision.

      As long as they don't sell it. Once they sold their products to millions of user, they are also responsible for that what they are selling has no built-in secrets what so ever.

      NVIDIA sells hardware. That's one market. NVIDIA distribute software. That's an other. Not releasing the information about their hardware creates a situation where NVIDIA (an the rest of the hardware market virtually) is abusing its market leading position on one market, to sniffle the other. All this because of contracts all around between Microsoft, the gaming industry and so on. For fuck sake, that's my fucking video card, I'd like to know how to use it. I didn't by with a computer, and I could use it in a completely different architecture. No, they narrow the market choices, to control not the product, but the customers, so they can get juicy extra money through anti-competition deals from software companies.

      I have to disagree with you. They don't need to tell you how it works. I've been using closed-source nvidia linux drivers for a long time on both Ubuntu and Suse and been happy with it - never really had any problems.

      Nvidia makes a product that works, and if you don't like it, it's not a monopoly. There are 3 very large and several small manufacturers of video chipsets. They work deals with software companies because it makes sense. You buy a video card from them use software that needs cards that perform well.

      It is your fucking video card, and they aren't going to go after you for reverse-engineering, reflashing, sottering, updating, selling, mailing, or destroying it. You can do whatever you want with it.

      They sold a product, you bought it, and that's where their obligation ends. They've never been wishy-washy on where they stand - so this shouldn't be a surprise.

    13. Re:OP here.. by Anonymous Coward · · Score: 0

      While his exact words were "Fuck you, nVidia" it was in a jovial sort of way. Americans might not understand, but for most English speakers (especially Brits and non-natives) "Fuck you" is not always incredibly harsh.

      An minor point but Americans = most English speakers.

    14. Re:OP here.. by Anonymous Coward · · Score: 0

      As long as they don't sell it. Once they sold their products to millions of user, they are also responsible for that what they are selling has no built-in secrets what so ever.

      [Citation needed]

    15. Re:OP here.. by Anonymous Coward · · Score: 0

      He was asked a simple question. A women in the audience (clearly a very techy bunch) asked why her laptop didn't work properly. She was aware of Linux + Nvidia binary drivers, was expect support at some point, but after 18 months it was never forthcoming. This was a very sore issue because many many Linux users were burned by this, and were relying on NV's unified driver to address the crap surrounding "Window only" for this particular graphic chipset.

      The fact NV won't put a wrapper in the kernel to stabilise the ABI they desire, nor will they cooperate with any kernel developers to do so, is another issue. Rolling your own kernel, testing etc, means NV's driver will break over and over. Sometimes any-any patches are released, sometimes not. It's a complete mess.

      Add to that NV are desperate for part of the Android market, Linus said something like 900,000 new activations per day were being made (according to Google). And still NV will not cooperate.

      Linus isn't moaning about their lack of open source drivers, he's moaning that this company never cooperates despite trying to make large sums of money from Linux machines and that it's in their interest to do stop ignoring devs of both Linux and xorg.

    16. Re:OP here.. by adisakp · · Score: 1

      As long as they don't sell it. Once they sold their products to millions of user, they are also responsible for that what they are selling has no built-in secrets what so ever.

      Ummm... no, millions of people buy stuff with built-in secrets on a daily basis. For example, 11 secret herbs and spices. Don't like secrets? Then fry your own chickens.

    17. Re:OP here.. by Anonymous Coward · · Score: 0

      yep

      -like their decision to knowingly ship flawed mobile graphics chips which overheated and borked thousands of laptops, getting manufacturers including Dell,HP and even Apple in trouble with customers who found out about it...

    18. Re:OP here.. by Anonymous Coward · · Score: 0

      Depends if your rail network is state run, state-run for profit, or corporate. State-run not-for-profit's could care less, until the seats were all full all the time which would usually result in more trains, who brought what on to the trains. Within reason. Obviously for-profits would try to take as much cash as possible charging for every square millimetre, milligram, and advertising space available to them. And no, you cant take your business elsewhere with most countries with rail networks. Especially now they are dying off in some regions in favour of automobiles.

      Where would you place GNU/Linux in such an analogy?

      From my point of view 12000 kilomtres away, your analogy does not make much sense to me. It sounds very McAmerican-centric. "Our way or the tollway".

    19. Re:OP here.. by wisty · · Score: 1

      The country with the greatest number of English speakers is India (roughly 25% of the population of India). USA is about 2/3ds of native English speakers, but most English speakers aren't native.

    20. Re:OP here.. by progician · · Score: 1

      11 secret herbs and spices? What? And for the record, I do roast my own chicken man, it's not that hard... Also, very week analogy as the chicken is easily paired with other food because it's a quick taste and you know what sides it needs. Also, you have the information that it is a chicken. That's the fucking big difference. You can find the sketch of chickens in any biology book.

      On the other hand, your argument is getting weaker every time I think about it. The fact that people use stuff with built-in secrets does not make the problem go away. We have a politico-economical system that encourage keeping dangerous secrets, and then people wonder why the fucking economy falls apart. I tell you why: consumers and producers are kept in dark, lack of information that would be essential to make informed decisions. So much for markets, and so much for democracy. So, if that is the case, we ought to change it IMHO.

  26. I Have Already Purchased The Card!!! by zenlessyank · · Score: 0

    Since the purchase has been made, then NVidia has made their money. Since NVidia has already decided to write drivers for Linux, it only stands to reason that that NVidia is getting paid by another OS manufacturer to NOT open the API's or source code for optimizations, which is what I think several other posters have stated in so many words. And if I remember correctly, what is good for the goose, is good for the gander, so I would imagine that AMD/ATI is also getting paid, hence the same deal from both companies. Money talks, bullshit gets 2D.

  27. Linus needs to look in the mirror by Anonymous Coward · · Score: 0

    Since I am a FreeBSD user this problem also occurs with...gasp...linux! As in companies and developers only support Linux versions of their software. I still build it myself when I can anyway. For instance I had to jump in with my own custom changes and make Bitcoin-QT build in qtcreator under FreeBSD 9.0 because it didn't "just work". So did I yell at the BitCoin devs for this or Nokia claiming they make the single worst IDE in the planet? Not really- in fact how I felt was that with all the advances with Linux its just so fragmented and the efforts behind it are so aloof and out for profit that they are now worse than microsoft and almost as bad as apple. Old age has made Linus very ornery and when it comes down to it kids its all about money. I would rather be able to "actually" compile everything from source than get linux binaries when a project is unable to be cross-compatible due to the "unholy mess" Linus has created. Time to get a new spokesman- when I read this I could have mistaken Linus for Ballmer there.

  28. Small number of bins of numbers of defects by tepples · · Score: 3, Informative

    it's common for perfect chips to be marketed lower than what they can actually do.

    You do realize that the whatsit where the defect is doesn't actually work, right?

    For one thing, perfect chips get marked as defective if there aren't enough defective chips to meet the demand for low-end hardware. For another, there are probably only a small number of bins of numbers of defects. If there are models with 48, 64, and 96 working whatsits, and 63 of them work, it'll be sold as a 48, and drivers won't be able to use 15 of the working whatsits.

  29. The community failed on ATi by ndtechnologies · · Score: 3, Insightful

    So ATi opens up, and the community COMPLETELY failed to deliver a usable solution. WTH should Nvidia care? The FOSS community has already shown that they can't do it. Mod me down if you want, but I speak the truth. We failed. As long as Nvidia continues to provide a driver that works, and works well (which it does), then I will always use Nvidia cards.

    --
    I have nothing clever to put here...
    1. Re:The community failed on ATi by cockroach2 · · Score: 4, Interesting

      Huh? The radeon driver is pretty damn good these days.

    2. Re:The community failed on ATi by BeansBaxter · · Score: 2

      Don't bother him with facts.

    3. Re:The community failed on ATi by Rogerborg · · Score: 1

      For certain definitions of "radeon", "pretty", "damn" and "good".

      Seeing is believing. You see it working fine, so you believe it. I see flickering, tearing, a Unity 3D desktop that regularly explodes into shards, and occasional hard lockups, so I believe that. Installing the ATI binary driver solves my problem.

      The "works for me, you must be doing something wrong" attitude prevalent in open source gets tiring pretty fast, by the way.

      --
      If you were blocking sigs, you wouldn't have to read this.
    4. Re:The community failed on ATi by cockroach2 · · Score: 1

      Seeing is believing. You see it working fine, so you believe it. I see flickering, tearing, a Unity 3D desktop that regularly explodes into shards, and occasional hard lockups, so I believe that. Installing the ATI binary driver solves my problem.

      "pretty damn good" doesn't mean "free of bugs" and compared to the binary ATi driver it works significantly better (at least for me), supports all the latest fancy stuff (KMS etc.) and generally just does its job without needing special attention – pretty much what I'd expect from a driver. That there are issues is unfortunate but happens to any piece of software (I still occasionally get a corrupted mouse pointer).

      The "works for me, you must be doing something wrong" attitude prevalent in open source gets tiring pretty fast, by the way.

      Which I said where exactly? Loving the attitude, btw.

    5. Re:The community failed on ATi by Anonymous Coward · · Score: 1

      I have an AMD A6 APU. It does not work on BSD. It does not work on many linux distros. The binary blob works on a 3.x linux kernel if you get the magic list of software installed. There is no open source solution yet.

      No, we have failed.

    6. Re:The community failed on ATi by Andy+Dodd · · Score: 2

      If you actually bothered to read his complants, they were directed at Optimus (almost completely unsupported in Linux) and Tegra (Nvidia is making a shit-ton of money off of Linux and not being cooperative. Their PR bullshit about contributing to Linux is inconsistent with the reality of the code. They might have had the most changes from 3.3 to 3.4 - but that's probably because their shit was in the worst state to begin with. Even in 3.4, looking at their codebase it's woefully incomplete in mainline, for example the cpuidle driver is missing the most important power-saving states. Their support is simply shit compared to TI's OMAP support.)

      --
      retrorocket.o not found, launch anyway?
    7. Re:The community failed on ATi by ratboy666 · · Score: 5, Insightful

      The AMD community supports all (11 now?) chip types, over all (4 now?) generations of Radeon released (since 2000).

      KMS (kernel mode setting) and other features of the Linux graphics stack are supported over all hardware, including TV out, and other features.

      3D is a work in progress. Yes, it's been almost five years, but the features do work.

      I would say that, objectively, the open source drivers have been a success. I would even say that the open source drivers are arguably superior to the closed ones. Work continues (especially in the 3D area). Does the proprietary driver support stuff like multi-seat?

      Of course, you claim that it doesn't work at all, and that the effort has been for nought. Please clarify. Bug reports would probably be welcome (not sure, but check x.org, freedesktop.org).

      At the least, please post your hardware information, so that other people will know to avoid it.

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    8. Re:The community failed on ATi by Jeng · · Score: 1

      The "works for me, you must be doing something wrong" attitude prevalent in open source gets tiring pretty fast, by the way.

      Would you prefer it if it was worded differently?

      It worked fine for me so therefor I do not have the experience to help you with your issue, but I can demonstrate that it can work since it installed fine for me.

      Is that an acceptable response?

      --
      Don't know something? Look it up. Still don't know? Then ask.
    9. Re:The community failed on ATi by Anonymous Coward · · Score: 0

      Then stop whining and fix it or STFU. No-one is your servant here.

    10. Re:The community failed on ATi by Anonymous Coward · · Score: 0

      Ah, yes, because that "Unity desktop" is the epitome of software, right? And everything that goes wrong is the fault of the driver, right?

      Installing the ATI binary driver solves my problem.
      Post hoc ergo propter hoc

      Frankly speaking, this constant mudslinging and lying by nvidia fanboys and proponents for closed crapware is really getting obnoxious, by the way.

    11. Re:The community failed on ATi by cockroach2 · · Score: 1

      +1 Insightful.

    12. Re:The community failed on ATi by div_2n · · Score: 1

      Sounds like this problem which seem like it's fixed in the latest patches that will likely get rolled into 12.10. Not sure if they'll get back-ported to 12.04:

      https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/933289

    13. Re:The community failed on ATi by Anonymous Coward · · Score: 0

      That's only true for a limited definition of "supports." When Firefox and KDE can stop turning off features for cards that have capable hardware but incapable drivers then you can use "supports" in the same context as the rest of the world.

      Let's see the open source keep up with the GL spec instead of holding the whole damn platform back in 2.0 land. No one's turning off features or limiting their programs for the sake of NVIDIA.

      The gap is slowly closing but that doesn't mean you can ignore it. It's going to be interesting with Valve brining Steam to Linux. It'll be interesting to see if they can bring some real GPU hungry games to the table without requiring some binary only driver to do so.

    14. Re:The community failed on ATi by David+Chappell · · Score: 1

      So ATi opens up, and the community COMPLETELY failed to deliver a usable solution.

      I guess that depends on what you mean by "usable solution". I can now pop in a recent AMD card, install Ubuntu, and working opensource drivers are automatically installed. Hardware accelaration (including OpenGL support) just works. That's good enough for me. Perhaps you have stricter requirements.

    15. Re:The community failed on ATi by Anonymous Coward · · Score: 0

      I would say that, subjectively, the open source drivers have been a success.

      FTFY.

    16. Re:The community failed on ATi by Anonymous Coward · · Score: 0

      in all honesty as another AC, which also per defition makes me a consumer... "working" is a weird defition. 2 years and the latest is not the greatest, and you need something as ancient as 1XXX for a roughly full feature set. AMD is not great, but some of it works. The point is: They could at the least shared a bit of secret sauce in a closed mailing list.

  30. "Consistent Experience" by TechieRefugee · · Score: 1

    Yeah, sure, I guess they're right on that. Nvidia drivers have crashed my (now long gone) install of Vista and forced me to reinstall Linux Mint two times because both available proprietary drivers crashed the GUI, leaving me no access to my OS. Oh well, at least I didn't have much on there anyways.

  31. Hobson's choice by tepples · · Score: 1

    Also, its the user choice to buy their cards or not.

    What other choice is there for 3D graphics on a laptop, apart from Intel whose performance is perpetually 6 to 10 years behind?

    1. Re:Hobson's choice by Anonymous Coward · · Score: 0

      Let Intel buy Nvidia!

    2. Re:Hobson's choice by Anonymous Coward · · Score: 0

      Serious question: Why are laptops sporting AMD GPUs no longer viable? Amazon seems to offer a ton of those right now and with decent reviews.

    3. Re:Hobson's choice by higuita · · Score: 1

      what is wrong with laptops with amd/ati cards?

      you have plenty of laptops with amd/ati graphic cards, from low end to high end
      those laptops also come with cpus from amd and intel, so no excuse about wrong cpu.

      --
      Higuita
  32. Re:"nouveau" is the blank-screen-driver by armanox · · Score: 1

    Umm...What?

    I haven't had any issues* with nouveau. If you need a compatitbility list, I've used it with a GT210, GT240, 9800GT, 6200, 7150, Quadro FX 1800, and currently a GTX 460 (can't recall if I ever used it with a Geforce 3). Usually I use Red Hat or Fedora, but I've not had issues with my cards when I've used Gentoo, Ubuntu, Debian or Slackware either.

    *I preferred the nvidia driver when gaming under Linux, it provided much better 3D preformance. But, that was several years ago I must admit (Neverwinter Nights was the main game I was playing at the time).

    --
    I'm starting to think GNU is the problem with "GNU/Linux" these days.
  33. Damn good idea. by Picass0 · · Score: 1

    Apart from the video card issue, I hate auto makers for playing this game. Good for MA. They catch a lot of crap but this is good legislation. I hope other states follow their lead.

  34. What Torvalds wants.... by Anonymous Coward · · Score: 0

    ... is a access to the power-saving features. All he wants is access to the API, and how it runs, so his laptop won't suck. Even the closed source driver doesn't provide it on Linux.

  35. Is he selling access to his bank account? by Anonymous Coward · · Score: 1

    Because, unless I have this "manufacturer" business thing all cockeyed, NVidia *sell* their hardware. He doesn't *sell* his bank account.

    PS my PIN is 5014.

    How much has that helped you?

  36. Open Computer by Anonymous Coward · · Score: 0

    I would buy a completely open computer. Open BIOS, open chip design, everything. Could someone explain to me why it doesn't exist yet? Let China manufacture it, and the F/OSS community provides the code. Is it simply because no free design exists?

    1. Re:Open Computer by Robert+Zenz · · Score: 1

      It doesn't exist because that would mean the it would be easily copyable...and we don't the other kids playing in our sandbox, do we?

      On a more serious note, the problem in this case is the market. Why should I spend much money on inventing something, just to give it to everyone basically free of charge. Sure, that is how FLOSS works, but that is only *very* slowly adopted around the rest of the world.

    2. Re:Open Computer by progician · · Score: 2

      It's certainly not impossible to do, but there's a huge difficulty. Computer architectures today involve a lot different bits and pieces from different manufacturers. To get all the pieces from completely new manufacturers who are willing to give all the specs, I mean, ALL THE SPECS is pretty hard given that most of the existing companies are involved in some market distorting practices, such as patents, holding back the manuals, and copyright and other bullshit.

      Even worse, because we already have a billion-magnitude user base who have gadgets and computers based on standards which come these dodgy practices, a completely new architecture would be doomed to fail because the market is saturated in terms of available options that consumers are willing to choose. You have to serve millions of legacy apps and if the new brand fails any of that, the system will not last long. I mean, you can see here and elsewhere that the consumer culture of technology is deliberately was kept in the dark, and now the darkness dictates not any rational sense. So, when somebody considers a new phone, don't give a shit about the actual technical issues or the software maintainability on the really long run, only the cool factor and the possibility of running the Angry Birds. Symptomatic to our age, the consumer age, where everything made for throwing away in order to generate false growth. Anyway, a completely open architecture would be enormous advance in our life time, but it must measure up to the currently existing technologies right away, or will phase out without a trace.

    3. Re:Open Computer by Anonymous Coward · · Score: 0

      It doesn't exist because that would mean the it would be easily copyable...and we don't the other kids playing in our sandbox, do we?

      Sure it does, otherwise Stallman wouldn't have anything to compute on.

  37. Android by Anonymous Coward · · Score: 0

    The video card binary blobs are only half the concerns he voiced. The other problem is NVIDIA selling of massive numbers of undocumented Tegra chips to the Android market. Their refusal to provide documentation force the devices to get stuck on older releases such as 2.2 Froyo causing fragmentation. Just look at the Tegra 2 Harmony boards that are still only supported up to 2.2 through official channels even only months after their release. The official response from NVIDIA always seemed to be to get a newer by a couple months device with a Ventana board. Hobbyists have gotten most functionality to work all the way up to ICS through writing custom drivers and a lot of hard work. The work can and will be done by the community (saving NVIDIA time, work, and money) but they simply refuse to release important information such as the full VI/CSI interface. Their public TRM document the CSI interface but leave registers missing and doesn't even document all the CSI registers. Most times people request information from them through their forums or other channels the posts are DELETED or simply not answered. If they do not want to spend the money to support and update their product a couple months after release the community would be happy to do it for them with proper documentation. If you want to see and feel the pain of buying a NVIDIA product just look a some of the Notion Ink, GTablet, and other products that unfortunately thought including their board was a good idea.

    1. Re:Android by Anonymous Coward · · Score: 0

      The work can and will be done by the community (saving NVIDIA time, work, and money) but they simply refuse to release important information such as the full VI/CSI interface. Their public TRM document the CSI interface but leave registers missing and doesn't even document all the CSI registers.

      Posting Anon. Inside nvidia they don't really have any better documents for these registers. The hw guy that designed it basically wrote crap documentation these and that part of the nvidia driver that finally got it to work is an opaque mess and most changes internally had to be done by reverse engineering the working original driver... So buck up and join the reverse engineering effort. The working code is already in the android GIT archive (un obfuscated and open source) , there's nothing else that nvidia has to document it ;^)

  38. Re:"nouveau" is the blank-screen-driver by h4rr4r · · Score: 1

    Does that have any tearing?
    I have a GTX460 and am getting terrible tearing. I never had that issue with my old 7600GT.

  39. Re:"nouveau" is the blank-screen-driver by armanox · · Score: 1

    I haven't noticed any - but I'm generally not doing 3D stuff these days, and I'm not using Compiz (running MATE on Fedora 16, kernels 3.1 - 3.5rc have been fine). Is it constant or only under certain conditions?

    --
    I'm starting to think GNU is the problem with "GNU/Linux" these days.
  40. re: Why risk tipping their hat? by King_TJ · · Score: 2

    I don't know.... Right now, I think both AMD and nVidia have pretty good handles on how to produce graphics boards consumers think are worthwhile. They could start copying every single innovation that each other formerly had as "company secrets", to the point where both brands of board performed absolutely identically in benchmark tests -- and STILL, I suspect they'd both sell about the same number of boards as before.

    The real problem is, the marketplace has consolidated so much, you really only have these two companies as your choices for a 3D accelerated video chipset. Intel is trying to work their way in as a 3rd. player with accelerated, yet integrated, graphics chipsets -- but truthfully? I doubt they'll seriously chase after the high-performance graphics market in any serious way. For them, it's more lucrative to offer decent/usable levels of performance for the typical user and compete on having a lower price.

    Once upon a time, we had choices from companies like Matrox, Diamond, Hercules, Trident .... Not so much anymore.

  41. The better question - and solution by rraylion · · Score: 3, Interesting

    Everyone is upset NVIDIA doesn't give away all it's secrets. There hard earned property. that they built. Why not go the more open route and create one set of driver standards for video cards. VESA -- everyone knows the standard and its up to the manufacturer to optimize their side and on the consumer side you get what you asked for.

    This is actually a battle over special features -- my hardware can do some pretty sweet stuff, but I wanna control how you can access that stuff. the concept from above still applies, but there is no incentive for the hardware designer to devote resources (people and the salaries they have to pay those people) to help you bang out that new framework.

    I love open source, but it's built on peoples free time. Companies have to justify how something makes them money. Saying this will build product sales in a 10% market share is not enough. So come halfway and get the framework done and they will optimize their side. This is the best of both world I get a product and they stay behind their doors, but it's a blackbox I can use.

    1. Re:The better question - and solution by Ash-Fox · · Score: 1

      I love open source, but it's built on peoples free time.

      I await your citations disproving the various people paid to work on Linux were actually not paid and doing it just on their free time (yes, I'm aware there are those that do, do it in their free time, but I'm not disputing those).

      --
      Change is certain; progress is not obligatory.
    2. Re:The better question - and solution by Anonymous Coward · · Score: 0

      If you start buying freedom friendly hardware from companies that are making an impact this won't be an issue forever. It's our willingness to accept the non-free bits that is HARMING us. Sadly- most don't care. They just go buy a Mac and end up with shitty support. Yes- Apple's hardware sucks. They are proprietary and won't support you beyond a specified period. After that- all is fucked.

    3. Re:The better question - and solution by Anonymous Coward · · Score: 0

      The entire lower level of the OS X operating system is open-source...

    4. Re:The better question - and solution by Anonymous Coward · · Score: 0

      " NVIDIA doesn't give away all it's secrets"

      Do we really have to explain that opening up interface information so people can write their own Drivers is not giving away all their super secret design information?

      Yep. We do. Sigh.

  42. MBA's and idiots without cloths. by bored · · Score: 4, Interesting

    They all think there is secret sauce in their product with some genuine trade secret level information.

    In reality, having seen the secret sauce from a 3rd party perspective a few times, it turns out that often times the competitor is doing it basically the same way. So the only people being hurt by not publishing the hardware specifications (as was the normal state of things until the late 1990's) are the hackers and budding engineers trying to make the product better in some way.

    In the case of graphics companies, it seems they are somewhat justified for not releasing the source to the proprietary drivers, as that is such a huge part of their performance work (aka sometimes the games aren't faster because the hardware is faster, they are faster because the driver is using a better algorithm, or has more micro optimization). Not releasing the hardware specs is just silly, because at this point, a big portion of the graphics chips are understood well enough that releasing information on mode setting or shader setup is more like filling in the details, rather than giving away any secrets.

    The Optimus stuff is a prime example, its basically just going to be information on enabling/disabling parts of the chip or setting power envelops for certain functions. The real secret sauce is how to use that information. I have a similar issue with my little NAS box at home based on a guru plug. Marvell claims to be open source friendly, and gives away specifications that look good until you actually try to do something like power down an unused sata port. Then your SOL without the NDA, because knowing the register which controls the power gating is some kind of secret....

    Mostly, what is being hidden is the fact that the emperor has no cloths.

  43. Re:"nouveau" is the blank-screen-driver by Anonymous Coward · · Score: 0

    Well, here's my INcompatibility list:
    Quadro FX 4500
    Quadro FX 4600
    Quadro FX 4800
    Quadro FX 5800
    GeForce 450 GTS
    GeForce GTX 480
    GeForce 9800 GT (Yes, despite being in your list, every time I've tried this machine with nouveau, it's been a blank screen.)

    These are only the cards in the current machines I manage - there were several older ones that have been retired (and the Quadro FX 4500 machines are close to being retired as well) - The nouveau driver has not worked on any of them. The closest to a response is from the Quadro FX 4500, which gets a flickering blue rectangle on the screen. Everything else just shows a blank screen that then goes into power saving mode due to no signal. Swapping out to the bare bones vesa driver gives me working video, and downloading and installing the NVidia drivers gets full working video running. Most of these machines have been through Fedora, though the GTX 480 and the FX 4500s have been set up with Ubuntu and Debian as well, with exactly the same effectiveness from nouveau (ie: none). Every time I'm due for another install cycle I get told "Oh, you should try the nouveau driver - they've really improved it since last time!", and every time it continues to produce blank screens. (Better hardware acceleration for the blankness? Not sure what the improvement is here...)

  44. Key quote... by Bert64 · · Score: 1

    NVIDIA assures us that 'at the end of the day, providing a consistent GPU experience across multiple platforms

    What's good enough for windows users, isn't good enough for linux users...

    Linux users enjoy a host of benefits which windows users lack, and the nvidia binary drivers remove or restrict some of those.

    Access to source code, to learn from or build upon.
    Ability to debug problems with the os.
    Ability to use a completely modular system, even so far as using a different type of processor architecture.
    Ability to advance the os without being saddled with backwards compatibility baggage that plagues other systems (hence no driver abi as it would soon become limiting and start holding things back, even ms dropped their previous driver abi with vista).
    Ability to use old hardware, long after the hardware manufacturer has given up supporting it.
    A GUI system which is optional.

    Many people choose to use linux specifically because it offers things that windows or macos don't, we don't want a "consistent" experience.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  45. Re:"nouveau" is the blank-screen-driver by h4rr4r · · Score: 1

    Pretty much constant. I am not using Compiz either, XFCE on ubuntu. Supposedly I can almost fix it if I turn off compositing, then enable vsync and page flipping in nvidia-settings. Flash videos will still tear.

    I am so glad that only one of my computers has an Nvidia card. I used to swear by them, but these days even fairly modern games will run on intel GPUs and I think I might just live with less shiny and convert over to them 100%.

  46. effective communication and public perception. by NemoinSpace · · Score: 0

    It seems Linus' 2 word complaint was responded to in kind, albeit, in a more professional manner.
    Far be it from me to dictate someone else's communication skills.
    I'll just take it under advisement before I recommend to my clients that they enter into business relationships with people that throw public temper tantrums.
    The year of the Linux desktop has been postponed while we re-evaluate our options. We're talking to Bill right now to confirm our market share figures, and will get back to you shortly.
    BTW: if you don't like NVIDIA, feel FREE not to use them.

    1. Re:effective communication and public perception. by Anonymous Coward · · Score: 0

      Ballmer. Chair. Cancer. Need I go on?

  47. True, not my primary point, but still true. by Anonymous Coward · · Score: 1

    Linus Torvalds can criticize all he wants. It doesn't make him right, or certainly doesn't enable him to see more clearly.

    1. Re:True, not my primary point, but still true. by rtfa-troll · · Score: 1

      Linus Torvalds can criticize all he wants. It doesn't make him right, or certainly doesn't enable him to see more clearly.

      Linus Torvalds is right about whether Linus Torvalds feels put out by Nvidia by definition. Nvidia has to deal with that by making Linus happy. As long as they don't I, as a person who has influence over the purchase of lots of Linux hardware, will avoid their products. That doesn't mean I will rule them out where there is no alternative, but it does mean I'm writing working on an AMD drivein monitor. It does mean that wherever there is a choice I will avoid them. This does mean that I, personally cost them hundreds to thousands of euros yearly. There are tens of thousands of people who think like me and thousands of those who cost them real money/

      Simply put, they want to put some corporate people towards making Linus happy. I don't care why he's unhappy; What I care about is that it makes him less likely to be well disposed to looking after that hardware in future. That's a real financial risk from my point of view and I'd like to minimize that risk. If Nvidia makes him unhappy and others don't I'm going to prefer them. Allowing this to happen is straight incompetence and nothing more.

      --
      =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
    2. Re:True, not my primary point, but still true. by Anonymous Coward · · Score: 0

      Linus Torvalds can criticize all he wants.

      Correct.

      It doesn't make him right, or certainly doesn't enable him to see more clearly.

      It doesn't have to. In this case, as well as in many other (but not all) cases, he is right and does see more clearly.

  48. Re: Why risk tipping their hat? by Nadaka · · Score: 1

    Let me know when intel starts offering usable levels of performance. They just don't have it yet if you play anything more advanced than solitaire.

  49. Intel Phi will DEEPLY hurt nVidia's stance by Anonymous Coward · · Score: 1

    I am not sure this marketing spin will save nVidia's beacon on the HPC side, where they're about to get into an axe fight with Intel.

    Intel Phi is not even really released, and already works with open drivers. Open high quality drivers are extremely important for long term support and long term flexibility, which are key decision points when acquiring HPC clusters. Phi already does much better than current nVidia and ATI offerings in both hardware *and* software.

    I predict nVidia will see its share of the HPC market go down to the low single digits in about two years after Phi is in the market, and they'll be forced to release high quality open drivers for CUDA usage to reduce the damage.

  50. Re: Why risk tipping their hat? by Kjella · · Score: 1

    Intel is trying to work their way in as a 3rd. player with accelerated, yet integrated, graphics chipsets -- but truthfully? I doubt they'll seriously chase after the high-performance graphics market in any serious way. For them, it's more lucrative to offer decent/usable levels of performance for the typical user and compete on having a lower price.

    I think Intel would like to jump as high up that tree as possible, but it's not as easy as just saying it. You can bet they had bigger plans for Larrabee and whatnot than what became reality. Anyway, for at least another 1.5-2.5 years all games will continue to be designed to run well on 2005-2006 era hardware in the Xbox360/PS3 - the number of PC exclusives is getting slimmer and slimmer. The big question is when the 720/PS4 rolls around, if they set a new "low bar" for gaming performance but until then the more Intel can shrink the discrete graphics market the better for Intel.

    --
    Live today, because you never know what tomorrow brings
  51. 3D perf vs. Linux integration by Anonymous Coward · · Score: 1

    Their 3D drivers may deliver superior performance (than nouveau). But their driver is a bad linux driver. It doesn't embrace linux specific technologies enough. Last time I checked it didn't play well with RANDR. Multi-Monitor and Ext Video support was horrible. KMS? Nope. 57 MB (!!!) package for a freaking driver? Check. Breaks suspend/resume? Course.

    If that's what they call committment, then, yeah, fuck you nVidia.

    1. Re:3D perf vs. Linux integration by Anonymous Coward · · Score: 0

      As a comparison: nouveau UMS driver is some 140 KB, the KMS code is 2.4 MB.

    2. Re:3D perf vs. Linux integration by diego.viola · · Score: 1

      That's exactly why I stopped using the binary blob, the binary blob is just a Windows port of the driver to Linux, and it sucks badly.

      I use nouveau now which is IMHO a lot better and embraces Linux a lot better, KMS, Wayland, XRandR from the beginning, and so on. It might not have the performance of the blob yet but I'm sure that will come with time. Performance will only get better from here if we all help.

    3. Re:3D perf vs. Linux integration by diego.viola · · Score: 1

      Oh I forgot: Fuck you nvidia.

  52. Re: Why risk tipping their hat? by drinkypoo · · Score: 1

    Let me know when intel starts offering usable levels of performance. They just don't have it yet if you play anything more advanced than solitaire.

    Hyperbole, much? That is so not true. It is (just barely) adequate to play that pinball game that comes with Windows...

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  53. test by Anonymous Coward · · Score: 0

    test

  54. Both Sides are Wrong by Plekto · · Score: 3, Interesting

    First off, Nvidia are buttheads. They are. But they also have a right to make money. Apple, EA games, Sony, Intel, and on an on - they all operate this way, as does 99% of business. Where Nvidia is wrong is, well, where can I go out and pay $5 or $10 for a driver from them that works? You see, part of it is that the companies say that they offer a proprietary driver but I can't actually go out and BUY it from them or obtain it from them.

    But this brings up the other side of the dirty coin, as it were. That the Linux (in particular) community seems to have a major issue with paying for anything. I have zero issue with paying small fees. I do it all the time. I pay for my sandwich at lunch, my gas in my car, and well, pretty much everything in life. I just want a solution and to move on to the dozen other things that that I have to do during my day. So there's this great divide. They often don't even deal with issues or fix things at all, because it requires paying "the man" or using their code. ie - if it's not free and 100% open-source, we won't touch it at all.

    It's just as bad as Windows. They have effectively decided that you're SOL and stuck with their vision of 100% free or it's impossible to obtain view of their OS (which while open-source, is controlled on most Distros by a group of whingey, anal buttheads that might as well be CEOs at a typical software company, since they control the project with an iron fist) And this filters down to the forums and "help" groups that are as useful as a wet rag most of the time. Yes, the people mean well, but it's always "just install this". Without any explanation or documentation. Instead of mentioning the exact codecs you need to buy, they just will say "there is no package for that". No link - it's this attitude that if it's not 100% free, we don't even mention it or link to it.

    This idiocy is most apparent with "projects" like Wine. There has been a long-standing mouse driver issue that never gets discussed, fixed, or worked on. Because the code to make it work, is proprietary and there is no work-around (requires paying Microsoft a small fee, and their code is the only way to make it work properly). Cedega had a version of the driver that worked. Cedega went out of business, and as an end-user, stuff just stopped working a few months ago. The mouse driver(among other things like sound drivers and so on) and is effectively locked away as it's Cedega's proprietary (and legally protected) code. Wine won't release it.(yes, these are the same people) The official response over at Wine is "there is no fix". There is an actual fix, but they refuse to release it or make it available for a small fee.

    They whine about everything having to be open-source to the point of acting like it's a holy war, and yet when there's money involved, the same people don't act any different than Nvidia.

    Me, I just want to pay my fee and get on with my life.

    1. Re:Both Sides are Wrong by ledow · · Score: 1

      Because combining LGPL code and proprietary code is a dubious legal area, nothing to do with idealism, and would have required that code to ship in a DLL or shared object that was separate from Wine and only loaded by it. That would mean creating an API that ANY "mouse function" DLL could be replaced by it (kinda a condition of the LGPL, in fact), which means you've got to create, manage and maintain that API pretty much forever (wouldn't you be pissed if the next version of Wine broke that interface after you paid for that module?). And the very act of creating that API fixes the problem forever, for everyone, with just a few more lines of code (and still doesn't circumvent things like patent laws in some countries because ANYTHING that plugs into that module might be considered within the scope of the patent and, thus, the code itself to support that might be subject to patent infringement!)

      It's not that there's some secret coven determined to make things free. It's that if you want to manage a free-alternative to Windows API calls as a project, you keep it free. You don't then go and sell parts of it off because then you could have just created a "Windows-clone" product yourslef and started closed-source from the beginning.

      Cedega's existence proves that ANYONE could have done this. They did. They went out of business because they couldn't make profit doing it. TransGaming do similar things. They didn't do badly, but they still aren't any more popular than Wine is. I know, I'm a Crossover subscriber of old. I can't remember the last time I loaded it up in preference to Wine. They had to GIVE the software away for a day in the end.

      I don't know what this "mouse issue" is that you're so adamant about, nor why it ABSOLUTELY REQUIRES a closed-source module. The only reason to do that is presumably patents. Paying patent licenses for functionality is not what open-source is about - the point is to avoid black-boxes and unknown code doing magical things, free or not.

      And by the same token we could have just "bought" a DIB engine, and a window themer, and a Securom layer, and every single bit of Wine. And we'd have ended up with Windows, basically.

      Even Windows isn't immune to this - did you own valid MPEG2 codecs for Windows XP? Only if you bought something else from a company other than Microsoft because, by default, XP couldn't play DVD's because of software licensing for codecs! Windows 8 is supposed to have the same restriction, according to a The Register article I read a few months back.

      It's not a question of "You can't do it". It's a question of "Why should we support that? How much does it cost to support that API? What if we need to change something in a year's time? What are the licensing and other legal - e.g. patent - implications? Who's going to manage that closed source software for us? How do we verify that module is legal for our users to use? Can anyone even sell that software in some jurisdictions at all?..."

      There are a billion and one problems. And if you want to run Windows programs and use that particular functionality, you still have options outside of Wine trunk (hell, use Windows!). So use them. But Wine trunk is there to be a pure source of only code that is licensed consistently and can be distributed anywhere. It's there to make an alternative to Windows that DOES NOT NEED black boxes and mysterious payments to third-parties for normal functionality.

      It's like complaining that the people writing LibreOffice don't just use closed-source Office plugin filters. You've missed the point. Office software are ten-a-penny. Nobody buys them because if you're using those sorts of plugins, you might as well just have bought Microsoft Office. The point is that, this particular software project, we know what every line of code it executes is and can fix problems in all those parts whenever we want without having to worry about 20+ year old compatibility layers and licensing issues.

      If you want to pay the fee and get on w

    2. Re:Both Sides are Wrong by Nimey · · Score: 1

      First off, Nvidia are buttheads. They are. But they also have a right to make money.

      Has anyone ever said they don't?

      But this brings up the other side of the dirty coin, as it were. That the Linux (in particular) community seems to have a major issue with paying for anything.

      That'd be why pretty much every Humble Indie Bundle has gotten much higher per-capita payments from Linux users, then?

      Get your head out of your ass.

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    3. Re:Both Sides are Wrong by Plekto · · Score: 1

      The issue is that, like I said, both sides are just as awful about it. There is little middle-ground. In Windows case with the DVDs, we all bought software to play DVDs if we needed to do so (mine came with my video card - crappy software that it was). What bothers me (the mouse issue is just a tiny example, and is not something that requires support, as it's 20+year old patents/code/etc we're talking about 3-4K of code here that dates back to Windows 3.1) is the unwillingness of both sides to meet in the middle.

      I pay for codecs and drivers when they are available (sometimes, there IS a free version that works, usually it's just crap though). It's a cheap amount of money, really. But you have fools like Torvalds on one side saying "give it to us for free!" and the other side saying "we're releasing nothing". The "pay to use it" option is rarely available. Nvidia says they do work with Linux devices. Well, show us where we as the end-user can buy the driver for Linux for $10.

      I just want my machine to work. Not to get stuck in the middle of some holy war about free for all eternity and through all alternate universes versus never going to give up my rights, even when the sun has burned itself out. It's either 100% or 0% and nothing in the middle.

      What we need is a more same approach to all of this. I'd gladly pay for a copy of Linux with actual drivers and codecs and all of the rest that worked. This idea of "we can't let anything commercial pollute the sanctity of our distro's freedom" has to stop. Especially when the same group of hypocrites is often running for-profit versions or code on the side. If it were a group of guys living a bohemian lifestyle who were coding something in their free time, I could kind of understand, but when a company is grinding out a free and a pay-to-use version and then starts preaching to me that they can't offer me the drivers even if I wanted to pay for them, it gripes me.

      I hate Windows, but honestly, I hate Linux just about as much. One puts me in a straight-jacket and the other leaves in on a raft in the middle of the ocean.

    4. Re:Both Sides are Wrong by Plekto · · Score: 1

      You seem to think that I want to pay nothing, like the rest of them. I'm willing to pay money. I just want my machine to work and have a little freedom on the side. Nvidia's refusal to release their drivers even at a price is inane. But so is the insistence by the other side that everything in Linux be free even if it means you're stuck with broken programs and a horrible experience.

      With the issue of a mouse driver, it's doubly crazy. Every mouse has a driver on a floppy or CD that comes with it. I've bought enough mice over the years from Logitech to pay for that 3-4K worth of code ten times over. If your machine has a mouse connected to it, you already have bought and paid for the mouse driver. Just, the code isn't integrated into Linux. I suppose you could pull the code out, insert it, and re-compile everything, but that's just crazy. The same goes with a sound card. You bought the sound card. It came with a sound driver. But because of the holy war that's going on right now, you as the end user are stuck.

    5. Re:Both Sides are Wrong by Nimey · · Score: 1

      You seem to think that I want to pay nothing, like the rest of them.

      I don't know how you got /that/ out of what I said. I might be willing to pay $5 for good video drivers myself, but I'll let someone else test and make sure it's worth the money first.

      As to mice, who needs a mouse driver? Just use the default HID driver and find a program that will let you map the extra buttons to events.

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    6. Re:Both Sides are Wrong by Anonymous Coward · · Score: 0

      >First off, Nvidia are buttheads. They are. But they also have a right to make money.

      They do make money, or do you steal the NVidia graphics adapter from the store?

      >part of it is that the companies say that they offer a proprietary driver but I can't actually go out and BUY it from them or obtain it from them.

      You can download it from their homepage... it's just that it probably won't work (or at least be flaky) because they don't work together with the other kernel people. If that was a company and one employee wouldn't talk to another employee even though they should, what would you call that?

      >Instead of mentioning the exact codecs you need to buy, they just will say "there is no package for that".

      While you are free to throw money out as you please, EU law made VERY sure that file formats are NOT protected under copyright or patents.

      >No link - it's this attitude that if [the file format]'s not 100% free, we don't even mention it or link to it.

      Yeah, because while it would not be against the law, it would be definitely something weird, kinda like those companies that are selling bottled air or bottled water. Also, you never quite get the bad taste out of your mouth that they'll bribe some politicians somewhen and force everyone to pay retroactively. So like bottled water with lead in it or something else having bad effects in the long run.

      >The mouse driver(among other things like sound drivers and so on) and is effectively locked away as it's Cedega's proprietary (and legally protected) code. Wine won't release it.(yes, these are the same people) The official response over at Wine is "there is no fix". There is an actual fix, but they refuse to release it or make it available for a small fee.

      They can't do it if it's protected by copyright and they are not the ones holding it right now. It's called respect for the clients (also, it's the law).

      >Me, I just want to pay my fee and get on with my life.

      Well, have fun drowning in a thousand $1 fees for every little thing just to get your computer to work (note: an operating system in itself is something so banal and useless it's not even funny). You would pay for a mouse driver? I think I have some hardware to sell you. It's fine if you then have to pay again for the drivers you need to to make them work, right? (the drivers will only work until you update anything else, btw)

    7. Re:Both Sides are Wrong by Anonymous Coward · · Score: 0

      I pay for my sandwich at lunch

      did you also pay for the secret information required to eat the sandwich?

    8. Re:Both Sides are Wrong by gun26 · · Score: 1

      Cedega was _not_ done by the same people who contribute to Wine. They forked their code from Wine when Wine was under a more liberal license that didn't require contributing your code back. Therefore their proprietary mouse driver fix died with them. The commercial outfit that DOES contribute - and contribute a great deal - to Wine is Codeweavers, who sell their commercial version of wine as various versions of CrossOver. Generally, bleeding edge code goes into Wine first and appears in a subsequent CrossOver if it stands the test of time. I don't think you're being at all fair in characterizing Linux people as being unwilling to pay for stuff. I think every Humble Bundle with Linux support has seen Linux users pay appreciably more than Windows and Mac users. I think our problem with Nvidia is one of educating the company's management to see the benefits of going open source. Thus far we've failed. Linus's "outburst" might get their attention, although the Nvidia response shows that they still don't get it. We have to keep trying. We'll persuade them yet.

    9. Re:Both Sides are Wrong by Plekto · · Score: 1

      It does seem odd that Nvidia is just giving away customers to ATI. It's not like ATI makes junk, either. If we were talking cars, it would be like Mercedes and BMW. Mercedes makes slightly better cars, but their total dropping of manuals in the U.S. in the last year or two has basically just handed over a small but important chunk of the market to BMW.

      The easiest way to deliver the drivers would be to manually ship them out on CDs for $5 or $10. That way, any version online would be "not approved" and easier to deal with legally.

    10. Re:Both Sides are Wrong by Anonymous Coward · · Score: 0

      > They whine about everything having to be open-source to the point
      > of acting like it's a holy war,

      in other words people are miffed that companies are introducing artificial scarcity where there would otherwise be infinite supply

      gee wiz, someow I'm not at all suprised by that reaction.

  55. Re: Why risk tipping their hat? by tlhIngan · · Score: 1

    Intel is trying to work their way in as a 3rd. player with accelerated, yet integrated, graphics chipsets -- but truthfully? I doubt they'll seriously chase after the high-performance graphics market in any serious way. For them, it's more lucrative to offer decent/usable levels of performance for the typical user and compete on having a lower price.

    I think Intel would like to jump as high up that tree as possible, but it's not as easy as just saying it. You can bet they had bigger plans for Larrabee and whatnot than what became reality. Anyway, for at least another 1.5-2.5 years all games will continue to be designed to run well on 2005-2006 era hardware in the Xbox360/PS3 - the number of PC exclusives is getting slimmer and slimmer. The big question is when the 720/PS4 rolls around, if they set a new "low bar" for gaming performance but until then the more Intel can shrink the discrete graphics market the better for Intel.

    Intel doesn't need to jump up as high - they already are the primary graphics in the vast majority of computers sold (heck, Apple might actually one of the few keeping Intel-only graphics down by shipping large quantities of computers with discrete GPUs - though,they also do ship plenty of Intel-graphics computers as well).

    For Intel to go after the remaining percentage of people, it's going to require a much larger investment in resources just to get a little bit more marketshare.

    Intel just needs to maintain marketshare - realizing fewer people play PC games, they concentrate on video so as long as they can do Blu-ray playback and handle Aero with some decency, the vast majority of consumer needs will be satisfied. Consumers looking for a gaming machine would pick up a discrete ATi/nVidia card anyhow.

  56. Problem in collaboration, not in source licensing by DrYak · · Score: 1

    but not everybody has the opinion that everything linux related must be open source

    That's not the main concern about Nvidia. The problem is this part :

    Basically the company replied they're committed to Linux using their proprietary driver that is largely common across platforms

    When translating from PR-speak to geek-english : basically, they aren't writing specific Linux drivers, they are just recompiling the Windows, while throwing a crappy adaptation layer in the middle and completely ignoring any best practice, standard or newer technology developed for Linux. They are just doing things their own way and not playing nicely with the rest of the kernel, even if this behaviour is problematic. Even if kernel developers step in and try to collaborate. Nvidia prefers doing their own thing alone in their own way, until said way aren't able to work at all, in which case they have to be brought to the new standard while kicking and screaming.

    Their driver fail to follow newer standarts like Kernel Mode Setting (KMS) (and thus can barf badly when switch consoles on some hardware configuration), or have finally taken up some other at glaciation-speed (XRandr, and that's after the latest XRandr standard was made so on purpose to make Nvidia's job easier).
    Instead of playing nice with all the facilities in the kernel (for memory management, context switching and the like) they just use their own incomptible in-house implementation instead, which don't play nicely with the rest. Same also for their user space which doesn't play nicely with other drivers for other hardware (Intel's driver are written to take advantage of the Mesa (older) and Gallium3D (newer) stacks - but Nvidia's use their own solution which doesn't play along). As a result of this, there are several technologies which aren't supported under Linux, like Optimus (doesn't play nicely with the various facilities to switch GPU on and off, doesn't play nicely with the Intel drivers for the onboard GPU, doesn't play nicely with the facilities to redirect output from the discrete GPU through the onboard GPU to the ouput connected to the onboard only). Sometime this even results in complete failure to display anything (not just the power adjustment not working. But no working display at all).

    This is while some of these facilities are even used by several other drivers, enabling even crazier use-cases: for example output 3D on an external USB screen, using the computer's internal GPU card for acceleration (as long as said card has a moden driver following said standard).

    Even AMD/ATI is putting in more efforts to follow the Linux trends even though they also try to recycle as much work from their Windows Catalyst as possible (although they have a little bit lesser quality proprietary drivers).

    Many developers complain with the "not playing nicely" behaviour of Nvidia regarding their drivers. Linus just happen to be less polite and more vocal about it, probably counting on the publicity stunt to attract attention on a problem which is hindering the kernel developer community.

    This is far from "you're forced to open the source to your drivers". This is more "please stop ignoring what everyone else is doing in the kernel". Nvidia is simply refusing to collaborate with kernel developers.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  57. Re:"nouveau" is the blank-screen-driver by David+Chappell · · Score: 1

    Seriously, I don't see any point in anyone supporting that piece of crap. Every NVidia card I've ever tried it on has resulted in either a blank screen, or a flickering blue screen - this goes from older NVidia cards (which should be supported by now) right up to the latest new $2000+ cards - it works on nothing. Why do distributions even bundle it? All it does is make it difficult for people with NVidia cards to get their distro up and running, because first they have to deliberately disable the nouveau driver, force the system to use bare bones vesa, add the real driver manually, and then re-configure the system to use it. Not exactly "new user friendly" there.

    Seriously distro maintainers - nouveau is a chunk of crap, dump it and you'll be making your distro easier to use for a lot of people. Even if you have NVidia cards all get sent to the low-res vesa driver by default, at least they'll be able to see things on their screens.

    My experience is different. I just ran some tests on Ubuntu 12.04. Both Nouveau and Nvidia's own driver worked, the difference was thet Nouveau worked without screen glitches during video mode switches. There was no noticable difference when running Bzflag at max quality.

  58. Re: Why risk tipping their hat? by mister_playboy · · Score: 1

    Windows 2000 was the last MS operating system to include that game.

    You can copy over the files and have it run just fine on Win7, however. :)

    --
    Do what thou wilt shall be the whole of the Law ::: Love is the law, love under will
  59. Re:I Have Already Purchased The Card!!! by Gavagai80 · · Score: 2

    Yeah, it's clearly the aliens teaming up with the Illuminati to suppress linux graphics drivers.

    --
    This space intentionally left blank
  60. Linus is just plain wrong by THE_WELL_HUNG_OYSTER · · Score: 1

    Saying "at the end of the day, ..." makes everything better to me. It is corporate-speak that gives me the warm-and-fuzzies.

  61. There are facility for that. by DrYak · · Score: 2

    Did it occur to anyone that optimus (as written) won't work on Linux.

    Well to be more precise, the way Nvidia does optimus in Windows won't work on Linux, and thus can't work with their strategy of "rebuild the same driver as on Windows and throw some shitty wrapper module in between".

    Basically you have to have hardware carveout memory shared between the two graphics units (nvidia and intel integrated) and that memory model doesn't mesh with the linux driver memory model

    Indeed. The linux kernel has a way to do such routing from card to card. It works. Even to the point that it's possible to do crazy stuff like ouput 3D on an external USB LCD display pannel, which was accelerated by the GPU card inside the computer (as long as the GPU card has an opensource drivers). There are even some prelimilinary support in GIT repositories to get the Nouveau drivers (done only by reverse engineering, without Nvidia help) to do exactly that: route the Nvidia's ouput through the onboard Intel GPU.
    But no, Nvidia doesn't play nicely and collaborate with this technologies, they prefere to do their things their way even if it doesn't work for optimus.

    (and maybe even the open source intel integrated driver).

    Indeed, on Linux Intel officially use an opensource drivers which was written by Thungsten graphics and which runs on Mesa (for older hardware) or Gallium3D (for newer hardware). Nvidia doesn't want to spend the effort playing nicely with those.

    Also you have to (virually) unplug the graphics which means state-save and state restore which isn't just limited to the graphics, but the PCIe hot-plug driver as well.

    Tha'ts what "switheroo" is for and it works (although that a restart of the X server might be needed for now, Works on Wayland too). the PCIe hot-pluging has been present since long time in the Linux kernel (in fact, Linux tend to have more support for crazy attempts at hotplugin. Including bat shit crazy stuff like hot-plugin not electrically-hotpluggable interfaces like IDE, or even replacing live memory modules. Of course there's a risk of crashing a controller or frying electronics, but from the software side the abilities are here).

    No doubt nvidia got these working on windows with great effort, but there's no such infrastructure in Linux to fit their driver into, and there's little incentive for nvidia to do this work {...} So if the linux community would just provide the infrastructure for Optimus for the nvidia driver,

    There are the necessary infrastructures. They are currently used with more or less success for opensource drivers, including for Nouveau. It's just that Nvidia prefers doing things their way, which is among other using their own in-house facilities instead of playing along with what everybody else is doing and refuses to collaborate with kernel developers in order to find a solution to have support for what interface they need between the in-kernel facilities and their own driver.

    This is really bad, because for some optimus configuration, this can mean no display AT ALL. (At least not without switching to Nouveau once the specifics get reverse engineered).

    you might just see that feature pop-up in their closed source driver.

    No, you won't. Because their official position is:

    Basically the company replied they're committed to Linux using their proprietary driver that is largely common across platforms

    Translating from PR-Speak to geek-english: they reuse their windows code as-is and only slap a crappy adaptor module in between. They prefere doing things their way, because it's easier for them, and don't want to play nicely and collaborate with kernel development to use the facilities that everyone else is using.

    They might start to offer optimus, if there a too big buyer pressure on them, in which case, they'll jus

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
    1. Re:There are facility for that. by Yvanhoe · · Score: 1

      Mod this guy up to heaven. He knows the technical details.

      I'll steal this post to ask from a knowledgeable person : As someone who has been bitten by the optimus thing, who has now a poor ATI driver, are intel graphics any good ? I heard they really pimped up their acceleration abilities these years. Are the open source drivers really good under linux ?

      --
      The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
  62. No ECC by DrYak · · Score: 1

    ECC memory

    There is no actual ECC memory on the card. It's the same memory except that when the drivers are in Quadro mode, they reserve a part of the memory to hold checksum data. The end result is grossly the same (resistance against unreadable bits)

    Appart from the separate 3D Stereo connector that some Quadro card have, there is no difference between Quadro and GeForce cards.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  63. Example: 3D stereo by DrYak · · Score: 1

    As an exemple: take to cards.
    - a GeForce
    - and a Quadro with exactly the same hardware.

    Under Linux, only the Quadro cards can do 3D stereo, because the API to do it under linux is through standard "stereo quad buffering" under OpenGL, and Nvidia has decided that their drivers will only enable setereo quad buffering with cards which report a "quadro" PCI ID.

    Even if the hardware present on both cards is fully able to do 3D stereo, as proven by the Windows DirectX 3D driver able to run DX3D games in stereo 3D also with the GeForce card (well, as long as you get the exact perfect combination of Nvidia drivers and stereo drivers).

    Thus if you need 3D stereo for anything beside 3D gaming (like for exemple, molecular modelling), you need to buy the more expensive Quadro card, because modelling software use the standard "stereo quad buffering" API in OpenGL, and not the proprietary Nvidia API in DirectX3D.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  64. nVidia is the only option on Linux by Chibi+Merrow · · Score: 2

    I'm going to third this opinion. I make my living writing and maintaining Linux-based 3D simulators for the FAA. We use only nVidia cards, and only the proprietary driver, as we just can't get the performance out of nouveau or ATI's joke of a driver.

    Hell, I remember at my last job when we got our first 8800GTX, and the Windows driver was completely borked (couldn't disable vsync, control FSAA, anything), but the six month old Linux driver we were using gave us 150fps on a dual-channel setup to drive the HMD, right out of the box without any tweaking. nVidia's on the right track, their universal Linux driver is pretty much always fast and rock-solid.

    That being said, I have a Radeon on my home PC (Windows box used for gaming), so I'm not using nVidia at work by choice. We don't have the luxury of choice.

    --
    Maxim: People cannot follow directions.
    Increases in truth directly with the length of time spent explaining them
  65. ATI by Anonymous Coward · · Score: 0

    Aside from how they are to work with and the proprietary driver, I have historically had much better success with NVIDIA under Linux than ATI (before AMD).

  66. Andriod by BrookHarty · · Score: 1

    You can never use a new release of android until the manufacture releases its updated version that includes updated drivers.

    This is the perfect example of the closed driver issue.

  67. Guess no one thought the Nvidia doesn't have to by bryan1945 · · Score: 1

    Do anything. They don't have to release specs or drivers for Linux at all. Of course it would be dumb of them to ignore that market space, but Tovalds needs to realize the entire world is not servicing his wang on his whim.

    --
    Vote monkeys into Congress. They are cheaper and more trustworthy.
  68. On Keeping Up with OpenGL by ratboy666 · · Score: 1

    "Let's see the open source keep up with the GL spec instead of holding the whole damn platform back in 2.0 land"

    Normally, I wouldn't bother responding, because there is little chance that you will see this response. However, the above quote is important.

    I will refer you to [Blythe2011] http://www.cs.cmu.edu/afs/cs/academic/class/15869-f11/www/lectures/blythe_compute.pdf

    for an interesting critique on current 3D work.

    And remember, the "radeon" driver supports R100 on up.

    --
    Just another "Cubible(sic) Joe" 2 17 3061
  69. Yesterday I was buying a video card by Alain+Williams · · Score: 1

    since my old one was over heating. I'm not a gamer, I don't need a great spec. My first criterion was: ''Not Nnidia''. Quite simply: I don't want a kernel that is tainted. There are plenty of other cards to choose from.

  70. There are good reasons not to release specs by Brannon · · Score: 1

    They are probably worried that releasing low-level specifications for external driver writers would create the following burdens:
        1. Answering inevitable questions related to those specs
        2. Pressure to not change driver-visible behavior across generations
        3. Dealing with the fallout from people using buggy drivers written by third parties--most of the anger will be directed at NVidia eventhough the real problem is that not everybody is qualified to write a tricky low-level driver.

    1. Re:There are good reasons not to release specs by David+Chappell · · Score: 1

      They are probably worried that releasing low-level specifications for external driver writers would create the following burdens:

          1. Answering inevitable questions related to those specs

          2. Pressure to not change driver-visible behavior across generations

          3. Dealing with the fallout from people using buggy drivers written by third parties--most of the anger will be directed at NVidia eventhough the real problem is that not everybody is qualified to write a tricky low-level driver.

      These sound like likely rationalizations. The answers are:

      1) Answering some questions (i.e., publishing a spec.) is better than answering none.

      2) Changing driver-visible behavior must make life difficult for their own developers. Avoiding it where possible is a good idea.

      3) They are themselves publishing buggy drivers right now.

  71. Re:"nouveau" is the blank-screen-driver by Anonymous Coward · · Score: 0

    Or just use the blob driver, which works fantastically. I really don't understand this whole concept of not using a working piece of software because it wasn't developed in a manner consistent with your religion.

  72. Posturing for DRM-compliance? by Anonymous Coward · · Score: 0

    Could they be going this route so that they can please Hollywood in the future? I admit I'm a little weak on knowledge about why they'd make a decision like this, but speculation is fun, and this notion fits the bill.

  73. Wrong group? by Anonymous Coward · · Score: 0

    Get real. Should I direct my ire at a group which gives me software with source, for me to study, modify or distribute at will, only subject to the small restriction that I give as I get? Or to the group not giving me the source?

    Sheesh.

    For me it's: "Meh. I won't buy NVIDIA. I won't recommend them"

  74. zero benefit in supporting Nouveau by Anonymous Coward · · Score: 0

    Why would nvidia support a hobbyist project that produces an consistently out dated and inferior driver?

    I guess it might be fun. but at the end of the day it sounds like they would just end up with unhappy customers trying to use the wrong driver. And nvidia would have to wrestle control away from open source arm chair architects trying to design DRI/DRM layers for hardware that they do not understand. Given that a vendor knows more about the future architecture of their own products than an open source enthusiast, I see no reason to solve this particular problem democratically through the open source community.

    Accept some tyranny and all will be well.

  75. Nouveau almost good enough anyway by DMJC · · Score: 1

    I've followed this topic for years and honestly, I don't think this is a problem anymore. Nouveau is making ridiculously fast progress on supporting modern cards and hardware features that I just don't see this as being a problem within 1-2 years. I think if people really want nvidia open source support they should just back the crap out of nouveau since they've almost got full support for all the cards anyway. I am much more interested in seeing nouveau complete 3d support across their cards rather than focus on peripheral things like Optimus. Considering that they don't have to implement OpenGL 4, and that that is where Gallium3d's devs are working I think the future of these drivers is looking pretty good.

    1. Re:Nouveau almost good enough anyway by diego.viola · · Score: 1

      I agree, nouveau is progressing really fast. One thing that we really need as nouveau progress is to get rid of the patent issues in Mesa, S3TC and solve those kind of things. We need to invalidate all software patents.

  76. the thing is my experience is their drivers suck by Anonymous Coward · · Score: 0

    All I can say is MY experience is their drivers have sucked. So much so that for my latest PC - I got an AMD Radeon Card instead. That has proven to be less hassle so far. To be honest - whilst I prefer Open Source... all i care about is it works well - and their drivers kept having little issues.... 3D mode wouldnt work or they wouldnt install right on ubuntu without extra fiddling etc etc...
      They were a nightmare on Linux Mint.
        And their decision means - issues are difficult to fix - SO THEY CHOOSE a path that makes things difficult for the community... and they poduce a crap product.
    Im sorry... I choose to use another product. Im not a gamer. I dont need the best graphics card. I just want it to work....

  77. Interesting by Anonymous Coward · · Score: 0

    Of course Nvidia would have to respond to Linus' comments and of course it would be pathetic (they don't have a lot to back them up). The fact is, Nvidia create various pieces of hardware and also provide closed-source drivers for some of that hardware and which is designed to hook into various versions of the Linux kernel. This can be great for some Linux users but is undeniably inferior to source code. Nvidia also don't even provide detailed specs for their hardware!

    For people that don't really care about FLOSS but are happy to use cheaper and more reliable software where it's available, Linux and Nvidia can both be recommended. For people that do care about FLOSS Nvidia is a waste of time.

  78. Avoid nVidia!!! Buy from ThinkPenguin.com by Anonymous Coward · · Score: 0

    The problem right now is that people are throwing money at this "great" nVidia hardware when the reality is very different. Intel's graphics chipsets are comparable to nVidia on the low end and more than capable of meeting 95% of the world's computer using populations needs. Including the "techy" crowd. The idea you can't have a "high end" system without nVidia (not to say it isn't difficult to go high end without also getting nVidia as a consumer though) isn't true.

    You can get "business class" laptops with as much as 16GB of ram, higher than 1280x768 screens, USB 3.0, and Intel HD graphics WITHOUT going nVidia or ATI. They are hard to find though. That said none of the current models are available without Microsoft Windows.

    ThinkPenguin.com's working on releasing some more impressive models specification wise without nVidia or ATI graphics chipsets. I's not an easy task though given the lack of demand. More people need to be purchasing with freedom in mind if things are going to change for the better. Free software needs the money (ThinkPenguin donates a significant portion of its profits to free software development efforts too) and the demand needs to go up for free software compatible hardware to become a reality. All ThinkPenguin hardware is free software friendly- not just "open source" friendly. The problem right now is there are minimum quantities necessary for products to be cost effective at manufacturing or supporting and right now the support ain't that great because GNU/Linux users aren't spending money on freedom. Without that demand from companies like ThinkPenguin the chipset vendors (Atheros, Intel, etc) don't have an incentive to release the complete source code for newer chipsets or provide the specifications that Linus and the free software community need to provide adequate support.

    Most mainstream manufacturers targeting Microsoft Windows/Apple expect people to want nVidia and ATI. These are known for being the "better" graphics chipsets. And in some respects it's better. Although it isn't better in all respects. ATI and nVidia are more power hungry. Intel's graphics are also better with video acceleration on GNU/Linux. There are other things Intel does better than nVidia and AMD.

    In any case it is possible to design a model with support for 16GB, USB 3.0, and 1600x900 / 1920x1080 screens which use Intel graphics. Celvo is one of the few companies which actually does the manufacturing for laptop computers, there are 4-5 companies that actually manufacturer laptops, and none of which typical consumers would be aware of this. Companies like Dell, Lenovo, HP, and even Apple generally don't manufacture anything. These companies are just branding systems made by others. ThinkPenguin is working with Clevo to put together a model with a higher resolution screen 1600x900 +, 16GB of ram, USB 3.0, and Intel HD. The model ThinkPenguin.com ships may end up being without 16GB of ram depending. If that happens there may be a 1280x768 screen, USB 3.0, and 16GB ram in addition to the other. ThinkPenguin works with the companies who actually do the manufacturing to get GNU/Linux users the right hardware.

    From what I've been told the availability of higher end models with Intel graphics chipsets will probably available in the September time frame. Until then you can still get laptops with some serious horsepower (i7, 8GB of ram, SSD, etc and of high quality).

    Another thing to note is that most companies shipping Linux laptops don't really care if the product works later on. Or they don't know enough to realise the systems they sell suck. They are merely branding laptops without actually doing ANY work at all to make them GNU/Linux or free software friendly. Even utilising the right wireless chipsets is too much work. Despite this being easy to do so it's all about marketing for them. Part of this is because many of them aren't building the systems themselves and aren't offering any real support. They simply have hired a third party to do it and pocket the profits. They aren't

  79. Linus was a bit hard by Anonymous Coward · · Score: 0

    I think Linus was being a bit hard on them. They have the best video drivers out of the video bunch, so i'm sure they want to keep some things in-house. But at the end of the day, any linux box i've ran with an nvidia card inside has worked very well and accelerated by using those drivers, I've never really had a problem getting stuff to work and they have a pretty useful config tool, even some multimonitor hacks so we can have a better experience. This is what I run at home and at work. I know linus wants everything in the kernel and free and open as do I, but seeing how they actively keep their own stuff up to date I don't see this as a really big issue.

  80. Until it's illegal to close specs on components by AbominousSalad · · Score: 1

    I'll just be thankful I can game under Linux at all.

    --
    Every trollism an AC posts is prefixed, in my mind, with "A. Coward whined, in a weak and cowardly voice:"
  81. I'll call them out by WOOFYGOOFY · · Score: 1

    just watch me...

    Kensington and Logitech for not supporting trackballs in *nix

    NVIDIA as per Linus's remarks

    Since for the most part, my computer - to me- is my screen and my input devices , I'd say there is basically a deliberate and con$scious effort to starve *nix of a decent user experience and that such concerted effort is probably not coincidental or driven even by market forces, seeing as the implied beneficiary of such a "starve the beast" approach is clearly micro$soft who has been caught, tried and convicted in a court of law of just exactly the tactic of wielding it monopoly power in order to effect "starve the competition from access to users":

    For those too young for the events to have been contemporary and in personal memory, the BBC tells it like it is:

    From Judge Jackson's Finds of Fact regarding micro$oft's coercive practices:

    http://news.bbc.co.uk/2/hi/in_depth/business/2000/microsoft/700702.stm

    . The OEM Channel

    With respect to OEMs, Microsoft's campaign proceeded on three fronts.

    First, Microsoft bound Internet Explorer to Windows with contractual and, later, technological shackles in order to ensure the prominent (and ultimately permanent) presence of Internet Explorer on every Windows user's PC system, and to increase the costs attendant to installing and using Navigator on any PCs running Windows.

    Second, Microsoft imposed stringent limits on the freedom of OEMs to reconfigure or modify Windows 95 and Windows 98 in ways that might enable OEMs to generate usage for Navigator in spite of the contractual and technological devices that Microsoft had employed to bind Internet Explorer to Windows.

    Finally, Microsoft used incentives and threats to induce especially important OEMs to design their distributional, promotional and technical efforts to favor Internet Explorer to the exclusion of Navigator.

    Microsoft's actions increased the likelihood that pre-installation of Navigator onto Windows would cause user confusion and system degradation, and therefore lead to higher support costs and reduced sales for the OEMs.

    Internet Explorer is not demonstrably the current "best of breed" Web browser, nor is it likely to be so at any time in the immediate future

    Not willing to take actions that would jeopardize their already slender profit margins, OEMs felt compelled by Microsoft's actions to reduce drastically their distribution and promotion of Navigator.

    The substantial inducements that Microsoft held out to the largest OEMs only further reduced the distribution and promotion of Navigator in the OEM channel

    The response of OEMs to Microsoft's efforts had a dramatic, negative impact on Navigator's usage share.

    The drop in usage share, in turn, has prevented Navigator from being the vehicle to open the relevant market to competition on the merits.

    2. Maintenance of Monopoly Power by Anticompetitive Means

    ...

    Microsoft early on recognized middleware as the Trojan horse that, once having, in effect, infiltrated the applications barrier, could enable rival operating systems to enter the market for Intel-compatible PC operating systems unimpeded.

    Middleware [like Netscape's browser] threatened to demolish Microsoft's coveted monopoly power

    Simply put, middleware threatened to demolish Microsoft's coveted monopoly power. Alerted to the threat, Microsoft strove over a period of approximately four years to prevent middleware technologies from fostering the development of enough full-featured, cross-platform applications to erode the applications barrier.

    Microsoft's campaign succeeded in preventing - for several years, and perhaps permanently - Navigator and Java from fulfilling their potential to open the market for Intel-compatible PC operating systems to competition on the m

  82. There's a simple answer here. (and a rant) by Anonymous Coward · · Score: 0

    Just buy AMD hardware instead. It's a better investment for the future, as once OSS driver support is complete, you will be able to use it regardless of what happens to AMD.

    I know, I know, this implies that you won't just-be-upgrading-again-next-year-so-why-bother, but the way performance is currently going, it no longer really matters much.
    Smarter software is more important.
    Less power use is more important.

    Peak specs just haven't been a market driver for a few years now. We got "fast enough", "enough memory", etc.
    The applications just can't use more. Lower power, lighter weight and longer battery life have been the main things.

    4 GiB ought to be enough for anybody. And often is. How often do you ever have more than that allocated and actually used, rather than just being used for buffers that *maybe* help performance a little here and there? How many games require more than that to run at all? How much difference in performance of games is there between systems running 8 GiB and 16 GiB? Sure, it gives you something to brag about, but do you really need it?

    How much of a difference does that jump from 2 GiB to 3 GiB on video memory make?

    Now if we jump to retina display resolution then that isn't true - but there's no level beyond retina display.
    An improvement of resolution beyond that point simply makes no difference at all, that's the point of a retina display. You just start getting physically bigger, and/or enable a closer focal length.

    proper, working, non-tiring VR will take over soon and eliminate even big high resolution displays. Our eyes simply don't have all that much actual retinal resolution anyway. With low-latency VR incorporating gaze tracking and dynamic resolution (as well as tracking focal plane depth per eye as well) computational requirements will actually *drop*. Since only what you're looking at directly need be rendered in high resolution. Carmack is already looking into this.

    So then what you will *need* will be a video card with at least two outputs, and a couple orders of magnitude *less* performance than the top end of today. So, why upgrade?

    So are NVIDIA in the wrong here?

    Hell yes they are, they're not following scientific practice, and are therefore not following engineering practice, and are therefore negligent in their mandated responsibility to their customers.

    Sure we've let a lot of companies get away with doing this for a long time now, but just because a practice is common, doesn't excuse it from being *wrong*. Ultimately it ought to be stopped.

    Delete patent law! Registering source design documents should be the function of the people currently in the patent office. We should be requiring the source code to all sold items.

    We should be requiring that so that it can be confirmed that their engineering is in fact competent to the standards at the time of the design. We should be requiring all hardware to be open source in this fashion so that it is always possible to repair the things that we own, rather than continuing the wasteful and unsustainable "disposable" culture that we have. Such wastefulness ultimately hurts us all - the energy wasted can never be used again, it's entropy never naturally decreases. Once energy has been made to do work, that's it! For all time!

    Economically, practical market systems are unable to optimize for efficiency by themselves. It's just something they cannot do, and this is known as a mathematical proof!

    Fix things as above, and the increase in efficiency will soon impact an increase in overall economic growth, and *everyone* benefits. Those who have "given away their competitive advantage" will end up richer too!

    Science and engineering only work because science is exactly "open source". That science itself isn't publishing all the source details and data freely anymore means that science itself as a culture has become corrupt. Hell, ever try to read an ISO standard online lately? These standards often are legislated into legal req

  83. reverse engineering by Anonymous Coward · · Score: 0

    When I was a kid, I programmed games and demos on Commodore AMIGA.
    When I saw a special effect or a technique in another game that I liked and could not find documentation on it, I just lauched my debugger and looked at the assembler code to see how they did it, try to understand it and then do the same, but better and faster. And by looking for the PUSH's and POP's you could even guess what Pascal or C functions were originally used. Something bothered me ? (like a life counter in a game) Just change it...

    If you know a bit of assembler, closed source doesn't exist.