Jump to content
  • Announcements

    • Allan

      Forum Rules   04/13/2018

      Hello folks! As some things are being fixed, we'll keep you updated. Per hour the Forum Rules don't have a dedicated "Tab", so here is the place that we have our Rules back. New Users Lounge > [READ] - InsanelyMac Forum Rules - The InsanelyMac Staff Team. 
buoo

Patched mach_kernel 10.8.X for Atom CPUs

72 posts in this topic

Recommended Posts

@theconnactic

 

Same here on asrock atom ion 330 pro it gets stuck at pci configuration begins even if i set "npci=2000".... i've also tried other ways to get past that screen but without success (with snow 10.6.8 it works perfectly)...

Share this post


Link to post
Share on other sites

Did you try npci=0x3000 also? It works sometimes.

 

Please report back anyway! Is important for us to know if the solution worked or not. :)

 

Ok, i've tried also npci=0x3000... nothing.... it always get stuck at this point:

 

 

post-449896-0-81978800-1346004828_thumb.jpg

 

 

If it helps i've attached my E/E on the usb installation pendrive for troubleshooting (chameleon version is the latest one available in the official thread as today)

Cheers

 

 

Extra.zip

Share this post


Link to post
Share on other sites

Which method did you use to install Mountain Lion?

 

Did you try to boot without the dsdt.aml?

 

Maybe this solution works: http://netkas.org/?p=1053

 

Ok, i've tried with the patched iopcifamily.kext .... and it goes forward from the previous error, but now it stucks few lines down... (see screenshot)...

post-449896-0-56764400-1346014896_thumb.jpg

Share this post


Link to post
Share on other sites

I've tried to ovverride DSDT GFX injection with graphicenabler=yes ... nothing... it stucks always at the same point... it seems that my htpc doesn't like ML :|

What makes me disappointed is the fact that in Snow it works without a glitch! ok... i know that there are so many variables... but...

Share this post


Link to post
Share on other sites

That's easy, a MacBook Air 11'!

 

Just kidding: i would opt for an Asus 1201n, because of it's ability to get QE/CI enabled, since it has nVidia Ion graphics. Until now, we couldn't solve this issue for Intel GMA graphics in Mountain Lion. Anyway, it depends on your needs, expectations and budget.

Share this post


Link to post
Share on other sites

Doesn't seem to work too well with the Dev release of 10.8.2. The kernel patches but the machine refuses to boot with it. Tried the patcher, tried patching manually by running the perl strings in Terminal but same result. Using the 10.8.1 Atom kernel with the update causes a KP.

Share this post


Link to post
Share on other sites

Doesn't seem to work too well with the Dev release of 10.8.2.

 

I'm surprised it even worked on the 12.1.0 kernel, the addresses that need to be patched usually change.... which is probably what happened with the 12.2.0 kernel.

Share this post


Link to post
Share on other sites

Anyway, even for vanilla hacks, this update seems a little tricky (see the other topic).

 

Sorry if the question (or the one who asks) sounds inept , but probably there will be changes between the dev. 10.8.2 and the final end-user 10.8.2 update, right?

Share this post


Link to post
Share on other sites

I'm surprised it even worked on the 12.1.0 kernel, the addresses that need to be patched usually change.... which is probably what happened with the 12.2.0 kernel.

 

Ah. So this Atom patcher is a bit pointless, then? Pity. Would have been a neat solution without having to bug those that understand kernel development better to come up with an updated kernel for each point release.

Share this post


Link to post
Share on other sites

Sorry if the question (or the one who asks) sounds inept , but probably there will be changes between the dev. 10.8.2 and the final end-user 10.8.2 update, right?

 

 

no doubt ! Apple can release many beta builds before the final public release, so many changes or not :) ! Some times, Apple modify many things, and some times, not so !

 

 

 

I'm surprised it even worked on the 12.1.0 kernel, the addresses that need to be patched usually change.... which is probably what happened with the 12.2.0 kernel.

 

 

in the 10.8.1 beta builds (12B13, 12B17, 12B19), the addresses don't changed.... but in this first 10.8.2, clearly yes !

 

in the 12B13, we had the same 12.0.0 kernel, he changed to 12.1.0 in the 12B17 and stay the same in the 12B19 !

Share this post


Link to post
Share on other sites

Ah. So this Atom patcher is a bit pointless, then? Pity. Would have been a neat solution without having to bug those that understand kernel development better to come up with an updated kernel for each point release.

 

It's not pointless at all (well, this one might be), in fact I have a kernel patcher that goes and reads the correct addresses + patches everything appropriately (it's the same codebase as the KernelPatcher module for chameleon)

Share this post


Link to post
Share on other sites

It's not pointless at all (well, this one might be), in fact I have a kernel patcher that goes and reads the correct addresses + patches everything appropriately (it's the same codebase as the KernelPatcher module for chameleon)

 

Yes, I meant the script shared here. I know you have your own private patcher as nawcom mentioned on his blog.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Posts

    • I have put it into clover drivers 64uefi folder on Yosemite thru High Sierra which allows me to edit my High Sierra disk if needed in Yosemite system.   There is no functionality of apfs in other versions but it does allow other clover bootloaders and systems to recognize the HS apfs drive or open it for inspection.   If you don’t have it you can’t see your HS drive or access it in another macOS version.
    • Hi! Is it possible to get codec AD1981 running with AppleHDA on HP Compaq 8710w? It works nicely with VoodooHDA. Speakers and HP are switching automatically.  Internal and HP mic also work - no switching in SysPref but it works when mic is plugged in and internal mic works when hp mic is unplugged.   It has same weird pathmap - connected directly:  Playback: nid=5 [pin: Speaker (Analog)] | + <- nid=3 [audio output] [src: pcm] bindSeq=00008001 nid=6 [pin: Headphones (Grey Left)] | + <- nid=3 [audio output] [src: pcm] bindSeq=00008001   But inputs are really weird. There are 5 nodes from input to HP mic/Internal mic nid=4 [audio input] | + <- nid=21 [audio selector] [src: mix] bindSeq=00000003 | + <- nid=12 [audio mixer] [src: mix] bindSeq=00000003 | + <- nid=30 [audio selector] [src: mic] bindSeq=00000001 | + <- nid=8 [pin: Microphone (Grey Left)] [src: mic] bindSeq=00000001 + <- nid=31 [audio selector] [src: monitor] bindSeq=00000002 | + <- nid=24 [pin: Microphone (Analog)] [src: monitor] bindSeq=00000002 Can pathmap like that even work with AppleHDA? What codec should I patch? I tried patches from AD1984 but no luck.    These are manually patched verbs: 00571c10 00571d01 00571e17 00571f90 00570C02 00671c20 00671d10 00671e21 00671f03 00771cf0 00771d00 00771e00 00771f40 00871c30 00871d10 00871e81 00871f03 00971cf0 00971d00 00971e00 00971f40 00a71cf0 00a71d00 00a71e00 00a71f40 01671cf0 01671d00 01671e00 01671f40 01771cf0 01771d00 01771e00 01771f40 01871c40 01871d01 01871ea0 01871f90 01971cf0 01971d00 01971e00 01971f40   Codecgraph and linux codecdump attached. Thx for any help or suggestions.              codec.txt 2.svg codec.txt
    •   Yes, 'cause APFS log is coming before clover boot screen.
    • and you suspect apfs on before clover issues  
    • Can someone help me? I have an HP PRODESK 400 G4
      Corei5 7500
      4GB
      video card AMD R5 230 Caicos 6450 I can not put the video card to work on High Sierra. Can you tell me which kext to use? I discovered the id of my board through this link >>https://github.com/Clover-EFI-Bootloader/clover/blob/master/rEFIt_UEFI/Platform/ati.c


×