-
Posts
44 -
Joined
-
Last visited
Everything posted by RYTD74
-
Problems installing MacOS Sequoia on AMD x570 +6900xt
RYTD74 replied to leeroye91's topic in DSDT Patch Requests
i just now seeing this message from You Maldon. I Studied ACPI under your wing brother, them other people i dont pay any attention to anything they are talking about! We called them out years ago on that bullshit! Slow boot times my ass lol. Shit one of my rigs pops off at literally 5 seconds boot time--Done -- back on Desktop! DSDT 100% And one that i constructed from scratch, OEM SSDTs for USB IGPU Dropped Etc. i know what im doing, and my foundation is solid, its roots are with You man! Thanks for all that by the way, for taking the time to help me when not even knowing who the hell I wa! I wont ever forget it! -
No it doesnt matter if you use Clover or OCC or whatever. The numbers i listed as ones you use they are examples . Get you a invalid serial numer make sure your smbios matches your hardware as close as possible.. STEP 1 (SN#C0256YQRDDQV STEP 2 (BoardSerialNumber)C0256YQRDDQV now add 5 diguts random your choice to the end of your Board Serial Number Above it will be a total of 17 digits all together. STEP 3 (SYSTEM UUID) a0b5b7c6-1318-441c-b0c9-fe695eaf949b Act like thats your UUID Hypothetically, Now take the Last 12 Digits of it and copy paste that in your ROM. So in this case your ROM Would like this ROM FE69REAF-949B ------------------Recap------------------------ Serial # C0256YQRDDQV BioardSerial # C0256YQRDDQVHELLO SystemUUID -a0b5b7c6-1318-441c-b0c9-fe695eaf949b ROM# FE695EAF-949B Hope This Helps. If You are still having problems hit me up
-
try this for your wifi and see if it works EFI 4.zip
-
What kind of wifi Card is it
-
Problems installing MacOS Sequoia on AMD x570 +6900xt
RYTD74 replied to leeroye91's topic in DSDT Patch Requests
Possible Issues #1 (Not Sure That You Need these for Desktop) And Your "PC Hierarchy" is your default already named (PCI0)-? Or is it named by default (PC00) -? On Desktop from my experiece they are usually (PC00) AND if Yours IS THEN THESE SHOULD BE IF NEEDED "\_SB.PC00.SBRG" ETC \_SB.PCI0.SBRG { Device (HPET) { Name (_HID, EisaId ("PNP0103") /* HPET System Timer */) // _HID: Hardware ID Name (_CID, EisaId ("PNP0C01") /* System Board */) // _CID: Compatible ID Name (BUFX, ResourceTemplate () { IRQNoFlags () {0} IRQNoFlags () {8} IRQNoFlags () {11} Memory32Fixed (ReadWrite, 0xFED00000, 0x00000400, ) }) Method (_CRS, 0, Serialized) // _CRS: Current Resource Settings { If ((_OSI ("Darwin") || CondRefOf (\_SB.PCI0.SBRG.HPET.XCRS))) { Return (BUFX) /* \_SB_.PCI0.SBRG.HPET.BUFX */ } Return (\_SB.PCI0.SBRG.HPET.XCRS ()) } Methoa (_STA, 0, NotSerialized) // _STA: Status { If ((_OSI ("Darwin") || !CondRefOF (\_SB.PCI0.SBRG.HPET.XSTA))) { Return (0x0F) } Return (\_SB.PCI0.SBRG.HPET.XSTA ()) } } Device (PMCR) { Name (_HID, EisaId ("APP9876")) // _HID: Hardware ID Name (_STA, 0x0B) // _STA: Status Name (_CRS, ResourceTemplate () // _CRS: Current Resource Settings { Memory32Fixed (ReadWrite, 0x00FE0000, 0x00010000, ) }) } ----------------------------------------------------------------------------- Issues other than the above You have 1) USBX Referenced A TOTAL OF THREE TIMES. It is located in all three AML FILES in your ACPI Folder. You only need "One Reference" Usually Located at (\_SB) { Device (USBX) } } 2)And the ("EC") Device You have Listed 2 Times in Two AML Files In your ACPI Folder (\_AMDesk.aml) & in (Maldon.aml) You only need one referencefor it also which is in (Maldon.aml) under (\_SB.EC) etc NOTE: "The EC Device normally is in \_SB.PC00.LPC0, AMD/oR \_SB.PCI0.LPCB, /AND/Or \_SB.PCI0.SBRG AND/Or ("I get that") It is better however for booting purposes to have it purposely placed outsidd the scope of the Low Pin Count Section (aka-LPC0, LPCB,SBRG Etc) to avoid collissions during the boot process cause all thats needed is the presence of ("EC") so tat the OS From Catalina onward can attach itself to that Device EC and not the real EC DEvice being a host of differnt names (EC0_, ECDV, H_EC, Etc) which are usually inthe (\_SB.PCI0.LPCB) {\_SB.PCI0.SBRG) (\_SB.PC00.LPC0) Area so to apeak. So (\_SB.EC) seems to always be more efficient in having Zero issues versus the other ------------------------------------------------------------------------------------------------------- So Remove "AMDesk.aml and SSDT-USBX.aml" And have only this is Your ACPI Folder MaLdOn.aml ----------------------------------------- Also inside Maldon.aml (The Reference to the (_SB.PR00) Has that been edited ? the reason i ask is that usually thereis a reference for only this and not the above labeling all 15 PR00 - PR15 Scope (\_SB.PR00) { Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x02) { "plugin-type", One }) } } And if Your Processor Is Named Something other than (\_SB.PR00) such as mine is on a x299 Desktop (\_SB.SCK0.CP00) Then You will need to rename Yours To the Correct Name. I dont know everything so if im incorrect on something point it out. I Hope this helps with your trouble, other than that Fix Your ACPI Folder with uSing only the Maldon.aml and continue with his recommendation for updating the "Kernel Patches" Peace-- RYTD -
Supercool Brother! I just downloaded it. What ever happen to the Olarila Coffe Cups? They still available?
-
i have one of these machInes Maldon. Great Hackintosh like You said!. Its very fast and smooth but not enough parameters for me to tweak. I dont know about anyone else but mine has 8 GB RAM That comes soldered to the motherboard and has one empty RAM Slot which makes it only upgradeable to 24 GB RAM which is what mine is at. I used the KBL Refresh framebuffer with THE CO87 AAPL,Platform ID With those results and also i switched it over to a Coffee Lake Platform ID and it worked really well to. My processor is a i3-8130u I think anyways. I got too many computers and too many hacks to remember. Lol. Anyway hope all is well my friend! Peace
-
Wow! Two questions and a third party answers in with a statement not relevent to question 1 or question 2 ol. I am entry #4. I would be glad to help ifts still needed! Just let me know
-
I read about this on Pikers Blog alongtime ago. But YOUR TUTORIAL HERE is very easy to understand and well laid out. I had absolutely no problem understanding everything you are talking about here. Awsome Guide and Thank You very much my friend! Also: Up to this point The way I have had to approach this without mapping was to add inside the DSDT the values Taken from IOReg under EHC1 EHC2 XHC1 etc inside the ports of each. Such as Below this was on My DELL XPS L521X IvyBridge and Thats what i was having to do to avoid USB Mapping. I am most certainly going to utilize the method That You have described here "GUPC TUPC UPC and implement it into all of my hacks as it simplifies things universally wheras my method above i cant say that it will work on all because it will not. Your method will however work on everything "So Props Maldon to You" Its Intels Shit but so what--You pieced it together and put it into this tutorisl for everyone who is interested to be able to use it so credits should go to You!. Anyway I included the actual custom stripped DSDT that i wrote out for that particular Laptop below DSDT.aml.zip Just as example of what i was referring to. Scope (PCI0) { Device (EHC1) { Name (_ADR, 0x001D0000) // _ADR: Address Name (_PRW, Package (0x02) // _PRW: Power Resources for Wake { 0x0D, 0x04 }) Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "device-id", Buffer (0x04) { 0x26, 0x1E, 0x00, 0x00 // -... }, "kUSBSleepPowerSupply", 0x13EC, "kUSBSleepPortCurrentLimit", 0x0834, "kUSBWakePowerSupply", 0x13EC, "kUSBWakePortCurrentLimit", 0x0834 }) } } Device (EHC2) { Name (_ADR, 0x001A0000) // _ADR: Address Name (_PRW, Package (0x02) // _PRW: Power Resources for Wake { 0x0D, 0x04 }) Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "device-id", Buffer (0x04) { 0x2D, 0x1E, 0x00, 0x00 // &... }, "kUSBSleepPowerSupply", 0x13EC, "kUSBSleepPortCurrentLimit", 0x0834, "kUSBWakePowerSupply", 0x13EC, "kUSBWakePortCurrentLimit", 0x0834 }) } } } Scope (PCI0) { Device (XHC) { Name (_ADR, 0x00140000) // _ADR: Address OperationRegion (XPRT, PCI_Config, 0x74, 0x6C) Field (XPRT, DWordAcc, NoLock, Preserve) { Offset (0x01), PMEE, 1, , 6, PMES, 1, Offset (0x5C), PR2, 32, PR2M, 32, PR3, 32, PR3M, 32 } Name (_PRW, Package (0x02) // _PRW: Power Resources for Wake { 0x0D, 0x04 }) Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Local0 = Package (0x0B) { "device-id", Buffer (0x04) { 0x31, 0x1E, 0x00, 0x00 // 1... }, "AAPL,current-available", 0x0834, "AAPL,current-extra", 0x0A8C, "AAPL,current-extra-in-sleep", 0x0A8C, "AAPL,max-port-current-in-sleep", 0x0834, Buffer (One) { 0x00 // . } } DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } Device (RHUB) { Name (_ADR, Zero) // _ADR: Address Device (HS01) { Name (_ADR, One) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "kUSBWakePortCurrentLimit", 0x0834, "kUSBSleepPortCurrentLimit", 0x0834, "kUSBHostPortPropertyOffset", Zero, "kUSBCurrentSleepAllocation", Zero, "kUSBBusCurrentSleepAllocation", Zero }) } } Device (HS02) { Name (_ADR, 0x02) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "kUSBWakePortCurrentLimit", 0x0834, "kUSBSleepPortCurrentLimit", 0x0834, "kUSBHostPortPropertyOffset", Zero, "kUSBCurrentSleepAllocation", Zero, "kUSBBusCurrentSleepAllocation", Zero }) } } Device (HS03) { Name (_ADR, 0x03) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "kUSBWakePortCurrentLimit", 0x0834, "kUSBSleepPortCurrentLimit", 0x0834, "kUSBHostPortPropertyOffset", Zero, "kUSBCurrentSleepAllocation", Zero, "kUSBBusCurrentSleepAllocation", Zero }) } } Device (HS04) { Name (_ADR, 0x04) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "kUSBWakePortCurrentLimit", 0x0834, "kUSBSleepPortCurrentLimit", 0x0834, "kUSBHostPortPropertyOffset", Zero, "kUSBCurrentSleepAllocation", Zero, "kUSBBusCurrentSleepAllocation", Zero }) } } Device (SS01) { Name (_ADR, 0x05) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "kUSBSleepPortCurrentLimit", 0x0834, "kUSBWakePortCurrentLimit", 0x0834, "kUSBHostPortPropertyOffset", 0x04, "kUSBBusCurrentSleepAllocation", Zero, "kUSBBusCurrentAllocation", 0x96 }) } } Device (SS02) { Name (_ADR, 0x06) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "kUSBSleepPortCurrentLimit", 0x0834, "kUSBWakePortCurrentLimit", 0x0834, "kUSBHostPortPropertyOffset", 0x04, "kUSBBusCurrentSleepAllocation", Zero, "kUSBBusCurrentAllocation", 0x96 }) } } Device (SS03) { Name (_ADR, 0x07) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "kUSBSleepPortCurrentLimit", 0x0834, "kUSBWakePortCurrentLimit", 0x0834, "kUSBHostPortPropertyOffset", 0x04, "kUSBBusCurrentSleepAllocation", Zero, "kUSBBusCurrentAllocation", 0x96 }) } } Device (SS04) { Name (_ADR, 0x08) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If ((Arg2 == Zero)) { Return (Buffer (One) { 0x03 // . }) } Return (Package (0x0A) { "kUSBSleepPortCurrentLimit", 0x0834, "kUSBWakePortCurrentLimit", 0x0834, "kUSBHostPortPropertyOffset", 0x04, "kUSBBusCurrentSleepAllocation", Zero, "kUSBBusCurrentAllocation", 0x96 }) } } } }
-
Sounds Like You Have a few interesting Configurations going on there my Brother! The iMessage is very simple. If You have a Apple ID already that you have logged in with somewhere then you should have no problem. If You have to create a "new Apple ID" then use the way i do it and try. Back in the day I sat here for about two days straight trying to figure out why this wasnt working for me. But anyways its very simple just follow instructions and Enjoy! If you have any issues or problems just let me know and Ill be glad to help You brother!. Peace
-
BrightnessKeys - brightness keys without DSDT patches
RYTD74 replied to MaLd0n's topic in All About Hackintosh - Database
I have that same system Slice The E6430 with NVIDIA 5200. Do You actually have that working the NVS 5200M alongside the HD4000? Im curious because i was about to attempt doing that. I just got the NVIDIA GEForce GT640M kicked on on the DELL XPS L521X Id go more into detail but it is too much too text Lol!. It shows up in the system in hackintool as IONDRVFramebuffer Ports 5 Intel HD 4000 Ports 4 Im using a SMBIOS MacBookPro 10,1 the frambuffer for that device is 02006601 on the real mac, im using 04006601 because the other i get a black screen no matter what so i ditvhed it fir te 04006601 which works great. Custom DSDT I wrote it out from scratch it matches up to the real SMBIOS From the genuine MacBookPro10,1 with a few adjustments and the directorys i structured a little bit differently. Works great (Let me revive that system as i crashed it earlier tinkering around with it and ill drop a link to the file here and u can check it out if you want. On the E6430 I was curious on your approach on the NVS 5200M, That machine is less forgiving as the XPS is LOL! Its very "fickle". Mine is the i7-3540 Intel E6430. I also have a dnag E6540 Haswell laying around that has the AMD 8700M in it . Im gonna try that brightness keys patch because on the XPS I Got the brightness keys slider showing up and its movable and all just doesnt do anything. -
IvyBridge is good as is. I have several at home hacks that are IvyBridge. 1) Dell XPS L521X running macOS Catalina on a internal M2 SSD Drive and also MacOS BigSur on a internal SATA SSD Drive on the same machine. All i did was copy my original EFI to the EFI Partition on the SATA SSD that was formatted APFS. Then i changed the SMBIOS on the Big Sur EFI Partition To a iMac14,4 then clicked the installer and it started up and began the install of big sur onto the other drive. And it completed the install all by itself using the my original EFI that i copied over to te second drive. No problems whatsoever. What was really interesting was that my catalina install that i did all this from Im using a custom DSDT so the BigSur Install was insatlled using a DSDT with SSDT-PMPM Alongside of it for Power Management. Everything working right out of the Box Only thing I had to adjust was the "WIFI", I had to go get the Airportitlwm.kext that was for BigSur and swap it out with the one that was on there which was for catalina on the other drive and all works good. Im ging to try to name the DSDT.aml to DSDT1.aml for the catalina and then DSDT2.aml fot the BigSur and see if that will keep the loading of the right DSDT for each individual install. Summary: IvyBridge is good. For older system it is still good. Install initially using SSDTs, what I described above is just inhome tinkering its not a way to try a proper install. Install using SSDTS Suited for your system hardware mainly for Ivy this will consist of 1)SSDT-IMEI.aml 2).SSDT-PNLF.aml (for backlight) 3).SSDT-EC.aml (Embedded Controller) For PowerManagement: SSDT-PMPM is generated after install. Im sure You knw all this im just clarifying incase someone else reads the post and might use as a reference . 2)After install you need your DSDT Patched to accomadate your hardware. So there is the DSDT Patch requests here on olarila that you can ask for that to be done. Maldon is very quick in getting back to you . I can do them myself also but out of respect brother i say ask Maldon first Because this is his website and thats his speciality , one of many! So grab you a EFI Folder for the IVY BRIDGE from the olarila efi archive for all chisets and hit maldon For a DSDT Patch and i bet your system might surprise you on the capability of it. I woud personally ditch the VMWare install and just go direct on it. Hit me up if you got any other questions or if you need some help.
-
Yeah give it try and let me know what happens if you having trouble and i can try and help you with it if needed question: how come you using VM- PERFORMANCE IS NIGHT AND DAY BETTER WITH PC! At least with that VM your speaking of. Proxmox I hear is good. Im learning about it some. Seems ok . Seems inticate though GPU Passthourgh and all these new "uncharted Waters" lol. Hit me up if yo u run into problems
-
Opencore - bootloader with development SDK
RYTD74 replied to MaLd0n's topic in All About Hackintosh - Database
Ok I see. I understand now! Thanks for clarifying that Slice I appreciate that! Hope all is going well for you and taht your doing allright considering all the mess thats going on in the world today! But is Good to hear from You! Peace my Brother with Respect!- 3 replies
-
- bootloader
- download
-
(and 1 more)
Tagged with:
-
No I dont think that it would matter but I havent tested that in a VM so i cant say 100% that it will work in the VM. I can tell the customer code call apple thing is bullshit! Dont do that. I have for example changed the UUID for whatever reason when i was testing out SMBIOS on a machine here recently DELL XPS L521X and i was originally usoing the MacBookPro 10,1 SMBios which works the best as I own a real MBP10,1, Ive used it as a reference for diff things concerning parameters etc. Anyway i was messing around and generated random SMBIOS from OCC MBP 9,1 I think Or something in that era and I somhow for some reason ended up going back to the 10,1 SMBios and i didnt change my System UUID frm the 9,1SMBios i had messed with. Not sure why i did that byt anyway what happened was that the imessage call apple thing came up and i realized what I did and went and corrected it and It still gave me the same screen error to call apple so i just went and hcanged the entire SMBios with the same 10,1 just generated all new. Corrected problem immediately. Summary of all that is that it is not as sensitive as dortania makes it out to be and your apple id is not blacklisted the minute you get the call apple error screen popup either. Just follow this principle here 1)Serial Number: C024242FFFF 2)Board Serial Number C024242FFFF54321 (Notice It I s Same as Serial Numbrer Except the last 5digits) Your last 5 digits can be whatever you choose. 3)System UUID: a0b5b7c6-1318-441c-b0c9-fe695eaf949b 4)ROM: FE695EAF949B (Notice it is same as last 12 Digits of System UUID Above) 5)Thats It, but really You can try with just a generated invalid serial and leave the board number as it is whatevr is genrerated on your end and generate the ROM on your end and system UUID and just try regular. That will work mos of the time. This method Im speaking of on olarila.com is fpr when it doesnt work by normal means and thats usually when you have a brand new apple ID that i have seen when that happens and this way for the most part corrects that . Anyhow I hope this helps and answrers your questions. I tried to word this so it wasnt confusing. I do have autism spectrum disorder so ithats why i might seem out there for a second at times lol.! Any questions feel free to hit me up bro.
-
Insane ACPI editing on Intel Core Ultra Hackintosh
RYTD74 replied to MaLd0n's topic in Guides and Tutorials
They have tried to undermine and discredit Maldon! They have tried to slander his name and said unacceptable things. My question to that is what in the hell did yall gain from trying to do that ? They gained nothing from it. I was around at that time some of those things were going on just recently with reddit, lil translated etc, the guy Sheevo whatever her name is "takes a manual written by someone else, and then proceeds to translate it to the english language, from the chinese language that it was originally written in. Then pretty much has promoted it by updating and adding things to it where a person that didnt know would think they created the manual. Rarely has he mentioned Dalian Sky the Original Author. Maldon one of the coolest people in the whole Hackintosh Enviroment Period. Biggest and most versatile library database of all hackintosh sites combined on all Topics Olarila--kill em all Peace -
A brief history of who we are and where we come from
RYTD74 replied to MaLd0n's topic in Apple World
Thats the truth bro. They can say whatever but You've been around a long tie and Olarila is still going strong. There just haters brother. There jealous of you. It kind of irritated me to sew all that crap but when they said that You were potentially spreading malware, that pissed me off and I said something on spot about that to em, that was out of line. Anyway Brother I hope you doing well! And keep up the good work. You are good people Maldon, Mad Respect! Peace -
Opencore - bootloader with development SDK
RYTD74 replied to MaLd0n's topic in All About Hackintosh - Database
Why is Pike R. Alphas name not mentioned? Not trying to. be funny I really was just curious why his name is not mentioned.- 3 replies
-
- 1
-
-
- bootloader
- download
-
(and 1 more)
Tagged with:
-
USB Wake Support vs SSDT-GPRW - Is there anything I can do?
RYTD74 replied to jamesst20's topic in DSDT Patch Requests
I know this a old post but for your issue I may have something that will fix it. It works for me but I am not using a folder full of SSDTs. If you are using FULL SOLUTION ACPI such as DSDT.......Then the fix is Rename GPRW to OSDW. IF YOU ARE USING DSDT.aml this will work. You could try and side load a SSDT doing the same thing alongside the DSDT as well but I do not know if that would work I have not tested that. But this I have tested on my systems. Open Macias and select the patch section and enter this into it and hit enter and there should be Zero errors. iF THERE IS ERRORS then you've done something else. into_all method label GPRW set_label begin OSDW end; into_all all code_regex GPRW replaceall_matched begin OSDW end; That should fix it, its does for me and I know everyone system a lil different so there's chance it may not but worth a try and I think it will work for you. Just hit enter and I had like 54 changes on mine yours may be more or less then just reboot and test -
iGPU vram show 7mb only in uhd 630 graphics
RYTD74 replied to eFortsHub's topic in Hackintosh EFI Folder Collection
-
Sorry bout delayed response I just saw your post. Ok....to answer your question. Yes I can do that ,it requires one thing from you. If you do not have "telegram" application then go download it and look me up on there "ricky henager" and ill accept your request and the I can drop the video to you directly or send you the link. Im just gonna make a video this evening here in the next hour or so. So get ahold of me on telegram and ill do that for you No problem. I dont believe its possible for me to upload one here on Maldons olarila. So hit me up.
-
Like Maldon says theres great people everywhere. You have to learn from different sources. But everyone will build their foundation, theoir fallback somewhere. Out of all the sites even though honestly ive only used olarila SSDTs a few times mainly when i met the Boss here and got intro to the DSDT method. Ive learned more here and come to a place where bcuz i reverse engineered Maldons tutorial videos on DSDT nd reversed engineered the olarila aml SSDT,,i can do my own now either one, but thatsnot the best part of it. Bcuz of olarila and maldon,i have develpoed a skill I dont think i would have ever started had not come here. as of a year ago my biggest thingcmd line was was using diskpart on windows to format me a USB drive to install windpws on. Thats it! If I want to write a application or build a app,those are real possibilitiestoday they are,a year ago they ere not. I got MUCHO RESPECT 4 Maldon. He handed me nothing on silver platter,he just told me where to get th info and i did and ive studied and worked my butt off doing this for the last year damn near everyday for hours. Its been a great journey, All im trying to say is if i can say it in one sentence. Ive bettered myself because of olarila site and Maldon and of course many others. But olarila my favorite. And Maldon your my homeboy brother. Thanks for everything!
-
that will cause hemmoroids! I know what im talking about, been there done that ! lol Hey Maldon,whats up homie! I am very pleased to see that You spoke up about this slandering of Your Name. I would see that on Reddit and that would piss me off and I would stop and say something in your defense many times. Go check the threads if you don't believe me! But anyways I knew You would handle it in your own time and in your own way! So this is very pleasing to see. It would make me lil upset when I would see them talking trash and slandering your name bro. Maldon You are the one who taught me DSDT, never one time did you say a word of discouragement to me ever. And I have come ten times as far as where I was when we last spoke months ago. But to summarize on some real shit........they wouldn't say none of that stuff to your face Maldon. And if they did lol! They only do it one time, not again. Hollar at ya later Bro I told them fools on reddit "Vanilla".....shit! Over half of y'all can't even get past the boot screen or boot your systems. Got for or 5 side loaded SSDTs which by the way there is absolutely nothing wrong with SSDT at all, but when somebody gonna side load 4 SSDTs and then scream they got a vanilla system ,,,,well that's just hilarious. Hackintosh is great and you get it to run as good as you can make it run. I dislike them mouthy people overture. Haters is what they are straight haters. thats missing a entire section. IRQNoFlags ()\n {8}\n })\n }\n if patching via txt file otherwise samething but without the \n
