I think that NvClock and his doc it's not need in the new page because:if this trick works for many people (even if not for me), shall we add it to the new doc page?
- if you have MacBook 5,1 --> nvidia_bl works better of NvClock
- if you have MacBook PRO 5,1 --> mbp_nvidia_bl (and nvidia_bl in the future) works better of NvClock
Am I in wrong?
P.s. I update the "MacBook5-1/Intrepid" with all info (some sections must be re-write in the future days) for the MacBook 5,1 (not Pro, because the correct page for it is "MacBookPro5-1/Intrepid").
Last edited by ercoppa; January 27th, 2009 at 11:40 PM.
Excuse me for my bad english - MacBook 5,1 2.0 Ghz
Yep, the MBP5,1 page is here:
not much there yet as the MBP got overlooked for some reason when all this work started.
indeed, nvclock does not work for me. and if MB5.1 owners are not using it (thanks to the latest developments of nvidia-bl-dkms), it definitely should not go on the doc page.
i will take care of filling up the MBP5.1/intrepid page instead, just give me a couple of days to finish some work and i'll be back to it.
greetings to all, Lo.
Lo runs Kubuntu 9.10-amd64 on a MacBookPro 5.1, and feels Karmic :~)
however, if nvclock -S does not work, we have a serious problem. that means either Apple didn't connect the chips' smartdimmer signals to the display logic (maybe due to the second graphics adapter) and uses a different mechanism not yet discovered, or the registers have been moved (once again), which isn't very likely, though. that's not very satisfying ...
Here is a script which use the web-camera to "measure" the lux (candela/luminescence) and then set the screen brightness automatically. Thanks again for the module, and please enjoy.