Jump to content

I'm terrified of DSDT

652

By 652,
in General Discussion

 Share
17 posts in this topic

Recommended Posts

652
652
Posted
Posted

I’ve been trying to turn my workstation into a hackintosh for years now but I have yet to succeed. I’ve made slow progress over the years and believe that it’s impractical for a reasonable percentage of the visitors to this forum to achieve a fully functional machine with OSX running on it let alone get their computers to boot up even.

 

But me being the open minded and pragmatist that I am. Here I am ready to try again. I’ve been reading about some kind of tribal voodoo shtick for a few years and it’s always pummeled my brain into a fine mush.

I’ve watched videos I’ve watched tutorials, I’ve done it all. Each source has their own story; this forum has no story at all about DSDTs until recently as far as I know.

 

So let’s get started, here are my specs and people on this forum have told me over and over again that my specs are perfect for a hackintosh.

 

Asrock x58 Supercomputer

Intel i7 920

4GB of RAM (expandable to 24GB of RAM)

Samsung SSD

750w power supply

3x3TB HDDs = 9TB

nVidia GTX 275

 

I need help making a DSDT file for my computer. And I'm assuming from all that I've learned that this will be all I need to turn my machine into a fully working hackintosh.

 

A short question before we start:

1. My motherboard has version 2.90 of the bios flashed. The most current version is 3.40. Do you recommend that I flash the most current version before I begin?

 

I got OSX 10.7 to install on my workstation last year and as far as I can remember, everything worked except sleep and Audio; I believe I even got my graphics to work, but I'm not sure.

 

I got the audio to work using a voodoo driver but that caused a new problem. The computer would only boot up 50% of the time. Sometimes it would take a second try to boot up again. And also caused kernel panics once in a while. Without the voodoo audio the computer would boot up 100% of the time and there were zero kernel panics. When I did use the audio there was a static sound, the audio was not clear. I believe my motherboard required ALC890 which I could not find. Someone recommended I extract and edit a DSDT file to sidestep this problem last year. But I could never figure it out. 

 

 

I'm ready to upgrade to a Hackintosh! What do I need to do guys? What is the best tutorial! How do I get this done today? !!

Link to comment
Share on other sites
Alex009988
Alex009988
Posted
Posted

1)I did use the last Voodoo at the time and the only one that worked, well... somewhat worked.

 2)What do you mean by that?

The last voodoo doesn't work for and you use another, do you?

2) I meant if you made speadsteep working and if you use native AppleCpuPowerManagement without having kext crutch such as NullCPUPowerManagement.

Link to comment
Share on other sites
artur_pt
artur_pt
Posted
Posted

hello

 

i think u should bios last version.. is because of that .. exists bios updates.. generally it have improvements..

 

if u use nullcpupowermanagement .. u don't have native powermanagement.. like kext name say is to null apple kext

 

good hack

Link to comment
Share on other sites
Eloi Bermejo
Eloi Bermejo
Posted
Posted

Word of a newbie? Well, I once was terrified of DSDT as you are, but since I always tried to make a hackintosh out of (previously) totally unusable computers, I had no chance of getting a DSDT ready to go.

 

It is first and foremost a work of patience. Of course it helps if you read the Acpi specs, but even without it, you can get a lot of patches around, and ultimately your work is to try and try and try, every single one of them, until you're satisfied with the way your computer works. Change it, and then check if the computer boots, if it impacts anything like sleep/wake. Make notes, and backup your DSDT file every step of the way, so you can go back, if you later notice something doesn't work anymore.

 

By doing this, my old HP DV2268 worked as good as any 2-3yr old MacBook. Up until Lion that is... No 64b graphics though.... :(

 

If you want an example, for the removal of NullCPUPowerManagement, you have to change HPET. On the other hand, changing RTC didn't do anything for my computers, they worked fine either way. DSDTSE will help you a lot.

 

Good luck!

Link to comment
Share on other sites
artur_pt
artur_pt
Posted
Posted

hello

 

to install mac os x .. u don't need patched dsdt .. DSDT is not GOD.. it helps if u have compatible hardware .. to comunicate with mac os x..

 

but to install and having a working mac os .. is not need..

 

after install u can see .. and i can help u to patch the dsdt..

 

only post u untoched dsdt.. and i will edited for u..

 

good hack

  • Like 1
Link to comment
Share on other sites
  • 2 weeks later...
652
652
Posted
  • Author
Posted

That's really nice of you artur-pt. Sorry I've been off for a while. Been on a spiritual journey and working a little.

 

 

 

NOTE:

I added a ".txt" extension because this forum wouldn't allow me to upload the file without a file extension.

Asrock.txt

Link to comment
Share on other sites
652
652
Posted
  • Author
Posted

Great artur-pt!

 

I love you, you’re awesome!

 

 

I'll do a Clean Install of OSX on my Supercomputer sometime next week, I'm crazy busy, But I'm MAD excited about this, I love you thanks.

Link to comment
Share on other sites
Gringo Vermelho
Gringo Vermelho
Posted
Posted

AppleHDA loads on some systems but then fails to work because it hasn't been patched. This leads to conflicts with VoodooHDA which can cause kernel panics during boot.

 

Delete AppleHDA.kext when installing VoodooHDA....and beware of OS updates. Or try to find an AppleHDADisabler.kext if such a thing exists.

 

 

DSDT is not a miracle cure, it cannot replace software drivers. Patching your DSDT, you can nudge Apple drivers into loading for, or working better with, already compatible hardware that's similar to what Apple use.

It's in the name. DSDT means "Differentiated System Description Table", and it is just that - a description of certain on-board devices or functionality that is passed on to your OS via ACPI.

You edit your DSDT in order to fix a specific issue, in most cases related to power management. First you must know what the issue is. Then you can look around and try to find out if there's a way to fix it by patching your DSDT. If your hardware is not near-compatible to begin with, editing DSDT will not help.

 

For example, the HDEF device DSDT patches are not hardware specific, apart from some cosmetic details you can add if you wish.There are two versions of it, one for motherboards with Nvidia chipset and one for boards with Intel chipsets. But my point is; the code is added purely for the purpose of getting AppleHDA.kext to properly "attach" itself to your audio hardware.

You still need to patch AppleHDA.kext in order to have working audio.

 

Another example is the LPC device edit. On some motherboards AppleLPC.kext (which is needed for CPU power management to work properly) does not load even if the LPC device is compatible.

What you do in this case is override the device ID (the requirements went up for 10.8.5, it needs a little more) of the LPC device via DSDT.

This is necessary because the driver loads based on an internal list of compatible devices and expects to see a certain device ID. So, instead of modifying the driver itself (a simple info.plist edit), which gets tedious if you have to do it with each OS update, you can simply give it the device ID of a known compatible LPC device via DSDT, and trick AppleLPC.kext into loading this way.

 

The same goes for all the USB device patches. All the code examples you can find are about (again) describing the devices to OS X in such a way that they will work better with unmodified drivers.

  • Like 2
Link to comment
Share on other sites
  • 2 weeks later...
rvxtm
rvxtm
Posted
Posted

hello

 

there it is

 

attachicon.gifDSDT.zip

 

read and apply

 

http://olarila.com/forum/viewtopic.php?f=28&t=1703

 

good hack

Can you please take a look over my dsdt ? 

 

Untouched : CLEANdsdt.aml.zip

 

My Edit : dsdt.aml.zip

 

did i edit my dsdt ok ? the hardware is the one in the signature.

Link to comment
Share on other sites
rvxtm
rvxtm
Posted
Posted

hello

 

if u want u can try this one

 

attachicon.gifDSDT.aml.zip

 

good hack

thank you, i will try and report for any changes, btw i still use the 3rd party sata kext to not have yellow drive icons, do i still need to use that ?

 

EDIT: using your dsdt i have the 10 degree temperature plus in mavericks, i see that you deleted the lines in PX40 :

Method (_DSM, 4, NotSerialized)
                {
                    Store (Package (0x08)
                        {
                            "device-id", 
                            Buffer (0x04)
                            {
                                 0x18, 0x3A, 0x00, 0x00
                            }, 
                            "compatible", 
                            Buffer (0x0D)
                            {
                                "pci8086,3a18"
                            }, 
                            "IOName", 
                            Buffer (0x0D)
                            {
                                "pci8086,3a18"
                            }, 
                            "name", 
                            Buffer (0x0D)
                            {
                                "pci8086,3a18"
                            }
Link to comment
Share on other sites
artur_pt
artur_pt
Posted
Posted

hello

 

if any problems u can solve .. u should edit the parts u know

 

if u still have yellow drive icons

 

try apply this patch

# Change ID of SATA device to fake ESB2 AHCI (silver icons for internal HDs instead of orange ones)
#
into method label _DSM parent_adr 0x001F0002 remove_entry;
into device name_adr 0x001F0002 insert
begin
Method (_DSM, 4, NotSerialized)\n
{\n
    Store (Package (0x02)\n
        {\n
            "device-id", \n
            Buffer (0x04)\n
            {\n
                0x81, 0x26, 0x00, 0x00\n
            }\n
        }, Local0)\n
    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))\n
    Return (Local0)\n
}
end

good hack

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...