Contribute
Register

Battery in Dell Inspiron 14z

Status
Not open for further replies.
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.

Yep, it seemed kind of dangerous for me too. This time i didn't patched LPC (As I've seen that IOReg loads LPC correctly)

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.

MCHC it seems it refers to Intel DRAM Controller. I supposed it was a good thing to make OS X recognize that.

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

I've actually changed a bit some things. I decided to patch with IGPU/LVDS single link and don't use auto-inject from the IGPlatformID.

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

Yep, i've also applied that _PLD patch for the config i'm using now.

Also, I've patched my PEGP to persuade OS X to load KExts for that card. I'm using this snippet:

Code:
Method (_DSM, 4, NotSerialized)
                    {
                        Store (Package (0x06)
                            {
                                "name", 
                                "pci0,0", 
                                "device-id", 
                                Buffer (0x04)
                                {
                                    0x00, 0x00, 0x00, 0x00
                                }, 

                                "vendor-id", 
                                Buffer (0x04)
                                {
                                    0x00, 0x00, 0x00, 0x00
                                }
                            }, Local0)
                        DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                        Return (Local0)
                    }

With that, looking at IOReg, it doesn't load more the AMD Kexts. So, i guess its working as i expected.

Apart from that, i'm just renaming GFX0 to IGPU and adding MCHC, SMBus Patch, and DGTP. Nothing more at the moment. Ah yes, and i've generated the SSDT using the ssdtPRGen.sh from https://raw.github.com/Piker-Alpha/RevoBoot/clang/i386/libsaio/acpi/Tools/ssdtPRGen.sh

(I've modified the part of my processor, an i7-3517U, because it didn't had the correct low-freq mode at 800MHz)
Code:
i7-3517U,17,800,1900,3000,2,4

Also, i've patched AppleIntelCPUPowerManagement.kext to jump the restriction on locked bios. And i have, right now, a very different result from the one of the last time on 10.8.5. This time, loginwindowd don't crashes, but system get stucked on AppleACPIPlatformExpert, and then start logging that vtd error that i don't really know what means.

Code:
Oct  8 13:27:02 localhost configd[16]: InterfaceNamer: timed out waiting for IOKit to quiesce
Oct  8 13:27:02 localhost configd[16]: Busy services :
Oct  8 13:27:02 localhost configd[16]:   MacBookAir5,2 [1, 73288 ms]
Oct  8 13:27:02 localhost configd[16]:   MacBookAir5,2/AppleACPIPlatformExpert [2, 52327 ms]
Oct  8 13:27:02 localhost configd[16]:   MacBookAir5,2/AppleACPIPlatformExpert/CPU0@0 [1, 51989 ms]
Oct  8 13:27:02 localhost configd[16]:   MacBookAir5,2/AppleACPIPlatformExpert/CPU0@0/AppleACPICPU [1, 51961 ms]
Oct  8 13:27:02 localhost configd[16]:   MacBookAir5,2/AppleACPIPlatformExpert/PCI0@0 [1, 52285 ms]
Oct  8 13:27:02 localhost configd[16]:   MacBookAir5,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI [1, 52266 ms]
Oct  8 13:27:02 localhost configd[16]:   MacBookAir5,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/MCHC@0 [1, 51962 ms]
Oct  8 13:27:40 localhost warmd[28]: [warmctl_evt_timer_bc_activation_timeout:286] BC activation bcstop timer fired!
Oct  8 13:27:55 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd1e000
Oct  8 13:27:57 --- last message repeated 1 time ---
Oct  8 13:27:57 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd1f000
Oct  8 13:28:00 --- last message repeated 2 times ---
Oct  8 13:28:00 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd20000
Oct  8 13:28:02 --- last message repeated 2 times ---
Oct  8 13:28:02 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:03 --- last message repeated 89 times ---
Oct  8 13:28:03 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd21000
Oct  8 13:28:03 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:04 --- last message repeated 98 times ---
Oct  8 13:28:04 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd21000
Oct  8 13:28:04 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:05 --- last message repeated 90 times ---
Oct  8 13:28:05 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd22000
Oct  8 13:28:05 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:06 --- last message repeated 90 times ---
Oct  8 13:28:06 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd22000
Oct  8 13:28:06 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:07 --- last message repeated 97 times ---
Oct  8 13:28:07 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd22000
Oct  8 13:28:07 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:08 --- last message repeated 89 times ---
Oct  8 13:28:08 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd23000
Oct  8 13:28:08 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:09 --- last message repeated 90 times ---
Oct  8 13:28:09 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd23000
Oct  8 13:28:09 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:10 --- last message repeated 96 times ---
Oct  8 13:28:10 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd23000
Oct  8 13:28:10 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:11 --- last message repeated 90 times ---
Oct  8 13:28:11 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd24000
Oct  8 13:28:11 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:12 --- last message repeated 89 times ---
Oct  8 13:28:12 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd24000
Oct  8 13:28:12 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:13 --- last message repeated 97 times ---
Oct  8 13:28:13 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd25000
Oct  8 13:28:13 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:14 --- last message repeated 89 times ---
Oct  8 13:28:14 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd25000
Oct  8 13:28:14 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:15 --- last message repeated 90 times ---
Oct  8 13:28:15 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd25000
Oct  8 13:28:15 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:16 --- last message repeated 97 times ---
Oct  8 13:28:16 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd26000
Oct  8 13:28:16 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:17 --- last message repeated 89 times ---
Oct  8 13:28:17 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd26000
Oct  8 13:28:17 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:18 --- last message repeated 90 times ---
Oct  8 13:28:18 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd26000
Oct  8 13:28:18 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:19 --- last message repeated 96 times ---
Oct  8 13:28:19 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd27000
Oct  8 13:28:19 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:20 --- last message repeated 90 times ---
Oct  8 13:28:20 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd27000
Oct  8 13:28:20 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:21 --- last message repeated 89 times ---
Oct  8 13:28:21 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd28000
Oct  8 13:28:21 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:22 --- last message repeated 97 times ---
Oct  8 13:28:22 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd28000
Oct  8 13:28:22 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:23 --- last message repeated 89 times ---
Oct  8 13:28:23 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd28000
Oct  8 13:28:23 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:24 --- last message repeated 90 times ---
Oct  8 13:28:24 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd29000
Oct  8 13:28:24 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:25 --- last message repeated 97 times ---
Oct  8 13:28:25 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd29000
Oct  8 13:28:25 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000

It seems like a small progress to me, but i'm still trapped in that error. Any suggestion RehabMan?

Cheers ^^
 
Yep, it seemed kind of dangerous for me too. This time i didn't patched LPC (As I've seen that IOReg loads LPC correctly)



MCHC it seems it refers to Intel DRAM Controller. I supposed it was a good thing to make OS X recognize that.

I wonder what is bad about not having it load? I'll probably try it on my Probook too. Just to see what happens...

I've actually changed a bit some things. I decided to patch with IGPU/LVDS single link and don't use auto-inject from the IGPlatformID.

I prefer the DSDT patch as well...

Yep, i've also applied that _PLD patch for the config i'm using now.

Also, I've patched my PEGP to persuade OS X to load KExts for that card. I'm using this snippet:

Code:
Method (_DSM, 4, NotSerialized)
                    {
                        Store (Package (0x06)
                            {
                                "name", 
                                "pci0,0", 
                                "device-id", 
                                Buffer (0x04)
                                {
                                    0x00, 0x00, 0x00, 0x00
                                }, 

                                "vendor-id", 
                                Buffer (0x04)
                                {
                                    0x00, 0x00, 0x00, 0x00
                                }
                            }, Local0)
                        DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                        Return (Local0)
                    }

With that, looking at IOReg, it doesn't load more the AMD Kexts. So, i guess its working as i expected.

Cool. I always wondered if that would work...

Apart from that, i'm just renaming GFX0 to IGPU and adding MCHC, SMBus Patch, and DGTP. Nothing more at the moment. Ah yes, and i've generated the SSDT using the ssdtPRGen.sh from https://raw.github.com/Piker-Alpha/RevoBoot/clang/i386/libsaio/acpi/Tools/ssdtPRGen.sh

(I've modified the part of my processor, an i7-3517U, because it didn't had the correct low-freq mode at 800MHz)
Code:
i7-3517U,17,800,1900,3000,2,4

You should probably verify that your CPU can go to 800 as LFM. Search for Pike's AppleIntelCPUPowerManagementInfo.kext. Not all Ivy Bridge mobile CPUs can go to x8. Some only x12.

Also, i've patched AppleIntelCPUPowerManagement.kext to jump the restriction on locked bios. And i have, right now, a very different result from the one of the last time on 10.8.5. This time, loginwindowd don't crashes, but system get stucked on AppleACPIPlatformExpert, and then start logging that vtd error that i don't really know what means.

Code:
Oct  8 13:27:02 localhost configd[16]: InterfaceNamer: timed out waiting for IOKit to quiesce
Oct  8 13:27:02 localhost configd[16]: Busy services :
Oct  8 13:27:02 localhost configd[16]:   MacBookAir5,2 [1, 73288 ms]
Oct  8 13:27:02 localhost configd[16]:   MacBookAir5,2/AppleACPIPlatformExpert [2, 52327 ms]
Oct  8 13:27:02 localhost configd[16]:   MacBookAir5,2/AppleACPIPlatformExpert/CPU0@0 [1, 51989 ms]
Oct  8 13:27:02 localhost configd[16]:   MacBookAir5,2/AppleACPIPlatformExpert/CPU0@0/AppleACPICPU [1, 51961 ms]
Oct  8 13:27:02 localhost configd[16]:   MacBookAir5,2/AppleACPIPlatformExpert/PCI0@0 [1, 52285 ms]
Oct  8 13:27:02 localhost configd[16]:   MacBookAir5,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI [1, 52266 ms]
Oct  8 13:27:02 localhost configd[16]:   MacBookAir5,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/MCHC@0 [1, 51962 ms]
Oct  8 13:27:40 localhost warmd[28]: [warmctl_evt_timer_bc_activation_timeout:286] BC activation bcstop timer fired!
Oct  8 13:27:55 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd1e000
Oct  8 13:27:57 --- last message repeated 1 time ---
Oct  8 13:27:57 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd1f000
Oct  8 13:28:00 --- last message repeated 2 times ---
Oct  8 13:28:00 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd20000
Oct  8 13:28:02 --- last message repeated 2 times ---
Oct  8 13:28:02 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:03 --- last message repeated 89 times ---
Oct  8 13:28:03 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd21000
Oct  8 13:28:03 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:04 --- last message repeated 98 times ---
Oct  8 13:28:04 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd21000
Oct  8 13:28:04 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:05 --- last message repeated 90 times ---
Oct  8 13:28:05 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd22000
Oct  8 13:28:05 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:06 --- last message repeated 90 times ---
Oct  8 13:28:06 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd22000
Oct  8 13:28:06 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:07 --- last message repeated 97 times ---
Oct  8 13:28:07 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd22000
Oct  8 13:28:07 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:08 --- last message repeated 89 times ---
Oct  8 13:28:08 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd23000
Oct  8 13:28:08 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:09 --- last message repeated 90 times ---
Oct  8 13:28:09 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd23000
Oct  8 13:28:09 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:10 --- last message repeated 96 times ---
Oct  8 13:28:10 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd23000
Oct  8 13:28:10 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:11 --- last message repeated 90 times ---
Oct  8 13:28:11 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd24000
Oct  8 13:28:11 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:12 --- last message repeated 89 times ---
Oct  8 13:28:12 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd24000
Oct  8 13:28:12 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:13 --- last message repeated 97 times ---
Oct  8 13:28:13 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd25000
Oct  8 13:28:13 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:14 --- last message repeated 89 times ---
Oct  8 13:28:14 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd25000
Oct  8 13:28:14 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:15 --- last message repeated 90 times ---
Oct  8 13:28:15 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd25000
Oct  8 13:28:15 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:16 --- last message repeated 97 times ---
Oct  8 13:28:16 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd26000
Oct  8 13:28:16 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:17 --- last message repeated 89 times ---
Oct  8 13:28:17 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd26000
Oct  8 13:28:17 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:18 --- last message repeated 90 times ---
Oct  8 13:28:18 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd26000
Oct  8 13:28:18 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:19 --- last message repeated 96 times ---
Oct  8 13:28:19 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd27000
Oct  8 13:28:19 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:20 --- last message repeated 90 times ---
Oct  8 13:28:20 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd27000
Oct  8 13:28:20 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:21 --- last message repeated 89 times ---
Oct  8 13:28:21 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd28000
Oct  8 13:28:21 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:22 --- last message repeated 97 times ---
Oct  8 13:28:22 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd28000
Oct  8 13:28:22 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:23 --- last message repeated 89 times ---
Oct  8 13:28:23 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd28000
Oct  8 13:28:23 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:24 --- last message repeated 90 times ---
Oct  8 13:28:24 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd29000
Oct  8 13:28:24 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000
Oct  8 13:28:25 --- last message repeated 97 times ---
Oct  8 13:28:25 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x5 W:0xbcd29000
Oct  8 13:28:25 localhost kernel[0]: vtd[0] fault: device 9:0:0 reason 0x6 R:0xbcd1a000

It seems like a small progress to me, but i'm still trapped in that error. Any suggestion RehabMan?

I wonder if the 'vtd[0]' has something to do with VT-d capability of the CPU? Can you disable VT-d in BIOS? If not, my understanding is you must boot with dart=0 (which I believe is a kernel flag).
 
You should probably verify that your CPU can go to 800 as LFM. Search for Pike's AppleIntelCPUPowerManagementInfo.kext. Not all Ivy Bridge mobile CPUs can go to x8. Some only x12.

I've unset the SSDT.aml and set the DropSSDT to No. And this is the output of the Kext:

Code:
Oct  8 20:02:51 localhost kernel[0]: Low Frequency Mode : 800 MHz
Oct  8 20:02:51 localhost kernel[0]: Clock Speed        : 1900 MHz
Oct  8 20:02:51 localhost kernel[0]: Max Turbo Frequency: 3000 MHz
...
...
Oct  8 20:02:51 localhost kernel[0]: AICPUPMI: CPU P-States [ 19 ]
Oct  8 20:02:51 localhost kernel[0]: AICPUPMI: CPU P-States [ 8 19 ]

I wonder if the 'vtd[0]' has something to do with VT-d capability of the CPU? Can you disable VT-d in BIOS? If not, my understanding is you must boot with dart=0 (which I believe is a kernel flag).

I've set that flag, and the vtd error disappeared. But i'm still stuck on the IOKit hangup.
Code:
Oct  8 20:03:52 localhost configd[16]: Busy services :
Oct  8 20:03:52 localhost configd[16]:   MacBookAir5,2 [1, 72854 ms]
Oct  8 20:03:52 localhost configd[16]:   MacBookAir5,2/AppleACPIPlatformExpert [2, 52777 ms]
Oct  8 20:03:52 localhost configd[16]:   MacBookAir5,2/AppleACPIPlatformExpert/CPU0@0 [1, 52176 ms]
Oct  8 20:03:52 localhost configd[16]:   MacBookAir5,2/AppleACPIPlatformExpert/CPU0@0/AppleACPICPU [1, 52145 ms]
Oct  8 20:03:52 localhost configd[16]:   MacBookAir5,2/AppleACPIPlatformExpert/PCI0@0 [1, 52731 ms]
Oct  8 20:03:52 localhost configd[16]:   MacBookAir5,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI [1, 52720 ms]
Oct  8 20:03:52 localhost configd[16]:   MacBookAir5,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/MCHC@0 [1, 52154 ms]
Oct  8 20:04:30 localhost warmd[28]: [warmctl_evt_timer_bc_activation_timeout:286] BC activation bcstop timer fired!

I don't know what could be causing this hangup, but i'll keep an eye on this... It seems the last error to boot on normal mode without error.

------

Update: I think PM is working now :D I've used the SSDT from
Code:
http://www.tonymacx86.com/ssdt/86906-ssdt-generation-script-ivybridge-pm-49.html#post655176
and now DCPIManager show me more states than before :D I had to boot adding -f as kernel argument. For some reason, doing it without it, it just don't loads.


Cheers :3
 
Hi Foxburu,

I was reading the whole topic and was wondering if you were successful in disabling the AMD 7500 video by DSDT. I have a similar notebook as you and I am looking for a way to disable it to reduce temperature and to increase battery life. I tried the command \_SB.PCI0.PEG0.PEGP.DPOF () as you had mentioned before but didn't work for me. Maybe I am setting it in the wrong place. If it works for you can you gave me a hint on how to setup it on DSDT ?

Thanks
 
Status
Not open for further replies.
Back
Top