I have an EliteBook 8560w Mobile Workstation with a Quadro 1000m GPU.
On Ubuntu 12.04 LTS with 304.88 my system works as expected.
This is also true for 310.x versions, however, they have been removed from the official repositories (or it is just the jockey driver manager too lazy to show them). Unfortunately, with 313.x and 319.x, I can not control screen brightness (FN-key operations are recognized).
I thought that the new 331.x series would solve the problem as it has the following line in the what’s new description: “Added a new NV-CONTROL attribute, NV_CTRL_BACKLIGHT_BRIGHTNESS, for controlling backlight brightness.”. However, I have red forums on the net and it turned out, that with Ubuntu 13.10 and the very latest nvidia 331.x drivers, brightness control still does not work.
Sad background story: I have replaced my AMD GPU based HP notebook to this because of bad GPU driver support (AMD Legacy card). I thought to myself that this enterprise grade notebook equipped with this serious GPU would have no such problem. And when I bought this notebook 6 months ago, I was so satisfied that everything just worked.
However, now I’m desperately waiting for a fix for this problem. I can not use OpenSuSe or Fedora as they only have newer drivers in the repositories, and the 304.x drivers (which are the legacy branch for 6/7 series) do not work. I can still use the computer with Ubuntu 12.04 LTS/304.88 drivers until 2017 April. However, the software is becoming outdated, and Steam always notifies me that I should update my drivers.
My opinion: I think that Nvidia should make sure that at least the Quadro workhorses are supported well, even under Linux. I really hope that there will be a fix for this, and I will have the chance to move on with the next LTS Ubuntu release, which is 14.04 LTS, so the next one. I hope that my purchase will last longer than only one Ubuntu distribution.
I think that my problem is a duplicate of this: [url][NVidia 319.12] Brightness controls not working on laptop (Ubuntu 13.03) - Linux - NVIDIA Developer Forums
Question: Is this problem acknowledged? And if so, can we be sure that a fix will come in the near future?