Davirus Posted May 31, 2011 Share Posted May 31, 2011 Hi everybody. I usually don't like to make this kind of questions since I try to do everything manually and by myself (its a good way to learn). But I can`t do this anymore. Always I boot my system after deleting the NullCPUPowerManagement.kext I always get a kernel panic related to HPET and wrong CPU configurations. I patched my DSDT as many people around the forum and as the DSDTSE.app suggest to fix this problem, but the problem still happening. I have done everything (or at least, everything I can do) to my DSDT to fix all problems, but I can`t find a way to fix the HPET error. This is my HPET code inside the DSDT.aml Device (HPET) { Name (_HID, EisaId ("PNP0103")) Name (_CID, EisaId ("PNP0C01")) Name (BUF0, ResourceTemplate () { IRQNoFlags () {0} IRQNoFlags () {8} Memory32Fixed (ReadOnly, 0xFED00000, // Address Base 0x00000400, // Address Length ) }) Method (_STA, 0, NotSerialized) { If (LGreaterEqual (OSID (), 0x10)) { If (HPAE) { Return (0x0F) } } Return (Zero) } Method (_CRS, 0, NotSerialized) { Return (BUF0) } } If someone may checkout my dsdt.aml to see if there is something Im doing wrong, I will be greatly thankful. [ DOWNLOAD : DSDT.AML ] Thanks in advance. Link to comment Share on other sites More sharing options...
MaLd0n Posted May 31, 2011 Share Posted May 31, 2011 Try it dsdt.HPET.zip Link to comment Share on other sites More sharing options...
Davirus Posted May 31, 2011 Author Share Posted May 31, 2011 Try itdsdt.HPET.zip Im on it. I will post results (yes, Im going do it) later, since I don't have the mediums right now to fix the problem in case the DSDT your provide me don't fix the HPET problem. Thanks for the quick response :3 Link to comment Share on other sites More sharing options...
Gringo Vermelho Posted May 31, 2011 Share Posted May 31, 2011 You can type DSDT=nameofdsdt.aml at the bootprompt to test-drive a different DSDT. Link to comment Share on other sites More sharing options...
LatinMcG Posted June 1, 2011 Share Posted June 1, 2011 ForceHPET=Yes in boot might help ? Link to comment Share on other sites More sharing options...
Davirus Posted June 2, 2011 Author Share Posted June 2, 2011 Try itdsdt.HPET.zip I was trying about everything this days. Using your DSDT makes things a few different, it does not trigger the panic but makes my computer stay on "waiting for root device" and It do not go through that. You can type DSDT=nameofdsdt.aml at the bootprompt to test-drive a different DSDT. Thanks, I almost forgot I can do that, It was very helpful :3 Link to comment Share on other sites More sharing options...
MaLd0n Posted June 2, 2011 Share Posted June 2, 2011 I was trying about everything this days.Using your DSDT makes things a few different, it does not trigger the panic but makes my computer stay on "waiting for root device" and It do not go through that. the HPET was edited That's another problem Link to comment Share on other sites More sharing options...
Davirus Posted June 2, 2011 Author Share Posted June 2, 2011 ForceHPET=Yes in boot might help ? Nope, it didn't worked. I tried using that code in the boot.plist with and without the DSDT (both, mine and the patched by "MaLd0n"). the HPET was edited That's another problem Yup, but only happens when using the dsdt.aml you provide me, when I switch to mine I got the kernel panic again. the HPET was edited That's another problem btw, this is the exactly problem Im getting when I use your dsdt.aml USBF: 0.429 AppleUSBUHCI: Unable to initialize UIM Still waiting for root device. Still waiting for root device. Still waiting for root device. ... Link to comment Share on other sites More sharing options...
MaLd0n Posted June 2, 2011 Share Posted June 2, 2011 btw, this is the exactly problem Im getting when I use your dsdt.aml USBF: 0.429 AppleUSBUHCI: Unable to initialize UIM Still waiting for root device. Still waiting for root device. Still waiting for root device. ... send me complete files http://www.insanelymac.com/forum/index.php...st&id=81816 Link to comment Share on other sites More sharing options...
Davirus Posted June 2, 2011 Author Share Posted June 2, 2011 send me complete fileshttp://www.insanelymac.com/forum/index.php...st&id=81816 Here it is: http://www.cl.ly/3J27062h391s401Q1y2T In a extra note, my BIOS do not have any HPET configuration or LegacyUSB options. Link to comment Share on other sites More sharing options...
MaLd0n Posted June 2, 2011 Share Posted June 2, 2011 Here it is:http://www.cl.ly/3J27062h391s401Q1y2T In a extra note, my BIOS do not have any HPET configuration or LegacyUSB options. try it dsdt.Davirus.zip Chameleon USB fix USBBusFix=Yes Link to comment Share on other sites More sharing options...
Davirus Posted June 2, 2011 Author Share Posted June 2, 2011 try itdsdt.Davirus.zip Chameleon USB fix USBBusFix=Yes Nope, when using that dsdt.aml it give me a kernel panic while booting (No HPETs available...). The panic occurs whenever using the USBbus fix or not. In other notes, I was able to skip the "waiting for root device" using the first dsdt.aml your provide me using PCIroot=0 but it works randomly. Yet, using any of those bootloaders shows me an error about LPC, but I have my LPC patched (LPC, RTC and HPET). This is a total mystery to me. Link to comment Share on other sites More sharing options...
MaLd0n Posted June 2, 2011 Share Posted June 2, 2011 Yet, using any of those bootloaders shows me an error about LPC, but I have my LPC patched (LPC, RTC and HPET). the old problem in DELL laptop(many models) does not generate CST anyone found a solution to this look it for example http://www.insanelymac.com/forum/index.php?showtopic=237750 USB UHCI Method (_DSM, 4, NotSerialized) { Store (Package (0x0D) { "AAPL,clock-id", Buffer (One) { 0x01 }, "built-in", Buffer (One) { 0x00 }, "device_type", Buffer (0x05) { "UHCI" }, "AAPL,current-available", 0x04B0, "AAPL,current-extra", 0x02BC, "AAPL,current-in-sleep", 0x03E8, Buffer (One) { 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } EHCI Method (_DSM, 4, NotSerialized) { Store (Package (0x0D) { "AAPL,clock-id", Buffer (One) { 0x0A }, "built-in", Buffer (One) { 0x00 }, "device_type", Buffer (0x05) { "EHCI" }, "AAPL,current-available", 0x04B0, "AAPL,current-extra", 0x02BC, "AAPL,current-in-sleep", 0x03E8, Buffer (One) { 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } Link to comment Share on other sites More sharing options...
Davirus Posted June 2, 2011 Author Share Posted June 2, 2011 the old problem in DELL laptop(many models)does not generate CST anyone found a solution to this look it for example http://www.insanelymac.com/forum/index.php?showtopic=237750 Checking it out. By the way, I don't know why the heck I said "bootloader" (I wanted to mean "dsdts"). Link to comment Share on other sites More sharing options...
MaLd0n Posted June 2, 2011 Share Posted June 2, 2011 I forgot HPET dsdt.02.zip Link to comment Share on other sites More sharing options...
LatinMcG Posted June 3, 2011 Share Posted June 3, 2011 maldon. i was thinking maybe they need OSID changed from Windows 2006 to Darwin ? Link to comment Share on other sites More sharing options...
MaLd0n Posted June 3, 2011 Share Posted June 3, 2011 maldon. i was thinking maybe they need OSID changed from Windows 2006 to Darwin ? I think he should use the DSDT + fix USB(Chameleon RC5) Link to comment Share on other sites More sharing options...
Davirus Posted June 5, 2011 Author Share Posted June 5, 2011 I think he should use the DSDT + fix USB(Chameleon RC5) Ok, I have some good new (kinda). Using the first dsdt.aml you patched, the native Apple CPU Management kext is working, no more HPET errors. The USB problem looks its triggered using "arch=i386" on the boot.plist, so it seems that booting on 64bits kernel is the solution... i guess. The "waiting for root device" looks fixed by removing the "pci device = 1" or something like that (the code is automatically inserted on the boot.plist using myHack). I can confirm that removing the "arch=i386" on the boot.plist seems fixing almost everything I mentioned before, and all the USB ports are working. But the performance looks a bit little, uhmm... choppy. The effects looks like lagging and all the system looks like glitch or something. If I disable the multiprocessor feature on the bios solve this glitch thing, but obviously using 1 core is not a clever idea and Im not sure if speed steep works using only 1 core. Link to comment Share on other sites More sharing options...
Recommended Posts