osxfr33k

@onemanosx I agree with you about the offset except it doesn't work that way according to this example Rehabman told me I was wrong. My DSDT example Field (ECF2, ByteAcc, Lock, Preserve) { Offset (0x10), BDN0, 56, //0x10 Offset (0x18), BME0, 8, //0x18 Offset (0x20), BMNC, 8, //0x20 BMN0, 120, //0x21 BCT0, 128, //0x2F <<<< If I go by your way of calculating this should be 0x30 Offset (0x70), BCCL, 8, IDGS, 16, Offset (0x7E), The example you used on the first post looks like this is the way to calculate it. But from what I see you use 0x20 converted to (32) in decimal each time plus only the previous field bits divided by 8. Maybe it was pure coincidence it happed to work out that way in your example but it certainly does not work with my example above, unless Rehabman just happen to have a brain fart that day he replied to me? Rehabman's reply to me: Quote from Rehabman: Wrong. BCT0 is at offset 0x2f (0x20 + (120/8)). Edited: Rehabman must be wrong because if what he is saying is true in my DSDT example then the offset for BCT0 in his example would not be 0x30 but 0x2B. He must have replied to me in error what do you think?

I read this over and looked at the comparison of Clover versus OpenCore and Opencore does not support P states and C states so unless there is some elaborate way of creating a patch in the kernel section of Opencore or some SSDT which I don't think so then only Clover will work on Legacy Bios Devices. A google search shows no find for LGA 775 or specific older legacy motherboards with Opencore guides. Edited: I will stay with Clover for Legacy but the latest Clover after version r5126 or 5130 no longer uses older memory managers but I guess only concerned for UEFI but still uses OpenRunTime.efi do you have the latest clover.config configured for the later versions of clover or is Quirks settings just not needed for LGA 775? I also have a library of all your fantastic DSDT work from insanely many many years ago, are they still good as they are today for MacOS Catalina or need new patching or less patching, yes? I think I have all patches you made many years ago for almost all legacy Motherboards using MacIASL to load them these patches should still be good yes? Did you add anything new or remove anything old not needed? Thanks!

Can LGA 775 use OpenCore is there a guide for these desktops? Sorry never mind I see both Clover and Opencore EFI. Actually after looking it over I don't think opencore is for LGA 775 only Clover. There is no current opencore guide for LGA 775?

Is there an OpenCore Thread for LGA 775?

Maybe this processor is not supported in PRgen? Tried it and get an error unsupported. Looked over a bunch of CFG files and I don't see anything less than 2nd generation intel i7/i5/i3. I will see if adding this CPU to the CFG will help any but is that the only reason why for the error or os it possible PRgen was not coded to work with 1st generation CPU?

Is this method for CPU after first generation i7? I have a i7-920m CPU can I use this method for that CPU?

Actually not true for Nvidia only Laptop with Built in Intel disabled will not work without Rehabman's AppleBacklightFixup.kext. Anyhow good news. Problem solved sorry about all the noise above. It won't work in MacOS beta software so there is a bootflag to make it work '-applbklbeta'. But for the future just want to make sure the Nvidia Laptops that depend on this for backlight will still be supported and if AppleBacklightFixup.kext will no longer work in Future MAcOS then we need WEG to support exactly what AppleBacklightFIxup.kext does. If we can figure that out maybe a hotpatch in Clover? WEG Documentation does mention if some Injector is still needed to disable WEG Intel injector. From Wiki. applbkl=0 boot argument to disable AppleBacklight.kext patches for IGPU. In case of custom AppleBacklight profile needed as in my case.

How are you @MaLd0n, LCD brightness broke for me in Catalina working perfectly in Mojave. My laptop is ASus G750JX with Nvidia GTX770m native support in MacOS. The Integrated Intel GFX has been disabled by Asus a good thing for me. Attached is the send me files from Catalina. Do you you need the send me files from Mojave to? Edited: Forgot to mention and I have to have AppleBacklightFixup.kext for LCD brightness to work in Mojave so this is what is broken in Catalina. Is there a way to re-compile the AppleBacklightFixup.kext source in Catalina to work or is there way more to it than just re-compiling the source? Send me osxfr33ks-MBP.zip

Exactly what I am thinking to but something is going wrong and maybe that is why others have reported same issue unknown CPU then aborts. I stripped down your original cfg down to just one device took out everything left no spaces. Just left information above. Here is your file stripped down works perfect. So maybe a good idea to have your file in that DATA folder, because I kept downloading that DATA folder using a new User Defined.cfg and added the information exactly as the one I have attached just now and the one I modify from that DATA folder never works but the one you sent I can hack it to death and it works no matter what. See attached and thanks again! Edited: I think I know the possible problem something with the filename or the way the file was created. To prove this what I did is create an empty file in terminal with the touch command , then pasted all the contents of the file I attached in this post and ssdtPRGen runs fine and creates both the ssdt.dsl and ssdt.aml ACPI files. Edited Again: To compound this issue even more something really strange happens when I get a message unknown software and it aborts, I open the user cfg file up again using nano and it shows me an older cfg file not the current one as though somehow it was kept in buffer even though I exited nano cleanly so now I am thinking its something going on with nano in terminal under 10.14.4 causing these problems. I have to think about using a different editor maybe vi or an editor specific to cfg files, maybe a gui editor for MacOS. User Defined.cfg.zip

Well either way thanks for really helping me try to understand I thought the # just comments out anything so it won't think its part of the script I didn't realize you need the # before the close parenthesis ")" Ok One last time what is wrong with this file, I left 2 devices inside this file does not work either. User Defined.cfg.zip

Sorry I made another mistake again sent you the wrong file. Here is the one that is not working. User Defined.cfg.zip

Sorry here it is this one does not work maybe you can explain I cannot see anything wrong with it. User Defined.cfg.zip

I attached the wrong file I was testing my friends CPU check the new file I attached and let me know if you see anything wrong with it.

Wow thanks so much it worked!! NOw I Have to figure out why mine does not work I attached mine can you see what is wrong?

Yes added that exactly as you have and exactly as instructions say.

Yep followed the guide perfectly. Maybe for some reason which I cannot explain it’s not reading the Coffee Lake.cfg. I know it’s reading the User Defined.cfg because if I leave a couple spaces or something the CFG file should not contain it complains in the output showing such lines in cfg needs attending to. This happens when you don’t edit them in terminal with like nano or equivalent editor that will not change the format of the cfg. If I remove the Coffee Lake.cfg it doesn’t complain is why I suspect that for some reason ssdtPRGen is not reading the Coffee Lake.cfg file but it is reading the User Defined.cfg. I have never been so baffled by something like this.

Sorry I did not put my other PC in signature, its an OverPowered Laptop OP-LP3, a Walmart brand has an i7-8750H processor that is the one I am trying to get a ssdt.aml with.

I still use plugin type and cpufriend because with cpufriend I get down to 1000mghz at x10 without cpufriend I have 1300mhz at x13. Originally my friend created the ssdt.aml with ssdtPRGen, so I do have a working cpufriend and CPUFriendDataProvider, I just wanted to get the ssdt.aml again and it got deleted. I don't understand why it just stopped working after installing 10.14.4 or something else went wrong trying to figure out exactly what.

It never creates the ssdt.dsl or ssdt.aml. It does create the ACPI folder, look at my post above after running ssdtPRGen it aborts.

Thanks for clearing that up. I also posted about unknown processor and have been trying everything I know I can do and ssdtPRGen keeps telling me unknown processor even though I have followed all the steps. My friend has the Walmart brand OverPowered 15 inch with i5-8500H and MacOS 10.14.4 and is able to run ssdtPRGen no problems. I have the 17 inch i7-8750H and now on MacOS 10.14.4. Any ideas or work arounds?

If I go with this step do I still need step B and Step C or just Step A followed by the procedure I quoted? Reason I ask is because if I skip part B and C and compare the injector data, some cf-frequency-data is lacking in the injector but also duplicated to.

Are there any issues with running ssdtPRGen.sh in the latest released version of Mojave 10.14.4? I keep getting unknown processor and the processor is in Coffee Lake.cfg and I have followed the steps. I was successful running this on another laptop that is Kaby Lake but that version of MacOS is 10.14.2 this is why I am asking if anyone has tried running ssdtPRGen.sh in 10.14.4 without any issues? My mobile processor is i7-8750H and won't go less than 1000Mhz x13 CPU Package Multiplier so I need to run it, I want it down to x10 800mhz minimum. My friend ran this for me on my laptop a month ago since I was new to this procedure and I was on MacOS version 10.14.3 no problems running ssdtPRGen on that version and it brought it down to x10 800mhz. I am trying this procedure myself now but I am on MacOS 10.14.4 and I keep getting this unknown processor. The ACPI folder is created after running ssdtPRGen.sh inside the ssdtPRGen. osxfr33ks-MBP-2:ssdtPRGen osxfr33k$ ./ssdtPRGen.sh -p 'i7-8750H' -f 2200 -turbo 4100 ssdtPRGen.sh v0.9 Copyright © 2011-2012 by † RevoGirl v6.6 Copyright © 2013 by † Jeroen v21.5 Copyright © 2013-2019 by Pike R. Alpha ----------------------------------------------------------- Bugs > https://github.com/Piker-Alpha/ssdtPRGen.sh/issues < System information: Mac OS X 10.14.4 (18E226) Brandstring: "Intel® Core i7-8750H CPU @ 2.20GHz" Override value: (-p) processor model, now using: i7-8750H! Override value: (-f) clock frequency, now using: 2200 MHz! Override value: (-turbo) maximum (turbo) frequency, now using: 4100 MHz! Error: Unknown processor model ... Visit http://ark.intel.com to gather the required data: Processor Number TDP Low Frequency Mode (use AppleIntelInfo.kext) Base Frequency Max Turbo Frequency Cores Threads Aborting ... Done. osxfr33ks-MBP-2:ssdtPRGen osxfr33k$ Also hello to MaLd0n .

Hi Oldnapalm, Would you happen to have the latest version for Yosemite 10.10.2? Thanks EDITED next day: Found a working one from your Thread over at Insanely. The one you posted with SPDIF "in" gives me all the ports for both output and input. Thanks

Thanks for sharing. I can use that one for sure and I will change ID. Are those settings also for Nvidia for GTX 3x series for your notebook? Thanks Again!! Never mind I see from your signature its an ATI (AMD). I can just copy the settings from the Native AGPM they should be very close to the card I have since the hardware are very similar.

Thanks for trying to make it work. The Display still remains dark upon wake. External HDMA and VGA wake no problem its just the internal VGA display will not display on wake. My SMBIOS should be MacBookPro6,2 it is nearly the same as the real one except it has a GT 330M. Mine is a GTX 360M but very close to being the same. Models before and after do not have the same graphics at all. Where could I find a LegacyAGPM that will include the MacBookPro6,2 and just put my Device ID in it? I changed the device ID in the Native AGPM under macBookPro6,2 to my ID and it now displays vendor/device on verbose. See my first post, is this how it should display or its still incorrect?