Jump to content

[GUIDE] 1st Generation Intel HD Graphics QE/CI


GhostRaider
 Share

2,093 posts in this topic

Recommended Posts

@alboz83 for now you can only use the intel card no chances to make a dual video card setup work right now, by the way, i think this fix is driving my computer to hell since it's working at 70° celsius idle and it reach 100° easily watching flash videos online... is not so good, i don't want to cook eggs on it... any help? speedstep is working and i've patched my dsdt to disable the nvidia card (i'm running on a Optimus lap)... Plus, no wake from sleep... (it works but no backlit on screen)

Link to comment
Share on other sites

I was installing DualLink framebuffers. Installing DualLink LCD+VGA Alternative I got a distorted screen. Installing DualLink LCD+VGA my system isn't started.

 

For my screen resolution (1366x768) I need a SingleLink framebuffer. I had not heard that.

 

I reinstalled the AppleIntelHDGraphicsFB.kext with a SingleLink LCD+VGA Alternative framebuffer and now the screen is working flawlessly!

 

Thanks for the help!

  • Like 1
Link to comment
Share on other sites

Just to let you guys know, my ZIP archive already had this, you just had to pick the one you needed, i'm guessing the alternative frame buffer. You didn't have to go through all that trouble. :P Assuming you were using 10.8.3.

 

I tried all kinds of combinations but always had to remove the AppleIntelHDGraphics.kext to be able to boot. It didn't work until I followed enjiner's method. Dunno why :S And yes, I am on 10.8.3, installed via myhack.

Link to comment
Share on other sites

I need some litle help shoosing the right SMBios,

 

My CPU is dual core Processador Intel® Pentium® U5400, but in osx it assumes as core i7, what is the best SMBios for this CPU?

Thank you all for helping me!

 

Have you tried all framebuffers from the ZIP archive?

 

I tried all kinds of combinations but always had to remove the AppleIntelHDGraphics.kext to be able to boot. It didn't work until I followed enjiner's method. Dunno why :S And yes, I am on 10.8.3, installed via myhack.

 

I saw the plist file and yeah I can confirm there is a slight modification compared to the ones in my ZIP archive. I will add another framebuffer to the family.

  • Like 1
Link to comment
Share on other sites

Have you tried all framebuffers from the ZIP archive?

 

 

 

I saw the plist file and yeah I can confirm there is a slight modification compared to the ones in my ZIP archive. I will add another framebuffer to the family.

i have tested all and changed one like below, tested also all kind of SMBios and Clover Chimera and Chameleon. lol i have made so many restarts to my laptop that is better to guive VNC access to someone that understands much better than me wat todo hehe.

 

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>CFBundleDevelopmentRegion</key>

<string>English</string>

<key>CFBundleExecutable</key>

<string>AppleIntelHDGraphicsFB</string>

<key>CFBundleGetInfoString</key>

<string>AppleIntelHDGraphicsFB 8.10.44</string>

<key>CFBundleIdentifier</key>

<string>com.apple.driver.AppleIntelHDGraphicsFB</string>

<key>CFBundleInfoDictionaryVersion</key>

<string>6.0</string>

<key>CFBundleName</key>

<string>com.apple.driver.AppleIntelHDGraphicsFB</string>

<key>CFBundlePackageType</key>

<string>KEXT</string>

<key>CFBundleShortVersionString</key>

<string>8.10.44</string>

<key>CFBundleSignature</key>

<string>????</string>

<key>CFBundleVersion</key>

<string>8.1.0</string>

<key>IOKitPersonalities</key>

<dict>

<key>AppleIntelHDGraphicsFB</key>

<dict>

<key>CFBundleIdentifier</key>

<string>com.apple.driver.AppleIntelHDGraphicsFB</string>

<key>FBCControl</key>

<dict>

<key>Compression</key>

<integer>0</integer>

</dict>

<key>FeatureControl</key>

<dict>

<key>FBC</key>

<integer>0</integer>

<key>GPUInterruptHandling</key>

<integer>0</integer>

<key>Gamma</key>

<integer>0</integer>

<key>MaximumSelfRefreshLevel</key>

<integer>0</integer>

<key>PowerStates</key>

<integer>0</integer>

<key>RSTimerTest</key>

<integer>0</integer>

<key>RenderStandby</key>

<integer>0</integer>

<key>Watermarks</key>

<integer>0</integer>

</dict>

<key>IOClass</key>

<string>AppleIntelHDGraphicsFB</string>

<key>IOMatchCategory</key>

<string>IOFramebuffer</string>

<key>IOPCIClassMatch</key>

<string>0x03000000</string>

<key>IOPCIPrimaryMatch</key>

<string>0x468086</string>

<key>IOProbeScore</key>

<integer>80000</integer>

<key>IOProviderClass</key>

<string>IOPCIDevice</string>

<key>IOSourceVersion</key>

<string>8.10.44</string>

</dict>

</dict>

<key>NSHumanReadableCopyright</key>

<string>Copyright © 1999-2012 Apple Inc. All rights reserved.</string>

<key>OSBundleLibraries</key>

<dict>

<key>com.apple.iokit.IOACPIFamily</key>

<string>1.2</string>

<key>com.apple.iokit.IOGraphicsFamily</key>

<string>1.3</string>

<key>com.apple.iokit.IOPCIFamily</key>

<string>1.1</string>

<key>com.apple.kpi.bsd</key>

<string>8.0.0</string>

<key>com.apple.kpi.iokit</key>

<string>8.0.0</string>

<key>com.apple.kpi.libkern</key>

<string>8.0.0</string>

<key>com.apple.kpi.mach</key>

<string>8.0.0</string>

<key>com.apple.kpi.unsupported</key>

<string>8.0.0</string>

</dict>

<key>OSBundleRequired</key>

<string>Safe Boot</string>

</dict>

</plist>

Link to comment
Share on other sites

i have tested all and changed one like below, tested also all kind of SMBios and Clover Chimera and Chameleon. lol i have made so many restarts to my laptop that is better to guive VNC access to someone that understands much better than me wat todo hehe.

 

You said your computer has an Intel Pentium U5400? I'm not sure if the Intel HD Graphics IGPU on that processor is the same, but as I said awhile back, go to Alexanita's thread and create your own patched frame buffer by following his short guide.

  • Like 1
Link to comment
Share on other sites

You said your computer has an Intel Pentium U5400? I'm not sure if the Intel HD Graphics IGPU on that processor is the same, but as I said awhile back, go to Alexanita's thread and create your own patched frame buffer by following his short guide.

Thank you GhostRaider, i will do that, in mean wille your guide for CI worked great for me, before youtube videos were black and now i can see them, really thanks.
Link to comment
Share on other sites

Toshiba TOS5091 monitor problems: Looks like MAC can not define the fresh rate: 60HZ

 

13-4-7 下午3:32:08.372 System Preferences[204]: CVCGDisplayLink::setCurrentDisplay didn't find a valid display - falling back to 60Hz

 

 

There is no @60 HZ in my monitor Screen.

 

But where can I do it in DSDT?

 

EDID:

00 FF FF FF FF FF FF 00 51 F3 91 50 00 00 00 00 0E 10 01 03 80 1D 11 FF 2F 00 00 A0 57 49 9B 26 10 48 4F 00 00 00 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 14 1E 56 13 51 00 0C 30 23 70 12 00 27 A6 10 00 00 18 0E 14 56 13 51 00 0C 30 23 70 12 00 27 A6 10 00 00 18 00 00 00 FC 00 49 6E 74 65 72 6E 61 6C 20 4C 43 44 00 00 00 00 FD 00 00 3C 00 35 08 00 00 00 00 00 00 00 00 00 15

 

After fix the @60HZ issue, Maybe we can try the FB kext. So far all FB Kext can not show the internal LCD. Through the VNC there is no internal LCD available .

 

I only have CI with 8.3, With Chameleon and modules to get the 1366x768 screen.

post-884632-0-11769600-1365320542_thumb.png

dsdt.aml.zip

Link to comment
Share on other sites

Hi all,

I got in touch with Slice (the guy who made Clover Bootloader and many other stuff for the hackintosh community). I explained him my problem. Basically I told him my laptop panel is not outputting any edid and so the framebuffer cannot work at all. I told him I've done many tests (edid injection with clover, different FBs, device string injections and so on) and I came to the conclusion that the FB is not working in my case because of no edid datas were provided by the laptop panel.

 

Slice thinks the edid is not the problem. I'm quoting his answer: "......About your issue I may say that EDID is injected but Framebuffer don't find any connected monitor. It is not because of EDID. It is because of other address of I2C/DDC registers which is OEM specific. If someone disassemble the kext AppleIntelHDGraphicsFB and understand where is the register then we can propose a method to correct it."

 

It looks like we were wrong! If anyone is able to disassemble the kext AppleIntelHDGraphicsFB all people with EDID problems may finally have a working FB.

Maybe Verteks can do that?

 

With hope

Pentothal

Link to comment
Share on other sites

That makes sense considering the problems that others were having.

 

This is a little beyond my skill level, but a good place to start would be comparing the 10.6 fb to the 10.8 because evidently the panel works in sl also, this may explain why some people were having success with multiple edid overwrites

Link to comment
Share on other sites

Guys I Love to test new stuff and all beta's are part of it, i don't know if my consciousness is tricky but the new graphics drivers its like i have an nvidia in my system the fluidity is so amazing.I will attach them un-patched prove me wrong or right.

 

NOTE it's not patched so you will have to apply vertex patcher to it.

 

And i was thinking why don't we make verteks patch into a clover or chameleon module.

 

It would allow us to boot vanilla without deleting kexts and it would avoid patching after every update or installation

 

it would just need a argument like hdenabler -w 1 -p LVDS. or any other way you get the idea.

 

 

If flash video is black disable graphics acceleration of chrome/chromium.

Link to comment
Share on other sites

Guys I Love to test new stuff and all beta's are part of it, i don't know if my consciousness is tricky but the new graphics drivers its like i have an nvidia in my system the fluidity is so amazing.I will attach them un-patched prove me wrong or right.

 

NOTE it's not patched so you will have to apply vertex patcher to it.

 

And i was thinking why don't we make verteks patch into a clover or chameleon module.

 

It would allow us to boot vanilla without deleting kexts and it would avoid patching after every update or installation

 

it would just need a argument like hdenabler -w 1 -p LVDS. or any other way you get the idea.

 

 

If flash video is black disable graphics acceleration of chrome/chromium.

 

Thank you for reporting 2bad0 :smoke:

You're saying that our Intel HD Graphics IGPU works even better on 10.8.4? I noticed that every Mountain Lion release makes our IGPU better. I was on 10.8.2 and it worked alright. On 10.8.3 it works much better. On 10.8.4, well we'll wait and see lol.

 

Unlike Intel, they have stopped improving our 2010 Intel HD Graphics on Windows. Apple on the other hand is still improving and making our IGPU work better on OS X. That's really generous of them. :)

 

It's somewhat of a conspiracy, but I still think Verteks works for Apple lol.

Link to comment
Share on other sites

Has anyone "Computer sleep" working? I have "Display sleep" working, I can put it in hibernation but when I turn it back on it freezes. The login window is visible and the mouse pointer moves but clicking cancel or typing doesn't do anything. My log file shows the following:

 

2013-04-08 8:14:25.000 PM kernel[0]: sleep
2013-04-08 8:14:25.000 PM kernel[0]: Wake reason = PWRB
2013-04-08 8:14:25.000 PM kernel[0]: No interval found for . Using 8000000
2013-04-08 8:14:25.000 PM kernel[0]: Previous Sleep Cause: 5
2013-04-08 8:14:25.000 PM kernel[0]: The USB device HubDevice (Port 1 of Hub at 0x1a000000) may have caused a wake by issuing a remote wakeup (2)
2013-04-08 8:14:25.028 PM loginwindow[41]: ERROR | -[LWScreenLock(Private) screenIsLockedTimeExpired:] | No lock state found, use built in check
2013-04-08 8:14:25.000 PM kernel[0]: [0xffffff8008be1000](0)/(5) Device not responding
2013-04-08 8:14:25.000 PM kernel[0]: IONetworkController::enable
2013-04-08 8:14:26.438 PM WindowServer[84]: handle_will_sleep_auth_and_shield_windows: no lock state data
2013-04-08 8:14:28.062 PM configd[18]: network changed: v4(en1-:192.168.1.73) DNS- Proxy- SMB
2013-04-08 8:14:28.000 PM kernel[0]: USBMSC Identifier (non-unique): 20090516388200000 0xbda 0x138 0x3882
2013-04-08 8:14:31.000 PM kernel[0]: stampWait: Overflowed checking for stamp 0x8c27 on MAIN ring: called from
2013-04-08 8:14:31.000 PM kernel[0]: timestamp = 0x8c26
2013-04-08 8:14:31.000 PM kernel[0]: ****  Debug info for apparent hang in MAIN graphics engine  ****
2013-04-08 8:14:31.000 PM kernel[0]: ring head    = 0x000000a0, wrap count = 0x 0
2013-04-08 8:14:31.000 PM kernel[0]: ring tail    = 0x00000a38 ring control = 0x00003001   enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x004 4KB pages

 

It seems a problem with the graphics engine. Is anyone else experiencing this? Does anyone have wake from sleep working?

Link to comment
Share on other sites

Have you tried all framebuffers from the ZIP archive?

 

 

 

I saw the plist file and yeah I can confirm there is a slight modification compared to the ones in my ZIP archive. I will add another framebuffer to the family.

 

Good to know. And thanks so much for all your hard work. My laptop wouldn't run OSX so nicely f it wasn't for you. :)

Link to comment
Share on other sites

great franmglp ;) are your temperatures good or the lap get hot easily?

 

I'm looking temperatures... CPU temperatures goes from 40 to 50 celsius with normal usage and from 50 to 60 celsius when I'm watching a HD video.

 

I guess that are normal temperatures, right?

Link to comment
Share on other sites

Has anyone "Computer sleep" working? I have "Display sleep" working, I can put it in hibernation but when I turn it back on it freezes. The login window is visible and the mouse pointer moves but clicking cancel or typing doesn't do anything. My log file shows the following:

 

2013-04-08 8:14:25.000 PM kernel[0]: sleep
2013-04-08 8:14:25.000 PM kernel[0]: Wake reason = PWRB
2013-04-08 8:14:25.000 PM kernel[0]: No interval found for . Using 8000000
2013-04-08 8:14:25.000 PM kernel[0]: Previous Sleep Cause: 5
2013-04-08 8:14:25.000 PM kernel[0]: The USB device HubDevice (Port 1 of Hub at 0x1a000000) may have caused a wake by issuing a remote wakeup (2)
2013-04-08 8:14:25.028 PM loginwindow[41]: ERROR | -[LWScreenLock(Private) screenIsLockedTimeExpired:] | No lock state found, use built in check
2013-04-08 8:14:25.000 PM kernel[0]: [0xffffff8008be1000](0)/(5) Device not responding
2013-04-08 8:14:25.000 PM kernel[0]: IONetworkController::enable
2013-04-08 8:14:26.438 PM WindowServer[84]: handle_will_sleep_auth_and_shield_windows: no lock state data
2013-04-08 8:14:28.062 PM configd[18]: network changed: v4(en1-:192.168.1.73) DNS- Proxy- SMB
2013-04-08 8:14:28.000 PM kernel[0]: USBMSC Identifier (non-unique): 20090516388200000 0xbda 0x138 0x3882
2013-04-08 8:14:31.000 PM kernel[0]: stampWait: Overflowed checking for stamp 0x8c27 on MAIN ring: called from
2013-04-08 8:14:31.000 PM kernel[0]: timestamp = 0x8c26
2013-04-08 8:14:31.000 PM kernel[0]: **** Debug info for apparent hang in MAIN graphics engine ****
2013-04-08 8:14:31.000 PM kernel[0]: ring head = 0x000000a0, wrap count = 0x 0
2013-04-08 8:14:31.000 PM kernel[0]: ring tail = 0x00000a38 ring control = 0x00003001 enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x004 4KB pages

 

It seems a problem with the graphics engine. Is anyone else experiencing this? Does anyone have wake from sleep working?

 

 

 

Hi, I'm having the same issue and I tried several fixes in DSDT but without luck.

If anyone can login after wake with this Intel HD Graphics please try to share how make the fix.

 

Thanks.

Link to comment
Share on other sites

Has anyone "Computer sleep" working? I have "Display sleep" working, I can put it in hibernation but when I turn it back on it freezes. The login window is visible and the mouse pointer moves but clicking cancel or typing doesn't do anything. My log file shows the following:

 

2013-04-08 8:14:25.000 PM kernel[0]: sleep
2013-04-08 8:14:25.000 PM kernel[0]: Wake reason = PWRB
2013-04-08 8:14:25.000 PM kernel[0]: No interval found for . Using 8000000
2013-04-08 8:14:25.000 PM kernel[0]: Previous Sleep Cause: 5
2013-04-08 8:14:25.000 PM kernel[0]: The USB device HubDevice (Port 1 of Hub at 0x1a000000) may have caused a wake by issuing a remote wakeup (2)
2013-04-08 8:14:25.028 PM loginwindow[41]: ERROR | -[LWScreenLock(Private) screenIsLockedTimeExpired:] | No lock state found, use built in check
2013-04-08 8:14:25.000 PM kernel[0]: [0xffffff8008be1000](0)/(5) Device not responding
2013-04-08 8:14:25.000 PM kernel[0]: IONetworkController::enable
2013-04-08 8:14:26.438 PM WindowServer[84]: handle_will_sleep_auth_and_shield_windows: no lock state data
2013-04-08 8:14:28.062 PM configd[18]: network changed: v4(en1-:192.168.1.73) DNS- Proxy- SMB
2013-04-08 8:14:28.000 PM kernel[0]: USBMSC Identifier (non-unique): 20090516388200000 0xbda 0x138 0x3882
2013-04-08 8:14:31.000 PM kernel[0]: stampWait: Overflowed checking for stamp 0x8c27 on MAIN ring: called from
2013-04-08 8:14:31.000 PM kernel[0]: timestamp = 0x8c26
2013-04-08 8:14:31.000 PM kernel[0]: **** Debug info for apparent hang in MAIN graphics engine ****
2013-04-08 8:14:31.000 PM kernel[0]: ring head = 0x000000a0, wrap count = 0x 0
2013-04-08 8:14:31.000 PM kernel[0]: ring tail = 0x00000a38 ring control = 0x00003001 enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x004 4KB pages

 

It seems a problem with the graphics engine. Is anyone else experiencing this? Does anyone have wake from sleep working?

 

I'm still not able to get my screen to wake up sadly :wacko:

 

I'm looking temperatures... CPU temperatures goes from 40 to 50 celsius with normal usage and from 50 to 60 celsius when I'm watching a HD video.

 

I guess that are normal temperatures, right?

 

That's looks normal to me. You're temperatures are similar to mine.

  • Like 1
Link to comment
Share on other sites

OK, thanks guys. Good to know it's not me messing something up. I've played around a bit but to no avail.

It seems Mac's have had this issue and I've read an old post from bcc9 where it had to do with the order of connectors.

Link to comment
Share on other sites

Any news? Nothing about the high temperatures?

 

As for any breaking news, there's not really anything new ever since QE/CI has been discovered. Verteks hasn't been online ever since the discovery which leads me to believe he knows how the Intel HD Graphics works. About your high temperatures? I think that's more of a power management issue. I'm still trying to find out how to fix my sleep issues but nobody has a clue.

Link to comment
Share on other sites

Hacks (Optional)

 

:excl: I'm assuming that you already patched your DSDT with the DTGP method. If you don't know how to do that, the InsanelyMac community is filled with information about DSDT patching. Proceed at your own risk.

 

1. DSDT (Differentiated System Description Table)

 

*PNLF Section in DSDT

 

:excl:Just a reminder, this is not a guide to enable brightness for your internal LCD. To enable brightness for your internal LCD, take a look at mnorthern's forum post.

 

What is this PNLF section in the DSDT? Actually, the question is, do you even have this PNLF section in your DSDT? If you don't then that is normal. You have to add this section manually.

 

Basically, the PNLF section is where you set the values of the brightness levels for your internal LCD.

 

Let's take a look at this PNLF section.

 

post-620531-0-81575200-1365981138_thumb.png

 

The code is a bit longer than what the screenshot shows. This is my full PNLF code:

 

Device (PNLF)
 {
	 Name (_HID, EisaId ("APP0002"))
	 Name (_CID, "backlight")
	 Name (_UID, 0x0A)
	 Name (_STA, 0x0B)
	 Method (_BCL, 0, NotSerialized)
	 {
		 Return (Package (0x13)
		 {
			 0x0384,
			 0x0384,
			 Zero,
			 0x012C,
			 0x0258,
			 0x0384,
			 0x04B0,
			 0x05DC,
			 0x0708,
			 0x0834,
			 0x0960,
			 0x0AC8,
			 0x0BB8,
			 0x0CE4,
			 0x0E10,
			 0x0F3C,
			 0x10CC,
			 0x1194,
			 0x12C0
		 })
	 }
	 Method (_BCM, 1, NotSerialized)
	 {
		 Store (0x80000000, LEVW)
		 Store (0x13121312, LEVX)
		 Store (0x80000000, LEV2)
		 Store (Arg0, LEVL)
	 }
	 Method (_BQC, 0, NotSerialized)
	 {
		 Return (BRTL)
	 }
	 Method (_DOS, 1, NotSerialized)
	 {
		 ^^PCI0.GFX0._DOS (Arg0)
	 }
 }
}

 

Lets look at the code by piece. Let's start with Method (_BCL, 0, NotSerialized).

 

post-620531-0-53794300-1365982496_thumb.png

 

Because this part of this code is called Method _BCL, you can see that it stands for Backlight Levels. Let's take a deeper look.

 

Method (_BCL, 0, NotSerialized)
	 {
		 Return (Package (0x13)
		 {

 

The Return (Package (0x13) means that there are a total of 17 brightness levels. Never change this code since that is the maximum amount of levels that the brightness lever in System Preferences supports.

 

What about this part?

 

Method (_BCL, 0, NotSerialized)
	 {
		 Return (Package (0x13)
		 {
			 0x0384,
			 0x0384,

 

Don't worry about these two beginning numbers. I will explain what these do later on. Let's focus on the next part which are the 17 brightness levels:

 

Zero, (This first number means lowest brightness)
0x012C,
0x0258,
0x0384,
0x04B0,
0x05DC,
0x0708,
0x0834,
0x0960,
0x0AC8,
0x0BB8,
0x0CE4,
0x0E10,
0x0F3C,
0x10CC,
0x1194,
0x12C0 (This last number means maximum brightness)

 

Don't be scared of this. Let me explain what all this weird looking thing means. You'll be suprised that its not complicated to understand. Basically, these are regular numbers like 1, 2, 3...etc converted to hexadecimal since that is how OS X understands it. Let's break it down.

 

Zero means the number 0. So when the brightness lever is all the way to the left, the screen is black.

 

:excl: Just like before, there are commas "," after each hexadecimal. This means that after that number, the brightness lever executes the next level until you reach the number that does not have a comma. This is where the the maximum brightness is reached. There can only be 17 levels of brightness.

 

For OS X to read our next brightness levels after zero, we need to add "0x0" to every number converted to hexadecimal.

 

0x012C means the number 300.

0x0258 means the number 600.

0x0384 means the number 900.

0x04B0 means the number 1200.

0x05DC means the number 1500.

0x0708 means the number 1800.

0x0834 means the number 2100.

0x0960 means the number 2400.

0x0AC8 means the number 2700.

0x0BB8 means the number 3000.

0x0CE4 means the number 3300.

0x0E10 means the number 3600.

0x0F3C means the number 3900.

0x010CC means the number 4200.

0x01194 means the number 4500.

0x012C0 means the number 4800.

 

So why did I choose to use a pattern of 300 for my brightness levels? The reason is because I found out this pattern was the best choice for my internal LCD. When I move the brightness level all the way to the right, 4800 is the maximum brightness level I can use. If the last brightness level was 4900 or 5000, it won't do anything since 4800 was the maximum.

 

Basically you have to play around with these numbers. Every internal LCD is different. By using the pattern of 300, I reach 4800 and all my 17 levels of brightness have a value. Every time I move the brightness lever, it increases or decreases the backlight by 300.

 

How did I convert my numbers to hexadecimal? I used a website called Statman.info.

 

http://www.statman.i...exadecimal.html

 

post-620531-0-41393000-1365985499_thumb.png

 

Enter your regular number in the convert box. Press "to hexadecimal" and you'll get your number in hexadecimal.

 

Let's go back to something I skipped to explain. Remember this code in the beginning of the PNLF before the 17 brightness levels?

 

Method (_BCL, 0, NotSerialized)
	 {
		 Return (Package (0x13)
		 {
0x012C0, (Level brightness when computer boots up with AC adapter connected.)
0x0384, (Level brightness when computer boots up with battery.)

 

I changed the first hexadecimal code so I can explain it better. As you can see, the first hexadecimal is the level that is used when you have your computer connected to an AC adapter and the same level when you boot up your computer when connected to an AC power source. The second hexadecimal is the level that is used when your computer is using the battery and the same level when you boot up your computer with battery.

 

In other words, your brightness level will reset itself everytime you boot. If you want a specific brightness level everytime you boot to OS X, you need to set it here.

 

Under construction.

  • Like 1
Link to comment
Share on other sites

 Share

×
×
  • Create New...