Jump to content

ooptimum

Members
  • Posts

    7
  • Joined

  • Last visited

Everything posted by ooptimum

  1. Frankly, even though I am quite skilled in computers per se (25+ years of hands-on experience) and particularly in unices, I am a newbie in OS X and have yet no idea how to install OS X on a PC without help of third-party tools like unishit, MyHack etc., since I have to deal with MBR partitioning scheme on this particular notebook. Btw, are you trying to convince me that user-space apps could affect kernel during its booting? If I get you right, you're not questioning the fact that /S/L/E should be brand new after upgrade.
  2. Why? I suppose /S/L/E should be brand new. UPD. Sorry, I was wrong about appleintelcpupowermanagement.kext. It wasn't patched. I confused it with IOAHCIBlockStorage.kext. My bad... So, when I patched it with this patch, it didn't help and then I started to play with clover.
  3. Hello, Thank you for your support! If I upgrade my ML to 10.8.3 can we consider it clean install?
  4. The patch told me that my appleintelcpupowermanagement.kext is patched already, and it had, in fact, been a surprise to me, as I believed that my /S/L/E was untouched. I guess either unishit or multishit is responsible for that. <== This is wrong, my memory faulted me. So, the patched kext doesn't work either. Then I thought klover could solve the issue. However, neither klover's autopatching facility (AsusAICPUPM=true) nor autogenerating of C- and P-states were helpful (I've tried the very last version of clover available today - v2k r2165). Then I've been told to try this patch, but there is no patch for ML 10.8, it's solely for 10.8.3, so I am going to upgrade my ML to 10.8.3. If it wouldn't help, what else should I try?
  5. Thank you for your effort, artur-pt, but unfortunately, it doesn't work out as it was intended. Kernel still falls in panic during boot. There should be something else, which involves need in research, apart of auto-patching. Anyways, could you tell me which particular patches you've used in this case? I'd like not to bother you and be able to reproduce these steps myself whenever it would be necessary.
  6. Hello, I guess you won't compare them, as there are huge pile of cosmetic changes (0x00 -> Zero, 0x01 -> One, etc.), but if you ask, here it is. DSDT-as-in-BIOS.zip
  7. Recently I have installed vanilla OS X 10.8 (12A269) on my ASUS U24E notebook (i7-2620M, HD3000, 4GB RAM) using unishit method. The bootloader is Chimera v2.2.0 r2248 (I'm not happy with it, but that's different story). The essential minimum of extra kexts allowing usage of the system is: AppleACPIPS2Nub.kext, ApplePS2Controller.kext, FakeSMC.kext, GenericUSBXHCI.kext and NullCPUPowerManagement.kext. In order to eliminate dependence on NullCPUPowerManagement.kext I've patched all timers in DSDT: Device (HPET) { Name (_HID, EisaId ("PNP0103")) Name (_CID, EisaId ("PNP0C01")) Name (_UID, Zero) Name (BUF0, ResourceTemplate () { IRQNoFlags () {0} IRQNoFlags () {8} Memory32Fixed (ReadWrite, 0xFED00000, // Address Base 0x00000400, // Address Length ) }) Method (_STA, 0, NotSerialized) { Return (0x0F) } Method (_CRS, 0, Serialized) { Return (BUF0) } } Device (RTC) { Name (_HID, EisaId ("PNP0B00")) Name (_CRS, ResourceTemplate () { IO (Decode16, 0x0070, // Range Minimum 0x0070, // Range Maximum One, // Alignment /* Fix - RTC fix 0x08, // Length */ 0x02, // Length ) /* Fix - RTC fix IRQNoFlags () {8} */ }) } Device (TIMR) { Name (_HID, EisaId ("PNP0100")) Name (_CRS, ResourceTemplate () { IO (Decode16, 0x0040, // Range Minimum 0x0040, // Range Maximum One, // Alignment 0x04, // Length ) IO (Decode16, 0x0050, // Range Minimum 0x0050, // Range Maximum 0x10, // Alignment 0x04, // Length ) /* Fix - TIMR fix IRQNoFlags () {0} */ }) However, the kernel is panicing if I remove NullCPUPowerManagement.kext. What else could affect it? DSDT.dsl.zip
×
×
  • Create New...