Jump to content

UPDATED 20.12. GenericBrightness.kext


ivik
 Share

674 posts in this topic

Recommended Posts

PEG3 is in the original extracted DSDT, you just got me thinking that I tried to overwrite it with the same address, cause P0P3 and PEG3 share 0x00030000. But chams graphics enabler inject it under PEG3.GFX0, also without any enablers the display0 is under PEG3, I just verified it again, also with a freshly extracted DSDT that the PEG3 method is present.

 

I remember I tried months ago to inject values on all possible graphic sections, PCI0.P0P2.VGA, PCI0.P0P3.VGA, PCI0.GFX0, etc, because I couldn't really believe that PEG3 was responsible for the 330m card with all the other graphic spaces available, well the graphics worked only under the PEG3 space without any enablers (never used kext enablers anyway).

Link to comment
Share on other sites

Driver for test with hdmi.

With this driver, max brightness is hardcoded to 0x400. Use it only if you have this max brightness.

 

Current brightness is readed from getPMRootDomain()->getProperty(kIOBacklightUserBrightnessKey))))

 

After 5 second after manually loading I got KP.

 

post-256765-1294824056_thumb.jpg

Link to comment
Share on other sites

Driver loaded correctly, I thing:

Console:

	kernel	Acpi brightness levels:8, lowest brightness:20, highest brightness:93

 

IOreg:

MacBook_Pro__wojnar_.zip

 

Slider working, but brightness doesn't change.

 

//edit

Few lines later in console:

   kernel	GenericBrightness: No object of method _BCM
kernel	GenericBrightness: No object of method _BCM
kernel	GenericBrightness: No object of method _BCM

Link to comment
Share on other sites

Something is wrong with your dsdt.

It is wierd that _BCL is found, but not _BCM, and they are under same device.

 

Try this already compiled dsdt.

 

WOW it works, now I can change brightness. WOW

 

Thanks

Link to comment
Share on other sites

  • 2 weeks later...

on my notebook (See signature)

driver is loaded correctly I think

Jan 27 21:12:00 MacBook-Pro-di-Astaga kernel[0]: Previous Shutdown Cause: 3

Jan 27 21:12:00 MacBook-Pro-di-Astaga kernel[0]: Acpi brightness levels:6, lowest brightness:40, highest brightness:100 

Jan 27 21:12:01 MacBook-Pro-di-Astaga kernel[0]: NVDANV50HAL loaded and registered.

Slider is always at maximun (if I try to control, it return at maximun and brightness doesn't change)

 

Can someone help me?

 

Furthermore if I switch between AC/DC and battery, brightness doesn't change. Is this connected to the control LCD Brightness? how I can fix this too

dsdt_and_ioreg.zip

Link to comment
Share on other sites

Hey Ivik,

 

Just want to take a moment to say THANKS! This is really some quality work with much needed results.

 

I was seeing the KP when trying to plug-unplug HDMI, but with your latest one, all is great!

 

I have two suggestions:

 

1 - Update the version number on the new one. Currently they both show 1.0

 

2 - Post the new one on the first post. Right now it looks like just the first one is there (or was I confused because they are both showing 1.0?)

 

I am getting ready to roll out a new release of my installation guides for HP laptops and brightness control has been something many were clamoring for. I will be including this in the new release, and I have a link to your thread on our first post.

 

http://www.insanelymac.com/forum/index.php?showtopic=221653

 

Thanks again!

Link to comment
Share on other sites

@Astaga

 

You didn't read topic. LCD1234 must be added where _BCM, _BCL are... (LCD in your case)

Your max brightness is 0. This is why slider doesn't move.

Find on this topic how to inject your graphics properties into DSL. When you managed to get you slider moving, and if then doesn't work, post back.

 

@Mammoth

 

This driver is only for testing. It doesn't have max brightness detection (hardcoded 0x400), brightness is readed from another place in ioreg and it doesn't dim on battery.

It is also not linked to graphics familiy iokit.

I'm not able to find why it panics. It is just workaround for now... sorry.

Link to comment
Share on other sites

This driver is only for testing. It doesn't have max brightness detection (hardcoded 0x400), brightness is readed from another place in ioreg and it doesn't dim on battery.

It is also not linked to graphics familiy iokit.

I'm not able to find why it panics. It is just workaround for now... sorry.

I think Mammoth was referring to the driver from the first post. I don't know, for some reason the kernel panics have stopped, but we will still have to test more on this. Maybe it's because we use a different driver for battery management now or maybe it's the upgrade to 10.6.6.

Anyway, I have another problem with GenericBrightness at the moment. The Brightness level isn't remembered after reboot. It always goes back to about 80%. And of course, the backlight keys on the keyboard don't work for HP. I've tried some of your compiled versions of VoodooPS2, but then I loose trackpad and also none of the key combinations work properly.

How do we actually mod the VoodooPS2 (where?) to get the proper keys?

Btw, as the source we should use the latest optimized VoodooPS2 from here. At least for me, that works the best, and it doesn't require the ApplePS2Nub.

 

Thanks!

 

UPDATE: It's actually quite ironic what had just happened. I tried changing the resolution of the display, cause somewhere on the net I found that for real macs, if they stop remembering the backlight level after reboot, the solution is to change the resolution and change it back. So I tried that, but as soon as I changed the resolution, it KP'ed.

Photo attached.

post-72425-1296290327_thumb.jpg

Link to comment
Share on other sites

@NIXin

 

I posted some links in this topic where apple hardware store brightness levels for nvidia, but i can't test them since i don't have hardware. I know for intel graphics and i can set brightness slider on boot with just dsdt hack, reading EC value for brightness and then changing that memory on ec init.

 

Driver only reads ioreg value and then sets that to real brightness. I don't change ioreg value. Apple reads this from somewhere, depending on graphics card.

 

Do brightness keys work with my driver?

 

You can use andy's driver and just replace keyboard driver.

I mapped e012=down and e017=up from http://cgit.freedesktop.org/hal-info/tree/...0-keymap-hp.fdi

 

Other keys are not mapped. I use different version than andy.

I already explained how to map buttons. ( ApplePS2ToADBMap.h file) Dells, lg and samsung don't have release event, so driver fakes them (VoodooPS2Keyboard.cpp file)

Link to comment
Share on other sites

@Nixin,

 

Did you try adding the graphics device-properties from the MacBookPro6,1 to your boot plist (in manner suggested by Scorpy22)? As the MBP uses the 320M I would think that modding in this way will be the nicer way to achieve brightness control and probably better for you - it certainly works very well for my Vostro with 310M.

 

For me, that mod (e.g. see the device-properties key and string in my plist attached) plus adding the device (PNLF) to my DSDT gives native brightness adjustment without needing to use the genericbrightness method. As a bonus it also gives full QE/CI etc automatically (i.e. lets me set graphicsenabler=no and doesn't need any enabler kext) so it definitely makes my machine more "vanilla" than before. Another advantage is it is fully recognised in the IOREG and does the auto-dim tricks of sensing when the laptop is unplugged from mains power and dimming on battery before going to screen saver etc.

 

It does still revert to high brightness on boot, but this post gives you a way to set brightness to a given different pre-set value so that you can start up at a pre-decided brightness. It is not as good as remembering last brightness level, but it does help.

com.apple.Boot.plist.zip

 

N.B.// The same trick of taking the device-properties from a Mac model with the same/similar Nvidia graphics card and sticking them in the boot plist also works for my Zotac by using the device-properties from the MacMini3,1 (with 9400M graphics).

Link to comment
Share on other sites

@Nixin,

 

Did you try adding the graphics device-properties from the MacBookPro6,1 to your boot plist (in manner suggested by Scorpy22)? As the MBP uses the 320M I would think that modding in this way will be the nicer way to achieve brightness control and probably better for you - it certainly works very well for my Vostro with 310M.

 

Hi

Well, that's what I'm doing at the moment (more less). I'm not injecting it in the boot plist, but directly into DSDT, so even better - but I still have to use GenericBrightness for brightness to work (PNLF method though).

Anyway, I've converted your HEX string into ASCII and I see I don't inject all of the strings to my DSDT, so I'll try putting them in and see what happens. Btw, the MBP uses 330M not 320M.

Here's the converted string if anybody is interested.

<key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)</key>
<dict>
	<key>@0,AAPL,boot-display</key>
	<string></string>
	<key>@0,EDID</key>
	<data>
	AP///////wAGEM2cAAAAAAATAQOAJRd4CuWVo1RPnCYBUFQAAAABAQEBAQEB
	AQEBAQEBAQEBKDyAoHCwI0AwIDYAb+YQAAAYAAAAAQAGEDAAAAAAAAAAAAog
	AAAA/gBMUDE3MVdVNi1UTEEyAAAA/gBDb2xvciBMQ0QKICAgANE=
	</data>
	<key>@0,NVDA,UnderscanMin</key>
	<string>0x00000052</string>
	<key>@0,NVMT</key>
	<data>
	DgP/IAYQzZyAB7AEIAiwB9AHAADTBLMEuQQAAIDaLQkAAAEB/wAAAAAAAAAA
	AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD//wAAAAAAAED/EAUCAAAAAAAABAAI
	AAD/AwAAAAAAAAAAAACAB7AEgAewBA==
	</data>
	<key>@0,backlight-control</key>
	<string>0x00000001</string>
	<key>@0,built-in</key>
	<string></string>
	<key>@0,compatible</key>
	<string>NVDA,NVMac</string>
	<key>@0,connector-type</key>
	<string>0x00000002</string>
	<key>@0,device_type</key>
	<string>display</string>
	<key>@0,display-cfg</key>
	<string>0x00000103</string>
	<key>@0,fboffset</key>
	<string>0x00030000</string>
	<key>@0,name</key>
	<string>NVDA,Display-A</string>
	<key>@0,pwm-info</key>
	<data>
	AhgAZJBZAgAIUgAApRwAAAAEAAABAAAA
	</data>
	<key>@0,use-backlight-blanking</key>
	<string></string>
	<key>@1,NVDA,UnderscanMin</key>
	<string>0x00000052</string>
	<key>@1,can-hot-plug</key>
	<string></string>
	<key>@1,compatible</key>
	<string>NVDA,NVMac</string>
	<key>@1,connector-type</key>
	<string>0x00000400</string>
	<key>@1,device_type</key>
	<string>display</string>
	<key>@1,display-cfg</key>
	<string>0x0101ffff</string>
	<key>@1,name</key>
	<string>NVDA,Display-B</string>
	<key>AAPL,aux-power-connected</key>
	<string>0x00000001</string>
	<key>AAPL,backlight-control</key>
	<string>0x00000001</string>
	<key>AAPL00,DataJustify</key>
	<string>0x00000001</string>
	<key>AAPL00,Dither</key>
	<string>0x00000000</string>
	<key>AAPL00,DualLink</key>
	<string>0x00000001</string>
	<key>AAPL00,Inverter</key>
	<string>0x00000000</string>
	<key>AAPL00,InverterFrequency</key>
	<string>0x00005208</string>
	<key>AAPL00,LinkFormat</key>
	<string>0x00000000</string>
	<key>AAPL00,LinkType</key>
	<string>0x00000000</string>
	<key>AAPL00,PixelFormat</key>
	<string>0x00000000</string>
	<key>AAPL00,T1</key>
	<string>0x00000000</string>
	<key>AAPL00,T2</key>
	<string>0x00000001</string>
	<key>AAPL00,T3</key>
	<string>0x000000c8</string>
	<key>AAPL00,T4</key>
	<string>0x000000c8</string>
	<key>AAPL00,T5</key>
	<string>0x00000001</string>
	<key>AAPL00,T6</key>
	<string>0x00000000</string>
	<key>AAPL00,T7</key>
	<string>0x00000190</string>
	<key>AAPL00,blackscreen-preferences</key>
	<string>0x00000000</string>
	<key>AAPL01,blackscreen-preferences</key>
	<string>0x00000000</string>
	<key>NVCAP</key>
	<data>
	BQEAAAAAAQAGAAAAAAABDgAAAAA=
	</data>
	<key>NVDA,Features</key>
	<string>0x00c806ff</string>
	<key>VRAM,memvendorID</key>
	<string>0x0001</string>
	<key>VRAM,totalsize</key>
	<string>0x20000000</string>
	<key>device_type</key>
	<string>NVDA,Parent</string>
	<key>model</key>
	<string>NVIDIA GeForce GT 330M</string>
	<key>rom-revision</key>
	<string>0x32333533</string>
	<key>subsystem-id</key>
	<string>0x000000c8</string>
</dict>
<key>PciRoot(0x0)/Pci(0x1b,0x0)</key>
<dict>
	<key>MaximumBootBeepVolume</key>
	<string>0x5b</string>
	<key>PinConfigurations</key>
	<data>
	UEArAUABEJBCARCQIDCLARABoJAw4MsBYOBLAQ==
	</data>
	<key>layout-id</key>
	<string>0x00000047</string>
	<key>platformFamily</key>
	<string>0x00</string>
</dict>
<key>PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)</key>
<dict>
	<key>fwswappedbib</key>
	<string>0x00000001</string>
	<key>fwtune</key>
	<data>
	AAAACOPjBAAAAAgI4+MYQQAAQAggC0C/AABwCBAAAAA=
	</data>
</dict>
<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
<dict>
	<key>AAPL,aux-power-connected</key>
	<string>0x00000001</string>
	<key>AAPL,backlight-control</key>
	<string>0x00000001</string>
	<key>AAPL,os-info</key>
	<data>
	MEkBEQEQCAAAAQAAAAAAAP////8=
	</data>
</dict>

 

For me, that mod (e.g. see the device-properties key and string in my plist attached) plus adding the device (PNLF) to my DSDT gives native brightness adjustment without needing to use the genericbrightness method. As a bonus it also gives full QE/CI etc automatically (i.e. lets me set graphicsenabler=no and doesn't need any enabler kext) so it definitely makes my machine more "vanilla" than before. Another advantage is it is fully recognised in the IOREG and does the auto-dim tricks of sensing when the laptop is unplugged from mains power and dimming on battery before going to screen saver etc.

And yes, I do get everything you mention - auto dimming, QE CI, etc... with the DSDT string from MBP6,2.

 

It does still revert to high brightness on boot, but this post gives you a way to set brightness to a given different pre-set value so that you can start up at a pre-decided brightness. It is not as good as remembering last brightness level, but it does help.

com.apple.Boot.plist.zip

Exactly what I was looking for! THANKS! Very useful.

 

It's interesting. You're saying, you don't need to use GenericBrightness.kext at all? Even the PNLF version?

ivik was saying it's impossible, because real macs don't use EC to control brightness, and my HP does change EC registers to change the brightness value.

 

@ivik: they did work indeed, but just not the right ones, I believe Fn+Insert instead of Fn+BrightnessUp or something. But now that I check, for some reason it seams it's not working at all (tried different keys). Not using your keyboard driver though. I've looked at the code you provided for the nvidia mac, but don't have time to dig into it at the moment. How would this help us anyway?

Link to comment
Share on other sites

It's interesting. You're saying, you don't need to use GenericBrightness.kext at all? Even the PNLF version?

ivik was saying it's impossible, because real macs don't use EC to control brightness, and my HP does change EC registers to change the brightness value.

 

Yes, that's true - I don't use the genericbrightness kext at all, it never worked for my Vostro. The only thing I needed apart from grabbing the device properties from the MBP and adding them to the boot plist (or DSDT if you prefer) was to add Device (PNLF) to the DSDT.

 

I too do find it annoying though that there is no remembering of the brightness between boot, but at least by the method I mentioned you can pick your own preferred level for startup instead of it being full on.

 

I am sure though that for people who can code ( :( ) , it is probably an easy matter to read the brightness level before every shutdown and modify the brightness plist so it will start up at the brightness level you last used.....

Link to comment
Share on other sites

I am sure though that for people who can code ( ;) ) , it is probably an easy matter to read the brightness level before every shutdown and modify the brightness plist so it will start up at the brightness level you last used.....

If you can get the guy who originally wrote this brightness to give the source code for that little app I think I should be able to do it, hopefully it's written in something based on C.

 

EDIT:

actually, it's possible to do it with the app we have now.

I'll write a script for just that, but in about two weeks after I hand-in my university projects. Lot's of other work now.

Link to comment
Share on other sites

  • 3 weeks later...
...

UPDATE: It's actually quite ironic what had just happened. I tried changing the resolution of the display, cause somewhere on the net I found that for real macs, if they stop remembering the backlight level after reboot, the solution is to change the resolution and change it back. So I tried that, but as soon as I changed the resolution, it KP'ed.

Hi folks,

 

I confirm this what 'NIXin' wrote about KP after resolution change

 

Ivik any chance you could fix this in your kext ?

Thanks

s

 

Edit:

 

and if anybody interested, here you have compressed file with brightness command line tool, and three scripts examples (put one in your Login Items)

you can edit them with AppleScript Editor

variables for brightness utility are numbers between 0 and 1 so:

lowest lvl: brightness 0; brightness 0.1; brightness 0.x ....brightness 1 - max lvl

 

remember about copying brightness utility to your /bin or /usr/bin directory - these are hidden directories on your root folder

sudo su

cp /path_to_brightness_file/brightness /bin/

 

BRGT_script_util.zip

enjoy

s

Link to comment
Share on other sites

 

 

SUCCESS !!!

I managed to get brightness working on my laptop (Nvidia G310m) ! Although it doesn't use your kext, ivik, but I have used it a lot during my research and I think it is interesting information for other nvidia users.


Edit: Please see the post below as I have it working now.

I followed a similar approach and get the brightness kext, slider loaded. FN+Pg up, and FN+Insert are assigned to the brightness control. I have sun appear while changing the brightness.
40 0 0x566e2000 0x4000 0x3000 com.apple.driver.AppleBacklight (170.0.34) <39 21 14 5 4 3>
This is the DSDT code I used. I took the values from MacbookPro5,1, which has a 9600M GT. EDID and a few other things are different from the original one.
Method (_DSM, 4, NotSerialized)
{
Store (Package (0x5E)
{
"AAPL,aux-power-connected",
Buffer (0x04)
{
0x01, 0x00, 0x00, 0x00
},

"AAPL,backlight-control",
Buffer (0x04)
{
0x01, 0x00, 0x00, 0x00
},

"AAPL00,blackscreen-preferences",
Buffer (0x04)
{
0x00, 0x00, 0x00, 0x00
},

"AAPL01,DataJustify",
Buffer (0x04)
{
0x01, 0x00, 0x00, 0x00
},

"AAPL01,Dither",
Buffer (0x04)
{
0x00, 0x00, 0x00, 0x00
},

"AAPL01,DualLink",
Buffer (0x04)
{
0x01, 0x00, 0x00, 0x00
},

"AAPL01,Inverter",
Buffer (0x04)
{
0x00, 0x00, 0x00, 0x00
},

"AAPL01,InverterFrequency",
Buffer (0x04)
{
0x08, 0x52, 0x00, 0x00
},

"AAPL01,LinkFormat",
Buffer (0x04)
{
0x00, 0x00, 0x00, 0x00
},

"AAPL01,LinkType",
Buffer (0x04)
{
0x00, 0x00, 0x00, 0x00
},

"AAPL01,PixelFormat",
Buffer (0x04)
{
0x00, 0x00, 0x00, 0x00
},

"AAPL01,T1",
Buffer (0x04)
{
0x00, 0x00, 0x00, 0x00
},

"AAPL01,T2",
Buffer (0x04)
{
0x01, 0x00, 0x00, 0x00
},

"AAPL01,T3",
Buffer (0x04)
{
0xC8, 0x00, 0x00, 0x00
},

"AAPL01,T4",
Buffer (0x04)
{
0xC8, 0x00, 0x00, 0x00
},

"AAPL01,T5",
Buffer (0x04)
{
0x01, 0x00, 0x00, 0x00
},

"AAPL01,T6",
Buffer (0x04)
{
0x00, 0x00, 0x00, 0x00
},

"AAPL01,T7",
Buffer (0x04)
{
0x90, 0x01, 0x00, 0x00
},

"AAPL01,blackscreen-preferences",
Buffer (0x04)
{
0x00, 0x00, 0x00, 0x00
},

"@0,EDID",
Buffer (0x80)
{
/* 0000 */ 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00,
/* 0008 */ 0x4C, 0xA3, 0x4D, 0x31, 0x00, 0x00, 0x00, 0x00,
/* 0010 */ 0x00, 0x12, 0x01, 0x03, 0x80, 0x23, 0x14, 0x78,
/* 0018 */ 0x0A, 0x87, 0xF5, 0x94, 0x57, 0x4F, 0x8C, 0x27,
/* 0020 */ 0x27, 0x50, 0x54, 0x00, 0x00, 0x00, 0x01, 0x01,
/* 0028 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01,
/* 0030 */ 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x1D, 0x36,
/* 0038 */ 0x80, 0xA0, 0x70, 0x38, 0x1E, 0x40, 0x30, 0x20,
/* 0040 */ 0x25, 0x00, 0x61, 0xC6, 0x10, 0x00, 0x00, 0x19,
/* 0048 */ 0x00, 0x00, 0x00, 0x0F, 0x00, 0x00, 0x00, 0x00,
/* 0050 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x20, 0x91, 0x02,
/* 0058 */ 0x64, 0x00, 0x00, 0x00, 0x00, 0xFE, 0x00, 0x53,
/* 0060 */ 0x41, 0x4D, 0x53, 0x55, 0x4E, 0x47, 0x0A, 0x20,
/* 0068 */ 0x20, 0x20, 0x20, 0x20, 0x00, 0x00, 0x00, 0xFE,
/* 0070 */ 0x00, 0x31, 0x36, 0x30, 0x48, 0x54, 0x30, 0x33,
/* 0078 */ 0x2D, 0x30, 0x30, 0x31, 0x0A, 0x20, 0x00, 0x60
},

"AAPL,alias-policy",
Buffer (0x04)
{
0x00, 0x00, 0x00, 0x00
},

"@0,AAPL,blackscreen-preferences",
Buffer (0x04)
{
0x00, 0x00, 0x00, 0x00
},

"@0,AAPL,boot-display",
Buffer (Zero) {},
"@0,backlight-control",
Buffer (0x04)
{
0x01, 0x00, 0x00, 0x00
},

"@0,built-in",
Buffer (Zero) {},
"@0,connector-type",
Buffer (0x04)
{
0x00, 0x00, 0x00, 0x00
},

"@0,display-cfg",
Buffer (0x04)
{
0x03, 0x01, 0x03, 0x00
},

"@0,fboffset",
Buffer (0x04)
{
0x00, 0x00, 0x01, 0x00
},

"@0,pwm-info",
Buffer (0x14)
{
/* 0000 */ 0x01, 0x14, 0x00, 0x64, 0xA8, 0x61, 0x00, 0x00,
/* 0008 */ 0x08, 0x52, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00,
/* 0010 */ 0x00, 0x04, 0x00, 0x00
},

"@0,use-backlight-blanking",
Buffer (Zero) {},
"@1,AAPL,blackscreen-preferences",
Buffer (0x04)
{
0x00, 0x00, 0x00, 0x00
},

"@1,connector-type",
Buffer (0x04)
{
0x00, 0x00, 0x00, 0x00
},

"@1,display-cfg",
Buffer (0x04)
{
0xFF, 0xFF, 0x08, 0x01
},

"AAPL,slot-name",
Buffer (0x0F)
{
"PCI Slot@1,0,0"
},

"@0,compatible",
Buffer (0x0B)
{
"NVDA,NVMac"
},

"@0,device_type",
Buffer (0x08)
{
"display"
},

"@0,name",
Buffer (0x0F)
{
"NVDA,Display-A"
},

"@1,compatible",
Buffer (0x0B)
{
"NVDA,NVMac"
},

"@1,device_type",
Buffer (0x08)
{
"display"
},

"@1,name",
Buffer (0x0F)
{
"NVDA,Display-B"
},

"NVCAP",
Buffer (0x14)
{
/* 0000 */ 0x05, 0x01, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00,
/* 0008 */ 0x06, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x0B,
/* 0010 */ 0x00, 0x00, 0x00, 0x00
},

"VRAM,totalsize",
Buffer (0x04)
{
0x00, 0x00, 0x00, 0x20
},

"NVPM",
Buffer (0x1C)
{
/* 0000 */ 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
/* 0008 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
/* 0010 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
/* 0018 */ 0x00, 0x00, 0x00, 0x00
},

"device_type",
Buffer (0x0D)
{
"NVDA,GeForce"
},

"model",
Buffer (0x18)
{
"nVidia GeForce 9600M GT"
},

"rom-revision",
Buffer (0x26)
{
"nVidia GeForce 9600M GT OpenGL Engine"
},

"reg",
Buffer (0x78)
{
/* 0000 */ 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00,
/* 0008 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
/* 0010 */ 0x00, 0x00, 0x00, 0x00, 0x10, 0x00, 0x01, 0x02,
/* 0018 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
/* 0020 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01,
/* 0028 */ 0x14, 0x00, 0x01, 0x42, 0x00, 0x00, 0x00, 0x00,
/* 0030 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
/* 0038 */ 0x00, 0x00, 0x00, 0x10, 0x1C, 0x00, 0x01, 0x02,
/* 0040 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
/* 0048 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02,
/* 0050 */ 0x24, 0x00, 0x01, 0x01, 0x00, 0x00, 0x00, 0x00,
/* 0058 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
/* 0060 */ 0x80, 0x00, 0x00, 0x00, 0x30, 0x00, 0x01, 0x02,
/* 0068 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
/* 0070 */ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x08, 0x00
}
}, Local0)
DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
Return (Local0)
}
But it seems that i have problem with brightness values. See below.
post-562417-1297896991_thumb.jpg

And this the PNLF device.
post-562417-1297897002_thumb.jpg
Finally, this is my DSDT file.
http://www.mediafire.com/?82n4x89yovpodcs
This is the ioreg dump.
http://www.mediafire.com/?y433p96w52gb3c4

It seems that i am on the right path but there is something missing. I also tried different combination e.i GraphicsEnabler, EFI string etc. Same result.
Any ideas?


Edit: When I change the brightness and update the ioreg afterwards, I can see the brightness values changing but actual LCD brightness doesn't change.

Edit 2: Please see the post below as I have it working now.
Link to comment
Share on other sites

 Share

×
×
  • Create New...