Jump to content

syscl

Coders
  • Content Count

    290
  • Joined

  • Last visited

  • Days Won

    9

Reputation Activity

  1. Like
    syscl reacted to Slice in Clover Problems and Solutions   
    DarwinDumper do this.
  2. Like
    syscl got a reaction from gujiangjiang in Clover Problems and Solutions   
    @Slice, 
    sorry, the compile fail... How to print out the &gEfiSmbiosTableGuid 's content?
     
    Thanks,
    syscl
  3. Like
    syscl got a reaction from gujiangjiang in [GUIDE] Fix Skylake HDMI/DP Output   
    Well it's been a while I search to fix the issue below

    Note, there's no HDMI / DisplayPort Output in the screenshot above, even though you correct the port 0105, port 0204, port 0306 in AppleIntelSKLGraphicsFramebuffer.kext correctly.
     
     
    The problem lies in the AppleHDA(assume you are familiar with the basic concept to patch the AppleHDA and you already have a working AppleHDA), then what we have to do is the following
    Uncompress the layoutXXX.xml.zlib Open layoutXXX.xml you just uncompress Add PublishHDMI_DP as a Boolean type in Root/PathMapRef, value is True, like the below picture
    Save and compress the file back to layoutXXX.xml.zlib Copy to the place resource/ under your dummyHDA Reboot to see change  
    As a proof, please see the screenshot below

     
    Note: if you cite my work, please don't forget to add credit to syscl/me, since it took me time to figure out the solution. Thus your credit will make me feel my work do help others! Thank you!
     
    ​Good luck,
    syscl
  4. Like
    syscl reacted to RehabMan in Clover Problems and Solutions   
    The bug (wherever it is) only happens on certain (relatively new) Dell computers/laptops.
     
    I did a little google search and found an example (there are many such examples).
     
    See here: https://www.tonymacx86.com/threads/bcm94350zae-14e4-43a3-not-working-in-10-11.188509/page-2#post-1226888
     
    You can see in config.plist/SMBIOS the full name MacBookPro12,1, but in ioreg MacBookPro1.
  5. Like
    syscl got a reaction from Allan in [FIX] enable lid wake from sleep for Skylake Iris Graphics   
    Hola, I just got my own XPS 13 9350 with Iris 540 graphic card, and soon found out that I cannot light my lid up when resume from sleep, finally, I found out the solution. 
     
    Edited 2016-12-09:
    Now I found out the secret is the 0A -> 0F fixed the sleep issue(no more 2 stage patches), thus refine patch
    Comment: Enable lid wake for 0x19260004 credit syscl/lighting/Yating Zhou Kext: AppleIntelSKLGraphicsFramebuffer Find: 0A0B0300 00070600 03000000 04000000 Replace: 0F0B0300 00070600 03000000 04000000 Through Clover config.plist:
    <dict> <key>Comment</key> <string>Enable lid wake for 0x19260004 credit syscl/lighting/Yating Zhou</string> <key>Disabled</key> <false/> <key>Find</key> <data> CgsDAAAHBgADAAAABAAAAA== </data> <key>Name</key> <string>AppleIntelSKLGraphicsFramebuffer</string> <key>Replace</key> <data> DwsDAAAHBgADAAAABAAAAA== </data> </dict> That's it.
     
    For 0x19260002(Iris 540/550) , applied the following patch
    Comment: Enable lid wake for 0x19260002 credit syscl/lighting/Yating Zhou Kext: AppleIntelSKLGraphicsFramebuffer Find: 0A130300 00000600 00000000 00000000 Replace: 0F130300 00000600 00000000 00000000 For 0x193b0005(Iris P580), applied the following patch
    Comment: Enable lid wake for 0x193b0005(Iris P580) credit syscl/lighting/Yating Zhou Kext: AppleIntelSKLGraphicsFramebuffer Find: 0A130300 00000600 00000000 00000000 Replace: 0F130300 00000600 00000000 00000000   ////
     
    Below contents (posted at 11/15/2016) is no more needed since I refined/removed unnecessary patches!
    Apply the following patches I developer in Clover to enable lid wake for Iris 540/550 Comment: Enable lid wake for 0x19260004 #1 of 2 credit syscl/lighting/Yating Zhou Kext: AppleIntelSKLGraphicsFramebuffer Find: 0A0B0300 00070600 03000000 04000000 Replace: 0F090000 00000000 00000000 00000000 and
    Comment: Enable lid wake for 0x19260004 #2 of 2 credit syscl/lighting/Yating Zhou Kext: AppleIntelSKLGraphicsFramebuffer Find: 50EE1A00 00000000 00EF1A00 00000000 Replace: 50EE1A00 00000000 B0EE1A00 00000000 Through Clover config.plist:
    <dict> <key>Comment</key> <string>Enable lid wake for 0x19260004 #1 of 2 credit syscl/lighting/Yating Zhou</string> <key>Disabled</key> <false/> <key>Find</key> <data> CgsDAAAHBgADAAAABAAAAA== </data> <key>Name</key> <string>AppleIntelSKLGraphicsFramebuffer</string> <key>Replace</key> <data> DwkAAAAAAAAAAAAAAAAAAA== </data> </dict> <dict> <key>Comment</key> <string>Enable lid wake for 0x19260004 #2 of 2 credit syscl/lighting/Yating Zhou</string> <key>Disabled</key> <false/> <key>Find</key> <data> UO4aAAAAAAAA7xoAAAAAAA== </data> <key>Name</key> <string>AppleIntelSKLGraphicsFramebuffer</string> <key>Replace</key> <data> UO4aAAAAAACw7hoAAAAAAA== </data> </dict> Set ig-platform-id = 0x1926004 GFX0 -> IGPU through DSDT hot patch Comment: GFX0 -> IGPU Find: 47465830 Replace: 49475055 Through config.plist:
    <dict> <key>Comment</key> <string>GFX0 -> IGPU</string> <key>Disabled</key> <false/> <key>Find</key> <data> R0ZYMA== </data> <key>Replace</key> <data> SUdQVQ== </data> </dict> Rebuild kernel cache by the following under Sierra sudo rm -rf /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache sudo rm -rf /System/Library/PrelinkedKernels/prelinkedkernel sudo touch /Library/Extensions && sudo touch /System/Library/Extensions && sudo kextcache -u / Reboot to enjoy the laptop sleep  
    syscl
  6. Like
    syscl got a reaction from Allan in [FIX] enable lid wake from sleep for Skylake Iris Graphics   
    Hola, I just got my own XPS 13 9350 with Iris 540 graphic card, and soon found out that I cannot light my lid up when resume from sleep, finally, I found out the solution. 
     
    Edited 2016-12-09:
    Now I found out the secret is the 0A -> 0F fixed the sleep issue(no more 2 stage patches), thus refine patch
    Comment: Enable lid wake for 0x19260004 credit syscl/lighting/Yating Zhou Kext: AppleIntelSKLGraphicsFramebuffer Find: 0A0B0300 00070600 03000000 04000000 Replace: 0F0B0300 00070600 03000000 04000000 Through Clover config.plist:
    <dict> <key>Comment</key> <string>Enable lid wake for 0x19260004 credit syscl/lighting/Yating Zhou</string> <key>Disabled</key> <false/> <key>Find</key> <data> CgsDAAAHBgADAAAABAAAAA== </data> <key>Name</key> <string>AppleIntelSKLGraphicsFramebuffer</string> <key>Replace</key> <data> DwsDAAAHBgADAAAABAAAAA== </data> </dict> That's it.
     
    For 0x19260002(Iris 540/550) , applied the following patch
    Comment: Enable lid wake for 0x19260002 credit syscl/lighting/Yating Zhou Kext: AppleIntelSKLGraphicsFramebuffer Find: 0A130300 00000600 00000000 00000000 Replace: 0F130300 00000600 00000000 00000000 For 0x193b0005(Iris P580), applied the following patch
    Comment: Enable lid wake for 0x193b0005(Iris P580) credit syscl/lighting/Yating Zhou Kext: AppleIntelSKLGraphicsFramebuffer Find: 0A130300 00000600 00000000 00000000 Replace: 0F130300 00000600 00000000 00000000   ////
     
    Below contents (posted at 11/15/2016) is no more needed since I refined/removed unnecessary patches!
    Apply the following patches I developer in Clover to enable lid wake for Iris 540/550 Comment: Enable lid wake for 0x19260004 #1 of 2 credit syscl/lighting/Yating Zhou Kext: AppleIntelSKLGraphicsFramebuffer Find: 0A0B0300 00070600 03000000 04000000 Replace: 0F090000 00000000 00000000 00000000 and
    Comment: Enable lid wake for 0x19260004 #2 of 2 credit syscl/lighting/Yating Zhou Kext: AppleIntelSKLGraphicsFramebuffer Find: 50EE1A00 00000000 00EF1A00 00000000 Replace: 50EE1A00 00000000 B0EE1A00 00000000 Through Clover config.plist:
    <dict> <key>Comment</key> <string>Enable lid wake for 0x19260004 #1 of 2 credit syscl/lighting/Yating Zhou</string> <key>Disabled</key> <false/> <key>Find</key> <data> CgsDAAAHBgADAAAABAAAAA== </data> <key>Name</key> <string>AppleIntelSKLGraphicsFramebuffer</string> <key>Replace</key> <data> DwkAAAAAAAAAAAAAAAAAAA== </data> </dict> <dict> <key>Comment</key> <string>Enable lid wake for 0x19260004 #2 of 2 credit syscl/lighting/Yating Zhou</string> <key>Disabled</key> <false/> <key>Find</key> <data> UO4aAAAAAAAA7xoAAAAAAA== </data> <key>Name</key> <string>AppleIntelSKLGraphicsFramebuffer</string> <key>Replace</key> <data> UO4aAAAAAACw7hoAAAAAAA== </data> </dict> Set ig-platform-id = 0x1926004 GFX0 -> IGPU through DSDT hot patch Comment: GFX0 -> IGPU Find: 47465830 Replace: 49475055 Through config.plist:
    <dict> <key>Comment</key> <string>GFX0 -> IGPU</string> <key>Disabled</key> <false/> <key>Find</key> <data> R0ZYMA== </data> <key>Replace</key> <data> SUdQVQ== </data> </dict> Rebuild kernel cache by the following under Sierra sudo rm -rf /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache sudo rm -rf /System/Library/PrelinkedKernels/prelinkedkernel sudo touch /Library/Extensions && sudo touch /System/Library/Extensions && sudo kextcache -u / Reboot to enjoy the laptop sleep  
    syscl
  7. Like
    syscl got a reaction from Allan in [FIX] enable lid wake from sleep for Skylake Iris Graphics   
    Hola, I just got my own XPS 13 9350 with Iris 540 graphic card, and soon found out that I cannot light my lid up when resume from sleep, finally, I found out the solution. 
     
    Edited 2016-12-09:
    Now I found out the secret is the 0A -> 0F fixed the sleep issue(no more 2 stage patches), thus refine patch
    Comment: Enable lid wake for 0x19260004 credit syscl/lighting/Yating Zhou Kext: AppleIntelSKLGraphicsFramebuffer Find: 0A0B0300 00070600 03000000 04000000 Replace: 0F0B0300 00070600 03000000 04000000 Through Clover config.plist:
    <dict> <key>Comment</key> <string>Enable lid wake for 0x19260004 credit syscl/lighting/Yating Zhou</string> <key>Disabled</key> <false/> <key>Find</key> <data> CgsDAAAHBgADAAAABAAAAA== </data> <key>Name</key> <string>AppleIntelSKLGraphicsFramebuffer</string> <key>Replace</key> <data> DwsDAAAHBgADAAAABAAAAA== </data> </dict> That's it.
     
    For 0x19260002(Iris 540/550) , applied the following patch
    Comment: Enable lid wake for 0x19260002 credit syscl/lighting/Yating Zhou Kext: AppleIntelSKLGraphicsFramebuffer Find: 0A130300 00000600 00000000 00000000 Replace: 0F130300 00000600 00000000 00000000 For 0x193b0005(Iris P580), applied the following patch
    Comment: Enable lid wake for 0x193b0005(Iris P580) credit syscl/lighting/Yating Zhou Kext: AppleIntelSKLGraphicsFramebuffer Find: 0A130300 00000600 00000000 00000000 Replace: 0F130300 00000600 00000000 00000000   ////
     
    Below contents (posted at 11/15/2016) is no more needed since I refined/removed unnecessary patches!
    Apply the following patches I developer in Clover to enable lid wake for Iris 540/550 Comment: Enable lid wake for 0x19260004 #1 of 2 credit syscl/lighting/Yating Zhou Kext: AppleIntelSKLGraphicsFramebuffer Find: 0A0B0300 00070600 03000000 04000000 Replace: 0F090000 00000000 00000000 00000000 and
    Comment: Enable lid wake for 0x19260004 #2 of 2 credit syscl/lighting/Yating Zhou Kext: AppleIntelSKLGraphicsFramebuffer Find: 50EE1A00 00000000 00EF1A00 00000000 Replace: 50EE1A00 00000000 B0EE1A00 00000000 Through Clover config.plist:
    <dict> <key>Comment</key> <string>Enable lid wake for 0x19260004 #1 of 2 credit syscl/lighting/Yating Zhou</string> <key>Disabled</key> <false/> <key>Find</key> <data> CgsDAAAHBgADAAAABAAAAA== </data> <key>Name</key> <string>AppleIntelSKLGraphicsFramebuffer</string> <key>Replace</key> <data> DwkAAAAAAAAAAAAAAAAAAA== </data> </dict> <dict> <key>Comment</key> <string>Enable lid wake for 0x19260004 #2 of 2 credit syscl/lighting/Yating Zhou</string> <key>Disabled</key> <false/> <key>Find</key> <data> UO4aAAAAAAAA7xoAAAAAAA== </data> <key>Name</key> <string>AppleIntelSKLGraphicsFramebuffer</string> <key>Replace</key> <data> UO4aAAAAAACw7hoAAAAAAA== </data> </dict> Set ig-platform-id = 0x1926004 GFX0 -> IGPU through DSDT hot patch Comment: GFX0 -> IGPU Find: 47465830 Replace: 49475055 Through config.plist:
    <dict> <key>Comment</key> <string>GFX0 -> IGPU</string> <key>Disabled</key> <false/> <key>Find</key> <data> R0ZYMA== </data> <key>Replace</key> <data> SUdQVQ== </data> </dict> Rebuild kernel cache by the following under Sierra sudo rm -rf /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache sudo rm -rf /System/Library/PrelinkedKernels/prelinkedkernel sudo touch /Library/Extensions && sudo touch /System/Library/Extensions && sudo kextcache -u / Reboot to enjoy the laptop sleep  
    syscl
  8. Like
    syscl got a reaction from pbryanw in [Guide] Fix issue of "Disk not ejected properly"   
    Overview
    On OS X/Mac OS X, some people may suffer from the issue that the external disk was not ejected properly after sleep. This problem dates back to the period of the coming of Mavericks, even on a real Mac!

     
     
    Overview of the tools/solutions





    AFAIK, there's two solutions to fix this problem till now: 
    Install Jettison from Mac App Store. Use sleepwatcher to unmount the external devices before system go to sleep.
    But for me, install Jettison is not free of charge, and this application will place icon on the right corner of the statue bar once get installed, which is not a good solution from my point of view. 

    The latter one is open source and free of charge, which means I can know clearly what this application/daemon has done and add as many functions I want to it. With the help of sleepwatcher, there's various script to unmount/mount disk upon sleep, but none of it is so easy to read and some require sleep time delay settings, that's really strange! That's the reason why I started to create my "own" version of script to fix this issue. I optimized the whole progress as well as the installation progress. No more wake/sleep delay time settings! No more complicated command line, no more wake script, just one sleep script for unmount the external devices, once you resume from sleep, all the external devices will mount by system spontaneously. After following this guide step-by-step, no more "Disk not ejected properly" error will occur upon sleep. 
     
    Feel free to change whatever you want if you do not satisfy with my script: https://github.com/syscl/Fix-usb-sleep
     
    How to use?
    Download the latest fixUSB.sh by entering the following command in a terminal window: git clone https://github.com/syscl/Fix-usb-sleep Note: If it was the first you execute command "git", please install it by the tips from OS X online(Click "Install"), and then run the above command line again.
     
     
    This will download the fixUSB.sh to your current folder (./) and the next step is to change the permissions of the file(add +x) so that it can be run: chmod +x ~/Fix-usb-sleep/fixUSB.sh Run the fixUSB.sh in a terminal window by: cd ./Fix-usb-sleep ./fixusb.sh If all this procedures have done correctly, you will see the following message in the terminal window

    Hope you all enjoy this script and all feedbacks are welcome! Post issue on https://github.com/syscl/Fix-usb-sleep
     
    Credit:
    Bernhard Baehr (bernhard.baehr@gmx.de): without his great sleepwatcher, this project/script will not be created.
     
  9. Like
    syscl got a reaction from camillionario in [Guide] Fix issue of "Disk not ejected properly"   
    Recent update log
     
    2016-9-16
    Fixed an issue that will potentially mount external EFI partitions see issue #5 by @brousseau6933 Fixed typo: "${gFrom}/tools" --> "${gFrom}" 2016-7-16
    Switch to curl cmd instead of git clone cmd. 2016-5-26
    Mount points at wake to fix MacBook issue #2 .
  10. Like
    syscl reacted to Slice in VoodooHDA 2.9.2   
    CodecCommander is not needed for VoodooHDA. VH knows what to do.
     
    Your codec dump is from linux so I don't know what is happen in macOS. It will be better to see output from getdump utility in macOS.
    Anyway. If you want you can do the same sound as in Linux just making the same pinconfigs for all nodes as in Linux
    Node 0x12 0x90a60130
    Node 0x14 0x90170110
    Node 0x15 0x0321101f
    Node 0x16 0x40000000 - disabled
    Node 0x18 0x411111f0 - disabled
    Node 0x19 0x411111f0 - disabled
    Node 0x1a 0x411111f0 - disabled
    Node 0x1b  0x411111f0 - disabled
    Node 0x1d 0x40d6832d - wrong config
    Node 0x1e 0x411111f0 - disabled
    Node 0x1f 0x411111f0 - disabled
  11. Like
    syscl got a reaction from pbryanw in [Guide] Fix issue of "Disk not ejected properly"   
    Overview
    On OS X/Mac OS X, some people may suffer from the issue that the external disk was not ejected properly after sleep. This problem dates back to the period of the coming of Mavericks, even on a real Mac!

     
     
    Overview of the tools/solutions





    AFAIK, there's two solutions to fix this problem till now: 
    Install Jettison from Mac App Store. Use sleepwatcher to unmount the external devices before system go to sleep.
    But for me, install Jettison is not free of charge, and this application will place icon on the right corner of the statue bar once get installed, which is not a good solution from my point of view. 

    The latter one is open source and free of charge, which means I can know clearly what this application/daemon has done and add as many functions I want to it. With the help of sleepwatcher, there's various script to unmount/mount disk upon sleep, but none of it is so easy to read and some require sleep time delay settings, that's really strange! That's the reason why I started to create my "own" version of script to fix this issue. I optimized the whole progress as well as the installation progress. No more wake/sleep delay time settings! No more complicated command line, no more wake script, just one sleep script for unmount the external devices, once you resume from sleep, all the external devices will mount by system spontaneously. After following this guide step-by-step, no more "Disk not ejected properly" error will occur upon sleep. 
     
    Feel free to change whatever you want if you do not satisfy with my script: https://github.com/syscl/Fix-usb-sleep
     
    How to use?
    Download the latest fixUSB.sh by entering the following command in a terminal window: git clone https://github.com/syscl/Fix-usb-sleep Note: If it was the first you execute command "git", please install it by the tips from OS X online(Click "Install"), and then run the above command line again.
     
     
    This will download the fixUSB.sh to your current folder (./) and the next step is to change the permissions of the file(add +x) so that it can be run: chmod +x ~/Fix-usb-sleep/fixUSB.sh Run the fixUSB.sh in a terminal window by: cd ./Fix-usb-sleep ./fixusb.sh If all this procedures have done correctly, you will see the following message in the terminal window

    Hope you all enjoy this script and all feedbacks are welcome! Post issue on https://github.com/syscl/Fix-usb-sleep
     
    Credit:
    Bernhard Baehr (bernhard.baehr@gmx.de): without his great sleepwatcher, this project/script will not be created.
     
  12. Like
    syscl got a reaction from pbryanw in [Guide] Fix issue of "Disk not ejected properly"   
    Overview
    On OS X/Mac OS X, some people may suffer from the issue that the external disk was not ejected properly after sleep. This problem dates back to the period of the coming of Mavericks, even on a real Mac!

     
     
    Overview of the tools/solutions





    AFAIK, there's two solutions to fix this problem till now: 
    Install Jettison from Mac App Store. Use sleepwatcher to unmount the external devices before system go to sleep.
    But for me, install Jettison is not free of charge, and this application will place icon on the right corner of the statue bar once get installed, which is not a good solution from my point of view. 

    The latter one is open source and free of charge, which means I can know clearly what this application/daemon has done and add as many functions I want to it. With the help of sleepwatcher, there's various script to unmount/mount disk upon sleep, but none of it is so easy to read and some require sleep time delay settings, that's really strange! That's the reason why I started to create my "own" version of script to fix this issue. I optimized the whole progress as well as the installation progress. No more wake/sleep delay time settings! No more complicated command line, no more wake script, just one sleep script for unmount the external devices, once you resume from sleep, all the external devices will mount by system spontaneously. After following this guide step-by-step, no more "Disk not ejected properly" error will occur upon sleep. 
     
    Feel free to change whatever you want if you do not satisfy with my script: https://github.com/syscl/Fix-usb-sleep
     
    How to use?
    Download the latest fixUSB.sh by entering the following command in a terminal window: git clone https://github.com/syscl/Fix-usb-sleep Note: If it was the first you execute command "git", please install it by the tips from OS X online(Click "Install"), and then run the above command line again.
     
     
    This will download the fixUSB.sh to your current folder (./) and the next step is to change the permissions of the file(add +x) so that it can be run: chmod +x ~/Fix-usb-sleep/fixUSB.sh Run the fixUSB.sh in a terminal window by: cd ./Fix-usb-sleep ./fixusb.sh If all this procedures have done correctly, you will see the following message in the terminal window

    Hope you all enjoy this script and all feedbacks are welcome! Post issue on https://github.com/syscl/Fix-usb-sleep
     
    Credit:
    Bernhard Baehr (bernhard.baehr@gmx.de): without his great sleepwatcher, this project/script will not be created.
     
  13. Like
    syscl got a reaction from vandroiy2012 in How to: Intel Pentium G3XXX and Celeron G1XXX (Haswell) works with speedstep Yosemite 10.10 and Mavericks 10.9   
    Hello @vandroiy2012, I've tried to patch the mach_kernel for enabling XCPM, but sadly it does not work. So I have to dig out it from other ways.
     
    Till now the best we can achieve is to remove both AppleIntelCPUPowerManagement.kext, AppleIntelCPUPowerManagementClient.kext and NullCPUPowerManagement.kext once we finish installed Sierra.
     
    The support of XCPM on IvyBridge has since removed, so with the FakeCPUID=0x0306A0, system treats Haswell Pentium/Celeron as a IvyBridge model then calls for AppleIntelCPUPowerManagement::init(), which will cause kernel panic at booting stage. Things get worse on Sierra, because both AppleIntelCPUPowerManagement and XCPM cannot enable Pentium/Celeron P-State/C-State. 
     
    So people may think by easily replacing 83f83a with 83f83c can solve such issue to enable XCPM, but this issue is much deeper than we might think. I assume maybe we can patch mach_kernel in some place to bypass the kernel panic directly instead of faking CPUID to IvyBridge which is not enough/suitable for Haswell Pentium/Celeron.
     
    syscl 
  14. Like
    syscl got a reaction from vandroiy2012 in How to: Intel Pentium G3XXX and Celeron G1XXX (Haswell) works with speedstep Yosemite 10.10 and Mavericks 10.9   
    Hello @vandroiy2012, I've tried to patch the mach_kernel for enabling XCPM, but sadly it does not work. So I have to dig out it from other ways.
     
    Till now the best we can achieve is to remove both AppleIntelCPUPowerManagement.kext, AppleIntelCPUPowerManagementClient.kext and NullCPUPowerManagement.kext once we finish installed Sierra.
     
    The support of XCPM on IvyBridge has since removed, so with the FakeCPUID=0x0306A0, system treats Haswell Pentium/Celeron as a IvyBridge model then calls for AppleIntelCPUPowerManagement::init(), which will cause kernel panic at booting stage. Things get worse on Sierra, because both AppleIntelCPUPowerManagement and XCPM cannot enable Pentium/Celeron P-State/C-State. 
     
    So people may think by easily replacing 83f83a with 83f83c can solve such issue to enable XCPM, but this issue is much deeper than we might think. I assume maybe we can patch mach_kernel in some place to bypass the kernel panic directly instead of faking CPUID to IvyBridge which is not enough/suitable for Haswell Pentium/Celeron.
     
    syscl 
  15. Like
    syscl got a reaction from Blaggah in How to: Intel Pentium G3XXX and Celeron G1XXX (Haswell) works with speedstep Yosemite 10.10 and Mavericks 10.9   
    Hi @vandroiy2012 and @all, finally back to home and sit down to have a look at G1840 on Sierra. I wanna say, Haswell Celeron and Pentium on Sierra is OK

     
    Here's my solution:
    1. Use Clover r3650
    2. FakeCPUID = 0x0306A0
    3. Vanilla Sierra installation disk(public beta 16A238m) [Maybe unrelated, I haven't tested other Sierra version]
    4. Important: Place NullCPUPowerManagement.kext under Clover/kexts/Other, or place it directly into /S*/L*/E* to prevent kernel panic
    5. Vanilla/untouched mach_kernel.
     
    I've tested it successfully on my G1840, here's my specification and configuration files:
    Motherboard: MSI H87M-G43
    CPU: Celeron G1840
    Graphics: Dell GT630 with UEFI vBios
    CLOVER.zip
     
    P.S. Next step, I will find out the binary patch for AppleIntelCPUPowerManagement on Sierra, which is the main reason that causes the kernel panic on Haswell Pentium and Celeron. If this can be completed, we can no more use NullCPUPowerManagement.
     
    Wishes you can enjoy Sierra on Celeron and Pentium soon!
    syscl
  16. Like
    syscl got a reaction from Blaggah in How to: Intel Pentium G3XXX and Celeron G1XXX (Haswell) works with speedstep Yosemite 10.10 and Mavericks 10.9   
    Hi @vandroiy2012 and @all, finally back to home and sit down to have a look at G1840 on Sierra. I wanna say, Haswell Celeron and Pentium on Sierra is OK

     
    Here's my solution:
    1. Use Clover r3650
    2. FakeCPUID = 0x0306A0
    3. Vanilla Sierra installation disk(public beta 16A238m) [Maybe unrelated, I haven't tested other Sierra version]
    4. Important: Place NullCPUPowerManagement.kext under Clover/kexts/Other, or place it directly into /S*/L*/E* to prevent kernel panic
    5. Vanilla/untouched mach_kernel.
     
    I've tested it successfully on my G1840, here's my specification and configuration files:
    Motherboard: MSI H87M-G43
    CPU: Celeron G1840
    Graphics: Dell GT630 with UEFI vBios
    CLOVER.zip
     
    P.S. Next step, I will find out the binary patch for AppleIntelCPUPowerManagement on Sierra, which is the main reason that causes the kernel panic on Haswell Pentium and Celeron. If this can be completed, we can no more use NullCPUPowerManagement.
     
    Wishes you can enjoy Sierra on Celeron and Pentium soon!
    syscl
  17. Like
    syscl got a reaction from Blaggah in How to: Intel Pentium G3XXX and Celeron G1XXX (Haswell) works with speedstep Yosemite 10.10 and Mavericks 10.9   
    Hi @vandroiy2012 and @all, finally back to home and sit down to have a look at G1840 on Sierra. I wanna say, Haswell Celeron and Pentium on Sierra is OK

     
    Here's my solution:
    1. Use Clover r3650
    2. FakeCPUID = 0x0306A0
    3. Vanilla Sierra installation disk(public beta 16A238m) [Maybe unrelated, I haven't tested other Sierra version]
    4. Important: Place NullCPUPowerManagement.kext under Clover/kexts/Other, or place it directly into /S*/L*/E* to prevent kernel panic
    5. Vanilla/untouched mach_kernel.
     
    I've tested it successfully on my G1840, here's my specification and configuration files:
    Motherboard: MSI H87M-G43
    CPU: Celeron G1840
    Graphics: Dell GT630 with UEFI vBios
    CLOVER.zip
     
    P.S. Next step, I will find out the binary patch for AppleIntelCPUPowerManagement on Sierra, which is the main reason that causes the kernel panic on Haswell Pentium and Celeron. If this can be completed, we can no more use NullCPUPowerManagement.
     
    Wishes you can enjoy Sierra on Celeron and Pentium soon!
    syscl
  18. Like
    syscl got a reaction from Blaggah in How to: Intel Pentium G3XXX and Celeron G1XXX (Haswell) works with speedstep Yosemite 10.10 and Mavericks 10.9   
    Hi @vandroiy2012 and @all, finally back to home and sit down to have a look at G1840 on Sierra. I wanna say, Haswell Celeron and Pentium on Sierra is OK

     
    Here's my solution:
    1. Use Clover r3650
    2. FakeCPUID = 0x0306A0
    3. Vanilla Sierra installation disk(public beta 16A238m) [Maybe unrelated, I haven't tested other Sierra version]
    4. Important: Place NullCPUPowerManagement.kext under Clover/kexts/Other, or place it directly into /S*/L*/E* to prevent kernel panic
    5. Vanilla/untouched mach_kernel.
     
    I've tested it successfully on my G1840, here's my specification and configuration files:
    Motherboard: MSI H87M-G43
    CPU: Celeron G1840
    Graphics: Dell GT630 with UEFI vBios
    CLOVER.zip
     
    P.S. Next step, I will find out the binary patch for AppleIntelCPUPowerManagement on Sierra, which is the main reason that causes the kernel panic on Haswell Pentium and Celeron. If this can be completed, we can no more use NullCPUPowerManagement.
     
    Wishes you can enjoy Sierra on Celeron and Pentium soon!
    syscl
  19. Like
    syscl got a reaction from Huckleberry Pie in How to: Intel Pentium G3XXX and Celeron G1XXX (Haswell) works with speedstep Yosemite 10.10 and Mavericks 10.9   
    How to Make a Copy of IOReg (Note 1)
    1. IORegistryExplorer/File/Save a Copy As…. (no extension required)
    2. Open file to verify (Note 2)
    3. Attach to post (Note 3)
     
    Use IORegistryExplorer-SLRID_v10.6.3.
     
    syscl
  20. Like
    syscl got a reaction from vandroiy2012 in How to: Intel Pentium G3XXX and Celeron G1XXX (Haswell) works with speedstep Yosemite 10.10 and Mavericks 10.9   
    Weird, I saw same KP on macOS due to the lack of SSE4, but G18XX has SSE4. Will be back to my hometown and test on my G1840 next week or so.
    Can anyone lend me a Haswell Celeron PC now 
     
    syscl
    Please post at least verbose picture and ioreg, clover folder
     
    syscl
  21. Like
    syscl got a reaction from vandroiy2012 in How to: Intel Pentium G3XXX and Celeron G1XXX (Haswell) works with speedstep Yosemite 10.10 and Mavericks 10.9   
    Weird, I saw same KP on macOS due to the lack of SSE4, but G18XX has SSE4. Will be back to my hometown and test on my G1840 next week or so.
    Can anyone lend me a Haswell Celeron PC now 
     
    syscl
    Please post at least verbose picture and ioreg, clover folder
     
    syscl
  22. Like
    syscl got a reaction from Huckleberry Pie in How to: Intel Pentium G3XXX and Celeron G1XXX (Haswell) works with speedstep Yosemite 10.10 and Mavericks 10.9   
    Hi, @vandroiy2012, sorry for my late reply since I was busy doing my startup these days. 
    Now I'm back to my laptop, and dig into it. Let's do it;)
     
    Please try this one. I use a new method/way to fix that issue.
    kernel.zip
     
    Wait for your feedback!
    syscl
    Right argv. Note: you should add G3258 information first!
     
  23. Like
    syscl got a reaction from Huckleberry Pie in How to: Intel Pentium G3XXX and Celeron G1XXX (Haswell) works with speedstep Yosemite 10.10 and Mavericks 10.9   
    -c argv was replaced with -target. 
     
    Wrong CPU number, you have to add the right information for your processor. More details can be found in the conversations above.
     
    syscl
  24. Like
    syscl got a reaction from vandroiy2012 in How to: Intel Pentium G3XXX and Celeron G1XXX (Haswell) works with speedstep Yosemite 10.10 and Mavericks 10.9   
    Till now we've try 
    b6 c1 83 f8 3a --> b6 c1 83 f8 3a and
    40 04 83 f8 3a --> 40 04 83 f8 3c and replace all 83f83a with 83f83c, but all the three did not work. There's 39 83f83a(too many). To figure out those '83f83a', just type the following command line in terminal 
    hexdump -C [Your Kernel Loacation] then type in '83 f8 3a'.
     
    I will see it tomorrow to see if I can find more clues. Sorry for my late reply since I'm still busy with my startup.
     
    Best wishes
    syscl
  25. Like
    syscl got a reaction from vandroiy2012 in How to: Intel Pentium G3XXX and Celeron G1XXX (Haswell) works with speedstep Yosemite 10.10 and Mavericks 10.9   
    The method is the same as we did on 10.10.x and 10.11.x to make Haswell Pentium and Celeron work. That is fake cpu id to fool OS X think Haswell(0x0306C3) as IvyBridge(0x0306A0). Since the kernel patch does not work on macOS till now, we have to do the dirty patch in terminal. Sorry for my typo in #64, the correct one should be 
    sudo perl -pi -e 's|\x74\x11\x83\xF8\x3C|\x74\x11\x83\xF8\x0A|g' /System/Library/Kernels/kernel I mistyped it, sorry. 
     
    More details can be found here: http://www.insanelymac.com/forum/topic/301585-haswell-e-mach-kernel-patch-5960x-5830k-and-5820k-1010-10101-yosemite/
     
    It's better to use 10.11.x or older system to apply that patch in your Install USB, suppose your Install USB name install_osx, then apply the patch by typing
    sudo perl -pi -e 's|\x74\x11\x83\xF8\x3C|\x74\x11\x83\xF8\x0A|g' /Volumes/install_osx/System/Library/Kernels/kernel  Maybe I can patch that kernel for you(but I have no PCs to test, wait for your feedback)
     
    Still busy these day:(  But I want to thank you and vit9696, the AppleALC is invaluable and elegant kext to power AppleHDA up! Thanks!
     
    Best 
    syscl
×