Battery in Dell Inspiron 14z

[FoxBuru]

Try the laptop patch repo here: https://github.com/RehabMan/Laptop-DSDT-Patch

Then apply both "HD4000 Low Resolution" and "Brightness fix" patches. Save the changes to /Extra/dsdt.aml to try.

Or maybe you already have that in your DSDT? (ig-platform-id = 0166003)

That patch was already on my DSDT. Also the Brightness Fix.

Also you could try adding setting Graphics Mode in your /Extra/org.chameleon.Boot.plist:

	<key>Graphics Mode</key>
	<string>1366x768x32</string>

Added that, but no changes =< Keeps crashing loginwindow.

And, more screenshots with -v

Any idea RehabMan?

Cheers :3

 

[RehabMan]

Any idea RehabMan?

Cheers :3

Instead of doing combo update for 10.8.5, go directly there from initial install. Download fresh from Mac App Store, recreate Unibeast USB, fresh install...

Hold off on patched AppleHDA, and remove the USB Wifi.

And when you get a chance, extract your native DSDT from Linux (see: https://github.com/RehabMan/HP-ProBook-4x30s-DSDT-Patch/wiki/How-to-patch-your-DSDT). Post both the one you're using and the one from Linux.

 

[FoxBuru]

Ok, i'll generate the usb on a few minutes ^^

And, here are the DSDT's

Cheers ^^

P.S: I also have this tables available on Linux. Do you need another one, apart from DSDT?

 

[RehabMan]

Ok, i'll generate the usb on a few minutes ^^

And, here are the DSDT's

Cheers ^^

P.S: I also have this tables available on Linux. Do you need another one, apart from DSDT?

Was it necessary to change the device-id of the LPC to 0x1e44? I've not seen that done before on Ivy/series 7 boards. I know we don't do it on the 7-series ProBook 4x40s. I don't have any Ivy computer, so I could just be unaware of why you'd do that...

The _PLD patch used is incorrect (probably doesn't matter). Corrrect patch is at my laptop repo: "Fix _PLD Buffer/Package Error."

Maybe you could do the DPOF call in _SB.PCI0.IGPU._REG (inside the GINI=0 conditional)?

 

[RehabMan]

Was it necessary to change the device-id of the LPC to 0x1e44? I've not seen that done before on Ivy/series 7 boards. I know we don't do it on the 7-series ProBook 4x40s. I don't have any Ivy computer, so I could just be unaware of why you'd do that...

Or even if you really do want to do this (to get a different config for AppleLPC than would be normal, or to force AppleLPC to load if it is not), on 10.8.5, you need something additional. You need to also inject "name":

                Method (_DSM, 4, NotSerialized)
                {
                    Store (Package (0x04)
                        {
                            "name", "pci8086,1e44",
                            "device-id", 
                            Buffer (0x04)
                            {
                                0x44, 0x1E, 0x00, 0x00
                            }
                        }, Local0)
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                    Return (Local0)
                }

 

[FoxBuru]

Instead of doing combo update for 10.8.5, go directly there from initial install. Download fresh from Mac App Store, recreate Unibeast USB, fresh install...

Ok, i've recreated the USB using latest Unibeast and re-downloaded from App Store. But, now i don't even manage to get the installer working =(

Some screenshots on the specific point that Laptop crashes:

 

[RehabMan]

Ok, i've recreated the USB using latest Unibeast and re-downloaded from App Store. But, now i don't even manage to get the installer working =(

Some screenshots on the specific point that Laptop crashes:

Looks like a graphics problem.

What flags are you using to boot. You will probably need GraphicsEnabler=No -x -v

Perhaps it has been a while since the last fresh install and you didn't write down what you need to get into the OS X installer? Time to reach back into those memory banks...

Deleting AMD/ATI/Radeon kexts is another thing possible. Same goes for the Intel graphics kexts...

 

[FoxBuru]

Looks like a graphics problem.

What flags are you using to boot. You will probably need GraphicsEnabler=No -x -v

Perhaps it has been a while since the last fresh install and you didn't write down what you need to get into the OS X installer? Time to reach back into those memory banks...

Deleting AMD/ATI/Radeon kexts is another thing possible. Same goes for the Intel graphics kexts...

Ok, i had to install using "-x -v -F GraphicsEnabler=No IGPEnabler=Yes IGPlatformID=01660003". I'm also booting with that args right now the installed 10.8.5

But, it's kinda curious... In the installer, if i used all those flags except "-x", the installer loaded Graphics, but remained stucked on the Gray Background, so no Installer window was really displayed.

Should I proceed patching DSDT? What patches should i Apply? I was applying Patches from two of this Repos (snapshot attached).

Patches applied:

PJALM =>
- Add MCHC
- SATA
- SMBUS
- LPC

Rehabman =>
- IGPU/LVDS Single Link

Sourceforge =>
- Remove WMI

Toleda =>
- UEFI-Clean Compile

I didn't patched to get AppleHDA until i get a working configuration using normal mode boot. Also, i was thinking about patching the PEGP to an unknown device so OS X don't load Kexts for that. It would be advisable to do that, or to just remove AMD/ATI Kexts?

Cheers, and thanks for the help RehabMan :3

 

[RehabMan]

Ok, i had to install using "-x -v -F GraphicsEnabler=No IGPEnabler=Yes IGPlatformID=01660003". I'm also booting with that args right now the installed 10.8.5

But, it's kinda curious... In the installer, if i used all those flags except "-x", the installer loaded Graphics, but remained stucked on the Gray Background, so no Installer window was really displayed.

I'm not sure what -F does (is it another spelling for '-f'?). Oh... I looked it up -F is "ignore Kernel Flags in org.chameleon.Boot.plist," and since in a normal boot.plist for Unibeast there are no kernel flags there, it does nothing.

It is kind of strange that you had to use safe mode. Also, I would have thought "GraphicsEnabler=Yes IGPlatformID=01660003" would have been the same result as "GraphicsEnabler=No IGPEnabler=Yes IGPlatformID=01660003". But I don't have an Ivy-based laptop, so haven't been able to experiment. Safe mode must be keeping something else from loading while the system is still a little wrong.

Nice to know that the IGPlatformID can help get to the installer now as well though...

Should I proceed patching DSDT? What patches should i Apply? I was applying Patches from two of this Repos (snapshot attached).

Patches applied:

PJALM =>
- Add MCHC
- SATA
- SMBUS
- LPC

Rehabman =>
- IGPU/LVDS Single Link

Sourceforge =>
- Remove WMI

Toleda =>
- UEFI-Clean Compile

I would not apply a DSDT patch until it is obvious that you need it. I think the LPC patch is dangerous. As far as I know the native ID on 7-series mobile boards is already recognized by the system, so why change the ID to a different one. Seems just wrong and dangerous to me.

I don't know what the MCHC device does. I don't have it here on either my desktop or laptop. Find out what it is. I guess I could try it here and see what gets loaded for it in ioreg. For SATA, I don't see the point either, the native device is recognized as is proof in the fact you were able to install.

Definitely you need IGPU/LVDS single link, but it is also the same as using IGPlatformID=01660003.

As far as Toleda "clean compile." Only use it if there is something in there that you need. If you already have a clean compile, then why use it. As far as I can tell, the only error you have in your native DSDT is the _PLD buffer/package problem, which is available on my repo: https://github.com/RehabMan/Laptop-DSDT-Patch

Removing WMI is an optimization and is not necessary. Save it for after you have things working.

I didn't patched to get AppleHDA until i get a working configuration using normal mode boot.

Sounds like a plan.

Also, i was thinking about patching the PEGP to an unknown device so OS X don't load Kexts for that. It would be advisable to do that, or to just remove AMD/ATI Kexts?

You probably could do something like that, but if it isn't getting in the way, I wouldn't worry about it. What you really want to do (eventually) is turn it off, so it doesn't consume power (if you think it is...)

 

[RehabMan]

I don't know what the MCHC device does. I don't have it here on either my desktop or laptop. Find out what it is. I guess I could try it here and see what gets loaded for it in ioreg.

FYI: I added MCHC to my desktop DSDT and rebooted. A kext AppleSMCPDRC attached to it. I don't know what it does or whether it does any good, but it is there. It didn't crash me (so far), but I'm been surviving just fine for a year without it...